[wsjt-devel] Logging Prompt

2024-06-02 Thread Joe via wsjt-devel
I do not know if this is a N1MM+ issue, or a WSJT-X Issue. But the logging, I have it clearly selected to automatically log the contact. In the CQWW it does that. But the ARRL Digi contest this weekend every contact had the prompt window appear and I had to hit OK to log the contact.

Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-16 Thread Saku via wsjt-devel
Marco Calistri via wsjt-devel kirjoitti 15.2.2023 klo 22.17: Yeah! HI! Cqrlog wsjtx-remote can support only one remote wsjtx at time. Using multicast UDP I think you can have several wsjtxs sending to Cqrlog, but you have already found the problem that arises. The remote code is very

Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-15 Thread Marco Calistri via wsjt-devel
nesday, February 15, 2023 1:36:37 PM To: wsjt-devel@lists.sourceforge.net Cc: Brian Morrison Subject: Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations On Wed, 15 Feb 2023 14:26:07 + Marco Calistri via wsjt-devel wrote: > Hi Brian, > > Yes, i know Saku, he helped me in

Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-15 Thread Brian Morrison via wsjt-devel
On Wed, 15 Feb 2023 14:26:07 + Marco Calistri via wsjt-devel wrote: > Hi Brian, > > Yes, i know Saku, he helped me in many occasions. > > Since this is not a blocking issue for me but just a random and not > important one, occuring only under particular usage of the FT8 QSO > (trying to

Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-15 Thread Marco Calistri via wsjt-devel
per Android<https://aka.ms/AAb9ysg> Da: Brian Morrison via wsjt-devel Inviato: mercoledì 15 febbraio 2023, 11:12 A: wsjt-devel@lists.sourceforge.net Cc: Brian Morrison Oggetto: Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations On Tue,

Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-15 Thread Brian Morrison via wsjt-devel
On Tue, 14 Feb 2023 23:17:19 -0300 Marco Calistri via wsjt-devel wrote: > Il 14/02/23 11:44, Brian Morrison via wsjt-devel ha scritto: > > On Tue, 14 Feb 2023 08:39:54 -0300 > > Marco Calistri via wsjt-devel > > wrote: > > > >> Hello, > >> > >> I'm using CQRLOG as the default QSO logging

Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-14 Thread Marco Calistri via wsjt-devel
Il 14/02/23 11:44, Brian Morrison via wsjt-devel ha scritto: On Tue, 14 Feb 2023 08:39:54 -0300 Marco Calistri via wsjt-devel wrote: Hello, I'm using CQRLOG as the default QSO logging software with WSJT-X What version of CQRLOG are you using? Hello! CQRLOG 2.6.0 (2022-07-05) But, as I

Re: [wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-14 Thread Brian Morrison via wsjt-devel
On Tue, 14 Feb 2023 08:39:54 -0300 Marco Calistri via wsjt-devel wrote: > Hello, > > I'm using CQRLOG as the default QSO logging software with WSJT-X What version of CQRLOG are you using? -- Brian G8SEZ ___ wsjt-devel mailing list

[wsjt-devel] Logging of mixed data if you do QSO with two stations

2023-02-14 Thread Marco Calistri via wsjt-devel
Hello, I'm using CQRLOG as the default QSO logging software with WSJT-X, the two programs works jointly through the internal UDP ports 2337/2333. The following issue is occurring since several time, it is not related to a specific WSJT-X or CQRLOG version. It happened and it still happens

Re: [wsjt-devel] logging

2019-10-31 Thread Black Michael via wsjt-devel
You don't have ALL.TXT either so something is really wrong with your setup. Look at the WSJT-X.ini file (use Notepad) and find the "SaveDir" entry and see where it points to. de Mike W9MDB On Thursday, October 31, 2019, 07:51:03 PM CDT, Carl Buehler wrote: Thank you for the

Re: [wsjt-devel] logging

2019-10-31 Thread Carl Buehler
Thank you for the suggestion about file extensions. I attempted to make sure it is not set to hide file extensions but not certain. Attached is the listing when I go to Settings, and you can see that the adi log document does not appear. I plan to check with a local ham or computer person who

Re: [wsjt-devel] logging

2019-10-31 Thread Roeland Jansen
as said, it is is in the logging directory. be sure you don't hide file extensions under Windows On Wed, 30 Oct 2019, 15:49 Carl Buehler, wrote: > WSJT-X 2.1.0 logging still a concern. The wsjtx text log continues to > save contacts. I downloaded and installed the program but no .adi or >

[wsjt-devel] logging

2019-10-30 Thread Carl Buehler
WSJT-X 2.1.0 logging still a concern. The wsjtx text log continues to save contacts. I downloaded and installed the program but no .adi or similar file appears to be created in the tab 'open log directory'. Should this be somewhere in the program or be able to generate it for LOTW? Thanks much.

Re: [wsjt-devel] Logging

2019-07-23 Thread Peter Sumner
; > -Original Message- > From: Joe > To: Black Michael ; WSJT > software development > > Sent: Tue, Jul 23, 2019 11:00 am > Subject: Re: [wsjt-devel] Logging > > OK, > > I have the Log Automatically check marked as seen below in earlier message. > > Now

Re: [wsjt-devel] Logging

2019-07-23 Thread Sam W2JDB via wsjt-devel
, 2019 4:08 pm Subject: Re: [wsjt-devel] Logging I seriously doubt that the developers will change the way the logging system works.    It has been stated often enough that they do not want to create an automatic QSO machine, and so they want some human intervention to start a QSO, call CQ

Re: [wsjt-devel] Logging

2019-07-23 Thread Neil Zampella
. 73, Sam W2JDB -Original Message- From: Joe To: Sam W2JDB ; wsjt-devel Sent: Tue, Jul 23, 2019 11:52 am Subject: Re: [wsjt-devel] Logging OK, But if I check that box, None of the choices it wants you also pick fits true? or what should I chose? to fool it? the exchange is the typical

Re: [wsjt-devel] Logging

2019-07-23 Thread Joe
W2JDB -Original Message- From: Joe To: Sam W2JDB ; wsjt-devel Sent: Tue, Jul 23, 2019 11:52 am Subject: Re: [wsjt-devel] Logging OK, But if I check that box, None of the choices it wants you also pick fits true? or what should I chose? to fool it? the exchange is the typical any

Re: [wsjt-devel] Logging

2019-07-23 Thread Sam W2JDB via wsjt-devel
-devel Sent: Tue, Jul 23, 2019 11:52 am Subject: Re: [wsjt-devel] Logging OK, But if I check that box, None of the choices it wants you also pick fits true? or what should I chose? to fool it? the exchange is the typical any day FT exchange 4 digit grid square, what would work? Joe

Re: [wsjt-devel] Logging

2019-07-23 Thread Joe
-tyme.com On 7/23/2019 10:26 AM, Sam W2JDB wrote: Did you have the Spcl Oper box checked ? Sam W2JDB -Original Message- From: Joe To: WSJT software development Cc: Sam W2JDB Sent: Tue, Jul 23, 2019 11:22 am Subject: Re: [wsjt-devel] Logging But? It is a contest, it is fully integrated

Re: [wsjt-devel] Logging

2019-07-23 Thread Sam W2JDB via wsjt-devel
Did you have the Spcl Oper box checked ? Sam W2JDB   -Original Message- From: Joe To: WSJT software development Cc: Sam W2JDB Sent: Tue, Jul 23, 2019 11:22 am Subject: Re: [wsjt-devel] Logging But? It is a contest, it is fully integrated with N1MM+ the WWDIGI contest https://ww

Re: [wsjt-devel] Logging

2019-07-23 Thread Joe
Subject: Re: [wsjt-devel] Logging OK, I have the Log Automatically check marked as seen below in earlier message. Now I see someone CQing, I double click on them and it calls them, all is well, The QSO proceeds along as usual, and when finished, instead of "Logging Automatically"

Re: [wsjt-devel] Logging

2019-07-22 Thread Joe
I think I was in contesting mode. I started N1MM+, for the WWDIGI Contest,  then had N1MM+ Open the WSJT-X program, It all works fine but when the contact is complete the box still appears prompting me to log the contact.  what do i need to set differently? Joe WB9SBD On 7/22/2019 10:15

Re: [wsjt-devel] Logging button placement

2019-04-30 Thread Matthew Miller
want to break the rules, they will just find a newer “solution” to violate the FCC regulations on automation and do what they please. -Matt / KK4NDE From: Neil Zampella [mailto:ne...@techie.com] Sent: Tuesday, April 30, 2019 2:52 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel

Re: [wsjt-devel] Logging button placement

2019-04-30 Thread Adam Bartlett
The "developers" who don't follow the rules can figure out how to build the package where this feature is turned off quite easily - the instructions on what you need to build WSJT-X from sources is as easy as the sources are to come by. There have already been complaints about things like this

Re: [wsjt-devel] Logging button placement

2019-04-30 Thread Neil Zampella
My 2 cents ... there has been an issue with some 'developers' (and I use the term loosely) creating a way to get around the requirements that an operator must be in front of the rig when in operation; thus creating an automatic QSO machine.   This differs from beacons, as we all know, as it is a

[wsjt-devel] Logging button placement

2019-04-30 Thread WB5JJJ
My vote is with Steve on restoring consistent button positions as well, even though I can easily read and locate the OK button. It does take extra time plus "muscle memory" is of no value in this, especially with the 6 second turn around now. Streamlining the process should be paramount. My

Re: [wsjt-devel] Logging Issue

2018-03-30 Thread Ed Wilson via wsjt-devel
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

Re: [wsjt-devel] Logging Issue

2018-03-29 Thread Ed Wilson via wsjt-devel
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

[wsjt-devel] Logging Issue

2018-03-29 Thread Ed Wilson via wsjt-devel
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

Re: [wsjt-devel] Logging Issue

2018-03-12 Thread Bill Somerville
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

2018-03-12 Thread Louis Ricci
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

Re: [wsjt-devel] Logging Issue

2018-03-12 Thread Bill Somerville
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

2018-03-12 Thread Louis Ricci
? 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

Re: [wsjt-devel] Logging Issue

2018-03-12 Thread Bill Somerville
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

2018-03-12 Thread Louis Ricci
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

Re: [wsjt-devel] Logging Issue

2018-03-12 Thread Bill Somerville
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

2018-03-12 Thread Louis Ricci
,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

Re: [wsjt-devel] Logging Issue

2018-03-12 Thread Bill Somerville
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

2018-03-12 Thread Louis Ricci
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] Logging of PSK REPORTER spots

2017-12-28 Thread Dennis Drakopoulos via wsjt-devel
Michael es Brian, thank you very much for the support! Well, my programming skills & competencies are kind of rusty. So I'll have to put extra effort to write a program. Of course I can easily augment or modify a ready made one. Besides, I always believed that we shouldn't reinvent the wheel

Re: [wsjt-devel] Logging of PSK REPORTER spots

2017-12-25 Thread Brian Moran
It seems like you could help yourself in this instance. ALL.TXT contains information like this: 2017-12-20 21:29 14.074 MHz FT8 212915 -12 0.0 570 ~ N5YYF W2GW FN30 212915 -6 0.1 700 ~ K1PL NZ2X -14 212915 -19 0.1 800 ~ CQ KB8BIP EM88 212915 -7 0.3 1127 ~ PY6HD W4BCG EM65 212915

Re: [wsjt-devel] Logging of PSK REPORTER spots

2017-12-25 Thread Dennis Drakopoulos via wsjt-devel
Thank you dear Michael for coming back! Not suitable for me. First each line does not contain the date of decoded message, as well as the dial frequency. Secondly, data duplication. Only want CQ messages originating from a callsign and DE ones. How about making the software component

Re: [wsjt-devel] Logging of PSK REPORTER spots

2017-12-25 Thread Black Michael via wsjt-devel
Doesn't the ALL.TXT file do what you want?What kind of off-line analyis do you want? de Mike W9MDB On Monday, December 25, 2017, 9:41:31 AM CST, Dennis Drakopoulos via wsjt-devel wrote: Good afternoon to all!Is it possible to add as a feature the

[wsjt-devel] Logging of PSK REPORTER spots

2017-12-25 Thread Dennis Drakopoulos via wsjt-devel
Good afternoon to all!Is it possible to add as a feature the capability to log to a local text file all spots sent to PSK REPORTER?Rationale behind if to utilize them in offline analysis. If hot, perhaps you can suggest of another workaround to have these spots? Merry Xmas es HNY 2018! 73 de

Re: [wsjt-devel] Logging error with wsjt-x 1.5.0-rc2

2015-06-16 Thread Bill Somerville
On 16/06/2015 04:27, Richard Shaw wrote: Hi Richard, I was casually trying to make contacts while working on another FOSS radio project and I completed the QSO and the log window came up. I then saw a station I was interested in so I went ahead and double-clicked on it (with the

[wsjt-devel] Logging error with wsjt-x 1.5.0-rc2

2015-06-15 Thread Richard Shaw
I was casually trying to make contacts while working on another FOSS radio project and I completed the QSO and the log window came up. I then saw a station I was interested in so I went ahead and double-clicked on it (with the auto-enable TX turned on). I then went back and looked up the OP name

[wsjt-devel] Logging times

2014-10-13 Thread Michael Black
For logging pedantics could we get WSJT-X to log both time_on and time_off in the ADIF file? It's only doing time_on right now and it uses the logging window to determine that time. Time_on could be determined by TX-1 or TX-2 messages being sent or double-click on CQ and time_off by the logging