I just upgraded to 10.2 and now my WiFi Logging is broken. I use Putty on a Windows PC to Telnet into the Raspberry Pi and log port 30003 output. On the prior 9.X software it would run for hours to days with no problems. Now it won’t run for more than a minute before the logging freezes. Short of anyone knowing what is going on and has a fix – is there any way I can go back to 9.X? This is a classic “Well it used to work”.
Thanks,
Scott
Scott,
Firstly, welcome - it seems that this may be your first posting, so hi. You don’t comment which version of Windows you’re using, but if it’s 10, to eliminate Putty as a source of the problem, try this.
Open a Command Prompt (Windows key and R, then type CMD and press Enter) - should give you a black box.
On the assumption that your Pi user is still called pi, type in the following
SSH pi@whatever the IP address of your Pi is and press Enter. You should be challenged for the pi password; enter it and press Enter - this should give you a prompt.
Type in journalctl -f -u piaware and press Enter - this should give you a near-realtime update of the messages sent to/from 10.2 to FlightAware.
It would also be worth ensuring that either the IP address is static, or you have reserved the MAC address on the router, which causes it to issue the same IP address every time to the Pi.
Please advise how it goes!
I have just upgraded one of my remote sites to 10.2 and I am accessing it over a VPN.
I started Putty and entered the host name and port 30003 and it is running a continuous stream of messages as expected.
It is a Pi4 running Raspian installed with the Rapberry Pi imager and the Flightaware pagage install 10.0 and then updated to 10.2
It has now been running continuously for the last 20 minutes. I’ll leave it running for a while.
S.
Wifi issues are about the piaware image.
If you just install piaware on a pi, it won’t touch the wifi (as it should).
It has now been outputting messages on port 30003 for about 6 hours.
These are the types of messages I see continuously scrolling up the screen.
Is this what you want to see?
MSG,5,1,1,7C3DAD,1,2025/07/23,16:43:32.723,2025/07/23,16:43:32.743,3300,0,0,
MSG,6,1,1,7C3DAD,1,2025/07/23,16:43:32.731,2025/07/23,16:43:32.744,1200,0,0,0,
MSG,8,1,1,7C7CD1,1,2025/07/23,16:43:32.774,2025/07/23,16:43:32.797,0
MSG,4,1,1,7C7CD1,1,2025/07/23,16:43:33.323,2025/07/23,16:43:33.349,472,161,1536,0
MSG,8,1,1,7C3DAD,1,2025/07/23,16:43:33.404,2025/07/23,16:43:33.452,
MSG,8,1,1,7C34AB,1,2025/07/23,16:43:33.996,2025/07/23,16:43:34.052,0
MSG,3,1,1,7C34AB,1,2025/07/23,16:43:34.005,2025/07/23,16:43:34.053,1100,-38.05245,145.17406,0,0,0
MSG,4,1,1,7C34AB,1,2025/07/23,16:43:34.006,2025/07/23,16:43:34.053,102,321,-320,0
MSG,3,1,1,7C7CD1,1,2025/07/23,16:43:34.054,2025/07/23,16:43:34.107,33175,-39.31334,145.57100,0,0,0
MSG,8,1,1,7C3DAD,1,2025/07/23,16:43:34.524,2025/07/23,16:43:34.548,
MSG,8,1,1,7C7CD1,1,2025/07/23,16:43:34.974,2025/07/23,16:43:34.987,0
MSG,3,1,1,7C7CD1,1,2025/07/23,16:43:35.044,2025/07/23,16:43:35.091,33200,-39.31541,145.57190,0,0,0
MSG,5,1,1,7C3DAD,1,2025/07/23,16:43:35.143,2025/07/23,16:43:35.199,3300,0,0,
MSG,6,1,1,7C3DAD,1,2025/07/23,16:43:35.156,2025/07/23,16:43:35.200,1200,0,0,0,
MSG,4,1,1,7C7CD1,1,2025/07/23,16:43:35.204,2025/07/23,16:43:35.254,471,161,1472,0
MSG,8,1,1,7C3DAD,1,2025/07/23,16:43:35.594,2025/07/23,16:43:35.637,
MSG,4,1,1,7C34AB,1,2025/07/23,16:43:36.070,2025/07/23,16:43:36.080,102,323,-320,0
If I misunderstood the OP then please disregard my posts. 
S
No that’s my bad, didn’t read properly.
The wifi part confused me combined with all the other threads about broken wifi.
@satuthill
Log to check if the decoder is working:
sudo journalctl -u dump1090-fa --no-pager
Is this a piaware image or did you install dump1090-fa / piaware via commandline?
I’m a bit confused.
What has the output of port 30003 got to do with WiFi logging?
I use firefox and just type “< IP >:30003” into the address bar to display the output
Tony – a belated thanks for the reply. Yes I should have said Windows 11 among other background. I was in that “early frustrated” phase. I ended up power cycling the Raspberry Pi and all seems well now. 10.2 is behaving exactly like 9.X I was running before relative to logging on Putty. I am going to play around with some of your tips - it should increase my knowledge level overall.
Scott
Thanks again for the reply. I ended up power cycling the Pi4 and everything returned to normal. And, yes, those are exactly the types of messages I see as well. I log them then do some analysis looking at the impacts of different antennas.
Scott
Sorry I was not clearer - like I replied to Tony I was in the “early frustrated” phase and didn’t include all the details I should. Yes, your approach will display the Port 30003 output. What I am doing is logging it to a file for later analysis - for instance to see the impact of antenna changes. Putty has a built in logging function that writes the output to a file with structured files names etc. I pair this up with Windows Task Scheduler to create a new file every two hours. WiFi enters the picture because that is how I connect to the Pi4. And from the messages I received it seemed like the WiFi connectivity to the Pi4 somehow changed after the upgrade. But, you are correct, it was a poor use of vocabulary on my part. (And all seems to be well now after I power cycled the Pi.)
Scott
Got it, thanks.
I ran putty to see how it behaved. I was only displaying the data, not logging it to file, but it also stopped after a few hours.
All my Pi’s are wired.