[Dx4win] Spot irregularity

[Kris Mraz]

Dean,

The patterns are in the on-line help.

Quote:
When data is received from the TNC it is converted to upper case and 
each line is tested to see if it matches any of the four patterns. If 
a match is found, the DX spot is added to the DX Spotting window in the 
current sort order.

By default, the following four patterns are defined:

No	specification	        comments
1	DX|DE|r:|f|c|q|tZ	format of a regular spot
2	f|c|d|tZ|q|<r>	        format for SH/DX
3	r|f|c|q|<t|d>	        format for HTTP
4	DX|c|f|q	        format send to cluster

All characters have to match exactly as specified. Some characters have 
a special meaning:

char	interpretation
c	callsign of DX
f	frequency
q	all other fields combined. May contain QSX, WKD, etc. followed by 
        a frequency
r	callsign of station reporting the spot
t	time
#	single digit
|	one or more blanks

Unquote.

The "d" above isn't defined but its the date field.

Here's my guess at what's happening. Note that the time field pattern
is tZ. I think it sees the Z of AZ and thinks this is the Z of the time
field. It then assumes the A is the time info. Since "A" is an invalid 
time field it doesn't display the spot. Make sense?

I get these spots with the state appended but never noticed if the AZ
spots are displayed properly or not.

Kris N5KM