Re: beaconspot

Richard
 

The last time this was flagged, tracing the spot back to where is get corrupted ended up with some Finnish
cluster s/w.
When the clusters in Europe were RF linked it was very easy to see where things went wrong.
But with internet linking its much harder, especially when duplicate paths exist between servers on different platforms.
Duplicate spots are removed, unless they have been changed,
Remember running a cluster server is a thankless task
Richard




On Wed, 2019-06-12 at 20:36 +0000, Dave - G4RQI wrote:

Hello Neil,

 

Thanks for the reply it will be interesting to see if can be resolved.

 

LEX and CAM are still audible on RS as I type this but not heard anything else tonight and certainly not any human activity.

 

73 David

Sent from Mail for Windows 10

 


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Neil Smith G4DBN <neil@...>
Sent: Wednesday, June 12, 2019 9:28:51 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
 


-- 
 Best wishes /73 
 Richard Bown
 
 Email : richard@...

 HTTP  :  http://www.g8jvm.com
 
 ######################################################################

 Ham Call: G8JVM . QRV: 50-432 MHz + Microwave 
 Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W
 QRV 6mtrs 200W, 4mtrs 150W, 2mtrs 300W, 70cms 200W, 
Microwave 1296MHz 140W, 2320MHz 100W & 10368MHz 5W
 OS: Linux Mint 19.1 x86_64 Tessa, on a Dell Inspiron N5030 laptop
 ######################################################################

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