I could use some help with this Serial Output project from those that have had success hooking up to their EFIS.
I have an rP3 with 1090 and 978 SDRs with remote 1/2 wave antennae, an external GPS module, and the USB-serial cable from OFS. I’m running the Beta image file (ver 1.1b1) on my SD card. On the UI, I see tons of 1090 and 978 traffic (real and, I believe a few simulated) and have lock on at least 10 GPS satellites. Prior to this, I’ve run iFly over the Wifi adapter, and it worked fine. However, when I hook up the USB-serial cable, no joy.
For the USB-serial project, I’ve tried two devices to serve as my ‘EFIS’ . Neither has been able to see GPS data. One is a Naviter Oudie, a small PDA-like flight computer, which accepts external GPS and traffic (NMEA) data to a designated COM port, and the other is a Windows PC, running XCSoar, which does the same. For the Oudie, I patch directly to the rP3 thru the USB-serial cable. For the PC, I must connect the USB-serial from the rP3 thru another USB-serial cable to the the PC.
I know that I’m getting good connections, as both programs have a terminal feature that displays what is coming thru the COM ports. Both configurations display streams of characters interspersed with the flight numbers of many of the aircraft displayed on the UI. I think this means I’m getting ADS-B data, but no GPS thru the cable, as these devices cannot get a location fix on themselves or other traffic. It doesn’t seem to matter what baud rates I choose, as long as the Flightbox and EFIS COM port speeds match. It doesn’t seem to matter what ports I plug the GPS or USB-serial cables into on the rP3, nor does it help to use a powered USB for either device.
There was mention of a conflict between the USB-serial and GPS, but this was handled by designating unique identifiers to these devices. I’m not sure if there is an existing conflict between the USB and GPS, but am open to any ideas as how to troubleshoot his possibility.