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

yl2gd yl2gd at lral.lv
Wed Aug 12 20:00:41 CEST 2015


Hi VHF WT users!

EDI file problem on WinTest longs for years :-(
Below are related mails and N6TV answer to me a year ago.
Still no progress.

73! Gunar - YL2GD

----------------------------------------------------------------------


Thanks Gunar; I have forwarded your files to F6FVY.  He is the only one who can fix the code at this point. 


73, 
Bob, N6TV


On Wed, Jun 25, 2014 at 12:11 PM, yl2gd <yl2gd at lral.lv> wrote:

  Hello Bob!

  Thanks for your instant answer and your kindness!


  Lot of IARU R1 VHF contests are mixed mode contests
  and most log checking programs mandatory require "mode field"
  (between CALL and SENT RPRT) to be filled.

  WinTest formats ADIF file without any problems and errors!
  I attatched from the same contest my WTB file, ADIF file 
  and 2 versions of my short EDI file:
  1-generated by WinTest (wrong)
  2-corrected by hand (right)

  Mode of QSO is coded according IARU R1 VHF Handbook 
  http://www.iaru-r1.org/index.php?option=com_content&view=article&id=1201:vhf-manager-handbook-edition-612&catid=42:vhf&Itemid=100
  (page 76 in VHF Handbook V6 12.pdf)
  Codes of mode for most important cases - two way:
  SSB = 1
  CW = 2
  FM = 6
  Not specified = 0 (used for DIGI modes usually)

  But anyway - I LIKE WinTest !!!

  73! Gunar - YL2GD
    ----- Original Message ----- 
    From: Bob Wilson, N6TV 
    To: Win-Test Reflector 
    Sent: Wednesday, June 25, 2014 8:44 AM
    Subject: Re: [WT-support] WinTest v.4.xx VHF EDI file format


    I found this in the Release Notes:

    4.1.0 (Aug 6, 2009)

    Bugfix: In REG1TEST exports (European Standard File for V/UHF Contests), QSO logged in mode different than CW or SSB was not well formatted. Tks DL5NAH.

    Does this sound like the fix you  wanted?

    If you send me a .WTB file, I can try to import it into WT4 and generate an .EDI file.

    73,
    Bob, N6TV

    On Jun 25, 2014 1:25 AM, "yl2gd" <yl2gd at lral.lv> wrote:

      Hi folks!

      Does anybody have tested WinTest v.4.xx newest
      versions - is there fixed VHF EDI file problem - not 
      shown code of modulatin of QSO?
      There were some requests to fix this problem
      since WinTest v.3.xx times an later also ...
      Last year tested - it wasn`t fixed yet :-(

  ----- Original Message ----- 
  From: Polgár József 
  To: support at win-test.com ; 'Claudio Veroli' 
  Sent: Monday, August 10, 2015 6:39 PM
  Subject: Re: [WT-support] Mode code on .EDI VHF logs


  Hi Claudio !

   

  It is old problem, sorry..

   

  73! Jozef HA1VQ

   

  Feladó: support-bounces at f5mzn.org [mailto:support-bounces at f5mzn.org] Meghatalmazó Claudio Veroli
  Küldve: 2015. augusztus 10. 18:01
  Címzett: support at win-test.com
  Tárgy: [WT-support] Mode code on .EDI VHF logs

   

  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; CORRECT150804;1703;IZ5HQB;1;59;001;59;000;;JN53NS;80;;N;N; 

------------------------------------------------------------------------------


  _______________________________________________
  Support mailing list
  support at win-test.com
  http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20150812/90a76b74/attachment.html>


More information about the Support mailing list