Cluster Connections

Post Reply
KD0Q
Novice Class
Posts: 27
Joined: 06 Nov 2015, 13:04

Cluster Connections

Post by KD0Q » 14 Feb 2020, 13:54

I often lose my cluster connection due to my unreliable internet service. Is there a keep alive mechanism? How about an auto reconnect feature? I didn't see anything in the configuration or docs.

I use ve7cc user to connect to a cluster because auto reconnect works well and I connect log4om to that for DX spots. This works fine except for sending spots. I can send spots directly to a cluster but not via ve7cc user. With log4om v1 I can send spots via ve7cc user. Is there a configuration I need to add?

Thanks, Glenn - KD0Q

User avatar
kd0zv
Old Man
Posts: 471
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Cluster Connections

Post by kd0zv » 14 Feb 2020, 13:58

Glen,

When you edit your clusters there is a keep alive function in there.

Are you saying you cant send spots with CC User but you can Log4OM? That is strange.

One thing to note. Anytime you edit a cluster in your known servers list you need to remove it from active servers on bottom and re-add it. Because at this time the edits are not reflected if its already in the bottom box.

Rich
Log4OM Version 2.3.0
Windows 10/64
Flex 6600 via OmniRig
CW Skimmer localhost

KD0Q
Novice Class
Posts: 27
Joined: 06 Nov 2015, 13:04

Re: Cluster Connections

Post by KD0Q » 15 Feb 2020, 00:29

Thanks Rich,

OK, I see the keep alive checkbox. Keep alive is not sufficient in my environment, I need auto reconnect as I occasionally get a Winsock error and the socket gets dropped. Ve7cc user does that so I make a connection from log4om using 127.0.0.1 port 7300 to ve7cc user. Worked great on log4om v1.

Sending spots is an issue from log4om v2 when using a connection to the local ve7cc user app. I can send a spot from ve7cc user. I can send a spot from log4om v1 via ve7cc user. I can send a spot to the same cluster from log4om v2 when connected directly. But I can't send a spot with log4om v2 via ve7cc user.

RR on the re-add after edit.

Glenn

User avatar
kd0zv
Old Man
Posts: 471
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Cluster Connections

Post by kd0zv » 15 Feb 2020, 03:20

Pretty sure you can telnet to cc user just like we did in V1. No luck with that?

You mean the big city of Traer has internet issues? :shock: I am in Ankeny.
Log4OM Version 2.3.0
Windows 10/64
Flex 6600 via OmniRig
CW Skimmer localhost

KD0Q
Novice Class
Posts: 27
Joined: 06 Nov 2015, 13:04

Re: Cluster Connections

Post by KD0Q » 15 Feb 2020, 13:16

That's what I thought too. Sending a spot via ve7cc works with V1, doesn't with V2.

Actually, I'm 5 miles west of Traer out in the country and Internet is over a wireless link.

Glenn

User avatar
DF5WW
Log4OM Alpha Team
Posts: 1235
Joined: 02 May 2013, 09:49
Location: Kraam, Rhineland Palatinate, Germany

Re: Cluster Connections

Post by DF5WW » 15 Feb 2020, 16:13

Question ... did this cluster need a login to spot ? If so you have to set a call/password or it won´t
work. You can do this in the telnet window. If you use more than 1 cluster it could be possible that
the primary cluster [PRI] needs a login. The primary cluster is the way to send spots. So only an idea.

On my side all is fine whith sending spots.
73´s .. Juergen ... ALT-512 SDR (10W) , 2 x 6,5 mtr. indoor wire at CG-3000 autotuner ...

KD0Q
Novice Class
Posts: 27
Joined: 06 Nov 2015, 13:04

Re: Cluster Connections

Post by KD0Q » 17 Feb 2020, 23:06

No login required. Only connected to 1 cluster - the local ve7cc user app. This works fine with Log4OM v1 but not v2.

Following is the scenario with info from the V2 Realtime Log.:

Create a custom cluster server for the local ve7cc app and save it.

[FormClusterManagement] : Saving cluster information 127.0.0.1:7300

From cluster_user.xml file:

<SingleCluster>
<ClusterName>local VE7CC User</ClusterName>
<HostAddress>127.0.0.1</HostAddress>
<Port>7300</Port>
<IsPrimary>false</IsPrimary>
<KeepAlive>true</KeepAlive>
<Commands>
<string>// use &lt;callsign&gt; command to send your callsign to the server.</string>
<string>&lt;CALLSIGN&gt;</string>
<string>&lt;PASSWORD&gt;</string>
<string>SH/DX 30</string>
</Commands>
<Callsign>KD0Q</Callsign>
<Password />
<Ssid>-10</Ssid>
<ClusterStatus>UserDefined</ClusterStatus>
</SingleCluster>

Add it as the only active server and connect:

[ClusterManagement] : Connecting cluster(s)...
[TelnetConnection] : 127.0.0.1:7300 Connecting to 127.0.0.1:7300
[TelnetConnection] : 127.0.0.1:7300 Telnet connection opened
[TelnetConnection] : 127.0.0.1:7300 IS PRIMARY
[ClusterManagement] : 127.0.0.1:7300 Cluster Login started

[ClusterManagement] : 127.0.0.1:7300 Cluster Login completed

Everything is fine so far, getting DX spots.

Here's what I see when sending a spot:

[ClusterManagement][SendMessage] : No primary telnet connection found for outbound messages

Any ideas?

Glenn

User avatar
W7DRM
Log4OM Alpha Team
Posts: 732
Joined: 19 Feb 2014, 19:44

Re: Cluster Connections

Post by W7DRM » 18 Feb 2020, 08:27

Please, read the FAQ on submitting reports. We need basic data, version #, OS, etc.

Doug - W7DRM

KD0Q
Novice Class
Posts: 27
Joined: 06 Nov 2015, 13:04

Re: Cluster Connections

Post by KD0Q » 18 Feb 2020, 12:49

Log4OM v2.3.0.0
Windows 10 Pro v1903
CC User v2.4481

User avatar
G4POP
Log4OM Alpha Team
Posts: 6365
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Cluster Connections

Post by G4POP » 18 Feb 2020, 12:54

As far as I know we are not able to send spots by interaction to Cc user on the local pc, only to normal on line cluster servers.

I can't recall why but I am sure if it were possible Lele would have provided the opportunity
73 Terry G4POP

Post Reply