![planeplotter feed not working planeplotter feed not working](https://www.geogebra.org/resource/kentnzsf/pgpOjnbLu5pmIU81/material-kentnzsf.png)
Therefore, the problem looks like it’s on the FlightAware side. Rebooted my computer and ran the test within Planeplotter and everything per the test is working. I checked for an updated version of Planeplotter, I was behind one version, so I ran the update. The X-Range 2 is AirNav System's newest 1090 MHz ADS-B out receiver. My Planeplotter feed stopped working as well. So using PCHFDL-Display available at is the best solution if you want to feed multiple PC-HFDL logs to PlanePlotter. Not having one all I can detail is what Airnav provides. This seems to trigger PP to forget the ID's it knows and avoids combining messages that don't belong to the same aircraft. But you probably know better what exactly happens in PP then I do :-)Īnyway, to avoid this PCHFDL-Display (one of the programs in the Display-Launcher suite) adds an additional "" record to the output file when messages from another PC-HFDL instance are written to the log. So if messages of multiple HFDL frequencies are written to one logfile that is read by PP then PP could combine messages that are not from the same aircraft causing 'corrupted data'. This ID is a velua between 00 and FF and only unique for that groundstation on that frequency. The HFDL protocol uses an ID in each message which relates to the aircraft when it loggen on to the groundstation. After I good night sleep I realised that I forgot to mention that your suggestion (if it works at all) can give unexpected results.