The ping usb actually outputs mavlink messages over usb at 57600 as far as I’ve been told from uavonix.
So as for a direct connection that would probably be the simplest way to use it with MP but I think that would have to be added in. I don’t have a dump of that raw mavlink data.
As far as what I’ve described above… Here is a raw dump from the “base station” format of Virtual Radar Server.
TCP_DUMP.txt is the python script used to collect basestation_format_raw.txt (can’t upload a .py file)
Weird. I think i remember trying that and I couldn’t get it working that way. I don’t have one on hand right now to test with but next time I have one i’ll check. Thanks for the reply michael.
I already tried to connect via TCP (127.0.0.1) on ports 30003 and 31004, but the pingUSB is not communicating with MP. Virtual Radar shows the planes, but I can’t find a way to send that info back to MP (perhaps a format problem). According to uAvionix, “selecting the appropriate COM port on Mission Planner and Baud Rate at 57600, you will not see Parameters come through, but if you hit cancel on the “Connecting Mavlink” box, you will see ADS-B information displayed”. After canceling the MAVlink connection, the planes appear, but they obviously don’t update their position. Any thoughts? Please help. Thanks.
Hi Michael, I have also attempted to feed the Virtual Radar rebroadcast into MP GCS as Basestation format via the Planner ADSB checkbox without success. 127.0.0.1 and 30003, 31004 etc. The reason for Basestation format is due to the ADS-B receiver not outputting MAVLink format (uAvionix pingStation).
Have there been any developments here as I have not yet seen a resolution to this issue?