I migrated from Windows and have fr24feed installed on a Pi Zero and on Linux Mint (debian) on the previously Windows laptop. Both dump1090-mutability. The Pi zero has adequate power (2.2A). I was very careful to ensure the position of the aerial, RTL dongle, etc remained identical in my testing. Obviously I don't have both running at once as I only have one dongle!
I have now run both setups for a week each and the Laptop with Mint consistently manages a range of 53nm on the feed-stats (same as Windows did). The Pi zero only 30nm. I should explain that I have hills and mountains around me so that's the extent of my "view". I know where the Windows, now Mint, feed picks up planes at cruising altitudes so I can see what the Pi isn't getting looking at the FR24.com map. I have --gain 48 in the process arguments of both as per Oblivion's "DVBT Feeder Gain Adjustment - WIP" post.
Looking at the tracked aircraft on the local:8754 page it seems the Pi isn't picking up the lat and long where the laptop is. Just says "N/A". All the other details are there - ModeS, Altitude, Squawk, even Callsign. If it is receiving the lat/long it certainly isn't displaying it. This applies to major commercial aircraft not business jets etc. So presumably the incompleteness of the data is why my range is down on the stats. And even though the gain is set I can't see why it'd be that anyway - if the Pi's gain were too low it wouldn't pick up anything surely?
I'm flummoxed! Any ideas please?
I have now run both setups for a week each and the Laptop with Mint consistently manages a range of 53nm on the feed-stats (same as Windows did). The Pi zero only 30nm. I should explain that I have hills and mountains around me so that's the extent of my "view". I know where the Windows, now Mint, feed picks up planes at cruising altitudes so I can see what the Pi isn't getting looking at the FR24.com map. I have --gain 48 in the process arguments of both as per Oblivion's "DVBT Feeder Gain Adjustment - WIP" post.
Looking at the tracked aircraft on the local:8754 page it seems the Pi isn't picking up the lat and long where the laptop is. Just says "N/A". All the other details are there - ModeS, Altitude, Squawk, even Callsign. If it is receiving the lat/long it certainly isn't displaying it. This applies to major commercial aircraft not business jets etc. So presumably the incompleteness of the data is why my range is down on the stats. And even though the gain is set I can't see why it'd be that anyway - if the Pi's gain were too low it wouldn't pick up anything surely?
I'm flummoxed! Any ideas please?
Comment