Date   

Spot Collectoe

Joe
 

What does a blue flashing "Autoscroll" message mean?  How do I correct it?  I see a message when I hover over it but it is truncated and I cant see it all.

Thanks

Joe - N7JEH


Re: DXKeeper LoTW Setup/Handling for Portable Station Callsign

Dave AA6YQ
 

+ AA6YQ comments below

Several contest I participate in require a US call district suffix. Since I have a 4th district US callsign, I use "AC4CA/5" from Texas.

The N1MM ADIF generated shows the correct station callsign for each record (AC4CA/5). I created a DXKeeper database for such contest requiring the "/5" suffix.

+ Since those contest QSOs were made from the same DXCC entity as those made with your AC4CA callsign and thus "count" towards your DXCC awards, they should be recorded in your AC4CA log, not a separate log. Each contest QSO's STATION_CALLSIGN item should be set to AC4CA/5.

The DXKeeper default station callsign is "AC4CA/5." DXKeeper QSL Config is setup to log into the AC4CA LoTW account but uses an "AC4CA/5" LoTW certificate. (The AC4CA/5 certificate aggregates to the AC4CA certificate for awards.) I use this station location and station callsign in DXKeeper QSL Config when uploading to LoTW. The N1MM-generated ADIF loads properly into DXKeeper. The QSOs upload correctly to LoTW and show and show a "U" in the LotW Sent (L/S) field. When I attempt to "Sync LoTW QSOs" the process hangs, apparently, but given the size of the QSO ADIF returned from LoTW it might be chugging at the large file (cf. below). Checking the DXKeeper error log, it shows LoTW returning an ~11mB LoTW_QSOs_ADI.txt file that contains the 287 AC4CA/5 records but also a ton of AC4CA records. This tells me I have something setup wrong for handling these QSO/QSLs, most likely in DXKeeper. I have the DXKeeper error log text file ready for inspection. I'm wondering if I'm going about tracking these "/5" QSOs all wrong in DXKeeper.

+ As noted above, you are logging those QSOs incorrectly. After making backup copies of your log files and then combining them into your AC4CA log, I suggest that you review

<https://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations>;

+ If this doesn't get you going, please let me know.

73,

Dave, AA6YQ


DXKeeper LoTW Setup/Handling for Portable Station Callsign

John AC4CA
 

Several contest I participate in require a US call district suffix. Since I have a 4th district US callsign, I use "AC4CA/5" from Texas. The N1MM ADIF generated shows the correct station callsign for each record (AC4CA/5). I created a DXKeeper database for such contest requiring the "/5" suffix. The DXKeeper default station callsign is "AC4CA/5."  DXKeeper QSL Config is setup to log into the AC4CA LoTW account but uses an "AC4CA/5" LoTW certificate. (The AC4CA/5 certificate aggregates to the AC4CA certificate for awards.) I use this station location and station callsign in DXKeeper QSL Config when uploading to LoTW. The N1MM-generated ADIF loads properly into DXKeeper. The QSOs upload correctly to LoTW and show and show a "U" in the LotW Sent (L/S) field. When I attempt to "Sync LoTW QSOs" the process hangs, apparently, but given the size of the QSO ADIF returned from LoTW it might be chugging at the large file (cf. below). Checking the DXKeeper error log, it shows LoTW returning an ~11mB LoTW_QSOs_ADI.txt file that contains the 287 AC4CA/5 records but also a ton of AC4CA records. This tells me I have something setup wrong for handling these QSO/QSLs, most likely in DXKeeper. I have the DXKeeper error log text file ready for inspection. I'm wondering if I'm going about tracking these "/5" QSOs all wrong in DXKeeper. How do others handle these QSOs?


Re: Filtering WSJTX spots

Dick Grote
 

Thanks, Dave.  I don't think that I would have ever figured that out.

73,
--
Dick
K6PBF


Re: Filtering WSJTX spots

Dave AA6YQ
 

+ AA6YQ comments below

I have several SQL search filters which I've written for SpotCollector. My favorite (labeled BEST) is one which shows me needed spots which either have a good enough propagation SNR or has a ODX within 500 miles of by QTX. When I started using WSJTX as an additional spot source, things have gotten complicated. A lot of WSJTX spots show up in the BEST filter on the band which my radio is tuned to, but most of them have never been decoded by me. In other words, for many of these spots the ActualSNR value is empty. I'd rather not see these spots displayed in SpotCollector until I've actually had a decode and a chance of working them. Otherwise they tend to overload the display and I may lose track of opportunities from other spot sources on other bands.

I've tried adding additional conditions to my SQL filter that would only show spots from WSJTX that had a ActualSNR value. For example I tried (Network LIKE 'WSJTX' AND ActualSNR is NULL) or (Network LIKE 'WSJTX' AND ActualSNR = 0) and many variants of this without success. Some give me errors and the rest don't work.

Any thoughts? Is this approach reasonable and I just haven't figured out the correct SQL syntax or is there a better way?

+ If there is no ActualSNR value to record, SpotCollector sets the ActualSNR field to -9999, so the SQL Filter you want is

((Network LIKE 'WSJTX') AND (ActualSNR = -9999))

+ I neglected to document this value; this defect has been corrected in

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#SDB%20ActualSNR

73,

Dave, AA6YQ


Re: Enhancement request, qsl

Dave AA6YQ
 

+ AA6YQ comments below

Wondering if in dxkeeper, an indicator can be included to show an SASE is requested from the recipient. Or 'green stamps?

+ You could record that information in the QSO's comments item.

+ To find all QSOs requesting a SASE, you could then filter the Log Page Display with

Comment like '*SASE*'

+ To find all QSOs requesting green stamps, you could then filter the Log Page Display with

Comment like '*green*'

+ In DXKeeper's Capture window, the Comment item shares space with the "QSL Msg" item on the 10th row of text boxes. If the "QSL Msg" item is visible, click its ~ button to make the Comment item visible.

+ On the Main window's "Log QSOs" tab, the Comments item is present in the Details panel above the Log Page Display.

73,

Dave, AA6YQ


Re: Enhancement request, qsl

Mike Rhodes / W8DN
 

Robert,
  Are you talking about when a station requests SASE, etc., or when you have sent such? If a station is requesting it, how would that be known? I don't believe there is a place that tracks that sort of info. The only time I see that is in the occasional DX bulletin and that would be a nearly impossible job to administer (that is, unless you are volunteering ;-) . If you wish to track what you have or will send then I would think a 'standard' phrase in the comments would allow you to sort based on that 'phrase'.

Mike / W8DN

On 8/17/2020 12:38 PM, Robert galambos wrote:
Wondering if in dxkeeper, an indicator can be included to show an SASE is requested from the recipient. Or 'green stamps?

Just a thought

DEC for YORK & DURHAM Region ARES.
ASEC GTA ARES section
: +1-416-876-2979
H:  +1-416-227-1414
E:   va3bxg@...
When all else fails


Filtering WSJTX spots

Dick Grote
 

I have several SQL search filters which I've written for SpotCollector.  My favorite (labeled BEST) is one which shows me needed spots which either have a good enough propagation SNR or has a ODX within 500 miles of by QTX.  When I started using WSJTX as an additional spot source, things have gotten complicated.  A lot of WSJTX spots show up in the BEST filter on the band which my radio is tuned to, but most of them have never been decoded by me.  In other words, for many of these spots the ActualSNR value is empty.  I'd rather not see these spots displayed in SpotCollector until I've actually had a decode and a chance of working them. Otherwise they tend to overload the display and I may lose track of opportunities from other spot sources on other bands. 

I've tried adding additional conditions to my SQL filter that would only show spots from WSJTX that had a ActualSNR value.  For example I tried
(Network LIKE 'WSJTX' AND ActualSNR is NULL)  or (Network LIKE 'WSJTX' AND ActualSNR = 0)
and many variants of this without success.  Some give me errors and the rest don't work.

Any thoughts?  Is this approach reasonable and I just haven't figured out the correct SQL syntax or is there a better way?

Thanks, 

--
Dick
K6PBF


Enhancement request, qsl

Robert galambos
 

Wondering if in dxkeeper, an indicator can be included to show an SASE is requested from the recipient. Or 'green stamps?

Just a thought

DEC for YORK & DURHAM Region ARES.
ASEC GTA ARES section
: +1-416-876-2979
H:  +1-416-227-1414
E:   va3bxg@...
WL: va3bxg@...

When all else fails


Re: Time zone

eddy on5jk
 

Thanks Joe.

This means that i didn't miss a setting.

Now i am shure of it.

Eddy ON5JK

Op 17/08/2020 om 14:47 schreef Joe Subich, W4TV:


Is there any setting i missed?
No.  Not only is there no one standard for the start/end of
summer time (daylight saving time), not all countries (or
even states within the US) observe summer time.

It would be a major problem to update the DXCC database to enable
DXV to reflect the difference between local time for the user and
local time for the DX station under all conditions.  As it is,
DXV can show the difference within an hour which is generally
close enough to allow for accurate "good morning", "good afternoon"
or "good evening" ....

73,

   ... Joe, W4TV


On 2020-08-17 5:02 AM, eddy on5jk wrote:
Dave,

In Belgium we use wintertime/summertime.

When i look at DXV, the Belgian timezone is still marked: UTC+1

Now we are in summertime. So local time now is UTC+2.

Is there any setting i missed?

Thanks, 73

Eddy ON5JK




Re: Time zone

Joe Subich, W4TV
 

Is there any setting i missed?
No. Not only is there no one standard for the start/end of
summer time (daylight saving time), not all countries (or
even states within the US) observe summer time.

It would be a major problem to update the DXCC database to enable
DXV to reflect the difference between local time for the user and
local time for the DX station under all conditions. As it is,
DXV can show the difference within an hour which is generally
close enough to allow for accurate "good morning", "good afternoon"
or "good evening" ....

73,

... Joe, W4TV


On 2020-08-17 5:02 AM, eddy on5jk wrote:
Dave,
In Belgium we use wintertime/summertime.
When i look at DXV, the Belgian timezone is still marked: UTC+1
Now we are in summertime. So local time now is UTC+2.
Is there any setting i missed?
Thanks, 73
Eddy ON5JK


Time zone

eddy on5jk
 

Dave,

In Belgium we use wintertime/summertime.

When i look at DXV, the Belgian timezone is still marked: UTC+1

Now we are in summertime. So local time now is UTC+2.

Is there any setting i missed?

Thanks, 73

Eddy ON5JK


Re: FW: [adifdev] Proposal for new MFSK submode

Dave AA6YQ
 

I have extended the next version of DXKeeper to support FST4 on the assumption that the proposed addition to ADIF will be accepted.

If anyone who is testing WSJT-X 2.3 would like access to this new version, please send me email via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Sunday, August 16, 2020 4:45 PM
To: DXLab@groups.io
Subject: Re: [DXLab] FW: [adifdev] Proposal for new MFSK submode

+ AA6YQ comments below

On Sun, Aug 16, 2020 at 12:26 AM, Tony Dixon G4CJC wrote:

Thanks for the info. Where can I find out more about FST4?

+ The following is courtesy of Rick K1MU:

Version 2.3 of WSJT-X introduces a new family of digital modes we designate FST41 . These modes have a wide range of capabilities and potential applications. Their fundamental sensitivities are better than most older modes in WSJT-X and are close to the theoretical limits for the same information throughput rates. Particular target applications include ▪ WSPR-like, quasi-beacon transmissions on LF and MF bands ▪ QSOs with very weak signals on the LF and MF bands ▪ EME on VHF and UHF bands with T/R sequences both shorter and longer than 60 s ... but other uses will surely be found, as well. We expect that FST4 will serve some of its intended purposes better than older modes in WSJT-X, and without the strict time- and frequency-locking requirements of modes such as EbNaut.

FST4 uses 4-GFSK modulation and offers T/R sequence lengths of 15, 30, 60, 120, 300, 900, and 1800 s. Submodes A, B, C, and D provide different tone spacings, to allow for use with a variety of propagation types and Doppler spreads. Forward error correction uses a low density parity check (LDPC) code with 240 information and parity bits. Transmissions consist of a sequence of 120 information-carrying symbols (2 bits each) interspersed with 40 synchronizing symbols. The underlying message payloads contain either 77 bits (the standard payload for FT4, FT8, and MSK144) or 50 bits (the standard for quasi-beacon, WSPR-style messages). With WSPR-like messages the mode designation becomes FST4W and the A submode is always used. In all cases, message formats displayed to the user are the same as in the other 50-bit and 77-bit modes in WSJT-X


73,


Dave, AA6YQ



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


Re: FW: [adifdev] Proposal for new MFSK submode

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Aug 16, 2020 at 12:26 AM, Tony Dixon G4CJC wrote:

Thanks for the info. Where can I find out more about FST4?

+ The following is courtesy of Rick K1MU:

Version 2.3 of WSJT-X introduces a new family of digital modes we designate FST41 . These modes have a wide range of capabilities and potential applications. Their fundamental sensitivities are better than most older modes in WSJT-X and are close to the theoretical limits for the same information throughput rates. Particular target applications include  ▪ WSPR-like, quasi-beacon transmissions on LF and MF bands ▪ QSOs with very weak signals on the LF and MF bands ▪ EME on VHF and UHF bands with T/R sequences both shorter and longer than 60 s ... but other uses will surely be found, as well. We expect that FST4 will serve some of its intended purposes better than older modes in WSJT-X, and without the strict time- and frequency-locking requirements of modes such as EbNaut.

FST4 uses 4-GFSK modulation and offers T/R sequence lengths of 15, 30, 60, 120, 300, 900, and 1800 s. Submodes A, B, C, and D provide different tone spacings, to allow for use with a variety of propagation types and Doppler spreads. Forward error correction uses a low density parity check (LDPC) code with 240 information and parity bits. Transmissions consist of a sequence of 120 information-carrying symbols (2 bits each) interspersed with 40 synchronizing symbols. The underlying message payloads contain either 77 bits (the standard payload for FT4, FT8, and MSK144) or 50 bits (the standard for quasi-beacon, WSPR-style messages). With WSPR-like messages the mode designation becomes FST4W and the A submode is always used. In all cases, message formats displayed to the user are the same as in the other 50-bit and 77-bit modes in WSJT-X 


      73,

           Dave, AA6YQ


Re: Error logging into eQSL.cc for lookup

Dave AA6YQ
 

+ AA6YQ comments below

Hi - I've set up dx keeper with appropriate information, including my login for eqsl.cc.  I can login to the site directly and the login works with other software as well.  However, in dx keeper, when I try to do a lookup I get an error that the username or password is wrong.  Can't figure out what the issue is. 

+ So that I can see what's going on, please do the following:

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

2. Terminate DXKeeper

3. Start DXKeeper

4. Perform whatever action causes the error message cited above to appear

5. On the General tab of DXKeeper's Configuration window, uncheck the "log debugging info" box

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

aa6yq (at) ambersoft.com

     73,

            Dave, AA6YQ


Error logging into eQSL.cc for lookup

MSJ
 

Hi - I've set up dx keeper with appropriate information, including my login for eqsl.cc.  I can login to the site directly and the login works with other software as well.  However, in dx keeper, when I try to do a lookup I get an error that the username or password is wrong.  Can't figure out what the issue is. 

Thanks,
Michael
KB1PIE


Re: commander and or winwarbler cause powersdr to crash

geoff wiggins
 

Thanks Dave.

I have sent a similar email to Darrin, KE9NS who supports powersdr.

73 Geoff.

On 16/08/2020 18:32, Dave AA6YQ wrote:

+ AA6YQ comments below

On Sun, Aug 16, 2020 at 10:29 AM, geoff wiggins wrote:

Just tried to use winwarbler 9.2.9 today for the first time for several months and it immediately causes powersdr to stop and then close. Commander 14.6.5 does the same thing. Using latest win10 2004 version and all the updates, no doubt the issue is hidden here somewhere! Wsjt-x and log4om work fine no issues. Powersdr version 2.8.0.171, ie the latest.

+ By definition, that's a defect in PowerSDR. No one here has previously reported that behavior. I suggest that you report this to whoever is maintaining PowerSDR. If they need my help, I will be happy to provide it.

       73,

              Dave, AA6YQ


Re: commander and or winwarbler cause powersdr to crash

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Aug 16, 2020 at 10:29 AM, geoff wiggins wrote:

Just tried to use winwarbler 9.2.9 today for the first time for several months and it immediately causes powersdr to stop and then close. Commander 14.6.5 does the same thing. Using latest win10 2004 version and all the updates, no doubt the issue is hidden here somewhere! Wsjt-x and log4om work fine no issues. Powersdr version 2.8.0.171, ie the latest.

+ By definition, that's a defect in PowerSDR. No one here has previously reported that behavior. I suggest that you report this to whoever is maintaining PowerSDR. If they need my help, I will be happy to provide it.

       73,

              Dave, AA6YQ


commander and or winwarbler cause powersdr to crash

geoff wiggins
 

Hi, hope someone can help with this. Just tried to use winwarbler 9.2.9 today for the first time for several months and it immediately causes powersdr to stop and then close. Commander 14.6.5 does the same thing. Using latest win10 2004 version and all the updates, no doubt the issue is hidden here somewhere! Wsjt-x and log4om work fine no issues. Powersdr version 2.8.0.171, ie the latest.
Thanks in advance,
73 Geoff G4XMJ


Re: FW: [adifdev] Proposal for new MFSK submode

neil_zampella
 

I agree ... there's not much on the DEV list either.   This is fairly
close-hold to the developers right now.  Although Bill Somerville
mentioned that the beta is close to a test release in the next few weeks.

Neil, KN3ILZ

On 8/16/2020 7:18 AM, Joe Subich, W4TV wrote:

I would suggest the WSJTX Developers Group.  There is little
information being shared publicly.

73,

   ... Joe, W4TV


On 2020-08-16 3:26 AM, Tony Dixon G4CJC wrote:
Thanks for the info. Where can I find out more about FST4?
73
Tony, G4CJC

3221 - 3240 of 198998