Good news!
The beauty of this community is on the collaboration. This new firmware proves it.
I have the pleasure of announcing that "ArduCAM OSD" and "MinimOSD-Extra" teams are now working together to make MinimOSD better and better.
I've been planning this fusion with Gábor Zóltan and Pedro Santos and we've started a nice friendship.
We spend the latest days merging and retouching everything to improve your experience with the new firmware. The Wiki was also updated for matching the new resources.
What's up?
You'll se all those awesome improvements from MinimOSD-Extra as well as improvements we made together.
The latest one is the new auto detection and updating of the EEPROM mapping .
From now on both OSD Firmware and ArduCAM OSD Config Tool will share the same internal signature.
So, both will detect the need for an EEPROM remapping preventing from loading or saving truncated data.
After a firmware upgrading the OSD Config Tool will detect an outdated mapping updating it automatically.
If you update your firmware by other way, the new firmware will alert you on screen and the Config Tool will repair automatically before you load anything from the EEPROM.
Update your MinimOSD right now. The most important: Have fun!
Important NOTES:
- After install the new "ArduCAM OSD Config Tool" remember that you need to update the Character Set. A new one is available on the install folder. From now on it will be always there as "OSD_Charset.mcm".
- Both sides of the MinimOSD need to be powered during a Character Set updating. Max7456's internal memory is really picky about voltage level during a charset update.
Download it from here:
Comments
I also saw that its important to check you have the correct PAL or NTSC setting, if this is wrong you might also get a output view that looks like the character set did not take.
Hi, Jo and Oliver! That 3.3V FTDI from 3DR store has 5V on the power line and it has 3.3V as the logic level.
So, feeding the first stage through that cable is OK because of that.
@Oliver, we tried to do our best. I really sorry that you feel that way about it. Though the MinimOSD have been a useful tool to many people it's always frustrating to know about such particular issues. All I can say is that the most recurrent issue is on updating the CharSet. It's not a software problem. The Maxim's chip 7456 is really picky at the voltage level.
Jo, no worries. I was just going by the fact that 3DR only seems to stock the 3.3V cable. Beyond that I was hoping someone with more expertise would chime in.
General warning about minimOSD: It is by far the glitchiest piece of RC electronics I've ever used. I'm not sure if it's the hardware that's inherently flawed or the software (ArduCAM and minimOSD-extras) but overall, its a mess. Eventually I just gave up.
Hi Oliver,
You were right the 3.3V FDTI works. I had a faulty minimosd. After I got a new one from a friend all works fine now...
Thanks and sorry I doubted you
I don't think the 3.3V FTDI will work... I'd like to know what Sandro says about this
I am using a TTL-232R-3V3.. I am using a 3S bat, which is wired like the diagram on the wiki when updating the character set (camera still connected, just not plugging the transmitter)... The video stage is powered the same way when I connect back on the copter, I just plug the transmitter back then.
I believe a 3.3V FTDI cable is fine. Which cable are you using? Link?
Yes, both sides need to be powered during character set update. What are you using to power the video side while updating the character set?
Also, how is the video stage powered when it is connected to your copter?
Hi Sandro,
I have the same issue, cant seem to update character set successfully... I see some points here and would like to clarify something...
I have no soldering on my osd, ... I power the osd with the 12v bat as in the diagram... But on closer inspection I see that my FTDI cable is a 3.3V cable... Could this be the issue...
In other words are you saying here... Use a 5V FDTI, and power the other side of the OSD with the 12V battery?
To add: I figured out that a 4 pin FDTI does not work... Even with the "reset" trick.. With another 6 pin (3.3V) The config tool reads the config correct, updates the firmware, and confirms that the character set was updated... But when Plugging all back on the copter the info does not display correct... Mav link blinks.. But all the parameters on the display is wrong... The clock is ticking, and warnings seems to display, like low bat (All of this fonts being fuzzy, like its missing a pixlel line on all characters)... But nothing else on the screen is working... Like horizon line is not moving, battery voltage is not displaying, throttle display does not change...This all points to the character set for me..
Do you think its the 3.3V cable that is the problem?
Weird... it should not be a problem on a tied stages board. because the second one (with battery) would feed both ones. It would grant the supplying. Just in case, double check the blob solders too.
Anyway, I'm happy to now that it's working for you. =)
Congratulations by sticking on it until get it working.
THAT WAS IT! :) I guess the cable wasnt supplying enough power. Used a different cable and now we are GOOD! Hallelujah!
-
1
-
2
-
3
-
4
-
5
of 10 Next