Log4OM

A friend and I are running V1 and V2 concurrently and we are noticing that the cluster spot updates on V2 are anywhere from a few seconds to a couple of minutes slower than on V1, which itself is very quick to update. We are both logged into the VE7CC cluster.
Anyone else notice this and what might be the cause?

Version 2 is interrogating the incoming spots much more than version 1 to decipher a lot of information about award references and modes like the inevitable FT8 etc

Not only is it slower but when comparing V1 and V2 spots from the VE7CC cluster it often omits some spots showing on V1. This is happening when running V1 and V2 concurrently on one PC or on two separate PCs. I have identical Configuration setups on both PC' running V1 and V2. Shutting down V1 makes no difference. V2 still skipping some spots.

Bob,

This will not likely make any difference, but if you are using multiple instances of the same login (call sign) to the VE7CC cluster, but sure you have different SSIDs for each login.

Sometimes the same login will cause hiccups.

You may already be doing this, but I can tell from your messages.

Here is a link to Lee Sawkins' site with an explanation of the use of SSIDs.

http://www.bcdxc.org/ve7cc/ssid.htm

Want to add I have not been able to add two SSID instances (to same cluster) in Log4OM without making one instance host name in uppercase and one in lower case.

Log4OM does not seem to save based on the User Friendly name or callsign with SSID but must be host. So if you setup a second SSID using the same host-name regardless of SSID it overwrites the first.

I only found out that I needed to do a VE7CC.NET and ve7cc.net by mistake.

Yes, I can understand how that might work. However as I mentioned in the last sentence that even with V1 shut down V2 is still skipping spots. How do I know? I am in Virginia and my brother W7CQQ is in Arizona. We are both connected to VE7CC while I am using only V1 and he is using only V2. We are both on the telephone talking to each other while watching the spots coming in on the cluster here on V1 and in Arizona on V2 and can see that we are both observing skipped spots on his V2 cluster panel. We are seeing the same spots being skipped. Reversing the situation with me on V2 and him on V1 we see the same thing happening. So the notion of having two connections with the same SSID from one call sign doesn't seem to play into this issue unless I'm mistaken. I hope I have explained our observations clearly.

I'm still noticing that there is a significant delay in the Cluster recognizing my status with the spot. If I worked B4 and takes a minute is obvious. Just now I realized why perhaps I my Cluster Alerts work sometime, and not good othertimes. In looking just now I saw new ATNO E44CC Palestine show at first in my color Green as Confirmed, only to Change to Yellow as NOT CONFIRMED. It corrected itself in a few seconds, but as a result I didn't get any Alert for my new one. Just hopefully a helpful hint to the great gang making my Log4OM the best. Tnx, 73, Herb WB8ASI

Is anyone besides me experiencing the issue of slow cluster updates and found a cure? Not only is V2 slower than Version 1 but it misses some spots entirely. I can see this with just log4om V2 connected to the VE7CC cluster and V1 shut down completely, i.e., only my V2 PC is connected to the VE7CC cluster. When I connect my V1 PC to the VE7CC cluster I can see V1 updating spots every two or three seconds while V2 was updating spots about every few minutes, and skipping over some cluster spots.

Revelation! As I previously described it, while watching cluster (VE7CC-1(23)) spot updates on the main logging display under Cluster (F8) the cluster spots come very infrequently and most spots are not seen. However, if I click on Connect>Telnet cluster>Cluster management>Cluster it then display a full page of the most recent spots and continues to update at a fairly rapid pace. Not so the cluster display (F8 tab)on the main logging page. Furthermore, if I click on one of the spots on the full page of spots as I describe above it jumps back to the cluster spots page on the logging page under Cluster (F8) and displays only that spot on that page. Why is this?

Sounds like you might have some filters set on the F8 cluster which are excluding some of the spots. Herb WB8ASI