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:

Views: 83389

Comment by Ragnar Myhre on September 18, 2014 at 3:37am

Where is the firmware? The zip-file in the arducam-osd download area doesn't contain any hex file.

Comment by Daniel Estes on September 20, 2014 at 11:10am

Agreed.  Where's the latest firmware?

I purchased the Minimosd from 3D Robotics the other day.  I have everything working, but I can't configure my panel settings due to the following error.  "Failed to upload new config data".  Note:  My FTDI cable is plugged in and communicating. 

Comment by Joe Sleator on November 19, 2014 at 9:14pm

My MinimOSD is working fine, but I had a question.

What is the latest firmware, and charset? I went over to the -Extra site and found that it was more recently updated. That download also seems to have three separate *.mcm files. I'm wondering which one is appropriate, along with which version of the firmware. Is it the one at the top of this thread?

A slightly smaller problem, I'm using it with a Walkera Tali H500, and it looks like the F12E radio's FPV raster screen is slightly cropped in overscan. This means that the humble character generator is happily creating characters and icons at the edge of the screen that are only semi-visible.

I wonder if I can modify my copy of the source to change the Max chargen chip's configuration to move its screen matrix around within the video field. It's fine on the left, but slightly cropped on the top, bottom, and right. By about 5 pixels each.

The workaround is to simply use the config editor to scoot all the display field inwards on the top, right and bottom, but this does waste quite a bit of space, so a sub-character adjustment would be preferable.

Looking at the svn repo max7456.h and .cpp it appears it might be possible. I guess the chip's datasheet would provide the true answer...

Comment by Joe Sleator on November 20, 2014 at 4:11am

There seems to be another issue with getting this working on "2.0".

Before, I was playing around with the "extra" firmware, having flashed MinimOSD Extra Copter 2.2.hex and "Latest Charset.mcm" on the "extra" site.

The original FW that was loaded, and the "Extra" FW mentioned above, both would display the current flight mode, and seemed to do other things quite well.

But seeing this announcement, I decided to try this one, and I simply cannot get the current flight mode to display. If I plug in my 3DR radio to the same telemetry port and connect it to Droidplanner, the current flight mode displays with no issues, same with MP on the desktop. Other items seem to display fine.

I've also tried this with the "MinimOSD_22.hex" with identical results.

Can anyone make a declaration about which version is "dead" and which version is being maintained?



Comment by mP1 on November 20, 2014 at 5:44am


You will need to be more specific about the versions you are using. Its quite confusing for me to figure out exactly what versions you are using.

When you say "But seeing this announcement", im guess you might be referring to the latest Arducam , which is *very old*. THe problem is since that time new flight mods have come along. Each flightmode has a number which appears in mavlink, the old versions dont know about new flight modes as they dont have the this number = flight mode as text and other similar problems.

Unfortunately as mavlink changes, one needs newer firmware.

Comment by Joe Sleator on November 20, 2014 at 6:58am


Thanks for the kind reply!

I tried the versions available here (2.0):

And also here (2.2):

The problem with both is that the "mode switch" screen change would not work, and the "flight mode" panel item would not display.

Neither of those worked with my version of APM which is 3.1.5 circa 14 December 2013.

The firmware that came with the minimOSD appeared to work, but I un-knowingly replaced it thinking there were better versions.

So, under MinimOSD Extra, there are quite a few downloads;

The first 3 items in the list at this URL, essentially the FW Hex 2.4, Configuration Tool r727, and Character Set 2.4 bitmaps are the ones I have just tried.

They require some custom APM parameter settings, apparently to make them work. Not sure why, since the other release doesn't seem to. Just a bit concerned that those extra settings will increase the processing load on the autopilot.

Anyway, I installed those, and they worked a treat. Mode switch is fine, and flight mode displays fine.

But can I ask, what minimOSD fw/config version would one install to match the latest version of arducopter? How does one find this out for themselves? The announcement in this thread implies that the version mentioned above is the latest and greatest, incorporating the MinimOSD-Extra changes, but that doesn't seem to be the case.

> Unfortunately as mavlink changes, one needs newer firmware.

Certainly true. So, where is this newer firmware for the latest version of Mavlink running in APM2.x?

What FW do you run, and on what version of APM? Is there, perhaps, a table somewhere of which goes with what? Or do we need to browse the source to figure out compatibility?



Comment by Joe Sleator on November 20, 2014 at 7:01am


Sorry, left out the url for the 3 MinimOSD-Extra items I have used successfully, me not being specific enough's the top 3 items with the release numbers mentioned in the post above in the 4th paragraph at the top.

Comment by Joe Sleator on November 30, 2014 at 7:52am

So, where is the "latest" minimOSD firmware for download?

Let's say someone has the latest Arduplane or Arducopter. What is the URL for the minimOSD FW which goes with that?


Comment by Nathaniel Caner on November 30, 2014 at 8:07am

Hi Joe,

Go to the bottom of the Topic Description at the top of the page here and you will see a link "MinimOSD-Extra R800", be sure to take note of the username and password (both are case sensitive).

Be aware these are bug fix releases and haven't seen much (if any) testing.


Nathaniel ~KD2DEY

Comment by Dj-garfield on November 30, 2014 at 3:46pm

Hello DIY mate :)
I had spend many many hours trying to upgrade this MinimOSD ( I love it :) ), but I have some big troubles :
1/ at the begening => allways "can't talk to bootloader"I googleise so many and many tricks to be able to flash the board with an AVR programer = 0 , I finaly flashed with an old Arduino Board , and AvrDude comand line it's worked I have the Extra 2.2 ArduCam Inside .

But =>

2/ Since I made this , I plug the OSD to my APM2.6 , and => Black Screen , I thought that the MAX chip was burned ... nop cause when I press the reset button , I see on the screen :
"EEPROM Mapping is Outdated ..."
So , I start the Conf tool to test ... again "can't talk to bootloader" , updating EEPROM start , end without errors ... but On screen there is still "EEPROM Outdated bla bla " ...

Do I come back to the 2.0 FW ? or anyone have an Idea about this issue ?
Edit :

I come back to the 2.0 FW ... Still the same :( ...
Thanx in advance for your help :) and Happy fly to all :)


You need to be a member of DIY Drones to add comments!

Join DIY Drones

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service