Date
1 - 6 of 6
WSJT/JTDX intermittent logging to DXKeeper
Dave / NR1DX
I may be chasing a ghost in the machine here so bare with me
I run what I think is a pretty vanilla setup here. In FT8 mode i use WSJT-X + JTalert which in turn logs to DXKeeper. Logging for FT8 contacts is passed from WSJT through JTAlert to DXKeeper. The set up of all of this was done following the instructions in the DXLAb WIKI ( which I went back an recheked recently to be sure).
Now the problem on an apparently random ( at least I have failed to find a pattern so far) the connection between JTAlert and DXKeeper is broken meaning it wont pass the info contact info from JTAlert to DXKeeper and instead of the verification pop-up from JTAlert I get a pop up that says the logging action failed. When I say this happens randomly there are times when it happens on the first logging attempt after the morning system boot up of the day, but not every time. Some times it fails to pass info after a period on no activity 1/2 hour to 6+ hours, Finally it will occasionally stop passing contact info after 8-12 contacts in rapid succession.
Restarting WSJT has no affect still wont log subsequent FT8 contacts
Restarting JTAalert has no affect still wont log subsequent FT8 contacts
Restarting DXKeeper restores the connectivity between JTAlert and DXKeeper every time
This started several months ago probably after an update of Windows-10 ? DXKeeper? JTAlert and WSJT prior to that it was never a problem. But I didn't pay it much attention when it started and I generally do all recommend updates at least weekly.
The hardware is dedicated to the ham station control , no email, limited internet usage, I7-3.7GHz +16GB of ram . All windows-10 "Energy management" services are turned off,
Ideas and suggestions on what I might try welcome
Dave
NR1DX
--
Dave Manuals@... www.ArtekManuals.com
I run what I think is a pretty vanilla setup here. In FT8 mode i use WSJT-X + JTalert which in turn logs to DXKeeper. Logging for FT8 contacts is passed from WSJT through JTAlert to DXKeeper. The set up of all of this was done following the instructions in the DXLAb WIKI ( which I went back an recheked recently to be sure).
Now the problem on an apparently random ( at least I have failed to find a pattern so far) the connection between JTAlert and DXKeeper is broken meaning it wont pass the info contact info from JTAlert to DXKeeper and instead of the verification pop-up from JTAlert I get a pop up that says the logging action failed. When I say this happens randomly there are times when it happens on the first logging attempt after the morning system boot up of the day, but not every time. Some times it fails to pass info after a period on no activity 1/2 hour to 6+ hours, Finally it will occasionally stop passing contact info after 8-12 contacts in rapid succession.
Restarting WSJT has no affect still wont log subsequent FT8 contacts
Restarting JTAalert has no affect still wont log subsequent FT8 contacts
Restarting DXKeeper restores the connectivity between JTAlert and DXKeeper every time
This started several months ago probably after an update of Windows-10 ? DXKeeper? JTAlert and WSJT prior to that it was never a problem. But I didn't pay it much attention when it started and I generally do all recommend updates at least weekly.
The hardware is dedicated to the ham station control , no email, limited internet usage, I7-3.7GHz +16GB of ram . All windows-10 "Energy management" services are turned off,
Ideas and suggestions on what I might try welcome
Dave
NR1DX
--
Dave Manuals@... www.ArtekManuals.com
Dave AA6YQ
+ AA6YQ comments below
I may be chasing a ghost in the machine here so bare with me
I run what I think is a pretty vanilla setup here. In FT8 mode i use WSJT-X + JTalert which in turn logs to DXKeeper. Logging for FT8 contacts is passed from WSJT through JTAlert to DXKeeper. The set up of all of this was done following the instructions in the DXLAb WIKI ( which I went back an recheked recently to be sure).
Now the problem on an apparently random ( at least I have failed to find a pattern so far) the connection between JTAlert and DXKeeper is broken meaning it wont pass the info contact info from JTAlert to DXKeeper and instead of the verification pop-up from JTAlert I get a pop up that says the logging action failed. When I say this happens randomly there are times when it happens on the first logging attempt after the morning system boot up of the day, but not every time. Some times it fails to pass info after a period on no activity 1/2 hour to 6+ hours, Finally it will occasionally stop passing contact info after 8-12 contacts in rapid succession.
Restarting WSJT has no affect still wont log subsequent FT8 contacts Restarting JTAalert has no affect still wont log subsequent FT8 contacts Restarting DXKeeper restores the connectivity between JTAlert and DXKeeper every time
This started several months ago probably after an update of Windows-10 ? DXKeeper? JTAlert and WSJT prior to that it was never a problem. But I didn't pay it much attention when it started and I generally do all recommend updates at least weekly.
The hardware is dedicated to the ham station control , no email, limited internet usage, I7-3.7GHz +16GB of ram . All windows-10 "Energy management" services are turned off,
Ideas and suggestions on what I might try welcome
+ So that I can see what's going on, please check the "Log debugging info" box on the General tab of DXKeeper's Configuration window. When the next failure occurs, please note it in an email message to which you've attached the errorlog.txt file from your DXKeeper folder, and send it to me via
aa6yq (at) ambersoft.com
+ Then uncheck the "Log debugging info" box on the General tab of DXKeeper's Configuration window.
73,
Dave, AA6YQ
I may be chasing a ghost in the machine here so bare with me
I run what I think is a pretty vanilla setup here. In FT8 mode i use WSJT-X + JTalert which in turn logs to DXKeeper. Logging for FT8 contacts is passed from WSJT through JTAlert to DXKeeper. The set up of all of this was done following the instructions in the DXLAb WIKI ( which I went back an recheked recently to be sure).
Now the problem on an apparently random ( at least I have failed to find a pattern so far) the connection between JTAlert and DXKeeper is broken meaning it wont pass the info contact info from JTAlert to DXKeeper and instead of the verification pop-up from JTAlert I get a pop up that says the logging action failed. When I say this happens randomly there are times when it happens on the first logging attempt after the morning system boot up of the day, but not every time. Some times it fails to pass info after a period on no activity 1/2 hour to 6+ hours, Finally it will occasionally stop passing contact info after 8-12 contacts in rapid succession.
Restarting WSJT has no affect still wont log subsequent FT8 contacts Restarting JTAalert has no affect still wont log subsequent FT8 contacts Restarting DXKeeper restores the connectivity between JTAlert and DXKeeper every time
This started several months ago probably after an update of Windows-10 ? DXKeeper? JTAlert and WSJT prior to that it was never a problem. But I didn't pay it much attention when it started and I generally do all recommend updates at least weekly.
The hardware is dedicated to the ham station control , no email, limited internet usage, I7-3.7GHz +16GB of ram . All windows-10 "Energy management" services are turned off,
Ideas and suggestions on what I might try welcome
+ So that I can see what's going on, please check the "Log debugging info" box on the General tab of DXKeeper's Configuration window. When the next failure occurs, please note it in an email message to which you've attached the errorlog.txt file from your DXKeeper folder, and send it to me via
aa6yq (at) ambersoft.com
+ Then uncheck the "Log debugging info" box on the General tab of DXKeeper's Configuration window.
73,
Dave, AA6YQ
Ted Boerkamp
Hello all...I too am having the exact same issue as Dave NR1DX....started this morning...first 3 FT8 contacts I completed all failed to log and upload
To LOTW.....I have not seen this happen in quite some time...the connections between dxkeeper wsjt and jtalert all worked fine previously.
I made contacts the day before and all worked fine.
I am also using a win10 pc
Where do we go from here??
Thanks
Ted VE3SS
toggle quoted message
Show quoted text
To LOTW.....I have not seen this happen in quite some time...the connections between dxkeeper wsjt and jtalert all worked fine previously.
I made contacts the day before and all worked fine.
I am also using a win10 pc
Where do we go from here??
Thanks
Ted VE3SS
-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave / NR1DX
Sent: January 28, 2023 9:59 PM
To: DXLab@groups.io
Subject: [DXLab] WSJT/JTDX intermittent logging to DXKeeper
I may be chasing a ghost in the machine here so bare with me
I run what I think is a pretty vanilla setup here. In FT8 mode i use WSJT-X + JTalert which in turn logs to DXKeeper. Logging for FT8 contacts is passed from WSJT through JTAlert to DXKeeper. The set up of all of this was done following the instructions in the DXLAb WIKI ( which I went back an recheked recently to be sure).
Now the problem on an apparently random ( at least I have failed to find a pattern so far) the connection between JTAlert and DXKeeper is broken meaning it wont pass the info contact info from JTAlert to DXKeeper and instead of the verification pop-up from JTAlert I get a pop up that says the logging action failed. When I say this happens randomly there are times when it happens on the first logging attempt after the morning system boot up of the day, but not every time. Some times it fails to pass info after a period on no activity 1/2 hour to 6+ hours, Finally it will occasionally stop passing contact info after 8-12 contacts in rapid succession.
Restarting WSJT has no affect still wont log subsequent FT8 contacts Restarting JTAalert has no affect still wont log subsequent FT8 contacts Restarting DXKeeper restores the connectivity between JTAlert and DXKeeper every time
This started several months ago probably after an update of Windows-10 ? DXKeeper? JTAlert and WSJT prior to that it was never a problem. But I didn't pay it much attention when it started and I generally do all recommend updates at least weekly.
The hardware is dedicated to the ham station control , no email, limited internet usage, I7-3.7GHz +16GB of ram . All windows-10 "Energy management" services are turned off,
Ideas and suggestions on what I might try welcome
Dave
NR1DX
--
Dave Manuals@... www.ArtekManuals.com
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave / NR1DX
Sent: January 28, 2023 9:59 PM
To: DXLab@groups.io
Subject: [DXLab] WSJT/JTDX intermittent logging to DXKeeper
I may be chasing a ghost in the machine here so bare with me
I run what I think is a pretty vanilla setup here. In FT8 mode i use WSJT-X + JTalert which in turn logs to DXKeeper. Logging for FT8 contacts is passed from WSJT through JTAlert to DXKeeper. The set up of all of this was done following the instructions in the DXLAb WIKI ( which I went back an recheked recently to be sure).
Now the problem on an apparently random ( at least I have failed to find a pattern so far) the connection between JTAlert and DXKeeper is broken meaning it wont pass the info contact info from JTAlert to DXKeeper and instead of the verification pop-up from JTAlert I get a pop up that says the logging action failed. When I say this happens randomly there are times when it happens on the first logging attempt after the morning system boot up of the day, but not every time. Some times it fails to pass info after a period on no activity 1/2 hour to 6+ hours, Finally it will occasionally stop passing contact info after 8-12 contacts in rapid succession.
Restarting WSJT has no affect still wont log subsequent FT8 contacts Restarting JTAalert has no affect still wont log subsequent FT8 contacts Restarting DXKeeper restores the connectivity between JTAlert and DXKeeper every time
This started several months ago probably after an update of Windows-10 ? DXKeeper? JTAlert and WSJT prior to that it was never a problem. But I didn't pay it much attention when it started and I generally do all recommend updates at least weekly.
The hardware is dedicated to the ham station control , no email, limited internet usage, I7-3.7GHz +16GB of ram . All windows-10 "Energy management" services are turned off,
Ideas and suggestions on what I might try welcome
Dave
NR1DX
--
Dave Manuals@... www.ArtekManuals.com
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
Joe Subich, W4TV
Are you trying to upload to LotW, eQSL, ClubLog and/or
doing a callbook lookup with each QSO?
DXKeeper will delay logging until any on-line activity is complete
and, when one of those services is slow, I've seen log commands
time out because of the previous QSO (particularly FT4 but also a
quick FT8 QSO).
73,
... Joe, W4TV
toggle quoted message
Show quoted text
doing a callbook lookup with each QSO?
DXKeeper will delay logging until any on-line activity is complete
and, when one of those services is slow, I've seen log commands
time out because of the previous QSO (particularly FT4 but also a
quick FT8 QSO).
73,
... Joe, W4TV
On 1/29/2023 10:52 AM, Ted Boerkamp wrote:
Hello all...I too am having the exact same issue as Dave NR1DX....started this morning...first 3 FT8 contacts I completed all failed to log and upload
To LOTW.....I have not seen this happen in quite some time...the connections between dxkeeper wsjt and jtalert all worked fine previously.
I made contacts the day before and all worked fine.
I am also using a win10 pc
Where do we go from here??
Thanks
Ted VE3SS
-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave / NR1DX
Sent: January 28, 2023 9:59 PM
To: DXLab@groups.io
Subject: [DXLab] WSJT/JTDX intermittent logging to DXKeeper
I may be chasing a ghost in the machine here so bare with me
I run what I think is a pretty vanilla setup here. In FT8 mode i use WSJT-X + JTalert which in turn logs to DXKeeper. Logging for FT8 contacts is passed from WSJT through JTAlert to DXKeeper. The set up of all of this was done following the instructions in the DXLAb WIKI ( which I went back an recheked recently to be sure).
Now the problem on an apparently random ( at least I have failed to find a pattern so far) the connection between JTAlert and DXKeeper is broken meaning it wont pass the info contact info from JTAlert to DXKeeper and instead of the verification pop-up from JTAlert I get a pop up that says the logging action failed. When I say this happens randomly there are times when it happens on the first logging attempt after the morning system boot up of the day, but not every time. Some times it fails to pass info after a period on no activity 1/2 hour to 6+ hours, Finally it will occasionally stop passing contact info after 8-12 contacts in rapid succession.
Restarting WSJT has no affect still wont log subsequent FT8 contacts Restarting JTAalert has no affect still wont log subsequent FT8 contacts Restarting DXKeeper restores the connectivity between JTAlert and DXKeeper every time
This started several months ago probably after an update of Windows-10 ? DXKeeper? JTAlert and WSJT prior to that it was never a problem. But I didn't pay it much attention when it started and I generally do all recommend updates at least weekly.
The hardware is dedicated to the ham station control , no email, limited internet usage, I7-3.7GHz +16GB of ram . All windows-10 "Energy management" services are turned off,
Ideas and suggestions on what I might try welcome
Dave
NR1DX
Dave AA6YQ
Thanks for the DXKeeper errorlog, Ted. It shows that DXKeeper did not receive any directive to log a QSO. If you're using JTAlert,
it interoperates with DXKeeper via TCP. During the 7 minutes covered by your errorlog, no messages were received via TCP.
To check for interference from your firewall or other ant-malware, I would normally suggest the diagnostic step of rebooting Windows
into "Safe mode with networking", starting DXKeeper and WSJT-X and JTAlert, and then seeing if a QSO can now be logged via JTAlert -
but I don't know if WSJT-X will be able to connect to an operating soundcard when Windows is booted this way.
73,
Dave, AA6YQ
toggle quoted message
Show quoted text
it interoperates with DXKeeper via TCP. During the 7 minutes covered by your errorlog, no messages were received via TCP.
To check for interference from your firewall or other ant-malware, I would normally suggest the diagnostic step of rebooting Windows
into "Safe mode with networking", starting DXKeeper and WSJT-X and JTAlert, and then seeing if a QSO can now be logged via JTAlert -
but I don't know if WSJT-X will be able to connect to an operating soundcard when Windows is booted this way.
73,
Dave, AA6YQ
-----Original Message-----
From: tboerkamp@... [mailto:tboerkamp@...]
Sent: Sunday, January 29, 2023 12:46 PM
To: 'Dave AA6YQ'
Subject: my errorlog
Hi Dave..as per my post..issue today is that my FT8 contacts are not being logged to dxkeeper and not automatically being
Uploaded to LOTW (I don't use clublog etc)..I have attached my errorlog file after enabling it and working a fourth station
In a row this morning that wont log.
I see the file is quite long but I only enabled it for the last qso with 9A5CC
Please let me know what you find.
Thanks!
73 Ted VE3SS
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
From: tboerkamp@... [mailto:tboerkamp@...]
Sent: Sunday, January 29, 2023 12:46 PM
To: 'Dave AA6YQ'
Subject: my errorlog
Hi Dave..as per my post..issue today is that my FT8 contacts are not being logged to dxkeeper and not automatically being
Uploaded to LOTW (I don't use clublog etc)..I have attached my errorlog file after enabling it and working a fourth station
In a row this morning that wont log.
I see the file is quite long but I only enabled it for the last qso with 9A5CC
Please let me know what you find.
Thanks!
73 Ted VE3SS
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Dave AA6YQ
+ AA6YQ comments below
Are you trying to upload to LotW, eQSL, ClubLog and/or doing a callbook lookup with each QSO?
DXKeeper will delay logging until any on-line activity is complete and, when one of those services is slow, I've seen log commands time out because of the previous QSO (particularly FT4 but also a quick FT8 QSO).
+ When receiving a directive from another application to log a QSO, DXKeeper does so. If the directive also specifies that the logged QSO be uploaded to Club Log, eQSL, and/or LoTW, those uploads are sequentially initiated after the QSO has been successfully logged.
73,
Dave, AA6YQ
Are you trying to upload to LotW, eQSL, ClubLog and/or doing a callbook lookup with each QSO?
DXKeeper will delay logging until any on-line activity is complete and, when one of those services is slow, I've seen log commands time out because of the previous QSO (particularly FT4 but also a quick FT8 QSO).
+ When receiving a directive from another application to log a QSO, DXKeeper does so. If the directive also specifies that the logged QSO be uploaded to Club Log, eQSL, and/or LoTW, those uploads are sequentially initiated after the QSO has been successfully logged.
73,
Dave, AA6YQ