Thanks, Joe...r8591 fixed this little "glitch".
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Thursday, March 29, 2018, 10:47:03 AM EDT, Ed Wilson via wsjt-devel
wrote:
I reverted back to r8576 and this anomaly did not appear.
Ed, K0KC
I reverted back to r8576 and this anomaly did not appear.
Ed, K0KC
k0kc@arrl.nethttp://k0kc.us/
On Thursday, March 29, 2018, 8:58:24 AM EDT, Ed Wilson via wsjt-devel
wrote:
I am currently running WSJT-X 1.9-rc3 r8590. I have set the option to have the
I am currently running WSJT-X 1.9-rc3 r8590. I have set the option to have the
program prompt me to log a QSO. I noticed this morning that upon a prompt, the
Report Rcvd field is blank and that I have to enter that value manually.
Ed, K0KC
On 12/03/2018 21:05, Louis Ricci wrote:
Just for my own information, what is the difference between wsjtx.log and
wsjtx_log.adi?
Hi Lou,
the fromer is in CSV format and is write only by WSJT-X, the latter is
in ADIF format and is read in full on WSJT-X startup to load the
in-memory worked
suggest.
Just for my own information, what is the difference between wsjtx.log and
wsjtx_log.adi?
Many thanks
73
Lou
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, March 12, 2018 4:55 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel
On 12/03/2018 20:44, Louis Ricci wrote:
It's not ALL QSOs that are show up as not previously worked, only some of
them. If I have one giant .adi file that never gets deleted, then every
time I import it into my main logger, all of those QSOs get duplicated. The
next time make some additional
?
Thanks for your support
Lou
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, March 12, 2018 4:34 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Logging Issue
On 12/03/2018 20:14, Louis Ricci wrote:
> The original .adi file are gone
On 12/03/2018 20:14, Louis Ricci wrote:
The original .adi file are gone
Hi Lou,
there is you problem then. I suggest you select all the JT9/JT65/JT9
QSOs in your main station log and export an ADIF file of them. Rename
that file wsjtx_log.adi and put it into the WSJT-X log file directory
12, 2018 4:08 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Logging Issue
On 12/03/2018 19:59, Louis Ricci wrote:
> No, it wasn't.
>
> Some examples are MI0LLG, VA3HP, K4GHS
>
> Excerpt from the log file:
>
> 2018-03-04,20:36:45,2018-03-04,20:37:45,MI0LLG,I
On 12/03/2018 19:59, Louis Ricci wrote:
No, it wasn't.
Some examples are MI0LLG, VA3HP, K4GHS
Excerpt from the log file:
2018-03-04,20:36:45,2018-03-04,20:37:45,MI0LLG,IO65,14.075858,FT8,-05,-04,,,
<== First time
2018-03-12,19:14:45,2018-03-12,19:16:15,MI0LLG,IO65,14.075369,FT8,-06,-09,,,
<==
,K4GHS,,7.075521,FT8,-16,-08,,,
<== Just noticed that Grid is missing. Could that be a factor?
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, March 12, 2018 3:45 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Logging Issue
On 12/0
On 12/03/2018 19:37, Louis Ricci wrote:
I had a QSO with that station several days ago on 20. Wondering why
wasn’t the CQ displayed in GREEN, I opened the wsjtx.log file and sure
enough, the WSO was in the file.
HI Lou,
was the offending callsign a KG4 plus three or KG4 plus one format? If
Hello,
I searched around for an answer to this issue, but could not find anything.
I made some FT-8 contacts on 20m the other day then fired up the rig again
this morning saw some stations calling CQ. I noticed a call that was
displayed in Deep purple, so even though it looked familiar, I
13 matches
Mail list logo