Hi Taildra99er,
The enabling switch for MLAT is on the PAW ‘Configure’ Setup Screen - accessed from 192.168.1.1 (it’s called Mode-S/3D).
To be sure what is going on, we need to check several settings including what Mode C/S Range you have selected, so can you post a screenshot of your Configure Settings please.
To get fixed position MLAT reports, as well as being in receipt of an uplink from a Ground Station yourself, the Mode-S aircraft must also be in range of at least 4 360Radar receiving stations in order for it’s position to be triangulated. There are a considerable number of these across the UK, many of which are not PAW ATOM-GRID rebroadcast stations. Where this is not happening, PAW automatically reverts to reporting the aircraft as a Bearingless target - with in your case SD’s coloured rings to indicate degree of risk, plus relative altitude and either Mode-S Reg or a Mode-C identifier.
The warnings you then receive are dependent on the Mode C/S Range and Vertical Separation you have selected in PAW Configure. In this case, Rosetta will inform you of the aircraft it deems to be the greatest risk but this can cause the system to alternate between reports from two aircraft with similar received signals, where for example one is much higher power (e.g. commercial) but at greater range than the other, and possibly still out of visible range. I suspect this was what was happening in your case.
Regards
Peter