Sorry to be a lid but I've looked and looked in the docs and can't find instructions for setting up the apps so that needed grids get the nice SpotCollector highlight font the way needed countries do. I DON'T use jtalert only the DXLab apps. Help anyone? 

TNX de N6MZ

One update ... The FT-891 command set seems to be [nearly] identical to
that of the FT-950. You might want to experiment with some of the User
Defined Commands and Sliders for the FT-950 (from the files area).

It is often easier to learn the process by starting with some examples
that others have already debugged.

73,

... Joe, W4TV

In looking in the instructions, it appears that the command string
starts with FA. So I put in FAMS3;MS;MS3;

No, FA<P1>; is the command to 1) tell the rig to report the frequency
of VFO A or 2) Set VFO A to a frequency <P1>.

For example I would like to set up a User-defined control for
switching the meter to the SWR.

The FT-891 command to switch the Meter to SWR is simply MS3;, to
ALC is MS1; to Power Out is MS2;

The Commander syntax for sending an ASCII command requires placing
and apostrophe (') before the command to indicate ASCII instead of
hexadecimal.

You might get some ideas by looking at the FT-450 command examples
in the files area -> Command Sequences and Sliders -> Yaesu -> FT-450
"FT450 Meter Control.txt" selects ALC, Power Out, and SWR sequentially.

Note you will need to check the examples against the FT-891 documentation as the command sets are not identical (particularly in
VFO control).


73,

... Joe, W4TV


On 2020-06-18 1:33 PM, Scott wrote:

Thank you Joe and others for the help. I am very green when it comes to these types of things. For example I would like to set up a User-defined control for switching the meter to the SWR. In looking in the instructions, it appears that the command string starts with FA. So I put in FAMS3;MS;MS3;
The example at the beginning of the PDF instructions shows how to switch to a certain frequency using the FA. Can you enlighten me what I've done wrong? I ask for you to go easy on me with this because I'm just not the programming type.

Thank you Joe and others for the help. I am very green when it comes to these types of things. For example I would like to set up a User-defined control for switching the meter to the SWR. In looking in the instructions, it appears that the command string starts with FA. So I put in FAMS3;MS;MS3;

The example at the beginning of the PDF instructions shows how to switch to a certain frequency using the FA. Can you enlighten me what I've done wrong? I ask for you to go easy on me with this because I'm just not the programming type.

On Wed, Jun 17, 2020 at 7:13 PM Peter Dougherty <lists@w2irt.net> wrote:

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.

FWIW, there is an issue with the current version of SpotCollector when
the grid for a spot [database entry] is derived from the DXCC database
entry matching the station's callsign. In such cases, the spot
database entry is not supposed to be marked as needed, even if you do
need that grid, since the source of the grid data is not sufficiently
precise. There should be a fix in the next version of SpotCollector to
handle this properly. For me, this issue was most noticeable with VE
stations, where the grid would be one in the middle of the VE
province, most of which are in the middle of nowhere, hence needed.

Sorry that you missed out on EM43!

73,

~iain / N6ML

Also available directly from Yaesu:
<https://www.yaesu.com/downloadFile.cfm?FileID=15277&;FileCatID=158&FileName=FT%2D891%5FCAT%5FOM%5FENG%5F1909%2DC.pdf&FileContentType=application%2Fpdf>


CAT Reference Manuals for Yaesu's current products are typically
available at www.yaesu.com -> Products (HF Transceivers/Amplifiers).
Select your transceiver then the "Files" tab ...

73,

... Joe, 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.

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

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

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

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.

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

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

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

Dave,

I do not unfortunately. 

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

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

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

+ 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