This table shows the current clock synchronization state between all receivers. It will automatically update about every 30 seconds.

Each receiver pair has two main values: the number of synchronizations done in the last approx 30 seconds (larger is better) and the estimated synchronization error in microseconds (smaller is better)

The third value (at the bottom of each cell) is the relative frequency offset of the receiver clocks, in PPM. This is mostly just for interest. If you have values getting close to 200 it can be a problem, as the server will reject differences >200PPM - better fix your dump1090 --ppm setting!

Green cells are good, yellow cells are OK, red cells are bad. Grey cells mean there is no synchronization available between that pair of receivers.

It's normal to have quite a few yellow cells for number of synchronizations (usually this is infrequent synchronization between distant receivers).

Yellow cells for synchronization errors are uncommon - usually either the clock error is very good or very bad, there's not much middle ground.

Red cells for synchronization errors usually indicate a clock problem. If there's only one in a row/column it's probably a one-off outlier. If a whole row/column goes red that usually indicates clock instability in that receiver. Receiver pairs that have red cells are not used for multilateration.

The PPM values are relative values. They don't tell you anything about the true offset. However: the Vsky receiver is a GPS-synchronized Radarcape that should have an accurate frequency; so the offsets between Vsky and other receivers should be close to the true offsets.

If your column and row are empty then it means that your receiver is not synchronising with any others. The most likely cause is that dump1090 can no longer see your dongle so try a reboot in the first instance. If you can view the output of dump1090 locally in your web browser and there are no aircraft showing then check your aerial. If the column alternates between empty and partially full then you probably have two competing MLAT-Client installed on your system and both are fighting to send data to us. If that is the case, list them with

      sudo dpkg -l | grep mlat
      

      sudo dpkg --purge