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@amsat.org 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@ambersoft.com 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, AA6YQLoTW 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@gmail.com> 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.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: http://www.amsat.org/mailman/listinfo/amsat-bb
Sent via AMSAT-BB@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: http://www.amsat.org/mailman/listinfo/amsat-bb