Locator in database recorded wrong

4 posts / 0 new
Last post
OK1BIL
Offline
Last seen: 1 month 2 weeks ago
Joined: 2015/02/25 - 14:57
Locator in database recorded wrong

Hi,

I was looking at my spots past two days and found out there is a wrong locator constantly being recorded in the database:

2016-01-06 08:04 OK1BIL 10.140165 -19 -1 JN69ix 0.1 LA5GOA/RX2 JO29oi 1147 338
2016-01-06 08:04 OK1BIL 10.140176 -16 -1 JN69ix 0.1 GM4SFW IO77sn 1402 314
2016-01-06 08:04 OK1BIL 10.140171 -18 -1 JN69ix 0.1 LA3LJA JP53ej 1498 356
2016-01-06 08:00 OK1BIL 10.140165 -19 -1 JN69ix 0.1 LA5GOA/RX2 JO29oi 1147 338
2016-01-06 08:00 OK1BIL 10.140181 -23 -1 JN69ix 0.1 EA1FAQ IN71pn 1637 242
2016-01-06 08:00 OK1BIL 10.140175 -16 0 JN69ix 0.1 GM4SFW IO77sn 1402 314

After analyzing this in my head I found why this happened.

- WSPR transmits only 4-digit locator i.e. JN69 (TX locator)
- Receiving stations running WSJT on a PC report their own 6-digit locator over the internet (RX locator)
- It looks like that in order to artificially increase TX location precision, the database caches TX's locator reported over the internet during the time it was in RX period.
(Example: I am OK1BIL, during receiving period I report some stations and tell the WSPRnet I am in JN69IX, then I am in TX period sending out only JN69. The receiving station reports my callsign OK1BIL and my JN69 locator to WSPRnet. The WSPRnet looks into some caching table in DB and discovers I actually reported JN69IX previously when I was RX and uses this more accurate locator.)

Now my case where this does not work:

Few months ago I was /P with my KX3 and laptop and I was running WSPR software in JN69IX. At home in JN69QS I am running an Ultimate 3S device for WSPR, which is only TXing. I did not do any RX from my home in JN69QS, so the WSPRnet database is still using JN69IX for my reports - which is wrong.

Marek, OK1BIL