[Dxspider-support] Bug in sh/dx command
Andy Cook, G4PIQ
g4piq at btinternet.com
Tue Aug 19 12:59:10 BST 2003
Running 1.51 57.253, but this bug was also present in the previous release
that we were running (1.49 something I think).
Spots made locally whose frequency end in .0 do not show when you do a sh/dx
on [band].
For example
sh/dx by g4swx shows.....
144090.0 S50C 18-Aug-2003 1832Z jn76>jo02 51a qtf080 only si
<G4SWX>
144071.0 I2FAK 18-Aug-2003 1659Z new qrd 59A in JO02
<G4SWX>
144058.0 I2FAK 18-Aug-2003 1656Z jn45>jo02 59A
<G4SWX>
144260.0 G4DEZ 16-Aug-2003 2046Z HE IS A LIGHTHOUSE RUNNING
<G4SWX>
144306.0 EW6FS 22-Jul-2003 2005Z ko35>jo02 es hrd 59
<G4SWX>
144054.0 RA3AQ 22-Jul-2003 1951Z 419 hrd in JO02
<G4SWX>
144292.0 UA3WM 22-Jul-2003 1704Z ko72>jo02 es
<G4SWX>
144300.0 UT5ER 22-Jul-2003 1704Z kn78>jo02 es
<G4SWX>
144295.7 UR5LX 22-Jul-2003 1656Z Only G and PA/DL/ON calls !!
<G4SWX>
144296.0 UR5LX 22-Jul-2003 1653Z ko70>jo02 calling G
<G4SWX>
Just to complicate things the 4th spot down (G4DEZ) is actually a fake spot
coming from K1TTT - that's why it shows up below!
sh/dx by g4swx on 2m shows
144260.0 G4DEZ 16-Aug-2003 2046Z HE IS A LIGHTHOUSE RUNNING
<G4SWX>
144295.7 UR5LX 22-Jul-2003 1656Z Only G and PA/DL/ON calls !!
<G4SWX>
rcmd/gb7djk sh/dx by g4swx on 2m shows
GB7DJK:144090.0 S50C 18-Aug-2003 1832Z jn76>jo02 51a qtf080 only si
<G4SWX>
GB7DJK:144071.0 I2FAK 18-Aug-2003 1659Z new qrd 59A in JO02
<G4SWX>
GB7DJK:144058.0 I2FAK 18-Aug-2003 1656Z jn45>jo02 59A
<G4SWX>
GB7DJK:144260.0 G4DEZ 16-Aug-2003 2046Z HE IS A LIGHTHOUSE RUNNING
<G4SWX>
GB7DJK:144306.0 EW6FS 22-Jul-2003 2005Z ko35>jo02 es hrd 59
<G4SWX>
GB7DJK:144054.0 RA3AQ 22-Jul-2003 1952Z 419 hrd in JO02
<G4SWX>
GB7DJK:144292.0 UA3WM 22-Jul-2003 1704Z ko72>jo02 es
<G4SWX>
GB7DJK:144300.0 UT5ER 22-Jul-2003 1704Z kn78>jo02 es
<G4SWX>
GB7DJK:144295.7 UR5LX 22-Jul-2003 1656Z Only G and PA/DL/ON calls !!
<G4SWX>
GB7DJK:144296.0 UR5LX 22-Jul-2003 1653Z ko70>jo02 calling G
<G4SWX>
This is repeatable for a plain sh/dx on 2m command (without the callsign
qualifier) and also on other bands.
Maybe the frequency info in the local spot database is getting written
differently when doing a DX command to dealing with an incoming PC11?
Andy, G4PIQ @ GB7MRS
More information about the Dxspider-support
mailing list