Log4OM

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

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

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

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? I am in Ankeny.

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

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.

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

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

Doug - W7DRM

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

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