SOTA
Re: SOTA
Can you be more specific? Do you mean it does not update correctly?
If so, maybe the connection to your cluster has timed out. Open up the cluster in a detached window, then the Connection (F3) tab, then Disconnect, then Connect. Does that help?
Doug - W7DRM
If so, maybe the connection to your cluster has timed out. Open up the cluster in a detached window, then the Connection (F3) tab, then Disconnect, then Connect. Does that help?
Doug - W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Gig Harbor, WA, USA
Re: SOTA
Thanks,
The cluster in F9 of the Log4Om occasionally falls behind the the actual cluster scroll in F3 of the connection page. So there may be a spot showing on the scroll that I'm not seeing because I'm watching f9 on the main page of Log4Om. It's not a big deal because a disconnect/reconnect of the cluster usually gets both in sync. I was just wondering if I was doing something wrong. I'm using no filters. I also have SOTAwatch 2 running simultaneously and sometimes I even have Sota Goat running on my ipad. Not much chance of missing a spot. hi hi Log4Om is a fantastic program and this is really a minor issue-just wondering
73 de gene
The cluster in F9 of the Log4Om occasionally falls behind the the actual cluster scroll in F3 of the connection page. So there may be a spot showing on the scroll that I'm not seeing because I'm watching f9 on the main page of Log4Om. It's not a big deal because a disconnect/reconnect of the cluster usually gets both in sync. I was just wondering if I was doing something wrong. I'm using no filters. I also have SOTAwatch 2 running simultaneously and sometimes I even have Sota Goat running on my ipad. Not much chance of missing a spot. hi hi Log4Om is a fantastic program and this is really a minor issue-just wondering
73 de gene
Re: SOTA
Hi Gene,
I just tried your setup, watching the Connection (F3) as the spots come in and they appear immediately on the Cluster tab (F9) on the main application window. I have been watching for 10 minutes and have not missed one. Double check your filter settings, especially the Custom tab, Spotter field. If you have say NA selected there, then those spots from non-NA spotter will be seen in the cluster list (Connection tab) but not show up on the cluster grid display.
Doug - W7DRM
I just tried your setup, watching the Connection (F3) as the spots come in and they appear immediately on the Cluster tab (F9) on the main application window. I have been watching for 10 minutes and have not missed one. Double check your filter settings, especially the Custom tab, Spotter field. If you have say NA selected there, then those spots from non-NA spotter will be seen in the cluster list (Connection tab) but not show up on the cluster grid display.
Doug - W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Gig Harbor, WA, USA
-
IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: SOTA
This could happens if Log4OM parser doesn't correctly reads the cluster spot.
Parsing cluster is a very hard task, because there is not a fixed spacing/well structured protocol, and everything is matter of interpretation, but to the date i've no reports of anomalies on that.
Can you check program log if this disalignment happens again please?
Parsing cluster is a very hard task, because there is not a fixed spacing/well structured protocol, and everything is matter of interpretation, but to the date i've no reports of anomalies on that.
Can you check program log if this disalignment happens again please?
Daniele Pistollato - IW3HMH
Re: SOTA
Daniele,
Most of the time f9 stays in sync with the SOTA cluster. Occasionally it goes out of sync and f9 falls behind the cluster or may fail to show a spot altogether. Sometimes doing a disconnect/connect solves the problem and sometimes not. Some days I can go all day without a problem and other days it seems to be a little more erratic. Since I keep SOTAWatch2 going 24/7 it's not an issue of missing a spot. It is just so much easier to click on the f9 spot and have it go into the log automatically as opposed to entering the QSO manually. I'm running windows 7 pro with a pretty powerful CPU and I have run the log with no other programs loaded and it doesn't seem to make a difference.
BTW I have been a ham for over 55 years and this is by far the best program dedicated to ham radio that I have ever used. Log4om is so much more than just a log program. It is a logger on STEROIDS!!
I will be making a contribution to the cause. Thanks so very much.
73 de gene w6jmp
Most of the time f9 stays in sync with the SOTA cluster. Occasionally it goes out of sync and f9 falls behind the cluster or may fail to show a spot altogether. Sometimes doing a disconnect/connect solves the problem and sometimes not. Some days I can go all day without a problem and other days it seems to be a little more erratic. Since I keep SOTAWatch2 going 24/7 it's not an issue of missing a spot. It is just so much easier to click on the f9 spot and have it go into the log automatically as opposed to entering the QSO manually. I'm running windows 7 pro with a pretty powerful CPU and I have run the log with no other programs loaded and it doesn't seem to make a difference.
BTW I have been a ham for over 55 years and this is by far the best program dedicated to ham radio that I have ever used. Log4om is so much more than just a log program. It is a logger on STEROIDS!!
I will be making a contribution to the cause. Thanks so very much.
73 de gene w6jmp
-
IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: SOTA
Thank you Gene,
i'm running Log4OM cluster on SOTA since 2 days without catching anything strange. I'll keep it running over the weekend, where activity is usually higher
Keep me informed about troubles
i'm running Log4OM cluster on SOTA since 2 days without catching anything strange. I'll keep it running over the weekend, where activity is usually higher
Keep me informed about troubles
Daniele Pistollato - IW3HMH
