Re: Winwarbler Settings
Dave AA6YQ
+ AA6YQ comments below
Over the last couple of weeks when starting Winwarbler (9.2.9) I have found randomly it has "lost" the QSO Info settings. It becomes evident because I have initialise RST items to 59/599 checked and when I log the first QSO the fields are empty. Then upon checking I find all the checkboxes in the Log>>QSO info section are cleared (blank). Today when I started Winwarbler I got a warning message that the Xcvr Mode for RTTY AFSK was not set (it had been previously). This field was also cleared and again when checking the QSO info section was also all blank. It is no hassle to redo the settings but I wonder if there is an underlying reason - probably more Windows related than Winwarbler? + Like all DXLab applications, WinWarbler stores its settings in the Windows Registry. If over the past few weeks you've suddenly started seeing settings changes that you didn't make, I suggest examining the Windows event logs for hardware and software error reports. 73, Dave, AA6YQ
|
|
Winwarbler Settings
Over the last couple of weeks when starting Winwarbler (9.2.9) I have found randomly it has "lost" the QSO Info settings. It becomes evident because I have initialise RST items to 59/599 checked and when I log the first QSO the fields are empty. Then upon checking I find all the checkboxes in the Log>>QSO info section are cleared (blank).
Today when I started Winwarbler I got a warning message that the Xcvr Mode for RTTY AFSK was not set (it had been previously). This field was also cleared and again when checking the QSO info section was also all blank. It is no hassle to redo the settings but I wonder if there is an underlying reason - probably more Windows related than Winwarbler? 73 David A92ge
|
|
updated eQSL AG and LoTW databases are available ...
Dave AA6YQ
...via the Databases tab on DXView's Configuration window.
73, Dave, AA6YQ
|
|
Re: WinWarbler macro CW message length
Dave AA6YQ
+ AA6YQ comments below
I just started using WinWarbler and tried defining a macro to send a CW message. It works fine as long as the message is less than about 45 characters. If I execute a macro with a longer CW message I get an error message "Commander: Transceiver command rejected" and it stops sending after about 45 characters. + So that I can see what's going on, please do the following: 1. on the General tab of Commander's Configuration window, check the "log debugging info" box 2. terminate Commander 3. start Commander 4. wait until Commander's Main window is displaying your IC-7300's frequency and mode 5. execute the WinWarbler macro that previously caused Commander to report "Transceiver command rejected" 6. wait for the "Transceiver command rejected" message to appear 7. on the General tab of Commander's Configuration window, uncheck the "log debugging info" box 8. attach the errorlog.txt file from your Commander folder to an email message, and send the message to me via aa6yq (at) ambersoft.com 73, Dave, AA6YQ
|
|
WinWarbler macro CW message length
Andy - K0AF
I just started using WinWarbler and tried defining a macro to send a CW message. It works fine as long as the message is less than about 45 characters. If I execute a macro with a longer CW message I get an error message "Commander: Transceiver command rejected" and it stops sending after about 45 characters. My transceiver is IC-7300. For CI-V command 17 (send CW message) the user manual says "Up to 30 characters".
How do I program a WW macro to send a message longer than 45 characters? I'm sure the answer is in the Commander or WW help file but I haven't found it. Thanks! Andy K0AF
|
|
Re: Incorrect myQTH ID error when uploading to eQSL
Al Rusnak
Thanks. That worked.
toggle quoted messageShow quoted text
Al, KE6JAC
-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ Sent: Sunday, August 30, 2020 6:21 PM To: DXLab@groups.io Subject: Re: [DXLab] Incorrect myQTH ID error when uploading to eQSL + AA6YQ comments below Sorry. I looked and confirmed, but did not put the response in. Yes, the box is checked. + That's why DXKeeper is using KE6JAC as your eQSL Nickname. Uncheck that box. 73, Dave, AA6YQ
|
|
Re: Incorrect myQTH ID error when uploading to eQSL
Dave AA6YQ
+ AA6YQ comments below
Sorry. I looked and confirmed, but did not put the response in. Yes, the box is checked. + That's why DXKeeper is using KE6JAC as your eQSL Nickname. Uncheck that box. 73, Dave, AA6YQ
|
|
Re: Incorrect myQTH ID error when uploading to eQSL
Al Rusnak
Sorry. I looked and confirmed, but did not put the response in.
toggle quoted messageShow quoted text
Yes, the box is checked. Al, KE6JAC
-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ Sent: Sunday, August 30, 2020 5:59 PM To: DXLab@groups.io Subject: Re: [DXLab] Incorrect myQTH ID error when uploading to eQSL + AA6YQ comment sbelow The QTH nickname within DXLab is "Home". The QTH nickname within eQSL is also "Home". This what I've used for several months now. + On the eQSL tab of DXKeeper's "QSL Configuration" window, is the "Use each QSO's myQTHID as its QTH Nickname when uploading or exporting" option enabled? 73, Dave, AA6YQ
|
|
Re: Incorrect myQTH ID error when uploading to eQSL
Dave AA6YQ
+ AA6YQ comment sbelow
The QTH nickname within DXLab is "Home". The QTH nickname within eQSL is also "Home". This what I've used for several months now. + On the eQSL tab of DXKeeper's "QSL Configuration" window, is the "Use each QSO's myQTHID as its QTH Nickname when uploading or exporting" option enabled? 73, Dave, AA6YQ
|
|
Re: Incorrect myQTH ID error when uploading to eQSL
Al Rusnak
The QTH nickname within DXLab is "Home". The QTH nickname within eQSL is
toggle quoted messageShow quoted text
also "Home". This what I've used for several months now. Thanks, Al, KE6JAC
-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ Sent: Sunday, August 30, 2020 5:21 PM To: DXLab@groups.io Subject: Re: [DXLab] Incorrect myQTH ID error when uploading to eQSL + AA6YQ comments below Trying to upload qso info to eqsl and LotW. No problem with LotW, but error when doing so with eqsl. I've used this for several thousand uploads in the past, so I know that the system should work. Details 1. Add Needed: Get the list of QSLs to be uploaded as shown below. This is only the first few. 2. Upload to eqsl: Get the error message stating "Error: No match on APP_EQSL_QTH_NICKNAME: ke6jac" I have my QTH ID specified as "KE6JAC", i.e. all upper caps. Not sure if this makes a difference. I cannot find anywhere where I use the lower case name,( i.e. would change the information if I could find a place to edit it.) If I look at the specific QSO, all QTH ID information is "KE6JAC", i.e. upper case. So, I would like to change the nickname so either DXLab and/or eQSL are happy, but don't know what is wanted or where to go to change it. I even tried searching for "ke6jac", but could not get any positive results. + Your "QTH Nickname" is specified on the eQSL tab of DXKeeper's "QSL Configuration" window. + On that same tab, there is a "Use each QSO's myQTHID as its QTH + Nickname when uploading or exporting" option. If you enable this option, then when sending a QSO to eQSL, DXKeeper will use the QSO's myQTHID as its nickname. + I suggest that you start by determining what QTH Nicknames you've established with eQSL. 73, Dave, AA6YQ
|
|
Re: Incorrect myQTH ID error when uploading to eQSL
Dave AA6YQ
+ AA6YQ comments below
Trying to upload qso info to eqsl and LotW. No problem with LotW, but error when doing so with eqsl. I've used this for several thousand uploads in the past, so I know that the system should work. Details 1. Add Needed: Get the list of QSLs to be uploaded as shown below. This is only the first few. 2. Upload to eqsl: Get the error message stating "Error: No match on APP_EQSL_QTH_NICKNAME: ke6jac" I have my QTH ID specified as "KE6JAC", i.e. all upper caps. Not sure if this makes a difference. I cannot find anywhere where I use the lower case name,( i.e. would change the information if I could find a place to edit it.) If I look at the specific QSO, all QTH ID information is "KE6JAC", i.e. upper case. So, I would like to change the nickname so either DXLab and/or eQSL are happy, but don't know what is wanted or where to go to change it. I even tried searching for "ke6jac", but could not get any positive results. + Your "QTH Nickname" is specified on the eQSL tab of DXKeeper's "QSL Configuration" window. + On that same tab, there is a "Use each QSO's myQTHID as its QTH Nickname when uploading or exporting" option. If you enable this option, then when sending a QSO to eQSL, DXKeeper will use the QSO's myQTHID as its nickname. + I suggest that you start by determining what QTH Nicknames you've established with eQSL. 73, Dave, AA6YQ
|
|
Re: SOLVED: JTAlert logging to DXKeeper stopped working
Catherine James
Upgrading JTAlert to 2.16.13 solved this problem.
|
|
Incorrect myQTH ID error when uploading to eQSL
Al Rusnak
Trying to upload qso info to eqsl and LotW. No problem with LotW, but error when doing so with eqsl. I’ve used this for several thousand uploads in the past, so I know that the system should work.
Details 1. Add Needed: Get the list of QSLs to be uploaded as shown below. This is only the first few. 2. Upload to eqsl: Get the error message stating “Error: No match on APP_EQSL_QTH_NICKNAME: ke6jac”
I have my QTH ID specified as “KE6JAC”, i.e. all upper caps. Not sure if this makes a difference. I cannot find anywhere where I use the lower case name,( i.e. would change the information if I could find a place to edit it.) If I look at the specific QSO, all QTH ID information is “KE6JAC”, i.e. upper case.
So, I would like to change the nickname so either DXLab and/or eQSL are happy, but don’t know what is wanted or where to go to change it. I even tried searching for “ke6jac”, but could not get any positive results.
Thanks, Al, KE6JAC
<HTML> <HEAD></HEAD> <BODY> <B> <a href="http://www.eqsl.cc">eQSL.cc</a> Problem Report @ 8/30/2020 22:57</B> <HR> 3D2AG at 8/27/2020 5:52:00 AM on 40M FT8 - Error: No match on APP_EQSL_QTH_NICKNAME: ke6jac <HR> 6E6E at 8/27/2020 5:50:15 AM on 40M FT8 - Error: No match on APP_EQSL_QTH_NICKNAME: ke6jac <HR> AA1UY at 6/28/2005 3:57:00 AM on 40M CW - Error: No match on APP_EQSL_QTH_NICKNAME: ke6jac <HR>
|
|
Re: Commander : slider command help pse
F5PHW Phil BERGER
Dave
Tnx again for quick answer. It works ! MG000 turns K3 MIC LEVEL to 000 and MG050 to 050. But there is no info of new value on the K3. When changing OUTPUT POWER or CW SPEED with Commander slider, we can see the new value on the K3 panel during 1 second. But, strangely, when changing MIC LEVEL, there is no info on the K3 like for OUTPUT POWER or CW SPEED. If we turn slowly the mic level potentiometer on the K3, we can see that the new value is ok. But never mind. It works for MIC LEVEL. I try also to command with slider the LINE LEVEL but did not find the right command for the K3. If anyone has info ... Many tnx Dave for help. Best 73 F5PHW Phil Web page on http://f5phw.free.fr F5PHW on FACEBOOK : https://www.facebook.com/phil.berger.75 WX in Nostang : http://www.nostang.meteoamikuze.com/index.html https://www.wunderground.com/personal-weather-station/dashboard?ID=IBRETAGN147 ----- Mail original ----- De: "aa6yq" <aa6yq@ambersoft.com> À: "DXLab" <DXLab@groups.io> Envoyé: Dimanche 30 Août 2020 22:18:44 Objet: Re: [DXLab] Commander : slider command help pse + AA6YQ comments below Tnx for your answers. It works now for CW SPEED. Great. Tnx But impossible to command MIC GAIN. In the "Commander User Slider" window, I have : - Lower bound : 0 - Upper bound : 60 - Small step : 1 - Big step : 5 - Label : GAIN MICRO <value> - Function : MIC LEVEL - Command : 'MG<D3>; - Initialize radio : yes I stopped and started Commander, also the K3, but no effect. I tried in SSB mode, DATA mode. Any idea ? + Take a look at <https://www.dxlabsuite.com/commander/Help/MonitoringMessages.htm> + Temporarily uncheck the Continuous box in the Interrogation panel. + Then try using the "Execute CAT Command" panel on Commander's Messages window to issue the following CAT commands: 'MG000; 'MG050; + Do these commands change your K3's microphone gain? If not, what response to these commands do you see from the K3 in the captured messages above the "Execute CAT Command" panel? + When you're done, check the Continuous box in the Interrogation panel. 73, Dave AA6YQ
|
|
Re: QRZ/PF question
George Steube
Thanks Dave.
toggle quoted messageShow quoted text
That password has been in PF for 15+ years and has never been touched, interesting. I will type it in again and see what happens. 73, George W2GS
On 8/30/2020 2:41 PM, Dave AA6YQ wrote:
Thanks for the errorlog, George. Here's what it shows:
|
|
Re: Install/Config DXLab for WSJT-X; Config SpotCollector's steps# 3a, 3b, 3c.
Dave AA6YQ
+ AA6YQ comments below
Subject: [DXLab] Install/Config DXLab for WSJT-X; Config SpotCollector's steps# 3a, 3b, 3c. I don't understand how to "add a column". + Each of those three steps suggests adding a column to SpotCollector's Spot Database Display to make specific information easily visible: --------------------------- 3. In the Layout panel on the Configuration window's Spot Database Display tab 3a. If you are pursuing awards based on primary administrative subdivisions (e.g. US States, Canadian Provinces, Russian Oblasts), add a column to the Spot Database Display for the Primary field 3b. To see the SNR most recently decoded by WSJT-X, add a column to the Spot Database Display for the ActualSNR field 3c. To see the smallest and largest SNRs decoded by WSJT-X, add columns to the Spot Database Display for the ActualSNRMin and ActualSNRMax fields, respectively --------------------------- + In each of instructions 3a, 3b, and 3c, the words "add a column to the Spot Database Display" are hyperlinked to this article <https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFormat> + which provides a screen shot showing the Spot Database Display, along with an explanation as to how to add new columns. I've looked at the Help section but, at this point, I'm in "mental overload". + Time to take a break, then. + If you haven't been using SpotCollector, then after your break I suggest reviewing <https://www.dxlabsuite.com/dxlabwiki/CollectingSpots> + and getting comfortable with how it works. + Take your time, and post questions here as you encounter them. 73, Dave, AA6YQ
|
|
Install/Config DXLab for WSJT-X; Config SpotCollector's steps# 3a, 3b, 3c.
Jerome Sodus
Hello,
|
|
Re: Commander : slider command help pse
Dave AA6YQ
+ AA6YQ comments below
Tnx for your answers. It works now for CW SPEED. Great. Tnx But impossible to command MIC GAIN. In the "Commander User Slider" window, I have : - Lower bound : 0 - Upper bound : 60 - Small step : 1 - Big step : 5 - Label : GAIN MICRO <value> - Function : MIC LEVEL - Command : 'MG<D3>; - Initialize radio : yes I stopped and started Commander, also the K3, but no effect. I tried in SSB mode, DATA mode. Any idea ? + Take a look at <https://www.dxlabsuite.com/commander/Help/MonitoringMessages.htm> + Temporarily uncheck the Continuous box in the Interrogation panel. + Then try using the "Execute CAT Command" panel on Commander's Messages window to issue the following CAT commands: 'MG000; 'MG050; + Do these commands change your K3's microphone gain? If not, what response to these commands do you see from the K3 in the captured messages above the "Execute CAT Command" panel? + When you're done, check the Continuous box in the Interrogation panel. 73, Dave AA6YQ
|
|
Re: Commander : slider command help pse
F5PHW Phil BERGER
Dave and Matthias Tnx for your answers. It works now for CW SPEED. Great. Tnx But impossible to command MIC GAIN. In the "Commander User Slider" window, I have : - Lower bound : 0 - Upper bound : 60 - Small step : 1 - Big step : 5 - Label : GAIN MICRO <value> - Function : MIC LEVEL - Command : 'MG<D3>; - Initialize radio : yes I stopped and started Commander, also the K3, but no effect. I tried in SSB mode, DATA mode. Any idea ? Anyone on this list succeed in command MIC GAIN with Commander ? Many tnx 73 F5PHW Phil De: "aa6yq" <aa6yq@...> À: "DXLab" <DXLab@groups.io> Envoyé: Dimanche 30 Août 2020 21:30:56 Objet: Re: [DXLab] Commander : slider command help pse + AA6YQ comments below The <D3> is a format placeholder. It means, that the position of the + Correct. Elecraft's documentation for the "Mic Gain" command is SET/RSP format: MGxxx; where xxx is 000-060. + That means the slider value must be inserted into the command as a 3-digit number. The mechanism for inserting the slider value into a command is called a "Substitution String", and is documented here: <https://www.dxlabsuite.com/commander/Help/CommandSequences.htm#Substitution%20strings> + As you can see, <D3> is replaced by the slider's value represented as 3 unsigned decimal digits. The slider's lower bound should be set to 0, and its upper bound should be set to 60. If the Mic Gain slider command is specified as 'MG<D3>; + and you change the slider value to 25, then what will be sent to the radio is MG025;
+ The Keyer Speed command is documented as SET/RSP format: KSnnn; where nnn is 008-050 (8-50 WPM). + Like the MG command, the slider value should be presented with 3 decimal digits, with the lower-bound set to 8 and the upper bound set to 50. 'KS<D3>; 73,
|
|
Re: QRZ/PF question
Dave AA6YQ
Thanks for the errorlog, George. Here's what it shows:
2020-08-30 14:15:27.489 > PathfinderForm.CompleteQRZLoginPhase2: login failed: invalid password That means an incorrect password is specified in the "QRZ.com Online Callbook" panel on Pathfinder's Configuration window. 73, Dave, AA6YQ
|
|