| |
CX2SA > SATDIG 27.02.19 03:33l 803 Lines 33796 Bytes #999 (0) @ WW
BID : AMSATBB1486
Read: GUEST
Subj: AMSAT-BB-digest V14 86
Path: IW8PGT<IR2UBX<DB0RES<DB0OVN<DB0GOS<ON0AR<GB7CIP<CX2SA
Sent: 190227/0131Z @:CX2SA.SAL.URY.SOAM #:969 [Salto] FBB7.00e $:AMSATBB1486
From: CX2SA@CX2SA.SAL.URY.SOAM
To : SATDIG@WW
Today's Topics:
1. Re: [ARRL-LoTW] Lotw use (Dave AA6YQ)
2. Re: Lotw use (R.T.Liddy)
3. Re: Lotw use (James McIrvin)
4. Re: Activating Northern Maine Grids - March 2-3 (James McIrvin)
5. Re: Activating Northern Maine Grids - March 2-3 (R.T.Liddy)
6. Re: [ARRL-LoTW] Lotw use (Dave AA6YQ)
7. Re: [ARRL-LoTW] Lotw use (Michael Carper, Ph.D.)
8. Re: Lotw use (Andrew Glasbrenner)
9. Re: [ARRL-LoTW] Lotw use (Bob Meyers)
----------------------------------------------------------------------
Message: 1
Date: Tue, 26 Feb 2019 15:16:08 -0500
From: "Dave AA6YQ" <aa6yq@?????????.???>
To: <ARRL-LoTW@??????.??>, "'Paul Stoetzer'" <n8hm@????.???>
Cc: 'AMSAT BB' <amsat-bb@?????.???>
Subject: Re: [amsat-bb] [ARRL-LoTW] Lotw use
Message-ID: <01a801d4ce10$1cec3df0$56c4b9d0$@?????????.???>
Content-Type: text/plain; charset="UTF-8"
+ AA6YQ comments below
SAT/LoTW Users,
ARRL does not give much attention to Satellite LoTW users and/or operations
- IMHO. If there is something needing to be done for DXCC-HF, they fall over
themselves working on it - again, IMHO.
+ From late 2012 through 2017, the addition of new functionality to LoTW was
suspended so that the ARRL's small IT staff could focus on making the LoTW
Server reliable and scalable. After that task was successfully completed,
the announced but long-delayed support for CQ WAZ awards was implemented and
released; note that this award includes 6m, as well as HF bands.
+ Since CQ WAZ was released last April, no new functionality has been added
to LoTW because the IT staff are working on other projects.
Maybe we should bombard various League Officials with e-mails to get their
attention? I'm not suggesting this as a solution, just a question in the
recesses of my mind.
Perhaps, a knowledgeable person from the SAT Community could work with a
willing person at the ARRL. They might be able to get things corrected and
up-to-date some day. HIHI
+ Your efforts will likely be more effective if you describe what is need of
correction, and what is in need of updating. Perhaps this will help:
<https://lotw.arrl.org/lotw-help/satellite-qsos/?lang=en>
+ LoTW is currently aware of these Satellites; note that JO-97, FO-99, and
QO-100 are included:
<satellite name="AO-10" startDate="1983-06-16">AMSAT-OSCAR 10</satellite>
<satellite name="AO-13" startDate="1988-06-15"
endDate="1996-12-07">AMSAT-OSCAR 13</satellite>
<satellite name="AO-16" startDate="1990-01-22">AMSAT-OSCAR 16</satellite>
<satellite name="AO-21" startDate="1991-01-29" endDate="1994-09-16">OSCAR
21/RS-14</satellite>
<satellite name="AO-27" startDate="1993-09-26">AMRAD-OSCAR 27</satellite>
<satellite name="AO-3" startDate="1965-03-18"
endDate="1965-03-27">AMSAT-OSCAR 3</satellite>
<satellite name="AO-4" startDate="1965-12-21"
endDate="1966-03-16">AMSAT-OSCAR 4</satellite>
<satellite name="AO-40" startDate="2000-11-16"
endDate="2004-01-25">AMSAT-OSCAR 40</satellite>
<satellite name="AO-51" startDate="2004-06-29"
endDate="2011-11-29">AMSAT-OSCAR 51</satellite>
<satellite name="AO-6" startDate="1972-10-15"
endDate="1977-06-21">AMSAT-OSCAR 6</satellite>
<satellite name="AO-7" startDate="1974-11-15">AMSAT-OSCAR 7</satellite>
<satellite name="AO-73" startDate="2013-11-21">AMSAT-OSCAR 73</satellite>
<satellite name="AO-8" startDate="1978-03-15"
endDate="1983-06-24">AMSAT-OSCAR 8</satellite>
<satellite name="AO-85" startDate="2015-10-09">AMSAT-OSCAR 85
(Fox-1A)</satellite>
<satellite name="AO-91" startDate="2017-11-23">AMSAT-OSCAR 91 (RadFxSat /
Fox-1B)</satellite>
<satellite name="AO-92" startDate="2018-01-12">AMSAT-OSCAR 92
(Fox-1D)</satellite>
<satellite name="ARISS" startDate="1998-11-20">ARISS</satellite>
<satellite name="Arsene" startDate="1993-05-13" endDate="1993-09-10">OSCAR
24</satellite>
<satellite name="BY70-1" startDate="2016-12-28" endDate="2017-02-17">Bayi
Kepu Weixing 1</satellite>
<satellite name="CAS-3H" startDate="2015-09-18">LilacSat-2</satellite>
<satellite name="CAS-4A" startDate="2017-10-18">CAMSAT 4A (CAS-4A)</satellite>
<satellite name="CAS-4B" startDate="2017-10-18">CAMSAT 4B (CAS-4B)</satellite>
<satellite name="DO-64" startDate="2008-04-28">Delfi OSCAR-64</satellite>
<satellite name="EO-79" startDate="2014-06-19">FUNcube-3</satellite>
<satellite name="EO-88" startDate="2017-02-15">Emirates-OSCAR 88
(Nayif-1)</satellite>
<satellite name="FO-12" startDate="1986-08-12"
endDate="1989-11-05">Fuji-OSCAR 12</satellite>
<satellite name="FO-20" startDate="1990-02-07">Fuji-OSCAR 20</satellite>
<satellite name="FO-29" startDate="1996-07-17">Fuji-OSCAR 29</satellite>
<satellite name="FO-99" startDate="2019-01-26">Fuji-OSCAR 99
(NEXUS)</satellite>
<satellite name="FS-3" startDate="2017-09-24">FalconSAT 3</satellite>
<satellite name="HO-68" startDate="2009-12-15">Hope-Oscar 68</satellite>
<satellite name="IO-86" startDate="2015-09-28">Indonesia-OSCAR 86
(LAPAN-ORARI)</satellite>
<satellite name="JO-97" startDate="2018-12-08">Jordan-OSCAR
97(JY1Sat)</satellite>
<satellite name="KEDR" startDate="2011-08-03"
endDate="2012-01-04">ARISSat-1</satellite>
<satellite name="LO-19" startDate="1990-01-22">Lusat-OSCAR 19</satellite>
<satellite name="LO-78" startDate="2014-04-22"
endDate="2014-07-28">LituanicaSAT-1</satellite>
<satellite name="LO-87" startDate="2016-05-30">LUSEX-OSCAR 87</satellite>
<satellite name="LO-90" startDate="2017-05-25">LilacSat-OSCAR 90
(LilacSat-1)</satellite>
<satellite name="MIREX" startDate="1991-02-01" endDate="2000-06-16">MIR
Packet Digipeater</satellite>
<satellite name="NO-44" startDate="2001-09-30">Navy-OSCAR 44</satellite>
<satellite name="NO-83" startDate="2015-05-20">BRICsat</satellite>
<satellite name="NO-84" startDate="2015-05-20">PSAT</satellite>
<satellite name="QO-100" startDate="2019-02-02">Qatar-OSCAR 100
(Es'hail-2/P4A)</satellite>
<satellite name="RS-1" startDate="1978-10-26" endDate="1979-02-01">Radio
Sputnik 1</satellite>
<satellite name="RS-10" startDate="1987-06-23" endDate="2000-11-01">Radio
Sputnik 10</satellite>
<satellite name="RS-11" startDate="1987-06-23" endDate="2000-11-01">Radio
Sputnik 11</satellite>
<satellite name="RS-12" startDate="1991-02-05" endDate="2002-02-15">Radio
Sputnik 12</satellite>
<satellite name="RS-13" startDate="1991-02-05" endDate="2002-02-15">Radio
Sputnik 13</satellite>
<satellite name="RS-15" startDate="1994-12-16">Radio Sputnik 15</satellite>
<satellite name="RS-2" startDate="1978-10-26" endDate="1979-02-01">Radio
Sputnik 2</satellite>
<satellite name="RS-5" startDate="1981-12-17" endDate="1987-05-10">Radio
Sputnik 5</satellite>
<satellite name="RS-6" startDate="1981-12-17" endDate="1984-12-09">Radio
Sputnik 6</satellite>
<satellite name="RS-7" startDate="1981-12-18" endDate="1987-06-01">Radio
Sputnik 7</satellite>
<satellite name="RS-8" startDate="1981-12-17" endDate="1985-12-16">Radio
Sputnik 8</satellite>
<satellite name="SAREX" startDate="1990-12-02" endDate="1999-07-28">Shuttle
Amateur Radio Experiment (SAREX) Digipeater</satellite>
<satellite name="SO-35" startDate="1999-02-23"
endDate="2001-06-10">Sunsat-OSCAR 35</satellite>
<satellite name="SO-41" startDate="2000-09-26">Saudi-OSCAR 41</satellite>
<satellite name="SO-50" startDate="2002-12-20">Saudi-OSCAR 50</satellite>
<satellite name="SO-67" startDate="2009-09-17">Sumbandila Oscar 67</satellite>
<satellite name="UKUBE1" startDate="2016-06-01">UKube-1
(FUNcube-2)</satellite>
<satellite name="UO-14" startDate="1990-01-22">UOSAT-OSCAR 14</satellite>
<satellite name="VO-52" startDate="2005-05-05"
endDate="2014-07-11">VUsat-OSCAR 52</satellite>
<satellite name="XW-2A" startDate="2015-09-18">Hope 2A (CAS-3A)</satellite>
<satellite name="XW-2B" startDate="2015-09-18">Hope 2B (CAS-3B)</satellite>
<satellite name="XW-2C" startDate="2015-09-18">Hope 2C (CAS-3C)</satellite>
<satellite name="XW-2D" startDate="2015-09-18">Hope 2D (CAS-3D)</satellite>
<satellite name="XW-2E" startDate="2015-09-18">Hope 2E (CAS-3E)</satellite>
<satellite name="XW-2F" startDate="2015-09-18">Hope 2F (CAS-2F)</satellite>
73,
Dave, AA6YQ
------------------------------
Message: 2
Date: Tue, 26 Feb 2019 20:40:02 +0000 (UTC)
From: "R.T.Liddy" <k8bl@?????????.???>
To: John Kludt <johnnykludt@?????.???>
Cc: AMSAT BB <amsat-bb@?????.???>, "arrl-lotw@??????.???
<arrl-lotw@??????.??>
Subject: Re: [amsat-bb] Lotw use
Message-ID: <1884847236.5548668.1551213602542@????.?????.???>
Content-Type: text/plain; charset=UTF-8
John,
LoTW having to satisfy the numerous Logging Programs in use
has to be a total nightmare and next to impossible. I use DX4WIN
and it is NOT Satellite friendly and very much out of date. Much of
the time I need to add my SAT QSOs to LoTW manually. Fortunately,
doing it that way allows me to always use the correct syntax wanted
by LoTW and the proper names they use for each SAT. My roving
QSOs on SAT are also entered manually when transcribed from my
digital recorder. Glad to hear the ARRL/LoTW Team is doing much
better with the SATs.
TNX/73,? ? ? ?Bob? K8BL
On Tuesday, February 26, 2019, 2:16:31 PM CST, John Kludt
<johnnykludt@?????.???> wrote:
R.T. and Team,
The satellite list is carried in TQSL which is revised frequently.? A
release came out on February 4, 2019 adding JO-97, FO-99 and QO-100 to the
list of supported satellites.? That should pretty much bring them up to
date.? I am sure everyone is keeping their TQSL version current as that is
where these additions reside.? Going back through the TSQL Change Log it
looks to me like most everything is there.? In the January 23, 2017 TQSL
Update they even added "SAREX" and "MIREX" to catch old QSO's that may be
coming along as people enter paper logs from the good old days to the LoTW.
And, yes, as far as syntax goes gotta use the right name or things don't
work quite right.? But, heck, SATpc32 is exactly the same.? Trying to write
code to cover every possible "creative" use of a satellite name can run to
hundreds if not thousands of lines of code and it really serves no purpose
other than allowing us, the end users, to be very sloppy.
So bottom line to me is the ARRL is not as unresponsive as it may seem.? So
like I said, I am sure everyone has updated to the latest release (February
14, 2019 config.xml v11.7).? If you have done that you are ready to log
QSO's through FO-99, JO-97 and if you are lucky enough to live in the
covered part of the globe QO-100.
73,
John K4SQC
------------------------------
Message: 3
Date: Tue, 26 Feb 2019 16:21:42 -0500
From: James McIrvin <arsn1ipa@?????.???>
To: "R.T.Liddy" <k8bl@?????????.???>
Cc: AMSAT BB <amsat-bb@?????.???>, "arrl-lotw@??????.???
<arrl-lotw@??????.??>
Subject: Re: [amsat-bb] Lotw use
Message-ID:
<CAHKjG8M=PW=rM25SKidw8+NGR_dio6grmGw7O=ytMxN_YYr3mQ@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
I only put this out as a general question to the group. I know that DXLab
Suite is pretty good to work with and I have used it for years. I tried
another program that I liked the looks of and it hosed my log up from years
past and I have not tried to get it fixed up yet. As of right now, I am
only using a log that I have set up for Sat logging because that is the
only thing that I am working on as of right now.
But the thing that I was mentioning was that some of the folks that I have
worked don't seem to do anything with LOTW and as to E-crap, ( phishing
card ), I don't use that for anything. I have uploaded to it in the past,
however, as of right now I can't even get into that one and that will be
fixed someday when I take the time to get into that. Another story.
However, as I was alluding to before was that also I have a couple of folks
that I have worked and they don't seem to have uploaded any Sat's. So I
will have to wait on them.
Now someone had mentioned about talking to the league, well don't waste
your breath, they don't seem to care about the little guy as much as those
that send in big money for contesting stations and things like that.
The one thing that still has not been answered is if going for a AMSAT
award is LOTW usable or not? If used with a screen shot?
I am still very new to the Sats and I have been having a lot of fun with
them and they have given me more reason to try to get on the air. Some of
the stuff is out there now for modes is like shooting ducks in a barrel.
Just to easy to work those modes.
Many years ago I did some paper chase work and have some wallpaper to hang
if I wanted, and then there is some that I have not gone for the
Certificate because of the cost, however I know that I have done it and if
someone wants to see those that I have not gone for you will find them on
the LOTW page if I have logged in.
Things like triple play have paper, 20m WAS RTTY, DXCC digital, and some
others, but like 9 band JT65 the cost for that piece is more then I want to
pay for.
Like I said this work on the sats have given me more to work on besides and
I have learning a lot and want to continue with it. Just would be nice to
see more folks use the program that is out there and then at least do the
upload via your logging software.
Just some of my thoughts and replies to those that have responded so far.
73 de JIM N1IPA
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campa
ign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campa
ign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Feb 26, 2019 at 3:42 PM R.T.Liddy <k8bl@?????????.???> wrote:
> John,
>
> LoTW having to satisfy the numerous Logging Programs in use
> has to be a total nightmare and next to impossible. I use DX4WIN
> and it is NOT Satellite friendly and very much out of date. Much of
> the time I need to add my SAT QSOs to LoTW manually. Fortunately,
> doing it that way allows me to always use the correct syntax wanted
> by LoTW and the proper names they use for each SAT. My roving
> QSOs on SAT are also entered manually when transcribed from my
> digital recorder. Glad to hear the ARRL/LoTW Team is doing much
> better with the SATs.
>
> TNX/73, Bob K8BL
>
>
> On Tuesday, February 26, 2019, 2:16:31 PM CST, John Kludt <
> johnnykludt@?????.???> wrote:
>
> R.T. and Team,
>
> The satellite list is carried in TQSL which is revised frequently. A
> release came out on February 4, 2019 adding JO-97, FO-99 and QO-100 to the
> list of supported satellites. That should pretty much bring them up to
> date. I am sure everyone is keeping their TQSL version current as that is
> where these additions reside. Going back through the TSQL Change Log it
> looks to me like most everything is there. In the January 23, 2017 TQSL
> Update they even added "SAREX" and "MIREX" to catch old QSO's that may be
> coming along as people enter paper logs from the good old days to the LoTW.
>
> And, yes, as far as syntax goes gotta use the right name or things don't
> work quite right. But, heck, SATpc32 is exactly the same. Trying to write
> code to cover every possible "creative" use of a satellite name can run to
> hundreds if not thousands of lines of code and it really serves no purpose
> other than allowing us, the end users, to be very sloppy.
>
> So bottom line to me is the ARRL is not as unresponsive as it may seem.
> So like I said, I am sure everyone has updated to the latest release
> (February 14, 2019 config.xml v11.7). If you have done that you are ready
> to log QSO's through FO-99, JO-97 and if you are lucky enough to live in
> the covered part of the globe QO-100.
>
> 73,
>
> John K4SQC
>
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 4
Date: Tue, 26 Feb 2019 16:25:22 -0500
From: James McIrvin <arsn1ipa@?????.???>
To: Clayton Coleman W5PFG <tasmac@?????.??>
Cc: AMSAT-BB <amsat-bb@?????.???>
Subject: Re: [amsat-bb] Activating Northern Maine Grids - March 2-3
Message-ID:
<CAHKjG8N7sqyPGUtJWULbvCY2S1Gh3deoZ8TBN-s7m_tHtm_-KA@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Clayton,
It would be nice to be able to work you for a couple of those grids for
myself. I could even activate a couple of those this summer myself for
some since I am right here in FN53.
I will have to watch for you.
Jim N1IPA
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campa
ign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campa
ign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Feb 26, 2019 at 11:31 AM Clayton Coleman W5PFG <tasmac@?????.??>
wrote:
> Between ~03:00 UTC March 2 thru ~17:00 UTC March 3, I will operate
> satellites /TM (Tobaggan Mobile) thru grids FN54, FN55, FN56, FN57,
> FN66, and FN67. I plan to activate the FN54/55, FN56/66, and FN57/67
> grid lines I've used on previous Maine expeditions. This will be a
> fast-paced trip and I don't anticipate working every bird or every pass.
> I will stop to sleep, drink, and eat. Weather will be a huge factor.
> Like many of my activations, it's recommended you monitor my @?????
> Twitter feed for the latest information.
>
> 73
> Clayton
> W5PFG
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 5
Date: Tue, 26 Feb 2019 21:41:21 +0000 (UTC)
From: "R.T.Liddy" <k8bl@?????????.???>
To: AMSAT-BB <amsat-bb@?????.???>, Clayton Coleman W5PFG
<tasmac@?????.??>
Subject: Re: [amsat-bb] Activating Northern Maine Grids - March 2-3
Message-ID: <1909203289.5575669.1551217281186@????.?????.???>
Content-Type: text/plain; charset=UTF-8
Clayton..... You are one brave soul!!!!!!? ?GL!!!!!!? ?Bob? K8BL
On Tuesday, February 26, 2019, 10:30:47 AM CST, Clayton Coleman W5PFG
<tasmac@?????.??> wrote:
Between ~03:00 UTC March 2 thru ~17:00 UTC March 3, I will operate
satellites /TM (Tobaggan Mobile) thru grids FN54, FN55, FN56, FN57,
FN66, and FN67. I plan to activate the FN54/55, FN56/66, and FN57/67
grid lines I've used on previous Maine expeditions. This will be a
fast-paced trip and I don't anticipate working every bird or every pass.
I will stop to sleep, drink, and eat. Weather will be a huge factor.
Like many of my activations, it's recommended you monitor my @?????
Twitter feed for the latest information.
73
Clayton
W5PFG
_______________________________________________
Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 6
Date: Tue, 26 Feb 2019 16:42:19 -0500
From: "Dave AA6YQ" <aa6yq@?????????.???>
To: <ARRL-LoTW@??????.??>
Cc: 'AMSAT BB' <amsat-bb@?????.???>
Subject: Re: [amsat-bb] [ARRL-LoTW] Lotw use
Message-ID: <01d401d4ce1c$270174c0$75045e40$@?????????.???>
Content-Type: text/plain; charset="UTF-8"
Logging applications should populate their "Satellite Selectors" with the
list of satellite names provided in LoTW's Configuration Data file; this
will enable users to easily and correctly log QSOs that will be accepted
when submitted to LoTW.
Note that each satellite QSOs submitted to LoTW must specify a "Propagation
Mode" of SAT -- another opportunity for automation in the logging application.
73,
Dave, AA6YQ
LoTW having to satisfy the numerous Logging Programs in use has to be a
total nightmare and next to impossible. I use DX4WIN and it is NOT Satellite
friendly and very much out of date. Much of the time I need to add my SAT
QSOs to LoTW manually. Fortunately, doing it that way allows me to always
use the correct syntax wanted by LoTW and the proper names they use for each
SAT. My roving QSOs on SAT are also entered manually when transcribed from
my digital recorder. Glad to hear the ARRL/LoTW Team is doing much better
with the SATs.
TNX/73, Bob K8BL
On Tuesday, February 26, 2019, 2:16:31 PM CST, John Kludt
<johnnykludt@?????.???> wrote:
R.T. and Team,
The satellite list is carried in TQSL which is revised frequently. A
release came out on February 4, 2019 adding JO-97, FO-99 and QO-100 to the
list of supported satellites. That should pretty much bring them up to
date. I am sure everyone is keeping their TQSL version current as that is
where these additions reside. Going back through the TSQL Change Log it
looks to me like most everything is there. In the January 23, 2017 TQSL
Update they even added "SAREX" and "MIREX" to catch old QSO's that may be
coming along as people enter paper logs from the good old days to the LoTW.
And, yes, as far as syntax goes gotta use the right name or things don't
work quite right. But, heck, SATpc32 is exactly the same. Trying to write
code to cover every possible "creative" use of a satellite name can run to
hundreds if not thousands of lines of code and it really serves no purpose
other than allowing us, the end users, to be very sloppy.
So bottom line to me is the ARRL is not as unresponsive as it may seem. So
like I said, I am sure everyone has updated to the latest release (February
14, 2019 config.xml v11.7). If you have done that you are ready to log
QSO's through FO-99, JO-97 and if you are lucky enough to live in the
covered part of the globe QO-100.
73,
John K4SQC
------------------------------
Message: 7
Date: Tue, 26 Feb 2019 15:49:22 -0600
From: "Michael Carper, Ph.D." <mike@??????.???>
To: Dave AA6YQ <aa6yq@?????????.???>
Cc: AMSAT BB <amsat-bb@?????.???>, ARRL-LoTW@??????.??
Subject: Re: [amsat-bb] [ARRL-LoTW] Lotw use
Message-ID:
<CAKJep-AdUBJ1by67pwm4etd5KZBY40ktc05GJ8PVvRqV50sp+Q@????.?????.???>
Content-Type: text/plain; charset="UTF-8"
Yeah, I think that's what I was referring to earlier for sure.
How you doing Dave? I miss you buddy!
Mike, WA9PIE
On Tue, Feb 26, 2019 at 3:45 PM Dave AA6YQ <aa6yq@?????????.???> wrote:
> Logging applications should populate their "Satellite Selectors" with the
> list of satellite names provided in LoTW's Configuration Data file; this
> will enable users to easily and correctly log QSOs that will be accepted
> when submitted to LoTW.
>
> Note that each satellite QSOs submitted to LoTW must specify a
> "Propagation Mode" of SAT -- another opportunity for automation in the
> logging application.
>
> 73,
>
> Dave, AA6YQ
>
>
>
>
> LoTW having to satisfy the numerous Logging Programs in use has to be a
> total nightmare and next to impossible. I use DX4WIN and it is NOT
> Satellite friendly and very much out of date. Much of the time I need to
> add my SAT QSOs to LoTW manually. Fortunately, doing it that way allows me
> to always use the correct syntax wanted by LoTW and the proper names they
> use for each SAT. My roving QSOs on SAT are also entered manually when
> transcribed from my digital recorder. Glad to hear the ARRL/LoTW Team is
> doing much better with the SATs.
>
> TNX/73, Bob K8BL
>
>
> On Tuesday, February 26, 2019, 2:16:31 PM CST, John Kludt <
> johnnykludt@?????.???> wrote:
>
> R.T. and Team,
>
> The satellite list is carried in TQSL which is revised frequently. A
> release came out on February 4, 2019 adding JO-97, FO-99 and QO-100 to the
> list of supported satellites. That should pretty much bring them up to
> date. I am sure everyone is keeping their TQSL version current as that is
> where these additions reside. Going back through the TSQL Change Log it
> looks to me like most everything is there. In the January 23, 2017 TQSL
> Update they even added "SAREX" and "MIREX" to catch old QSO's that may be
> coming along as people enter paper logs from the good old days to the LoTW.
>
> And, yes, as far as syntax goes gotta use the right name or things don't
> work quite right. But, heck, SATpc32 is exactly the same. Trying to write
> code to cover every possible "creative" use of a satellite name can run to
> hundreds if not thousands of lines of code and it really serves no purpose
> other than allowing us, the end users, to be very sloppy.
>
> So bottom line to me is the ARRL is not as unresponsive as it may seem.
> So like I said, I am sure everyone has updated to the latest release
> (February 14, 2019 config.xml v11.7). If you have done that you are ready
> to log QSO's through FO-99, JO-97 and if you are lucky enough to live in
> the covered part of the globe QO-100.
>
> 73,
>
> John K4SQC
>
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
>
------------------------------
Message: 8
Date: Tue, 26 Feb 2019 20:21:24 -0500
From: "Andrew Glasbrenner" <glasbrenner@??????????.???>
To: "'R.T.Liddy'" <k8bl@?????????.???>, "'Paul Stoetzer'"
<n8hm@????.???>
Cc: 'AMSAT BB' <amsat-bb@?????.???>, arrl-lotw@??????.??
Subject: Re: [amsat-bb] Lotw use
Message-ID: <056e01d4ce3a$c155aeb0$44010c10$@??????????.???>
Content-Type: text/plain; charset="UTF-8"
Bob, I think some major changes have occurred recently. In the past I would
not have disagreed with you, but for the past year or two I've been the
designated point-person on sending in new satellites to be added to TQSL.
The last three I sent were added in less than 24 hours. I still hear of the
occasional hiccup, but overall satellites seem to be well integrated and
supported lately. The ARRL should be commended for that improvement.
73, Drew KO4MA
AMSAT VP Operations
-----Original Message-----
From: AMSAT-BB <amsat-bb-bounces@?????.???> On Behalf Of R.T.Liddy
Sent: Tuesday, February 26, 2019 2:52 PM
To: Michael Carper, Ph.D. <mike@??????.???>; Paul Stoetzer <n8hm@????.???>
Cc: AMSAT BB <amsat-bb@?????.???>; arrl-lotw@??????.??
Subject: Re: [amsat-bb] Lotw use
SAT/LoTW Users,
ARRL does not give much attention to Satellite LoTW users and/or operations
- IMHO. If there is something needing to be done for DXCC-HF, they fall over
themselves working on it - again, IMHO. Maybe we should bombard various
League Officials with e-mails to get their attention? I'm not suggesting
this as a solution, just a question in the recesses of my mind.
Perhaps, a knowledgeable person from the SAT Community could work with a
willing person at the ARRL. They might be able to get things corrected and
up-to-date some day. HIHI
GL/73, Bob K8BL
(50+ Year ARRL Member, AMSAT Member since 1979)
On Tuesday, February 26, 2019, 12:01:46 PM CST, Paul Stoetzer
<n8hm@????.???> wrote:
Note that the list on the ARRL's website has not been updated with the
recent additions of JO-97, FO-99, and QO-100. Also, it lists "EO88", but the
correct name in the LoTW configuration file is "EO-88"
73,
Paul, N8HM
_______________________________________________
Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Message: 9
Date: Tue, 26 Feb 2019 18:59:49 -0600
From: Bob Meyers <meyersb@???????.???>
To: "Michael Carper, Ph.D." <mike@??????.???>
Cc: AMSAT BB <amsat-bb@?????.???>, Dave AA6YQ <aa6yq@?????????.???>,
ARRL-LoTW@??????.??
Subject: Re: [amsat-bb] [ARRL-LoTW] Lotw use
Message-ID: <63693497-86BE-401A-8DBE-E4084300617C@???????.???>
Content-Type: text/plain; charset=us-ascii
I have been successfully using N3FJP to log satellite contacts and have been
using it to send contacts to LoTW. The input form had to be modified to
make it more satellite friendly but that was easy. The upload to LoTW
feature works very good and I usually have contacts uploaded within minutes
of the pass. If the satellite name is not right it will reject your upload
and then you can correct it and try again. It works great.
I haven't been able to use it to download from LoTW yet but as I am not
tracking grids that is not important to me. The program supports it but I
haven't figured it out yet.
Bob WA8FXQ
> On Feb 26, 2019, at 3:49 PM, Michael Carper, Ph.D. via AMSAT-BB
<amsat-bb@?????.???> wrote:
>
> Yeah, I think that's what I was referring to earlier for sure.
>
> How you doing Dave? I miss you buddy!
>
> Mike, WA9PIE
>
>> On Tue, Feb 26, 2019 at 3:45 PM Dave AA6YQ <aa6yq@?????????.???> wrote:
>>
>> Logging applications should populate their "Satellite Selectors" with the
>> list of satellite names provided in LoTW's Configuration Data file; this
>> will enable users to easily and correctly log QSOs that will be accepted
>> when submitted to LoTW.
>>
>> Note that each satellite QSOs submitted to LoTW must specify a
>> "Propagation Mode" of SAT -- another opportunity for automation in the
>> logging application.
>>
>> 73,
>>
>> Dave, AA6YQ
>>
>>
>>
>>
>> LoTW having to satisfy the numerous Logging Programs in use has to be a
>> total nightmare and next to impossible. I use DX4WIN and it is NOT
>> Satellite friendly and very much out of date. Much of the time I need to
>> add my SAT QSOs to LoTW manually. Fortunately, doing it that way allows me
>> to always use the correct syntax wanted by LoTW and the proper names they
>> use for each SAT. My roving QSOs on SAT are also entered manually when
>> transcribed from my digital recorder. Glad to hear the ARRL/LoTW Team is
>> doing much better with the SATs.
>>
>> TNX/73, Bob K8BL
>>
>>
>> On Tuesday, February 26, 2019, 2:16:31 PM CST, John Kludt <
>> johnnykludt@?????.???> wrote:
>>
>> R.T. and Team,
>>
>> The satellite list is carried in TQSL which is revised frequently. A
>> release came out on February 4, 2019 adding JO-97, FO-99 and QO-100 to the
>> list of supported satellites. That should pretty much bring them up to
>> date. I am sure everyone is keeping their TQSL version current as that is
>> where these additions reside. Going back through the TSQL Change Log it
>> looks to me like most everything is there. In the January 23, 2017 TQSL
>> Update they even added "SAREX" and "MIREX" to catch old QSO's that may be
>> coming along as people enter paper logs from the good old days to the LoTW.
>>
>> And, yes, as far as syntax goes gotta use the right name or things don't
>> work quite right. But, heck, SATpc32 is exactly the same. Trying to write
>> code to cover every possible "creative" use of a satellite name can run to
>> hundreds if not thousands of lines of code and it really serves no purpose
>> other than allowing us, the end users, to be very sloppy.
>>
>> So bottom line to me is the ARRL is not as unresponsive as it may seem.
>> So like I said, I am sure everyone has updated to the latest release
>> (February 14, 2019 config.xml v11.7). If you have done that you are ready
>> to log QSO's through FO-99, JO-97 and if you are lucky enough to live in
>> the covered part of the globe QO-100.
>>
>> 73,
>>
>> John K4SQC
>>
>> _______________________________________________
>> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
> _______________________________________________
> Sent via AMSAT-BB@?????.???. 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: http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
Subject: Digest Footer
_______________________________________________
Sent via amsat-bb@?????.???.
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 member? Join now to support the amateur satellite program!
http://www.amsat.org/mailman/listinfo/amsat-bb
------------------------------
End of AMSAT-BB Digest, Vol 14, Issue 86
****************************************
Read previous mail | Read next mail
| |
