I have been using DXLab for approximately 8 months. As recommended by Dave, I have been turning one application on at a time as I learn how they all work. I have now logged in over 500 QSOs in

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.

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

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>. The FT-891 command to switch the Meter to SWR is simply MS3;, to ALC is MS1; to

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

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

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

On the QSL tab, in "QSL Config" -> "General" -> Add Needed panel. You had to have set all those values at some point. FFMA *IS* all Grids for the contiguous US. I doubt that "All US Grids" even

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,

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

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

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

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

The FFMA script was written before DXKeeper provided a built-in FFMA report. Notice that the script calls the VUCC Report. If one uses the same SQL as the "Filter" statement in the FFMA script to

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

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

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

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

+ AA6YQ comments below + 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.