Latest firmare version for your OSD

A

Alex Villa

Super Moderator
Instructions to update:

-This tutorial might be useful: http://www.rcgroups.com/forums/showthread.php?t=1907371
-Make sure you have the latest pickit2 software, v2.61. Else download from Microchip.com
-On the pickit 2 install directory, replace the device list file(PK2DeviceFile.dat). Download from Microchip.com

-Use the latest firmware for the main board(big board) and the graph board if available.

-Make slight side pressure while the board is being programmed, this to prevent bad contacts and errors because of that.

-After this you have to cycle power to the OSD, so it restarts. The OSD will be locked on a debug screen, Change the screens with the IR remote control until the a unique ID is generated on the screen #3. You have to send me a private mail with this ID, and I will send you a unlock code to be entered on the call sign menu item. The OSD will be unlocked and ready to go. Call sign can be set to OFF, or changed to whatever you like.
I usually send the code within 24-48hours. If you can't wait this time, do not try a firmware update.

-If the OSD does not get any screen after firmware update, then you have to re-flash the graphic board. If the screen gets stuck on the firmware version display, then you have to re-flash the main board firmware.

Warning!
-If there is no new firmware update available for the graph board on your RVOSD version, dont flash it. Because upgrading the graphic board will make your OSD to be locked and will have to wait for an unlock code.
-Upgrading the firmware will overwrite all your settings. You will need to configure everything again after upgrade.

Version 3.05-4.05: Fixed a bug introduced on previous version. Altitude display dont display properly over 256 mts or feets.
Version 3.06: Fixed a bug on the derivative gain, causing GPS only RTH take over to destabilize the plane when derivative gain set to anything but zero.
Version 4.06: Fixed a bug on autopilot bank derivative. Increased maximum plane angle to display coordinates up to 90°. Changed altitude to show peaks under 8mts(26 feets)


This is the side to update the main board firmware:


This is the side to update the graphic board firmware:



For RVOSD G1, G2:
Main board: Main_3.06.hex Release date: 20/July/2010
Graphic board: Graph_2.20.hex
Main board with waypoint sequencer: Main_3.05S.hex (ready)*

For RVOSD G3:
Main board: Main_3.06.hex Release date: 20/July/2010
Graphic board: None Available
Main board with waypoint sequencer: Main_3.05S.hex (ready)*

For RVOSD G4:
Main board: Main_4.06.hex Release date: 25/July/2010
Graphic Board: None available
Main board with waypoint sequencer: Main_4.05S.hex (ready)*

For RVOSD G2, G3, G4 upgraded to G5:
Main board: 5.02 Release date 30/June/2011
-Fixed compatibility issue with LRS PPM string
-Fixed absolute current sensor sensibility at low currents
-Internal changes to inertial unit

Main board: Main_5.03auS Release date 15/July/2011
-Fixed a bug in AHI neutral when set to 90 or 270°.

Main board: Main_5.04uS Release date: 20/July/2011
-Fixed instability selecting RSSI levels.
-Added PWM pulse coded RSSI for EZUHF receivers.
-Internal changes to the GPS parser to make it more robust against interference or affected GPS signal levels.

Main board: Main_5.05uS Release date: 23/July/2011
-Improved inertial unit compensations

Main board: Main_5.06uS Release date: 06/October/2011
-Distance left calculation ignore throttle range when current is less than 1A.
-Improved pwm capture from servos.
-Fixed landing gear selection not saved on permanent memory.
-Increased general accuracy of distance calculations for more than 100km distances.
-Improved inertial unit capability to deal with vibrations.
-USB comms working for waypoint configuration.
-Added ruddervator (V-Tail) option, elevator + rudder inputs ---> elevator (ruddervator1) + rudder (ruddervator2) outputs
-Improved range left calculations.
-Changed static current display to 500mA.

; Data, commands accepted:
;-$RVWPT,02,18.685760,N,069.903368,W,500,20,-1000,M*3E\n\r
;Message ID: $RVWPT
;Waypoint number being updated: 02
;Latitude: 18.685760
;N/S indicator: N
;Longitude: 069.903368
;E/W indicator: W
;Altitude: 500 (always round to multiples of 25)
;Speed: 20 (always round to multiples of 5)
;Loiter radius: -1000 (always round to multiples of 25, negative values is CCW, positive is CW)
;Units: M (M is metric, I is imperial)
;Checksum: 3E (not implemented yet, just dummy)
;

Warning!
You have to install the new G5 board before patching this upgrade to the main board. This upgrade will not work with old graphic boards!
Waypoint sequencer is already installed on this upgrade. But only active for USA-Canada area.






For RVOSD G5.0:
Main board: 5.02 Release date 30/June/2011
-Fixed compatibility issue with LRS PPM string
-Fixed absolute current sensor sensibility at low currents
-Internal changes to inertial unit

Main board: Main_5.03aS Release date 15/July/2011
-Fixed a bug in AHI neutral when set to 90 or 270°.

Main board: Main_5.04S Release date: 20/July/2011
-Fixed instability selecting RSSI levels.
-Added PWM pulse coded RSSI for EZUHF receivers.
-Internal changes to the GPS parser to make it more robust against interference or affected GPS signal levels.

Main board: Main_5.05S Release date: 23/July/2011
-Improved inertial unit compensations

Main board: Main_5.06S Release date: 06/October/2011
-Same changes than Main_5.06uS

Firmware 5.07: Main and graphic board firmware !!!!!!!!!!------------------->can be found here. <--------------- !!!!!!!!!!!!!!!








For RVOSD G5.1:

Firmware 5.07: Main and graphic board firmware !!!!!!!!!!------------------->can be found here. <--------------- !!!!!!!!!!!!!!!

Pre-release firmware to use a second auxiliary channel:
There is also the option to test an experimental firmware that adds the option to set a second auxiliary channel to select the auxiliary autopilot mode without entering the menu. This firmware has to be flashed to main board only. Provided that you have the latest firmware version on the graphic board. This works for RVOSd 5.0 and 5.1.
Can be found here:
http://forum.rangevideo.com/index.php?threads/cycling-screens-now-triggers-autopilot-after-upgrading-to-rvosd-v5.1656/#post-27806

For RVOSD G6:
Flash this firmware to main board only, does not require unlock code.

Main board: M6.01_H6.00_r006.hex, Release date: 23/November/2013
-Improved filter for vibration rejection.

Main board: M6.02_H6.00_r006.hex, Release date: 16/December/2013
-Removed random ones and zeroes displaying on the F16 screen, undocumented feature for thermal assist that have yet to be debugged. Removed now.

Main board: M6.03_H6.00_r002.hex, Release date: 8/January/2014
-Fixed a bug causing wrong pan servo output pule on camera stabilization mode.

Main board: M6.03_H6.00_r004.hex, Release date: 13/February/2014
-Fixed a bug causing telemetry not to be inserted on the video signal.

Graph board: G6.01_H6.00_r002.hex, Release date: 13/February/2014

--------------------------------------------------------------------------------------
Main board: M6.06_H6.00_d001.hex, Release date: 20/October/2014
Graph board: G6.02_H6.00_d002.hex, Release date: 20/October/2014

For RVOSD G6 with Rvlink:

The latest firmware set is this:
View attachment 3066
View attachment 3065


This latest firmware does also make the RVOSD configurator software to work again, download it from here: http://www.rangevideo.com/forum/showthread.php?2266-RVGS-Telemetry-software
Install, then use the search option on your computer to look for the file: RVOSDConfig.txt
Use the one here to overwrite it.

View attachment 3067


Note: If you have your OSD with the firmware set M6.05 - G6.02, then you only need to flash the main board with M6.06, this will fix a bug causing the mAh counter to go backwards. On this case you dont need an unlock code.

-Variable throttle control.
-Flaperon-Spoileron mix built in improved.
-Thermal assist.
-Few general improvements to internal stuff.
 

Attachments

Last edited by a moderator:
A

Alex Villa

Super Moderator
I am making this post so users can have all the info about updates in one thread. I am still working on it.

Version 4.04
- Baro height will be used by the autopilot if the altitude is selected for "baro" or "both", GPS height will be used if altitude ladder is selected to GPS.
- Throttle channel no longer goes to full throttle if RC link is lost while you are using the "Fly by wire" stabilization mode.
- I added back the stabilization mode cancel if RC link is lost, so now it will be back to manual mode after RC link lost.
- Removed the virtual fence changing the autopilot mode to "Return to home" if the virtual fence is treaspased.
 
A

Alex Villa

Super Moderator
Main_3.04.hex is the new available update for RVOSD G1, 2 and 3. It has all the same fixes and updates than Main_4.04.hex for RVOSD G4. Only difference is G4 has a menu to setup altitude for baro or GPS.
 
G

Gary Evans

Well-Known Member
Alex Villa said:
I am making this post so users can have all the info about updates in one thread. I am still working on it.

Version 4.04
- Baro height will be used by the autopilot if the altitude is selected for "baro" or "both", GPS height will be used if altitude ladder is selected to GPS.
- Throttle channel no longer goes to full throttle if RC link is lost while you are using the "Fly by wire" stabilization mode.
- I added back the stabilization mode cancel if RC link is lost, so now it will be back to manual mode after RC link lost.
- Removed the virtual fence changing the autopilot mode to "Return to home" if the virtual fence is treaspased.
Click to expand...
Alex can you elaborate on these two so I'm sure I understand.

I was not aware that the throttle channel went to full throttle if the RC link was lost while in fly-by-wire mode. It seemed like it would go to cruise throttle as was intended. I don't recall this being discussed but could have missed it.

On the stablization mode if you are using fly-by-wire mode, lose and then regain the RC link will the fly-by-wire mode still be active? Originally it was turned off when the RC link was regained.

Thanks!
 
A

Alex Villa

Super Moderator
On G4 I had made the stabilization mode to resume after RC link lost take over, but someone was landing on 3rd person and switched level flight accidentally, he turned the Tx on and off trying to get control back and nothing, because the new feature. I think on other situations this could be bad. So now RC link lost gets the control back to manual.

Also I added the ability to set the virtual fence for all stabilization modes so if you hit the fence with any stabilization mode active it is changed to RTH. This caused this: http://www.youtube.com/watch?v=R74qYod5tGE&feature=channel
The user though it was RC link really lost, tried siwtching Tx on and off. But unfortunatly never tried to disable stabilization with the switch.
The RTH flew the plane untill the battery was drained and autolanded 40 feets away. He was lucky there was nothing on the landing path. But I removed this option as well.
And yes there was a bug with RTH setting full throttle if the RC link was lost in FBW mode.
I think I will eventually add this features back, but I have to add also modifications to the graphic firmware so everything gets clear, and even add menus to enable this options. With the defaults set to disabled.
 
G

Gary Evans

Well-Known Member
Making one firmware compatable with all applications can as you know get pretty complicated. Another approach maybe could be to have patches available for specific functions and let each user decide on their own configuration. Candidates could be -

1) Maintaining FBW mode after RC loss
2) A altitude or horizontal distance from home to disable the RTH function

Yes I admit it these are my favorite mod's!
 
G

Gary Evans

Well-Known Member
The bug in the RTH throttle setting was only in the Gen4 firmware? I tested my Gen3 and it goes to cruise throttle.
 
S

slides

Member
Yeah ! Understand nothing. So others corresponds about no full throttle after FBW mode - my 3.02 switches to cruise speed. Not understand about virtual fence - RTH switches on after crossing this range at 3.02 firmware ? If so i need no to upgrade to 3.04.

Alex ! Wanna recommend to reprogram idea of FS throttle to not "+" 110%, but to "-" 110%. Because I can get body damage at the ground when test my radio !!! Failsafe is better to set to turn motors off, not maximum throttle.
 
Last edited:
V

vaa

Active Member
slides said:
Alex ! Wanna recommend to reprogram idea of FS throttle to not "+" 110%, but to "-" 110%. Because I can get body damage at the ground when test my radio !!! Failsafe is better to set to turn motors off, not maximum throttle.
Click to expand...
Absolutely agree! Also in this mode, if the autopilot failed in flight, the plane did not fly off into nowhere, but just falls somewhere nearby.
 
A

Alex Villa

Super Moderator
Gary Evans said:
The bug in the RTH throttle setting was only in the Gen4 firmware? I tested my Gen3 and it goes to cruise throttle.
Click to expand...
Is possible that this bug was added on the first G4 firmware versions. Hard to know since I cant work on firmware for several hardware versions at same time. What I do is working on a master firmware. And then make the changes for different hardware versions.
 
A

Alex Villa

Super Moderator
- RTH switches on after crossing this range at 3.02 firmware ? If so i need no to upgrade to 3.04.
Click to expand...
No! Virtual fence will change the stabilization mode(Fly by wire, level flight, heading hold...etc) to RTH if you are flying with any other stabilization mode ON. If you are flying on manual mode, nothing will happen. And you always can disable the stabilization mode back to manual at any stage of flying.
 
A

Alex Villa

Super Moderator
Alex ! Wanna recommend to reprogram idea of FS throttle to not "+" 110%, but to "-" 110%. Because I can get body damage at the ground when test my radio !!! Failsafe is better to set to turn motors off, not maximum throttle.
Click to expand...
The reason for this is that if anything fails, the autopilot has more chances to get the plane back to home at full throttle than at zero throttle. Also most ESCs will reset themself to this new -110% level as minimum. So you will have to reprogram again the ESC after programming the OSD failsafe. Or else when you go to normal range (-100%), the engine will not stop.


Absolutely agree! Also in this mode, if the autopilot failed in flight, the plane did not fly off into nowhere, but just falls somewhere nearby.
Click to expand...
If you configured the RC link lost detection on the ground, then the autopilot will never fail in flight and output this value. Actually the +110% throttle level will never pass the OSD. So your engine will always see normal throttle range.
 
S

slides

Member
Hello ! All my ESC doesn't reprogram to -110% minimum ! Most of ESC goes to calibrate stick range only at maximum throttle position, when you power on your ESC.

Second, I'll remember my dangereous situation at the ground, when my radio accu shutdown and FS was programmed to turn off motor. At that time my fingers was very close to propeller. Do you think, what can happend, if my ESC was tuned to RVOSD3 autopilot ?

For safety I'll recommend you to create alternative firmware for low-point FS. Thanks.
 
M

mspencer1

Well-Known Member
Waypoint Sequencer

I already have the previous WPS software for my gen 3 board. Do you just email me the link again to get the update?
 
You must log in or register to reply here.
Top