Log4OM

An option to filter out no LoTW users from the cluster display.

73 de Vince, VA3VF

va3vf wrote: 16 Feb 2022, 21:16 An option to filter out no LoTW users from the cluster display.

73 de Vince, VA3VF

Vince,

If you happen to use a cluster (such as ve7cc-1) you can filter the feed via the CC User APP. Actually any cluster that you can control via CC User has this option.

Under the "Set" dropdown Lee has an option called: "Reject All Except LoTW"

Then only the items so filtered will appear in the cluster in L4OM V2.

Quite efficient and would be far less processing/RAM work in L4OM V2.

I can't speak for other clusters that can't be managed by an APP such as CC User, but I would guess they would also have 'set' commands that can be entered.

KI5IO wrote: 19 Feb 2022, 02:02

va3vf wrote: 16 Feb 2022, 21:16 An option to filter out no LoTW users from the cluster display.

73 de Vince, VA3VF

Vince,

If you happen to use a cluster (such as ve7cc-1) you can filter the feed via the CC User APP. Actually any cluster that you can control via CC User has this option.

Under the "Set" dropdown Lee has an option called: "Reject All Except LoTW"

Then only the items so filtered will appear in the cluster in L4OM V2.

Quite efficient and would be far less processing/RAM work in L4OM V2.

I can't speak for other clusters that can't be managed by an APP such as CC User, but I would guess they would also have 'set' commands that can be entered.

Also note that in the L4OM V2 Cluster Tab View when the cluster time is coloured red it indicates it is an LOTW user.

See Page 70 of the "current" User Guide.

KI5IO wrote: 19 Feb 2022, 02:27

KI5IO wrote: 19 Feb 2022, 02:02

va3vf wrote: 16 Feb 2022, 21:16 An option to filter out no LoTW users from the cluster display.

73 de Vince, VA3VF

Vince,

If you happen to use a cluster (such as ve7cc-1) you can filter the feed via the CC User APP. Actually any cluster that you can control via CC User has this option.

Under the "Set" dropdown Lee has an option called: "Reject All Except LoTW"

Then only the items so filtered will appear in the cluster in L4OM V2.

Quite efficient and would be far less processing/RAM work in L4OM V2.

I can't speak for other clusters that can't be managed by an APP such as CC User, but I would guess they would also have 'set' commands that can be entered.

Also note that in the L4OM V2 Cluster Tab View when the cluster time is coloured red it indicates it is an LOTW user.

See Page 70 of the "current" User Guide.

Hi,

Thank you very much for getting back.

Regarding the cluster time being coloured red, I knew that, but I still suggest it would be a nice option to filter out the non LoTW users in Log4OM, just like the option to filter out FT(x) modes.

As for using CC-User to configure a CC-Cluster...That's what I use, but to the best of my observation, the option you mention only filters out the non LoTW users on the CC-User display. The setting does not filter out the non LoTW user at the cluster, and therefore those spots continue to be sent to Log4OM.

I just tried again, I'm rejecting all non LoTW users in CC-User, but those spots are still being sent to Log4OM by the cluster.

I only have one connection to the cluster at a time, I do not keep CC-User and Log4OM connected to the cluster simultaneously.

Thanks and 73.

Vince, VA3VF

KI5IO wrote: 19 Feb 2022, 02:02 Quite efficient and would be far less processing/RAM work in L4OM V2.

For FT8 users, reducing the torrent of FT8 spots is a must. Log4OM cannot handle 200+ spots per minute.

Using CC-User, I set VE7CC to only send me spots originating from US areas 1,2,3, and 9. In addition to that, I reject spots for the least wanted 50 entities. Now I see 10 spots per minute tops.

Back to filtering non LoTW users at the cluster - but as I said in my previous post, it does not seem to work for me with VE7CC - the one other reason to do it in Log4OM is to easily switch between the two settings.

Accepting spots from non LoTW users is a must for DXpeditions, as many will not be setup in LoTW until after the DXpedition is complete.

73 de Vince, VA3VF