<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000099">
<br>
It doesn't take a lot to confuse me these days. OK I'll admit it.
I am confused by the list of stations Mike has copied below.<br>
<br>
I've checked for myself and that's more or less what the site is
delivering in real time at this moment. <br>
<br>
My station is one of those listed with today's date. It hasn't
been on HF APRS since I returned from our Flinders Ranges trip over
a couple of weeks ago: <br>
<br>
<a
href="http://aprs.fi/?call=vk5atn-15&mt=m&z=11&timerange=86400">http://aprs.fi/?call=vk5atn-15&mt=m&z=11&timerange=86400</a>
gives the true picture. It's in the shed with the HF rig off and
the 20 metre whip on the bar. (I just checked) <br>
<br>
So why is it appearing in the lists for today? And all of those
going back over the past day or so?<br>
<br>
Simple answers only please - type slowly ....... <br>
<br>
Puzzled 73<br>
Terry<br>
<br>
<br>
Date: Wed, 29 Jun 2011 13:37:07 +0200<br>
<blockquote
cite="mid:mailman.1439.1309357458.27360.ozaprs@aprs.net.au"
type="cite">
<pre wrap="">From: "Mike Zwingl oe3mzc" <a class="moz-txt-link-rfc2396E" href="mailto:oe3mzc@oevsv.at"><oe3mzc@oevsv.at></a>
Subject: [OZAPRS] QRG drift HF APRS
To: "Australian APRS Users" <a class="moz-txt-link-rfc2396E" href="mailto:ozaprs@aprs.net.au"><ozaprs@aprs.net.au></a>
Message-ID: <00ed01cc3650$e08f6800$cda8a8c0@WORKSTATION>
Content-Type: text/plain; charset="iso-8859-1"
see how all stations on 10Mhz are drifting offset in QRG:
<a class="moz-txt-link-freetext" href="http://aprs.fi/?c=raw&call=vk6uz-4">http://aprs.fi/?c=raw&call=vk6uz-4</a>
It is not the absolute but the relative value to each other that makes the problem in decoding hf-aprs sigs.
(values after callsigns is given in Hz)
2011-06-29 11:24:57 UTC: VK6UZ-4>APU25N,TCPIP*,qAC,T2AUST:=3211.17S/11604.17E&HF-IGATE 10147.6USB Perth
2011-06-29 11:29:01 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): WIDE1 +100, VK2GKA-15 +50, VK7BW-15 +50, VK8ZAB-4 +25
2011-06-29 11:29:02 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): VK4UN-4 +62, VK5ATN-15 +65, VK5LY-15 +43, VK4KWI-15 +75
2011-06-29 11:29:02 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): VK2AJ-15 +50, KF7EU-6 +25, ZS6SS-3 +62, VK2TV-4 +143
2011-06-29 11:29:02 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): VK3DHI-15 +68, VP8DEU +43, VK2DQC-15 +81, VK4DMI-4 +96
2011-06-29 11:29:02 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): VK4HW-15 +46, VK4VP-15 +25, DL8RCB-3 +100, IW2GOB-10 +100
2011-06-29 11:29:02 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): VK4KMR-15 +46, F5LDS-4 +112, VK2SX-15 +50, LA4FPA-15 +87
2011-06-29 11:29:02 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): VK7DIK-4 +40, VK3MY-4 +65, VK3BZQ-9 +37, VK5LY-4 +43
2011-06-29 11:29:02 UTC: VK6UZ-4>APRS,TCPIP*,qAC,T2AUST:>dF (Hz): VK4UN-15 +43, VK8LM +50, VK5LY-6 +50, VK3BDG-9 -18
</pre>
</blockquote>
<br>
</body>
</html>