ClubLog Integration and Multiple Callsigns

Support
1

I am experiencing unexpected behavior from a trigger and think the cause may be from using multiple callsigns with ClubLog band slots.

The first question I should ask is whether the ClubLog band slot criteria queries each of multiple callsigns and unions their QSOs together together to determine whether or not to trigger, or does any one ClubLog callsign activate the trigger?

Here is the scenario and what I’m seeing:

  • I have two callsigns WQ9N and KC1ACY that have significant dx activity.
  • I put both of them into the callsign field for the ClubLog band slot filter because it’s not helpful to me to trigger for countries I have already worked on my first callsign.
  • I received triggers for Australia on 40m, despite having many prior QSOs. I checked DXCC and noticed that the confirmed QSOs for Australia on 40m were all from my older callsign. This made me suspect that multiple callsigns were not working as expected.

Any advice here would be appreciated.

2

The “Band slots” condition supports one callsign only (i.e. you cannot enter multiple callsigns separated with commas or spaces, or undefined operation will result). This is the callsign that Club Log will be queried against.

If you have worked DXCC band slots under multiple different callsigns and are only interested in alerts for those that you have not worked at all (regardless of which callsign you used), then unfortunately the “band slots” condition will not work for you. You may have to resort to manually curating triggers for your missing band slots, e.g. by creating one trigger per band, with a band condition and a DXCC condition for those DXCCs that you are missing on that band.