Olddude wrote:my current sensing is kinda working Its almost accurate now I set it to 58 and offset high 8
and this seems to kinda work for the sensor i use. .......
Hi olddude, I'm glad it works now, but I don't understand why you must set Offset High to 8, are you sure ? may be Offset Low=8 ? This for me is very strange. Can you confirm me your setup ? I Want verify it. Bye Carlo
scrat wrote:V2.3 - when in settings screen where you can hide things from OSD...OSD just freezes and all text is scattered over the screen. Have to reboot osd.
Yes, I know about the page 8 crash issue, try this: 1) In file config.h at line n. 8 "#define MAXSCREENITEMS 27" change with value 26 2) In file KV_Team_OSD.cpp delete the Whole line n. 227 "#define MAXSCREENITEMS 26 // 28 w/ GPS alt & Temperature" as this line is duplicated. Recompile and reload it in minimosd. I hope that kataventos has a time to put on line the debugged version as you can see here: http://code.google.com/p/rush-osd-development/source/list
Hi ALL, I have an Upgraded MAVLinkOSD V2.0 board. Please let me know the possible configuration parameters compulsory in order to make it work with the 2.3 version.
scrat wrote:V2.3 - when in settings screen where you can hide things from OSD...OSD just freezes and all text is scattered over the screen. Have to reboot osd.
Yes, I know about the page 8 crash issue, try this: 1) In file config.h at line n. 8 "#define MAXSCREENITEMS 27" change with value 26 2) In file KV_Team_OSD.cpp delete the Whole line n. 227 "#define MAXSCREENITEMS 26 // 28 w/ GPS alt & Temperature" as this line is duplicated. Recompile and reload it in minimosd. I hope that kataventos has a time to put on line the debugged version as you can see here: http://code.google.com/p/rush-osd-development/source/list
Cheers Carlo
Thanks Carlo. It's working. But unfortunately, there is still known bug left...but now it is written KV_OSD before it was DISARMED.
scrat wrote:V2.3 - when in settings screen where you can hide things from OSD...OSD just freezes and all text is scattered over the screen. Have to reboot osd.
Yes, I know about the page 8 crash issue, try this: 1) In file config.h at line n. 8 "#define MAXSCREENITEMS 27" change with value 26 2) In file KV_Team_OSD.cpp delete the Whole line n. 227 "#define MAXSCREENITEMS 26 // 28 w/ GPS alt & Temperature" as this line is duplicated. Recompile and reload it in minimosd. I hope that kataventos has a time to put on line the debugged version as you can see here: http://code.google.com/p/rush-osd-development/source/list
Cheers Carlo
Thanks Carlo. It's working. But unfortunately, there is still known bug left...but now it is written KV_OSD before it was DISARMED.
Hi scrat, Please explain better this issue, I never seen that, I will take a look. Note: If you can it's better that you attach here the Whole zipped version you are using. Bye Carlo
Hi all. Could You help me please. Mavlink OSD (2.3 firmware) and Crius SE 2.5 (2.3 firmware) does not work. Mavlink blinks, but where no data from crius. I tried to change tx-rx wires, but with no results. Is that broken circuit?
Romeo84 wrote:Hi all. Could You help me please. Mavlink OSD (2.3 firmware) and Crius SE 2.5 (2.3 firmware) does not work. Mavlink blinks, but where no data from crius. I tried to change tx-rx wires, but with no results. Is that broken circuit?
Hi Romeo, Mavlink (firmware) has nothing to do with MWii and KV team OSD firmware. You must upload KV team osd firmware in your OSD device Cheers
cofl1001 wrote:I have it connected, worked before on MPNG but since I switched to MWII 2.3 all I got is awaiting heartbeats message... So I guess I must enable or define it, but not really sure how ... Any help is appreciated. Thanks
Florin, MPNG & ArduCopter use the MAVLink protocol. MultiWii uses the MSP (Multiwii Serial Protocol).
The KV_OSD firmware expects to see MSP and not MavLink, so you must update the firmware on your OSD board. As it is now, you do not have KV_OSD at all... just a MinimOSD board ready for arducopter.
Been searching for a few days and cannot get the voltage in for monitoring to work. Have flashed different firmwares and have a working osd, except i get no voltage reading. I have the battery plugged in to bat1 and have also tried bat2. Is there something im simply missing?
I'm having a problem flashing my board with KV OSD 2.3. I can clear the EEPROM, but when I try to upload the 2.3 sketch, I get this error:
/var/folders/9b/13s0m9ts7nj1q6r0sf9msx300000gn/T/build5501178423522795094.tmp/KV_Team_OSD.cpp:261:32: error: variable 'item_table' must be const in order to be put into read-only section by means of '__attribute__((progmem))' PROGMEM const char *item_table[] = ^ Error compiling.
Does anyone have a solution for this? I'm running OS X and Arduino 1.6.0.
Ok got a real odd problem now....... I have ver 2.3 and when I power up my fpv equipment I can see the main start up screen and then get into the menu but when I enable an item for the osd to display it will not show up on the screen anywhere??? Any ideas please???? Many thanks Rct
EDIT: Solved it, I just reflashed it with the latest files again and all is well. Rct
Hi, I try several thinks and several hardware (minimosd,microsd,arduino uno, arduino nano) When I'm on the GUI everything I try to write in eeprom is erased when I click on READ
It's like if write button on gui not working... I had to modify source code to force enable my option I need...
There is something I need to do to make GUI working ? (I tried of corse to erase eeprom before download firmware)
Hi, I try several thinks and several hardware (minimosd,microsd,arduino uno, arduino nano) When I'm on the GUI everything I try to write in eeprom is erased when I click on READ
It's like if write button on gui not working... I had to modify source code to force enable my option I need...
There is something I need to do to make GUI working ? (I tried of corse to erase eeprom before download firmware)
Thanks
Olivier
I had the same issue with kvosd. The current version of MWOSD has worked for me. http://www.mwosd.com