No mavlink data on Pixhawk or APM with r726

[GoogleCodeExporter]

What steps will reproduce the problem?
1.All attempts to view mavlink data with MinimOSD as master Telem device after 
fw r726 update fails to show live readings.
2.System works fine with old non extra fw 2.1.3 
3.

What is the expected output? What do you see instead?
Expected to work with r726 as well as it does with original fw as supplied (by 
3DR in this case). It seems like its not requesting mavlink data properly.

What version of the product are you using? On what operating system?
MinimOSD 1.1 

Please provide any additional information below.
It seems at this time that unless there is another device on the serial bus 
that the OSD doesn't work with APM2.6 or a Pixhawk, tried both here. Reverting 
to original minimosd firmware restores function. 
Will confirm properly later but it looks like when a 3DR radio is in parralel 
the OSD works as expected on r726 but not alone.

Original issue reported on code.google.com by mrdotsne...@gmail.com on 16 Aug 2014 at 2:31

[GoogleCodeExporter]

Additional info. Tried the older MinimOSD EXTRA firmwares 2.2 and 2.4 releases, 
and none work either. Reverting again to original MinimOSD fw resolves display 
of telemetry. 

Original comment by mrdotsne...@gmail.com on 16 Aug 2014 at 2:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This is HUGE!  I spent the better part of the last month trying to get my OSD 
to work.  I ordered a FTDI cable to revert my OSD back to stock, but I got 
stuck with a cable that wouldn't work due to Windows and FTDI screwing me on 
driver updates.  (I've since turned off auto driver updates). In any case, this 
info is definitely not mainstream yet.  I was only able to get my OSD working 
by putting it on the same port as my telemetry radio.  It didn't matter which 
telemetry port I used, the 1st one or the 2nd one.  What mattered was if my 
telemetry radio was on the same port or not.  The nice part of the hobbyking 
board was the fact that it got me away from the -Cable.  I guess someone said 
"not so fast".

So I guess the two options right now are 
1) revert back to original firmware. (I cannot confirm this method)
2) don't use two telemetry ports.  Use a Y cable instead.

HKPilot 2.7
Minim OSD

Original comment by Jason.C....@gmail.com on 23 Nov 2014 at 6:50

[GoogleCodeExporter]

Closed as we have a new version.

Ifthe problem is still present please reopen it.

Original comment by gabek...@gmail.com on 28 Nov 2014 at 11:44

• Changed state: Done

[GoogleCodeExporter]

Been trying to load FTDI driver for MAVlink and 3DR. The problem is within the 
FTDI driver itself. Says it installs but then shows as uninstalled in the 
Device manager. Not listed in programs. XBee works and the system lets the XCTU 
"see" the XBee modem. Strange, as I never loaded any driver for it. as if some 
part of the FTDI driver exists somewhere. Never worked before without loading 
driver for XBee Serial adaptor. Complete fresh reboot of entire Window 8.1 
System. HOURS. tried to install FTDI with nothing else installed yet. Only 
recognizes FT232 USB UART without driver and can not find driver online or 
anywhere. Just wrote extensive explanation to FTDI. Awaiting response.    D 
Drake  propel7@msn.com   

Original comment by propelse...@gmail.com on 1 Dec 2014 at 6:12

[GoogleCodeExporter]

I too am having issues. I get Mavlink data on my OSD as long as it is connected 
to APM Planner. If not, there is no data. I am using the y-cable sent from HK 
for my 2.7 board.

Original comment by twstee...@gmail.com on 4 Dec 2014 at 2:38