search

PlayUAV / PlayuavOSD

A Graphical OSD for FPV
http://en.playuav.com
GNU General Public License v3.0
67 stars 60 forks source link

Enhancement request/Bugfix: delayed startup #31

Closed athertop closed 8 years ago

athertop commented 8 years ago

I often find that when the craft is first powered up for flight, the PlayUAV momentarily flickers the camera output on the OSD screen (without telem overlay) then simply displays a blank screen with no camera output or telemetry overlay from that point on. The only way I can imagine the cause of this would be if the PlayUAV started up before the telemetry feed from the Pixhawk and decided that no telem feed = choose not to startup. Re-powering the craft often cures this race condition (assuming this is in fact the cause) and things then work normally. This is of course a guess as to the cause, but if this suggestion was in fact true, then would it be possible to introduce a delayed startup on the PlayUAV OSD, such that it allows the Pixhawk to boot up before the OSD checks for the telemetry feed? Maybe a manually entered delay parameter in the settings? If this assessment is not true, then maybe some other bug causing the startup failure. Not sure if I am able to capture a log in some way to help with debugging of this issue, but would be happy to assist where possible to find a resolution. Thanks.

TobiasBales commented 8 years ago

@athertop The osd does work fine when the mav link data comes somewhat later (it does take a while for me) the issues is probably something else. Have you tried hitting the reset button on the osd after startup to see if the picture is there then?

TobiasBales commented 8 years ago

@athertop did this fix itself? Or did you change something? Just so we have that documented ;)

athertop commented 8 years ago

I think it might have been due to having 2 cameras one pal and the other ntsc. Seems OK now