I have APM2, XBee Pro 900, connected to MinimOSD without TX line as advised. When I power up the system, the MinimOSD always shows Booting, then "Update Charset" and goes no further. If I press the hard reset it works fine again, but never on initial bootup. It also does this if I unplug the XBee and connect the MinimOSD directly to the APM with all pins connected.
Is anyone else having this problem? This does not seem like normal behavior.
I have also re-updated the firmware and charset with the MinimOSD software and nothing changed.
Please help!
Replies
I'm having the same issue as described. I have the latest OSD firmware and Character set installed. I've tried various TELEM_DELAY times from 0 to 10 and the problem still insists. The default time was set to 0. By the way, I have the Pixhawk with Aruduplane 3.2 loaded.
Recently when I wired up my Iris+ to do OSD, i notice that when I first power on my Iris+, I do not power the gimbal until the OSD board boots up. Once it boots I can then plug in my 2d gimbal.
When I have the gimbal power cord plugged in when I plug in the Iris+ I get the update character set. This usually indicates that I have powered on the Iris+ with the gimbal plugged in. I then restart the Iris+ with the gimbal unplugged.
APM 2.6 and new MinimumOSD all from the shop here and Same issue. I ordered a USB to the MinimumOSD cable so I can update the OSD. I hope that will solve this!
hi all,
I have a problem,
after updating the firmware with the latest relase and subsequently updated the character set with Latest_Charset.mcm
but always visualize these writings:
can anyone help me? please
OK, in the latest MinimOSD release, you can avoid the "Charset Update" problem on power/boot by simply setting the TELEM_DELAY to be 4 seconds or less. Setting it to 5 seconds or more will cause it every time. Enjoy!
I'm seeing this issue again after upgrading to the latest minimOSD firmware (2.0) with APM 2 using 2.8.1. Is there a good way to correct this that doesn't require code tweaking?
It seems terrible that the standard procedure after powering up is to hard reset the OSD before it is actually usable.
I emailed 3DR support and explained the problem to them directly as well. They asked me to ship it back for warranty repair/replacement, so they sent a FedEx label and RMA # and I sent it back... I Hope they can reproduce and solve the issue.
Also, I've tied the power line from the analog to digial side so that the video chip will be powered from the +5V from the APM2 since my video equipment has it's own power. Can't imagine that this would make any difference, but that's how I've run it from the start.