Date   

Re: FTDX101MP Dual Watch / Split issue

Dave AA6YQ
 

+ AA6YQ comments below

Here's the scenario.
Split operation (mode does not matter)
MAIN VFO set to RX
SUB VFO set to TX and RX
The rigs MAIN TUNING DIAL is set to SUB (I do this so that I can follow the listening pattern of the DX station.)

This is what happens when you click on a new spot that is simplex (mode does not matter)

MAIN VFO is set to the spot frequency
MAIN VFO set to TX
SUB VFO is set to RX
The rigs MAIN TUNING DIAL is set to SUB

Because the MAIN VFO is not set to RX, there is no audio for the spotted frequency.

I "believe" what should happen is
MAIN VFO is set to the spot frequency
MAIN VFO set to TX and RX
SUB VFO is set to RX
The rigs MAIN TUNING DIAL is set to MAIN

Note: when clicking on a new spot that is SPLIT, the VFO settings stay as they were and the frequencies are properly set.

+ When you double-click on the Spot Database Entry for a station operating in split, the Main VFO is set to receive the station's RX frequency, the Sub VFO is set to transmit on the most recently reported TX frequency, and split is enabled.

73,

Dave, AA6YQ


Re: Problem with split on Icom IC-7300

Dave AA6YQ
 

+ AA6YQ comments below

I have got a problem with the split operation of a Icom IC-7300.

For example if I have set the receiver frequency to 21.074 and do some calls, after while the receive freq is not correct set to 21.074.
Instead it's changed to something slightly different. Probably the TX frequency used, and I have to reset the receive frequency with WSJT-X.
It's looks like it's something wrong with the split changing of RX/TX frequences.

+ Please provide a step-by-step description of how the receive frequency becomes incorrect.

73,

Dave, AA6YQ


Re: New user, delete initial test database, import full ADIF data

Dave AA6YQ
 

+ AA6YQ comments below

I uploaded logs for my 3 calls with a single error, I have one record that was logged as AK for Arkansas, now changed to AR.

Ready to move to the next stage:

+ Good!

"+ If you are able to complete step 8 with no errors, let me know, and we'll move to the next stage: assuming that you are pursuing DXCC awards, updating your log to reflect DXCC award credits granted. After that, we'll tackle syncing with LoTW..."

+ Please do the following:

1. On DXKeeper's Main window's "Log QSOs" tab, there's a Filter panel below the Log Page Display; click this panel's X button. The Main window's title bar will show how many QSOs are present in the Log Page Display; how many are shown as present?

2. On DXKeeper's Main window's "Log QSOs" tab, click the Adv button above the Log Page Display; the "Advanced Sorts, Filters, and Modifiers" window will appear

3. In the "Advanced Sorts, Filters, and Modifiers" window's "SQL Query Filters" panel, type

app_DXKeeper_LoTW_QSL_Sent = 'R'

into an "SQL expression" textbox, and then click the Filter button to its right. How many QSOs are shown as present in the Log Page Display?

4. repeat step 3 with the expression

app_DXKeeper_LoTW_QSL_Sent = 'U'

5. repeat step 3 with the expression

app_DXKeeper_LoTW_QSL_Sent = 'Y'

6. repeat step 3 with the expression

app_DXKeeper_LoTW_QSL_Rcvd = 'R'

7. repeat step 3 with the expression

app_DXKeeper_LoTW_QSL_ Rcvd = 'Y'

8. repeat step 3 with the expression

app_DXKeeper_LoTW_QSL_ Rcvd = 'V'

73,

Dave, AA6YQ


Re: New user, delete initial test database, import full ADIF data

RICH NU6T
 

I uploaded logs for my 3 calls with a single error, I have one record that was logged as AK for Arkansas, now changed to AR.

Ready to move to the next stage:

"+ If you are able to complete step 8 with no errors, let me know, and we'll move to the next stage: assuming that you are pursuing DXCC awards, updating your log to reflect DXCC award credits granted. After that, we'll tackle syncing with LoTW..."

On Monday, May 2, 2022, 04:55:27 PM PDT, RICHARD Hill <r.e.hill@...> wrote:


OK.  I successfully imported KG6JOT and AE6JW logs with no errors, no error log created.
NU6T logs included an error and an error log re: Invalid Primary Admin Subdivision: AK, and much more in one line.  I don't read this string well, but it seems to be a single item.

Thanks for the clear guidance!  I look forward to the next steps.

Rich
NU6T

On Monday, May 2, 2022, 10:55:57 AM PDT, RICHARD Hill <r.e.hill@...> wrote:


OK, questions:

    2a. on the General tab of DXView's Configuration window, specify your "Station Callsign", Location, Latitude, and Longitude

-- At this point, I believe the station callsign is NU6T?  We are about to import logs separately for my calls: KG6JOT, AE6JW and current call, NU6T.



     7e. in the "Replacement options" panel,

- check the "Station Callsign" box, and set the textbox to its right to KG6JOT

- check the "Operator Callsign" box, and set the textbox to its right to KG6JOT

- if you want your QSOs made as KG6JOT to specify an owner callsign, check the "Owner Callsign" box, and set the textbox to its right to the desired owner callsign (there is no automation in DXLab that is sensitive to a QSO's "Owner Callsign" item other than filtering and sorting QSOs)

-- AT THE TIME, KG6JOT was the Station callsign, Operator callsign, and, as I understand, the Owner callsign.  But since the ownership moved with callsign upgrades, should the current data remain with KG6JOT or upgrade to NU6T.  I'm thinking it should remain as the historic data, KG6JOT?

Of course, AE6JW was the same for that time, and now NU6T.  Should I apply NU6T as owner callsign for all three?  Eventually, I may add in data from guest operator logs where NU6T was the operator callsign, but the Station and Owner will be a different callsign.

I also have contest logs where I was the operator, but used a borrowed callsign at my QTH, or a borrowed call at a nice station owned by another ham.  At home, the borrowed call would be the Operator call, the Station and Owner calls were mine, NU6T.  At someone else's station, the borrowed call would be the Operator call, and the Station and Owner calls would be that someone's call.  Yes?

It seems useful to include NU6T as the owner callsign.  Am I missing anything?  Thank you!

Trying to keep it all straight and relearn much.  Glad to have great advice, and take small steps!

Rich
NU6T




On Monday, May 2, 2022, 10:26:24 AM PDT, RICHARD Hill <r.e.hill@...> wrote:


Thanks, Dave, will go to work on it!  Much appreciated!

On Monday, May 2, 2022, 10:21:53 AM PDT, RICHARD Hill <r.e.hill@...> wrote:


Forward

----- Forwarded Message -----
From: Dave AA6YQ <aa6yq@...>
To: "dxlab@groups.io" <dxlab@groups.io>
Sent: Sunday, May 1, 2022, 08:19:24 PM PDT
Subject: Re: [DXLab] New user, delete initial test database, import full ADIF database

Correction: in step 4a below, the pathname should be

C:\DXLab\DXKeeper\LOGS\NU6T.mdb

(no space between the \ and the NU6T.mdb)

      73,

            Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Sunday, May 01, 2022 11:09 PM
Subject: Re: [DXLab] New user, delete initial test database, import full ADIF database

+ At the top of the Configuration window's Log tab, what pathname is specified in the "Log file" panel?

C:\DXLab\DXKeeper\LOGS\Test-8_Jan_2022_NU6T.mdb

+Thanks. Here's my recommended initial course of action. If you have questions or concerns, please post them here before proceeding.

1. terminate DXKeeper


2. direct the DXLab Launcher to install DXView so that DXKeeper will have access to up-to-date information databases

2a. on the General tab of DXView's Configuration window, specify your "Station Callsign", Location, Latitude, and Longitude

2b. on the Databases tab of DXView's Configuration window, upgrade all relevant databases to their currently-available versions

- you don't need the RDA database if you're not pursuing RDA awards for confirming  Russian Districts

- you don't need the eQSL AG database if you're not pursuing the CQ WAZ or CQ WPX awards


3. Start DXKeeper


4. In the "Log file" panel at the top of DXKeeper's Configuration window's Log tab,

4a. change the pathname to

C:\DXLab\DXKeeper\LOGS\ NU6T.mdb

4b. click the Create button on the right side of the panel


5. Configure DXKeeper for interoperation with LoTW, as described here:



6. Since in the future you may be making QSOs from new locations,

6a. review


6b.on the Main window's "my QTHs" tab, create and populate a "my QTH" for your current location

- I suggest FairOaks as the ID for this "my QTH"

- set the LoTW selector in the FairOaks "my QTH" to the "Station Location" you've been using to upload QSOs made from your current QTH to LoTW

- check the VUCC and WAS boxes so that QSOs made from your current location will be considered for those awards, even if you aren't now pursuing them


7. On DXKeeper's Main window's "Import QSOs" tab,

7a. there are 12 checkboxes at the top of the panel; disable (uncheck) them all except these two, which you should enable by checking:

- "Deduce missing items ..."
- "Record import errors in error file"

7b. in the "ADIF style options" panel, select "standard ADIF"

7c. in the "Duplicate checking" panel, uncheck the "Check duplicates on import" box

7d. in the "Substitution options" panel, uncheck all boxes

7e. in the "Replacement options" panel,

- check the "Station Callsign" box, and set the textbox to its right to KG6JOT

- check the "Operator Callsign" box, and set the textbox to its right to KG6JOT

- if you want your QSOs made as KG6JOT to specify an owner callsign, check the "Owner Callsign" box, and set the textbox to its right to the desired owner callsign (there is no automation in DXLab that is sensitive to a QSO's "Owner Callsign" item other than filtering and sorting QSOs)

- uncheck the "Contest ID" and "State, Province, & Section" boxes

7f. click the Start button in the lower-left corner of the tab; in the "ADIF Import" window that appears, select the ADIF file containing your KG6JOT QSOs, and then click the Open button in the window's lower-right corner. DXKeeper will import your KG6JOT QSOs.


8. If errors are encountered, they will be recorded in an error file present in the same folder as the ADIF file containing your KG6JOT QSOs; if there errors reported, please describe them here so that I can help you resolve them. If no errors are reported, then repeat steps 7e and 7f for AE6JW and NU6T.

+ If you are able to complete step 8 with no errors, let me know, and we'll move to the next stage: assuming that you are pursuing DXCC awards, updating your log to reflect DXCC award credits granted. After that, we'll tackle syncing with LoTW...

      73,

                Dave, AA6YQ















On Sunday, May 1, 2022, 03:00:26 PM PDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below


    I don't understand, " What is specified in the wide textbox in the "Log file" panel at the top of the Configuration window's Log tab?"  I don't understand where to look.  I'm not finding it in TQSL or Logger32.  I did not find such in DXKeeper,  Sorry

+ On the "Log QSOs" tab of DXKeeper's Main window, please click the Config button near the lower-right corner - just above the Log Page Display.

+ DXKeeper's Configuration window will appear; select its Log tab.

+ At the top of the Configuration window's Log tab, what pathname is specified in the "Log file" panel?

      73,

              Dave, AA6YQ














--
This email has been checked for viruses by AVG.







Re: Dxlabs with FTDX101MP

Joe Subich, W4TV
 

+ Thanks, Rick. WSJT-X has a similar defect, but I've not been able to convince the WSJT-X development team to correct it.
Probably because JTDX uses the WSJTX transceiver control code (and
hamlib) without change. The significant differences between JTDX
and the version of WSJTX on which it is built lie in the UI plus
the addition of auto sequencing capabilities (but not full robot
mode).

73,

... Joe, W4TV


On 2022-05-03 5:35 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
I think that I have resolved the problem. I use JTDX for my FT-8 program. I use USB on my FTDX101 when operating FT-8. In the JTDX settings under radio-- mode I had selected USB. When I changed that to
none-- the auto switching problem when in trying to operate split in CW stopped and FT-8 still worked fine.
+ Thanks, Rick. WSJT-X has a similar defect, but I've not been able to convince the WSJT-X development team to correct it.
73,
Dave, AA6YQ


Re: Flex6600

Dave AA6YQ
 

+ AA6YQ comments below

I actually had two thoughts going when I responded to the post Dave. As I was typing the "YES" response it dawned on me that being able to return the first copy command slice to the original frequency and mode would also be beneficial. Hence the added remark. In thinking about it, this would be something that would functionally resemble swap slice B A or A B in addition to the copy commands. So in this scenario, to answer your question, it would take , for example, the frequency and mode of Slice A and swap it with frequency and mode of Slice C. Once accomplished, you would just initiate a swap back of Slice C to A if so desired. This , in my mind, would eliminate the need to copy Slice 'n' to Slice 'n' and just use swap instead.

+ Implementing a "swap" instead of a "copy" would eliminate the need to save VFO A's state (frequency, mode, passband, antenna selection, etc.), but I fear this would confuse users.

+ The objective is to make it easy to log a QSO with a station being worked via slice C, D, E, F, G, or H.

+ To work a station via one of those slices, that slice has to be "selected" in SmartSDR. Commander can detect that to be the case. Thus the objective can be accomplished by providing two new button-activated functions:

1. "Activate slice X", where X is the currently selected slice: saves VFO A's and VFO B's state, and copies slice X's state to both VFO A and VFO B. If the user wishes to operate split, he or she can click one of Commander's Up or Down buttons, or manually check the split box and adjust VFO B's frequency.

2. "Restore": restores VFO A's and VFO B's state as of the last time the "Activate slice X" function was invoked.

+ When controlling a Flex Signature transceiver, the Mode panel on Commander's Main window can be shortened to make room for the above two buttons.

+ Comments? Better ideas?

73,

Dave, AA6YQ


Re: Dxlabs with FTDX101MP

Dave AA6YQ
 

+ AA6YQ comments below

I think that I have resolved the problem. I use JTDX for my FT-8 program. I use USB on my FTDX101 when operating FT-8. In the JTDX settings under radio-- mode I had selected USB. When I changed that to
none-- the auto switching problem when in trying to operate split in CW stopped and FT-8 still worked fine.

+ Thanks, Rick. WSJT-X has a similar defect, but I've not been able to convince the WSJT-X development team to correct it.

73,

Dave, AA6YQ


Re: Dxlabs with FTDX101MP

Dave AA6YQ
 

+ AA6YQ comments below

Dave, you should know that with the FTdx101 it is not necessary to use the split button to operate split. I almost never do. I use the red and green buttons above the main tuning dial.

+ Thanks, Bill. DXLab's automation employs the functionality provided in most modern transceiver. When you double-click a Spot Database Entry for a station operating split with the "Set Xcvr split" option enabled, SpotCollector will direct Commander to place your transceiver in split mode, and set VFOs A and B with the RX and TX frequencies respectively. You can disable "Set Xcvr split" if your radio provides a better way to operate split.

73,

Dave, AA6YQ


Re: RDA PRI/SEC LOGGING SELECTION OPTIONS

Jose - N4BAA <jose-castillo@...>
 

Hello..

OK...yes. I see the issue. 
NOT knowing exactly where this station was 'mobile' was MY issue.
Had I changed his country from UA0 to UA, I would have seen the PRI and SEC divisions presented properly.

Stand down! ALL is working as designed.... Pilot error! <smiling>

Thanks
Jose 
N4BAA


-----Original Message-----
From: Dave AA6YQ <aa6yq@...>
To: DXLab@groups.io
Sent: Tue, May 3, 2022 8:54 pm
Subject: Re: [DXLab] RDA PRI/SEC LOGGING SELECTION OPTIONS

+ AA6YQ comments below

When working Russian Oblasts (RDA AWARD)....
When a Russian is worked who is MOBILE of PORTABLE (RN9N/m for example), often times it is not possible to indicate the their correct RDA (Oblast) from the presented drop down menu.

+ When I enter RN9N/M in the Capture window and strike the enter key, the DXC prefix selector is set to UA0, the primary (subyekt) selector is empty, and the secondary selector is empty. Opening the primary selector, I see a list of all primary subdivisions in Asiatic Russia, and can select one. After I do that, the secondary selector is populated with all of the districts in the selected primary subdivision, any one of which I can select.

+ If I change the DXCC prefix from UA0 to UA, then the primary selector is populated with all primary subdivisions in European Russia; choosing one populates the secondary selector all districts in the selected primary subdivision.

+ Is this not working for you, Jose?


      73,


                Dave, AA6YQ








Re: RDA PRI/SEC LOGGING SELECTION OPTIONS

Dave AA6YQ
 

+ AA6YQ comments below

When working Russian Oblasts (RDA AWARD)....
When a Russian is worked who is MOBILE of PORTABLE (RN9N/m for example), often times it is not possible to indicate the their correct RDA (Oblast) from the presented drop down menu.

+ When I enter RN9N/M in the Capture window and strike the enter key, the DXC prefix selector is set to UA0, the primary (subyekt) selector is empty, and the secondary selector is empty. Opening the primary selector, I see a list of all primary subdivisions in Asiatic Russia, and can select one. After I do that, the secondary selector is populated with all of the districts in the selected primary subdivision, any one of which I can select.

+ If I change the DXCC prefix from UA0 to UA, then the primary selector is populated with all primary subdivisions in European Russia; choosing one populates the secondary selector all districts in the selected primary subdivision.

+ Is this not working for you, Jose?

73,

Dave, AA6YQ


Re: version 3.6.5 of the VarAC realtime HF chat application can directly log QSOs to DXKeeper via TCP

Dave AA6YQ
 

+ AA6YQ comments below
It does not look like there’s a mechanism for eQSL to achieve this, correct?

(Map VARA mode to DATA)

+ Not to my knowledge.

73,

Dave, AA6YQ


Re: FTDX101MP Dual Watch / Split issue

WB1DX
 

Hi Bill - I am not using the outer dial for tuning the SUB VFO, I use the CS function for other purposes. Instead, I am directly setting the main tuning dial to tune the SUB VFO, ie pressing the SUB button so that it illuminates BLUE. I prefer this because I have more control than trying to get my fat fingers to tune the outer ring.

73, Ken
WB1DX


Re: FTDX101MP Dual Watch / Split issue

n6ws
 

Ken,

What you describe as, "I believe what should happen" is exactly how mine operates.  I also usually have the Main/Sub enabled, so I can use the outer tuning dial to tune the pileup for QSX frequency.  Are you double-clicking on the spot in the main SpotCollector display window?

73, Bill
N6WS


On 5/3/2022 9:51 AM, WB1DX wrote:

Here's the scenario. 
Split operation (mode does not matter)
MAIN VFO set to RX
SUB VFO set to TX and RX
The rigs MAIN TUNING DIAL is set to SUB (I do this so that I can follow the listening pattern of the DX station.)

This is what happens when you click on a new spot that is simplex (mode does not matter)

MAIN VFO is set to the spot frequency
MAIN VFO set to TX
SUB VFO is set to RX
The rigs MAIN TUNING DIAL is set to SUB

Because the MAIN VFO is not set to RX, there is no audio for the spotted frequency.

I "believe" what should happen is
MAIN VFO is set to the spot frequency
MAIN VFO set to TX and RX
SUB VFO is set to RX
The rigs MAIN TUNING DIAL is set to MAIN

Note: when clicking on a new spot that is SPLIT, the VFO settings stay as they were and the frequencies are properly set.

Let me know if you'd like me to capture or provide more details.

Ken, WB1DX


Problem with split on Icom IC-7300

Markku SM5FLM
 
Edited

I have got a problem with the split operation of a Icom IC-7300.

For example if I have set the receiver frequency to 21.074 and do some calls, after while the receive freq is not correct set to 21.074.
Instead it's changed to something slightly different. Probably the TX frequency used, and I have to reset the receive frequency with WSJT-X.
It's looks like it's something wrong with the split changing of RX/TX frequences.
This has not been a problem before.

It has been several months I last used DXlab. So I had to do several updates of DXlab and windows 10.
I'm now using all the latest versions of all programs in DXlab, WSJT-X ver 2.5.4,  and win10 version 21H2, os-version 19044.1645.


FTDX101MP Dual Watch / Split issue

WB1DX
 

Here's the scenario. 
Split operation (mode does not matter)
MAIN VFO set to RX
SUB VFO set to TX and RX
The rigs MAIN TUNING DIAL is set to SUB (I do this so that I can follow the listening pattern of the DX station.)

This is what happens when you click on a new spot that is simplex (mode does not matter)

MAIN VFO is set to the spot frequency
MAIN VFO set to TX
SUB VFO is set to RX
The rigs MAIN TUNING DIAL is set to SUB

Because the MAIN VFO is not set to RX, there is no audio for the spotted frequency.

I "believe" what should happen is
MAIN VFO is set to the spot frequency
MAIN VFO set to TX and RX
SUB VFO is set to RX
The rigs MAIN TUNING DIAL is set to MAIN

Note: when clicking on a new spot that is SPLIT, the VFO settings stay as they were and the frequencies are properly set.

Let me know if you'd like me to capture or provide more details.

Ken, WB1DX


Re: Flex6600

dxradio33
 

I actually had two thoughts going when I responded to the post Dave. As I was typing the "YES" response it dawned on me that being able to return the first copy command slice to the original frequency and mode would also be beneficial. Hence the added remark. In thinking about it, this would be something that would functionally resemble swap slice B A or A B in addition to the copy commands. So in this scenario, to answer your question, it would take , for example, the frequency and mode of Slice A and swap it with frequency and mode of Slice C. Once accomplished, you would just initiate a swap back of Slice C to A if so desired. This , in my mind, would eliminate the need to copy Slice 'n' to Slice 'n' and just use swap instead.

Thanks for entertaining these suggestions Dave.

73,
Joe K8FC

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Monday, May 02, 2022 23:03
To: DXLab@groups.io
Subject: Re: [DXLab] Flex6600

+ AA6YQ comments below

I would personally like to vote YES for this idea. I am presently looking at three active slices, on three separate bands using three separate modes. I can directly control Slice A & B with commander but having the ability to copy slice C or D to A would solve a myriad of problems me thinks. Lastly, if you could return Slice A to it's previous state would be most appreciated.

+ Thanks, Joe. Please consider this scenario:

Slice A: 7005

Slice B: 14005

Slice C: 21005

+ The following commands are executed in sequence:

copy_slice B A (sets slice A to 14005)

copy_slice C A (sets slice A to 21005)

+ Now suppose a command that returns slice A to its previous state is executed; to what frequency should A be set?

73,

Dave, AA6YQ


Re: Dxlabs with FTDX101MP

rick boulis
 

I think that I have resolved the problem. I use JTDX for my FT-8 program. I use USB on my FTDX101 when operating FT-8. In the JTDX settings under radio-- mode I had selected USB. When I changed that to none-- the auto switching problem when in trying to operate split in CW  stopped and FT-8 still worked fine.

Thanks to all.

Rick N4HU

On 5/2/2022 10:52 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I need some guidance please. Been using DXlabs for several years. After setting up the new radio-- FTDX101MP- all operates as expected except for one thing. I don't know if I have a setup problem in the software or the radio.
VFO A set to CW automatically goes back to USB whenever I go split.

+ Does this happen when you enable split via the radio's front panel, via Commander's Main window, or both?

73,

Dave, AA6YQ






Re: Dxlabs with FTDX101MP

BILL KENNAMER
 

Dave, you should know that with the FTdx101 it is not necessary to use the split button to operate split. I almost never do. I use the red and green buttons above the main tuning dial.

I also don’t have a problem with the radio being on the wrong mode when I operate split.

K5FUV 

On Monday, May 2, 2022, 9:52 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I need some guidance please.  Been using DXlabs for several years. After setting up the new radio-- FTDX101MP-  all operates as expected except for one thing. I don't know if  I have a setup problem in the software or the radio.
VFO A set to CW automatically goes back to USB whenever I go split. 

+ Does this happen when you enable split via the radio's front panel, via Commander's Main window, or both?

      73,

              Dave, AA6YQ








Re: Flex6600

Joe
 

That may be true for your first DXCC, or if you have worked 300 entities on every band, but not so otherwise.  If you are still pursuing needed DX for all band/mode slots, and when 10-12-15-17 are hot as of lately, it is common, for me, to see needed band/mode slots a few at a time.

Joe/WQ6Q


RDA PRI/SEC LOGGING SELECTION OPTIONS

Jose - N4BAA <jose-castillo@...>
 

Good Morning,

When working Russian Oblasts (RDA AWARD)....
When a Russian is worked who is MOBILE of PORTABLE (RN9N/m for example),
often times it is not possible to indicate the their correct RDA (Oblast) from the presented drop down menu.

Would like to recommend the PRI/SEC sub divisions all be presented to allow logging correct RDA from Entry Window.

Thanks/73,

Jose - N4BAA
RDA Hunter