On 2021-11-06 11:13 AM, g4wjs wrote:

DT GAIN on the FT-991A (note not he FT-991) is on the front panel display menu and set the modulation level in DATA modes - see Page 24
of the owners manual "About the Display".

Unfortunately, there is no access to the front panel display via the
menu structure and thus no access to the front panel display via the
CAT "EX" command.

73,

... Joe, W4TV


On 2021-11-06 11:13 AM, g4wjs wrote:

On 06/11/2021 15:04, Dave AA6YQ wrote:

+ AA6YQ comments below


call me blind, but I didn't find the command for DT GAIN in the CAT Operation Reference Manual.
Someone in the group using it and can tell me the command for programming in the Commander?

+ “DT Gain” in mentioned on page 118 of the user manual, but without any description of what it does. Unless someone here responds, I suggest that you contact Yaesu technical support.

73,

Dave, AA6YQ

Hi Dave and Ralf,
DT GAIN on the FT-991A (note not he FT-991) is on the front panel display menu and set the modulation level in DATA modes - see Page 24 of the owners manual "About the Display".

The FT-991/991A apparently lacks the capability to set DATA GAIN via
CAT command. There is no DT GAIN or DATA TX GAIN in the menu (unlike
078 FM PKT TX GAIN and 049 AM DATA GAIN).

73,

... Joe, W4TV

@ more AA6YQ comments below

call me blind, but I didn't find the command for DT GAIN in the CAT Operation Reference Manual.
Someone in the group using it and can tell me the command for programming in the Commander?

+ “DT Gain” in mentioned on page 118 of the user manual, but without any description of what it does. Unless someone here responds, I suggest that you contact Yaesu technical support.

DT GAIN on the FT-991A (note not he FT-991) is on the front panel display menu and set the modulation level in DATA modes - see Page 24 of the owners manual "About the Display".

@ Thanks, Bill. It's referred to as "DT-G" in the FT-991 operating manual. I don't see anything in the FT991A CAT documentation that would control it, but that may just be a documentation deficiency.

73,

Dave, AA6YQ

+ AA6YQ comments below

call me blind, but I didn't find the command for DT GAIN in the CAT Operation Reference Manual.
Someone in the group using it and can tell me the command for programming in the Commander?

+ “DT Gain” in mentioned on page 118 of the user manual, but without any description of what it does. Unless someone here responds, I suggest that you contact Yaesu technical support.

 

        73,

 

                   Dave, AA6YQ

Hi Dave and Ralf,

DT GAIN on the FT-991A (note not he FT-991) is on the front panel display menu and set the modulation level in DATA modes - see Page 24 of the owners manual "About the Display".

--
73

Bill

G4WJS.

Hello together,

call me blind, but I didn't find the command for DT GAIN in the CAT Operation Reference Manual.
Someone in the group using it and can tell me the command for programming in the Commander?

--
73 Ralf
--
DO5RBB
DL0103SWL
https://www.youtube.com/c/RalfBender/

+ AA6YQ comments below

I'll give this a shot, thanks. You see where I'm going.. it'd be nice to be able to generate a list of needed QSOs without LOTW confirms that the other station has uploaded to LOTW subsequently, so you can go chase down OQRS or whatever other issues there might be.

+ Yes, I understood the enhancement request from your first post in this thread. I'm in the middle of adding an RDA database that knows the Oblast and District of tens of thousands of Russian stations, and extending SpotCollector, DXKeeper, DXView, and WinWarbler to exploit it. I'd like to complete that before addressing additional enhancements.

      73,

               Dave, AA6YQ

 

On Tue, Oct 26, 2021 at 09:23 PM, Dave AA6YQ wrote:

+ You can identify needed DXCC prefixes by generating a DXCC progress report, but there is no automated way of producing a list in the above format.

I'll give this a shot, thanks. You see where I'm going.. it'd be nice to be able to generate a list of needed QSOs without LOTW confirms that the other station has uploaded to LOTW subsequently, so you can go chase down OQRS or whatever other issues there might be. I know you love my feature requests, so I'll throw this one in the bucket too. :)

73 de KM8V Jon

+ AA6YQ comments below

37 46' 15" N 78 2' 30" W

ve3gqj says 895 mi bearing 342
va3ike same
ve3zv same

i know they are not all same distance and bearing .

+ Running by itself, DXView does not have the ability to reference an online callbook to obtain the location of a specific callsign. It determines from the DXCC database that all three of the callsigns above are in Ontario, for which it uses the central location of

50' N, 84' W

+ If you run Pathfinder and configure it to access the QRZ online callbook, then on DXView's Main window you will be able to enter a callsign, click the QRZ button, and obtain the callsign's location from QRZ. A free QRZ subscription is all that is required.

+ If you run DXKeeper and configure it to access the QRZ, QRZ XML, RAC, HamCall, or HamQTH callbooks, then when you type a callsign into the Capture window and strike the Enter key, DXKeeper will perform a callbook lookup and convey the location information to DXView.

73,

Dave, AA6YQ

Laurie's comments about the Windows Metro Style brought me shivers.  I was able to skip over that release, but had enough experience with it to do all I could to keep it off my PCs.

Social media, safe space junk just doesn't work for me.  I'm just too old and old-fashioned.

My wife and I have 3 old/mature laptops that I've updated over the years with SSDs, maximum memory, new mother-board, fan units, etc., etc..  None of these rock-solid, boat-anchors meet specifications for W-11.  And we're retired with fixed $$ and those fixed $$ don't include new computers for a new O/S.

The laptop I use for my radio work gets a workout when the cluster(s) are active on special events, but I just deal with it and adjust the cluster filters to help throttle the flow to help keep the CPU from running its legs off.  :-) 
--

73 - Nolan K.  -  ki5io

37 46' 15" N   78 2' 30" W  

ve3gqj says 895 mi  bearing 342
va3ike  same
ve3zv same

i know they are not all same distance and bearing . 

+ AA6YQ comments below

when i look up a call from ve land the distance always shows 895 miles and strange headings mostly 342 degrees when qrz says mush different lie 480 miles and 9 degrees.

+ In the QTH panel on the General tab of DXView’s Configuration window, what latitude and longitude have you specified?

+ What are several examples of Canadian callsigns that produce the results you cite above?

73,

Dave, AA6YQ

when i look up a call from ve land the distance always shows 895 miles and strange headings mostly 342 degrees when qrz says mush different lie 480 miles and 9 degrees.

im not sure where to look for the error, maybe a recompute? 

+ AA6YQ comments below

Everything has been working just fine and I have made hundreds of contacts on FT-8 until several hours ago. I am using WSJT-X with JTAlert and Commander. The CAT indicator light on my FTDX5000 went out when I changed bands from 20M to 15M and Commander is not communicating with the FT5K. I was not able to terminate Commander with Launcher or clicking on the X at the top right of the Commander window. I shut down the rest of the DXLab modules with the Launcher and rebooted the computer.

I restarted DXLab with Launcher and when Commander re-started I got a window that stated:

TCP/IP Port 52002 is already in use. Chose another port and restart the network server.

Not being that computer literate I said OK and went into the Commander config and noticed that the radio model was blank. When changed to FTDX5000 a window opened that said

Invalid port number (8002) the port = primary CAT port, port number = 4 Settings = 38400, N,8,2

I am using a serial to USB converter between the computer and the FT5000. I thought that it was possible that the converter failed.

After shutting down again and turning the FTDX5000 off and letting the equipment cool down I restarted everything and all was well. Everything appeared “fixed”. I chalked it up to some glitch in one of the software modules. After running for several days the same problem has cropped up again.
I have not been able to get things running again as before.

As I said initially I made no changes and this issue just popped up.
Any help resolving the issue appreciated.

+ The “Invalid port number (8002)” message comes from Windows. It means that the COM port number that Commander is configured to use to interact with your transceiver does not exist. Windows has the occasional habit of scrambling COM port assignments when it installs updates. That’s why it’s best to configure Windows to not install an update without your direct approval, as described in the “Configuring Windows and Anti-malware Updates” section of

https://www.dxlabsuite.com/dxlabwiki/WindowsTricks

+ This won't stop Windows from scrambling your COM ports if it's in the mood to do so, but you'll know exactly what happened.

+ You must determine which COM port is now associated with your USB converter:

1. Open the Windows Device Manager, and click the small triangle to the left of "Ports (COM LPT).

2. Jot down all of the COM ports listed.

3. Disconnect your USB converter from your computer.

4. Wait for one of the listed COM ports to dissappear - the one that Windows had assigned to your USB converter.

5. Reconnect your USB converter from your computer.

6. A new COM port will appear in the Device Manager's list; compare what you now see to the list of Com ports you made in step 2 above. Configure Commander to use the new (with respect to the step 2 list) COM port to interact with your transceiver.

+ The fact that Commander's "Radio Model" selector was lost may indicate that an event more serious than the usual "musical COM ports" has occurred. Terminate Commander, and direct the Launcher to restore Commander's settings from the Workspace you created when everything was working correctly; step-by-step instructions are in the " Loading the Windows Registry with One Selected DXLab Application's Settings from a Workspace" section of this article:

https://www.dxlabsuite.com/dxlabwiki/CreateUpdateWorkspace

+ You should also examine Windows' Event Logs to see if hardware or software errors have recently occurred:

https://www.dxlabsuite.com/dxlabwiki/CheckingWindowsEventLogs

73,

Dave, AA6YQ

Everything has been working just fine and I have made hundreds of contacts on FT-8 until several hours ago. I am using WSJT-X with JTAlert and Commander. The CAT indicator light on my FTDX5000 went out when I changed bands from 20M to 15M and Commander is not communicating with the FT5K. I was not able to terminate Commander with Launcher or clicking on the X at the top right of the Commander window. I shut down the rest of the DXLab modules with the Launcher and rebooted the computer.

I restarted DXLab with Launcher and when Commander re-started I got a window that stated:

        TCP/IP Port 52002 is already in use. Chose another port and restart the network server.

Not being that computer literate I said OK and went into the Commander config and noticed that the radio model was blank. When changed to FTDX5000 a window opened that said

        Invalid port number (8002) the port = primary CAT port, port number = 4 Settings = 38400, N,8,2

I am using a serial to USB converter between the computer and the FT5000. I thought that it was possible that the converter failed.

After shutting down again and turning the FTDX5000 off and letting the equipment cool down I restarted everything and all was well. Everything appeared “fixed”. I chalked it up to some glitch in one of the software modules. After running for several days the same problem has cropped up again.

I have not been able to get things running again as before.

As I said initially I made no changes and this issue just popped up.

Any help resolving the issue appreciated.

73...Bill...W1GY

@ more AA6YQ comments below

+ The CW DXCC award requires obtaining award credit for all 340 entities in CW. It does not require obtaining award credit for all 340 entities in CW on every band.

Yeah, I just realized this after digging in a bit more. So then the way to have a station show up for all bands/modes is by adding it to the Leaderboard list in the special callsigns.

+ Adding a callsign to SpotCollector's "Special Callsign" list with a Leaderboard tag will prompt you to work that callsign in all band-mode combinations. See

https://www.dxlabsuite.com/dxlabwiki/LeaderboardAwardTracking

+ Alternatively, you can use SpotSpy, a SpotCollector add-in that supports pursuit of the "Quixote Quest": confirming every DXCC entity on every combination of bands and modes. See

http://www.dl9ho.de/SpotSpy/SpotSpy.htm

73,

Dave, AA6YQ

Reposting since y'all seem to be paying attention to the next major
version of Windows now. Note Dave's last line especially.

I will also note that Windows 10 "Home" and Windows 10 "Pro" will not
be "retired" (EOL for the rest of us) until Oct 14, 2025, which I make
as 1,439 days from now.

https://docs.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro

---------- Forwarded message ---------
From: Dave AA6YQ <aa6yq@ambersoft.com>
Date: Thu, Jul 1, 2021 at 3:27 PM
Subject: Re: [DXLab] Windows 11
To: <DXLab@groups.io>


+ AA6YQ comments below

I assume it is too soon to access the impact of Windows 11 on current
sset-ups but wonder if you have any initial thoughts on what we will
gain form 11 and what we may lose?

+ Here's how Microsoft describes Windows 11:

"Windows 11 provides a calm and creative space where you can pursue
your passions through a fresh experience. From a rejuvenated Start
menu to new ways to connect to your favorite people, news, games, and
content—Windows 11 is the place to think, express, and create in a
natural way."

"Maximize your productivity: Access all the apps you need and
multi-task with ease with tools like Snap layouts, Desktops, and a new
more-intuitive redocking experience."

"New ways to connect: Connect instantly to the people you care about
right from your desktop with Microsoft Teams. Call or chat for free—no
matter what device they’re on."

"Your content, curated by you: With Microsoft Edge and a multitude of
Widgets you can choose from, you can quickly stay up to date with the
news, information, and entertainment that matters most to you. Easily
find the apps you need and the shows you love to watch in the new
Microsoft Store."

https://www.microsoft.com/en-us/windows/windows-11

+ Translation: this is a marketing driven release with a few usability
improvements aimed at bolstering Microsoft Teams (over Zoom),
Microsoft Edge (over Google Chrome), and content from the Microsoft
Store (over everyone else).

+ The only substantive technical improvement I've seen so far is the
added security gained by requiring Trusted Platform Module (TPM) 2.0,
but unless this will put an end to ransom-ware or phone spam, it will
likely be perceived as weak tea; for the details, see

https://www.howtogeek.com/738163/why-does-windows-11-need-tpm-2.0/

+ The CPU and TPM prerequisites for Windows 11 could change with
time, depending upon Windows 11's rate of adoption.

+ So far, I see nothing in Windows 11 that will make DXLab run better,
or run worse.

73,

Dave, AA6YQ

On Fri, Nov 5, 2021 at 10:31 AM, Dave AA6YQ wrote:

+ The CW DXCC award requires obtaining award credit for all 340 entities in CW. It does not require obtaining award credit for all 340 entities in CW on every band.

Yeah, I just realized this after digging in a bit more. So then the way to have a station show up for all bands/modes is by adding it to the Leaderboard list in the special callsigns.