Date   
Setting ALC Levels for Digital Mode Operation

Dave AA6YQ
 

Thanks to Joe W4TV, "Getting Started with DXLab" now includes this article:

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

73,

Dave, AA6YQ

Re: JRC JST-245

Dave AA6YQ
 

+ AA6YQ comments below

The antenna selection is indicated in the same query ("I") used to get the frequency and mode. Here is response format,

Iabdfg
where,
a = 1-3, indicates antenna selected
b = 0-2, indicates selected bandwidth (0-Wide, 1-Intermediate, 2-Narrow)
d = 0-5, indicates the mode selected
f = 8 digits show transmit and receive frequency
g = 0-2, indicates AGC setting

The meter readings can be obtained with a M command. I tried the command using the Message Monitoring tool. Adding H1 before the meter command and a H0 after. I tried it with M in receive and the S-meter value was returned. I did not try the meter commands in transmit so far.

+ Thanks.

+ Commander does not display antenna selection for any supported transceiver. For most radios that can switch among multiple antenna connectors, this would be consuming scarce screen real estate to replicate information already displayed on the radio's front panel.

+ In order to display a JST-245's S-meter and a selected transmit meter, Commander will have to know whether the radio is receiving or transmitting, which its currently not the case. I will extend Commander to do this, and send you this extended version to test. Then we can proceed to add support for metering.

73,

Dave, AA6YQ

Re: WSJT-X with Commander and Flex Maestro

Dave AA6YQ
 

+ AA6YQ comments below

To use WSJT-X with Flex, you need to have SSDR CAT, and SSDR DAX installed on the same computer as WSJT-X.

+ That's not correct.

+ As described in

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes>

+ WSJT-X should be configured to use Commander to control the transceiver, which in the case of a Flex Signature it does via SmartSDR's API over a local area network. SmartSDR CAT is superfluous, and should not be running.

+ Unless, of course, you aren't using DXLab. If that's the case, why post on this Discussion Group?

73,

Dave, AA6YQ

Re: Cabrillo file for the ARRL RTTY contest

Bernd - KB7AK
 

Hi Neil,

I was on Tab 1, and the exchange is captured automatically in TX Info and RX Info fields in the Contest section in the main QSO Tab.

Re: Cabrillo file for the ARRL RTTY contest

neil_zampella
 

Were you in TAB1 on the main WSJT-X window?    There is an issue where the exchange is not captured in WSJT-X if you're not on TAB 1.

Neil, KN3ILZ

On 1/9/2019 2:07 PM, Bernd - KB7AK wrote:
No to both to be honest. It was a last minute decision to stick with what I use (and it was a good decision). I understand that I should have entered my state abbreviation into the TX Serial# number field and uncheck Increment TX Serial#. But, what does this mean capture your QSO partner's state abbreviation, province abbreviation or serial number in each QSO's RX# item?" when the data comes automatically from JTAlerts. Do I need to touch each QSO after it has been logged and modify the record by entering the other side's State code?



AVG logo

This email has been checked for viruses by AVG antivirus software.
www.avg.com


Re: WSJT-X with Commander and Flex Maestro

Al Groff
 

Joe,
  To use WSJT-X with Flex, you need to have SSDR CAT, and SSDR DAX installed on the same computer as WSJT-X.  The easiest way to install CAT and DAX is to install the whole SSDR package on the PC, which will install DAX & CAT.  You need not run SSDR on the PC.  You can run Maestro to control the radio and run DAX and CAT on the PC to transport audio and control signals to WSJT-X.

AL, K0VM

On 1/9/2019 12:21 PM, K4PX K4PX wrote:
As I look at NM1W'a instructions to configure Commander with Flex6400 and WSJT-X, it specified that you need to configure SmartSDR menus.  I use a Maestro with my Flex 6400 and therefore do not have SmartSDR loaded on my network PC.  The menus on my Maestro do not have the choices that he specifies.  Advice?
Thanks,
Joe
K4PX

Re: Cabrillo file for the ARRL RTTY contest

Bernd - KB7AK
 

No to both to be honest. It was a last minute decision to stick with what I use (and it was a good decision). I understand that I should have entered my state abbreviation into the TX Serial# number field and uncheck Increment TX Serial#. But, what does this mean capture your QSO partner's state abbreviation, province abbreviation or serial number in each QSO's RX# item?" when the data comes automatically from JTAlerts. Do I need to touch each QSO after it has been logged and modify the record by entering the other side's State code?

Re: Cabrillo file for the ARRL RTTY contest

Dave AA6YQ
 

+ AA6YQ comments below

This is for FT8 part of the contest. I used my standard setup (WSJT-X, JTAlerts, DXKeeper) for this contest and QSOs were written to a new database to keep the data clean. When I generate the Cabrillo file, everything looks accurate, except the State/Province information is missing for both my station and the stations I worked. I am sure I overlooked something. The proper exchange information is shown for each record in DXK in the Contest section in the txinfor and rxinfo fields. I am sure I overlooked something else, what is it?

+ Did you log a few test QSOs before the contest and generate a Cabrillo file from them to be sure that you were recording the exchange correctly, as is strongly recommended in the 3rd paragraph of

<https://www.dxlabsuite.com/dxkeeper/Help/Contesting.htm>

?

+ Did you follow the instructions in "Note 16" in the above reference documentation for correctly recording the contest exchange?

73,

Dave, AA6YQ

Re: WSJT-X with Commander and Flex Maestro

Dave AA6YQ
 

+ AA6YQ comments below

As I look at NM1W's instructions to configure Commander with Flex6400 and WSJT-X, it specified that you need to configure SmartSDR menus.

+ Where can these instructions be found?

I use a Maestro with my Flex 6400 and therefore do not have SmartSDR loaded on my network PC. The menus on my Maestro do not have the choices that he specifies. Advice?

+ DXLab supports Flex Signature Radios running SmartSDR. I don't have a Maestro, don't know how it works, and don't claim that DXLab supports it. I'm still waiting for Flex to identify and correct the defects that cause audio stuttering and dropouts when valid commands are sent to SmartSDR 2.4.9.

73,

Dave, AA6YQ

Cabrillo file for the ARRL RTTY contest

Bernd - KB7AK
 

This is for FT8 part of the contest. I used my standard setup (WSJT-X, JTAlerts, DXKeeper) for this contest and QSOs were written to a new database to keep the data clean. When I generate the Cabrillo file, everything looks accurate, except the State/Province information is missing for both my station and the stations I worked. I am sure I overlooked something. The proper exchange information is shown for each record in DXK in the Contest section in the txinfor and rxinfo fields. I am sure I overlooked something else, what is it?

WSJT-X with Commander and Flex Maestro

K4PX K4PX
 

As I look at NM1W'a instructions to configure Commander with Flex6400 and WSJT-X, it specified that you need to configure SmartSDR menus.  I use a Maestro with my Flex 6400 and therefore do not have SmartSDR loaded on my network PC.  The menus on my Maestro do not have the choices that he specifies.  Advice?
Thanks,
Joe
K4PX

Re: JRC JST-245

Brian Rehmer
 

Dave,

The antenna selection is indicated in the same query ("I") used to get the frequency and mode.  Here is response format,

Iabdfg
where,
            a = 1-3, indicates antenna selected
            b = 0-2, indicates selected bandwidth (0-Wide, 1-Intermediate, 2-Narrow)
            d = 0-5, indicates the mode selected
            f = 8 digits show transmit and receive frequency
            g = 0-2, indicates AGC setting

The meter readings can be obtained with a M command.  I tried the command using the Message Monitoring tool.  Adding H1 before the meter command and a H0 after.  I tried it with M in receive and the S-meter value was returned.  I did not try the meter commands in transmit so far.

Is there anything I can do to help.

Brian, KC4KK




Re: A Question about Station, Op and Owner Call

Mike Flowers
 

Thanks, Dave. DXKeeper has allowed me to find and correct all the strangeness that had a accumulated in my log.

I’ve created myQTHIDs for all the locations from which I’ve operated and applied them to the appropriate log entries, as well as the callsigns I used.

My log is in the best shape it has ever been! Backed it up multiple network locations, flash drives and the Cloud.

Thanks for this great software!!

-- Mike Flowers, K6MKF, NCDXC - "It's about DX!"

On Jan 8, 2019, at 5:24 PM, Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

I've eliminated all sorts of artefacts from previous loggers in my DXKeeper log, and now I'm ready to address the question of the
Auxiliary pane's Station, Op and Owner Call data elements. This also relates to the myQTH data element.

I've held four callsigns since 1968 and operated from several QTH locations with them, so myQTH, I think, should reflect where I was
operating.

My sense is that when I was making QSOs as KD3AN, for example, the Station, Op and Owner Call would all be KD3AN, as I've only
logged QSOs made with my callsign from my own home station.

+ The only automation that involves "Operator Call" and "Owner Call" are the <opcall> and <ownercall> QSL substitution commands that
can be used to print this information on a QSL card or label:

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSL%20Substitution%20Commands

+ If you pursue awards, I'd use "Operator Call" to note QSOs made by operators other than you employing your "Station Callsign"
over the air, as such QSOs are not valid for DXCC awards an may not be valid for other awards.

I'd just like to know that what I am thinking is correct.

+ That's how I've handled my previous callsignsigns.

+ For more information, see

<https://www.dxlabsuite.com/dxlabwiki/MultipleLogFiles>

<https://www.dxlabsuite.com/dxlabwiki/ManageMultipleQTHs>

<https://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations>

73,

Dave, AA6YQ



Re: A Question about Station, Op and Owner Call

Dave AA6YQ
 

+ AA6YQ comments below

I've eliminated all sorts of artefacts from previous loggers in my DXKeeper log, and now I'm ready to address the question of the
Auxiliary pane's Station, Op and Owner Call data elements. This also relates to the myQTH data element.

I've held four callsigns since 1968 and operated from several QTH locations with them, so myQTH, I think, should reflect where I was
operating.

My sense is that when I was making QSOs as KD3AN, for example, the Station, Op and Owner Call would all be KD3AN, as I've only
logged QSOs made with my callsign from my own home station.

+ The only automation that involves "Operator Call" and "Owner Call" are the <opcall> and <ownercall> QSL substitution commands that
can be used to print this information on a QSL card or label:

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSL%20Substitution%20Commands

+ If you pursue awards, I'd use "Operator Call" to note QSOs made by operators other than you employing your "Station Callsign"
over the air, as such QSOs are not valid for DXCC awards an may not be valid for other awards.

I'd just like to know that what I am thinking is correct.

+ That's how I've handled my previous callsignsigns.

+ For more information, see

<https://www.dxlabsuite.com/dxlabwiki/MultipleLogFiles>

<https://www.dxlabsuite.com/dxlabwiki/ManageMultipleQTHs>

<https://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations>

73,

Dave, AA6YQ

Re: DXKeeper

Kent Olsen
 

Stan

Was this for an IU8 (I cant remember the rest of the call)?? If so I got the same message.

Thanks
73
Kent
N6WT


On Tue, Jan 8, 2019 at 9:01 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

When I do sync LotW QSLs, why does DXKeeper display the result message "WAZ candidate doesn't specify a CQ zone"   The QSO record shows a CQ zone and a ITU zone.

+ The message "WAZ candidate doesn't specify a CQ zone" means that even though the QSO is confirmed via LoTW, your QSO partner did not specify a CQ zone in the "Station Location" he or she used to submit your QSO, so the QSO is not "confirmed for WAZ". There are similar messages when a QSO is reported as confirmed by LOTW but your QSO partner fails to specify a "US State" (for WAS) or grid square (for VUCC) in the "Station Location" used to submit your QSO.

      73,

              Dave, AA6YQ




A Question about Station, Op and Owner Call

Mike Flowers
 

Hi Folks,

 

I’ve eliminated all sorts of artefacts from previous loggers in my DXKeeper log, and now I’m ready to address the question of the Auxiliary pane’s Station, Op and Owner Call data elements.  This also relates to the myQTH data element.

 

I’ve held four callsigns since 1968 and operated from several QTH locations with them, so myQTH, I think, should reflect where I was operating.

 

My sense is that when I was making QSOs as KD3AN, for example, the Station, Op and Owner Call would all be KD3AN, as I’ve only logged QSOs made with my callsign from my own home station.

 

I’d just like to know that what I am thinking is correct.

 

Thanks!

 

- 73 and good DX de Mike, K6MKF, Past President - NCDXC

 

Re: DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

When I do sync LotW QSLs, why does DXKeeper display the result message "WAZ candidate doesn't specify a CQ zone" The QSO record shows a CQ zone and a ITU zone.

+ The message "WAZ candidate doesn't specify a CQ zone" means that even though the QSO is confirmed via LoTW, your QSO partner did not specify a CQ zone in the "Station Location" he or she used to submit your QSO, so the QSO is not "confirmed for WAZ". There are similar messages when a QSO is reported as confirmed by LOTW but your QSO partner fails to specify a "US State" (for WAS) or grid square (for VUCC) in the "Station Location" used to submit your QSO.

73,

Dave, AA6YQ

DXKeeper

Stan Gammons
 

When I do sync LotW QSLs, why does DXKeeper display the result message "WAZ candidate doesn't specify a CQ zone"   The QSO record shows a CQ zone and a ITU zone.


73

Stan
KM4HQE

Re: Flex Radio Spots issue

Dave AA6YQ
 

* AA6YQ comments below

On Tue, Jan 8, 2019 at 07:13 AM, Mark Hanson wrote:

= W3II comments below
+ AA6YQ comment below

=The clear command is not necessary; each spot is / can be assigned a lifetime then when expired will delete.
+ It is necessary to remove all callsigns when changing bands.
= Individually managing your spots or letting them timeout are viable options; changes to spots are easily tracked

=Clearing all spots should not be done as it assumes you are the only spot generator.
+ It is unreasonable to have more than one application rendering callsigns on a Flex panadaptor. The color schemes used will vary from application to application, as will the behavior when clicked.
= I believe this is where we disagree; I have encountered many flex radio users that use multiple spot sources. Spot color and behavior is / can be controlled on a per spot basis allowing for these scenarios.

+ Users can configure Commander to not render callsigns on the panadaptor. I hope FRStack offers a similar option.
= FRStack spot feature are and have always been optional; FRStack is a widely popular companion application for the Flex Signature Series Radios that adds MRU band stacking memories, memories, memory scanning, squelch, remote operation via SmartLink and many other features.

= Thank you for your time; I will add logic to detect errant spot removal then recover accordingly

* My position is that users should not enable DXLab's display of active callsigns on a Flex panadapter unless Commander is the only application directly displaying such callsigns. Operation with multiple applications directly displaying such callsigns is not supported.

* SpotCollector provides an interface that enables other applications to report active DX stations, the callsigns of which would be displayed on a Flex panadapter. JTAlert employs this interface, for example. If you're interested, take a look at the sample code behind the Cluster and Local buttons on the SpotCollector tab on the Main window of the DXLabTest application, available via

<https://www.dxlabsuite.com/Interoperation.htm>

         73,

                Dave, AA6YQ

 

 

 

 

Re: Flex Radio Spots issue

Mark Hanson
 

= W3II comments below
+ AA6YQ comment below

=The clear command is not necessary; each spot is / can be assigned a lifetime then when expired will delete.
+ It is necessary to remove all callsigns when changing bands.
= Individually managing your spots or letting them timeout are viable options; changes to spots are easily tracked

=Clearing all spots should not be done as it assumes you are the only spot generator.
+ It is unreasonable to have more than one application rendering callsigns on a Flex panadaptor. The color schemes used will vary from application to application, as will the behavior when clicked.
= I believe this is where we disagree; I have encountered many flex radio users that use multiple spot sources. Spot color and behavior is / can be controlled on a per spot basis allowing for these scenarios.

+ Users can configure Commander to not render callsigns on the panadaptor. I hope FRStack offers a similar option.
= FRStack spot feature are and have always been optional; FRStack is a widely popular companion application for the Flex Signature Series Radios that adds MRU band stacking memories, memories, memory scanning, squelch, remote operation via SmartLink and many other features.

= Thank you for your time; I will add logic to detect errant spot removal then recover accordingly