Actually, I was wrong, it was this I was trying to follow. Upgrade rather than Update as it is an existing station. Not sure what the difference is?
http://pilotaware.lode.co.uk/downloads/OGN/README.upgrade
I ran this anyway and got no errors. I wonder if it still works!
$ cd rtlsdr-ogn
$ ./PilotAware-OGN.update.sh
Hi Ian,
a number of methods, firstly monitor communications to/from the OGN APRS Servers
(from the PI)
$ telnet localhost 50001
The above will monitor the OGN Decoder talking to the APRS servers, errors will be displayed if there are issues, the interrogation time is 300seconds, so you probably need to run for over 5 minutes
$ telnet localhost 50002
As per OGN Decoder, except this is the PAW decoder, there is an initial latency of 5 minutes (it listens to the OGN Decoder), it then talks to the APRS servers every 5 minutes
Also you can look on the APRS Servers to see if your station is listed, ie Thame and PWThame
http://wiki.glidernet.org/aprs-server-listedit:
OK, I am seeing something weird, I am seeing stations called
THAME 78.32.242.250:34582
THAME 78.32.242.250:50326
THAME 78.32.242.250:62392
Thame 143.159.81.27:33498
PWThame 143.159.81.27:33506
That is unexpected on my part !
I would only expect to see Thame, PWThame
Thx
Lee