|
|
Post by Glenn KD0Q on Feb 18, 2023 16:39:48 GMT
It appears that JTDX hijacks my XCVR. After using JTDX in FT8 and without closing the JTDX application, I can move the XCVR to CW frequency and change to CW mode. All is OK. If I enable Split operation on the XCVR, JTDX changes the XCVR to DATA mode. The only way I can operate the XCVR in CW Split mode is to exit JTDX.
JTDX v2.2.159
Windows 10 Pro 19044.2604 Elecraft K3 w/KIO3B
Any ideas?
Thanks, Glenn - KD0Q
|
|
|
|
Post by Wolfgang OE1MWW on Feb 18, 2023 16:56:22 GMT
Glenn, I would not consider this as 'hijacking', it's just a normal rig control by JTDX. In 'File' 'Settings' 'Radio' you can see a setting right beside the Rig Type, labled 'polling'. JTDX will request and set control of your rig every time cycle set in 'polling'. If you change the mode or split, JTDX will set it back according to the settings entry. As long as the task of JTDX is active, it will control the rig.
Unfortunately this rule does not apply exactly to every rig, there are zillion of different
rigs on the market, core control is the 'Hamlib' library included in JTDX.
73's de OE1MWW Wolfgang |
|
|
|
Post by Glenn KD0Q on Feb 18, 2023 18:22:53 GMT
Wolfgang,
I don't think this is a function of the polling. JTDX only changes the mode back when I enable Split on the XCVR.
This doesn't happen in JTDX v2.2.156.
Glenn - KD0Q
|
|
|
|
Post by Wolfgang OE1MWW on Feb 18, 2023 19:17:42 GMT
This doesn't happen in JTDX v2.2.156.
156 and 159 using different versions of Hamlib. As long as the JTDX task is active, it may control your rig. If you set split on K3, the K3 send info to Hamlib -> JTDX and JTDX can react. JTDX, like in WSJT-X - think it's even mentioned somewhere in the manual: don't change any settings in your rig, as long as the main task = JTDX is active.
73's de OE1MWW Wolfgang
|
|
|
|
Post by Arvo ES1JA on Feb 18, 2023 19:20:24 GMT
Yeahh, jtdx-s fault is that it allows You change mode to CW when jtdx is still running. Simply close jtdx when You not use it anymore.
|
|
|
|
Post by Glenn KD0Q on Feb 19, 2023 3:38:06 GMT
OK. That is inconvenient. Never had to do that before. And never had an app change the XCVR when changing something with a XCVR button. Why now?
Also noticed that I'm getting a notification on my XCVR that JTDX is attempting to set to Split mode without setting VFO B to DATA mode first. That may just be a K3 thing.
Glenn - KD0Q
|
|
|
|
Post by Arvo ES1JA on Feb 19, 2023 7:16:09 GMT
OK. That is inconvenient. Never had to do that before. And never had an app change the XCVR when changing something with a XCVR button. Why now? Because running jtdx try's always to be ready for working. So simple it is. In general can be something like "Silent state" to be implemented into jtdx but more easy is just close jtdx. Also noticed that I'm getting a notification on my XCVR that JTDX is attempting to set to Split mode without setting VFO B to DATA mode first. That may just be a K3 thing. Glenn - KD0Q This should be investigated deeply, this is a fault but not sure where? I even don't know that VFO-s can have different modes when split is enabled. |
|
|
|
Post by Wolfgang OE1MWW on Feb 19, 2023 9:03:34 GMT
You have started JTDX to control your rig, simple as it is, any manual
change on your rig may either result in revert to before - or malfunctions
on your K3. Some rigs report on the com port the manual change by hand,
some do not. Because the K3 and JTDX may tell each other a command at the
same time, there is no way to avoid a clash in such a situation.
The point is: If JTDX task is active - NO changes by hand on the rig.
I have written a long batch file for my Kenwood, all settings for data,
filter etc. is set via com port. JTDX is started, batch file waiting,
after termination of JTDX, all is reverted to SSB again. Nothing to
touch on the Kenwood during the JTDX task running.
You can check what your current Hamlib will/can do with your K3
open a cmd window, change with cd command into the JTDX bin directory
enter the following command:
rigctl-jtdx -l > rigs.txt
Now search in the rigs.txt file the number for your K3, be surprised how many
rigs there are in the list ;-) In my file the number for the K3 is 2029, in your
installation it my be a different number.
Now enter (use the rig number you found before!):
rigctl-jtdx -u -m2029 > myrig.txt
Now you can see in the myrig.txt what functions Hamlib will support for your K3
Btw., Hamlib (rigctl) is a huge and never ending project. Enhancements / new rigs / bugs ...
|
|
|
|
Post by Arvo ES1JA on Feb 19, 2023 9:34:45 GMT
Tnx Wolfgang for (hopefully detailed enough) explanation, I'm to lazy to write so and explain more from jtdx-s point of view.
|
|
|
|
Post by Glenn KD0Q on Feb 19, 2023 13:55:32 GMT
Wolfgang & Arvo,
Thanks for all the info.
Yes Arvo, at least on the K3, VFOs can have different modes.
It still remains that neither JTDX v2.2.156 nor WSJT-X v2.6.1 change the XCVR mode to DIGITAL when Split is enabled on the XCVR. Evidently this new behavior is intended in JTDX v2.2.159.
For my style of operating where I switch modes modes often, this is not an improvement.
To compound things, JTDX v2.2.159 takes over 100 seconds to load and establish CAT control of the XCVR. JTDX v2.2.156 takes less than 20 seconds. It appears that something significant has changed in the initialization process.
Thank you for your timely responses and good information.
Glenn - KD0Q
|
|
|
|
Post by Arvo ES1JA on Feb 19, 2023 15:26:19 GMT
If You not enabled mode control in settings, then it should not touch mode settings in tranceiver, to digital change only when Data/Pkt selected in settings and there should be no differences between wsjtx and jtdx. Control is same in both programs, if different then this is hamlib different. 100 and 20 are they in real seconds?? If so then something is really bad. What is cat poll interval in settings?
|
|
|
|
Post by Glenn KD0Q on Feb 19, 2023 16:27:55 GMT
Setting Mode control to "none" is the perfect solution. Thank you Arvo! My DX cluster app sets the XCVR mode when I select a spot. Also have a macro on the K3.
Polling is set to 1 s.
Those are real stopwatch seconds for CAT control establishment after app launch. Waterfall activity also starts about the same time as CAT. WSJT-X v2.6.1 takes about 10 seconds, JTDX v2.2.156 about 17 seconds and JTDX v2.2.159 about 105 seconds. Having Mode control set to "none" makes no difference.
|
|
|
|
Post by Wolfgang OE1MWW on Feb 19, 2023 16:47:15 GMT
Glenn, long time ago we had problems with Kenwood by using 19200 on CAT.
Took the software (Hamlib) for many cycles to 'understand' the Kenwood.
Try to reduce your cat speed (unfortunately to be set on all sides).
4800 or even 2400 is more than sufficient to send the few bytes from
JTDX to the rig. You will not recognize a differenc during operation,
but the initial setup will be instantly. Would be interresting to
trace the communication during the 105 (!) seconds. What's going on ?
|
|
|
|
Post by Arvo ES1JA on Feb 19, 2023 17:32:18 GMT
Also try flow control to None
|
|
|
|
Post by Glenn KD0Q on Feb 19, 2023 17:51:43 GMT
Is there some tracing that can be turned on?
|
|
