Re: [wsjt-devel] ADIF log: QSLMSG field

[Black Michael via wsjt-devel]

Read this note from the eQSL FAQs,,,
The ADIF tag COMMENT is used for private comments about the QSO. We found out a 
decade ago that people did NOT want those comments disclosed on their cards! 
The ADIF tag QSLMSG is designed to be used for QSL Card Comments. That is the 
one we display on the eQSL card.
 
Turns out JTAlert has both fields available and puts the comment in the qslmsg 
field too (at least that's what it's doing for me right now...I think their may 
be a bug).
de Mike W9MDB

  From: Claude Frantz 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Saturday, August 5, 2017 12:02 PM
 Subject: Re: [wsjt-devel] ADIF log: QSLMSG field
   
On 08/05/2017 06:02 PM, Black Michael via wsjt-devel wrote:

Hi Mike & all,

> Do you mean eQSL's QSL card? 

I mean the eQSL service.

> If so, it uses the COMMENT field.  That
> field works for me on eQSL.

Please note that there is an important difference between the COMMENT
and the QSLMSG fields: In the COMMENT field, there are the comments for
myself. In the QSLMSG field, there are the comments for my QSO partner.

Further, there is a NOTES field in the ADIF spec. There is only a little
difference between the COMMENT and the NOTES fields. COMMENT is defined
as an string field and NOTES is defined as an multi-line field. The
purpose is the same. In my opinion, NOTES should be declared as
depreciated, because the ADIF standard doesn't defines the concept of a
line.

Best wishes,
Claude (DJ0OT)

--
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] WSJTX user Guide

[Bob Thornton via wsjt-devel]

Having RTFM here are my comments.

2 System Requirements says time  UTC within ±1 second.   Is this good 
enough with FT8 which I believe needs an end to end error of less than 1.5 
seconds so each end ought to be within 0.75 seconds.


4.7 Colors
Somebody raised the issue of how to identify Worked Before stations. I replied 
direct that it's the green ones but from the guide and the config screen this 
is not  made clear.
From program behaviour I believe the label for Green should be "CQ Worked B4" 
and the Purple and Magenta should also have CQ in front of their descriptions.
For me the Green is too bright a choice for something that should be of low 
interest, and should be Grey ( or Gray) to be in line with  JTALERT but since 
it is re-configurable I guess it is a personal choice.

7.1 "I" paragraph has information on sensitivity of JT9 and JT65 but nothing 
for FT8.

8.1 VHF setup. Should this section remind us that the decoder will only spot 
one signal at a time" when in "VHF mode". I had missed that point in the past.

19 Utility Programs 
No mention of FT8 in this section. Should it be listed even if to say not 
available at this time.

Bob Thornton G3WKW 

--
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] ADIF log: QSLMSG field

[Claude Frantz]

On 08/05/2017 06:02 PM, Black Michael via wsjt-devel wrote:

Hi Mike & all,

> Do you mean eQSL's QSL card? 

I mean the eQSL service.

> If so, it uses the COMMENT field.  That
> field works for me on eQSL.

Please note that there is an important difference between the COMMENT
and the QSLMSG fields: In the COMMENT field, there are the comments for
myself. In the QSLMSG field, there are the comments for my QSO partner.

Further, there is a NOTES field in the ADIF spec. There is only a little
difference between the COMMENT and the NOTES fields. COMMENT is defined
as an string field and NOTES is defined as an multi-line field. The
purpose is the same. In my opinion, NOTES should be declared as
depreciated, because the ADIF standard doesn't defines the concept of a
line.

Best wishes,
Claude (DJ0OT)

--
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] ADIF log: QSLMSG field

[Black Michael via wsjt-devel]

Do you mean eQSL's QSL card?  If so, it uses the COMMENT field.  That field 
works for me on eQSL.Or do you mean some other software package?
de Mike W9MDB

  From: Claude Frantz 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Saturday, August 5, 2017 10:47 AM
 Subject: Re: [wsjt-devel] ADIF log: QSLMSG field
   
On 08/05/2017 05:05 PM, Black Michael via wsjt-devel wrote:

Hi Mike & all,

> Is there one of the logging services that uses that field?
> WSJT-X and JTAlert use the COMMENT field as does QRZ and eQSL.
> 
> So why QSLMSG?

At my knowledge, eQSL is using it. This field is important for the
software which create the QSL card.

Best whishes,
Claude (DJ0OT)

--
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

Re: [wsjt-devel] ADIF log: QSLMSG field

[Claude Frantz]

On 08/05/2017 05:05 PM, Black Michael via wsjt-devel wrote:

Hi Mike & all,

> Is there one of the logging services that uses that field?
> WSJT-X and JTAlert use the COMMENT field as does QRZ and eQSL.
> 
> So why QSLMSG?

At my knowledge, eQSL is using it. This field is important for the
software which create the QSL card.

Best whishes,
Claude (DJ0OT)

--
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] Slider values

[charlie]

Hi Mike

Installed and working here.  Having numerical values easily available
would make it easier to recommend settings to other folks, for particular
applications.

73

Charlie

> Add slider values while pressing or changing slider values on widegraph
> and fastgraph.
> https://www.dropbox.com/s/sl2hwlt2me63yfu/slider.patch?dl=1
>
> de Mike
> W9MDB--
> 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

Re: [wsjt-devel] ADIF log: QSLMSG field

[Black Michael via wsjt-devel]

Is there one of the logging services that uses that field?WSJT-X and JTAlert 
use the COMMENT field as does QRZ and eQSL.
So why QSLMSG?
de Mike W9MDB


  From: Claude Frantz 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Saturday, August 5, 2017 9:50 AM
 Subject: [wsjt-devel] ADIF log: QSLMSG field
   
Hi Bill & all,

I suggest to add the QSLMSG field in the logging window and in the ADIF
log record. I think that the reason is easy to understand.

Thanks !

Best wishes,
Claude (DJ0OT)

--
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] Slider values

[Black Michael via wsjt-devel]

Add slider values while pressing or changing slider values on widegraph and 
fastgraph.
https://www.dropbox.com/s/sl2hwlt2me63yfu/slider.patch?dl=1

de Mike W9MDB--
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] ADIF log: QSLMSG field

[Claude Frantz]

Hi Bill & all,

I suggest to add the QSLMSG field in the logging window and in the ADIF
log record. I think that the reason is easy to understand.

Thanks !

Best wishes,
Claude (DJ0OT)

--
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] WSJT-X manual

[Bill Somerville]

On 05/08/2017 11:06, Alessandro Gorobey via wsjt-devel wrote:
in manual r8003 in section "12.2. Decoded Lines"for FT8 is missed the 
"?" simbol description
I see in ALL.TXT a lot of lines with "a1", but some also with "? a1" 
as in follow


084830 -21  0.1  939 ~  CQ DL1KSW JO30 a1
084830 -23  0.2 1013 ~  CQ DL9SUB JO53   ? a1

In the manual there is a full description of -r --rig-name option, but 
no note on -c --config


By the way referring to big success of FT8 in line 113 of main.cpp FT8 
is missed. See wsjtx --help 


Hi Sandro,

the '?' lower confidence decode marker is described in the "AP Decoding" 
section just above.


I have made the other changes you have suggested, thanks!

73
Bill
G4WJS.


--
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] WSJT-X manual

[Alessandro Gorobey via wsjt-devel]

Hi,

in manual r8003 in section "12.2. Decoded Lines"for FT8 is missed the 
"?" simbol description
I see in ALL.TXT a lot of lines with "a1", but some also with "? a1" as 
in follow


084830 -21  0.1  939 ~  CQ DL1KSW JO30 a1
084830 -23  0.2 1013 ~  CQ DL9SUB JO53   ? a1

In the manual there is a full description of -r --rig-name option, but 
no note on -c --config


By the way referring to big success of FT8 in line 113 of main.cpp FT8 
is missed. See wsjtx --help



--
73
Sandro
IW3RAB

--
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] Feature request - sticky reports

[Charles Suckling]

Hi Gary

I think yours is a different requirement.  

On EME, some operators prefer to receive the same report every transmission.
This probably comes from experience with correlation decoding, where under
marginal conditions the decoder may produce flagged low confidence decodes.
Standard practice has been, if the receiving operator is uncertain, to wait
for another decode as confirmation before proceeding to a R report message
or RRR. 

73

Charlie

-Original Message-
From: Gary McDuffie [mailto:mcduf...@ag0n.net] 
Sent: 04 August 2017 18:55
To: WSJT software development
Subject: Re: [wsjt-devel] Feature request - sticky reports


> On Aug 4, 2017, at 1:37 AM, Charles Suckling
 wrote:
> 
> The subject of sticky reports has already come up.  It seems desirable
(from user feedback)  if the first decoded report could be used in all
subsequent messages in that QSO,  to avoid confusion over existing practice
where the sent report does not change as the QSO progresses.

I'm not involved in EME, but I've often wished that when the signal report
is given more than once, it would send the highest report to that point.  In
other words, if the signal went from -12 to -10 before it was acknowledged,
the -10 would be the official report and put in the log that way.  This
could be the case for all modes, I assume.  I don't know if this would cause
a problem, but I thought I would mention it in relation to your post.

Gary - AG0N

--
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

Re: [wsjt-devel] Pulled back on 73

[Mark Turner via wsjt-devel]

Hi Jim,

I concur re habitually unchecking "Lock Tx=Rx" when sending Tx6 ("CQ") - 
I curse myself when I've forgotten to do it and someone calls me split, 
consequently finding myself dragged off to their qrg. Calling cq and 
then accidentally leaving the original qrg seems to be considerably more 
disruptive (especially when running a pileup) than accidentally replying 
in "split mode" to someone else's CQ.


Regards, Mark

PS Glad to see there are attempts to make FT8 auto-sequencing more 
"context sensitive" - it's discussed elsewhere but I've also seen bad 
sequencing and mis-logs due to unfortunate non-related (but perhaps 
close qrg) decodes.


Currently WSJT-X v1.8.0-rc2 r7996


On 04/08/2017 14:26, James Shaver (N2ADV) wrote:

Thanks, Bill!  I typically keep the box unchecked myself when calling CQ but I 
know there are folks who find it handy.

Appreciate the peek!

Jim S.
N2ADV


On Aug 3, 2017, at 9:32 PM, Bill Somerville  wrote:


On 04/08/2017 02:22, James Shaver (N2ADV) wrote:
I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he responded to me, 
we went through the sequence, he sent his 73 and then moved off to call CQ elsewhere on 
the band. Unfortunately, my 73 pulled his TX back to where I was causing him to 
accidentally start calling CQ where he had just answered me. Would it be simple to have 
the TX not be pulled back upon receipt of the 73?  I know he could have unchecked 
"Call 1st" and avoided being pulled back but then if someone had answered him 
after calling CQ, he would have to manually answer.

Hi Jim,

I can reproduce that behaviour if I have him with "Lock Tx=Rx" checked. The more use 
cases I test with auto-sequencing the more I am growing to dislike "Lock Tx=Rx".

I will see if I can work out how to stop this sort of thing happening.

73
Bill
G4WJS.


--
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



--
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