KV Team Multiwii OSD

urkadurka · Post by **urkadurka** » Wed Feb 13, 2013 9:50 pm

Hi, I bougth a clone of minim osd from RCTIMER (http://www.rctimer.com/index.php?gOo=go ... oductname=) but after chars and software download (I followed http://code.google.com/p/rush-osd-devel ... Map_Upload) the screeen isn't like expected :shock:

, there are a lot of strange chars

.

So, please could help to understand or investigate ?

Bye

kataventos · Post by **kataventos** » Wed Feb 13, 2013 10:39 pm

urkadurka wrote:Hi, I bougth a clone of minim osd from RCTIMER (http://www.rctimer.com/index.php?gOo=go ... oductname=) but after chars and software download (I followed http://code.google.com/p/rush-osd-devel ... Map_Upload) the screeen isn't like expected , there are a lot of strange chars .

So, please could help to understand or investigate ?

Bye

Hi,

I think that your problem have been mentioned here before. The clone you use is a little different, so, please take some good pictures of both sides of it and post them here.

Probably you are not getting the new char map on max as it should, because you are not connecting both sides of the board, neither the mod that you suppose to do!

Cheers,
KV

urkadurka · Post by **urkadurka** » Thu Feb 14, 2013 8:41 am

Hi,

Thanks for the answer
I inserted these two images, both are from rctimer on line store.
So if you need more detail I can do more detailed photos

Bye
http://www.gte-elicotteri.com

rotary65 · Post by **rotary65** » Thu Feb 14, 2013 12:16 pm

KV needs pics of your exact board to verify if soldering has been done to bridge the video (which is powered via a regulator from 12vdc) and processing (powered at 5vdc via the ftdi connector) sides or not. If the halves are not bridged, you need to provide 12vdc via the video connector in order to power the Max OSD chip while you are running the font loader (while connected to the PC via ftdi).

Version 1 of the clone board has an undersized voltage regulator and will overheat, so the bridge must be done which will run the whole board off the 5vdc from the ftdi port. V2 has a beefier regulator and should be fine without the bridge being done (ie. running the video side off the 12v input and the processor side off the 5v input).

I have 3 of the same RC Timer v2 OSDs and they came unbridged.

Another possibility is that you uploaded the font loader using arduino, but didn't upload the font file using the terminal software. There are two steps to the font update.

kataventos · Post by **kataventos** » Thu Feb 14, 2013 6:17 pm

Hi,

Urkadurka please read Rotary65 email carefully and proceed accordingly.

But there is something annoying there, I do not see any jumpers on the RCTimer version of Minim! But it does look to have better regulator and noise filter.

Please confirm.

Cheers,
KV

PS: Nice flying Group you have there on your site!

EDIT: That board can only be used with both sides connected, I followed the link you posted above.
In this case you need to connect both sides inclusive to upload the char map, hope this help you!

urkadurka · Post by **urkadurka** » Thu Feb 14, 2013 7:37 pm

Ohhh Yes now it does work !!

With the power supply on both side 12V and 5V the char upload was successfull.

I can confirm that there aren't any jumper as suggested, I think that are present on like the original one

Many thanks to all for the suggestion !!!

So I'm checking about power supply unit about noise and warming.

Urkadurka

kataventos · Post by **kataventos** » Sat Feb 16, 2013 10:15 am

Hi all

we know that you all are anxious and we decided to release a KVTeam dev this weekend :mrgreen:

The responsible for the serial protocol/communication (on this case between the OSD and GUI) is no longer on this team because of bad attitude issues.
And the last one was to resign just before this release :?:

On propose ? Maybe not... :geek:

OK...

This bug not always happen and involves the use of the serial port between GUI and OSD. We are sending a great deal of information over the port. If the port is closed before a msp message is completed, an unhandled error is thrown. This is due to the nature of how the MultiWii sends and receives msp commands, even when we send 32 bits of information, it is broken down into 8 bit segments for sending. Processing uses a java library called RXTX, there are know issues with this library. The larger the data stream the more chance of an error.

The OSD code is ready to rock, but at this time it depends 95% on GUI. You will be able to read and write to the EEPROM your preferences but the simulator is disabled.
We have made some progress this evening but there still is a chance that the error will occur, if it does, the user will need to shut down the app and restart.
And thats about all we can think of

Anyway, we will crush this bug very soon, and the OSD part is running 100%, you will enjoy for sure.

Thank you all for your help and support, go on and have fun flying with it!

Cheers,
KV

dramida · Post by **dramida** » Sat Feb 16, 2013 2:18 pm

Great news!
I just checked google repository from here http://code.google.com/p/rush-osd-devel ... loads/list and i could't find any downloads. Is it anywere else?

kataventos · Post by **kataventos** » Sat Feb 16, 2013 3:03 pm

dramida wrote:Great news!
I just checked google repository from here http://code.google.com/p/rush-osd-devel ... loads/list and i could't find any downloads. Is it anywere else?

Hi Dragu,

It will be in an hour or two

I said this weekend :geek:

kataventos · Post by **kataventos** » Sat Feb 16, 2013 3:57 pm

Hi all,

If you would like to give us the pleasure to try our work :arrow:

http://www.kvteamosd.com

Have fun!

1- upload the new Char map like before (do not use the one on GUI for now);
2- upload the Team dev (look at config.h, still are a few options left);
3- open GUI and your port, make a RESET;
4- configure it according your needs and save;
5- close port, done.

The Wiki already have crucial information about the GUI, to make possible for you to understand what to do once you´r there!

EXAMPLE - This is my setup/options on the GUI

realpastaman · Post by **realpastaman** » Sat Feb 16, 2013 6:17 pm

Thanks for you hard work on this kataventos, I'm going to try in the morning weather permitting.

Does this do imperial or just metric?

kataventos · Post by **kataventos** » Sat Feb 16, 2013 8:39 pm

realpastaman wrote:Thanks for you hard work on this kataventos, I'm going to try in the morning weather permitting.

Does this do imperial or just metric?

Hi,

Do not thank only me this is a Team project.

The brains behind the GUI is RossPower67, he is still working with me on this even today after the release, we are both tracking down a persistent issue. The true professional coder, Itai has worked hard on this release too but is no longer with us, it seems that he can do everything by itself and better then the rest of the world :roll:

we are just going to sit back and wait for his work... this way we can relax and "enjoy the flight"! Just kidding.

This team is essentially made of people who love this hobby, there are no professional coders on it (at this moment), we are just professionally persistent :mrgreen:

Another non-professional guy who translated my bad english so that everyone understands the steps to get this stuff in the air is Liam the Wiki editor.
And we have the true bug buster Carlonb and some more that did not work as much, but they are mentioned on the code main page!

We are very grateful that everyone here is trying our work on their Minim OSD boards!
Thanks for your support, we really enjoy uploading our work for everyone so you can do what we can do with this stuff!

Cheers,
KV

PS: Imperial bug fixed

cswiger · Post by **cswiger** » Sat Feb 16, 2013 10:38 pm

What happened to video system in config.h ? Looks like it's hardwired for PAL now

/******************************************* Video System ***********************************/

//#define VideoSignalType_PAL
//const char videoSignalType=1;

#define VideoSignalType_NTSC
const char videoSignalType=0;

kataventos · Post by **kataventos** » Sun Feb 17, 2013 1:52 am

cswiger wrote:What happened to video system in config.h ? Looks like it's hardwired for PAL now

Hi,
now you select your preferences on the GUI.

Please read previous posts or go to the wiki on: http://www.kvteamosd.com

Cheers,
KV

Woppit · Post by **Woppit** » Sun Feb 17, 2013 12:01 pm

Hi all, just like to say thanks to all the team (sorry to here about the drop outs!) for the time and effort put into this project.
Looking good and running smooth! can't wait to give it a go (still building the ground station!) but with this up front I'm sure it's going to be fun.
Thanks again

Shane

realpastaman · Post by **realpastaman** » Mon Feb 18, 2013 7:25 pm

Trying out R280 (multiwii r1316) I have the following problems

1. There seems to be no Browse window to update the fonts through the Gui (windows 7 64 bit but using 32bit Gui)

2. This is the font that shows up when I select edit from the Gui

3. There seem to be some strange characters on the display

Does seem to be showing imperial units correctly now.

4. Apart from non seeing a Browse button on the Gui, it seems to run really slow / laggy

5. With the previous version I used to set for example
#define STABLEMODE 1 // OK
#define BAROMODE 4 // OK
#define MAGMODE 8 // OK
//#define BOXCAMSTAB 16 // not used
#define ARMEDMODE 16 // OK
#define GPSHOMEMODE 32 // OK
#define GPSHOLDMODE 128 // OK
//#define BOXCAMTRIG 256 // not used

I cant see how to do this on R280?

Thanks to the team working on this - hope you can understand my questions

kataventos · Post by **kataventos** » Mon Feb 18, 2013 11:08 pm

@Realpastaman,

thank you for your reporting your experience, we appreciate that very much.
The font uploading is not working on the released dev r280, that is why you see strange stuff on screen. You can see that is not on the download file description.
When you download any file you do have a board under the link, please read carefully ... I will anyway put the none functional parts in bold!! it may help the next downloaders...

Simulator is too disabled on that dev, that´s why you can not see it mentioned.
We are at this precise moment taking care of all those "problems"

You need to upload the font map like before, all other steps are OK since you were able to get it running! :mrgreen:

About mode bits! you do not need to do anything... get it ? (see description again) :ugeek:

About the very slow GUI, it is fixed at this moment, we will upload it ASAP!

Thank you once more for your support.

Cheers,
KV

PS: Don´t forget to report 8-)

NikTheGreek · Post by **NikTheGreek** » Tue Feb 19, 2013 10:41 am

I guess that this one will do the job
http://www.hobbyking.com/hobbyking/store/__36844__Minim_OSD_v1_1.html

Right ?

thebgrian · Post by **thebgrian** » Tue Feb 19, 2013 9:37 pm

NikTheGreek wrote:I guess that this one will do the job
http://www.hobbyking.com/hobbyking/store/__36844__Minim_OSD_v1_1.html

Right ?

That one should do the job, and even better - it looks like it's the updated version with switching power supply for the analog side, and still have the pads to connect both sides(if you don't want to use the 12V and separate power (the RC timer version doesn't have those pads)).
There is a buddy code for 2% discount

http://rcsearch.info/hobbyking/i36844/#catalog

realpastaman · Post by **realpastaman** » Wed Feb 20, 2013 1:27 am

kataventos wrote:@Realpastaman,

thank you for your reporting your experience, we appreciate that very much.
The font uploading is not working on the released dev r280, that is why you see strange stuff on screen. You can see that is not on the download file description.
When you download any file you do have a board under the link, please read carefully ... I will anyway put the none functional parts in bold!! it may help the next downloaders...

Simulator is too disabled on that dev, that´s why you can not see it mentioned.
We are at this precise moment taking care of all those "problems"

You need to upload the font map like before, all other steps are OK since you were able to get it running!
About mode bits! you do not need to do anything... get it ? (see description again)

About the very slow GUI, it is fixed at this moment, we will upload it ASAP!

Thank you once more for your support.

Cheers,
KV

PS: Don´t forget to report

Hi Kataventos In the end when I saw no browse button was working I did use Tera Term to upload the new font (the picture I uploaded before of the font map shows 16 position arrows) is that correct? If it is correct then I'm
still getting those strange characters on the screen Maybe I'll wait until the GUi allows for font updating!

kataventos · Post by **kataventos** » Wed Feb 20, 2013 3:10 am

@Realpastaman

Hi,
the new char map was not successfully uploaded, that one you have on the pic is the old char map.
Please try again all the steps carefully with the new char map, like I said you should be fine.

Today I made a video tutorial for the new firmware

and it is uploading as I am writing you... so, you all need be patient,
new and stable release will be ready for download ASAP!

Cheers,
KV

kataventos · Post by **kataventos** » Wed Feb 20, 2013 3:32 pm

Hi all,

this may help http://www.youtube.com/watch?v=egStpPl9 ... e=youtu.be thanks for watching!

Cheers,
KV

copterrichie · Post by **copterrichie** » Wed Feb 20, 2013 5:20 pm

Please, may I make a special request;

define CALLSIGN XXXXXX (If the Pilot has a Ham License)

If this is defined, the OSD will display the Callsign every 10 minutes or so to be legal in some areas.

realpastaman · Post by **realpastaman** » Wed Feb 20, 2013 6:46 pm

kataventos wrote:Hi all,

this may help http://www.youtube.com/watch?v=egStpPl9 ... e=youtu.be thanks for watching!

Cheers,
KV

Thanks for all your work on this video - Its really easy to understand now thanks!! - Now shall i go out tonight or wait in to see if V2.2 is ready

Seriously big thanks to the team !!

ABL · Post by **ABL** » Thu Feb 21, 2013 8:54 pm

I have old minim (marked 0.1), probably from GLB (still with linear reg). Soldered both bridges (on top and bottom), flashed arduino bootloader (with usbasp), flashed minimOSD FW, connected with arducam control software - it updated charmap, i could change settings, looks OK.
Then flashed (via FTDI) Max7456_Font_Update, uploaded font (at least, it said "successfully"), then flashed 280 rev. from downloads. Looks OK with flashing, no errors.
I installed 32-bit Java, ran KV_Team_OSD_GUI, selected port, it become green. But i could not make any changes - if i press write, nothing happens, TX LED on FTDI blinks once, RX does not blink. If i restart program and try to read anything - all values are defaults (i think, they aren't written, as there's no communication with minimosd).
Just took latest hg repo (f54c46fef29a), ran via processing, it says:

Code: Select all

WARNING:  RXTX Version mismatch
   Jar version = RXTX-2.2pre1
   native lib Version = RXTX-2.2pr

(it's described in readme) - so i guess, RXTX version is OK (running everything on 32-bit). Still nothing - can't write, but now "reset" button hangs application completely (earlier it timeouted after some time). If i turn simulation on - TX LED on FTDI blinks all time, RX still OFF.
I attached cam and easycap, when board is turned on - i get video (without any OSD elements). Connecting RX/TX to NAZE32 board (sorry, no other arduino boards available atm) doesn't make any difference.

My guess - board is working, but i management via serial port isn't working at all... I tried to connect via COM port with putty - no answer (only TX blinks if i type something, and no symbols even when i press 'reset').

Would say that serial port on board died - but i just downloaded arducam tool including FW - it successfully flashed FW, updated charmap, then i did some changes, wrote to minimosd, turned off software, turned on and read - everything is here, all changes successfully read. So, my guess there's something with GUI.

Should i expect something in OSD serial output (i mean, capture anything with putty or other serial monitor)?

Lapino · Post by **Lapino** » Fri Feb 22, 2013 3:36 pm

Same for me...i use the minimosd 0.1 from glb and could upload anything but couldn't change the displayed values per gui.
I've another question: as i use the attopilot current and voltage sensor, can i connect the voltage sensing part directly to the belonging pin or do i have put a resistor inbetween?

Lapino · Post by **Lapino** » Fri Feb 22, 2013 8:52 pm

Anyone? Please help

kataventos · Post by **kataventos** » Fri Feb 22, 2013 11:38 pm

Hi all,

please wait for KV Team 2.2 release on the repo (I or someone of this Team will post here when it´s ready) and follow this instructions exactly:
http://www.youtube.com/watch?v=c7y5VCInojA

I have flashed today 3 new Minin OSD´s with no problem at all.

Cheers,
KV

alexia · Post by **alexia** » Sat Feb 23, 2013 12:09 am

kataventos wrote:Hi all,

please wait for KV Team 2.2 release on the repo (I or someone of this Team will post here when it´s ready) and follow this instructions exactly:
http://www.youtube.com/watch?v=c7y5VCInojA

I have flashed today 3 new Minin OSD´s with no problem at all.

Cheers,
KV

does it minimosd from rctimer

Woppit · Post by **Woppit** » Sat Feb 23, 2013 1:49 am

Hi all, I'm using these http://www.goodluckbuy.com/on-screen-display-osd-board-minimosd-apm-telemetry-to-apm-1-and-apm-2.html
with no prob's at all!

thanks
Shane

Lapino · Post by **Lapino** » Sat Feb 23, 2013 4:03 am

That's the one I'm using too. But when I am using the GUI to change some things being displayed or not and hit write nothing happens...e.g. If I hit read everything is default again. How did you configure your minimosd? Maybe I uncommented or did something wrong though I did just follow the wiki...

one more thing I'm concerned about: as I have the attopilot current and voltage sensor, can i just solder the voltage sensing directly to the pin if the processor it do I have to use a resistor in between?

Thanks in advance

vpb · Post by **vpb** » Sat Feb 23, 2013 4:07 am

Hi,

I see this small Crius V/I Sensor (16$) http://www.goodluckbuy.com/crius-v-i-se ... pilot.html, can it be integrated with multiwii and use with this OSD sw? Hardware sensors will be more accuracy than sw.

ABL · Post by **ABL** » Sat Feb 23, 2013 8:59 am

kataventos wrote:please wait for KV Team 2.2 release on the repo (I or someone of this Team will post here when it´s ready) and follow this instructions exactly:
http://www.youtube.com/watch?v=c7y5VCInojA

Well, just telling that "it works for me" does not means that it will work for everyone...
As i told before, i already tested latest hg snapshot, this includes latest rxtx library and performance mods. Does not make difference at all.
It seems there's something with hardware - APM FW handles that, while this one does not (and because you do not know about this - just waiting for "more features" 2.2 won't fix that).
I checked with LA, board does not output anything on TX wire when i send "read" or "write" - only "RX" is active:

But it does work OK with APM FW.... Hm.

EDIT: just noticed that there are 2 more changes on google code... Sync'ed latest changes, uploaded, added charmap, and ... Connected!
"Reset" button still hangs, but at least now it could read and save changes. And display something on screen. Also, flashing charmap (also updated) works. So far - looks good, need to test if it will take data from NAZE32 and... Will go into air! =)

Woppit · Post by **Woppit** » Sat Feb 23, 2013 11:22 am

Lapino wrote:That's the one I'm using too. But when I am using the GUI to change some things being displayed or not and hit write nothing happens...e.g. If I hit read everything is default again. How did you configure your minimosd? Maybe I uncommented or did something wrong though I did just follow the wiki...

one more thing I'm concerned about: as I have the attopilot current and voltage sensor, can i just solder the voltage sensing directly to the pin if the processor it do I have to use a resistor in between?

Thanks in advance

Hi, to get it to work with the GUI I had to unplug FTDI from usb and plug in and re-connect until I got the red and green dots to flash showing connection.
I had to do it a couple of times but when it connected and they flash, I was able to write to the board.

If you are NOT using sensor board then you WILL need divider resistors, but the sensor board should output the correct voltage for the processor board.
Hope this helps.

Lapino · Post by **Lapino** » Sat Feb 23, 2013 2:47 pm

Hi,

I solved the problem! I had to clear the EEPROM first, then everything worked like discribed in the wiki...maybe that should be added there

Thank you Woppit for the sensor input, I'll try that and make a report if it works

I'm really glad the other stuff like AH etc works^^

Lapino · Post by **Lapino** » Sat Feb 23, 2013 5:29 pm

so...at least nothing puffed but the only values changing are Alt, heading and the horizontal line, though the amperage is kind of oscillating around 4.9Amps...with or without motors running...
so what isn't displayed correctly are the modes I'm in, armed-stat and the tuneable parameters like A/mAh/V/Rssi....strange enough the A display oscillates with 0.1 around 4.9A...though I installed the current sensor with a resistor as displayed in the wiki.
Any recommendations?

alexia · Post by **alexia** » Sat Feb 23, 2013 6:28 pm

Lapino wrote:Hi,

I solved the problem! I had to clear the EEPROM first, then everything worked like discribed in the wiki...maybe that should be added there

Thank you Woppit for the sensor input, I'll try that and make a report if it works
I'm really glad the other stuff like AH etc works^^

how do you clear eeprom?

Lapino · Post by **Lapino** » Sat Feb 23, 2013 6:32 pm

its in the arduino IDE under File->Examples->EEPROM->eeprom_clear

alexia · Post by **alexia** » Sat Feb 23, 2013 8:09 pm

thanks it s very nice

Lapino · Post by **Lapino** » Sat Feb 23, 2013 10:21 pm

I got a problem with the armed-status and the modes being displayed incorrect (always disarmed and in afro-mode) ...anyone got a solution to this? I use KV_Team_osd latest download version

Lapino · Post by **Lapino** » Sat Feb 23, 2013 10:32 pm

I got it working...I activated the Box option but don't get the GPS mode displayed...anyone?^^

kataventos · Post by **kataventos** » Sun Feb 24, 2013 4:38 am

Lapino wrote:I got it working...I activated the Box option but don't get the GPS mode displayed...anyone?^^

Hi Lapino,

thanks for trying this beta dev and for report the issues.
Don´t know if I understood your problem but, now GPS related info will only be displayed with a fix until then you will only see sats number.

KV

Lapino · Post by **Lapino** » Sun Feb 24, 2013 9:08 am

Yeah that's Ok for me and makes sense but my problem was that the gps mode wasn't displayed (like changing to stable mode).

Another question is if I have to use a resistor in between my current sensor and the arduino pin?

And how do I use the rssi for frsky?

I made the resistor mod and changed the analogreference to default (5v) to have a correct voltage reading (in combination with a correction factor as I don't know why the reading differs from the sparkfun example sketch for attopilot 90A sensor that gives perfect readings for voltage (amps seem too low, that's why I'm asking if the resistor mod for current sensor it's needed ).

Lapino · Post by **Lapino** » Sun Feb 24, 2013 12:23 pm

I removed the resistor to the current sensor and the values seem to be good, I don't use RSSI anymore as I can't figure it out but my TX warns me anyway

So only the GPS-mode acknowledgement is missing to make me happy

Woppit · Post by **Woppit** » Sun Feb 24, 2013 1:46 pm

Hi, I get the little arrow marker for GPS RTH but not for GPS position hold, all other arrows acc, bar, mag are ok

kataventos · Post by **kataventos** » Sun Feb 24, 2013 3:57 pm

Hi,

please check on previous pages, they have the information for FRSky RSSI.

Question: The ones who are having problems with GPS mode, are you using I2C GPS ?

KV

Edit: And what MW version?

kataventos · Post by **kataventos** » Sun Feb 24, 2013 4:04 pm

Lapino wrote:Yeah that's Ok for me and makes sense but my problem was that the gps mode wasn't displayed (like changing to stable mode).

Another question is if I have to use a resistor in between my current sensor and the arduino pin?

And how do I use the rssi for frsky?

I made the resistor mod and changed the analogreference to default (5v) to have a correct voltage reading (in combination with a correction factor as I don't know why the reading differs from the sparkfun example sketch for attopilot 90A sensor that gives perfect readings for voltage (amps seem too low, that's why I'm asking if the resistor mod for current sensor it's needed ).

Probably not needed, but I can not test because I use software for that. keep in mind that you can only make analogue readings from 0 to 5v, if this is the case go on and try.

Sometime ago I made this defines on config.h, use them according your needs to find the right match to your setup.

Code: Select all

#define AMPDIVISION 3600            // Hardware current sensor division ratio
#define AMPERAGE_CAL 1.1            // Amperage calibration
#define AMPRERAGE_OFFSET 512        // Amperage = AMPRERAGE_OFFSET - analogRead * AMPERAGE_CAL / 10.23

Pay attention to the formula for collecting and sum amperage: Amperage = AMPRERAGE_OFFSET - analogRead * AMPERAGE_CAL / 10.23

Probably we will use them on GUI in future.

Thanks again for reporting this stuff.

KV

Woppit · Post by **Woppit** » Mon Feb 25, 2013 12:35 am

kataventos wrote:Hi,

Question: The ones who are having problems with GPS mode, are you using I2C GPS ?

KV

Edit: And what MW version?

Hi, Crius AIO Pro, MW 2.2 pre.
GPS all works, it's just the little arrow for pos hold that does not show on mine, RTH shows fine.

kataventos · Post by **kataventos** » Mon Feb 25, 2013 1:24 am

Woppit wrote:
Hi, Crius AIO Pro, MW 2.2 pre.
GPS all works, it's just the little arrow for pos hold that does not show on mine, RTH shows fine.

And is it actually engaged? that sounds very strange to me...
Verify on your MW GUI please, you have the same board then the ones I use so, no doubt that it should be OK.

Lapino · Post by **Lapino** » Mon Feb 25, 2013 10:42 am

Hi,

as you mentioned in your last reply if GPS was engaged I realized GPS couldn't be engaged though I flipped the switch BECAUSE I was in the basement thus no GPS signal could be received so it isn't a bug but it may be mentioned that a GPS-Fix is needed to have GPS-mode displayed

(if it's not already in the wiki of multiwii or so^^)

I also made some modifications so everybody else who uses the attopilot sensor could just define it and solder the sensor readings directly(!) without any resistors or whatnot to the atmega pins.

So here it is:

make this define in config.h:

Code: Select all

#define ATTOPILOT_VI

whereby old values have to be:

Code: Select all

#define EST_PMSum 1
#define HARDSENSOR                // Uncomment to change from MW_POWERMETER to Hard current sensor on analogue Pin (MW_POWERMETER is DEFAULT and must be defined on MWCode)
#define AMPDIVISION 36         // Hardware current sensor division ratio
#define AMPERAGE_CAL 1.0           // Amperage calibration
#define AMPRERAGE_OFFSET 0//512

In KV_TEAM_OSD.ino:

in setup() instead of:

Code: Select all

analogReference(INTERNAL);

place this:

Code: Select all

#ifdef ATTOPILOT_VI
    analogReference(DEFAULT);
    #define VREF 5
#else 
    analogReference(INTERNAL);
    #define VREF 1.1
#endif

In loop() (I added VREF and the specific calculations for voltage and amperage for attopilot current and voltage sensor):

Code: Select all

if (Settings[S_ENABLEADC]){
    temperature=(analogRead(temperaturePin)*VREF)/10.23;
    if (!Settings[S_MAINVOLTAGE_VBAT]){
      static uint8_t ind = 0;
      static uint16_t voltageRawArray[8];
      voltageRawArray[(ind++)%8] = analogRead(voltagePin);                  
      uint16_t voltageRaw = 0;
      for (uint8_t i=0;i<8;i++)
        voltageRaw += voltageRawArray[i];
       
      #ifdef ATTOPILOT_VI  
        voltage = analogRead(voltagePin)/1.141; 
      #else
        voltage = float(voltageRaw) * Settings[S_DIVIDERRATIO] * (VREF/102.3/4/8);
      #endif  
    }
    if (!Settings[S_VIDVOLTAGE_VBAT]) {      
      vidvoltage = float(analogRead(vidvoltagePin)) * Settings[S_VIDDIVIDERRATIO] * (VREF/102.3/4);
    }
    if (!Settings[S_MWRSSI]) {
      rssiADC = (analogRead(rssiPin)*VREF)/1023;
    }
    #ifdef ATTOPILOT_VI  
        amperage = analogRead(amperagePin)/0.649;
    #else
        amperage = (AMPRERAGE_OFFSET - (analogRead(amperagePin)*AMPERAGE_CAL))/10.23;
    #endif  
  }

thats it!
Have fun