Accessing State and Section Information in Clusters - n4af/TR4W GitHub Wiki
This page is to provide support information helpful in implementing full state multiplier support. The idea is that is the cluster provides state (and/or ARRl section info) in the spot record, we can use that in TR4W to guess if this is a multiplier for contests that use state as a mult. The same goes for contests that use ARRl section like SS. Of course, the station could be operating portable in another state or section, so if there is a valid mult in the spot comment, we let that override things.
Here is a summary of how to get the accessible information in various DX cluster servers.
#CC Cluster
##Enable State support
CC Cluster requires the user to turn on state displays in the system so each spot will have the state info if there. The way to do this is to enter set/usstate
##Spot Formats
DX de K5TDA-#: 7043.7 KA4EET CW 13 dB 17 WPM CQ FL 0036Z TX
DX de K7EG-#: 7029.6 KC6Z CW 07 dB 24 WPM CQ CA 0036Z WA
DX de WZ7I-#: 10148.4 W0PV RTTY 30 dB CQ FL 0036Z PA
DX de W8WTS-#: 3529.0 K1YAN CW 17 dB 18 WPM CQ MA 0036Z OH
DX de K9IMM-#: 7027.0 KB4GYT CW 10 dB 21 WPM CQ SC 0036Z WI
DX de K9IMM-#: 7030.6 N2EGA CW 37 dB 18 WPM CQ NJ 0036Z WI
The state is at the end of the comment record. The state of the SPOTTER is at the end of the record after the timestamp.
#AR Cluster
AR Cluster version 6 supports several very useful extensions.
##Enable State/Section Support
To enable state and/or sections display, enter set dx extension state section
. As this is only a version 6 command, you can also enter sh/version
to check the version of the AR software. This will return,
AR-Cluster version: 6.1.5123
Copyright (c) 1998 - 2014 AR-Technology de AB5K
##Spot Formats
DX de NO1D-#: 7028.0 N5DY CW 27 dB 27 WPM CQ OK-OK 0024Z
DX de N7TR-#: 7048.9 K4WAL CW 15 dB 16 WPM CQ FL-NFL 0024Z
DX de N7TR-#: 7028.0 N5DY CW 30 dB 28 WPM CQ OK-OK 0024Z
DX de SE0X-#: 3527.0 OK1RR CW 37 dB 25 WPM CQ 0024Z
DX de F5RRS-#: 3527.0 OK1RR CW 47 dB 24 WPM CQ 0024Z
In this reply, the state will always be first and then the section. This data is always added from position 30 and back int he spot. So if you only requested set dx state, the state record would be in positions 29 and 30. To process this data, it is important to look at position 30 and read backwards to detect a - or a + (the + indicates LOTW if the set dx extension lotw
command is used).
My thought for the way this works is that when we see NFL in the example above (assuming NFL), we run this call through the possible mults and highlight it accordingly in the bandmap. This really would be a killer application in SS so you can just see the ones you need to work. We have that in DX Contacts based on country derived from the prefix or zone so why not state or section.