Loading ...
Sorry, an error occurred while loading the content.

Re: [ARRL-LOTW] LoTW

Expand Messages
  • JV
    Hi All Dave has resolved the problem. The original adif file from DXBase is listed below followed by the corrections. Note BOLD and UNLINED sections. F has
    Message 1 of 49 , Jan 31, 2007
    • 0 Attachment
      Hi All
          Dave has resolved the problem. The original adif file from DXBase is listed below followed by the corrections. Note BOLD and UNLINED sections. "F" has been removed and Count Number has been changed.
      =========================================

      ADIF Export from DXbase 2005

      Copyright 2003-2004 Scientific Solutions, Inc.

      www.dxbase.com

      <EOH>

      <CALL:4>XT2C <QSO_DATE:8>20070118 <TIME_ON:4>2112 <RST_SENT:3>599 <RST_RCVD:3>599 <QSL_VIA:6>Direct <TX_PWR:3>100

      <ITUZ:2>46 <OPERATOR:4>KT4U <PFX:3>XT2 <QSL_RCVD:1>N <DXBQSL_RCVD:1>0 <FREQ:8>10.14000

      <BAND:3>30M <CQZ:2>35

      <DXBSUBMODE:6>PSK63F <MODE:6>PSK63F <QSL_SENT:1>Y <DXBQSL_SENT:1>3 <QSLSDATE:8>20070118

      <DXBPFX:2>XT <DXBMGRN:1>1 <DXBAWD:1>0 <DXBSEL:1>0 <DXBVAL:1>3

      <EOR

      =============================

          It needs to changed to:

      =============================

      ADIF Export from DXbase 2005

      Copyright 2003-2004 Scientific Solutions, Inc.

      www.dxbase.com

      <EOH>

      <CALL:4>XT2C <QSO_DATE:8>20070118 <TIME_ON:4>2112 <RST_SENT:3>599 <RST_RCVD:3>599 <QSL_VIA:6>Direct <TX_PWR:3>100

      <ITUZ:2>46 <OPERATOR:4>KT4U <PFX:3>XT2 <QSL_RCVD:1>N <DXBQSL_RCVD:1>0 <FREQ:8>10.14000

      <BAND:3>30M <CQZ:2>35

      <DXBSUBMODE:5>PSK63 <MODE:5>PSK63 <QSL_SENT:1>Y <DXBQSL_SENT:1>3 <QSLSDATE:8>20070118

      <DXBPFX:2>XT <DXBMGRN:1>1 <DXBAWD:1>0 <DXBSEL:1>0 <DXBVAL:1>3

      <EOR

      ========================

      JV

      ==========================================================

      -------Original Message-------
       
      Subject: Re: [ARRL-LOTW] LoTW
       
      Hi Rick
          I can send PSK31 to LoTW with out any problems. LoTW will not accept
      PSK63F that DXBase uses. I think the problem lies in the "F" that DXBase
      uses. If LoTW had PSK63F added to the preferences, I think the submittal
      would be OK. Only draw back is one would probable have to send their PSK63F
      QSOs from DXBase one at a time or in a group.
       
          Here is what I sent Dave, N1NN, who is also working on the problem.
      There are others who are trying to reach a solution also. I have confidence
      that this problem will be resolved for any else who may submit PSK63 QSOs.
       
          "Trying to send a PSK63 mode QSO to LoTW and getting nowhere. I am
      importing the QSO (XT2C) from DXBase2005. In DXBase the submode is
      PSK63F. In tqsl, preferences, I added DATA, high lighted PSK63 and hit OK.
      Now I
      have DATA->PSK63. When I try to convert to a tq8, I get an error. I'm
      guessing DXBase2005 with PSK63F is not compatible with tqsl PSK63. What
      do I need to do to correct this problem? I tried editing the DXBase2005
      XT2C.adi file to PSK63 but that didn't work. Still got the error
      message. I also tried PSK63->DATA. This allowed me to submit the tq8 but
      the mode showed up in LoTW as DATA instead of PSK63."
       
      JV KT4U
       
       
    • Peter Laws
      On Tue, Oct 21, 2014 at 8:03 PM, Dave AA6YQ aa6yq@ambersoft.com ... In the last 6 or so months, we ve had better communications of scheduled down time and I
      Message 49 of 49 , Oct 22, 2014
      • 0 Attachment
        On Tue, Oct 21, 2014 at 8:03 PM, ' Dave AA6YQ' aa6yq@...
        [ARRL-LOTW] <ARRL-LOTW@yahoogroups.com> wrote:



        > In my opinion, the ARRL must be far more pro-active in engaging with the LoTW user community here and in other online forums. That
        > includes posting timely updates when LoTW is not working correctly.


        In the last 6 or so months, we've had better communications of
        scheduled down time and I appreciate that. I'd like to see a little
        more timely explanations of unscheduled downtime which, as a long-time
        sysadmin, is something I know sysadmins are not fond of doing. If
        nothing else, it conveys a sense that "yep, it broke, but we're on
        it".

        The other thing that needs to be worked into all this 20x increase in
        support capacity is public defect tracking. Ideally, it would be
        public with the ability for any user to enter a bug, but there are
        operational constraints there (like it takes a lot of time to curate
        the defect database).

        Something like this would work:
        http://www.dxlabsuite.com/Launcher/defects.htm I can't put stuff
        there myself, but I know the guy that runs it and if my defect is
        clearly explained and isn't pilot error (as it is so often in my case)
        he'll put it there. Unfortunately, the guy that runs the example is a
        one-man show with, apparently, an unlimited time budget which is not
        the case with LOTW. But even a list of stuff that we know they know
        about would be VERY helpful.

        Nice analogy, BTW. :-)

        --
        Peter Laws | N5UWY | plaws plaws net | Travel by Train!
      Your message has been successfully submitted and would be delivered to recipients shortly.