locked #Logging - with N3FJP FD logger #logging


James C. Hall, MD WB4YDL
 

As part of our groups after action reporting, we noted the following anomaly which we couldn’t readily isolate or explain :

Occasionally, the logging would just stop. Everything worked well up to the point you were asked to click OK to log the QSO - which would normally cause the QSO to appear in both the WSJT contest log and the FD logger. Several more awake operators quickly noticed this after a few QSO’s, stopped, recovered the info in the buffer and manually entered the QSO’s in the FD logger.

We did not run ancillary programs such as JTAlert, just N3FJP FD log and WSJT-X newest GR version (2.4.0 ? IIRC). After restarting both programs, it resumed normal operation, but we quickly determined (after a few instances) that we only needed to restart WSJT (we didn’t like to restart a networked program !). The network was not a factor as it also occurred a couple times with the GOTA station. It did not occur with the VHF station. So different computers (OS’s both Win7 and Win10), different radios - no rhyme or reason. RF in the shack ?? We don’t know.

We recovered most if not all data. Thought you should know.

BTW, as part of the prior discussion, we teach our young ops to “finish the QSO”, don’t assume ! After the RR73, wait for any repeated exchange, hover over Tx4 and get ready to rapidly click it and enable TX ! :) They caught on pretty well.

73, Jamie
WB4YDL


 

Re finishing the QSO. If you set “enable TX” again after the sending RR73 clears it. If the QSO partner resends R-xx, WSJT-X will resend your RR73. Saves hovering over TX4. It will also automatically start sending CQ if they don’t repeat the R-xx.

 

73 Phil

 

Sent from Mail for Windows 10

 

From: James C. Hall, MD
Sent: 28 June 2021 10:49
To: main@wsjtx.groups.io
Subject: [WSJTX] #Logging - with N3FJP FD logger

 

As part of our groups after action reporting, we noted the following anomaly which we couldn’t readily isolate or explain :

 

Occasionally, the logging would just stop. Everything worked well up to the point you were asked to click OK to log the QSO - which would normally cause the QSO to appear in both the WSJT contest log and the FD logger. Several more awake operators quickly noticed this after a few QSO’s, stopped, recovered the info in the buffer and manually entered the QSO’s in the FD logger.

 

We did not run ancillary programs such as JTAlert, just N3FJP FD log and WSJT-X newest GR version (2.4.0 ? IIRC). After restarting both programs, it resumed normal operation, but we quickly determined (after a few instances) that we only needed to restart WSJT (we didn’t like to restart a networked program !). The network was not a factor as it also occurred a couple times with the GOTA station.  It did not occur with the VHF station. So different computers (OS’s both Win7 and Win10), different radios - no rhyme or reason. RF in the shack ?? We don’t know.

 

We recovered most if not all data. Thought you should know.

 

BTW, as part of the prior discussion, we teach our young ops to “finish the QSO”, don’t assume ! After the RR73, wait for any repeated exchange, hover over Tx4 and get ready to rapidly click it and enable TX ! :) They caught on pretty well.

 

73, Jamie

WB4YDL

 


--
73 Phil GM3ZZA


Josh VanRiet / K7DOC
 

I've never had much luck with N3FJP.  I prefer to use Log4OM (Log 4 Old Men).  It integrates field day as well as other contests, automatically reads the wsjtx log file after each QSO, automatically updates to QRZ, LOTW, EQSL, HamClub and others in a much easier to use format. (And can be setup to have 1 network logbook that other computers can feed in to).

Josh VanRiet 
K7DOC AE VE 
COML(t) 
KARS Logistics Chief 
SVAOC VP of Resources 
MVP Support Specialist 
PAVE Peer Advisor 
KCDEM Fleet and Assets 

On Jun 27, 2021 5:49 PM, "James C. Hall, MD" <heartdoc@...> wrote:

As part of our groups after action reporting, we noted the following anomaly which we couldn’t readily isolate or explain :

Occasionally, the logging would just stop. Everything worked well up to the point you were asked to click OK to log the QSO - which would normally cause the QSO to appear in both the WSJT contest log and the FD logger. Several more awake operators quickly noticed this after a few QSO’s, stopped, recovered the info in the buffer and manually entered the QSO’s in the FD logger.

We did not run ancillary programs such as JTAlert, just N3FJP FD log and WSJT-X newest GR version (2.4.0 ? IIRC). After restarting both programs, it resumed normal operation, but we quickly determined (after a few instances) that we only needed to restart WSJT (we didn’t like to restart a networked program !). The network was not a factor as it also occurred a couple times with the GOTA station.  It did not occur with the VHF station. So different computers (OS’s both Win7 and Win10), different radios - no rhyme or reason. RF in the shack ?? We don’t know.

We recovered most if not all data. Thought you should know.

BTW, as part of the prior discussion, we teach our young ops to “finish the QSO”, don’t assume ! After the RR73, wait for any repeated exchange, hover over Tx4 and get ready to rapidly click it and enable TX ! :) They caught on pretty well.

73, Jamie
WB4YDL






Butch Washer
 

I use it with AClog ever since he added that upgrade with no problems. Haven’t tried it yet with any other of them. But probably will in near future. 

Butch N5SMQ 


On Jun 29, 2021, at 2:47 AM, Josh VanRiet / K7DOC via groups.io <K7DOC@...> wrote:


I've never had much luck with N3FJP.  I prefer to use Log4OM (Log 4 Old Men).  It integrates field day as well as other contests, automatically reads the wsjtx log file after each QSO, automatically updates to QRZ, LOTW, EQSL, HamClub and others in a much easier to use format. (And can be setup to have 1 network logbook that other computers can feed in to).

Josh VanRiet 
K7DOC AE VE 
COML(t) 
KARS Logistics Chief 
SVAOC VP of Resources 
MVP Support Specialist 
PAVE Peer Advisor 
KCDEM Fleet and Assets 

On Jun 27, 2021 5:49 PM, "James C. Hall, MD" <heartdoc@...> wrote:

As part of our groups after action reporting, we noted the following anomaly which we couldn’t readily isolate or explain :

Occasionally, the logging would just stop. Everything worked well up to the point you were asked to click OK to log the QSO - which would normally cause the QSO to appear in both the WSJT contest log and the FD logger. Several more awake operators quickly noticed this after a few QSO’s, stopped, recovered the info in the buffer and manually entered the QSO’s in the FD logger.

We did not run ancillary programs such as JTAlert, just N3FJP FD log and WSJT-X newest GR version (2.4.0 ? IIRC). After restarting both programs, it resumed normal operation, but we quickly determined (after a few instances) that we only needed to restart WSJT (we didn’t like to restart a networked program !). The network was not a factor as it also occurred a couple times with the GOTA station.  It did not occur with the VHF station. So different computers (OS’s both Win7 and Win10), different radios - no rhyme or reason. RF in the shack ?? We don’t know.

We recovered most if not all data. Thought you should know.

BTW, as part of the prior discussion, we teach our young ops to “finish the QSO”, don’t assume ! After the RR73, wait for any repeated exchange, hover over Tx4 and get ready to rapidly click it and enable TX ! :) They caught on pretty well.

73, Jamie
WB4YDL









James C. Hall, MD WB4YDL
 

Thanks for the tip, Phil.

73, Jamie
WB4YDL


On Jun 29, 2021, at 1:43 AM, Philip Rose via groups.io <gm3zza@...> wrote:



Re finishing the QSO. If you set “enable TX” again after the sending RR73 clears it. If the QSO partner resends R-xx, WSJT-X will resend your RR73. Saves hovering over TX4. It will also automatically start sending CQ if they don’t repeat the R-xx.

 

73 Phil

 

Sent from Mail for Windows 10

 

From: James C. Hall, MD
Sent: 28 June 2021 10:49
To: main@wsjtx.groups.io
Subject: [WSJTX] #Logging - with N3FJP FD logger

 

As part of our groups after action reporting, we noted the following anomaly which we couldn’t readily isolate or explain :

 

Occasionally, the logging would just stop. Everything worked well up to the point you were asked to click OK to log the QSO - which would normally cause the QSO to appear in both the WSJT contest log and the FD logger. Several more awake operators quickly noticed this after a few QSO’s, stopped, recovered the info in the buffer and manually entered the QSO’s in the FD logger.

 

We did not run ancillary programs such as JTAlert, just N3FJP FD log and WSJT-X newest GR version (2.4.0 ? IIRC). After restarting both programs, it resumed normal operation, but we quickly determined (after a few instances) that we only needed to restart WSJT (we didn’t like to restart a networked program !). The network was not a factor as it also occurred a couple times with the GOTA station.  It did not occur with the VHF station. So different computers (OS’s both Win7 and Win10), different radios - no rhyme or reason. RF in the shack ?? We don’t know.

 

We recovered most if not all data. Thought you should know.

 

BTW, as part of the prior discussion, we teach our young ops to “finish the QSO”, don’t assume ! After the RR73, wait for any repeated exchange, hover over Tx4 and get ready to rapidly click it and enable TX ! :) They caught on pretty well.

 

73, Jamie

WB4YDL

 


--
73 Phil GM3ZZA



James C. Hall, MD WB4YDL
 

Yes, I use Log4OM here at home. N3FJP FD logger is what is used here for FD. Just the way it is !

73, Jamie
WB4YDL


On Jun 29, 2021, at 1:48 AM, Josh VanRiet / K7DOC via groups.io <K7DOC@...> wrote:


I've never had much luck with N3FJP.  I prefer to use Log4OM (Log 4 Old Men).  It integrates field day as well as other contests, automatically reads the wsjtx log file after each QSO, automatically updates to QRZ, LOTW, EQSL, HamClub and others in a much easier to use format. (And can be setup to have 1 network logbook that other computers can feed in to).

Josh VanRiet 
K7DOC AE VE 
COML(t) 
KARS Logistics Chief 
SVAOC VP of Resources 
MVP Support Specialist 
PAVE Peer Advisor 
KCDEM Fleet and Assets 

On Jun 27, 2021 5:49 PM, "James C. Hall, MD" <heartdoc@...> wrote:

As part of our groups after action reporting, we noted the following anomaly which we couldn’t readily isolate or explain :

Occasionally, the logging would just stop. Everything worked well up to the point you were asked to click OK to log the QSO - which would normally cause the QSO to appear in both the WSJT contest log and the FD logger. Several more awake operators quickly noticed this after a few QSO’s, stopped, recovered the info in the buffer and manually entered the QSO’s in the FD logger.

We did not run ancillary programs such as JTAlert, just N3FJP FD log and WSJT-X newest GR version (2.4.0 ? IIRC). After restarting both programs, it resumed normal operation, but we quickly determined (after a few instances) that we only needed to restart WSJT (we didn’t like to restart a networked program !). The network was not a factor as it also occurred a couple times with the GOTA station.  It did not occur with the VHF station. So different computers (OS’s both Win7 and Win10), different radios - no rhyme or reason. RF in the shack ?? We don’t know.

We recovered most if not all data. Thought you should know.

BTW, as part of the prior discussion, we teach our young ops to “finish the QSO”, don’t assume ! After the RR73, wait for any repeated exchange, hover over Tx4 and get ready to rapidly click it and enable TX ! :) They caught on pretty well.

73, Jamie
WB4YDL