That is corruption I have only seen one time before, which was fixed with a full reboot of the system. You will notice the date/time stamps on the left are invalid, and that the payload data on the far right is "sliding to the left" on the next line below. Included below is a short sample of some of the raw data. I just spot checked your Pi ppup1090 system 'ZD', and as of 1645 UTC, the raw data it totally corrupt. That can really complicate testing from the server end. Your system looks fine, but I expect there is no need to have the Raw data for mlats enabled like you do.
Planeplotter raspberry pi windows#
We have users uploading from a Pi and ppup1090, that still upload other types of data such as ACARS through their Windows PP system. There is likely some small bit of data exchanged as part of the up/down process, but it is not aircraft. Your total aircraft up count also equals zero as expected. Hi Don, (check your Pi system 'ZD') I just checked your PP system. On Fri, at 11:22 AM, Donald Froula wrote: I wonder if any data is uploaded to the servers from Planeplotter if bidirectional arrows are enabled on the top portion of the window, but no upload sharing options are selected? Perhaps bidirectional sharing needs to be enabled to allow Planeplotter to initiate an MLAT request to the servers? I can confirm that the ppup1090 command option you have listed is correct to forward mlat to PP. Upload section? Also make sure that Upload positionless data above the Upload section is not checked. I dislike enabling sharing uploads from Planeplotter, as it duplicates the data uploaded to the servers from the Pi and also includes some MLAT aircraft from FlightAware due to the way I mix that data into the Planeplotter feed with modesmixer2.ĭon, Have you tested with PP running up/down, however with no boxes selected in the Options. In fact, I seem to be unable to initiate an MLAT on any aircraft unless bidirectional sharing from planeplotter is active.
I then see the color-coded "aircraft with MLAT possible" and can initiate an MLAT request. I find that in my aircraft list view, I am unable to select the "Aircraft with MLAT possible" filter unless I select bidirectional sharing.
Planeplotter raspberry pi Pc#
My 9742 port forwarding goes to the Pi, of course I also have invoked ppupto90 with the "-net-pp-ipaddr 192.168.1.130", pointing to my Planeplotter PC with fixed IP address. On Fri, at 10:42 AM, Donald Froula wrote: I am still a bit puzzled about MLAT initiation from a system where Planeplotter has inherited MU status by virtue of the Raspberry Pi ppup1090 (mode a/c version) MLAT capability. What is the difference between initiating an MU MLAT request with Ctrl-click and Shifted-Ctrl-click? Should I not be able to initiate an MLAT without Planeplotter upload active? Thanks for any clarification. The ground stations send data back on port 9742 to the Pi which forwards the data back to Planeplotter for processing. Planeplotter sends requests for MLAT data to those ground stations. My understanding is the MU MLAT request goes directly from Planeplotter to the servers, which sends a list of ground stations in return.
"Allow auto MLATS" and "Raw data for MLATs" are selected in my IO settings. I dislike enabling sharing uploads from Planeplotter, as it duplicates the data uploaded to the servers from the Pi and also includes some MLAT aircraft from FlightAware due to the way I mix that data into the Planeplotter feed with modesmixer2. I am still a bit puzzled about MLAT initiation from a system where Planeplotter has inherited MU status by virtue of the Raspberry Pi ppup1090 (mode a/c version) MLAT capability.
0 kommentar(er)
