Date   

Re: Can't update to TQSL 2.5.9

Dave AA6YQ
 

+ AA6YQ comments below

Thanks Dave for calling in the big guns. I will wait for their responses.

+ I’ve forwarded Rick K1MU’s response to you.

73,

Dave, AA6YQ


Re: Can't update to TQSL 2.5.9

John W1JA
 

Thanks Dave for calling in the big guns. I will wait for their responses.

Thanks Neil. I have been hearing about Revo for decades. I would have bought it on sale right now, just to have around. But the sale price is for just 1 year. :(  I have problems like this way less often than annually. I'll just use the free version if I need it.


Re: Issue attempting to remove Duplicate QSO's - Program Error 3043

Dave AA6YQ
 

+ AA6YQ comments below

thanks for swift reply. I started the task again with the database on a local hard drive and that process worked perfectly - so I am good. only 3517 dupes which means some triples or more.

+ Great, but you should still get to the bottom of the "Disk or network error", especially if you're going to continue maintaining your log file in the cloud. Problems left unresolved have a nasty habit of re-appearing at the worst possible time...

73,

Dave, AA6YQ


Re: Issue attempting to remove Duplicate QSO's - Program Error 3043

Joe Bales
 

Hi Dave 

thanks for swift reply.  I started the task again with the database on a local hard drive and that process worked perfectly - so I am good.  only 3517 dupes which means some triples or more.

thanks 73


Re: Issue attempting to remove Duplicate QSO's - Program Error 3043

Dave AA6YQ
 

+ AA6YQ comments below

When following the instructions located at https://www.dxlabsuite.com/dxlabwiki/RemovingDuplicates I am left with ALL of my 41,000 QSO's displayed in the log. I have a few hundred dupes. The routine in the link previously mentioned seems to go through the process to select dupes. I looked at the error log and found the following error message at the time of completion of the removingduplicate routine. program error 3043 in module DXLogModule.FlagDuplicateQSOs: Disk or network error. -

Any ideas on this one?

+ The " Disk or network error" message comes from Windows. So that I can see what's going on, please do the following:

1. On the Configuration window's General tab, check the "Log debugging info" box

2. Terminate DXKeeper

3. Start DXKeeper

4. Attempt to remove your duplicate QSOs, just as you did before

5. When the failure occurs,

5a. On the Configuration window's General tab, uncheck the "Log debugging info" box

5b. Attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

I would like to remove the dupes with them only being the items showing in the log. This is a 2 week old new computer build with Solid State hard drives. I doubt there is a real disk error.

+ I wouldn't be so sure; SSD failure rates follow a bathtub-shaped curve. Check the Window Event Logs to see if hardware or software errors were reported:

https://forums.tomshardware.com/faq/how-to-use-windows-10-event-viewer.2752289/


The data file is in the cloud. perhaps this is the issue ... but I have been using the data in the cloud for years.

+ The number of log accesses required to eliminate duplicates is proportional to the square of the number of QSOs in your log. With 41K logged QSOs, that's a lot of network traffic, which could expose latent hardware or software problems. Any such problems should be recorded in the Windows Event Logs.

+ You could try copying your log from the cloud to a local file and see if duplicate elimination succeeds.

73,

Dave, AA6YQ


Issue attempting to remove Duplicate QSO's - Program Error 3043

Joe Bales
 

When following the instructions located at https://www.dxlabsuite.com/dxlabwiki/RemovingDuplicates I am left with ALL of my 41,000 QSO's displayed in the log.  I have a few hundred dupes.  The routine in the link previously mentioned seems to go through the process to select dupes.  I looked at the error log and found the following error message at the time of completion of the removingduplicate routine.  program error 3043 in module DXLogModule.FlagDuplicateQSOs: Disk or network error. -

Any ideas on this one?  I would like to remove the dupes with them only being the items showing in the log.  This is a 2 week old new computer build with Solid State hard drives.  I doubt there is a real disk error.  The data file is in the cloud.  perhaps this is the issue ... but I have been using the data in the cloud for years.

K4JKB


Re: Can't update to TQSL 2.5.9

Dave AA6YQ
 

+ AA6YQ comments below

Don't "delete files and registry entries" ... use Revo Uninstaller. There are free and pro versions, and the pro version is on sale right now for 9.98. About $15 off. Even the free version will remove programs, but the pro does more and at that price WELL worth the money.

+ I suggest holding off on changes until TQSL developer Rick K1MU has a chance to weigh in.

73,

Dave, AA6YQ


Re: Can't update to TQSL 2.5.9

neil_zampella
 

Don't "delete files and registry entries" ... use Revo Uninstaller.   There are free and pro versions, and the pro version is on sale right now for 9.98.      About $15 off.  Even the free version will remove programs, but the pro does more and at that price WELL worth the money.

Neil, KN3ILZ

On 11/20/2021 7:44 AM, Dave AA6YQ wrote:

Since 2.5.9 became available I have been unable to update to it.

My installed TQSL says it's 2.5.7, but Programs and Features in Control Panel, and Apps & Features (the W10 app,) both say I have 2.5.5 installed. Installing 2.5.9 fails - process can't find a valid installation package. Even when I point it at tqsl-2.5.9.msi that I downloaded manually from the LotW page, the installation fails.

I cannot uninstall TQSL either - the process looks for a valid 2.5.5 installation package. I couldn't find a 2.5.5 installation .msi file on the web to download.

I suppose I could uninstall manually (by deleting files and registry entries) but am reluctant to tinker with the registry. After some rooting around on the LotW pages I found a Trouble Ticket submission mechanism (it's at http://www.arrl.org/lotw-help-ticket ). I submitted a ticket two weeks ago; no response.

Does anyone have suggestions?

73, John W1JA

 

+ Rick K1MU, could you give John a hand with this?

+ Greg K0GW, you might check to see why John received no response to his Trouble Ticket.

        73,

 

                Dave, AA6YQ


Re: Can't update to TQSL 2.5.9

Dave AA6YQ
 

Since 2.5.9 became available I have been unable to update to it.

My installed TQSL says it's 2.5.7, but Programs and Features in Control Panel, and Apps & Features (the W10 app,) both say I have 2.5.5 installed. Installing 2.5.9 fails - process can't find a valid installation package. Even when I point it at tqsl-2.5.9.msi that I downloaded manually from the LotW page, the installation fails.

I cannot uninstall TQSL either - the process looks for a valid 2.5.5 installation package. I couldn't find a 2.5.5 installation .msi file on the web to download.

I suppose I could uninstall manually (by deleting files and registry entries) but am reluctant to tinker with the registry. After some rooting around on the LotW pages I found a Trouble Ticket submission mechanism (it's at http://www.arrl.org/lotw-help-ticket ). I submitted a ticket two weeks ago; no response.

Does anyone have suggestions?

73, John W1JA

 

+ Rick K1MU, could you give John a hand with this?

+ Greg K0GW, you might check to see why John received no response to his Trouble Ticket.

        73,

 

                Dave, AA6YQ


Can't update to TQSL 2.5.9

John W1JA
 

Since 2.5.9 became available I have been unable to update to it.

My installed TQSL says it's 2.5.7, but Programs and Features in Control Panel, and Apps & Features (the W10 app,) both say I have 2.5.5 installed. Installing 2.5.9 fails - process can't find a valid installation package. Even when I point it at tqsl-2.5.9.msi that I downloaded manually from the LotW page, the installation fails.

I cannot uninstall TQSL either - the process looks for a valid 2.5.5 installation package. I couldn't find a 2.5.5 installation .msi file on the web to download.

I suppose I could uninstall manually (by deleting files and registry entries) but am reluctant to tinker with the registry. After some rooting around on the LotW pages I found a Trouble Ticket submission mechanism (it's at http://www.arrl.org/lotw-help-ticket ). I submitted a ticket two weeks ago; no response.

Does anyone have suggestions?

73, John W1JA


Re: jtalert not logging to dxkeeper

Dave AA6YQ
 

+ AA6YQ comments below

This was all working before a hard drive crash. After a restore, it seems that all is working well except for the jtalert logging to dxkeeper.

No alerts seem to show up on jtalert and when I log a QSO in FT8, it seems nothing gets passed to dxkeeper.

+ When you're using JT-Alert, DXLab applications are relatively passive: they receive directives - like "lookup callsign" and "log QSO" from JT-Alert, and then execute them.

+ Focus first on getting JT-Alert to correctly interoperate with WSJT-X. When that's working, then configure JT-Alert to correctly interoperate - one at a time -- with DXKeeper, DXView, SpotCollector, and Pathfidner.

73,

Dave, AA6YQ


Re: jtalert not logging to dxkeeper

neil_zampella
 

I would take a look at WSJT-X to make sure that the UDP settings are correct.   Make sure all the checkboxes are checked.

Neil, KN3ILZ

On 11/19/2021 8:10 PM, Kurt Cathcart wrote:
This was all working before a hard drive crash.  After a resore, it seems that all is working well except for the jtalert logging to dxkeeper.

No alerts seem to show up on jtalert and when I log a QSO in FT8, it seems nothing gets passed to dxkeeper.

I've been through the config guid multiple times. https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert

Suggestions?


jtalert not logging to dxkeeper

Kurt Cathcart
 

This was all working before a hard drive crash.  After a resore, it seems that all is working well except for the jtalert logging to dxkeeper.

No alerts seem to show up on jtalert and when I log a QSO in FT8, it seems nothing gets passed to dxkeeper.

I've been through the config guid multiple times. https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert

Suggestions?


Re: Apparently self spotting my call in SpotCollector?

Ed
 

Thanks Dave

I now understand.

Regards,   Ed


Re: Apparently self spotting my call in SpotCollector?

Dave AA6YQ
 

In the message below, I meant to say

"As has been pointed out in this thread, you can configure SpotCollector to ignore callsigns decoded by skimmers"

On the "Special Callsigns" tab of SpotCollector's Configuration window, check the "Discard spots from spotting station callsigns ending in -#"

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Friday, November 19, 2021 8:45 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Apparently self spotting my call in SpotCollector?

+ AA6YQ comments below

A few years back, 90% of the time i used CW. Have not used SpotCollector for quite awhile, playing with FT-8. So In my Spot Sources, I had one Host Address as: dxc.ve7cc.net port 7373

VE7CC is causing this to happen with enabled checked. When not enabled, problem goes away. Will see how it goes.

+ There is no "self-spotting" problem. There are stations that continuously scan bands for CW and digital mode signals, decode these signals, and submit them to some nodes of the DX Cluster network; these stations are referred to as "skimmers". If one of your spot sources is connected to a skimmer, then the callsigns decoded by that skimmer -- including yours when you transmit -- will appear in your Spot Database Display.

+ As has been pointed out in this thread, you can configure SpotCollector to callsigns decoded by skimmers. For more information, see "Using the Reverse Beacon Network with DXLab" in

http://www.dxlabsuite.com/RBN/

73,

Dave, AA6YQ


Re: Apparently self spotting my call in SpotCollector?

Dave AA6YQ
 

+ AA6YQ comments below

A few years back, 90% of the time i used CW. Have not used SpotCollector for quite awhile, playing with FT-8. So In my Spot Sources, I had one Host Address as: dxc.ve7cc.net port 7373

VE7CC is causing this to happen with enabled checked. When not enabled, problem goes away. Will see how it goes.

+ There is no "self-spotting" problem. There are stations that continuously scan bands for CW and digital mode signals, decode these signals, and submit them to some nodes of the DX Cluster network; these stations are referred to as "skimmers". If one of your spot sources is connected to a skimmer, then the callsigns decoded by that skimmer -- including yours when you transmit -- will appear in your Spot Database Display.

+ As has been pointed out in this thread, you can configure SpotCollector to callsigns decoded by skimmers. For more information, see "Using the Reverse Beacon Network with DXLab" in

http://www.dxlabsuite.com/RBN/

73,

Dave, AA6YQ


Re: Apparently self spotting my call in SpotCollector?

Ed
 

A few years back, 90% of the time i used CW.  Have not used SpotCollector  for quite awhile, playing with FT-8.
So
In my Spot Sources, I had one Host Address as: dxc.ve7cc.net  port 7373    

VE7CC is causing this to happen with enabled checked.  When not enabled, problem goes away.   Will see how it goes.

ED  WA6WGS


Re: Enter call in WinWarbler

Daniel W9DGI
 

Thanks very much Dave; I had searched the WinWarbler documentation -- it hadn't occurred to me to look for the answer in the SpotCollector instructions. DXLabs is a wonderfully capable set of programs!
73
Daniel W9DGI


Re: Apparently self spotting my call in SpotCollector?

ve3ki
 

RBN spots do not come from your skimmer (if you had one); they come from someone else's skimmer (the callsign before the -# tells you whose skimmer spotted you). There may be a command you can send to the cluster node to turn RBN spots off, but regardless, these are not self-spots - you have been spotted by someone else, namely the station whose callsign appears as the source.

73,
Rich VE3KI


On Fri, Nov 19, 2021 at 06:28 PM, Ed wrote:
Hi Joe,

I have no skimmer software.
Looking in SpotCollector Configuration only Dxpots.com is checked for Spot,  Likewise WSJT-x is not enabled.

Ed


Re: Apparently self spotting my call in SpotCollector?

Joe Subich, W4TV
 

Go to Spot Collector -> Config -> Special Callsigns and *CHECK* the
"Discard spots from spotting station callsigns ending in -#"

This will cause SpotCollector to ignore any spots from skimmer stations
(being relayed by DXspots.com).

Or ... go to the Window for DXSpots and type in SET/NOSKIMMER <enter>
this will tell DXSpots not to send you skimmer originated spots.

73,

... Joe, W4TV

On 2021-11-19 6:28 PM, Ed wrote:
Hi Joe,
I have no skimmer software.
Looking in SpotCollector Configuration only Dxpots.com is checked for Spot,  Likewise WSJT-x is not enabled.
Ed

4481 - 4500 of 208958