开云体育

+ AA6YQ comments below

Very appreciate to help me to connect Commander to Acom 2000S remote antenna switch via serial port.
First question: it’s possible?

+ No. As described in

<>

+ Commander supports two standard serial port protocols for transceiver selection and auxiliary device control: microHam, and OTRSP. The command set described on page 16 of

<>

+ is not compatible with either of the protocols that Commander supports.

+ Given the poor quality of the Acom 2000S remote antenna documentation, I will not attempt to extend Commander to support it without having physical access to one for rapid resolution of documentation ambiguities.

73,

Dave, AA6YQ

+ AA6YQ comments below

I am using Commander / DXKeeper / WSJT-X / JT Alert for FT-8 and all seems to work well, including automatic logging to LoTW and DXKeeper. However in DXK I notice that the name and town of my QSO partner is not shown. When I press the DXK "CBA" button, I get the following error message:

"This QSO has not been unlocked for modification. Perform a call book look up Yes or No?"
When I press yes, it does put in the name and town.

+ You have the "Require Edit to modify logged QSO" box check in the "Main Log QSOs options" panel on the General tab of DXKeeper's Configuration window, which protects against inadvertent modifications to logged QSOs. To avoid message reported above, click Edit button before clicking the CBA button; the Edit button is located to the left of the CBA button just above the Log Page Display on the "Log QSOs" tab of DXKeeper's Main window.

In DXK, I am using HomeQTH.com, having posted my user name and password in DXK config.

+ JTAlert is responsible for the content of the QSOs it logs to DXKeeper. If you want such QSOs to include the results of a callbook lookup, appropriately configure the "Online XML Callbooks" sub-section in the "Web Services" section on the left panel of the JTAlertX Settings window. This is step 2.d in the JTAlert section of

<>

73,

Dave, AA6YQ

+ AA6YQ comments below

Hello all. I use WSJT-X 2.1.2 and JTAlert 2.15.10 for FT8. I have the box checked in JTAlert, Logging to fill the SFI, A, and K boxes in DXKeeper 15.4.3. When I first started this a couple years ago, it would fill in automatically. With one of the upgrades of JTAlert, it quit doing so. I have the latest updates for WSJT-X, JTAlert, the current Netframe edition 4.7.2, and am running Win7 Professional 32 bit, all updates. Does this feature not work anymore, or what am I missing?

+ Unless someone more familiar with JTAlert than me responds here, I suggest that you post your question on the JTAlert Support group:

<>

73,

Dave, AA6YQ

+ AA6QY comments below

Anyway to use the "standard" Fkeys in Winwarbler, F1, CQ, F4 my call, etc, to be consistent with other logger programs?

+ No. In all modes, F2 is used to start transmission, and F4 is used to terminate transmission after all characters have been transmitted. When operating PSK, F1 is used to set the transmit frequency to the receive frequency associated with the currently-selected display pane, and F3 initiates a CW ID.

73,

Dave, AA6YQ

+ AA6YQ comments below

I love the possibility to keep an up-to-date database for exceptions to the "standard" callsign rules in DXView but recently I have found a limitation that I find a bit frustrating.

If I, for instance, enter VP8PJ in the callsign box and hit ENTER, the grid box ends up empty.
The distance (13931km) shows, however. Since the grid and geographical coordinates are undefined, clicking the Sun button yields an empty array.

When I open the Config's Override List panel and right-click the VP8PJ entry and chose "Populate override content from entity" I get the message "all override components are already populated".
No grid.

Is there a reason to not populate the grid with the entity's default locator?

+ Yes: DXLab treats the grid square specified in an override as accurate enough to count for awards that involve pursuing grid squares, like VUCC. As Joe W4TV explained, the grid square produced by a DXCC Database lookup does not meet that accuracy criterion.

If I simply select VP8-O from the drop down menu, the grid box is populated.

+ I assume that you're referring to the DXCC prefix selector on DXView's Main window. Using the grid square produced by a DXCC Database lookup is accurate enough for the purpose of displaying a great circle path and computing a beam heading.

73,

Dave, AA6YQ

I am using Commander / DXKeeper / WSJT-X / JT Alert for FT-8 and all seems to work well, including automatic logging to LoTW and DXKeeper. However in DXK I notice that the name and town of my QSO partner is not shown. When I press the DXK "CBA" button, I get the following error message:

"This QSO has not been unlocked for modification. Perform a call book look up Yes or No?"
When I press yes, it does put in the name and town.

In DXK, I am using HomeQTH.com, having posted my user name and password in DXK config.

What am I doing wrong?

Thanks in advance for any help and 73,
Carter?? K8VT

SpotCollector's add on SpotSpy provides support for 60M

For more information about SpotSpy visit
Full release is available at

73
Volker, DL9HO

Is there a reason to not populate the grid with the entity's default
locator?

There is no "default locator" for any entity other than HC1, 1A, 3A
which are smaller than a four character grid.

If I simply select VP8-O from the drop down menu, the grid box is
populated.

The grid that is populated when selecting any entity is the one that
either Dave or I selected as a reference (typically geographical center
with some modifications to "center of largest city") when creating or
updating the DXCC database.

73,

... Joe, W4TV


On 2020-02-26 11:35 AM, Bj?rn Ekelund, SM7IUN wrote:

I love the possibility to keep an up-to-date database for exceptions to the
"standard" callsign rules
in DXView but recently I have found a limitation that I find a bit
frustrating.
If I, for instance, enter VP8PJ in the callsign box and hit ENTER, the grid
box ends up empty.
The distance (13931km) shows, however. Since the grid and geographical
coordinates are
undefined, clicking the Sun button yields an empty array.
When I open the Config's Override List panel and right-click the VP8PJ
entry and chose
"Populate override content from entity" I get the message "all override
components are already populated".
No grid.
Is there a reason to not populate the grid with the entity's default
locator?
If I simply select VP8-O from the drop down menu, the grid box is populated.
Bj?rn SM7IUN

Hello all.? I use WSJT-X 2.1.2 and JTAlert 2.15.10 for FT8.? I have the box checked in JTAlert, Logging?to fill the SFI, A, and K boxes in DXKeeper 15.4.3.? When I first started this a couple years ago, it would fill in automatically.? With one of the upgrades of JTAlert, it quit doing so.? I have the latest updates for WSJT-X, JTAlert, the current Netframe edition 4.7.2, and am running Win7 Professional 32 bit, all updates.? Does this feature not work anymore, or what am I missing?

Anyway to use the "standard" Fkeys in Winwarbler, F1, CQ, F4 my call, etc, to be consistent with other logger programs?

+ AA6YQ comments below

I sometimes see this after a spot source callsign. Couldn't find it in the documentation.

+ It's mentioned in the description of the "Discard spots from spotting stations callsigns ending in - #" option in

<>

+ When generating spots, Skimmers like "CW Skimmer" append -# to the callsign of the spotting station.

+ This above-cited option gives you the ability to have SpotCollector ignore such spots.

73,

Dave. AA6YQ

Thank you, Dave. It all went well and everything seems to be in place and correct.

-- Jay W8ES

I sometimes see this after a spot source callsign. Couldn't find it? in the documentation.
Cheers
Tony G4CJC

Thanks a million Dave and also thanks to Mike, ND9G.? As you probably recall, Dave, I did try DX Labs years ago.? Actually, I tried it several times.? My biggest mistake was trying to learn everything too fast which you probably are aware of hence your bit of advice.? This time I'm going nice and slow.? I'm still using AC Log and importing new QSOs to DX Labs but at the same time I'm slowly familiarizing myself with your program.? I originally just started with DX Keeper, but I now have the whole suite downloaded and in use.

I hope you've been well, Dave.? I haven't been in the eHam DX forum for a couple years now.? I'll probably rejoin the DX forum when solar conditions improve.

73,

Chris? NU1O

+ AA6YQ comments below

Is there an EASY way to see 60 stats without going through all of the filtering steps?

How can I add 60M to the "DXView Info" matrix? That would be MOST helpful, too!

How can I add 60M to "Check Progress" > DXCC progress button OR make a separate "Progress" button for 60M like there is for the other reports (WAC reports, WAS, Maidenhead reports.....etc)?????

Thanks in advance for any suggestions.

+ The ARRL goes out of its way to avoid promoting DXing on 60m. None of its HF awards - DXCC, WAC, or WAS count QSOs made on 60m.

+ As Joe W4TV has pointed out, you can create a script to automate the 4-step process now required to see a DXCC-style progress report on 60m. I've placed such a script in this Group's Files area:

/g/DXLab/files/DXKeeper%20Scripts//60m%20DXCC.txt

+ Download it into DXKeeper's Scripts folder, and you'll be able to invoke it by clicking the Scripts button that will appear in the Filter panel at the bottom of DXKeeper's Main window's "Log QSOs" tab after you click the ~ button.

+ Even if I didn't share the ARRL's view that 60m is too narrow for DXing, extending DXKeeper's "DXCC Progress Report" function to include a column for 60m would cause endless trouble, because QSOs made in this band don't count for DXCC awards. An op whose only QSO with 9N is on 60m, for example, would be confused by his or her total entity count being one less than expected. Extending DXLab's realtime DXCC award tracking to support 60m would generate even more confusion. The nooks and crannies in the current DXCC award program rules are challenging enough without reporting statistics for a band that doesn't count. If the ARRL extends the DXCC award program to support 60m, I'll extend DXLab in a heartbeat.

+ Note that DXLab applications do provide realtime award tracking and progress reporting for the CQ DX Marathon and CW WPX awards, in which count 60m QSOs count.

73,

Dave, AA6YQ

+ AA6YQ comments below

I want to transfer DXLab Suite to another laptop. I put together all the programs in a work space as directed in the on-line help files and installed DXLab on the second laptop. Then I remembered I use Google Drive to hold my log backups and databases for my primary and a club call sign. The file route is C:\Users\(name)\Google Drive\LogBackups\DXKeeper\. Unfortunately, the (name) part is different on the two laptops.

If I complete the work space transfer, will I simply be able to edit the db file routing on the second laptop to make everything right?

+Yes, after restoring your Workspace on the second laptop, you can start your applications on the second laptop and use them to modify settings there. When you start DXKeeper, it will try - unsuccessfully, I assume --to open the log file using the pathname specified in your first laptop's instance of DXKeeper. On your second laptop, open the Log tab of DXKeeper's Configuration window, and use the "Log File" panel to select your log file using the appropriate pathname.

+ Note: you cannot have the same log file simultaneously open in two instances of DXKeeper. So Terminate DXKeeper on your first laptop before starting it on your second laptop, and vice versa.

I seem to remember reading something about problems caused with different user names a long time ago, but I can’t find an answer to this via searches.

+ I don't recall any problems with different user names. When moving a Workspace from one computer to another, you'll have to manually change settings on the second computer if folders and files are in different locations -- like your log file.

73,

Dave, AA6YQ