Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MicroMinimOSD not programmable
#1
I've read many threads so far but none of the solutions seem to work.

So here are the facts:

- The OSD Boots and shows the "ArduCAM OSD V2.0" Screen with "Waiting for MAVLink Heartbeats..." which is the "factory default".
- I am using a Prolific USB-> Serial converter and downloaded the latest driver for my 64bit Windows 7 System.
- The Arduino Version is 1.6.10 and the Arduino drivers are installed aswell
- The minim OSD is only connected to a 5V powersupply, a Videomonitor and the Serial Connection, nothing else.

Connections [USB/Serial to MinimOSD]:

- RX-TX
- TX-RX
- GND-GND
- DTS-DTS

Problem:

MWOSD Configurator GUI (1.7.1.2) can be connected "2017-04-24 @ 10:14:10 -- Connected" is shown. But the connection isn't really finished. Top of the screen shows "Waiting for OSD..." and I can't use any of the functions. If i click a button it says "Another task is in progress".

If I use Arduino IDE to program MWOSD i get

avrdude: stk500_recv(): programmer is not responding

avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x4f

Things I've tried:

- Swapping RX/TX, after the Swap nothing works. Neither Arduino IDE or MWOSD Configurator can establish any kind of connection
- Switching the Bautrates in MWOSD Configurator. Same problems continues.
- Updating the USB/Serial driver.

I am sorry that I have to ask here but none of the 10000 threads about this topic helped so far :/
I like turtles
Reply
Login to remove this ad | Register Here
#2
What board are you using to program it? I'm using the red FTDI adapter from banggood and it works without any problems
Reply
#3
The micro minimOSD needs DTR, RX, TX, 5V, Gnd from the programmer to DTR, TX, RX, 5V, Gnd on the minimOSD.  I haven't tried getting 5V from somewhere other than the serial programmer.

EDIT: I think if you are getting the Mavlink Heartbeats message, it means you haven't flashed MWOSD to the OSD yet. So MWOSD configurator won't work anyway.
Reply
#4
Just went back and looked at your build thread.  You are using the SP F3 Evo (and Clean/BetaFlight presumably).  The minimOSDs you got are programmed to expect a MAVlink protocol, while your FC is communicating via MSP.  You will necessarily have to reflash your micro minimOSDs with MWOSD firmware.

Here's a video that explains the differences:


I'm not sure, but your USB/serial cable may not work to do this - I'm not familiar with it.  But like oyvinla said, there are some good cheap ones on Banggood that work great.
Reply
#5
(24-Apr-2017, 12:27 PM)oyvinla Wrote: What board are you using to program it? I'm using the red FTDI adapter from banggood and it works without any problems

I am using a USB to Serial adapter (Profilic). But since I am also thinking that that might be the cause I went to a colleague and got a Proper AVR Flasher (AVRISP MK II)

(24-Apr-2017, 12:28 PM)sloscotty Wrote: The micro minimOSD needs DTR, RX, TX, 5V, Gnd from the programmer to DTR, TX, RX, 5V, Gnd on the minimOSD.  I haven't tried getting 5V from somewhere other than the serial programmer.

EDIT: I think if you are getting the Mavlink Heartbeats message, it means you haven't flashed MWOSD to the OSD yet. So MWOSD configurator won't work anyway.

Since people suggested that it's possible to Set it up via serial passthrough i expected it to only need a Serial connection, but I looked at other threads and Videos and it seems that at first it actually needs to be flashed with a proper programmer and after that the config via Serial only can be used
I like turtles
Reply
#6
(24-Apr-2017, 12:59 PM)Apicalis Wrote: I am using a USB to Serial adapter (Profilic). But since I am also thinking that that might be the cause I went to a colleague and got a Proper AVR Flasher (AVRISP MK II)


Since people suggested that it's possible to Set it up via serial passthrough i expected it to only need a Serial connection, but I looked at other threads and Videos and it seems that at first it actually needs to be flashed with a proper programmer and after that the config via Serial only can be used

Yeah, you can't flash the firmware via serial passthrough (unless something has changed).  It's got to have the MWOSD firmware already on it.
Reply
#7
(24-Apr-2017, 01:07 PM)sloscotty Wrote: Yeah, you can't flash the firmware via serial passthrough (unless something has changed).  It's got to have the MWOSD firmware already on it.

Why didn't it work:

- Serial wiring I did was correct, but it was RS232 and the Arduino needed TTL Signal. So I used an Arduino UNO and bridged RESET and GND. When you do that your Arduino acts as an USB<->TTL Converter. BUT the DTS Line is missing, so during compiling you have to bridge RESET and GND on the MinimOSD board and once you see the "Upload" bar within the Arduino IDE you can disconnect RESET and GND from eachother.

- The AVRISP MKII is a ISP Programmer and is needed to add the bootloader or the program without bootloader. So it was not needed in this case.

Litte issue:

I get a connection via MWOSD Configurator and can change settings and flash them and if i disconnect and reconnect and load the current data i can see the exact same settings. So the upload is working properly to the chip.
But I get nothing on my Testmonitor anymore :/ I can hear how it "turns on" but shows a blank screen. Shouldn't at least the Call Sign be displayed?

The OSD is set to PAL since my Runcam also runs with PAL

EDIT: Does it wait for a connection to my Flightcontroller? I put a test signal into the OSD that gets passed through the OSD and shown on my test monitor. BUt the OSD information is still missing
I like turtles
Reply
#8
Just a side note: with the new mwosd chrome gui, you can flash a hex file in the GUI. I think it is from v1.7.0

I have tried it with an ftdi adapter, and it works. Maybe we can use the FC serial passthrough and flash as well?
Reply
#9
Requires DTR passthrough, not implemented in BF.
Reply
#10
I didn't realize that when i first wanted to hook up the AVRISP MKII i ripped off one of the solder pads. After I saw it I tried the descriped programming process with the OSD that was already mounted in my Quad and got it to work! So the other OSD is broken now but that's okay. Its only a few € anyways.

Ty for your help guys!
I like turtles
Reply
#11
Aaand as always i have follow up problems...

The OSD was working perfectly fine and i was able to setup the layout... BUT, the Signs (mAh, Battery Symbol etc.) were wrong and partially cut off. I think most of the signs were Arrows. So I thought "just reupload the standard Fonts". After uploading the letters are completely unreadable. It's still the same layout and all but the letters are unreadable. So I decided to try all the 3 standard Fonts but nothing fixed the issue or brought it back into the first state.

I reset everything and it's still bugged. Does anbody have an Idea how to fix it?

I don't want to unsolder everything again to wipe the eeprom Sad


EDIT: Looks like i got to desolder and wipe the EEPROM -.- Totally forgot that I only did that on the faulty one and not the one that was already mounted in the quad. Come to think of it, I should be able to do the whole thing without desoldering. I just have to bridge RESET and GND until the actual Upload process in the Arduino IDE starts
I like turtles
Reply
#12
Sad news, the EEPROM erase didnt help. Still the same issue Sad Absolutely unclear letters that are basically fading away.
I like turtles
Reply
#13
What version of MWOSD are you using?
If you are using 1.6, try a different version like 1.5 or 1.4..
Same thing happened to me, using a different version sometimes help... only downside is PID tuning might not work but at least gets you flying
Don't be a LOS'er, be an FPV'er :)  My Gear - Facebook - Instagram - Twitter
Reply
#14
(26-Apr-2017, 11:11 AM)Oscar Wrote: What version of MWOSD are you using?
If you are using 1.6, try a different version like 1.5 or 1.4..
Same thing happened to me, using a different version sometimes help... only downside is PID tuning might not work but at least gets you flying

I am using the most recent Version 1.7 I just read that some people had to use EEPROM Clear over and over again until the OSD worked properly. I will try that first and if that doesn't help I will check out the older versions
I like turtles
Reply
#15
(26-Apr-2017, 12:06 PM)Apicalis Wrote: I am using the most recent Version 1.7 I just read that some people had to use EEPROM Clear over and over again until the OSD worked properly. I will try that first and if that doesn't help I will check out the older versions

Cool Smile
IMO MinimOSD is an outdated technology Smile check out Betaflight F3 if you are next looking for FC, the built-in OSD works so much nicer!
Don't be a LOS'er, be an FPV'er :)  My Gear - Facebook - Instagram - Twitter
[-] The following 2 users Like Oscar's post:
  • Apicalis, sloscotty
Reply



Login to remove this ad | Register Here