[amsat-bb] RS-44 on LOTW?

Wed May 13 23:30:49 UTC 2020

Bernie,

Glad to see that It all worked out for you.

73

On Wed, May 13, 2020 at 4:27 PM Bernie and Cheryl <hamdan at ix.netcom.com>
wrote:

> Thanks to everyone who replied.  And yes, Tucker, I am using HRD for my
> logging, and therein lay my problem.
>
> Here's what the problem was.  I originally had a problem uploading RS-44
> QSO's to LOTW.  Several here on the list replied to my original post and
> suggested that my version of TQSL might be outdated.  So, I downloaded
> Version 2.5.3.  This resulted in a situation where NO QSO's could be
> uploaded, including non-satellite contacts, such as HF contacts.
>
> Tucker's question about using HRD (aka, Ham Radio Deluxe, of which I am
> using the latest version, i.e, V6.7.0.277) and his link to the HRD blog
> sent me off in the right direction.  It turned out that the "Station
> Location" data I had first input into HRD included the use of the word
> "Colorado" rather than the postal abbreviation of "CO".  TQSL now
> interprets the use of the full spelling of a state, as opposed to its
> postal abbreviation as an "error", and won't allow the log entry to be
> uploaded.  Once I changed the home state field in my HRD program, I went
> out and worked someone and was able to upload that new QSO to LOTW
> immediately.
>
> But, what about my old QSO's that I hadn't uploaded yet?  It turns out
> that BOTH states need to use the postal abbreviation.  In other words, not
> only does the entry for the state of my station need to use the postal
> abbreviation, but now the state of the station I am working needs to be
> changed to use the postal abbreviation.  If this is not done both ways, the
> QSO can't be uploaded.  So, I went back to my RS-44 QSO's, and had to
> change a few QSO's to the respective postal abbreviations (there were only
> about 3-4 our out of 19 QSO's like this, and yet none of them could be
> uploaded in the same attempt).  After doing that, all of my RS-44 QSOs were
> uploaded to LOTW without a problem.
>
> I'm not sure that what the programmers for TQSL did was an improvement.
> But, I can testify to the fact that I learned a great lesson in patience,
> so maybe that was the whole point???  I hate software updates!
>
> Thanks to Tucker, KI7UNJ, and the rest of you for your helpful replies.
> See you on the birds!
>
> 73 de Bernie, KF0QS
> On 5/12/2020 7:29 AM, KI7UNJ Tucker wrote:
>
> You using HRD by chance for your logging?
>
> Here is a post from my local club about HRD And the new version of TQSL
>
> **************
> It turns out that you are right, the problem appears to be in the Log file
> created by HAM Radio Deluxe. This article tells us how to fix it:
> https://www.hamradiodeluxe.com/blog/TQSL
> -v252-TipsnTricks-for-Correcting-Your-Log-Data.html
>
> Rick Murphy provided that pointer:
> https://groups.arrl.org/g/ARRL-LoTW/message/32757?p=,,,20,0,0,0
> *****************
>
> https://groups.arrl.org
> <https://groups.arrl.org/g/ARRL-LoTW/message/32757?p=,,,20,0,0,0>On Tue,
> May 12, 2020 at 06:22 KI7UNJ Tucker <ki7unj at gmail.com> wrote:
>
>> Good morning
>>
>> For the BB when you want to respond do a “reply all” that will reply to
>> both the person whom responded and back to the BB. now if that person only
>> did a reply to you and not to the BB you can add the BB email on the to
>> list with there name if you want the response to go to the BB.
>>
>> As for TQSL... I assume your using a logging software and it’s sending
>> the data to TQSL?  If so TQSL changed a bit in what it expects in the log 2
>> versions ago and many logging apps need to be updated. I’ll try and find
>> the post about it and forward it to you.
>>
>>
>> On Mon, May 11, 2020 at 22:15 Bernie and Cheryl <hamdan at ix.netcom.com>
>> wrote:
>>
>>> Hi Tucker:
>>>
>>> We've worked on the birds several times.  Indeed, I believe we've
>>> exchanged QSL's.
>>>
>>> I have a couple of questions if you don't mind.  First, I downloaded the
>>> newest version of TQSL.  Now, it refuses to upload *any *contacts.  I
>>> get the following screen when I try to upload:  "Failed to sign the ADIF
>>> with TQSL, see logfile for more info."  Do you know what the problem is?
>>>
>>> Secondly, so that I don't have to pester you with every question, how do
>>> I respond to a post on the AMSAT board so that the whole board can read
>>> it?  Obviously, I can respond to individuals who replied to my original
>>> post using direct email (at least I know how to do original posts), but I
>>> don't know how to respond on the board itself.
>>>
>>> Thanks, and hope to see you on the birds soon.
>>>
>>> 73 de Bernie, KF0QS
>>> On 5/10/2020 1:44 PM, KI7UNJ Tucker wrote:
>>>
>>> RS-44 is in LOTW,  I have multiple QSL in LTOW from it.  You will need
>>> to update your TQSL (came out May 1st) with the latest config. and make
>>> sure you have sat = "RS-44"
>>>
>>>
>>>
>>>
>>> On Sun, May 10, 2020 at 11:53 AM Bernie and Cheryl via AMSAT-BB <
>>> amsat-bb at amsat.org> wrote:
>>>
>>>> Dear Folks:
>>>>
>>>> I have been uploading my QSO's to LOTW fairly quickly.  I have noticed
>>>> that none of my RS-44 QSOs show up.  Is this happening for everyone?
>>>> If
>>>> not, what am I doing wrong?
>>>>
>>>> Thanks, in advance, for any help you can give me.
>>>>
>>>> 73 de Bernie, KF0QS
>>>>
>>>> _______________________________________________
>>>> Sent via AMSAT-BB at amsat.org. AMSAT-NA makes this open forum available
>>>> to all interested persons worldwide without requiring membership.
>>>> Opinions expressed
>>>> are solely those of the author, and do not reflect the official views
>>>> of AMSAT-NA.
>>>> Not an AMSAT-NA member? Join now to support the amateur satellite
>>>> program!
>>>> Subscription settings: https://www.amsat.org/mailman/listinfo/amsat-bb
>>>>
>>>
>>>
>>> --
>>> *Casey Tucker  KI7UNJ*
>>> https://twitter.com/KI7UNJ
>>>
>>> --
>> *Casey Tucker  KI7UNJ*
>> https://twitter.com/KI7UNJ
>>
>> --
> *Casey Tucker  KI7UNJ*
> https://twitter.com/KI7UNJ
>
>

-- 
*Casey Tucker  KI7UNJ*
https://twitter.com/KI7UNJ