Today I worked a station in Northern Ireland with call beginning "MI0". MI is one of the prefixes used for Northern Ireland, but in DXKeeper's DXCC field it was saved as "G" (England) instead of "GI". Last November I worked another station with call beginning "MI5", and it correctly saved the DXCC value "GI". Why was today's contact saved with the wrong value?

Last December, between the two QSOs, I did move to a new computer, so I suspect something like my copy of the DXCC database or something else is out of date. Is that the problem?

+ The current DXCC database (version 2.6.1) considers any callsign beginning with MI as "Northern Ireland". To see this, type MI or MI0 into DXView's callsign box, and strike the Enter key.

+ Possible reasons why your MI0 QSO was logged with a DXCC entity of "England":

1. the QSO was logged from another application that conveyed the QSO to DXKeeper with a DXCC entity of "England"

2. DXView's "Override List" contains an entry for the callsign that specifies its DXCC entity as "England"

3. You have a previously logged QSO with the callsign that specifies a DXCC entity of "England"

4. You have DXKeeper configured to perform a callbook lookup, which reported the callsign's DXCC entity as "England"

73,

Dave, AA6YQ

On 2021-10-23 4:20 PM, Steve, N5EP via groups.io wrote:

Today I worked a station in Northern Ireland with call beginning
"MI0". MI is one of the prefixes used for Northern Ireland, but in
DXKeeper's DXCC field it was saved as "G" (England) instead of "GI".

DXCC Database 2.6.1 properly recognizes MI0 callsigns as Northern
Ireland.

What was the specific callsign that was logged as G instead of GI?

Do you have a previous QSO with that callsign in DXKeeper? Do you
have an override for that callsign that defines G instead of GI?

73,

... Joe, W4TV


On 2021-10-23 4:20 PM, Steve, N5EP via groups.io wrote:

Today I worked a station in Northern Ireland with call beginning "MI0". MI is one of the prefixes used for Northern Ireland, but in DXKeeper's DXCC field it was saved as "G" (England) instead of "GI".  Last November I worked another station with call beginning "MI5", and it correctly saved the DXCC value "GI".  Why was today's contact saved with the wrong value?
Last December, between the two QSOs, I did move to a new computer, so I suspect something like my copy of the DXCC database or something else is out of date.  Is that the problem?
Thanks.
Steve, N5EP

+ AA6YQ comments below

I seem to have the problem resolved. I believe you inadvertently gave me the clue when you sent me your e-mail this morning saying that everything looked normal in WW. It sent back to think about his again from the beginning.
If WW/Commander were functioning completely normally, and MMTTY was functioning normally, then by process of elimination, my only conclusion was that the Yaesu manual and one bit of advice that you gave me awhile back might explain the problem.
The misinformation (or, at least, nonfunctional information in my case) in the Yaesu manual is that only the USB cable is necessary for proper operation.

+ That's correct for RTTY AFSK. The FT101 manual also shows how to transmit and receive RTTY with an external modem. The FT101 manual is completely silent on how to use RTTY FSK.

There must have been some port conflict with the use of the USB pathways (COM 10 and COM 12). Any juggling of the ports only resulted in port errors. So, leaving the USB cable in place, I attached a cable to the RS-232 port, which the PC set at COM 14. (I run a lot of stuff out of this computer!) On the PTT tab in WW, I entered COM 14 instead of NONE, and left MODE at Xcvr Ctrl App.

+ That's wrong. You want Commander controlling RX/TX switching, not WinWarbler. If Commander can't interact with your transceiver, it can't keep WinWarbler aware of your transceiver's frequency, which means; that means WinWarbler can't accurately log QSOs.

I then went to the EXTFSK64 mini-window in MMTTY and checked to see that it was set to COM 10, the standard port for USB. It worked. I tested it online with a friend using essentially the same setup, i.e., same radio, DXLab running WW and Commander, and both the USB and RS-232 ports active, and he verified the integrity of my transmissions. Incidentally, it turns out that he was also using both ports, although he wasn't sure the RS-232 port was active. I assured him that it probably is.

+ Yaesu's transceiver documentation is generally terrible, but they have reached a new low with the FTDX101. Nowhere is there documentation describing the functions of the radio's physical and virtual serial ports. Without this documentation, we're all just guessing.


So, I appreciate both your help and your patience with me. Your verifying that WW and Commander were working properly, and my knowing that MMTTY was working normally, is what gave me the final clue. There had to be a conflict. For anyone else having the same problem with RTTY using an FTdx-101MP, you might let them know that resolution for them may well involve invoking both the USB and RS-232 ports. FYI, the Yaesu manual shows the radio connected by a single USB cable for digital communication, and that was working for me for FT8 but not RTTY.I needed the third port.

+ My advice to anyone contemplating an FTDX-101 is "instead consider a transceiver with accurate, comprehensive documentation".

73,

Dave, AA6YQ

+ AA6YQ comments below

Thanks again. You are Everywhere! I'm surprised you have time to get on the radio. hi hi

+ I spent most of the afternoon burying a new armored rotator cable and tracking down an "open" in the power cable for my low-band RX 4-square that has prevented me from working Eswatini on 160m.

      73,

             Dave, AA6YQ

+ AA6YQ comments below

I got it. I didn’t double click, just single clicked.

+ I don't know what you mean, Marty. No double-clicking is required to access the Fonts panel on the Configuration window's "Spot Database Display" tab.

+ You might find this article to be helpful:

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

73,

Dave, AA6YQ

Dave,

 Thanks again. You are Everywhere! I'm surprised you have time to get on the radio. hi hi

 I followed these instructions and clicked on the in step 2. Instead of going to a file to download, it just displayed the text file on screen. So I copied all and pasted it into the existing Radios.txt file and replaced the old info in the file. I then started commander, found the 7300 on the list and selected it. So far so good. I will now proceed with getting the radio/computer setup with the warbler. If all goes well, I think I will dump HRD and go with DXLab/FLDigi.

As usual, thanks again and 73,
Steve - N6RSH

>1. terminate Commander

>2. download the current radios.txt file from

>https://www.dxlabsuite.com/commander/Radios.txt

>and place it in your Commander folder, replacing the existing file with the same name

>3. start Commander

I got it. I didn’t double click, just single clicked.

AA6YQ comments below

At one time, we had the capability to change different fonts characteristics.

+ We still have that capability.

 

For instance you could go MS Sans Serif (current) but then select Bold, Italic etc and the font point (12,14 , etc).
With the current configuration, it is extremely difficult for these old eyes to see the spots displayed in Spot Collector.
Has this feature been m Ovid to another area or removed completely?

+ No. It's still available in the Fonts panel on the Configuration window's "Spot Database Display" tab.

     73,

           Dave, AA6YQ

Thanks Dave.
I don't know how I missed that.  Duhh!

Should have been set to RTTY.
Don

+ AA6YQ comments below

Name is Don.
I pasted the message but see that it did not show up.
The message says:
CI-V Commander
the mode WBFM in memory 10 is not supported by the currently-selected radio.
I have no idea what that means or where to look.

+ I means that Commander's memory #10 specifies a mode of wide-band FM, which your transceiver does not support. To prevent the message, select memory #10 and change its mode to one that your transceiver supports, like CW or SSB. See

https://www.dxlabsuite.com/commander/Help/UsingMemories.htm

73,
Dave, AA6YQ

Name is Don. 
I posted the message but see that it did not show up.
The message says:  
CI-V Commander
the mode WBFM in memory 10 is not supported by the currently-selected radio.
I have no idea what that means or where to look.
Thanks,
Don-NK6A
Mar Vista, CA

That was an enhancement that I suggested to Dave several years ago and he did additional as an enhancement. If something is entered in the user defined fields, one of which you can label “comments”, they will appear next time you work that station. I use that feature for comments, FOC or CW Ops number of a station, etc.

Alan - AC2K

+ AA6YQ comments below

I am sorry I did not see a name in your message. I probably can't help you, but did want to let you know you mentioned getting "a very strange message"... but readers of your post have no idea what that message says, so I don't see how they could help either.

+ Exactly right.

+ Don NK6A, please post the text of the message you are seeing.

     73,

             Dave, AA6YQ

All of a sudden when I start Commander I now get this very strange message.  I click OK a few times and Commander will start. I am using a FTDX101MP for my radio. I never to my knowledge made any changes to my setup or config. Anyone ever have this issue?  How do I correct it?

+ AA6YQ comments below

That direction/instruction certainly helps me to unpeel more about DXLabs and all the modules.

+ The best way to learn about DXLab is to slowly scan the reference documentation for each application, one at a time. While scanning, ignore all the details, but jot down the names of any functions to which you'd like to later return. After completing this "top-level review", prioritize the list functions you've assembled, and return to the reference documentation and the task-oriented documentation as you implement each one.

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

+ Don't expect to ingest all of this information over a weekend, or to instantly become as facile with DXLab as you were with its predecessor. There's a lot of functionality, and some of it is unique with respect to amateur radio software. Take your time, and enjoy the ride up the learning curve.

73,

Dave, AA6YQ

These are my Versions:
Cmd - 15.2.0
DxK - 16.3.2
DxV - 4.7.9
Laun - 2.1.4
Path - 5.2.6
Prop - 2.0.0
Spot - 8.9.2
Warb - 9.3.7

When I first installed DXLabs a couple of years ago, I know I had the 7300 set up. According to the Launcher, I am up to date.

????

+ If 15.2.0 appears in the title bar of Commander's Main window but the IC-7300 is not present in Commander's Radio Model selector, then the Radios.txt file in your Commander folder is obsolete, either because the Launcher's update mechanism was prevented from replacing it with the current version, or because the file was subsequently replaced with the obsolete version. To correct this,

1. terminate Commander

2. download the current radios.txt file from

https://www.dxlabsuite.com/commander/Radios.txt

and place it in your Commander folder, replacing the existing file with the same name

3. start Commander

73,

Dave, AA6YQ