[WT-support] Mode code on .EDI VHF logs

[Claudio Veroli]

Hi all
we are using WT for VHF contests logging (ver 4.17) . 
In the .edi  REG1TEST exports the QSO mode code (ex. 1=SSB, 2=CW) is not formatted. 
There is always a blank. 
This is a problem for many check log programs e we need to fill this info manually. 

Is it possible to fix the problem in next versions of WT?.  

73 de Claudio I4VEQ

Here is a short table of the .edi REG1TEST  file requirments:
   
All fields in the QSO record is written on the same line, and ending with ASCII characters 13 and 10 (CR LF). 

Field Maximum length 
Date = YYMMDD, 6 characters 6 
Time = UTC, 4 characters, with leading zeros 4 
Call = 3 to 14 characters 14 
Mode code = 0 or 1 character 1 
Sent-RST = 0 or 2 or 3 characters 3 
Sent QSO number = 0 or 3 or 4 characters, with leading zeros 4 
Received-RST = 0 or 2 or 3 characters 3 
Received QSO number = 0 or 3 or 4 characters, with leading zeros 4 
Received Exchange = 0 or 1 to 6 characters (see also PExch) 6 
Received WWL = 0 or 4 or 6 characters, World Wide Locator 6 
QSO points = 1 to 6 characters, including bandmultiplier 6 
New-Exchange = 0 or 1 character, "N" if QSO is a new exchange 1 
New-WWL = 0 or 1 character, "N" if QSO is a new WWL 1 
New-DXCC = 0 or 1 character, "N" if QSO is a new DXCCL 1 
Duplicate-QSO = 0 or 1 character, "D" if contact is a duplicate QSO 1 

Mode code 
The mode code is used to show which modes were used for the QSO. Below is a list of the code with corresponding modes. 

Mode code TX mode RX mode 
0 non of below non of below 
1 SSB SSB 
2 CW CW 
3 SSB CW 
4 CW SSB 
5 AM AM 
6 FM FM 
7 RTTY RTTY 
8 SSTV SSTV 
9 ATV ATV 

If the mode is not important it can be left blank, i.e. not stated in rules/invitation.   


Example:
WRONG (WT 4.17)
150804;1703;IZ5HQB;;59;001;59;000;;JN53NS;80;;N;N; 
CORRECT
150804;1703;IZ5HQB;1;59;001;59;000;;JN53NS;80;;N;N;
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20150810/2bcc02c9/attachment.html>