MLAT Sync Matrix

Discussion in 'Feeding' started by Olivier, Nov 18, 2018.

  1. Olivier

    Olivier New Member

    Hi,

    I had a look at my MLAT sync data and I'm afraid I do not understand the data I see.
    Most of the boxes are green but some are yellow. Is there anything I should worry about?

    What do the yellow boxes mean?

    Olivier MLAT.PNG
     
  2. Freqman

    Freqman Member

    From the sync-site:

    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. (Sorry if you're colorblind! The colors are all configured in the stylesheet - send me better suggestions?)

    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.
     
  3. Olivier

    Olivier New Member

    Thank you, very helpful.

    Haha, it appears that I am moderatly colorblind but the choosen colors are separated enough for me to clearly see the difference so the stylysheet is fine for me.

    Olivier.
     
  4. W6CZ

    W6CZ New Member

    OK. So I’m having Sync issues. Running PiAware 3.7.0.1. I’ve rechecked the clock settings. I guess I could try another P 3B+
     
  5. W6CZ

    W6CZ New Member

    Swapped Pi - no difference
     
  6. wiedehopf

    wiedehopf Administrator Staff Member

    Are you running two dongles by chance?

    The other likely reason would be an insufficient power supply.

    Or are you running the Raspberry Pi4? That one needs the a fix which is currently only available via rpi-update.
     
  7. W6CZ

    W6CZ New Member

    No. I found the problem. I had entered

    DDD.MM.MMMM not DDD.DDDDDDD
     
    wiedehopf likes this.