Latest firmare version for your OSD

F

ferrocium

Member
Ok guys, I need some help. I bought an RVOSD v6 a couple years ago when they first came out. I used it for almost a year without issues with everything setup, then I had a random bug of some kind that reset my RVOSD and all I could see was the lock screen. I messaged Alex and he sent me an unlock code but recommended that I reflash the board because he thought I probably needed a fresh install. I didn't reflash it because I have no clue how. The reason I bought an RVOSD is because it is basically plug and play with no programming skill required. So here now a year later and I had the same random glitch that put my RVOSD into the lock screen. I messaged Alex and he sent me an unlock code. I used the unlock code but it didn't work, it just locked back up with a new lock screen ID. So I'm at the point where I need to try to figure out how to reflash the OSD board and Alex doesn't even seem to want to start helping to show me how to do it. :( I have already purchased a Pickit3 programmer (another $60 later :mad:) and I have some connector pins to plug into the OSD board. I have already read the link here in detail: http://www.rangevideo.com/forum/showthread.php?814-Latest-firmare-version-for-your-OSD
But I still have no clue how to program the board. Sorry, I really have no experience with this stuff. I downloaded the pickit program from www.microchip.com/mplabx. I can open the microchip program but what do I do from there?
Am I supposed to start a new project with the "prebuilt hex loadable image" option and select the hex file for the main board that I downloaded?
Then the program asks to select "family" and "device" what do I select?
Then below that it wants me to pick a "hardware tool", I found the pickit3 in the list with the correct serial number so the computer recognizes that its there, but it wont let me highlight it. What do I do here?
Then once I get the hex file open and working what do I do from there? Connect to the main board on the OSD? Will it automatically do something?

Sorry, like I said, I really have no clue what I'm doing.
A step by step list of instructions on how to reflash the board with a pickit3 programmer would be GREATLY appreciated.
Thanks in advance to anyone who helps out.
 
A

Alex Villa

Super Moderator
...and Alex doesn't even seem to want to start helping to show me how to do it.
Click to expand...
You are really fast to jump in to conclusions. Wrote a PM yesterday and come now writing this?
This is the part of attending a forum that really piss me off. You have to deal with all kind of people.
 
Last edited:
F

ferrocium

Member
Alex, I purchased the RVOSD because it was advertized as a plug and play OSD. If I wanted to tinker for hours with programming and learning new programs I would have bought a different OSD for 3 times less the price. The RVOSD6 that I purchased worked out of the box and I had everything up and running fine for several flights but soon had a random glitch that locked it up for no reason. I figured I could message you and get the problem fixed for free since it wasn't working as advertized. Your only solution was for me to reflash the board. This is exactly the kind of thing that I wanted to avoid and the reason why I bought the much more expensive RVOSD. The only instructions I got from you was a link you gave me 10 days ago on reflashing the OSD. The only instructions on the link are "download the latest hex file and upload it into the RVOSD with the Pickit programmer". Well, thats incredibly vague to say the least. I'm not a programmer and have no experience flashing or reprogramming. Doing something that seems so simple to you that would have taken 2 minutes for you to explain to me was like learning a different language for me. So $60 and over 10 hours (and 2 wasted days off) of tinkering later and having to disassemble my entire fpv aircraft to get the board back out, I've finally figured out how to reprogram the board that should have worked fine in the first place. It will take me more time yet to get everything reassembled and all parameters reprogrammed, and thats IF I was in fact able to reflash it correctly(fingers crossed but won't know until I get an unlock code back). There should at least be an option to send it in to you or someone who can reflash it for free.
SO, I think I have a little more right to be pissed off than you do right now! And all I said was that you didn't seem interested in helping, that was after 10 days of waiting for detailed instructions from you and one day after I PM'd you again I still had no response. I was just reaching out to other people to see if I could get some detailed help. And still you took the time today to make a mean remark instead of using that time to help. I think I was being pretty nice and patient, more so than you don't you think?
I wouldn't be bothering you if the board was working as it is supposed to, and you are apparently the only tech support for this board. And I also wouldn't be bothering you if you didn't put a lock feature in the board! What is that all about anyway? Why did you make it so these boards lock so easily and so we have to bother you and contact you every time we need it to be unlocked? If you don't like to be bothered why not just make the board so that it goes back to the regular flight screen if there was an issue?

Anyway, that being said, I'm not mad at you, I'm just frustrated that the process to fix the issue was not much quicker, free, and easier. When the RVOSD6 works it is an awesome product and I give you props for that Alex. But please understand how frustrating it can be for people when it doesn't work. Later I will post detailed (dummy proof) instructions on how to reflash the card for future users struggling with it like I did, hopefully it can help somebody out in the future.
 
E

evox

Member
Hi Ferrocium
i understand its probably a bit frustratrating at first but trust me flashing the OSD is very very easy even for the novice computer user.
watch the below video 4 or 5 times, then flash your OSD while watching the youtube video step buy step pausing as you go.

https://www.youtube.com/watch?v=x9MukFJvw7I

where do you live? maybe someone close buy could flash it for you or help over Skype. worst case take the OSD and picket to a computer repair shop email them the video link / forum page and they will be able to do it for you in 5 minutes.

I know it sounds overwhelming at first but having the ability to update the software on the RVOSD is a good thing and as you know when it works its an amazing OSD




ferrocium said:
Ok guys, I need some help. I bought an RVOSD v6 a couple years ago when they first came out. I used it for almost a year without issues with everything setup, then I had a random bug of some kind that reset my RVOSD and all I could see was the lock screen. I messaged Alex and he sent me an unlock code but recommended that I reflash the board because he thought I probably needed a fresh install. I didn't reflash it because I have no clue how. The reason I bought an RVOSD is because it is basically plug and play with no programming skill required. So here now a year later and I had the same random glitch that put my RVOSD into the lock screen. I messaged Alex and he sent me an unlock code. I used the unlock code but it didn't work, it just locked back up with a new lock screen ID. So I'm at the point where I need to try to figure out how to reflash the OSD board and Alex doesn't even seem to want to start helping to show me how to do it. :( I have already purchased a Pickit3 programmer (another $60 later :mad:) and I have some connector pins to plug into the OSD board. I have already read the link here in detail: http://www.rangevideo.com/forum/showthread.php?814-Latest-firmare-version-for-your-OSD
But I still have no clue how to program the board. Sorry, I really have no experience with this stuff. I downloaded the pickit program from www.microchip.com/mplabx. I can open the microchip program but what do I do from there?
Am I supposed to start a new project with the "prebuilt hex loadable image" option and select the hex file for the main board that I downloaded?
Then the program asks to select "family" and "device" what do I select?
Then below that it wants me to pick a "hardware tool", I found the pickit3 in the list with the correct serial number so the computer recognizes that its there, but it wont let me highlight it. What do I do here?
Then once I get the hex file open and working what do I do from there? Connect to the main board on the OSD? Will it automatically do something?

Sorry, like I said, I really have no clue what I'm doing.
A step by step list of instructions on how to reflash the board with a pickit3 programmer would be GREATLY appreciated.
Thanks in advance to anyone who helps out.
Click to expand...
 
Last edited:
I

Izord

Member
Hi Alex,

I bought an RVOSD 5.1 a few years ago, but just started playing with it. Is it still possible to get an unlock code from you if I flash the latest firmware for it?
 
B

BloomingtonFPV

Active Member
Combined PPM issues

I'm swapping out my Ruby for a RVOSD. I've done several RVOSD builds, but this is the first that I've used Combined PPM input from the TSUHF. My problem is that I can't get the auxiliary channel to behave properly (or at least how I think it should work).

I've made a short video here:

[video=youtube;LBg1kwuibW4]https://www.youtube.com/watch?v=LBg1kwuibW4[/video]

The demo at around the 2:00 mark most clearly illustrates the issues I've been having.

The one thing I forgot to mention is that in the Combined PPM screen in the RVOSD, I never see the Aux channel go below 1.5 uS. It will go up to about 2 when in the away position. When moved to the front position it will stay at about 1.5uS in the RVOSD combined PPM assignment screen.

I have no idea what I'm doing wrong, but it is probably something stupid :p

Any ideas from the RVOSD intelligencia? I realize that in practice the aux switch is supposed to be in the middle position, and just toggled up or down to either change the screen or the flight control mode. But if it is in the middle position the servos don't work correctly.

I thought it might be a PPM frame overrun problem, but it only works when the Aux channel is LONGER, and gets weird when it gets shorter, so that isn't it.
 
Last edited:
Pegru

Pegru

Well-Known Member
Using sum PPM from TS rx, no problems here. My tx is no Multiplex but MC20. No three-position-switch for AUX but a momentary-two-position-switch.
System is watching the changes in pulse width not the actual pulse length
To be shure that PPM stream coming from rx I connected sum pin to my oscilloscope

ppm.jpg
.

Toggling AUX switch gives corresponding changes in diagram ... wonder if you already verified?
As you cant find proper Aux switch reaction on RVOSD Combined PPM Screen, input stream maight be interrupted.
Again: Toggle switch must be a momentary switch. RVOSD is triggered when level changes.

Is RVOSD showing up with failsave - RTH in your case?

Can remember,that some time ago Alex stated: PPM stream either works or doesn't. Nothing in between.
 
Last edited:
B

BloomingtonFPV

Active Member
I agree that the overall pulse length isn't an issue (it is just 9 channels anyway).

I'm now thinking that I don't understand how the auxiliary switch works when the combined PPM stream is selected and the Aux2 channel is defined. Does it function as a toggle switch, or is it:

high- normal control
middle- activates whichever autopilot mode is selected by aux2
low- nothing

If this is correct, then how do I toggle through different OSD screens?
 
Pegru

Pegru

Well-Known Member
from manual -

Auxiliary channel:
The auxiliary channel can be used to change the OSD screens, and activate/deactivate autopilot modes. On a change from less to more than 1.85mS it cycles screens. On a change from more to less than 1.35mS it toggle autopilot mode.
It needs a three position switch assigned to this channel. Each time you toggle center-up you will cycle one screen and each time you toggle center-down it will turn ON and OFF some of the OSD options. This action will depend on some of the menu settings.

So if you dont touch toggle switch it always returns to center position which generates 1.5ms
Permanent pulse width more then 1.85ms/less then 1.35ms might cause your issue.
So toggle switch should set to center position by itself. Try to center the switch very fast by hand.
Hardware change to a spring centered switch is perfect.

This is my solution: http://www.rangevideo.com/forum/showthread.php?3490-Implantation-AUX2-rotary-switch&p=33354#post33354
 
Last edited:
B

BloomingtonFPV

Active Member
Pegru said:
from manual -

Auxiliary channel:
On a change from more to less than 1.35mS it toggle autopilot mode.
Click to expand...
I think this is what is weird- I never see values less than 1.52mS in the PPM configuration screen on the aux channel, despite the fact that the servo will go to positions less than 1.5mS. It is as if the RVOSD is preventing the aux channel from having low values of the aux channel.
 
Dionysos

Dionysos

Well-Known Member
Hi Bloom,
I'm not sure why you need 2AUX channel, there are applications but I'd try it with Aux1 for now.

So your CPPM from the TSLRS goes to the Elevator/combined PPM1 input.

The most convenient way is now to use a 3 pos switch. "switch center" does nothing, "switch up" triggers your AP mode (Heading hold, FBW, position hold, usually I have FBW there), "switch down" should switch screens and make you access the AP menu.

Try to verify the functions of the switch. Then adjust endpoints in your radio.

Seems to me not RVOSD related but rather a setup issue.

Dio
 
B

BloomingtonFPV

Active Member
Good thought on checking endpoints. I'll try that. I'm pretty sure that the weirdness I'm seeing is the plane in some kind of autopilot mode. Do you see anything on the OSD when it is on the ground to indicate that it is in an autopilot mode?

I think I'll take out the Aux2 for now. My hope was to use it to launch the Plankton LOS and then put it in loiter mode while I get my FPV gear on. Using Aux2 would mean that I could switch to FBW mode after launch to stablize the plane for good video.
 
Dionysos

Dionysos

Well-Known Member
you can switch AP modes with only AUX1, you just gotta go into the menu, select your desired AP mode and good. Ultimately the choice is yours.

Before you can do/see anything you need to wait 30secs for startup. Then, if you're in FBW, you should see that flicker on your screen (for maybe 5 secs) plus when you move the plane, the control surfaces should be controlled by the OSD. in RTH you can see "Return to home" written...

Try another switch as well to be sure.
 
B

BloomingtonFPV

Active Member
Ok, I think I solved my problems. First, I needed to be in negative shift in the TX. Not sure why; I thought both the TSUHF and the RVOSD didn't care, but negative worked.
Second, I think that the autopilot trigger mode with the throttle below normal range wasn't set up properly. This was forcing me into autopilot mode or something weird. Anyway, things are working. Thanks to everyone for helping out.
 
B

BloomingtonFPV

Active Member
Ok, now I feel like an idiot. It turns out that my Multiplex radio will put out a variable PPM stream depending on which channels are defined. I changed the number of channels, but I didn't rebind the receiver. Thus it was receiving an 8 channel stream but interpreting it as a 5 channel stream. This was likely the cause of most of my problems, and all I had to do was to rebind the RX to the TSUHF TX and all is well. I can even define Aux2 so that a slider on the radio allows me to switch between different flight modes. Waypoints here I come!
 
O

ommadawn

Well-Known Member
Just a tip on using Aux2. I have mine set up on a rotary pot, and limited the end points so that I don't have the first and last items, RTH and WP. (RTH has a dedicated switch, I dont use WP)
Regardless, I found that if you are in one A/P flight mode, and then select another, sometimes the mode won't change until you toggle the Aux1 switch off and on.
 
A

Alex Villa

Super Moderator
1- No, you just flash the latest firmware.

2- IF that pickit 2 is compatible with the original one, it should work.
 
You must log in or register to reply here.
Top