Log4OM

G4POP wrote: 14 Apr 2020, 19:41 Then you will need either to send a filter to the cluster to exclude those frequencies or edit the Log4OM bandplan_r1.xml bandplan

Thanks Terry,
unfortunately it wont work either.
I modified the R1 file with no success. I also tried modifing the remaining xml files to correctly identify the frequency range for FT but with no success.
VE7CC filter let some FT8/FT4 spots pass by, and the filter for a portion of the band is not working.
This cluster behaviour is annoying 'cause I spend most of my time chasing CW DX on 30mt and the FT8, wrongly identified as CW drives me nut

Max IU4JNR

Max
FT8 is a major issue and has caused all developers a lot of hard work trying to remove it from clusters, like you I am mostly interested in CW so I share your problem.

G4POP wrote: 15 Apr 2020, 06:55 Max
FT8 is a major issue and has caused all developers a lot of hard work trying to remove it from clusters, like you I am mostly interested in CW so I share your problem.

thanks Terry,
the only DXCluster software that i know that has a great filter is HamRadioDeluxe in his free version. It is widely customizable. For example, the user can cut slices of bands to his need.
This is what i would like on the LOG4OM cluster.
Best,
Max IU4JNR

G4POP wrote: 14 Apr 2020, 19:41 Then you will need either to send a filter to the cluster to exclude those frequencies or edit the Log4OM bandplan_r1.xml bandplan

Terry, thanks to your hint i'm now happy with the cluster .
I modified all the xml files (r1-r3) to have the FT8/FT4 falls into the digital window and no more unwanted spots in the cw window. Thank you.
Max IU4JNR