Date   
Re: SQL String

Don Inbody AD0K
 

Next question. How do I restrict that SQL string (DXCCPrefix<>'K') to only the transceiver band? That one disregards the transceiver band.

Re: Dual modes same freq with Commander & 6400 Flex

Dave AA6YQ
 

+ AA6YQ comments below

Dave, I have the same problem with Flexradio 6700 running SSDR v3.1.8.145. When I start Commander, with only Slice A on, Slice B opens up on the same frequency as Slice A. I can delete Slide B with no problem but there is definitely some interaction going on. I have not found any other problems.

+ On the Configuration window's Radio tab, do you have the "Create VFO B at startup" box checked?

73,

Dave, AA6YQ

Interesting Issue with DXC/WSJT-X and Kenwood TS-590sg

Hasan Schiers N0AN
 

Win10 Pro, Latest, 8 gB Ram, Intel Core I5
On FT8 (or any digital mode of WSJT-X.)

I was frequently being told by a distant station (while we were experimenting and troubleshooting) that the freq I said I was tx'ing on was NOT the freq I was really on. Many times during our experiment I was 500 or 1000 Hz off. (Always, exactly that amount).

After playing around with as many variables that seemed to be potentially connected to the problem, I stumbled on it:

In WSJT-X > Settings > Radio, I had to increase the Poll Interval (Extreme Right from Rig:), from 1 sec to 2 sec.

Problem solved. The freq was not getting properly updated.

Just in case anyone has a similar problem.

In FT8, the problem is not obvious, because FT8 doesn't care what freq you transmit own, it decodes the entire passband. I only noticed it when we were trying to fix another fellow's Anan, which was showing frequency instability (slanted decodes).

73, N0AN
Hasan

Re: Dual modes same freq with Commander & 6400 Flex

Ed Ireland
 

Dave, I have the same problem with Flexradio 6700 running SSDR v3.1.8.145.  When I start Commander, with only Slice A on, Slice B opens up on the same frequency as Slice A.  I can delete Slide B with no problem but there is definitely some interaction going on.  I have not found any other problems.

Thanks,

Ed K5YZW

On Mon, Jan 20, 2020 at 12:33 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

SmartSDR with VFO A on one frequency. When I shutdown SmartSDR and relaunch with Commander running the whole time I get VFO A AND VFO B on Same Frequency with opposite modes? USB/LSB, DIGU/DIGL. It is repeatable as when commander is off no funny business. Other than that weird operation Commander works perfectly with Flex 6400 and SmartSDR 2.6.1. Using 14.4 Commander.

+ On initial connection, Commander does not direct SmartSDR to QSY; when SmartSDR starts up with Commander already running, Commander's VFO A and VFO B display SmartSDR's Slice A and B frequencies and modes, respectively.  I don't see the behavior you report above with my Flex 6500 running SmartSDR 3.1.7.138.

       73,

               Dave, AA6YQ





Re: Spot Collector

Dave AA6YQ
 

+ AA6YQ comments below

Please give me the settings to implement the Arcala - dxCluster into the Spot-Collector Here the site:
http://www.dxsummit.fi/#/
I can get results of DL9GTB, W1NR, EI7MRE and HA6DX but not the finnish cluster.

Could somebody help me please ?

+ Instructions for connecting to the "DX Summit" web cluster are here:

<https://www.dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting%20to%20the%20#CQDX%20IRC%20channel>

+ Alternatively, click the Help button at the top of SpotCollector's Main window, and navigate to the "DX Summit" element of the "Connecting to Spot Sources" section.

73,

Dave, AA6YQ

Spot Collector

Germain Schutz
 

Hello everyone,
Please give me the settings to implement the Arcala - dxCluster into the Spot-Collector
Here the site:
http://www.dxsummit.fi/#/
I can get results of DL9GTB, W1NR, EI7MRE and HA6DX but not the finnish cluster.




Could somebody help me please ?
Great thanks in Advance
'73 from LX1SG

Re: SQL String

Inbody, Don
 

Thanks, Mike. Both are handy, but the first is what I actually meant to ask for.

73

Don Inbody
Buda, TX


On Mon, Jan 20, 2020 at 1:21 PM ND9G Mike <mike.nd9g@...> wrote:
I'm not sure if you're wanting to also exclude KH6/KL7 spots, or want them along with other DX spots. Also assuming you're looking for spots of non-US stations, and not spot sources.

With KH6/KL7 to be shown:  DXCCPrefix<>'K'  

Also ignore KH6/KL7: DXCCPrefix NOT IN ('K','KH6','KL7')

73,
Mike ND9G


On Mon, Jan 20, 2020 at 1:11 PM Don Inbody AD0K <ad0k@...> wrote:
What would the SQL string be to only show non-US (excluding KH6 and KL7) spots?

Re: SQL String

ND9G Mike
 

I'm not sure if you're wanting to also exclude KH6/KL7 spots, or want them along with other DX spots. Also assuming you're looking for spots of non-US stations, and not spot sources.

With KH6/KL7 to be shown:  DXCCPrefix<>'K'  

Also ignore KH6/KL7: DXCCPrefix NOT IN ('K','KH6','KL7')

73,
Mike ND9G


On Mon, Jan 20, 2020 at 1:11 PM Don Inbody AD0K <ad0k@...> wrote:
What would the SQL string be to only show non-US (excluding KH6 and KL7) spots?

SQL String

Don Inbody AD0K
 

What would the SQL string be to only show non-US (excluding KH6 and KL7) spots?

Re: Dual modes same freq with Commander & 6400 Flex

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the reply Dave. "Could" it be a bug in SmartSDR 2.6.1 that is the issue.

+ I don't know.

I can not be definitive but it "may" have started with the last Flex 2.6.1 upgrade? It is not a show stopper so I'll just wait for the next Flex upgrade. I really don't want to back up to the previous Flex software to find out.

+ Since the behavior has no adverse operational impact, me neither.

73,

Dave, AA6YQ

Re: Spot Collector Filtering

Dave AA6YQ
 

+ AA6YQ comments below

I am going to push hard this year to finish up my 5BWAS.

I forgot how to set up Spot Collector to just show spots from states that I still need on whatever band(s).

+ In the "WAS Bands & Modes" panel on the Awards tab of DXKeeper's Configuration window, check the 80m, 40m, 20m, 15m, 10m boxes,
and "Realtime Award Progress" boxes. On DXKeeper's Main window's "Check Progress" tab, click the Recompute button along the bottom.
When that operation finishes, on the "Spot Database" tab of SpotCollector's Configuration window, click the Recompute button to
update the existing Spot Database Entries to reflect your new WAS award goals.

+ See

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

73,

Dave, AA6YQ

Re: JARL progress reports

Dave AA6YQ
 

+ AA6YQ comments below

I was in the process of controlling/updating my two possible Japanese Awards, JCC and JCG and I have a couple of questions regarding the “JARL progress reports” in DxKeeper.

JCC (for Cities) has references composed by 4 numbers (plus, in few cases, 6 numbers), JCG (for Guns) by 5 numbers (always).

JCC and JCG are not **overlapping** each other and are designating completely **independent** areas.


In “DxKeeper/Log QSOs/Award for Japanese calls” there is a field “prefecture” and another one “city/gun”.

Easy to insert the JCG Guns putting in “prefecture” the first two numbers and then chose in “city/gun” the proper reference.

For JCC how to proceed? Not taking into consideration “prefecture” and only indicate the 4 (or 6) numbers in “city/gun”?

+ If a logged QSO with a Japanese stations specifies a prefecture, the Subdivision selector will be populated with all cities and guns within that prefecture. Choose the one specified by your QSO partner over the air, or on his or her QSL card.


And then the reports are properly extracting, separately, only JCC or JCG?

+ Yes. Cities and Guns are distinguishable by the length of their reference numbers.

Is the algorithm behind the report/extraction working separately for JCC and JCG?

+ Yes.


Furthermore, downloading from Lotw, I have seen that for JCC automatically both fields “prefecture” and “city/gun” are fulfilled, the first one with the 2 numbers of JCC, the second with the full 4 or 6 numbers of JCC. On my view the “prefecture” indication has to be omitted and therefore cancelled.

+ The reference number logged in a Japanese QSO's CNTY item begins with the 2-digit number of its Prefecture. Do not remove the 2-digit Prefecture number from the City or Gun reference number logged in DXKeeper's CNTY item!

+ DXLab follows the ADIF convention of recording both the Primary and Secondary Subdivision information in the Secondary Administrative Subdivision item. For US counties, for example, the Secondary Administrative Subdivision item contains a two-letter State abbreviation, a comma, and then the County name, e.g.

MA,Middlesex

+ DXKeeper's "Sync LoTW QSLs" function correctly populates the Primary Administrative Subdivision and Secondary Administrative Subdivision items in logged QSOs with Japanese stations. No modification of the information obtained from LoTW is required.

+ Here is the ADIF that LoTW returns for my QSO with JA6FIO.

<APP_LoTW_OWNCALL:5>AA6YQ
<STATION_CALLSIGN:5>AA6YQ
<CALL:6>JA6FIO
<BAND:3>20M
<FREQ:8>14.07527
<MODE:3>FT8
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20190705
<TIME_ON:6>105445
<PROP_MODE:2>F2
<QSL_RCVD:1>Y
<QSLRDATE:8>20190708
<DXCC:3>339
<COUNTRY:5>JAPAN
<APP_LoTW_DXCC_ENTITY_STATUS:7>Current
<PFX:3>JA6
<APP_LoTW_2xQSL:1>Y
<IOTA:6>AS-077
<GRIDSQUARE:6>QN13KF
<STATE:2>40 // Fukuoka-ken
<CNTY:4>4001 // Fukuoka-shi
<CQZ:2>25
<ITUZ:2>45
<eor>

+ The QSO's STATE item conveys 40 (Fukuoka Prefecture)

+ The QSO's CNTY item conveys 4001 (Fukuoka City within Fukuoka Prefecture)


Am I correct? I have not found in Wiki answers to my issue.

+ To what "issue" are you referring?


+ The reference documentation for the JCC progress report is here:

<https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#AP%20JCC>

+ The reference documentation for the JCG progress report is here:

<https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#AP%20JCG>

+ If while logging or updating a QSO with a Japanese station, you select the Prefecture (by name) and then select the City/Gun (by name) within that Prefecture, the correct reference numbers will be recorded in the QSO. "Sync LoTW QSLs" will update a logged QSO with information submitted to LoTW by your Japanese QSO partners; any discrepancy between information in the logged QSO and information submitted by your QSO partner will be resolved as specified in the "Handling of LoTW QSL detail inconsistencies" panel on the "QSL Configuration" window's LoTW tab.

73,

Dave, AA6YQ

Re: Ignoring a DXkeeper entry for suspected Pirate station

Joe Subich, W4TV
 

On 2020-01-20 1:17 PM, Curt wrote:

However lately I've worked suspected pirates and when that happens
those entities do not display any longer in the filtered mode.
The suspected pirate callsign will not be displayed but another
callsign (in that entity/band or entity/mode) will be displayed if
it is spotted.

If I've misunderstood the filter then how can I continue to have
Unconfirmed entities displayed without simply deleting the QSO from
my log?
If you are concerned about displaying the "pirate" callsign - for
example if it is the announced callsign of an upcoming DXpedition -
you can either prefix the callsign of the QSO record in DXKeeper
with an "!" or set QSL_RCVD='I' for that QSO (QSO invalid for DXCC).

73,

... Joe, W4TV


On 2020-01-20 1:17 PM, Curt wrote:
I like to keep SpotCollector filtered (Ctrl + Need) to only display ATNO's.  When I hit "Ctrl+Need" the text in blue says "Filter and [entity Unworked or Unconfirmed]".  However lately I've worked suspected pirates and when that happens those entities do not display any longer in the filtered mode.  They of course are not confirmed and I thought they should continue to display because of this?  What am I missing?
If I've misunderstood the filter then how can I continue to have Unconfirmed entities displayed without simply deleting the QSO from my log?
Thanks

Re: DX Keeper question

Ron KU7Y
 

Thanks Dave,

I now have a shortcut setup on my desktop.

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
SKCC #4904
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Sunday, January 19, 2020 10:27 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DX Keeper question

+ AA6YQ comments below

That was what I needed. It looks like I need to have DXV running with
DXKeeper for that to work but I can live with that!

+ That's correct, DXView must be running.

My biggest problem is that I can almost never seem to find what I'm
looking for in the help wiki!

+ Please navigate to

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

+ In the upper right corner, there's a Search box with two buttons
labeled "Titles" and "Text".

+ Please type the word

Club

+ into the Search box, and then click the Titles button. Your browser
will display three article:

ClubLogUpload

IdentifyLogClubMembers

QSLingClubLog

+ The two referencing ClubLog are clearly not of interest, but
IdentifyLogClubMembers is the article you seek.

+ Every page in "Getting Started with DXLab" provides the Search box and
buttons in its upper-right corner. If the Titles search
doesn't find what you need, try the Text search -- it inspects the text
of every article in "Getting Started with DXLab" (and thus
can take awhile).

+ But when you can't find the information you need, don't hesitate to
post message here.

73,

Dave, AA6YQ





--
This email has been checked for viruses by AVG.
https://www.avg.com

Ignoring a DXkeeper entry for suspected Pirate station

Curtis WX4W
 

I like to keep SpotCollector filtered (Ctrl + Need) to only display ATNO's.  When I hit "Ctrl+Need" the text in blue says "Filter and [entity Unworked or Unconfirmed]".  However lately I've worked suspected pirates and when that happens those entities do not display any longer in the filtered mode.  They of course are not confirmed and I thought they should continue to display because of this?  What am I missing?

If I've misunderstood the filter then how can I continue to have Unconfirmed entities displayed without simply deleting the QSO from my log?

Thanks

Re: Dual modes same freq with Commander & 6400 Flex

Dan R
 

Thanks for the reply Dave. "Could" it be a bug in SmartSDR 2.6.1 that is the issue. I can not be definitive but it "may" have started with the last Flex 2.6.1 upgrade? It is not a show stopper so I'll just wait for the next Flex upgrade. I really don't want to back up to the previous Flex software to find out. Time will tell.

73 de Dan KG0AQ

Re: Spot Collector No Sun Spot date appearing

Peter Laws / N5UWY
 

On Sun, Jan 19, 2020 at 7:44 AM wb6bee <wb6bee@...> wrote:

What am I missing. Two Telnet connections, one my own skimmer, one DJ1YFK

*You're* not missing anything - the sun is missing spots! Nothing to
count! :-D




(OK, OK, a few Cycle 25 spots have appeared)


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!

Spot Collector Filtering

Joe WB9SBD
 

I am going to push hard this year to finish up my 5BWAS.

I forgot how to set up Spot Collector to just show spots from states that I still need on whatever band(s).

Anyone?

Joe WB9SBD

Re: Spot Collector No Sun Spot date appearing

David Bunte
 

Don -

Glad you have it cooking now. 

161 de Dave - K9FN

On Mon, Jan 20, 2020 at 8:49 AM wb6bee <wb6bee@...> wrote:
I connected to a third cluster with SH/WWV and it worked.   Tried that command on my own skimmer and it didn't work.   Not sure how you set that up.

I also tried connecting to CQ DX IRC and nothing worked,

Will leave connected to the third cluster for now.

Thanks, Dave

Don
WB6BEE

Re: Spot Collector No Sun Spot date appearing

wb6bee
 

I connected to a third cluster with SH/WWV and it worked.   Tried that command on my own skimmer and it didn't work.   Not sure how you set that up.

I also tried connecting to CQ DX IRC and nothing worked,

Will leave connected to the third cluster for now.

Thanks, Dave

Don
WB6BEE