ndutton / minimosd-extra

Automatically exported from code.google.com/p/minimosd-extra
0 stars 0 forks source link

Minim OSD Overlay Changes Upon Bootup, No Video, Parameters Change #105

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I am having problems with my APM 2.6 and MininOSD. I have read through the 
forums and have found no answers. I am running an APM 2.6 with the new updated 
APM Planner. I have flashed the MinimOSD with the newest Extra firmware. I have 
set up my overlay just like I want and once I plug in the battery, I see 
MinimOSD Extra 2.4 flash up. The overlay is just like I set up in the Config 
Tool, but then it changes to a bunch of unreadable overlay info all across the 
screen. Also, no video feed either. Parameters in APM Planner default upon 
re-opening, also. Followed the wiring set up from here: 
https://code.google.com/p/arducam-osd/w ... e_Diagrams. Using an Immersion RC 
TX. Lots of problems, no answers on here. Please help!!!!

Original issue reported on code.google.com by cale.h...@gmail.com on 1 Dec 2014 at 5:59

GoogleCodeExporter commented 9 years ago
HEllo,

Could you please show me a video of this problem?

Gábor

Original comment by gabek...@gmail.com on 1 Dec 2014 at 8:37

GoogleCodeExporter commented 9 years ago
I have included a video of exactly what is happening.  Sorry for the small 
screen, I attempted to video through my Fatshark goggles.  

https://www.youtube.com/watch?v=nDh-zznGgaY&feature=youtu.be

You can see the firmware boot up, flash the version, then go directly to the 
proper info overlay I have set up through the CT tool.  Once the APM 2.6 boots 
up and starts talking back and forth, the Minim changes the overlay completely, 
which you can see directly after the first overlay layout.  

Original comment by cale.h...@gmail.com on 1 Dec 2014 at 11:59

GoogleCodeExporter commented 9 years ago
I think you character set is not updated.

Update it then it should work.

Original comment by gabek...@gmail.com on 1 Dec 2014 at 2:19

GoogleCodeExporter commented 9 years ago
I was able to update my character set, but this didn't change a thing.  I was 
able to solve the no video problem.  The only way I was able to get the OSD 
overlay to work properly was to run the Arducam 2.1.2.0 CT program with 
MinimOSD Extra Copter 2.2.  Everything seems to be working OK except for 
Distance from Home, Home Direction, and RSSI.  Any pointers to get these to 
work?  In my opinion, those would be the most important.  How to get home, how 
far from home you are, and your reciever strength.  Thanks!

Original comment by cale.h...@gmail.com on 2 Dec 2014 at 4:37

GoogleCodeExporter commented 9 years ago
It seems like a more like you have a hardware problem. Which hardware do you 
use? Did you do any modification to hardware?

Original comment by osiarbay...@gmail.com on 2 Dec 2014 at 6:49

GoogleCodeExporter commented 9 years ago
Definitely not a hardware problem.  I have two MinimOSD's, both from 3DR and 
two VTX, one is an Immersion RC and one is a Fatshark.  Everything is stock, 
just like out of the box.  As I flash different firmware, I get different 
results.  However, I have found a pretty good combination, allowing me to get 
most of the things I need to work properly.  Using the newest CT tool, the 
newest Extra firmware for the copter, and an older version of the charset, I 
was able to get things working.  I know and understand hardware, it is what I 
do.  I do not understand software, but this seems to be a bit of a joke.  Why 
release something that isn't good or has bugs?  Just my two cents.  I shouldn't 
complain, as I was able to get things working for the most part.  

Original comment by cale.h...@gmail.com on 3 Dec 2014 at 1:06

GoogleCodeExporter commented 9 years ago
How did you upload character set file?

Was analogue side powered also?

Gábor

Original comment by gabek...@gmail.com on 3 Dec 2014 at 8:59

GoogleCodeExporter commented 9 years ago
Did you solve your problem completely?

Original comment by osiarbay...@gmail.com on 9 Dec 2014 at 4:25

GoogleCodeExporter commented 9 years ago
The issue was resolved by running older versions of firmware and charsets.

Original comment by c...@nextgenfoam.com on 11 Dec 2014 at 8:22