Re: [wsjt-devel] Guantanamo

On 12/03/2018 21:00, Pino Zollo wrote: KG4W appears as USA in violet as if it were a new one and keeps being printed in violet also after having been saved at log. V. 1.9.0-rc2 73 Pino ZP4KFX Hi Pino, understood, this defect has been repaired for the next release. 73 Bill G4WJS.

Re: [wsjt-devel] Logging Issue

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

Re: [wsjt-devel] Logging Issue

Bill, My apologies. I was under the impression that wsjtx.log was the main logfile, and that wsjtx_log.adi was for convenience, since WSJT-X proves an option to deleted the .adi and it operates (pretty much) properly when the .adi is deleted, showing may CQs in GREEN. I will attempt what you

[wsjt-devel] Guantanamo

KG4W appears as USA in violet as if it were a new one and keeps being printed in violet also after having been saved at log. V. 1.9.0-rc2 73 Pino ZP4KFX -- Check out the vibrant tech community on one of the world's

Re: [wsjt-devel] Logging Issue

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

Re: [wsjt-devel] Logging Issue

Hi Bill, 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 contacts and import it again,

Re: [wsjt-devel] Logging Issue

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

Re: [wsjt-devel] Logging Issue

The original .adi file are gone, but the fact that they are in my main logging program (because I imported the .adi's into it) twice would indicate that they were in fact in the .adi Thanks, Lou -Original Message- From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Monday, March

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

Re: [wsjt-devel] Logging Issue

Hi Bill, 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,,, <== Duplicate 'cause I didn't

Re: [wsjt-devel] Logging Issue

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

[wsjt-devel] Logging Issue

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

Re: [wsjt-devel] Ft -8 in normal mode

On 3/12/2018 8:35 AM, Ray Jacobs wrote: It says you should be in expedition mode. What is the reason for this? It happened twice. Ray KA3PCX. No, it *asks* you whether you should be in DXpedition mode. As you must have noticed when you clicked "OK", the program does this because it decoded

[wsjt-devel] Ft -8 in normal mode

It says you should be in expedition mode. What is the reason for this? It happened twice. Ray KA3PCX. Sent from AOL Mobile Mail-- Check out the vibrant tech community on one of the world's most engaging tech sites,

Re: [wsjt-devel] FT8 DX-ped mode

PLEASE encourage stations to stay out of the PSK subbands!  There is quite a bit of PSK activity on 20 and 40, and the other bands will pick up when propagation improves.  Mike WM4B On Mar 12, 2018 7:38 AM, jarmo wrote: > > Mon, 12 Mar 2018 06:37:44 -0400 > "James Shaver"

Re: [wsjt-devel] NonCQ patch

On 10/03/2018 19:52, Black Michael via wsjt-devel wrote: Allow UDP clients (e.g. JTAlert) to set up Std Messages for nonCQ calls without Tx Enable.  Rename displayText objects. https://www.dropbox.com/s/7jvp6cv5xwv6xg3/noncq.patch?dl=1

Re: [wsjt-devel] FT8 DX-ped mode

Mon, 12 Mar 2018 06:37:44 -0400 "James Shaver" kirjoitti: > Is there a reason TY7C chose a well known PSK watering hole for this > "test"? That probably made the PSK users quite angry... > > Jim S. > N2ADV As there in docs stands, Don't use "normal" FT8 freqs...etc. And

Re: [wsjt-devel] FT8 DX-ped mode

Is there a reason TY7C chose a well known PSK watering hole for this "test"? That probably made the PSK users quite angry... Jim S. N2ADV -Original Message- From: jarmo [mailto:oh1...@nic.fi] Sent: Monday, March 12, 2018 4:39 AM To: WSJT software development Subject: [wsjt-devel] FT8

[wsjt-devel] FT8 DX-ped mode

Today got first tests from TY7C. They worked "some" qsos with pedition mode. Seems, that there is big need to tell people how it does work. Was quite mess with stations, who tried from same Hz. Most of those stations were trying under 1000Hz. TY7C told that they are FOX, still mess... And TY7C was