[wsjt-devel] Clock patch

[Black Michael via wsjt-devel]

This patch shows a message if 80% of DT values are >= 0.5 seconds.
https://www.dropbox.com/s/8j7qao9wa4wmzdm/clock.patch?dl=1

I picked the 50% point of FT4's 1 second tolerance but perhaps a slightly 
larger value might be appropriate.
I think most, if not everybody, can get the > 20% < 0.5 seconds without a 
problem.
Even with my rather extreme latency of 300-400ms I don't trigger this.
de Mike W9MDB

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Rich Zwirko - K1HTV]

Your suggestion does not  work here with Windows 7.  I tried simply typing
"ALL.TXT" in the search window but the file, which resides in
AppData/Local/WSJT-X, is not found.

Your suggestion of using "FIND" does not allow the user to easily browse
through the ALL.TXT file, which is what I want to be able to do and can do
easily in the monthly files that I manually archive. What good is a
humongous ALL.TXT file to a WSJT-X user if he can't easily browse through
it?

I was told by another local FT8 user that JTDX does what I have requested,
that is archiving ALL.TXT files in separate monthly files. He also informed
me that my other request that Red/Green colors be used in the 15 second
count up bar also already exists in the JTDX software.

73,
Rich - K1HTV

= = =

From: Black Michael 
To: WSJT 
Cc:
Bcc:
Date: Tue, 25 Jun 2019 14:05:11 + (UTC)
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives
On Windows:

find "K1HTV" ALL.TXT | find "S92HP"
190611_06190014.074 Rx FT8-17  0.1 2393 S92HP K1HTV -11
190611_06203014.074 Rx FT8-15  0.1 1106 S92HP K1HTV -11
190611_06210014.074 Rx FT8-17  0.4 1107 S92HP K1HTV -11
190611_06214514.074 Rx FT8-17  0.4 1106 S92HP K1HTV -11
190611_06220014.074 Rx FT8-15  0.4 1107 S92HP K1HTV RR73
190611_06223014.074 Rx FT8-15  0.4 1107 S92HP K1HTV RR73

On Linux
grep "K1HTV" ALL.TXT | grep "S92HP"

de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Jim Nuytens via wsjt-devel]

Try Notepad++

https://notepad-plus-plus.org/


---
This email has been checked for viruses by AVG.
https://www.avg.com



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Please remove me from your mailing list.

[rjai...@gmail.com]

I believe simply replying “unsubscribe” will also do the trick

Ria
N2RJ

On Tue, Jun 25, 2019 at 4:20 PM James Shaver  wrote:

> You need to click on the link at the bottom of every email from this list
> to unsubscribe.
>
> 73,
>
> Jim S.
> N2ADV
>
> On Jun 25, 2019, at 1:58 PM, James Buffington 
> wrote:
>
> j...@jimbuffington.com
> ___
>
> *IN GOD WE TRUST*
>
> "The Ultimate in Website Design for Exceptional Clients"
>
> Thorns may hurt you, men desert you, sunlight turn to fog; but you're
> never friendless ever, if you have a dog. - *Douglas Malloch*
>
>
> 662-813-3145
> j i...@jimbuffington.com
>
> *CONFIDENTIALITY DISCLAIMER*
> This email (including attachments) is confidential information protected
> by the Electronic Communications Privacy Act 18 U.S.C. §2510-2521 and any
> other applicable law, and may not be opened or forwarded without consent of
> the named recipient(s). It is intended only for the use of the individual
> or entity named herein. If the reader of this message is not the intended
> recipient, or the employee or agent responsible to deliver it to the
> intended recipient, you are hereby notified that any retention,
> dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error, please
> immediately notify us by return email. Thank you.
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Please remove me from your mailing list.

[James Shaver]

You need to click on the link at the bottom of every email from this list to 
unsubscribe. 

73,

Jim S. 
N2ADV

> On Jun 25, 2019, at 1:58 PM, James Buffington  wrote:
> 
> j...@jimbuffington.com 
> ___
> 
> IN GOD WE TRUST
> 
> "The Ultimate in Website Design for Exceptional Clients"
> 
> Thorns may hurt you, men desert you, sunlight turn to fog; but you're never 
> friendless ever, if you have a dog. - Douglas Malloch
> 
> 662-813-3145
> j...@jimbuffington.com
> 
> CONFIDENTIALITY DISCLAIMER 
> This email (including attachments) is confidential information protected by 
> the Electronic Communications Privacy Act 18 U.S.C. §2510-2521 and any other 
> applicable law, and may not be opened or forwarded without consent of the 
> named recipient(s). It is intended only for the use of the individual or 
> entity named herein. If the reader of this message is not the intended 
> recipient, or the employee or agent responsible to deliver it to the intended 
> recipient, you are hereby notified that any retention, dissemination, 
> distribution or copying of this communication is strictly prohibited. If you 
> have received this communication in error, please immediately notify us by 
> return email. Thank you.
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Please remove me from your mailing list.

[James Buffington]

j...@jimbuffington.com
___

*IN GOD WE TRUST*

"The Ultimate in Website Design for Exceptional Clients"

Thorns may hurt you, men desert you, sunlight turn to fog; but you're never
friendless ever, if you have a dog. - *Douglas Malloch*


662-813-3145
j i...@jimbuffington.com

*CONFIDENTIALITY DISCLAIMER*
This email (including attachments) is confidential information protected by
the Electronic Communications Privacy Act 18 U.S.C. §2510-2521 and any
other applicable law, and may not be opened or forwarded without consent of
the named recipient(s). It is intended only for the use of the individual
or entity named herein. If the reader of this message is not the intended
recipient, or the employee or agent responsible to deliver it to the
intended recipient, you are hereby notified that any retention,
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
immediately notify us by return email. Thank you.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Sam W2JDB via wsjt-devel]

Hi, I recompiled the program with "openread" and "sharedenynone" but it seems 
that when wsjtx attempts to append to the file I received the same error 
message.  BTW, I open the file and close the file as soon as I finish scanning 
the file. It is only at the end of the decode when wsjtx is attempting to 
append to the file while alltext.exe is still parsing the file that the error 
pops up. If the scan finishes before wsjtx attempts to append to the file, 
there is no error.  Sorry, but that is the best that I can do. As I posted 
before, I do not use the alltext.exe while wsjtx is running. Sam W2JDB
  -Original Message-
From: DG2YCB, Uwe 
To: 'WSJT software development' 
Sent: Tue, Jun 25, 2019 12:13 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives

#yiv6314331436 #yiv6314331436 -- _filtered #yiv6314331436 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv6314331436 
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} #yiv6314331436 
#yiv6314331436 p.yiv6314331436MsoNormal, #yiv6314331436 
li.yiv6314331436MsoNormal, #yiv6314331436 div.yiv6314331436MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New;} 
#yiv6314331436 a:link, #yiv6314331436 span.yiv6314331436MsoHyperlink 
{color:blue;text-decoration:underline;} #yiv6314331436 a:visited, 
#yiv6314331436 span.yiv6314331436MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;} #yiv6314331436 
p.yiv6314331436MsoAcetate, #yiv6314331436 li.yiv6314331436MsoAcetate, 
#yiv6314331436 div.yiv6314331436MsoAcetate 
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;} #yiv6314331436 
span.yiv6314331436E-MailFormatvorlage17 {color:#1F497D;} #yiv6314331436 
span.yiv6314331436SprechblasentextZchn {} #yiv6314331436 
.yiv6314331436MsoChpDefault {} _filtered #yiv6314331436 {margin:70.85pt 70.85pt 
2.0cm 70.85pt;} #yiv6314331436 div.yiv6314331436WordSection1 {} #yiv6314331436 
Sam,alltext.exe works great, BUT there is one big disadvantage: Once the 
ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by Windows. 
And due to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because 
the file is in use (see screen shot). Is there a fix for this (or any 
workaround)? I don’t know why, but the normal Windows editor does not lock the 
ALL.txt. file like alltxt.exe does.    73 de Uwe, DG2YCB     Von: Sam W2JDB via 
wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Gesendet: Dienstag, 25. Juni 2019 16:07
An: wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB
Betreff: Re: [wsjt-devel] Monthly ALL.TXT archives  Hi Rich, IN the QLOGBeta 
file folder is a program called alltext.exe.I use it to search the all.txt 
file. It has various filters and presents only the lines that meet the 
criteria. I use that when I need to confirm what I think is an incomplete QSO. 
Try it. Its pretty fast.  73,  Sam W2JDB    -Original Message-
From: Rich Zwirko - K1HTV 
To: WSJT 
Sent: Tue, Jun 25, 2019 10:00 am
Subject: [wsjt-devel] Monthly ALL.TXT archivesRecently, a WSJT-X users asked me 
how to check if a QSO was actually completed. He had received a request to 
confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He 
got back to me later saying that the file size was enormous and too large for 
any of his text editors to read.   Monthly, I edit my ALL.TXT file and manually 
archive the decoded data for future use. These files have been used a number of 
times to confirm QSOs when a station that I work, usually a DXpedition, says 
I'm not in the log and I know that it was a solid QSO. I excerpt the decodes, 
showing responses to me and others, attaching the info to an email that is sent 
to him.  Unless it is kept to a reasonable size, the ALL.TXT will be useless to 
most WSJT-X ops who want to check it. Why not archive the lines of decoded data 
into a file with a file name reflecting the month that the data was decoded, 
such as:  2019-06ALL.TXT  I believe that this change should be seriously 
considered in a future release of WSJT-X.  73,Rich - K1HTV    
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Sam W2JDB via wsjt-devel]

Hi Bill, Done. Thanks.   73,  Sam W2JDB
  -Original Message-
From: Bill Somerville 
To: wsjt-devel 
Sent: Tue, Jun 25, 2019 12:58 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives

On 25/06/2019 17:50, Sam W2JDB via wsjt-devel wrote:
> I had to remove it from SourceForge as my program is not open source
> And I could not figure out how to delete the project from there.

Hi Sam,

https://sourceforge.net/p/forge/documentation/How%20to%20Remove%20a%20Project/

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Sam W2JDB via wsjt-devel]

Hi, Never used alltext.exe while wsjtx was running so I never ran into this 
problem. I will look into changing that. Will be going on holiday but will see 
if I can update the program before I leave. Will let you know if I did manage 
to do that. 73,  Sam W2JDB
  -Original Message-
From: DG2YCB, Uwe 
To: 'WSJT software development' 
Sent: Tue, Jun 25, 2019 12:13 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives

#yiv6314331436 #yiv6314331436 -- _filtered #yiv6314331436 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv6314331436 
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;} #yiv6314331436 
#yiv6314331436 p.yiv6314331436MsoNormal, #yiv6314331436 
li.yiv6314331436MsoNormal, #yiv6314331436 div.yiv6314331436MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New;} 
#yiv6314331436 a:link, #yiv6314331436 span.yiv6314331436MsoHyperlink 
{color:blue;text-decoration:underline;} #yiv6314331436 a:visited, 
#yiv6314331436 span.yiv6314331436MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;} #yiv6314331436 
p.yiv6314331436MsoAcetate, #yiv6314331436 li.yiv6314331436MsoAcetate, 
#yiv6314331436 div.yiv6314331436MsoAcetate 
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;} #yiv6314331436 
span.yiv6314331436E-MailFormatvorlage17 {color:#1F497D;} #yiv6314331436 
span.yiv6314331436SprechblasentextZchn {} #yiv6314331436 
.yiv6314331436MsoChpDefault {} _filtered #yiv6314331436 {margin:70.85pt 70.85pt 
2.0cm 70.85pt;} #yiv6314331436 div.yiv6314331436WordSection1 {} #yiv6314331436 
Sam,alltext.exe works great, BUT there is one big disadvantage: Once the 
ALL.txt file is opened with alltext.exe, the ALL.TXT file is locked by Windows. 
And due to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because 
the file is in use (see screen shot). Is there a fix for this (or any 
workaround)? I don’t know why, but the normal Windows editor does not lock the 
ALL.txt. file like alltxt.exe does.    73 de Uwe, DG2YCB     Von: Sam W2JDB via 
wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Gesendet: Dienstag, 25. Juni 2019 16:07
An: wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB
Betreff: Re: [wsjt-devel] Monthly ALL.TXT archives  Hi Rich, IN the QLOGBeta 
file folder is a program called alltext.exe.I use it to search the all.txt 
file. It has various filters and presents only the lines that meet the 
criteria. I use that when I need to confirm what I think is an incomplete QSO. 
Try it. Its pretty fast.  73,  Sam W2JDB    -Original Message-
From: Rich Zwirko - K1HTV 
To: WSJT 
Sent: Tue, Jun 25, 2019 10:00 am
Subject: [wsjt-devel] Monthly ALL.TXT archivesRecently, a WSJT-X users asked me 
how to check if a QSO was actually completed. He had received a request to 
confirm a QSO which was not in his log. I pointed him at the ALL.TXT file. He 
got back to me later saying that the file size was enormous and too large for 
any of his text editors to read.   Monthly, I edit my ALL.TXT file and manually 
archive the decoded data for future use. These files have been used a number of 
times to confirm QSOs when a station that I work, usually a DXpedition, says 
I'm not in the log and I know that it was a solid QSO. I excerpt the decodes, 
showing responses to me and others, attaching the info to an email that is sent 
to him.  Unless it is kept to a reasonable size, the ALL.TXT will be useless to 
most WSJT-X ops who want to check it. Why not archive the lines of decoded data 
into a file with a file name reflecting the month that the data was decoded, 
such as:  2019-06ALL.TXT  I believe that this change should be seriously 
considered in a future release of WSJT-X.  73,Rich - K1HTV    
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Sam W2JDB via wsjt-devel]

Hi Bill, Thanks. Will do that shortly.  Sam W2JDB
  -Original Message-
From: Bill Somerville 
To: wsjt-devel 
Sent: Tue, Jun 25, 2019 12:58 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives

On 25/06/2019 17:50, Sam W2JDB via wsjt-devel wrote:
> I had to remove it from SourceForge as my program is not open source
> And I could not figure out how to delete the project from there.

Hi Sam,

https://sourceforge.net/p/forge/documentation/How%20to%20Remove%20a%20Project/

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Bill Somerville]

On 25/06/2019 17:50, Sam W2JDB via wsjt-devel wrote:

I had to remove it from SourceForge as my program is not open source
And I could not figure out how to delete the project from there.


Hi Sam,

https://sourceforge.net/p/forge/documentation/How%20to%20Remove%20a%20Project/

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Sam W2JDB via wsjt-devel]

Hi Bill, I had to remove it from SourceForge as my program is not open source
And I could not figure out how to delete the project from there.Very sorry 
about that. 73, Sam W2JDB
  -Original Message-
From: Bill Somerville 
To: wsjt-devel 
Sent: Tue, Jun 25, 2019 12:38 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives

 Hi Mike, 
  did you miss the ;-) 
  Yes the Groups.io forum is probably the best place to go. 
  73
 Bill
 G4WJS. 
  On 25/06/2019 17:31, Black Michael via wsjt-devel wrote:
  
   Well without knowing Sam is the author 
  And the top result has non-downloadable links. 
  https://sourceforge.net/projects/w2jdb-quicklog/
  
   
Mike 
  On Tuesday, June 25, 2019, 10:59:34 AM CDT, Bill Somerville 
 wrote:  
  
   On 25/06/2019 16:50, Black Michael via wsjt-devel wrote:
 > And where can one get that software?
 >
 > Lots of "qlog" programs out there it seems.
 >
 Hi Mike,
 
 https://lmgtfy.com/?q=w2jdb+qlog
 
 ;-)
 
 73
 Bill
 G4WJS.
 
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Bill Somerville]

Hi Mike,

did you miss the ;-)

Yes the Groups.io forum is probably the best place to go.

73
Bill
G4WJS.

On 25/06/2019 17:31, Black Michael via wsjt-devel wrote:

Well without knowing Sam is the author

And the top result has non-downloadable links.

https://sourceforge.net/projects/w2jdb-quicklog/


Mike

On Tuesday, June 25, 2019, 10:59:34 AM CDT, Bill Somerville 
 wrote:



On 25/06/2019 16:50, Black Michael via wsjt-devel wrote:
> And where can one get that software?
>
> Lots of "qlog" programs out there it seems.
>
Hi Mike,

https://lmgtfy.com/?q=w2jdb+qlog

;-)

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Black Michael via wsjt-devel]

Well without knowing Sam is the author
And the top result has non-downloadable links.
https://sourceforge.net/projects/w2jdb-quicklog/


 Mike
On Tuesday, June 25, 2019, 10:59:34 AM CDT, Bill Somerville 
 wrote:  
 
 On 25/06/2019 16:50, Black Michael via wsjt-devel wrote:
> And where can one get that software?
>
> Lots of "qlog" programs out there it seems.
>
Hi Mike,

https://lmgtfy.com/?q=w2jdb+qlog

;-)

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[DG2YCB, Uwe]

Sam,

alltext.exe works great, BUT there is one big disadvantage: Once the ALL.txt 
file is opened with alltext.exe, the ALL.TXT file is locked by Windows. And due 
to that WSJT-X is showing error messages “Cannot open …ALL.TXT” because the 
file is in use (see screen shot). Is there a fix for this (or any workaround)? 
I don’t know why, but the normal Windows editor does not lock the ALL.txt. file 
like alltxt.exe does.

 



 

73 de Uwe, DG2YCB 

 

 

Von: Sam W2JDB via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Gesendet: Dienstag, 25. Juni 2019 16:07
An: wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB
Betreff: Re: [wsjt-devel] Monthly ALL.TXT archives

 

Hi Rich,

 

IN the QLOGBeta file folder is a program called alltext.exe.

I use it to search the all.txt file. It has various filters and presents only 
the lines that meet the criteria. I use that when I need to confirm what I 
think is an incomplete QSO. Try it. Its pretty fast. 

 

73, 

 

Sam W2JDB

 

 

 

-Original Message-
From: Rich Zwirko - K1HTV 
To: WSJT 
Sent: Tue, Jun 25, 2019 10:00 am
Subject: [wsjt-devel] Monthly ALL.TXT archives

Recently, a WSJT-X users asked me how to check if a QSO was actually completed. 
He had received a request to confirm a QSO which was not in his log. I pointed 
him at the ALL.TXT file. He got back to me later saying that the file size was 
enormous and too large for any of his text editors to read. 

 

Monthly, I edit my ALL.TXT file and manually archive the decoded data for 
future use. These files have been used a number of times to confirm QSOs when a 
station that I work, usually a DXpedition, says I'm not in the log and I know 
that it was a solid QSO. I excerpt the decodes, showing responses to me and 
others, attaching the info to an email that is sent to him.

 

Unless it is kept to a reasonable size, the ALL.TXT will be useless to most 
WSJT-X ops who want to check it. Why not archive the lines of decoded data into 
a file with a file name reflecting the month that the data was decoded, such as:

 

2019-06ALL.TXT

 

I believe that this change should be seriously considered in a future release 
of WSJT-X.

 

73,

Rich - K1HTV

 

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Receiving/Transmitting colored indicator

[Don AA5AU]

 I second this recommendation. I also use my phone (and tablet) to work FT8 
remotely with Real VNC. WSJT-X is great when viewed on the tablet but not so 
great on the phone with the smaller screen. The changes Rich asks for certainly 
would help.
Thanks,Don AA5AU
On Tuesday, June 25, 2019, 09:28:31 AM CDT, Rich Zwirko - K1HTV 
 wrote:  
 
 I often use my Android phone with Real VNC to make FT8 QSOs when I'm not in 
the shack. But with its small screen, the WSJT-X screen must be enlarged in 
order to read what is on the screen. Its important to know the progress of the 
TX/RX sequences. But when zoomed in on the lower right hand of the WSJT-X 
screen, there is no easy way to tell if I'm in the TX or RX sequence. The 
colored "Receiving/Transmitting" bar in the lower left corner or the screen can 
not be seen unless the focus is moved to the left with the touch screen.
A suggestion to consider regarding the WSJT-X screen:Change the color of the 12 
segment progress bar on the lower right side of the screen from always blue to 
alternating between Green when receiving, Red when the user is transmitting, 
and gray or blue when the program is processing data or when monitoring has 
been turned off.
Another request is to move the Date/Time clock to the right of its present 
position. This also would help the folks who use small phones or tablets which 
require zooming in to view.
73,Rich - K1HTV___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Bill Somerville]

On 25/06/2019 16:50, Black Michael via wsjt-devel wrote:

And where can one get that software?

Lots of "qlog" programs out there it seems.


Hi Mike,

https://lmgtfy.com/?q=w2jdb+qlog

;-)

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Black Michael via wsjt-devel]

And where can one get that software?
Lots of "qlog" programs out there it seems.
de Mike W9MDB


 

On Tuesday, June 25, 2019, 09:40:52 AM CDT, Sam W2JDB via wsjt-devel 
 wrote:  
 
 Hi Rich, IN the QLOGBeta file folder is a program called alltext.exe.I use it 
to search the all.txt file. It has various filters and presents only the lines 
that meet the criteria. I use that when I need to confirm what I think is an 
incomplete QSO. Try it. Its pretty fast.  73,  Sam W2JDB

  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-devel Digest, Vol 64, Issue 149

[Al Pawlowski]

I like the idea of a built in “Time Fudge” like function that would adjust WSJT 
timing relative to the PC clock, rather than the PC clock itself - a +- few 
seconds and 100ms resolution would be enough.

It is easy enough to see from a window of decodes how much you might be off and 
you might want to purposely make yourself off to work someone special who is 
off too much to work if you are on.


Al Pawlowski, K6AVP
Los Osos, CA USA



> On Jun 24, 2019, at 21:45, wsjt-devel-requ...@lists.sourceforge.net wrote:
> 
> Date: Tue, 25 Jun 2019 07:45:31 +0300
> From: Sergio Yes UT9LI mailto:ut...@ukr.net>>
> To: WSJT software development  >
> Subject: Re: [wsjt-devel] Field Day time problem
> Message-ID: <1561437914.611645000.726w1...@frv55.fwdcdn.com 
> >
> Content-Type: text/plain; charset="utf-8"
> 
> Adjustment dT can be organized in the program itself. Discarding values, for 
> example, dT greater than 0.7, calculate the average value of dT over all 
> accepted values ??in the "callLog" list and automatically enter this value by 
> analogy with the "+/- dT" button. In this case, the operator will generally 
> forget about the synchronization parameter (except in the case of a start, 
> when on Band call "NO!".

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question for WSJT-X Programmers re: Tx power logging

[Al Pawlowski]

How about the log function saving the last power setting per band vs just last 
regardless of band as it does now. That would help me (and probably quite a few 
others) a lot as I usually do not change power once set on a band, but have 
varying levels per band because of equipment capability, wanted QSO’s and 
propagation.

Al Pawlowski, K6AVP
Los Osos, CA USA



> On Jun 24, 2019, at 20:11, wsjt-devel-requ...@lists.sourceforge.net wrote:
> 
> Date: Mon, 24 Jun 2019 22:21:36 +0100
> From: Bill Somerville mailto:g4...@classdesign.com>>
> To: wsjt-devel@lists.sourceforge.net 
> Subject: Re: [wsjt-devel] Question for WSJT-X Programmers re: Tx power
>   logging
> Message-ID:  >
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 24/06/2019 18:46, Dave Slotter wrote:
>> I was wondering, if WSJT-X uses HamLib, and at least some rigs are 
>> capable of setting and getting the transmit power, why do users have 
>> to fill in the Log QSO Field, "Tx power", manually? Is there a reason 
>> for not implementing this feature?
> 
> Hi Dave,
> 
> the main reason is inaccuracy. Using AFSK modes allows the power to be 
> controlled in many ways including using the audio level into the rig. 
> The power setting on the rig may have little bearing on the actual 
> radiated power. The rigs that allow metering the power leaving the 
> transceiver PA could be more accurate but require constant polling of 
> the Tx power meter level while transmitting. Even if the above were not 
> an issue, an individual station may be using a PA after the transceiver. 
> In summary, the user has a much better idea of the radiated power than 
> any indirect measurement available via CAT commands.
> 
> For a counter example, measuring SNR of received signals is far more 
> deterministic and reliable and we happily support that as an automated 
> feature in the WSJT-X modes.
> 
> 73
> Bill
> G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Sam W2JDB via wsjt-devel]

Hi Rich, IN the QLOGBeta file folder is a program called alltext.exe.I use it 
to search the all.txt file. It has various filters and presents only the lines 
that meet the criteria. I use that when I need to confirm what I think is an 
incomplete QSO. Try it. Its pretty fast.  73,  Sam W2JDB
  -Original Message-
From: Rich Zwirko - K1HTV 
To: WSJT 
Sent: Tue, Jun 25, 2019 10:00 am
Subject: [wsjt-devel] Monthly ALL.TXT archives

Recently, a WSJT-X users asked me how to check if a QSO was actually completed. 
He had received a request to confirm a QSO which was not in his log. I pointed 
him at the ALL.TXT file. He got back to me later saying that the file size was 
enormous and too large for any of his text editors to read.
Monthly, I edit my ALL.TXT file and manually archive the decoded data for 
future use. These files have been used a number of times to confirm QSOs when a 
station that I work, usually a DXpedition, says I'm not in the log and I know 
that it was a solid QSO. I excerpt the decodes, showing responses to me and 
others, attaching the info to an email that is sent to him.
Unless it is kept to a reasonable size, the ALL.TXT will be useless to most 
WSJT-X ops who want to check it. Why not archive the lines of decoded data into 
a file with a file name reflecting the month that the data was decoded, such as:
2019-06ALL.TXT
I believe that this change should be seriously considered in a future release 
of WSJT-X.
73,Rich - K1HTV


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Receiving/Transmitting colored indicator

[Rich Zwirko - K1HTV]

I often use my Android phone with Real VNC to make FT8 QSOs when I'm not in
the shack. But with its small screen, the WSJT-X screen must be enlarged in
order to read what is on the screen. Its important to know the progress of
the TX/RX sequences. But when zoomed in on the lower right hand of the
WSJT-X screen, there is no easy way to tell if I'm in the TX or RX
sequence. The colored "Receiving/Transmitting" bar in the lower left corner
or the screen can not be seen unless the focus is moved to the left with
the touch screen.

A suggestion to consider regarding the WSJT-X screen:
Change the color of the 12 segment progress bar on the lower right side of
the screen from always blue to alternating between *Green* when receiving, *Red
*when the user is transmitting, and gray or blue when the program is
processing data or when monitoring has been turned off.

Another request is to move the Date/Time clock to the right of its present
position. This also would help the folks who use small phones or tablets
which require zooming in to view.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Black Michael via wsjt-devel]

On Windows:
find "K1HTV" ALL.TXT | find "S92HP"190611_061900    14.074 Rx FT8    -17  0.1 
2393 S92HP K1HTV -11190611_062030    14.074 Rx FT8    -15  0.1 1106 S92HP K1HTV 
-11190611_062100    14.074 Rx FT8    -17  0.4 1107 S92HP K1HTV -11190611_062145 
   14.074 Rx FT8    -17  0.4 1106 S92HP K1HTV -11190611_062200    14.074 Rx FT8 
   -15  0.4 1107 S92HP K1HTV RR73190611_062230    14.074 Rx FT8    -15  0.4 
1107 S92HP K1HTV RR73
On Linuxgrep "K1HTV" ALL.TXT | grep "S92HP"
de Mike W9MDB 

On Tuesday, June 25, 2019, 09:01:02 AM CDT, Rich Zwirko - K1HTV 
 wrote:  
 
 Recently, a WSJT-X users asked me how to check if a QSO was actually 
completed. He had received a request to confirm a QSO which was not in his log. 
I pointed him at the ALL.TXT file. He got back to me later saying that the file 
size was enormous and too large for any of his text editors to read.
Monthly, I edit my ALL.TXT file and manually archive the decoded data for 
future use. These files have been used a number of times to confirm QSOs when a 
station that I work, usually a DXpedition, says I'm not in the log and I know 
that it was a solid QSO. I excerpt the decodes, showing responses to me and 
others, attaching the info to an email that is sent to him.
Unless it is kept to a reasonable size, the ALL.TXT will be useless to most 
WSJT-X ops who want to check it. Why not archive the lines of decoded data into 
a file with a file name reflecting the month that the data was decoded, such as:
2019-06ALL.TXT
I believe that this change should be seriously considered in a future release 
of WSJT-X.
73,Rich - K1HTV


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Monthly ALL.TXT archives

[Rich Zwirko - K1HTV]

Recently, a WSJT-X users asked me how to check if a QSO was actually
completed. He had received a request to confirm a QSO which was not in his
log. I pointed him at the ALL.TXT file. He got back to me later saying that
the file size was enormous and too large for any of his text editors to
read.

Monthly, I edit my ALL.TXT file and manually archive the decoded data for
future use. These files have been used a number of times to confirm QSOs
when a station that I work, usually a DXpedition, says I'm not in the log
and I know that it was a solid QSO. I excerpt the decodes, showing
responses to me and others, attaching the info to an email that is sent to
him.

Unless it is kept to a reasonable size, the ALL.TXT will be useless to most
WSJT-X ops who want to check it. Why not archive the lines of decoded data
into a file with a file name reflecting the month that the data was
decoded, such as:

2019-06ALL.TXT

I believe that this change should be seriously considered in a future
release of WSJT-X.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Field Day time problem

[Lee. KX4TT via wsjt-devel]

Gm All, 

 

Ideally, you would have a read-through of the manual and help from an 
experienced op. At the Tampa ARC, we have several rigs available, with a pdf of 
the operating manuals available on the computer at each position. With new ops, 
I like to show them the features of the radio - while the new op is the 
operator of said rig -  we would have the pdf pulled up and set to the relevant 
page. You get tactile training, visual training, and aural training as the op 
can hear the results of the changes they make to the rig. That way we avoid the 
Amateur Extra who cannot turn on a radio (yes, it happened to me; I had a new 
AE ask me how to turn on a radio). 

 

Michael, it is really not asking too much of an experienced op to read their 
manual, period. After reading, if they don’t understand – or are simply not 
sure about - what they’ve read, the puzzled op can access YouTube, send 
messages to great user groups such as this one, get on the local repeater with 
their buddies, call a friend, check with the local club, ad infinitum -  and 
get an answer; not always the best answer or even the correct one, but an 
answer nonetheless -)   … 

 

Your first step should be to “ read the ___ manual”  (you can place a rude 
adjective in front of manual if you wish)

 

73 de Lee KX4TT

 

From: Fred Price [mailto:n...@hotmail.com] 
Sent: Tuesday, 25 June, 2019 08:57 
To: Black Michael ; WSJT software development 

Subject: Re: [wsjt-devel] Field Day time problem

 

Michael, 

I been teaching other hams for a lot of years. I been a ham for 34+ years. 
Sorry but I disagree about reading the manual. Almost at least if not more then 
75% of questions I'm asked are in the manual and or any release notes and yes I 
read everything that the WSJT dev group puts out.

I could go on but I feel this list isn't the place to do this.

Thanks,

Fred

N2XK

 

 

On Jun 25, 2019 8:06 AM, Black Michael via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

It's completely reasonable (or should I say expected) that when one installs 
software that it "works".  In particular for the common operating mode.

I've found the most you can expect from an operator with 40+ years of ops is 
that they know how to turn on their rig and plug in cables.  They will know 
nothing about how to do any audio settings, bandwidth, data rates, serial 
ports, CAT control, timing requirements, never seen a waterfall, and have no 
real understanding of suppressed carrier audio.there's lots to learn if all 
you've ever done is phone & CW.

 

It should not require a user to read (and completely understand) a  25,000-word 
manual -- that's asking and expecting far too much.

 

Try taking a teaching attitude -- if there's something you can teach the 
operator that's one of the major goals of this hobby and life in general.

 

So my idea is simply to give the user an indication when their time is 
obviously off and educate them in the hopes that they will then educate others.

 

de Mike W9MDB

 

 

 

 

 

 

On Tuesday, June 25, 2019, 06:52:55 AM CDT, Fred Price mailto:n...@hotmail.com> > wrote: 

 

 

Because it seems a lot of ops want a set it and forget it piece of software. 
The things I read on this list that ops want WSJT to do amazes me.

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net  
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net  
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Field Day time problem

[Lee. KX4TT via wsjt-devel]

GM,

 

The Tampa ARC used Ublox8 GPS dongles and software (which allows for syncing 
either by dongle or NTP Server) to sync to the GPS sats during the contest for 
two stations; the third synced to WWV by ear and still stayed pretty close. $16 
each from Amazon for the dongles is a real bargain…..

 

73 de Lee KX4TT

 

 

 

From: Dave Slotter, W3DJS [mailto:slotter+w3...@gmail.com] 



 

The operators on my station alerted me that my station's clock was off by 2 
seconds, and I was more focused on fixing the issue quickly to get them back on 
track, than asking them how they noticed it!

 

I had operated before them with FT8 and I never even noticed it, despite my 
laptop syncing to NTP before the contest. Any indication from WSJT-X to check 
my clock would be welcome!

 

I made over 153 contacts on FD, all FT8.

 

-Dave

 W3DJS  

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Field Day time problem

[Dave Slotter, W3DJS]

Late to the party because I've had other things on my plate, but I like
this approach and fully support your efforts.

The operators on my station alerted me that my station's clock was off by 2
seconds, and I was more focused on fixing the issue quickly to get them
back on track, than asking them how they noticed it!

I had operated before them with FT8 and I never even noticed it, despite my
laptop syncing to NTP before the contest. Any indication from WSJT-X to
check my clock would be welcome!

I made over 153 contacts on FD, all FT8.

-Dave
 W3DJS 

On Sun, Jun 23, 2019 at 4:48 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Of all the DT drifeters I saw not one was running JTAlert.
>
> Then again highlighting the DT values > 0.5 seconds might be a better
> solution though once you get your clock set the I find the highlighting
> irritating as all highlight should be calling your attention to something.
>
> And based on watching FD today I think 80% (4 of 5) > 0.5 second might be
> the good target.
>
> Mike.
>
>
>
>
>
> On Sunday, June 23, 2019, 03:10:58 PM CDT, August Treubig <
> atreu...@sbcglobal.net> wrote:
>
>
> JTAlert already does that.   Highlights in red.
>
> Aug
> AG5AT
>
> Sent from my iPad
>
> On Jun 23, 2019, at 2:04 PM, Gary Hinson  wrote:
>
> Instead of “Your clock is off” (which, to some, may mean “Your clock is
> turned off”) I suggest “Your clock is wrong” or better still the
> action-oriented “Check your clock”.
>
>
>
> And the proposed 3 out of 5 decodes being more than half a second wrong
> risks triggering the message far too often when the band is busy,
> especially during events such as field day and DXpeditions when a greater
> proportion of ops are probably using temporary setups without atomic clock
> references.  I think a statistical test would be more appropriate, although
> I’m not sure which one (ask a statistician!).
>
>
>
> Another approach would be simply to highlight DT values that are more
> than, say, 1 second wrong in the decode panes (e.g. with red or orange
> backgrounds for minus and plus DT values), and leave the ops to notice the
> slew of reds or oranges and figure out what’s going on.  This has the
> advantage that, if we are reasonably sure of our own clocks, we might
> notice and maybe send a message to other stations whose DT values are
> highlighted.
>
>
>
> 73
>
> Gary  ZL2iFB
>
>
>
> *From:* Black Michael via wsjt-devel 
> *Sent:* 24 June 2019 00:27
> *To:* WSJT Software Development 
> *Cc:* Black Michael 
> *Subject:* [wsjt-devel] Field Day time problem
>
>
>
> I've seen about 2 dozen clubs doing Field Day where their clocks are off.
>
>
>
> We need to provide an indication in WSJT-X when clocks are off like this.
>
>
>
> With concurrence I can do a patch for thismy idea is this.
>
>
>
> At least 5 decodes where 60% or more > 0.5 seconds is an indication of bad
> timing.
>
> A message would be put in the Rx Frequency window "Your clock is off...see
> help".  With appropriate references in the Help to search "your clock is
> off" and time solutions.
>
>
>
> This doesn't cover the case where their clock is way off as they won't see
> any decodes.  The only solution for that would be doing a time query from a
> known source and I don't think we want to go that route.
>
>
>
> de Mike W9MDB
>
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Field Day time problem

[Fred Price]

Michael,
I been teaching other hams for a lot of years. I been a ham for 34+ years. 
Sorry but I disagree about reading the manual. Almost at least if not more then 
75% of questions I'm asked are in the manual and or any release notes and yes I 
read everything that the WSJT dev group puts out.
I could go on but I feel this list isn't the place to do this.
Thanks,
Fred
N2XK


On Jun 25, 2019 8:06 AM, Black Michael via wsjt-devel 
 wrote:
It's completely reasonable (or should I say expected) that when one installs 
software that it "works".  In particular for the common operating mode.
I've found the most you can expect from an operator with 40+ years of ops is 
that they know how to turn on their rig and plug in cables.  They will know 
nothing about how to do any audio settings, bandwidth, data rates, serial 
ports, CAT control, timing requirements, never seen a waterfall, and have no 
real understanding of suppressed carrier audio.there's lots to learn if all 
you've ever done is phone & CW.

It should not require a user to read (and completely understand) a  25,000-word 
manual -- that's asking and expecting far too much.

Try taking a teaching attitude -- if there's something you can teach the 
operator that's one of the major goals of this hobby and life in general.

So my idea is simply to give the user an indication when their time is 
obviously off and educate them in the hopes that they will then educate others.

de Mike W9MDB






On Tuesday, June 25, 2019, 06:52:55 AM CDT, Fred Price  wrote:


Because it seems a lot of ops want a set it and forget it piece of software. 
The things I read on this list that ops want WSJT to do amazes me.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Field Day time problem

[Black Michael via wsjt-devel]

It's completely reasonable (or should I say expected) that when one installs 
software that it "works".  In particular for the common operating mode.I've 
found the most you can expect from an operator with 40+ years of ops is that 
they know how to turn on their rig and plug in cables.  They will know nothing 
about how to do any audio settings, bandwidth, data rates, serial ports, CAT 
control, timing requirements, never seen a waterfall, and have no real 
understanding of suppressed carrier audio.there's lots to learn if all 
you've ever done is phone & CW.
It should not require a user to read (and completely understand) a  25,000-word 
manual -- that's asking and expecting far too much.
Try taking a teaching attitude -- if there's something you can teach the 
operator that's one of the major goals of this hobby and life in general.
So my idea is simply to give the user an indication when their time is 
obviously off and educate them in the hopes that they will then educate others.
de Mike W9MDB



 

On Tuesday, June 25, 2019, 06:52:55 AM CDT, Fred Price  
wrote:  
 
 Because it seems a lot of ops want a set it and forget it piece of software. 
The things I read on this list that ops want WSJT to do amazes me.


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Field Day time problem

[Fred Price]

Because it seems a lot of ops want a set it and forget it piece of software. 
The things I read on this list that ops want WSJT to do amazes me.

On Jun 25, 2019 7:31 AM, VE3FBZ  wrote:
Why add complexity/code to the software app when the problem is the user - not 
the software or the rest of the community?


 Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca




On Jun 25, 2019, at 04:51, DG2YCB, Uwe mailto:dg2...@gmx.de>> 
wrote:


The old JT65-HF Comfort had one additional feature: With “DT offset” one could 
temporally shift DT until +- 2.5 seconds (in steps of 100 ms). Very useful in 
situations where PC time sync failed, for whatever reasons. IMO would be good 
to implement something like that to WSJT-X. Not a big deal, but works 100 %.

Yes, TimeFudge could do something similar, but (A) it’s only available for 
Windows, and (B) at least for me it was sometimes difficult to see which is the 
correct system time and which is the “fudged” time (especially when one had to 
do more than one correction). With the JT65-HF Comfort functionality it was 
easy to see that. (After restarting the software it should be automatically set 
to zero again.)







73 de Uwe, DG2YCB

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Field Day time problem

[VE3FBZ]

Why add complexity/code to the software app when the problem is the user - not 
the software or the rest of the community?


 Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca 




> On Jun 25, 2019, at 04:51, DG2YCB, Uwe  wrote:
> 
> The old JT65-HF Comfort had one additional feature: With “DT offset” one 
> could temporally shift DT until +- 2.5 seconds (in steps of 100 ms). Very 
> useful in situations where PC time sync failed, for whatever reasons. IMO 
> would be good to implement something like that to WSJT-X. Not a big deal, but 
> works 100 %.
> Yes, TimeFudge could do something similar, but (A) it’s only available for 
> Windows, and (B) at least for me it was sometimes difficult to see which is 
> the correct system time and which is the “fudged” time (especially when one 
> had to do more than one correction). With the JT65-HF Comfort functionality 
> it was easy to see that. (After restarting the software it should be 
> automatically set to zero again.)
>  
> 
>  
> 73 de Uwe, DG2YCB
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel