Date   

Re: Feature Request:-- Commander Memories

Dave AA6YQ
 

+ AA6YQ comments below
Would itbe possible to ask for a feature request in COMMANDER?
What I'd like to see is the memories remembering which antenna to switch to. (Mine is an Icom IC-756 Pro 3),
This would be handy for when running transverters using the 10mtr band as an IF
+ You can do that now by employing a user-defined command sequence as a memory: have is set the desired frequency and mode, and issue the correct CI-V command to select the desired antenna.

        73,

              Dave, AA6YQ


Re: Spot collector random reset

Dave AA6YQ
 

+ AA6YQ comments below
Several times in the past week, when starting the DXLab suite (all modules except WinWarbler) a SpotCollector dialog box pops up asking that I enter my callsign. I do so and then find that the Spot Sources I have used previously have been reset to the factory defaults. After re-entering the sources I normally use, everything runs as expected. 
I'd like to understand why this occurs and how to fix it. All modules and databases are kept up-to-date.

+ The implication of that is that the entry in the Windows Registry that SpotCollector uses to store your callsign is being cleared or deleted. When this happens, are the rest of your SpotCollector settings intact, or must you recover them from your Workspace?

This also raises a question: I know I can backup my whole workspace, but is there a simple way to save only my choices of spot sources and then retrieve them if needed?

+ There is no partial or selective storage or recovery of settings store in a Workspace.  You could create several Workspaces, each with a different set of spot sources.

     73,

            Dave, AA6YQ

 


Re: Spot collector and bandwidth RTTY click on frequency

Ron T
 

DOn't see any "-" for LSB setting. Use the DATA_L instead?


Spot collector random reset

David Aslin
 

Several times in the past week, when starting the DXLab suite (all modules except WinWarbler) a SpotCollector dialog box pops up asking that I enter my callsign. I do so and then find that the Spot Sources I have used previously have been reset to the factory defaults. After re-entering the sources I normally use, everything runs as expected. 
I'd like to understand why this occurs and how to fix it. All modules and databases are kept up-to-date.
This also raises a question: I know I can backup my whole workspace, but is there a simple way to save only my choices of spot sources and then retrieve them if needed?
73, David G3WGN M6O


Re: Spot collector and bandwidth RTTY click on frequency

Ron T
 

So the Data_L needs to be included with the -2125 offset.


Re: Spot collector and bandwidth RTTY click on frequency

Ron T
 

N6ML....
you are correct....seems to depend a lot on listener who becomes the spotter....and I do mean bandspread window...mistaken to call it the bandwidth window since there isn't one of those. Tnx...just need some rtty signals now to play around with.


Re: Spot collector and bandwidth RTTY click on frequency

Joe Subich, W4TV
 

Set the mark offset to -2125, select AFSK LSB and set Xcvr Mode to
DATA_L.

73,

... Joe, W4TV

On 2021-02-15 2:15 PM, Ron T via groups.io wrote:
[Edited Message Follows]
Tnx Joe....I'll give that a try. Did some of the rtty contest over the weekend and it would have been slick to just click on the bandwidth window at the spots shown there and be on the station rather than trying to guess where that station would be by sliding the freq down some. I think the optimal setting for AFSK is set by default to 2210 and the mark offset at 0. I should set the mark offest at 2210 and -LSB?


Re: Spot collector and bandwidth RTTY click on frequency

iain macdonnell - N6ML
 

Hi Ron,

I think you mean the *bandspread* window?

It should be noted that click-to-QSY for RTTY spots is dependent on
the spotting station getting it right too. The convention amongst
"real RTTY ops" is to spot the mark frequency, but some "amateurs"
will spot their VFO frequency instead, so the spot will be off by the
amount of *their* tone offset (which you have no way of knowing).
Configured with the offsets for your setup, it should work at least
some (maybe most?) of the time, but not always.

73,

~iain / N6ML



On Mon, Feb 15, 2021 at 11:24 AM Ron T via groups.io
<flamateurradio=yahoo.com@groups.io> wrote:

[Edited Message Follows]

Tnx Joe....I'll give that a try. Did some of the rtty contest over the weekend and it would have been slick to just click on the bandwidth window at the spots shown there and be on the station rather than trying to guess where that station would be by sliding the freq down some. I think the optimal setting for AFSK is set by default to 2210 and the mark offset at 0. I should set the mark offest at 2125 and -LSB? I will give a try to this and see if it works as I expect. Tnx...73


Re: Spot collector and bandwidth RTTY click on frequency

Ron T
 
Edited

Tnx Joe....I'll give that a try. Did some of the rtty contest over the weekend and it would have been slick to just click on the bandwidth window at the spots shown there and be on the station rather than trying to guess where that station would be by sliding the freq down some. I think the optimal setting for AFSK is set by default to 2210 and the mark offset at 0. I should set the mark offest at 2125 and -LSB? I will give a try to this and see if it works as I expect. Tnx...73


Re: Spot collector and bandwidth RTTY click on frequency

Joe Subich, W4TV
 

Settings are "Mark Offset" and "Optimal Offset" in Winwarbler ->
Config -> RTTY.

Typically, if one is using "High tones" (2125 Mark, 2295 Space),
Optimal Offset would be 2210 ((Mark+Space)/2) and Mark Offset
would be *-*2125 (don't forget the - for LSB).

73,

... Joe, W4TV

On 2021-02-15 11:50 AM, Ron T via groups.io wrote:
I'm sure I've seen this topic before but didn't see a resolution to the question in the replies...
Using AFSK set to LSB with a 7300 and would like to click on the bandwidth or spot collector and have it come up with the freq I want instead of
compensating by dropping down about 2 kcs to actually find that station in the waterfall. .  I think there is a setting that compensates for
this but not sure which one it is n the configuration. Simply put, I want to click on the station in the bandwidth window (or spot collector) and find it there on the waterfall as well as xmit
for the qso.


Spot collector and bandwidth RTTY click on frequency

Ron T
 


I'm sure I've seen this topic before but didn't see a resolution to the question in the replies...

Using AFSK set to LSB with a 7300 and would like to click on the bandwidth or spot collector and have it come up with the freq I want instead of
compensating by dropping down about 2 kcs to actually find that station in the waterfall. .  I think there is a setting that compensates for 
this but not sure which one it is n the configuration. Simply put, I want to click on the station in the bandwidth window (or spot collector) and find it there on the waterfall as well as xmit 
for the qso.


Re: Exporting into SKCC logger

 

If you store the SKCC number in a DXLab user-defined field you can easily use ADIF Master to change the field name in the ADIF and the import is smooth. You can get ADIF Master here  - http://www.dxshell.com/adif-master.html

I do this in both directions to keep my SKCC and DXLab logs in sync. 

Bob AF9W


Re: Commander + JTDX CAT issues

Joe Subich, W4TV
 

On 2021-02-15 2:21 AM, Dave AA6YQ wrote:

+ Perhaps my characterization of JTDX as a hostile fork of WSJT-X is erroneous.
Your characterization is not erroneous. The developers of WSJT-X have,
on multiple occasions, objected to modifications in the decoding
algorithms made in JTDX.

73,

... Joe, W4TV


On 2021-02-15 2:21 AM, Dave AA6YQ wrote:
I have been using JTDX along with JTAlert and the DXLab Suite for several years, with no CAT issues - like WSJT-X, it offers Commander (and FLRig for that matter) as an option under the Radio selection. This has worked flawlessly for me - and I have the 2nd CAT port in Commander feeding an SDR with no problems. Bottom Line - any DXLab user should select Commander as the radio!!!
+ Thanks, Barry!
JTDX is a derivative focused purely on HF DX - all the VHF stuff is taken out, and the UI is designed for easier operation (I personally FAR prefer the JTDX UI, and I was an early adopter of the original WSJT back in 2001!!!)... also handles decodes a bit differently and has a much more refined (in my opinion at least) AutoSequencing methodology. Like WSJT-X, it requires operator intervention for logging (unlike the robotic function of WSJT-Z).
Not sure what a Hostile Fork is Dave?? Source code is available with every release, and the developers always abide by any requests made by the WSJT-X team.
+ A hostile fork is a fork unilaterally created without the approval of the original project. Barring a compelling rationale, hostile forks should be avoided, as they discourage developers from making their code available as open source.
+ The threat of a hostile fork is one of the reasons that DXLab is not an open source project.
+ Perhaps my characterization of JTDX as a hostile fork of WSJT-X is erroneous.
Dave, AA6YQ


Re: Bidirectional Rig Control

Norm - KC1BMD
 

While that might be the fundamental rule of this rig control application, it is clearly not the rule for all rig control applications.
--
73, Norm/KC1BMD


Feature Request:-- Commander Memories

Brian Bowers G0VAX
 

Hi ,

Would itbe possible to ask for a feature request in COMMANDER?
What I'd like to see is the memories remembering which antenna to switch to. (Mine is an Icom IC-756 Pro 3),
This would be handy for when running transverters using the 10mtr band as an IF

Best Wishes
Brian G0VAX


Re: Exporting into SKCC logger

Greg
 

Dave

From what I can see Rich is talking about importing an ADIF file from DXKeeper into SKCC logger. From the manual for SKCCLogger available at the skcc.com website (Page 30) the logger will add the SKCC number to an imported log - Tools - Add SKCC Numbers to Log.

Rich

I think that's all you need to do.

73

Greg VK3VT

On 15/02/2021 18:24, Dave AA6YQ wrote:
I was using DX Keeper and just wrote in the Comment column "SKCC and NR"

+ By "NR" do you mean a number, or the letter N followed by the letter R?

I do that so I know very easily what stations are SKCC.The help files were brief about ADIF files and nothing pertaining to importing,But I will check a little harder as there has to be something on importing.

+ The reference documentation for importing is here:

https://www.dxlabsuite.com/dxkeeper/Help/Import.htm

+ You can also access this information by clicking one of DXKeeper's Help buttons, and navigating to the "Importing ADIF and Tab-delimited Files" section.

+ Step-by-step instructions for importing QSOs are here:

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

73,

Dave, AA6YQ






Re: Exporting into SKCC logger

Dave AA6YQ
 

I was using DX Keeper and just wrote in the Comment column "SKCC and NR"

+ By "NR" do you mean a number, or the letter N followed by the letter R?

I do that so I know very easily what stations are SKCC.The help files were brief about ADIF files and nothing pertaining to importing,But I will check a little harder as there has to be something on importing.

+ The reference documentation for importing is here:

https://www.dxlabsuite.com/dxkeeper/Help/Import.htm

+ You can also access this information by clicking one of DXKeeper's Help buttons, and navigating to the "Importing ADIF and Tab-delimited Files" section.

+ Step-by-step instructions for importing QSOs are here:

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

73,

Dave, AA6YQ


Re: Commander + JTDX CAT issues

Dave AA6YQ
 

I have been using JTDX along with JTAlert and the DXLab Suite for several years, with no CAT issues - like WSJT-X, it offers Commander (and FLRig for that matter) as an option under the Radio selection. This has worked flawlessly for me - and I have the 2nd CAT port in Commander feeding an SDR with no problems. Bottom Line - any DXLab user should select Commander as the radio!!!

+ Thanks, Barry!

JTDX is a derivative focused purely on HF DX - all the VHF stuff is taken out, and the UI is designed for easier operation (I personally FAR prefer the JTDX UI, and I was an early adopter of the original WSJT back in 2001!!!)... also handles decodes a bit differently and has a much more refined (in my opinion at least) AutoSequencing methodology. Like WSJT-X, it requires operator intervention for logging (unlike the robotic function of WSJT-Z).

Not sure what a Hostile Fork is Dave?? Source code is available with every release, and the developers always abide by any requests made by the WSJT-X team.

+ A hostile fork is a fork unilaterally created without the approval of the original project. Barring a compelling rationale, hostile forks should be avoided, as they discourage developers from making their code available as open source.

+ The threat of a hostile fork is one of the reasons that DXLab is not an open source project.

+ Perhaps my characterization of JTDX as a hostile fork of WSJT-X is erroneous.

Dave, AA6YQ


Re: Commander + JTDX CAT issues

Barry Murrell ZS2EZ
 

I have been using JTDX along with JTAlert and the DXLab Suite for several years, with no CAT issues - like WSJT-X, it offers Commander (and FLRig for that matter) as an option under the Radio selection. This has worked flawlessly for me - and I have the 2nd CAT port in Commander feeding an SDR with no problems. Bottom Line - any DXLab user should select Commander as the radio!!!

JTDX is a derivative focused purely on HF DX - all the VHF stuff is taken out, and the UI is designed for easier operation (I personally FAR prefer the JTDX UI, and I was an early adopter of the original WSJT back in 2001!!!)... also handles decodes a bit differently and has a much more refined (in my opinion at least) AutoSequencing methodology. Like WSJT-X, it requires operator intervention for logging (unlike the robotic function of WSJT-Z).

Not sure what a Hostile Fork is Dave?? Source code is available with every release, and the developers always abide by any requests made by the WSJT-X team.

BTW, I also have WSJT-X installed, and when a new GA comes out (I avoid the RC versions) I run it for several days - always worth keeping an open mind!!

73 de BARRY MURRELL ZS2EZ
KF26ta - Port Elizabeth, South Africa
EPC#0558 DMC#1690 30MDG#4081
DXCC HONOR ROLL (332/340)
DXCC(mixed)#41,146 DXCC(RTTY)#1,916
DXCC(phone)#34,990 DXCC(CW)#11,714
DXCC 80m,40m,30m,20m,17m,15m,12m,10m 5BDXCC#8,916
WAS Triple Play #492 WAS(RTTY)#538 WAS(Digital)#163-Endorsements JT65,FT8
WAZ(RTTY)#185 WAE-I(mixed)#72 WAZS(mixed)#214 AAA#1569 SARL Top Band Award #120
AS ZR6DXB: VUCC(50MHZ)#1,334 UKSMG WAE(Silver)#75 UKSMG AFRICA#22 WAC (Satellite)
website : www.zs2ez.co.za

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Monday, 15 February 2021 00:04
To: DXLab@groups.io
Subject: Re: [DXLab] Commander + JTDX CAT issues

+ AA6YQ comments below

Other have reported difficulties when trying to use Commander with JTDX. It appears that the CAT interface on JTDX is intolerant to any serial port collisions. I've tried a number methods for multiple apps to access the CAT port on the K3 without success. I haven't used my K3 on FT8 for several months. I did not have this issue previously.

Has anyone come up with a stable solution?

Any assistance is greatly appreciated.

+ The only reliable way to enable multiple apps to simultaneously control the same transceiver is by developing a transceiver emulator that provides each client application with a dedicated virtual port that interacts with that emulator, and that keeps the emulated transceiver and physical transceiver in sync. That's how Commander's Secondary CAT port works (but it doesn't provide all of the functionality that JTDX requires), and that's how Tom VA2FSQ's Win4K3Suite works.

https://va2fsq.com/ultimate-control/

+ WSJT-X solves this problem by providing the option of using Commander for transceiver control. Does JTDX not provide that option? I've largely ignored JTDX because it is a hostile fork of the WSJT-X code.

73,

Dave, AA6YQ


Re: Exporting into SKCC logger

Rich KB1FGC <marzo7088@...>
 

I was using DX Keeper and just wrote in the Comment  column "SKCC and NR" I do that so I know very easily what stations are SKCC.The help files were brief about ADIF files and nothing pertaining to importing,But I will check a little harder as there  has to be something on importing.
Thanks

4801 - 4820 of 204546