Hi Rog,
The only way I know to tell if the 1090 feed is working is to connect to your OGN station locally, via its IP address or via 'ognpawlocal' - I suggest using a laptop (see * later).
Once connected you will see the OGN-R Status Page, with tabs to link to various other screens.
You now need to login to the Pi itself, using the login pi and your set password (or the default 12345678 if no password has yet been set). Once you have done so, you will see the prompt... pi@ognpaw:~$
Now you need to change directory by typing cd rtlsdr-ogn {enter}
You will now have the prompt... pi@ognpaw:~/rtlsdr-ogn $
Now type nc localhost 30003 {enter}
You should now see a stream of data being sent off to Radar 360 (assuming there is 1090 traffic within range).
* To exit the stream on screen - (not to Radar 360) you are supposed to type ^C - but I must admit I can't get this to happen from my iPad, hence why I suggest using a laptop where the alternative 'Ctrl C' typed together does work and returns you to...
pi@ognpaw:~/rtlsdr-ogn $
Finally simply type exit {enter} to disconnect the login session.
p.s. If anyone can tell me how to get ^C to work from an iPad I would appreciate it.
When using PAW RADAR, the main difference in depiction of MLAT traffic is that the Radar screen shows 'Ambiguity Circles' as pink discs around MLAT aircraft, (a larger circle indicates a higher potential for position inaccuracy), though this is only visible where the aircraft's potential positional inaccuracy is IIRC greater than 0.2Km - I would need to ask Lee to confirm the figure.
Where MLAT data is NOT available - e.g. due to lack of 1090 receiver station coverage, or where the conditions in my earlier post above ^^^^^^ aren’t met, the system automatically reverts to reporting these aircraft as bearingless targets.
Hope this helps
Regards
Peter