(Edit - the MLAT flag changed to red again Sun/3/21 so it stands unresolved. Updated antenna location/elevation so will see if that has anything to do with it. If that doesn’t fix it I’ll just let it do the red/green flip flop. ADS-B works fine and that’s most of the traffic I see.)
We just updated our internet connection with CenturyLink from 7Mbps single connection to a 60Mbps VDSL bonded connection. Now my MLAT banner has turned red and I see this message:
“This feeder is not being used for multilateration because its timing information appears to be unreliable. This can be caused by the site location being incorrect, or because your Pi is running out of free CPU.”
We’ve also seen video streams on Roku defocus and lose detail. I think there is possibly an issue with out of sequence packets due to the two paths and error correction on the two paths (we see RS FEC corrections on both links - not too many but 55 on one connection and 15281 on the other right now since a reboot this morning. This varies and initially the counts were swapped. No CRC errors at all so far.
Is the issue with MLAT something that just happens with these dual path connections? Is this an issue with the FEC corrections? And is there any workaround?
We don’t have fiber here yet but apparently it is available if I don’t mind paying for trenching to get fiber to the house. Presumably that would be a single connection without the possibility to have data arrive out of order like this trunked connection now does.
Thanks for any guidance. Still learning the down sides to this kind of connection. I didn’t know there were any but out of sequence packets seem to impact a lot of things to varying degrees. Sigh.