Hi Kev
It seems to periodically (twice now that I'm aware of) to show the FLARM traffic at the local airfield as being rebroadcast from a station much further away (Church Fenton/Leeds East). Then when I reboot the Pi, all the local FLARM traffic starts showing as local again to Rufforth.
Interested to know how you determine that
Are you monitoring both stations at the same time ?
I think there may also be some confusion here, so lets clear that up first
if you are referring to the letter 'l' or 'r' on the Front page display, this merely refers to where the last data was received from
it could be local capture (through the RF/SDR), or remote capture (via the GRID) - this data is timestamped, so only the most recent is used internally.
There is a co-ordination from the GRID to tell each ATOM who should rebroadcast, as we do not want to clog the airwaves with un-necessary data. This is quite complicated, but in simple terms lets say, the ATOM(s) closes to the PAW requiring the rebroadcast is chosen - that may not be your ATOM, even though you are closest to the FLARM, you may not be closest to the PAW
In reality, each PAW is informing the ATOMS periodically who it can hear, this is then used as part of the GRID profiling for rebroadcasting, in most cases this relates directly to proximity, but not always - for example, local topography such as buildings, hills etc affect the broadcast in certain directions, the same is try of the aircraft obscuration, if antenna are situated internally to the front or rear
We regularly see a situation where rebroadcast only ever comes from ATOMS at certain directions from a plane, this is usually
due to obscuration either from the perspective of the aircraft, or the ground.
regarding noise - this is completely unrelated, we do not use this information as part of rebroadcast.
Out of interest, what dates did you push any software updates?
I think it was the 4/5 April
thx
Lee
