Instructions for using arduino nano #2
Comments
|
It has been a while since I initially coded and tested with the Arduino Nano, but I think it may still work. The reason I stopped working with the Nano was it was more expensive than the Wemos D1 Mini and you don't get the speed or logging (memory) that you get with the ESP8266 core. You will also have to read through the code in the INO file for the pins -- they are there. |
|
Hi I managed to get it working on arduino nano. barro is working and osd
display is working but voltage is just showing 0v have set up with voltage
divider as your recommendation on pin a0 but not getting read out any ideas
why would be helpful. Thanks
…On Thu, 19 Jan 2023, 00:11 Qrome, ***@***.***> wrote:
It has been a while since I initially coded and tested with the Arduino
Nano, but I think it may still work.
In the OSD_positions_config.h -- fine the line:
#define ESP8266
and comment that out.
The reason I stopped working with the Nano was it was more expensive than
the Wemos D1 Mini and you don't get the speed or logging (memory) that you
get with the ESP8266 core.
You will also have to read through the code in the INO file for the pins
-- they are there.
—
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANQOVDU2UNUB5OVDLNYC5LDWTCBBRANCNFSM6AAAAAAT6GYROI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I am quite sure the Voltage divider should work on the Nano as that is where I originally tested it out. I don't know, off the top off my head, why you would not be able to read the voltage. |
|
thanks for getting back to me so fast, could it be anything to do with
speed/refresh rate? I'm not a coder, just have a little knolage how to
compile and comment in/out things from the multi wii days ?:)
I have an esp8266 nodemcu with wifi I found in my parts bin would this also
work?
would love to get this working maybe I just get the wemos d1 is it
thanks pete
…On Thu, 19 Jan 2023 at 16:22, Qrome ***@***.***> wrote:
I am quite sure the Voltage divider should work on the Nano as that is
where I originally tested it out. I don't know, off the top off my head,
why you would not be able to read the voltage.
—
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANQOVDWVNUB225O5YEY47B3WTFS3LANCNFSM6AAAAAAT6GYROI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I have also created a more simple version called VoltOSD using the XIAO SAMD21
|
|
that looks great supper compact !! dude your a wizard, using the
balance lead is a great idea. xiao board is a little more expensive from
what I can see, would still love to get it working on the nano as I have a
bag of 10 of them left over from a old project just need to get the volts
showing will play with it tonight a little more. see if I can work it out
did try to us the serial monitor to see if I could see volt read out on
that. could it be that I have the dji unit set up for inav on wtfos hack so
using compressed transmission msp? blow is cut and past from wtfos wiki so
you can see
Compressed Transmission
As of 0.7.0, a new option, compress_osd, has been added to the air side
process.
If this is set to "true", then the entire character buffer will be sent
using LZ4 compression at the rate defined in osd_update_rate_hz, instead of
sending raw MSP messages over the air.
When enabled, this should fix INAV delta update related issues as well as
provide better link stability.
To enable:
Use the CLI button in the configurator on your VTx side after updating to
0.7.0.
package-config set msp-osd compress_osd true
package-config apply msp-osd
If the apply hangs, just reboot your VTx.
Note that INAV HD mode sync issues may still be present, use the usual
workarounds (enter menu or switch screens) to fix these.
Compressed mode may also be valuable for other FCs, as it should make the
overall link much more reliable and stable
…On Thu, 19 Jan 2023 at 17:41, Qrome ***@***.***> wrote:
I have also created a more simple version called VoltOSD using the XIAO
SAMD21
- VoltOSD
-
- XIAO SAMD21 TX to DJI Air unit RX(115200)
- Voltage sensor on A0 pin 0
- PWM Arm Signal on D1 pin 1
[image: image]
<https://user-images.githubusercontent.com/32021227/213519781-b92fa9e9-8a16-42a0-a10a-e2f6f8bd3c6b.png>
https://github.com/Qrome/VoltOSD
—
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANQOVDVICPSWN3GDCXDNPA3WTF4GBANCNFSM6AAAAAAT6GYROI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
would i need to change anthing in here pasted code below for voltage read
out to work on nano?.
and also can I just change the
analogPin = A0
to a different pin ?
in here to check if the problem is the pin i.e can I just change to A2 ? or
will it break the code somewhere else ?
//Voltage and Battery Reading
#ifdef ESP8266
const float arduinoVCC = 3.25; //Measured ESP8266 3.3 pin voltage
#else
const float arduinoVCC = 5.0; //Measured Arduino 5V pin voltage
#endif
float ValueR1 = 7500; //7.5K Resistor
float ValueR2 = 30000; //30K Resistor
const int alanogPin = A0;
float averageVoltage = 0;
int sampleVoltageCount = 0;other to see if the my a0 pin is broken ?
On Thu, 19 Jan 2023 at 17:59, peter houghton ***@***.***>
wrote:
… that looks great supper compact !! dude your a wizard, using the
balance lead is a great idea. xiao board is a little more expensive from
what I can see, would still love to get it working on the nano as I have a
bag of 10 of them left over from a old project just need to get the volts
showing will play with it tonight a little more. see if I can work it out
did try to us the serial monitor to see if I could see volt read out on
that. could it be that I have the dji unit set up for inav on wtfos hack so
using compressed transmission msp? blow is cut and past from wtfos wiki so
you can see
Compressed Transmission
As of 0.7.0, a new option, compress_osd, has been added to the air side
process.
If this is set to "true", then the entire character buffer will be sent
using LZ4 compression at the rate defined in osd_update_rate_hz, instead
of sending raw MSP messages over the air.
When enabled, this should fix INAV delta update related issues as well as
provide better link stability.
To enable:
Use the CLI button in the configurator on your VTx side after updating to
0.7.0.
package-config set msp-osd compress_osd true
package-config apply msp-osd
If the apply hangs, just reboot your VTx.
Note that INAV HD mode sync issues may still be present, use the usual
workarounds (enter menu or switch screens) to fix these.
Compressed mode may also be valuable for other FCs, as it should make the
overall link much more reliable and stable
On Thu, 19 Jan 2023 at 17:41, Qrome ***@***.***> wrote:
> I have also created a more simple version called VoltOSD using the XIAO
> SAMD21
>
> - VoltOSD
> -
> - XIAO SAMD21 TX to DJI Air unit RX(115200)
> - Voltage sensor on A0 pin 0
> - PWM Arm Signal on D1 pin 1
>
> [image: image]
> <https://user-images.githubusercontent.com/32021227/213519781-b92fa9e9-8a16-42a0-a10a-e2f6f8bd3c6b.png>
>
> https://github.com/Qrome/VoltOSD
>
> —
> Reply to this email directly, view it on GitHub
> <#2 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ANQOVDVICPSWN3GDCXDNPA3WTF4GBANCNFSM6AAAAAAT6GYROI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
you can try a different pin to read the voltage on. |
|
didnt work still trying |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi great project
I see you have Arduino nano as an option as possible hardware on the parts list but no instructions on how to set up. I wanted to use the nano as I have a few lying around Could you add how to use I asked painless 360 as you reference his set-up video but he was not sure ?
Any advice would be appreciated.
The text was updated successfully, but these errors were encountered: