My main test receivers are a B and a B+ (not overclocked), so yeah, it works OK on them. The busier of the two does have very little spare CPU (2-3%)
The CPU required is very dependent on how much traffic you see, so in busy areas you may start to run out of CPU, especially if you have anything other than dump1090 + piaware on there.
I was wondering the same thing, I thought maybe my client had been barred temporarily as I was mucking around with the gain settings in dump1090, and thought that as my connection was flapping I’d been blocked… I guess not if you aren’t seeing any MLAT feedback…
PiAware.out is showing
07/19/2015 07:47:43 15610 msgs recv’d from dump1090-muta (1398 in last 5m); 15610 msgs sent to FlightAware
07/19/2015 07:52:43 16871 msgs recv’d from dump1090-muta (1261 in last 5m); 16871 msgs sent to FlightAware
07/19/2015 07:57:43 18022 msgs recv’d from dump1090-muta (1151 in last 5m); 18022 msgs sent to FlightAware
07/19/2015 08:02:18 mlat(20445): Receiver connection: ready
07/19/2015 08:02:18 mlat(20445): Server connection: ready
07/19/2015 08:02:18 mlat(20445): Receiver: 912.4 msg/s received 16.8kB/s from receiver
07/19/2015 08:02:18 mlat(20445): Server: 0.0 kB/s from server 0.0kB/s TCP to server 3.0kB/s UDP to server
07/19/2015 08:02:18 mlat(20445): Aircraft: 90 known, 62 requested by server
07/19/2015 08:02:43 19314 msgs recv’d from dump1090-muta (1292 in last 5m); 19314 msgs sent to FlightAware
07/19/2015 08:07:43 20795 msgs recv’d from dump1090-muta (1481 in last 5m); 20795 msgs sent to FlightAware
(times are UTC)
I was just wondering why the MLAT server is being told about the planes with position (the disparity in the total 90/94 would be covered by time gap between grabbing data from the file and dump 1090)
possibly and I’ll be adding to it next week with the installation of another base station out Ipswich way and while it won’t get MLAT data a base station in the North West Pilbara is in the pipeline! Hopefully be able to fill some of the black hole around Karratha.
I’m sure I posted a chunk of log showing the mlat being disabled/enabled from the server end just as the feedback to the mlat clients came back… Did that get moderated?
I gotta say guys, the accuracy of your DVB-T derived MLAT is excellent and very consistent! Loving seeing all the extra planes, and I cannot wait for the take up to increase and also for you to release it to other platforms as well with DVB-T… (why anyone with home brew would want anything other than a Pi though is slightly beyond me )