Date   

Re: Modes that can be submitted to LoTW

Joe Subich, W4TV
 

On 2018-10-07 5:54 PM, Dave AA6YQ wrote:
Why is IRLP accepted while INTERNET and RPT are not accepted?

Is there a reason to not accept QSOs made with any ADIF-defined propagation mode? Presumably each award will ignore QSOs made with propagation modes excluded by its rules.
LotW should not accept *non-amateur* QSOs period. That means that
IRLP should be deleted from the tQSL Configuration file and any
IRLP QSOs purged from the LotW database.

73,

... Joe, W4TV


On 2018-10-07 5:54 PM, Dave AA6YQ wrote:
When determining which propagation modes will be accepted in QSOs being submitted to LoTW, TQSL is governed by the "Configuration
Data" file periodically distributed by the ARRL. The current "Configuration Data" file, version 11.5, specifies these propagation
modes as acceptable:
AUE Aurora-E
AUR Aurora
BS Back scatter
ECH EchoLink
EME Earth-Moon-Earth
ES Sporadic E
F2 F2 Reflection
FAI Field Aligned Irregularities
ION Ionoscatter
IRL IRLP
MS Meteor scatter
RS Rain scatter
SAT Satellite
TEP Trans-equatorial
TR Tropospheric ducting
The current ADIF specification (3.0.8) specifies the above propagation modes plus 3 others:
AS Aircraft Scatter
INTERNET Internet-assisted
RPT Terrestrial or atmospheric repeater or transponder
"Aircraft Scatter" is a relatively new addition to ADIF that just hasn't yet been added to "Configuration Data". Is there any reason
to not include it in the next version?
I understand that QSOs made via the Internet or via a repeater are not valid for any of the awards that currently accept LoTW
confirmations. However, this is also true of IRLP, which is voice-over-ip, possibly via the internet:
<http://www.irlp.net/>
Why is IRLP accepted while INTERNET and RPT are not accepted?
Is there a reason to not accept QSOs made with any ADIF-defined propagation mode? Presumably each award will ignore QSOs made with
propagation modes excluded by its rules.
73,
Dave, AA6YQ


Re: WJST and LOTW

Dave AA6YQ
 

+ AA6YQ comments below

It was just too hard to do the Safe Mode boot because it wouldn't load all the drivers I need.

+ Booting Windows into "Safe Mode with Networking" is only intended as a diagnostic. Though drivers wouldn't be loaded, you'd be able to tell whether or not DXKeeper, WSJT-X, and JTAlert were interoperating.

So I used my head instead. What changed?

+ Exactly the right question to ask!

I disabled newly installed MalWareBytes and now DxKeeper and JTAlert are friends again.

+ Using MalwareBytes for continuous antimalware protection was added to the "known to interfere" list a week or two ago:

<https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference>

73,

Dave, AA6YQ


Re: WJST and LOTW

Buck
 

It was just too hard to do the Safe Mode boot because it wouldn't load all the drivers I need. So I used my head instead. What changed?

I disabled newly installed MalWareBytes and now DxKeeper and JTAlert are friends again.

k4ia, Buck
K3# 101
Honor Roll 8B DXCC
EasyWayHamBooks.com

On 10/1/2018 11:13 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
No joy Dave. I followed all those settings when I first set it up and just went over them again. Nothing has changed except I got a new password for LOTW.
I changed the password in DxKeeper but when I end a QSO I get a message
JTAlertX: QSO to DXLan DXKeeper
FAILURE: QSO Not logged!
ERROR Message: DXKeeper File: Unable to confirm QSO logged
When I look in DXKeeper, the QSO is not logged.
+ DXKeeper can't submit a QSO to LoTW if that QSO hasn't been logged. So let's forget about the changed LoTW password for now, and determine why JTAlert is suddenly unable to log QSOs to DXKeeper. As a first diagnostic step, please reboot Windows into "Safe Mode with Networking", and then start Commander, DXKeeper, WSJT-X, and JTAlert. Can you now log an FT8 QSO to DXKeeper via JTAlert?
73,
Dave, AA6YQ


updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Modes that can be submitted to LoTW

Dave AA6YQ
 

When determining which propagation modes will be accepted in QSOs being submitted to LoTW, TQSL is governed by the "Configuration
Data" file periodically distributed by the ARRL. The current "Configuration Data" file, version 11.5, specifies these propagation
modes as acceptable:

AUE Aurora-E
AUR Aurora
BS Back scatter
ECH EchoLink
EME Earth-Moon-Earth
ES Sporadic E
F2 F2 Reflection
FAI Field Aligned Irregularities
ION Ionoscatter
IRL IRLP
MS Meteor scatter
RS Rain scatter
SAT Satellite
TEP Trans-equatorial
TR Tropospheric ducting

The current ADIF specification (3.0.8) specifies the above propagation modes plus 3 others:

AS Aircraft Scatter
INTERNET Internet-assisted
RPT Terrestrial or atmospheric repeater or transponder

"Aircraft Scatter" is a relatively new addition to ADIF that just hasn't yet been added to "Configuration Data". Is there any reason
to not include it in the next version?

I understand that QSOs made via the Internet or via a repeater are not valid for any of the awards that currently accept LoTW
confirmations. However, this is also true of IRLP, which is voice-over-ip, possibly via the internet:

<http://www.irlp.net/>

Why is IRLP accepted while INTERNET and RPT are not accepted?

Is there a reason to not accept QSOs made with any ADIF-defined propagation mode? Presumably each award will ignore QSOs made with
propagation modes excluded by its rules.

73,

Dave, AA6YQ


Re: New version of TQSL

Curt Bowles
 

Hello All...

Tried to update TQSL to 2.4.1 buy going to TQSL Tab "Help/Check for updates"... it DID NOT update to 2.4.1

Had to go to http://www.arrl.org/tqsl-download and actually download the file and install it. No problems!

73
--
Curt Bowles
VE3ZN


Data-deletion bug forces Microsoft to suspend rollout of Windows 10 update

Dave AA6YQ
 

Yet another reason why it's critical to backup your files and settings:

<https://arstechnica.com/gadgets/2018/10/microsoft-suspends-distribution-of-latest-windows-10-update-over-data-loss-bug/>

For step-by-step instructions, see

<https://www.dxlabsuite.com/dxlabwiki/BackupRecovery>

Yes, this counts as October's "Harangue".

73,

Dave, AA6YQ


Re: SpotCollector - Special Tags

Dave AA6YQ
 

+ AA6YQ comments below

On Mon, Oct 1, 2018 at 10:11 AM, Bob WB2NVR wrote:

If I remove filtering (either by clicking the X or entering CNTRL X), most of the entities listed in my SpotCollector window are showing up as Special Tag (light green). The Tag column in the SpotCollector display for these entries are all blank. Right clicking on the first column to display the Award Tracking for a random entry (VO1FOG) shows confirmed, sought for DXCC, WAZ, worked, sought for Marathon. Other entries are similar. In SpotCollector Special Callsigns, I have a number of BadSource calls listed, but nothing as a Special Tag.

Clearly, something isn't set correctly, but I can't seem to find out what it might be. Can you provide any suggestions

The cause of the above behavior was that the coloring for un-needed entries and the coloring for entries for "special callsigns" were configured to be similar colors.

       73,

             Dave, AA6YQ


Re: spot collector, no mode showing

Dave AA6YQ
 

+ AA6YQ comments below

Its SC 8.0.6 Dave.

+ SpotCollector 8.0.6 includes the file

bandmodes 2017-12-27.txt

+ If it's not present on your system, then either you inadvertently deleted it, or your computer system is broken.

+ I've sent you a copy of the above file via email.

73,

Dave, AA6YQ

On October 7, 2018 at 3:14 PM Dave AA6YQ <aa6yq@...> wrote:


What version number does SpotCollector display in its Main window's title bar?


Got the DXLab suite up and running and all seems well, until I attempt to bring SpotCollector up, and it all comes up well except there is a box on the screen saying:

band mode file c:\dxlab\spotcollector\bandmodes 2017-12-27.txt does not exist, spot databaase entries wil be missing band and mode fields."

Indeed , when I click OK , SC comes up and there is no mode listed on any entry from day one, until now. That happened yesterday when I got the W10 back up ''

Did a search for that file, and there isnt one in the computer. Not sure where to go from here?


Re: Flex 6600: Loss of Frequency Control with 2.4.9

Dave AA6YQ
 

+ AA6YQ comments below

When I upgraded to SmartSDR 2.4.9 it fixed the spot/receiver problem, however, I have now lost reliable frequency control between SmartSDR
2.4.9 and Commander. After a few minutes I lose communications and I have to go into Commanders config and reset the rig interface.

I downgraded to SmartSDR 2.3.9 and have regained reliable frequency control.

I noticed the same situation with N3FJP's contest logging software. I had issues with 2.4.9 but resolved the issue by down grading to 2.3.9.

I may have to go to 2.3.7 as the receiver interuption's are quite annoying, even if I turn off spot settings in SmartSDR.

Has anyone else noticed this? or is this unique to my station/computer.

+ I encountered not problems of any kind with SmartSDR 2.3.9.

+ After upgrading to SmartSDR 2.4.9, I encounter audio dropouts when SmartSDR repaints callsigns on its panadaptor; sometimes the "RF Power" slider is zeroed by this action - not a great thing to have happen in the middle of a QSO!

+ SmartSDR 2.4.9 is clearly defective, and should be avoided until Flex identifies and corrects the responsible defects. I have received no further information from Flex since conveying to them the problems with SmartSDR 2.4.9 reported by users here.

73,

Dave, AA6YQ


Re: spot collector, no mode showing

Danny Douglas <n7dc@...>
 

Its SC 8.0.6 Dave.

N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On October 7, 2018 at 3:14 PM Dave AA6YQ <aa6yq@...> wrote:


What version number does SpotCollector display in its Main window's title bar?

73,

Dave, AA6YQ



Got the DXLab suite up and running and all seems well, until I attempt to bring SpotCollector up, and it all comes up well except there is a box on the screen saying:

band mode file c:\dxlab\spotcollector\bandmodes 2017-12-27.txt does not exist, spot databaase entries wil be missing band and mode fields."

Indeed , when I click OK , SC comes up and there is no mode listed on any entry from day one, until now. That happened yesterday when I got the W10 back up ''

Did a search for that file, and there isnt one in the computer. Not sure where to go from here?




Re: spot collector, no mode showing

Dave AA6YQ
 

What version number does SpotCollector display in its Main window's title bar?

73,

Dave, AA6YQ



Got the DXLab suite up and running and all seems well, until I attempt to bring SpotCollector up, and it all comes up well except there is a box on the screen saying:

band mode file c:\dxlab\spotcollector\bandmodes 2017-12-27.txt does not exist, spot databaase entries wil be missing band and mode fields."

Indeed , when I click OK , SC comes up and there is no mode listed on any entry from day one, until now. That happened yesterday when I got the W10 back up ''

Did a search for that file, and there isnt one in the computer. Not sure where to go from here?


Re: A DxKeeper Question about Prop_Mode. I am not sure I have ever logged a local Repeater Contact.

Dave AA6YQ
 

+ AA6YQ comments below

"Propagation Mode" in a lot of my contacts does not get set at all - mainly because I rarely remember to set it (I don't often log RPT QSO's) - as far as I have seen TQSL accepts those without any error.

+ Yes it does, and the "Add Requested" function in the next version of DXKeeper will continue to process QSOs whose "Propagation Mode" item is empty.

+ Stewart, you can specify a default "Propagation Mode" on the Configuration window's Defaults tab. I have mine set to F2, but change it to Es during 6M openings. TEP is another propagation mode we might encounter on the higher bands.

73,

Dave, AA6YQ


Re: Anniversary of DXView

Dave AA6YQ
 

Thanks, Mark!

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Mark W2OR via Groups.Io
Sent: Sunday, October 07, 2018 8:58 AM
To: DXLab@groups.io
Subject: [DXLab] Anniversary of DXView

This October is the 18-th anniversary of DXView, one of the many action-packed apps from it founder, Dave, AA6YQ. Three of the suite's apps were announced and activated in Year 2000. Big Congrats !!

And many thanks.



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


spot collector, no mode showing

Danny Douglas <n7dc@...>
 

As a follow up and addition to below.  I found the SpotCollector Config, general tab, sub band definition  and all it was saying is "modes 2017-12-1227.txt.  so changed that to the whole  file pathname as I give below, hit select and another box opens with  two names  DATABASES, and SOLAR-HISTROY,.   Clicked on the Databases, and results in "no items match your search.  So still dont know where this one went (mabe the stupid W10 updated, and happned after I read the new update was no good and people losing databases.  Apparently it was already in my computer (had never seen that they were uploading it to me), but it took and  had the below problem at the same time. 




N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

---------- Original Message ----------
From: Danny Douglas <n7dc@...>
To: DXLab@groups.io
Date: October 7, 2018 at 9:58 AM
Subject: [DXLab] spot collector, no mode showing

Got the DXLab suite up and running and all seems well, until I attempt to bring SpotCollector up, and it all comes up well except there is a box on the screen saying:

"

Spotcollector

band mode file c:\dxlab\spotcollector\bandmodes 2017-12-27.txt does not exist, spot databaase entries wil be missing band and mode fields."


Indeed , when I click OK , SC comes up and there is no mode listed on any entry from day one, until now.  That happened yesterday when I got the W10 back up ''


Did a search for that file, and there isnt one in the computer.  Not sure where to go from here?





N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.


 


Re: Flex 6600: Loss of Frequency Control with 2.4.9

John Battin
 

I run 2.3.9 and it seems to work ok with commander. I am not a computer whiz so that is all I can say.

John k9dx

 


From: DXLab@groups.io <DXLab@groups.io> on behalf of RIchard Thorne <rthorne@...>
Sent: Sunday, October 7, 2018 10:53:45 AM
To: dxlab@groups.io
Subject: [DXLab] Flex 6600: Loss of Frequency Control with 2.4.9
 
When I upgraded to SmartSDR 2.4.9 it fixed the spot/receiver problem,
however,   I have now lost reliable frequency control between SmartSDR
2.4.9 and Commander.  After a few minutes I lose communications and I
have to go into Commanders config and reset the rig interface.

I downgraded to SmartSDR 2.3.9 and have regained reliable frequency control.

I noticed the same situation with N3FJP's contest logging software. I
had issues with 2.4.9 but resolved the issue by down grading to 2.3.9.

I may have to go to 2.3.7 as the receiver interuption's are quite
annoying, even if I turn off spot settings in SmartSDR.

Has anyone else noticed this?  or is this unique to my station/computer.

Thanks in advance.

Rich - N5ZC






Flex 6600: Loss of Frequency Control with 2.4.9

RIchard Thorne
 

When I upgraded to SmartSDR 2.4.9 it fixed the spot/receiver problem, however,   I have now lost reliable frequency control between SmartSDR 2.4.9 and Commander.  After a few minutes I lose communications and I have to go into Commanders config and reset the rig interface.

I downgraded to SmartSDR 2.3.9 and have regained reliable frequency control.

I noticed the same situation with N3FJP's contest logging software. I had issues with 2.4.9 but resolved the issue by down grading to 2.3.9.

I may have to go to 2.3.7 as the receiver interuption's are quite annoying, even if I turn off spot settings in SmartSDR.

Has anyone else noticed this?  or is this unique to my station/computer.

Thanks in advance.

Rich - N5ZC


spot collector, no mode showing

Danny Douglas <n7dc@...>
 

Got the DXLab suite up and running and all seems well, until I attempt to bring SpotCollector up, and it all comes up well except there is a box on the screen saying:

"

Spotcollector

band mode file c:\dxlab\spotcollector\bandmodes 2017-12-27.txt does not exist, spot databaase entries wil be missing band and mode fields."


Indeed , when I click OK , SC comes up and there is no mode listed on any entry from day one, until now.  That happened yesterday when I got the W10 back up ''


Did a search for that file, and there isnt one in the computer.  Not sure where to go from here?





N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.


Re: SpotCollector Filter

Salvatore Besso
 

please, don't reply changing the subject to initiate a new thread, as often occurs!

73 de
Salvatore (I4FYV)


Anniversary of DXView

Mark W2OR <reston2010mm-orders@...>
 

This October is the 18-th anniversary of DXView, one of the many action-packed apps from it founder, Dave, AA6YQ.  Three of the suite's apps were announced and activated in Year 2000.   Big Congrats !!  

And many thanks.  

30581 - 30600 of 211182