The contest itself runs from 25 Jan 2200 UTC to 26 Jan 1000 UTC and is open to world participants. I competed and went to create my Cabrillo file and got that message. So of I went with my ADIF and imported it into N1MM and sent it off.
Hi David,
I'm a long-time N1MM user. Typically more than a dozen fairly mainstream contests a year, all supported by N1MM. Although I've never needed it, N1MM does have the option of user-defined contests (UDF). I suggest you study the N1MM doc on that, and ask on the N1MM reflector if you need help. And I think VE3KI monitors this and other reflectors as a member of the N1MM team, and answers a lot of questions.
I will begin with "DXLabs does not support xxxxxxxx" and the x's in my case was the WIA Australia Day contest. The contest itself runs from 25 Jan 2200 UTC to 26 Jan 1000 UTC and is open to world participants. I competed and went to create my Cabrillo file and got that message. So of I went with my ADIF and imported it into N1MM and sent it off. Not being the quickest but having a good understanding, it still took me best part of a day to do all this. Is there a simple way to add user templates to the Cabrillo creator or if supplied with the appropriate UDF files for N1MM, have them included in the contest listing.
+ No. Cabrillo is far too complex for that.
I was exclusively DX Labs Suite until I had to do this.
Another possibility to add an Access Database where these can be user added.
I will begin with "DXLabs does not support xxxxxxxx" and the x's in my case was the WIA Australia Day contest. The contest itself runs from 25 Jan 2200 UTC to 26 Jan 1000 UTC and is open to world participants. I competed and went to create my Cabrillo file and got that message. So of I went with my ADIF and imported it into N1MM and sent it off.? Not being the quickest but having a good understanding, it still took me best part of a day to do all this. Is there a simple way to add user templates to the Cabrillo creator or if supplied with the appropriate UDF files for N1MM, have them included in the contest listing. I was exclusively DX Labs Suite until I had to do this. Another possibility to add an Access Database where these can be user added. Cheers
On 29/01/2025 5:08 pm, Dave AA6YQ via
groups.io wrote:
2. on the
Properties window's Compatibility tab, uncheck the "Run as
administrator" box
In addition, check the properties of the
launcher exe file referenced by the shortcut, it may have run as
admin enabled despite not being enabled in the shortcut.
Thanks all; I couldn't figure out how to turn off DXLab Launcher (I think) running in Administrator mode, so i just told TQSL to always run in Administrator mode, and it seems to be working okay.
I have two stations I keep logs for. Both are set up with DXLAB. The first station is my home station, the second station is my vacation station in ZF. I Currently use lotw with the home station,. I would like to use lotw with the ZF station. What is the best process for handling both logs and lotw?
+ Your QSOs made from the continental US and your QSOs made from ZF should be maintained in separate log files, with separate default station callsigns.
+ You will need separate LoTW "Station Callsigns" and "Station Locations"
On Jan 28, 2025, at 19:54, Stan Burks via groups.io <n5ue@...> wrote:
I have two stations I keep logs for. Both are set up with DXLAB. The first station is my home station, the second station is my vacation station in ZF. I Currently use lotw with the home station,. I would like to use lotw with the ZF station. What is the best process for handling both logs and lotw?
I have two stations I keep logs for. Both are set up with DXLAB. The first station is my home station, the second station is my vacation station in ZF. I Currently use lotw with the home station,. I would like to use lotw with the ZF station. What is the best process for handling both logs and lotw?
Found one interesting moment- returning to data only from SSB and? RTTY, staying at AM, FM and CW modes.? Changing to longer command intervals does not helped. Later will test CI-V messages.
Thanks, Dave. You are always a step ahead. I looked at the Radio panel several times and never noticed the drop-down menu. I guess I just saw the RTTY sub-mode and quit looking. My K4 has many options available including FT8.
On Jan 28, 2025, at 17:57, Dave AA6YQ via groups.io <aa6yq@...> wrote:
+ 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.
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"?
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.
+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.
On Jan 28, 2025, at 16:31, Joe Subich, W4TV via groups.io <lists@...> wrote:
What mode did you select in the Log QSOs display? ?When manually 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??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. 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
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:
What mode did you select in the Log QSOs display? When manually 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.
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. 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
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?
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. ?
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?
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.
On Tue, Jan 28, 2025 at 12:04?PM Joe Subich, W4TV via <lists=[email protected]> wrote:
Is DXKeeper running in administrator mode?? If so, remove the
run as administrator permission.
73,
? ? ... Joe, W4TV
On 2025-01-28 11:29 AM, David Reed via 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.
>
> 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:
>
>? ?? Exit TQSL so I can re-run as a normal user
>? ?? Allow TQSL to continue this time.
>? ?? Always allow running as Administrator
>
> 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
>
--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA