Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
Re: Commander Configuration not recognizing K3
+ AA6YQ comments below
That fixed the problem and Commander starts up fine. However, the frequency indicator shows all 0's, which means that while the K3 on Port 5 is apparently communicating with Commander, the frequency is not being passed. + Is "Port 5" the COM port to which your K3 is connected? + If so, is Commander configured to communicate with your K3 via COM5? + What leads to conclude that " Port 5 is apparently communicating with Commander"? - does Commander track your K3's frequency? - can Commander set your K3's frequency? - does Commander track your K3's mode? - can Commander set your K3's mode? - can Commander switch your K3 between RX an TX? 73, Dave, AA6YQ |
|
Re: Mode Shows RTTY instead of FT8
+ AA6YQ comments below
Now that I think about it, it doesn¡¯t make sense to read a definition file. I¡¯m not sure what I was thinking, but it would be nice if there were a way to set a default mode when the radio is set to data. + Depending upon the transceiver being controlled, the Radio panel on the General tab of Commander's Configuration window provides one of 3 selectors populated with the modes specified in DXKeeper's Modes.txt file if present, or its DefaultModes.txt file: "Log Mode for Data-L or Data-U" - transceivers for which Commander provides a Data-L or Data-U mode "Log Mode for PKT or PKT-R" - transceivers for which Commander provides a PKT or PKT-R mode "Log Mode for DIGL or DIGU" - Flex Signature 6000 Series The selector specifies the "mode to be logged" that is conveyed to other applications. 73, Dave, AA6YQ |
|
Re: Mode Shows RTTY instead of FT8
¿ªÔÆÌåÓý+I did not select any mode initially. ?I thought DXKeeper would set the correct mode based on the frequency. ?When I first select NEW to entire a QSO all fields are blank until I hit enter then it does the QRZ lookup, populates the frequency, and fills in the mode with RTTY.After doing more playing I see DXKeeper is using the mode the radio is set to. ?I can have the radio set to 28074 and the radio set to CW, and DXKeeper logs it as CW. ?Set the radio to USB, and it gets logged as SSB. ?Set it to DATA or PSK, and it logs as RTTY. ?So it seems any data mode gets logged as RTTY. Now that I think about it, it doesn¡¯t make sense to read a definition file. ?I¡¯m not sure what I was thinking, but it would be nice if there were a way to set a default mode when the radio is set to data. ?Given the popularity of FT*, ?I¡¯m sure a lot more contacts are made on FT* than RTTY. Tom-KQ5S
--
Tom-KQ5S |
|
Re: Automatic mode change to data
+ AA6YQ comments below
Hello. After playing hard with settings, changed something, now when setting to LSB or USB mode, mode automaticaly reverts to Data-L or Data-U. It hapens when changing mode either from transceiver or commander. When all programs closed, transceiver works normaly. And if only run commander happens mode autochange. Where to dig?1. 10 ms is fast for a Command Interval; try backing it off to 25 ms 2.? use Commander's "Messages" window to see the CI-V commands being sent to the transceiver, and its responses: ?
? ? 73, ? ? ? ? ?Dave, AA6YQ |
|
Re: Mode Shows RTTY instead of FT8
What mode did you select in the Log QSOs display? When manually
toggle quoted message
Show quoted text
entering QSOs in DXKeeper's Log QSOs tab, I have to enter the mode as the field remains blank otherwise. DXKeeper does not read SpotCollector's Sub-Band Definition file and has no comparable configuration file. 73, ... Joe, W4TV On 2025-01-28 4:49 PM, TOM-KQ5S via groups.io wrote:
I normally use JTAlert but on occasion, I need to manually enter a QSO. ? I'll set the radio to the FT8 frequency and mode (DATA) and enter the callsign in DXKeeper's Log QSO's tab and hit the TAB key. ?I'll then manually change the begin and end dates to match the missed QSO's date/time but the mode is set to RTTY. |
|
Re: Automatic mode change to data
¿ªÔÆÌåÓýWhat radio?? What frequency is the Radio set to? ?If on an WSJTX mode frequency, then try setting the radio to a SSB frequency. ? 73, Dave, w6de ? From: [email protected]
<[email protected]> On Behalf Of drone777 via groups.io
Sent: 28 January, 2025 20:30 To: [email protected] Subject: [DXLab] Automatic mode change to data ? Hello. After playing hard with settings, changed something, now when setting to LSB or USB mode, mode automaticaly reverts to Data-L or Data-U. It hapens when changing mode either from transceiver or commander. When all programs closed, transceiver works normaly. And if only run commander happens mode autochange. Where to dig? |
|
Mode Shows RTTY instead of FT8
I normally use JTAlert but on occasion, I need to manually enter a QSO. ? I'll set the radio to the FT8 frequency and mode (DATA) and enter the callsign in DXKeeper's Log QSO's tab and hit the TAB key. ?I'll then manually change the begin and end dates to match the missed QSO's date/time but the mode is set to RTTY.
?
For example, I have the radio set to 28.074. ?I log an FT8 contact directly in DXKeeper's Log QSO's tab. ?The mode shows as RTTY. ?WinWarbler is not running.
?
This is from my BandModes 2022-12-06.txt file. ?SpotCollector's Sub-band Definition is set to this file. ?
28070,28074,PSK31,10M
28074,28077,FT8,10M 28077,28078,JT9,10M 28078,28080,JT65,10M 28080,28100,RTTY,10M ?
Why is it not showing as FT8? ?The Log QSO window shows the correct frequency.
--
Tom-KQ5S |
|
Automatic mode change to data
Hello. After playing hard with settings, changed something, now when setting to LSB or USB mode, mode automaticaly reverts to Data-L or Data-U. It hapens when changing mode either from transceiver or commander. When all programs closed, transceiver works normaly. And if only run commander happens mode autochange. Where to dig? |
|
Re: LoTW tries to launch in administrator mode
Joe's right - DXKeeper is running as administrator and passing that on to TQSL. If you ALWAYS run that way - Launcher running as Administrator, and any time you run TQSL you run it as administrator as well, then there won't be any issues. But running sometimes as Administrator and sometimes not means that the data that TQSL is using may not be visible to both ways that TQSL is being run. 73, ? ? -Rick On Tue, Jan 28, 2025 at 12:04?PM Joe Subich, W4TV via <lists=[email protected]> wrote:
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA |
|
Re: LoTW tries to launch in administrator mode
Is DXKeeper running in administrator mode? If so, remove the
toggle quoted message
Show quoted text
run as administrator permission. 73, ... Joe, W4TV On 2025-01-28 11:29 AM, David Reed via groups.io wrote:
I have recently sustained a PC crash and am trying to get things running; I will be addressing one issue at a time, to try to minimize my confusion. |
|
LoTW tries to launch in administrator mode
¿ªÔÆÌåÓýI have recently sustained a PC crash and am trying to get things running; I will be addressing one issue at a time, to try to minimize my confusion. Running Windows 10 (As it used to pre-crash). When dxk launches, it tries to launch TQSL (as selected), but for some reason, it tries to run it in administrator mode, I get a pop up window titled Administrator Error, which gives me 3 choices:
So I select the first option. Oddly enough, if I just click on the TQSL icon on my desktop, it launches with no complaints. Any ideas what is going on and how to fix it would be greatly appreciated. Thanks & 73 de W5SV, Dave
|
|
Re: spotcollector 60M issue
+ AA6YQ comments below
+ DXLab's Realtime Award Tracking does support the pursuit of DX Marathon and WPX on 60m. If you've enabled either of those but SpotCollector isn't flagging a 60m Spot Database Entry as "needed" for one of those awards - but should be doing so - then right-click the Entry and choose "Display award tracking for..." from the popup menu. A small window will appear whose contents explain why the Entry is not considered "needed". ? ? ? ?73, ? ? ? ? ? ? ? ?Dave, AA6YQ |
|
Re: spotcollector 60M issue
On 2025-01-28 10:16 AM, k9us via groups.io wrote:
I must have something not set to allow NEEDED dx to be spotted on 60M.By definition, 60M cannot be needed since DXCC does not recognize/accept QSOs made on 60M. As Dave has stated many times, as long as 60M is not accepted by ARRL DXLab will not support 60M (no highlighting, no alerts, no inclusion in DXCC RAT). 60M is also not supported for WAS, WPX or WAZ as those award programs also do not recognize 60M. *HOWEVER 60M IS supported* for DX Marathon. 73, ... Joe, W4TV On 2025-01-28 10:16 AM, k9us via groups.io wrote: Hi |
|
Re: spotcollector 60M issue
Tim, Contacts made in the 60 m band are not valid for any ARRL award and will not show as needed. Robie AJ4F On Tue, Jan 28, 2025 at 9:16?AM k9us via <k9us73=[email protected]> wrote:
|
|
spotcollector 60M issue
Hi
I must have something not set to allow NEEDED dx to be spotted on 60M.
I see spots on 60M but when one I need is spotted, its not being spotted as needed.
I have the 60M band enabled and I do see 60M spots but this morning I saw 2 countries
I need spotted but did not get an alert.
?
I also tried testing by spotting them via local, I see my spot (local) but no alert.
?
Tim K9US
?
? |
|
Re: Commander Configuration not recognizing K3
That fixed the problem and Commander starts up fine. ? However, the frequency indicator shows all 0's, which means that while the K3 on Port 5 is apparently communicating with Commander, the frequency is not being passed. ?What am I missing?
?
Sorry to be a pest.
?
Jim
? |
|
Re: Xiegu in commander
Setting address different from 0xA4 and with set "verify CI-V command acceptance" does either long delays when changing frequency or no response at all (I.e. address A3 does not work at all). When set as radio IC-705 and address A4, command interval can be set at 10ms and works flawlessly.
X6200 FW v1.0.6. |
|
Re: CTL/Lotw
Dave - You pointed out that on the AWARDS panel of DXK I had checked that I was chasing ALL entities on FT8. That was an error on my part... all I really wanted was to make sure if a country I needed for CHALLENGE was on FT8 I did not want to miss it. I must have set that a long time ago, and now realize that is not what I intended. I unchecked the FT8 box in the DXCC Bands & Modes section of the AWARDS tab, and all is now normal. Thanks again for your great software, and incomparable support, Dave - K9FN On Mon, Jan 27, 2025 at 12:47?PM Dave AA6YQ via <aa6yq=[email protected]> wrote: + AA6YQ comments below |
David Bunte
to navigate to use esc to dismiss