Re: [wsjt-devel] K4SHQ FT8 Notes

2017-06-30 Thread Dan Malcolm 
Thanks David.  Got that done and in the process found there is an updated
TQSL 2.3.1.

 

From: David Tiller [mailto:dtil...@captechconsulting.com] 
Sent: Friday, June 30, 2017 8:05 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] K4SHQ FT8 Notes

 

In TSQL, under preferences there's a tab called "ADIF Modes". In there you
can add an FT8  --> DATA mapping. 

 

Here's mine:

 



--

David Tiller

Sr. Architect/Lead Consultant | CapTech

(804) 304-0638 | dtil...@captechconsulting.com
<mailto:dtil...@captechconsulting.com> 

 

 

 

On Jun 30, 2017, at 8:58 PM, Dan Malcolm <dan.malcol...@gmail.com
<mailto:dan.malcol...@gmail.com> > wrote:





Thanks David. Log4OM does indeed use TQSL under the hood.  Just where in
TQSL do enter FT8-->DATA?

BTW I have found that QRZ will accept FT8.

 

From: David Tiller [ <mailto:dtil...@captechconsulting.com>
mailto:dtil...@captechconsulting.com] 
Sent: Friday, June 30, 2017 7:47 PM
To: WSJT software development < <mailto:wsjt-devel@lists.sourceforge.net>
wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] K4SHQ FT8 Notes

 

Re: the second part of item #2: You still can't upload to eQSL or LoTW with
FT8.

 

If Log4OM is anything like the macOS software I use, it actually uses TSQL
under the covers to do the digital signing and upload. At least in my case,
if you add the FT8 --> DATA mapping in TSQL, the upload works.

 

Might be worth a try.

 

--

David Tiller

Sr. Architect/Lead Consultant | CapTech

(804) 304-0638 |  <mailto:dtil...@captechconsulting.com>
dtil...@captechconsulting.com

 

 

 

On Jun 30, 2017, at 8:37 PM, Dan Malcolm < <mailto:dan.malcol...@gmail.com>
dan.malcol...@gmail.com> wrote:






1.   Log4OM can be made to accept FT8 as a mode.  But while it accepts
it as a mode, RST reports are set '59'. 

2.   Reference #1 above. Making Log4OM accept FT8 is trivial but moot.
You still can't upload to eQSL or LoTW with FT8.

3.   Log4OM also does not auto upload to eQSL when the mode is FT8.

4.   In order to capture the RST values I include them in my JTAlert-X
"QSL Message" text window using Laurie's replaceable tokens.  Check the
JTAlert Help file under Logging in the "Comments and QSL Message Text
Substitutions" section.

 

All short comings and disconnects will probably be resolved in time as FT8
moves into its own.  Again congrats to the devel team.  This is exciting.

 

I am running an Apache ANAN 100D.  There has been discussion of what to call
the "split" mode.  I didn't understand WSJT's use of it until it was
explained on this forum just recently.  Now I do understand and approve.  My
rig likes it just fine but I understand other rigs do not.  I do think we
need another name for it so as not to confuse WSJT "split" with the other
"split".  I offered "Audio Purity Offset", but will be happy with whatever
the devel team decides.

 

Since FT8 is still beta, it is too soon to approach the on line logbooks
about allowing FT8.  But that time is approaching.

 

 

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites,  <http://slashdot.org/> Slashdot.org!
<http://sdm.link/slashdot___>
http://sdm.link/slashdot___
wsjt-devel mailing list
 <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites,  <http://slashdot.org/> Slashdot.org!
<http://sdm.link/slashdot___>
http://sdm.link/slashdot___
wsjt-devel mailing list
 <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] K4SHQ FT8 Notes

2017-06-30 Thread Dan Malcolm 
Thanks David. Log4OM does indeed use TQSL under the hood.  Just where in
TQSL do enter FT8-->DATA?

BTW I have found that QRZ will accept FT8.

 

From: David Tiller [mailto:dtil...@captechconsulting.com] 
Sent: Friday, June 30, 2017 7:47 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] K4SHQ FT8 Notes

 

Re: the second part of item #2: You still can't upload to eQSL or LoTW with
FT8. 

 

If Log4OM is anything like the macOS software I use, it actually uses TSQL
under the covers to do the digital signing and upload. At least in my case,
if you add the FT8 --> DATA mapping in TSQL, the upload works.

 

Might be worth a try.

 

--

David Tiller

Sr. Architect/Lead Consultant | CapTech

(804) 304-0638 | dtil...@captechconsulting.com
<mailto:dtil...@captechconsulting.com> 

 

 

 

On Jun 30, 2017, at 8:37 PM, Dan Malcolm <dan.malcol...@gmail.com
<mailto:dan.malcol...@gmail.com> > wrote:





1.   Log4OM can be made to accept FT8 as a mode.  But while it accepts
it as a mode, RST reports are set '59'. 

2.   Reference #1 above. Making Log4OM accept FT8 is trivial but moot.
You still can't upload to eQSL or LoTW with FT8.

3.   Log4OM also does not auto upload to eQSL when the mode is FT8.

4.   In order to capture the RST values I include them in my JTAlert-X
"QSL Message" text window using Laurie's replaceable tokens.  Check the
JTAlert Help file under Logging in the "Comments and QSL Message Text
Substitutions" section.

 

All short comings and disconnects will probably be resolved in time as FT8
moves into its own.  Again congrats to the devel team.  This is exciting.

 

I am running an Apache ANAN 100D.  There has been discussion of what to call
the "split" mode.  I didn't understand WSJT's use of it until it was
explained on this forum just recently.  Now I do understand and approve.  My
rig likes it just fine but I understand other rigs do not.  I do think we
need another name for it so as not to confuse WSJT "split" with the other
"split".  I offered "Audio Purity Offset", but will be happy with whatever
the devel team decides.

 

Since FT8 is still beta, it is too soon to approach the on line logbooks
about allowing FT8.  But that time is approaching.

 

 

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites,  <http://slashdot.org/> Slashdot.org!
<http://sdm.link/slashdot___>
http://sdm.link/slashdot___
wsjt-devel mailing list
 <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] K4SHQ FT8 Notes

2017-06-30 Thread David Tiller 
Re: the second part of item #2: You still can’t upload to eQSL or LoTW with FT8.

If Log4OM is anything like the macOS software I use, it actually uses TSQL 
under the covers to do the digital signing and upload. At least in my case, if 
you add the FT8 --> DATA mapping in TSQL, the upload works.

Might be worth a try.

--
David Tiller
Sr. Architect/Lead Consultant | CapTech
(804) 304-0638 | 
dtil...@captechconsulting.com



On Jun 30, 2017, at 8:37 PM, Dan Malcolm 
> wrote:

1.   Log4OM can be made to accept FT8 as a mode.  But while it accepts it 
as a mode, RST reports are set ‘59’.
2.   Reference #1 above. Making Log4OM accept FT8 is trivial but moot.  You 
still can’t upload to eQSL or LoTW with FT8.
3.   Log4OM also does not auto upload to eQSL when the mode is FT8.
4.   In order to capture the RST values I include them in my JTAlert-X “QSL 
Message” text window using Laurie’s replaceable tokens.  Check the JTAlert Help 
file under Logging in the “Comments and QSL Message Text Substitutions” section.

All short comings and disconnects will probably be resolved in time as FT8 
moves into its own.  Again congrats to the devel team.  This is exciting.

I am running an Apache ANAN 100D.  There has been discussion of what to call 
the “split” mode.  I didn’t understand WSJT’s use of it until it was explained 
on this forum just recently.  Now I do understand and approve.  My rig likes it 
just fine but I understand other rigs do not.  I do think we need another name 
for it so as not to confuse WSJT “split” with the other “split”.  I offered 
“Audio Purity Offset”, but will be happy with whatever the devel team decides.

Since FT8 is still beta, it is too soon to approach the on line logbooks about 
allowing FT8.  But that time is approaching.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] K4SHQ FT8 Notes

2017-06-30 Thread Dan Malcolm 
1.   Log4OM can be made to accept FT8 as a mode.  But while it accepts
it as a mode, RST reports are set '59'.  

2.   Reference #1 above. Making Log4OM accept FT8 is trivial but moot.
You still can't upload to eQSL or LoTW with FT8.

3.   Log4OM also does not auto upload to eQSL when the mode is FT8.

4.   In order to capture the RST values I include them in my JTAlert-X
"QSL Message" text window using Laurie's replaceable tokens.  Check the
JTAlert Help file under Logging in the "Comments and QSL Message Text
Substitutions" section.

 

All short comings and disconnects will probably be resolved in time as FT8
moves into its own.  Again congrats to the devel team.  This is exciting.

 

I am running an Apache ANAN 100D.  There has been discussion of what to call
the "split" mode.  I didn't understand WSJT's use of it until it was
explained on this forum just recently.  Now I do understand and approve.  My
rig likes it just fine but I understand other rigs do not.  I do think we
need another name for it so as not to confuse WSJT "split" with the other
"split".  I offered "Audio Purity Offset", but will be happy with whatever
the devel team decides.

 

Since FT8 is still beta, it is too soon to approach the on line logbooks
about allowing FT8.  But that time is approaching.

 

 

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel