car2carl / rush-osd-development Goto Github PK

Speed is always calculated with a fix 50msec 
the time between consecutive calls of calculateTrip() doesn't have to be 50msec 
it is >= to 50 msec 

if((currentMillis - previous_millis_high) >= hi_speed_cycle)  // 20 Hz 
(Executed every 50ms)

so add parameter to calculateTrip(deltatime) and give it (currentMillis - 
previous_millis_high) the speed calculations become more stable. 

DB,

1. With older versions of multiwii, barometer altidude is not calibrating every 
power up. So OSD dont show 0 meters on the ground. OSD should automaticaly 
calibrate altitude every power up or manualy in the OSD software.

What steps will reproduce the problem?
1. Enter the Menu through Stick Command
2. Go to Item Position Screen
3. Turn off Display RSSI
4. Save and Exit

What is the expected output? What do you see instead?
Rssi indicator doesn't disappear, it should.

What version of the product are you using? On what operating system?
KV_Team_2.2_20131221 

Please provide any additional information below.
I'm using hobbyking minim osd, when I do the same procedure with other 
indicators they do disappear, Rssi is the only one that doesn't 

I've already tried running the erase eeprom script and loading the osd firmware 
again... it didn't make any difference.

Great Osd though. I've been using it for a while but this new release has that 
bug... no big deal but I don't use Rssi so it'd be nice to hide it.

What steps will reproduce the problem?
1.Just turn on my minimosd and voltage goes 0.0
2.it's 
http://www.rctimer.com/index.php?gOo=goods_details.dwt&goodsid=862&productname= 
 //rctimer mavlink

3.i've soldered the right pin rotated 45 º

What is the expected output? What do you see instead?
12.6 // 0.0

What version of the product are you using? On what operating system?
lastest //windows.
multiwii 2.2 crius aio pro 
with vbat on.

Please provide any additional information below.

What steps will reproduce the problem?
1. Using a FTDI Upload EEPROM clear to OSD
2. upload KV_Team_OSD.ino to OSD. 
2. Open KV_Team_OSD_GUI and upload fonts
3. Make any change to settings and write to OSD
4. Restart OSD... changes have not been saved

What is the exact brand and model of hardware you´r using?
The FTDI has a FT232R chipset
The MinimOSD is from Witespy

What is the expected output? What do you see instead?
Changes to settings... changes not saved

What official OSD version are you using?
2.3

Have it been modified in any way?
no

Please provide any additional information below.
I have tried powering the OSD three ways... 1) thru USB cable 2) 5v from the 
Naze32 3) 5v from a regulator

I fixed two issues I encountered while using rush-osd with baseflight, a 32bit 
port of MultiWii. One of them is related to the USE_BOXNAMES option, which is 
still a compile-time option in the current HG revision. The other is related to 
the range of RSSI sent via MSP. 

Both fixes are very small, it would be nice if you could review & apply them to 
the main tree:

MSP RSSI fix: 
https://github.com/the-kenny/rush-osd/commit/44fd9716603a53057e2dc18fd25a5b9fc99
1062e
MSP sends rssi as a value between 0 and 1023. rush-osd's rssi calibration 
assumes it max. value is 255 (or 254, don't remember). This fixes the 
calibration issue.


USE_BOXNAMES fix: 
https://github.com/the-kenny/rush-osd/commit/7fa51bbad6d6a27e97654f420e874d995fb
a1731

What steps will reproduce the problem?
1. go to screen 8, the one for changing locations of onscreen objects
2. Go to the NUM_SATS(first item in the list)
3. Scroll left one item
4. Lots of garbles text

What is the exact brand and model of hardware you´r using?
witespy kv team osd

What is the expected output? What do you see instead?
the menu should scroll all the way through

What official OSD version are you using?
2.3

Have it been modified in any way?
no

Please provide any additional information below.
It can be worked around by not hitting the end of the list(dont go left at the 
beginning of the or hit the end)

When my RSSI changes rapidly, then it takes about 5 seconds for the displayed 
RSSI to adjust to the new value. That's way too slow to be practical for when 
flying in hilly areas and accidently going out of LOS.

The problem is in calculateRssi().

In order to test the smoothing, I created a Perl test script that calls 
calculateRssi() at a simulated 10Hz and displays the actual as well as smoothed 
RSSI data. See attachments.

I can't seem to make sense of how the smoothing works in this line so I'm not 
sure if it's correct:
rssi_Int += ( ( (signed int)((aa*rssiSample) - rssi_Int )) / rssiSample );  // 
Smoothing the readings 

can´t start gui software. click at prog, nothing happens..
anyone..? 
latest java, arduino finds the minim osd board on com3.
any other way to upload the fonts? 

/JJ

in the usage of this function for longitude in screen.ino the 3rd parameter has 
changed between r345 and r370 from '4' to '3'

i believe it should be '4', why was it changed ?

what does the 3rd parameter do ?

as setting it to '4' as in r345 prevents 'crashes' experienced in r370

my coords are -31.052934,152.808094

What steps will reproduce the problem?
Rush OSD is flushed properly, working pretty well on simulator. When connected 
to MultiWii Pro flight controller - there is no output and yellow LED flashes 
only once upon startup and then goes off (while it should rapidly flashing 
indicating communication). I noticed that when I connect flight controller also 
to computer through USB, minim osd also starts working fine and works even 
after disconnecting FC from computer...

looks like some communication initialisation problem. tried to reduce baud rate 
(in config and in OpenSerial function call according to issue #21 
https://code.google.com/p/rush-osd-development/issues/detail?id=21)

What is the exact brand and model of hardware you´r using?
Multiwii flight controller: 
http://www.rcgroups.com/forums/showthread.php?t=1770898

I connect minim osd to serial 0 (telemetry) located next to radio ports.

I have noticed one small maybe a bug. As i am using only the sensors from 
multiwii i disabled the hardware ADC. I enabled the RSSI, Main voltage and 
Current read from multiwii. On the OSD the current was shown 0.0A but the 
consumption of mAh was shown properly. As i turn the ADC again on the current 
readout started to work. Maybe it is a small bug.

What steps will reproduce the problem?
1. I needed to Flash my OSD with your Arduino-Code as stated in the Manual. I 
can do everything as described in the Wiki, I see everything when using the 
Simulator.

2. When I connect to my APM 2.5.2 Board with Ardupilot 2.74b, I get only the 
nearly empty inital Screen without any IMU / ardupilot data.

3. This was not initially the case with the Witespy-Version of your Software. 
This has been working.

What is the exact brand and model of hardware you´r using?
Witespy

What official version of the product are you using?
latest; 

Have it been modified in any way?
No

Please provide any additional information below.

i would like to submit one, and maybe even write a guide to making one.

others could submit one too 

What steps will reproduce the problem?
1. download latest version 2.2
2. review code 
3. review GUI
4. confirm that both are missing important features from both source code and 
GUI, such as amperage scaling factor and simulator in gui.

What is the exact brand and model of hardware you´r using?

"rtf quad"-style minimosd with additiinal input pins for ADC sensors...
What is the expected output? What do you see instead?
features available in previous versions that are now listed as deprecated.

What official OSD version are you using?
2.2 latest downloadable zip

Have it been modified in any way?
no. its just missing important features for no apparent     reason.

Please provide any additional information below.
this is my first attempt at using your firmware, so I downloaded the 
recommended 2.2 version only to find that the GUI features and configurable 
parameters in the code do not match those that are listed in the wiki 
documentation. many features are missing...

What steps will reproduce the problem?
1. Enabled Compass/Heading Bar with 2.3
2. Enabled Armed/Disarmed Status
3. Arm/Disarm a few times and it appears from then on
4. This has been solved in a later branch based on KV team.

What is the exact brand and model of hardware you´r using?
Naze32 Funfly Rev 5 (Full version)

What is the expected output? What do you see instead?
The compass/heading tape without the armed text superimposed over it.

What official OSD version are you using?
2.3

Have it been modified in any way?


Please provide any additional information below.

What steps will reproduce the problem?
1. Update Jave
2. Start OSD GUI


What is the exact brand and model of hardware you´r using?
MinimOSD

What is the expected output? What do you see instead?

---------------------------
Java Virtual Machine Launcher
---------------------------
Error: Registry key 'Software\JavaSoft\Java Runtime Environment'\CurrentVersion'
has value '1.8', but '1.7' is required.
---------------------------
OK   
---------------------------


What official OSD version are you using?
KVOSD 2.2

What steps will reproduce the problem?
1. frsky D4R-II in ppm sum mode
2. minimosd pin 12 connected to PWM RSSI output


What is the expected output? What do you see instead?
Signal from 0 do 100% but I can see only max 5%. In menu raw rssi data shows 
random values between 0 and 25 rapidly changing while Tx and Rx are in the same 
position.

What version of the product are you using? On what operating system?
v2.2

Please provide any additional information below.
I think pulseIn function is not good for this. 

sorry for my english :)

KV Team Gui can't find virtual bluetooth ports (SPP). 
In forming the list of ports the program is not responding. 
But MultiWii Conf utility works well. 

SOLUTION: 
use rxtxSerial.dll and lib/serial.jar from MultiWii 2.3 Conf project. It works 
fine.
MultiWii Conf can be download here: 
https://code.google.com/p/multiwii/downloads/detail?name=MultiWii_2_3.zip&can=2&
q=
Have it been modified in any way?

My PC: HP 4520s, Windows 7 pro 32 bit 
Bluetooth-slave: HC-06

What steps will reproduce the problem?
1. I setup current meter to multiwii via A2 pin
2. Multiwii detects current consuption and works fine MWC config.
3. Is is possible that minim osd gets reading from multiwii instead of 
soldering additional to minim osd?

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1.Compile v2.3
2. Get Error:
Arduino: 1.5.7 (Windows 7), Board: "Arduino Pro or Pro Mini, ATmega328 (5V, 16 
MHz)"

In file included from KV_Team_OSD.ino:28:0:
GlobalVariables.h:681: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[] =
                                ^

  This report would have more information with
  "Show verbose output during compilation"
  enabled in File > Preferences.

3.
4.

What is the exact brand and model of hardware you´r using?


What is the expected output? What do you see instead?


What official version of the product are you using?
2.3

Have it been modified in any way?
No

Please provide any additional information below.

1.try starting the gui in linux.

Im useing an MinimOSD v2.3 i think, and a FTDI 232R bridge.


By posting this id like to find out what to do to start the GUI-file in Linux 
Ubuntu.

Using the MinimOSD hardware from HK with a fatshark video system white streaks 
appear on every line in which text is displayed.

It is caused by the white level being to bright for the fatshark system to 
handle.

The same issue is documented here:
https://code.google.com/p/minimosd-extra/issues/detail?id=40

Solution:
Change Max7456.cpp line 115 from
    MAX7456_Send(MAX7456ADD_RB0+x, WHITE_level_120);
to
    MAX7456_Send(MAX7456ADD_RB0+x, WHITE_level_90);

maybe you guys could expose this option in the config.h file to make it easier 
for users to fix it.

What steps will reproduce the problem?
1. Clck on gui exe file.
2.
3.Getting a no file association error and a shell execute error!
4.

What is the exact brand and model of hardware you´r using?


What is the expected output? What do you see instead?


What official OSD version are you using? Tried 2.3 and the latest version


Have it been modified in any way?


Please provide any additional information below.

What steps will reproduce the problem?
1.Attach TTL Adapter
2.Load Arduino 1.6.1
3.Load any ino - file
4. try uploading it

What is the exact brand and model of hardware you´r using?
Hardware Features:
- ATMEGA328P Microcontroller
- MAX7456-EUI monochrome on-screen display
- 5V/500mA DC/DC regulator for MAX7456-EUI
- Operating voltage: 5V(FTDI connector) and 12V(Video I/O connector)
- Supported NTSC & PAL
- FTDI connector

USB to RS232 TTL Upgrade PL2303HX Auto Converter Module


What is the expected output? What do you see instead?
syntax error at C:\Program Files 
(x86)\Arduino/hardware/tools/avr/etc/avrdude.conf:348

What official OSD version are you using?
none

Have it been modified in any way?
no

Please provide any additional information below.

What steps will reproduce the problem?
1. Changing "#define SPEED 115200" in config.h to 38400 for example
2. Compile and upload to OSD board
3. MultiWii Serial port is running at 38400 as well
4. Connect OSD board to MultiWii Board

What is the exact brand and model of hardware you´r using?
MinimOSD 1.1

What is the expected output? What do you see instead?
Expected communication and items on screen,
I see there is no communication

What official OSD version are you using?
2.3

Have it been modified in any way?


Please provide any additional information below.
When searching the code, i found the following line: "SerialOpen(0,115200);" in 
KV_Team_OSD.cpp,
suggesting that the SPEED definition is not in use.

What steps will reproduce the problem?
1.Cleared EEPROM
2.Installed KV Team OSD software/firmware using arduino board setting aurduino 
duemilanova w/atmega328 and selected com port, my case 10
3.Run KV Team GUI 2.2, browse font, selected MW_OSD_Team.mcm uploaded. able to 
edit/view fonts.
4.Reset OSD controls, Selected settings for OSD, write to OSD and Saved 
settings.
5.Hooked MinimOSD KVT (cut trace and checked with multimeter) to MultiWii Pro 
ez3 board ser "0" port also tried ser 1 and ser 3 ports. Both blue leds on and 
green led flashing. Camera FH18C 520tvl wide voltage mini camera (NTSC) Working 
voltage: 3.6-24V and TS832 Transmitter/RC832 receiver which is plugged into 
4.3inch monitor set to nTSC 16:9.
6.Monitor displays splash screen and display but with funky looking characters? 
see attached pictures.
7.What is wrong with Characters displayed. Is it a bad MinimOSD KVT
What is the expected output? splash screen and display to look like the  video 
teaser you have on youtube.

What do you see instead? see attached

What version of the product are you using? On what operating system?
KV Team 2.2 and MultiWii Pro ez3/Quad firmware from witespy

Please provide any additional information below.
Currently MinimOSD kvt trace cut and checked, pads are soldered. Powering MW 
board will power minimOSD KVT but will not diplay any video. but when I use 
cam/tx battery to power video cam/tx, minimOSD KVT and MW board work and video 
is displayed? I don't like the idea of powering all four components via cam/tx 
battery. 
I've also desoldered pads on MinimOSD KVT and used separate power for MW 
Board/MinimOSD KVT and powered cam/tx and MinimOSD KVT side. Board lights up 
blue and green leds but no video output/display? 
Please Help!
Joe Barnes

What steps will reproduce the problem?

1. EEPROM Clear - solid orange on communication light
2. Successful upload and configuration of MultiWii OSD
3. EEPROM Clear - solid orange on communication light
4. 'PWMrssiPin'was not declared in this scope (see bottom for error output). 
Exception, programming stops.
Note: have tried different processes, such as disconnecting, reconnecting, 
hitting reset, etc.

What is the exact brand and model of hardware you´r using?
Esscoe Ardupilot Flight Controller Board On-Screen Display APM OSD MinimOSD. 
Confirmed 5v, etc.

What is the expected output? What do you see instead?
Programming does not complete. Errors out. As noted above, I can successfully 
upload the MultiWii OSD so I'm pretty sure the board and comms are functional. 
Error output below.

What official OSD version are you using?
KV_Team_OSD_2.2_20131221  (downloaded 2-28-15)

Have it been modified in any way?
No. Stock, out of the box.

Please provide any additional information below.

Arduino: 1.0.6 (Windows NT (unknown)), Board: "Arduino Pro or Pro Mini (5V, 16 
MHz) w/ ATmega328"
C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avr-g++ -c -g -Os -Wall 
-fno-exceptions -ffunction-sections -fdata-sections -mmcu=atmega328p 
-DF_CPU=16000000L -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=106 -IC:\Program 
Files (x86)\Arduino\hardware\arduino\cores\arduino -IC:\Program Files 
(x86)\Arduino\hardware\arduino\variants\standard -IC:\Program Files 
(x86)\Arduino\libraries\EEPROM 
C:\Users\Data\AppData\Local\Temp\build6826590242901540799.tmp\EEPROM.cpp -o 
C:\Users\Data\AppData\Local\Temp\build6826590242901540799.tmp\EEPROM.cpp.o 

C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avr-g++ -c -g -Os -Wall 
-fno-exceptions -ffunction-sections -fdata-sections -mmcu=atmega328p 
-DF_CPU=16000000L -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=106 -IC:\Program 
Files (x86)\Arduino\hardware\arduino\cores\arduino -IC:\Program Files 
(x86)\Arduino\hardware\arduino\variants\standard -IC:\Program Files 
(x86)\Arduino\libraries\EEPROM 
C:\Users\Data\AppData\Local\Temp\build6826590242901540799.tmp\KV_Team_OSD.cpp 
-o 
C:\Users\Data\AppData\Local\Temp\build6826590242901540799.tmp\KV_Team_OSD.cpp.o 

KV_Team_OSD.cpp:103: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:139: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:140: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:141: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:142: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:143: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:144: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:147: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:148: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:149: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:150: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:151: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:152: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:153: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:154: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:158: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:159: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:160: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:161: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:162: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:163: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:164: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:165: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:167: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:168: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:169: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:170: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:171: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:172: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:173: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:174: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:176: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:177: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:179: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:181: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:182: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:183: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:184: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:185: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:187: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:188: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:189: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:190: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:191: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:192: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:193: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:194: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:196: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:197: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:198: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:199: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:201: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:202: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:203: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:204: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:205: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:206: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:207: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:209: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:210: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:211: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:213: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:214: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:215: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:216: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:217: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:218: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:219: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:220: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:231: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:232: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:233: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:234: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:235: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:237: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:238: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:239: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:240: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:242: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:243: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:244: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:245: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:246: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:247: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:248: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:249: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:250: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:251: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:252: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:253: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:254: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:255: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:256: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:257: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:258: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:259: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:261: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:304: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:306: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp:308: warning: only initialized variables can be placed into 
program memory area
KV_Team_OSD.cpp: In function 'void setup()':
KV_Team_OSD.cpp:355: error: 'PWMrssiPin' was not declared in this scope
KV_Team_OSD.cpp: In function 'void loop()':
KV_Team_OSD.cpp:444: error: 'voltagePin' was not declared in this scope
KV_Team_OSD.cpp:453: error: 'vidvoltagePin' was not declared in this scope
KV_Team_OSD.cpp:460: error: 'rssiPin' was not declared in this scope
KV_Team_OSD.cpp:464: error: 'amperagePin' was not declared in this scope
KV_Team_OSD.cpp:479: error: 'PWMrssiPin' was not declared in this scope
KV_Team_OSD.cpp: At global scope:
KV_Team_OSD.cpp:127: warning: 'temperature' defined but not used

What steps will reproduce the problem?
1. Tested and verified with r1240
2. Uploaded r1360 to MWC board
3. MinimOSD with RushOSD r345 fully updated
4. Connect MinimOSD with TX>RX and vice versa

What is the expected output? What do you see instead?
1. Signal (video and OSD) displayed
2. No MWC version displayed on 'boot-screen'
3. No connection with MWC

What version of the product are you using? On what operating system?
Please see above :)

Please provide any additional information below.
Thanks to Team KV's great work I've resurrected my Rushduino for a simple quad 
running MWC2.1. But my latest FPV unit with MinimOSD cannot get connection with 
MWC pre2.2. Will try 2.2 final soon.

What steps will reproduce the problem?

The OSD is showing fuzzy text when configured in PAL mode, in NTSC mode it 
isn't showing any text. The camera feed shows up just fine.
when I disconnect the camera the fuzzy text in PAL mode becomes clear and the 
text in NTSC mode is visible.
When I connect my mobius everything works fine

What is the exact brand and model of hardware you´r using?
MavLinkOSD 2.0 with 650TVL (starlight) camera


What is the expected output? What do you see instead?


What official OSD version are you using?
KV OSD 2.3


Have it been modified in any way?
5 volt mod


Please provide any additional information below.

What steps will reproduce the problem?
1.Connect Video monitor to MinimOSD
2.Connect power to Video Pin
3.Look at screen and see that second reading on the bottom, says 15.0 A, 
guessing it should say V instead.
4. On GUI need to adjust Amperage to get value down, really just have to plug 
it in and look at how the numbers come up and getting them adjusted.

What is the exact brand and model of hardware you´r using?
MinimOSD from Witespy

What is the expected output? What do you see instead?
See Above, also I changed the A to a V so the second reading says voltage, I 
swapped the pins around in the code, but really didn't fix the GUI issue.

What official OSD version are you using?

2.2

Have it been modified in any way?

No, Video Voltage is not correct on the downloaded one.

Please provide any additional information below.

What steps will reproduce the problem?
1. know formula for amperage calculation
2. look at existing code for amperage calculation
3. see there is something missing

What is the expected output? What do you see instead?

expect to see amperage value, but instead get raw analogRead integer formatted 
as amperage


What version of the product are you using? On what operating system?
2.2


Please provide any additional information below.

basically you forgot them[/b], prove me wrong but i just went over your new 
code and [b]there is nowhere to specify your amperage sensors[i] "sensitivity" 
[/i]as you call it, ie 40mv/A[/b]

this is your [b]only[/b] code for calculating amperage from the arduino's 
analog pin: it is not enough

[code]    if (!Settings[S_MWAMPERAGE]) {
    amperage = analogRead(amperagePin)- Settings[S_AMPOFFSET] /2;
    if (amperage >=999) amperage=999;
    }[/code]

There are some extra variables in Settings enum in GUI and 1 setting is 
misplaced:

 S_MWRSSI misplaced in GUI

S_GPSCOORDTOP missing in OSD settings;
S_GPSALTITUDE missing in OSD settings;
S_ANGLETOHOME missing in OSD settings;
S_MODEICON missing in OSD settings;

[deleted issue]

hello I'm using Crius SE 2.5 with MultiWii 2.1 because it works fine on my 
Tricopter with gps Ublox CN-06, install a miniOSD V0.1 with KV_Team_dev_r370 
but not walk ARMED and DISARMED, not the Km / h. Rush_KV_2.1 wanted install but 
when I compile fails Metro MetroTimer = (100); 
Any tips? 
Thank you!