3 devices sharing din/dout for telementry and osd?

I have had poor to mixed results so far with both on same port, when plain text is sent to OSD it interferes with MavLink.

I am now attempting to use Port 0 with 4 pins added for TM to xBee 900 Pro only and Port 3 for Remzibi_OSD shared with FTDI using a cable for monitoring on bench/ground, I get poor GCS performance sometimes 4 second latency and unable to read/write waypoints reliably, fails after 1 to 5 WP are sent/read, but will finally read all 13 OK after 5-8 retries, OSD is very robust so far. I use a Y splitter to read /write to Port 3 with Sf 5v FTDI in the middle. OSD tx & rx are parallel with FTDI. Do NOT connect 5+ volt lines from APM or OSD to FTDI connection. Keep both 5+ lines insulated don't connect either to anything. I am testing slower speeds to see if it will improve WP read/write commands.

Replies

Developer

Mark Colwell April 12, 2011 at 10:08am

I have had poor to mixed results so far with both on same port, when plain text is sent to OSD it interferes with MavLink.

I am now attempting to use Port 0 with 4 pins added for TM to xBee 900 Pro only and Port 3 for Remzibi_OSD shared with FTDI using a cable for monitoring on bench/ground, I get poor GCS performance sometimes 4 second latency and unable to read/write waypoints reliably, fails after 1 to 5 WP are sent/read, but will finally read all 13 OK after 5-8 retries, OSD is very robust so far. I use a Y splitter to read /write to Port 3 with Sf 5v FTDI in the middle. OSD tx & rx are parallel with FTDI. Do NOT connect 5+ volt lines from APM or OSD to FTDI connection. Keep both 5+ lines insulated don't connect either to anything. I am testing slower speeds to see if it will improve WP read/write commands.

This reply was deleted.