(26-Apr-2017, 05:56 PM)Oscar Wrote: Cool
IMO MinimOSD is an outdated technology check out Betaflight F3 if you are next looking for FC, the built-in OSD works so much nicer!

Well good thing I didn't knew about that ... god damn xD Well I am stuck for now with the MinimOSD and I need to fix it This is how it looks on the Screen



Here is a list of what I have done until now:

- Immediatly flashed MWOSD onto the chip without using EEPROM Clear before that
- MWOSD worked perfectly fine and the letters were crystal clear but the special signs like battery etc. were Arrows (partially cut off graphics of arrows).
- I uploaded the default Font again and reached exactly a text quality like shown in the Picture
- I desoldered everything and used EEPROM Clear and reflashed MWOSD and configured everythign again and I still have the quality like in the picture. I loaded every default font (bold,large,normal) but it was still the same unreadable garbage -.-

I hope someone can help me. The only thing I understand I could do is just to repeat the EEPROM Clear and reflash process over and over again until it works.


If i would've known that would happen i would've just stuck to the wrong I cons display with the correct Data in a readable font

Have you tried flashing the hex file with the chrome gui?

(27-Apr-2017, 10:17 PM)oyvinla Wrote: Have you tried flashing the hex file with the chrome gui?

You mean via the MWOSD Configurator? Tried it while the OSD is inserted into my quad but it seems that the UART Port is too busy with Data from the FC, even when I deactivated the Port in Betaflight. So Firmware Flashing via Serialpassthrough is out of the Question, even when I reset the Controller while I am flashing.

I will have to desolder it again. Also on the other Hand, it should make 0 difference to use the Arduino IDE, avrdude directly or MWOSD configurator. The Hex file is exactly the same and flashed in the exact same way. I will still try it though, sometimes logic doesn't help with hardware level programming xD

(27-Apr-2017, 09:10 PM)Apicalis Wrote: I hope someone can help me. The only thing I understand I could do is just to repeat the EEPROM Clear and reflash process over and over again until it works.

It does look as if the font is somehow corrupted. When you initially power on the quad, the OSD shows a welcome screen. How does that look?

The font is held in the video overlay chip's EEPROM and the MAX7456 has extremely fussy requirements when it comes to supply voltage. The spec sheet for the device says that it wants 5.0V with the minimum and maximum voltages being 4.75V and 5.25V. If the supply voltage is outside these limits, writing the font data to the internal EEPROM is normally the first thing to stop working.

So grab your multimeter and make sure that the voltage being supplied to the OSD is within limits.

This thing with running the clear EEPROM sketch is a bit of a red herring to be honest. All the sketch does is clear the EEPROM on the Atmega processor.

As the font is actually written to the video overlay chip by the OSD program running on the Atmega, clearing the Atmega's EEPROM cannot have any useful effect on problems writing to storage on a separate device.

I DID IT!!! God damn man!

I unsoldered the MinimOSD from my Quad and directly flashed it again. Of course the Arduino IDEs EEPROM Clear didn't change anything. Flashing the HEX via MWOSD Configurator was the wrong choice aswell...

BUT as I looked into it's Firmware Flasher I saw Utilities. I used the EEPROM Clear from there, which ran WAAAY longer, like 10 times the duration. After that I used Default Font installer 1.7.1  and BAM I got a screen with all the new Icons and all appeared correctly. So I scrolled Up and flashed under "Default MINIM" the Firmware "Betaflight 1.7.1" and it works!!!

BUT I tried to change the Font again within the normal Serial Configuration connection which messed everything up again. So Use the firmware flasher to choose a Font that you would like and stick with it. Aftewards you can configure everything!

   


I want to thank you all for your help and I hope this thread might help other people. It's now officially done

(28-Apr-2017, 09:32 AM)Apicalis Wrote: BUT I tried to change the Font again within the normal Serial Configuration connection which messed everything up again. So Use the firmware flasher to choose a Font that you would like and stick with it. Aftewards you can configure everything!

Congratulations!  And this is great info! 

(28-Apr-2017, 09:32 AM)Apicalis Wrote: BUT I tried to change the Font again within the normal Serial Configuration connection which messed everything up again. So Use the firmware flasher to choose a Font that you would like and stick with it. Aftewards you can configure everything!

Great to hear that you got it working!

It sounds like you found a bug in the new configurator though and it would help the developers and everyone else who runs into this if you open an issue and report it. https://github.com/ShikOfTheRa/scarab-osd/issues

(28-Apr-2017, 09:59 AM)unseen Wrote: Great to hear that you got it working!

It sounds like you found a bug in the new configurator though and it would help the developers and everyone else who runs into this if you open an issue and report it. https://github.com/ShikOfTheRa/scarab-osd/issues

Good Idea!

Submitted, ty for pointing it out unseen. this might help some people with this problem and them to fix this issue

https://github.com/ShikOfTheRa/scarab-osd/issues/417

Thanks for doing that, it helps everyone.

(28-Apr-2017, 10:11 PM)unseen Wrote: Thanks for doing that, it helps everyone.

It already did https://github.com/ShikOfTheRa/scarab-osd/issues/418

Hope other people post their fixes too. Really gonna do that more often in the future

Nice, the problem is submitted by ShikOfTheRa to the Developer. 3 people already were able to fix their issue with my guide Makes me really happy

That's really good to hear!

This is exactly what issue management on github is for. It's just such a shame that so many people try to use the issues list for support instead.

Well that went waaaay faster than I expected

"Thank you for reporting. Confirm bug found. Updated configurator being deployed to store today.

Estimate this will be available 12:00 UTC 11/05/2017
Configurator Version 1.7.1.5"