Re: beaconspot

Nicholas Shaxted
 

Hi Neil and Dave

I have just reviewed the cluster messaging for an entry from DL7VTX earlier this evening.

He also added a spot which reported the same issue.

The first entry is the correct entry (877) and GB3UJS and ON4KST seem to be involved, along with an IP

The second entry is incorrect (880) and seems to have GB3RDX and ON4KST involved.

 

Therefore, very tentatively, I would start to look a little closer at GB3RDX and its route.

 

CC11^10368877.0^OE1XGA/B^12-Jun-2019^2008^51s jn88eu - jo62tm^DL7VTX^24^GB7UJS^ON4KST-2^28^15^28^14^^^OE^DL^JN88^JO62^^2^48.5/-17^178.33.224.102^ (GB7DXS)

 

CC11^10368880.0^OE1XGA/B^12-Jun-2019^2008^51s jn88eu - jo62tm^DL7VTX^98^GB7RDX^ON4KST-2^28^15^28^14^^^OE^DL^JN88^JO62^^2^48.5/-17^^ (GB7DXS)

 

 

73

Nick – g4ogi

 

 

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Neil Smith G4DBN via Groups.Io
Sent: Wednesday, June 12, 2019 9:29 PM
To: UKMicrowaves@groups.io
Subject: Re: [UKMicrowaves] beaconspot

 

 

I just checked on one cluster on the web and it is even worse, truncating to the nearest MEGAHERTZ when you search. I’ll drop the author a line as I know who writes this one!

Neil G4DBN


2019-06-12 19:00:00       G4RQI   10369000             GB3LEX/B            IO92IQ(RS)IO93IR 55
2019-06-12 19:00:00       G4RQI   10369000             GB3LEX/B            IO92IQ(RS)IO93IR 55
2019-06-10 22:23:00       G4DBN 10369000             GB3LEX/B            IO92IQ<RS>IO93NR 55s SCP JO02B
2019-06-10 22:23:00       G4DBN 10369000             GB3LEX/B            IO92IQ<RS>IO93NR 55s SCP JO02B
2019-06-10 22:15:00       G4BAO 10369000             GB3LEX <rs>55S
2019-06-10 22:15:00       G4BAO 10369000             GB3LEX <rs>55S
2019-06-10 11:58:00       G4BAO 10369000             GB3LEX <rs> 52S
2019-06-10 11:58:00       G4BAO 10369000             GB3LEX <rs> 52S
2019-06-10 11:37:00       G0API   10369000             GB3LEX/B            IO92IQ(TR)IO80XS 419

 



On 12 Jun 2019, at 21:20, Neil Smith G4DBN <neil@...> wrote:

 

Some cluster software has a bug and truncates the precision, so when the originating cluster node sees the spot being looped back, instead of ignoring it, it thinks it is a new spot and displays it.  Only happens on certain beacons of course, depends on the frequency you spot.  If it is within X Hz of the boundary of a 10kHz increment, it is suppressed.  Not sure whose software is responsible, but a lot of authors didn’t realise anything existed above VHF.  Some cluster code chopped off the “10” from 10368.120 and the spot appeared as 368.120 with the digits “10” appended to the callsign.  That was fixed a while back, but the broken software which truncates the precision is still very prevalent.

 

I did try dropping Dirk a line to see if he had any ideas, but we really need to identify which software is doing it.

 

Neil G4DBN



On 12 Jun 2019, at 20:15, Dave - G4RQI <io93ir@...> wrote:

 

Hello...

 

I’m sorry if this has been answered before... I have posted a couple of 3cm beacon spots this evening using https://www.beaconspot.uk/beaconsp.php but when I do the spot appears twice on the DxCluster. The frequency is correct for one of the spots but 5Khz is added to the 2nd spot. Does anyone know why?

 

73 David

Sent from Mail for Windows 10

 

 

 

Join UKMicrowaves@groups.io to automatically receive all group messages.