Date   

Re: Confirming 6m grids for users not on LoTW

Joe Subich, W4TV
 

Can you please elaborate on steps 2 and 3? Where are these located?
On the QSL tab, in "QSL Config" -> "General" -> Add Needed panel.

You had to have set all those values at some point.

I mentioned the FFMA initially since I'm also looking to confirm all
US grids, but I don't want to limit it to *just* FFMA counters.
FFMA *IS* all Grids for the contiguous US. I doubt that "All US
Grids" even makes sense if one includes Alaska/Hawaii.

I have filtered the display with the 3 conditions I mentioned up thread (only 6m QSOs with a date after Jan.1 2015 and not an LoTW
user).
You should need to filter only by "not LotW User" if you select
FFMA in the Awards box of the QSL Config dialog.

But the trick becomes how to filter it further to *only* include grids that have not been otherwise confirmed via LoTW by other stations. This is the part I'm having difficulty with.
If you are looking at grids worldwide, again selecting (filtering
the log) for "not LotW User" and selecting VUCC in the Awards section
of the Add Needed dialog should identify any needed cards (a card
is *not needed* if one already has an LotW confirmation).

This information (describing QSL Config and the "Add Needed" panel)
*IS* in DXKeeper's help files.

73,

... Joe, W4TV


On 2020-06-18 10:23 AM, Peter Dougherty wrote:
On Thu, Jun 18, 2020 at 06:44 AM, Joe Subich, W4TV wrote:

actually be able to accomplish what you want by:

1) Filter the DXKeeper Log display with:
App_DXKeeper_LotW_User <> 'Y'
2) Clear the "Add Needed requests" boxes
3) Clear the Awards boxes in Add Needed
4) Select *only* FFMA
Can you please elaborate on steps 2 and 3? Where are these located? It's been more than a year or more since I last did anything with DXKeeper except import contest ADIFs; I'm a bit rusty on where certain things are located.
I mentioned the FFMA initially since I'm also looking to confirm all US grids, but I don't want to limit it to *just* FFMA counters.
I have filtered the display with the 3 conditions I mentioned up thread (only 6m QSOs with a date after Jan.1 2015 and not an LoTW user). I could add the condition of the entity being K or VE, but I'm fine with worldwide since I can send the non-US cards out via the bureau...most non-US/Canada are Italy, England, Scotland, Spain and Portugal. But the trick becomes how to filter it further to *only* include grids that have not been otherwise confirmed via LoTW by other stations. This is the part I'm having difficulty with.


Re: FT891 User-defined controls

Jim McPhee
 

It appears that the CAT Reference Book is available at:

https://rigreference.com/storage/manuals/yaesu/FT-891%20CAT%20Reference%20Book.pdf--5a6a4c01735456.71645851.pdf

--
Jim McPhee
Placitas, NM
W5ABA


Several DXLab apps "Preparing to Install" - won't open

Dave Corio
 

Probably more a Windows problem, but asking here in case someone has encountered it before. This is likely the failed upgrade to Win 10 v. 2004.

After reverting my Windows 10 2004 to 1909, I have three DXLab apps that will not open. They are
DXKeeper
Spot Collector
WinWabler

When I attempt to start any of those, a small window with the title "Windows Installer" opens showing a message "Preparing to install". The window remains in that state until the "Cancel" button is clicked, at which point the message says "Cancelling", but the window remains hour-glassed until stopped using "End Task". The Window gives no indication of what "Installer" it is running, and just allowing it to continue does not result in change of any kind.

All three apps do the same thing, regardless if they are started using the desktop shortcut or the app in the file folder. At the time this is happening, Task Manager shows the selected app actually running (ie- DXKeeper.exe (32 bit)), although the app never opens. Commander and DXView open as they should. I do not have PropView or PathFinder installed as I do not use them.

Do these apps sound like good candidates for removal and reinstall using the "Move to another PC" guidelines, or has someone run across this before and know of a fix?

Tnx es 73
Dave - K1DJE


Re: myQTH changed on most QSO's

Steve Wedge
 

Thanks, Dave.  I let things take their course and got the all-clear from ARRL after getting new keys for my old callsigns.  Sorry, this is way too much hocus-pocus for my hardware brain but that took care of everything.  I applied for the endorsements and credited everything I had on LoTW.  It cost me $$$ but better now than when really retired.  I do wish that DXK would let you know that it submitted with a prompt or an OK box.  I wasn't sure if it actually changed everything to Verified until I checked it by searching.  

LoTW has certainly reduced the number of cards that I'll need to submit for my 5BDXCC.  I was dreading having to find hundreds of cards and now, I only need 23 cards.  Progress!

73,

'ES


Re: Confirming 6m grids for users not on LoTW

Peter Dougherty
 
Edited

On Thu, Jun 18, 2020 at 06:44 AM, Joe Subich, W4TV wrote:
actually be able to accomplish what you want by:

1) Filter the DXKeeper Log display with:
App_DXKeeper_LotW_User <> 'Y'
2) Clear the "Add Needed requests" boxes
3) Clear the Awards boxes in Add Needed
4) Select *only* FFMA

Can you please elaborate on steps 2 and 3? Where are these located? It's been more than a year or more since I last did anything with DXKeeper except import contest ADIFs; I'm a bit rusty on where certain things are located.

I mentioned the FFMA initially since I'm also looking to confirm all US grids, but I don't want to limit it to just FFMA counters. 

I have filtered the display with the 3 conditions I mentioned upthread (only 6m QSOs with a date after Jan.1 2015 and not an LoTW user). I could add the condition of the entity being K or VE, but I'm fine with worldwide since I can send the non-US cards out via the bureau...most non-US/Canada are Italy, England, Scotland, Spain and Portugal. But the trick becomes how to filter it further to only include grids that have not been otherwise confirmed via LoTW by other stations. This is the part I'm having difficulty with.

If DXKeeper's stats are correct, I should only have a maximum of 50-odd records of worked-not-confirmed grids on 6, and I'd wager about 20% of those are LoTW users who either have not yet uploaded, who've busted my call, or I'm NIL to them.


Re: DXLabs/SDR Console/TS-590SG

Gordon LaPoint
 

I use DXLabs commander and HDSDR (RSP1a)  at the same time  with my TS590sg, Commander talks to the USB port and HSDR talks to the RS 232 port, using the Omni-Rig driver in HDSDR.  This worked better than the Secondary CCAT Port in Commander.  (was more responsive and works with other software without changing anything, like N1MM, WriteLog - etc).  This allowed clicking on the signals in HDSDR and having the radio tune to the signal.

I don't know if the TS-590sg specification states that this is acceptable or not, but it works great!  I don't know if it will work as good with the TS-590s, don't have one, just have the sg version.
Gordon - N1MGO

On 6/16/2020 20:38 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I can run Spectraview okay connected to the 590s comport and DXlabs Commander to the 590s USB port no problems. SDR Console must be a different animal :-).

+ Where in the TS-590S specification does it state that independent CAT instruction streams can be simultaneously sent to its COM and USB ports?

73,

Dave, AA6YQ




Re: Confirming 6m grids for users not on LoTW

Joe Subich, W4TV
 

The FFMA report is a good starting point, but I would respectfully
suggest going further with this concept for needs in general.
The FFMA script was written before DXKeeper provided a built-in
FFMA report. Notice that the script calls the VUCC Report.

Using "add needed" doesn't work properly either since it's selecting
LoTW users as well as non-LoTW users (and multiple non-6m QSOs with
those who I also need to confirm on 6).
If one uses the same SQL as the "Filter" statement in the FFMA script
to filter the DXKeeper log display then does an "Add Needed" for CARDS/LABELS without removing the filter it will certainly add any
QSOs that are not confirmed via LotW.

it's selecting LoTW users as well as non-LoTW users
If you don't want LotW users add "and App_DXKeeper_LotW_User <> 'Y'"
to the SQL used in the FFMA Script.

(and multiple non-6m QSOs with those who I also need to confirm on
6)
Well then don't tell DXKeeper you want the extra QSOs ... *CLEAR* the
"Add Needed requests" boxes in the QSL Config dialog.

I'm current with my FFMA grids so I can't check *but* one should
actually be able to accomplish what you want by:

1) Filter the DXKeeper Log display with:
App_DXKeeper_LotW_User <> 'Y'
2) Clear the "Add Needed requests" boxes
3) Clear the Awards boxes in Add Needed
4) Select *only* FFMA

73,

... Joe, W4TV


On 2020-06-18 9:18 AM, Peter Dougherty wrote:
The FFMA report is a good starting point, but I would respectfully suggest going further with this concept for needs in general.
If someone who uses LoTW goes in to that report it's almost certainly not to see what's confirmed/verified (he can do that via LoTW after all), but rather, to try and figure out what's still outstanding; to determine who will need to be sent a physical card.
Using "add needed" doesn't work properly either since it's selecting LoTW users as well as non-LoTW users (and multiple non-6m QSOs with those who I also need to confirm on 6). I'm willing to give LoTW users a couple of years before I mark those Qs as needed for paper card (or, more likely, not in their log or otherwise unconfirmable).


Re: 6m grid false positives in Spot Collector

Peter Dougherty
 
Edited

Well crap. I guess that did happen. I was getting hits on the call in Spot Collector, but JT Alert-X wasn't tweaking to whatever he was reporting. As I sit here and watch every other region getting these fantastic long-haul openings knowing NJ seems to get the dregs 99 times out of 100, then I see this. Shaping up to be One Of Those Mornings. If he was roving in EM43, though, I have to wonder why JTAlert-X didn't pick up on it, since it's usually VERY reliable in flagging new grids.

I guess I never really worried about domestic grids in the past, figuring they were a dime a dozen. But now that I'm over 500 (still wet behind the ears compared to many here, I'm sure) new grid flags are getting increasingly difficult, especially domestically. And it's funny how, when I look at my 6m grid worked/confirmed map in DX Atlas, everything falls off a cliff west of EM. I only have about 30% of grids worked in DM70-DM99, but about 95-98% of EM00-EM30. It's like the DM/EM divide is a DX wall. And the Canadian border is a much bigger DX wall. Looks like most Canadian hams don't pay much attention to 6m. My EN and FN grids all basically stop at the US-Canada border. Put down the maple syrup and the Timmies double-doubles and get up on six, eh? (I can say this...I'm also VE3THX; born and raised in the land of moose-and-elk).


Re: FT891 User-defined controls

Scott
 

Dave,

I do not unfortunately. 


Re: Confirming 6m grids for users not on LoTW

Peter Dougherty
 

The FFMA report is a good starting point, but I would respectfully suggest going further with this concept for needs in general.

If someone who uses LoTW goes in to that report it's almost certainly not to see what's confirmed/verified (he can do that via LoTW after all), but rather, to try and figure out what's still outstanding; to determine who will need to be sent a physical card.

Using "add needed" doesn't work properly either since it's selecting LoTW users as well as non-LoTW users (and multiple non-6m QSOs with those who I also need to confirm on 6). I'm willing to give LoTW users a couple of years before I mark those Qs as needed for paper card (or, more likely, not in their log or otherwise unconfirmable).


Re: 6m grid false positives in Spot Collector

Chad Kurszewski
 

That's correct.  AC0RA was in EM43 on Tuesday/Wesnesday this week.  I hope you didn't think it was false and got one of your two remaining EM grids.

Chad WE9V


Re: 6m grid false positives in Spot Collector

Al Groff
 



On 6/17/2020 9:13 PM, Peter Dougherty wrote:

[Edited Message Follows]

I'm having a problem with false FT8 positives firing off alerts.
 
I grid chase (and DXCC chase) on 6m. With my cluster connections up and WSJT and JTAlert-x connected, I get frequent hits for stations where the grid information is incorrect. I'm not talking about "gibberish spots" here, but legitimate spots that trigger incorrectly.
 
The source, according to Spot Collector, is my own copy of WSJT-x. There have been numerous examples of a spot arriving via WSJT-X with one (ostensibly) correct grid, but it shows up in the DX Grid column in S.C. with a different grid, causing alerts to sound. I could understand if this was a station I'd worked previously and an old grid was being auto-populated, but this happens even with stations I've never worked before.
 
One such station CQs on FT8 from grid EM31, a grid I have previously worked, confirmed via LoTW, and verified for VUCC credit. The station shows up correctly in WSJT and JTAlert-X, but in Spot Collector it's showing this particular station as EM43, one of only two EM grids I've never worked. This isn't the only circumstance, but since the op in question (AC0RA) is an avid 6m operator with a good signal to me, alerts on his call are frequent.  But with many others the same thing is happening. JTAlert-x/WSJT has the grid correct according to the CQ sent by the originator, but S.C. gets it wrong.

AC0RA is an AVID Rover and has recently been in EM43...

AL, K0VM
 
Now, if this isn't already the case, I would respectfully suggest than any incoming spot for a station previously worked that has grid information populated by the FT8 software, that information needs to override any previous grid info from past QSOs in DXKeeper. Obviously this would be especially needed for Rovers. I have a suspicion that this is already the case, but I wanted to mention it here just in case. But with that said, I'd really like to understand why I'm getting so many false positives.
 
And speaking of false positives, when the inevitable gibberish print from WSJT causes a "need" alert is JTAlert (and subsequently in Spot Collector), is there any way to maybe put in a lookup or truth table, etc, within S.C. so I won't get woken up by a badly interpreted FT8 "spot"?
 
Or some way to say "only alert if X number of "new grid" or "new zone" (etc) spots are received within Y minutes? I'd typically want to set that at 3 within 1 or 2 minutes personally.


Re: Confirming 6m grids for users not on LoTW

Dave AA6YQ
 

+ AA6YQ comments below

On Wed, Jun 17, 2020 at 11:01 PM, Dave AA6YQ wrote:

Good to see the Fishy Script--took me a moment to figure out what it did. But can I use this in conjunction with and SQL filter to display only QSOs with stations who will definitely not be able to confirm via LoTW? Display the grids and populate the log page so I can print off labels and start sending out cards?

+ Correction: it should not be necessary to construct a script. DXKeeper's "Add Needed" function can be configured to populate the QSL Queue with QSOs "needed" for FFMA. However, when I tried this, the QSL Queue was populated with QSOs with gridsquares confirmed via LoTW, which is not correct. I will investigate.

+ Note that DXKeeper can directly generate an FFMA progress report: click the FFMA button in the "Other Progress Reports" panel on the Main window's "Check Progress" tab.

      73,

             Dave, AA6YQ

 


Re: Confirming 6m grids for users not on LoTW

Dave AA6YQ
 

+ AA6YQ comments below

On Wed, Jun 17, 2020 at 07:48 PM, Dave AA6YQ wrote:


((BAND='6M') AND (App_DXKeeper_LotW_Member<>'Y') AND (QSO_BEGIN > #2015-01-01#))

OK, that syntax worked with 353 results. Now to narrow it down to do what I need.

Good to see the Fishy Script--took me a moment to figure out what it did. But can I use this in conjunction with and SQL filter to display only QSOs with stations who will definitely not be able to confirm via LoTW? Display the grids and populate the log page so I can print off labels and start sending out cards?

+ Yes. Give it a try.

73,

Dave, AA6YQ comments below


Re: 6m grid false positives in Spot Collector

Dave AA6YQ
 

+ AA6YQ comments below

If you ever do find yourself with some free time, the feature to alert only if X spots are received within Y time would be most welcome. I leave everything running overnight with my antenna beamed towards Europe, so any early-morning trans-Atlantic activity to a new zone or entity will trip the alarm bells, but if only one spot, legit or bogus, arrives there's no need to crawl bleary-eyed into the shack on 3 hours' sleep. If I get 3 in 2 minutes, or even 2 in 30 seconds, then it's likely the start of a legit opening and it's time to caffeinate and get going. I'd say a similar condition for DXpeditions or needed entities would weed out fake spots.

+ Why not put a tablet next to your bed and use SpotCollector's web interface so you can directly determine whether it's worth getting up? See

<https://www.dxlabsuite.com/spotcollector/Help/WebBrowser.htm>

+ and

<http://www.dxlabsuite.com/spotcollector/WebAccess.jpg>

73,

Dave, AA6YQ


Re: Confirming 6m grids for users not on LoTW

Peter Dougherty
 

On Wed, Jun 17, 2020 at 07:48 PM, Dave AA6YQ wrote:
((BAND='6M') AND (App_DXKeeper_LotW_Member<>'Y') AND (QSO_BEGIN > #2015-01-01#))
OK, that syntax worked with 353 results. Now to narrow it down to do what I need. 

Good to see the Fishy Script--took me a moment to figure out what it did. But can I use this in conjunction with and SQL filter to display only QSOs with stations who will definitely not be able to confirm via LoTW? Display the grids and populate the log page so I can print off labels and start sending out cards?


Re: 6m grid false positives in Spot Collector

Peter Dougherty
 

I meant Spot Collector, of course. I had been chatting about my days with DX Base with a friend earlier tonight and I typed that unintentionally. I have corrected it in my original question, above.

I will test this out tomorrow (or whenever the band opens enough to see the usual flood of spots).

If you ever do find yourself with some free time, the feature to alert only if X spots are received within Y time would be most welcome. I leave everything running overnight with my antenna beamed towards Europe, so any early-morning trans-Atlantic activity to a new zone or entity will trip the alarm bells, but if only one spot, legit or bogus, arrives there's no need to crawl bleary-eyed into the shack on 3 hours' sleep. If I get 3 in 2 minutes, or even 2 in 30 seconds, then it's likely the start of a legit opening and it's time to caffeinate and get going. I'd say a similar condition for DXpeditions or needed entities would weed out fake spots. 


Re: FT891 User-defined controls

Dave AA6YQ
 

+ AA6YQ comments below

I just picked up a Yaesu FT-891 for POTA/SOTA use. It easily configured with the DXLabs Suite. I am curious if anyone has any User-defined Controls or sliders they would be willing to share. I looked in the Files section and did not see any for the 891.

+ Since Yaesu switched to a more Kenwood-like CAT instruction set, there's more commonality among the radios. The FT-2000 Audio Gain Slider, for example, should work with your FT-891. Some of the FTDX-3000 controls should also work with some or no modification.

+ Do you have a copy of the FT-891 CAT Operation Reference Book?

73,

Dave, AA6YQ


Re: Spot Collector SOTA problem

Kent N6WT
 

I was an issue with the spot source. It is fixed now!

Thanks
73
Kent
N6WT


On Wed, Jun 17, 2020, 12:06 Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I use the sota cluster at cluster.sota.org.uk  port 7300 with Spot Collector. Normally this works great but today, after 1603Z, I get no updates although SotaWatch3 on the web is working with no issues. Is it reasonable to assume a problem at the cluster end in situations like this?

+ On the "Spot Sources" tab of SpotCollector's Configuration, uncheck that cluster's Hide and the Ann/Talk boxes to display a window that shows SpotCollector's interaction with the cluster. Click this window's Disconnect button, and then click its Connect button; does an error message appear?

+ If you see no interaction with the cluster, then either the cluster is offline or unreachable, or something is preventing SpotCollector from interacting with it (anti-malware being a likely candidate).

         73,

              Dvae, AA6YQ





FT891 User-defined controls

Scott
 

I just picked up a Yaesu FT-891 for POTA/SOTA use. It easily configured with the DXLabs Suite. I am curious if anyone has any User-defined Controls or sliders they would be willing to share. I looked in the Files section and did not see any for the 891.

Thanks in advance.
Scott - KN3A