Using the SPOT feature yields weird residual

Post Reply
User avatar
ng7v
Advanced Class
Posts: 36
Joined: 10 May 2022, 20:55
Location: DN13so, Meridian ID
Contact:

Using the SPOT feature yields weird residual

Post by ng7v »

Hello

I issued two spots of W5TEN and one other on 1AOC. Today, I noticed that these spots get re-sent whenever I start log4OM2. I saw a broken spot for a call in my club log window for a call sign "5TEN 3" from a spotter with callsign "G7V" with the same spot comment as the last time I sent it which was the source gridsquare (mine) and the destination gridsquare (his). It really surprise me because my pan adapter overlay displayed the spot.

I brought up the app again and captured this log output from the cluster management window. I clearly see the set of spots that are sent out to my primary cluster connection. All of them went out but the last one was the only one that ve7cc captured and propagated. It seems that spots that are issued out of the app do not get removed from whatever list or database that persists between application runs.

I do get the last two spots dated 7/30 and 7/31 on freq 10112, I issued those for sure but I do not get the ones above them dated 7/29 because I never sent them, the first of the two spots on 7/28 was mine (wrong spotter call sign). The rest of the 1AOC spots were spots that I recall seeing when someone was having difficulty figuring out the split frequency.

Total weirdness...

This is the cluster Log I captured this morning.

Code: Select all

1521 cluster.sota.org.uk:7300:   Welcome to the MM0FMF SOTA Cluster
1521 cluster.sota.org.uk:7300:   This is version 7.00 built 26th October 2022
1521 cluster.sota.org.uk:7300:   Set your keepalive pings to no less than 15mins
1521 cluster.sota.org.uk:7300:   login:
1521 cluster.sota.org.uk:7300:   -> NG7V
1521 ve7cc.net:23:   *** Connected to VE7CC-1:
1521 hamalert.org:7300:   HamAlert Telnet/Cluster emulation server
1521 cluster.sota.org.uk:7300:   -> NG7V
1521 ve7cc.net:23:   Greetings from the VE7CC-1 cluster.
1521 hamalert.org:7300:   login:
1521 ve7cc.net:23:   Located near Vancouver BC
1521 hamalert.org:7300:   -> NG7V
1521 ve7cc.net:23:   To see FT8 spots you MUST enter SET/FT8
1521 ve7cc.net:23:   To see Skimmer spots you must SET/SKIMMER
1521 ve7cc.net:23:   To turn OFF RBN CW Spots enter SET/NOCW
1521 ve7cc.net:23:   Running CC Cluster software version 3.372
1521 ve7cc.net:23:   *************************************************************************
1521 ve7cc.net:23:   *                                                                       *
1521 ve7cc.net:23:   *     Please login with a callsign indicating your correct country      *
1521 ve7cc.net:23:   *                          Portable calls are ok.                       *
1521 ve7cc.net:23:   *                                                                       *
1521 ve7cc.net:23:   *************************************************************************
1521 ve7cc.net:23:   New commands:
1521 ve7cc.net:23:   set/skimmer   turns on Skimmer spots.
1521 ve7cc.net:23:   set/noskimmer turns off Skimmer spots.
1521 ve7cc.net:23:   set/noft8     turns off FT8 spots.
1521 ve7cc.net:23:   set/ft8       turns on  FT8 spots.
1521 ve7cc.net:23:   set/noft8     turns off FT8 spots.
1521 ve7cc.net:23:   set/ft4       turns on  FT4 spots.
1521 ve7cc.net:23:   set/own       turns on all spots for own call.
1521 ve7cc.net:23:   unset/own     turns off spots for own call.
1521 ve7cc.net:23:   set/nobeacon  turns off spots for beacons.
1521 ve7cc.net:23:   set/beacon    turns them back on.
1521 ve7cc.net:23:   For information on CC Cluster software see:
1521 ve7cc.net:23:   http://bcdxc.org/ve7cc/ccc/CCC_Commands.htm
1521 ve7cc.net:23:   AR User program now at ver. 2.447
1521 ve7cc.net:23:   Please enter your call:
1521 ve7cc.net:23:   login:
1521 ve7cc.net:23:   -> NG7V
1521 cluster.sota.org.uk:7300:   -> SH/DX 30
1521 hamalert.org:7300:   -> ew6wYX
1521 ve7cc.net:23:   -> NG7V
1521 hamalert.org:7300:   -> SH/DX 30
1521 ve7cc.net:23:   -> SH/MYDX 30
1521 ve7cc.net:23:   NG7V
1521 ve7cc.net:23:   Hello Ronald Poulin.
1521 ve7cc.net:23:   **************************************************************************
1521 ve7cc.net:23:   If you do not wish to see DX spots for your own call enter UNSET/OWN
1521 ve7cc.net:23:   **************************************************************************
1521 ve7cc.net:23:   Cluster: 325 nodes  1222 Locals  6384 Total users   Uptime  31 days 10:03
1521 ve7cc.net:23:   Date        Hour   SFI   A   K Forecast                               Logger
1521 ve7cc.net:23:   31-Jul-2023   12   174   9   2 Minor w/S1 R1 -> Minor w/R1           <AE5E>
1521 ve7cc.net:23:   31-Jul-2023   15   174   9   2 Minor w/S1 R1 -> Minor w/G1 R1        <W0MU>
1521 ve7cc.net:23:   NG7V de VE7CC-1 31-Jul-2023 1521Z   CCC >
1521 ve7cc.net:23:   NG7V de VE7CC-1 31-Jul-2023 1521Z   CCC >
1521 ve7cc.net:23:   NG7V command error
1521 ve7cc.net:23:   NG7V de VE7CC-1 31-Jul-2023 1521Z   CCC >
1521 ve7cc.net:23:   Search ended 24-Jul-2023 2140Z
1521 ve7cc.net:23:   10104.0  1A0C        28-Jul-2023 0124Z  up 1.5                    <NG7M>
1521 ve7cc.net:23:   10104.0  1A0C        28-Jul-2023 0317Z  TU up 2                   <N7RD>
1521 ve7cc.net:23:   10104.0  1A0C        29-Jul-2023 0306Z                            <KN7T>
1521 ve7cc.net:23:   10106.0  1A0C        29-Jul-2023 0353Z  light                     <VE7VQ>
1521 ve7cc.net:23:   10104.0  1A0C        29-Jul-2023 0355Z  SRY UP 2                  <VE7VQ>
1521 ve7cc.net:23:   10104.0  1A0C        29-Jul-2023 0419Z  QRV agn CQ UP             <W7VS>
1521 ve7cc.net:23:   10112.0  W5TEN       30-Jul-2023 0105Z  carmine tx 599 in boise   <NG7V>
1521 ve7cc.net:23:   10112.0  W5TEN       31-Jul-2023 1503Z  CW DN13so -> EM10pd       <NG7V>
1521 ve7cc.net:23:   NG7V de VE7CC-1 31-Jul-2023 1521Z   CCC >
Ron (NG7V)
User avatar
G4POP
Log4OM Alpha Team
Posts: 11592
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Using the SPOT feature yields weird residual

Post by G4POP »

Try changing the ve7cc set up in log4om telnet to sh/dx/3, I think your initial login command is just receiving old spots because it's asking for too many spots.

Check the spot times you will see what I mean
73 Terry G4POP
User avatar
ng7v
Advanced Class
Posts: 36
Joined: 10 May 2022, 20:55
Location: DN13so, Meridian ID
Contact:

Re: Using the SPOT feature yields weird residual

Post by ng7v »

Thank you Terry. Actually SHow/MYDX defaults to the last 30 filtered spots on the cluster. I have a filter registered with the cluster. I set it to the default and it went away. The reason it didn't work is that my syntax was wrong:

SH/MYDX 30 means show me the last 30 spots on the 30 meter band and it did because the 30 meter band has been quiet lately specially in the Pacific North West.

What I should have had was SH/MYDX/30 which is show me the last 30 spots on any band.

That is what I specified in my new syntax using the default value of 30. It's just a fluke that 30m has been in poor shape lately.

Thank you for helping me sort this out.

73
Ron (NG7V)
Post Reply