After almost 3 weeks of successful feeding, I switched to a WiFi connection on my Raspberry Pi yesterday. Today I received an email saying I wasnt feeding (great idea that, I welcome it). I was getting :8080 plots on the LAN and could connect to the Pi with Putty and SCP, confirming the WiFi was ok. I could also ping an external address by name.
The log ended with:
07/13/2015 03:36:03 mlat: Aircraft: 15 known, 13 requested by server
07/13/2015 03:36:27 28113 msgs recv’d from dump1090 (142 in last 5m); 27514 msgs sent to FlightAware
07/13/2015 03:41:27 28270 msgs recv’d from dump1090 (157 in last 5m); 27671 msgs sent to FlightAware
07/13/2015 03:42:57 timed out waiting for alive message from FlightAware, reconnecting…
07/13/2015 03:42:57 multilateration data no longer required, disabling mlat client
07/13/2015 03:42:57 reconnecting after 60s…
07/13/2015 03:42:57 mlat: Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
07/13/2015 03:43:57 the system told us that process 16663 exited cleanly
07/13/2015 03:43:57 the system confirmed that process 16663 exited with an exit status of 0
07/13/2015 03:43:57 connecting to FlightAware 70.42.6.203/1200
A re-boot, resumed service. I wonder if anyone could give an indication of why it stopped sending to FlightAware and how I might correct/mitigate against that?
Some of the WiFi dongles go to power save mode and turn off.
There are scripts floating around here to turn the power saver off. Im sure more knowledgeable people will post soon and get you set up. Im still new with this stuff
Thanks. I dont think this is the reason as I could connect to the Pi over the LAN (via WiFi) successfully. I had seen this power save issue mentioned and ran a script which I believe turned off this power save function
