stixchicken / arducam-osd

Automatically exported from code.google.com/p/arducam-osd
0 stars 0 forks source link

MinimOSD always shows "Update Charset" on power up, requires hard reset before use. #32

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Apply power to all components simultaneously (APM, OSD, etc)
2. After a few seconds, OSD will show "Update Charset" and stop
3. In order to use OSD, must hard reset it or wait ~20 seconds to apply power 
after powering the APM.

What is the expected output? What do you see instead?
-> OSD should boot and be usable without a hard reset first.

What version of the product are you using? On what operating system?
-> APM 2.0 with 2.8.1, minimOSD 2.0.

Please provide any additional information below.
-> This problem is fairly well documented here: 
http://diydrones.com/forum/topics/minimosd-says-update-charset-on-bootup-must-re
set-first?id=705844%3ATopic%3A805912&page=1#comments
-> Basically the APM is sending 3 returns, causing the OSD to go into Update 
Charset mode.  I imagine this method is required for getting into update mode, 
but it would be very beneficial if there is a good way to avoid the false 
positive when simply booting up to fly.

Original issue reported on code.google.com by debak...@hotmail.com on 30 Oct 2012 at 3:12

GoogleCodeExporter commented 9 years ago
If there is no elegant all-in-one solution, an easy fix would be to release a 
normal firmware, and in addition, a No Update Charset (NUC) version, which 
would have the capability for Update Charset commented out.

Also, the more I think about this, what if we could set the Telemetry delay in 
the CGS to 20 or more seconds?  Currently it limits to 10.  The capability to 
set 20+ seconds there might resolve this issue completely.

Original comment by debak...@hotmail.com on 12 Nov 2012 at 6:53

GoogleCodeExporter commented 9 years ago
OK, after further reading of the code and testing, I realized that LOWERING the 
TELEM_DELAY to be less than 5 seconds (0 to 4) will fix this problem, not 
raising the delay as I had originally thought.  I think this just needs to be 
documented somewhere on the MinimOSD page and this bug can be closed.  Thanks.

Original comment by debak...@hotmail.com on 17 Nov 2012 at 8:50

GoogleCodeExporter commented 9 years ago
Hi Debaker! It was documented here:
http://code.google.com/p/arducam-osd/wiki/Troubleshooting

Thanks!

Original comment by sbeni...@gmail.com on 12 Jan 2013 at 12:03

GoogleCodeExporter commented 9 years ago
I am having this issue UPDATE CHARSET
PX4 2.76 plane
OSD fw 2.0
I have tried various TELEM_DELAY as recommended (default was 0) at no avail.
Initially the two supply jumpers on the minimOSD was connected (supplying from 
12V).
I removed the solder jumpers and problem persists.

Would this not justify a OSD firmware fix?!
It is quite frustrating...
/ Tom

Original comment by tomas.so...@gmail.com on 29 Nov 2013 at 6:14