|
|
Post by Pete G4RRM on Mar 7, 2022 13:36:05 GMT
Hi All
This is probably a trivial issue but somewhat annoying, to me at least.
I have installed 159 and all works well.
I have found that while running JTDX if an interesting spot appears on the Cluster and I use the Bandstack option in the FT5000 to move me to the SSB part of the band, (on each band I have it set for FT8 frequency, SSB section and one for the CW end of the bands), I used to be able to check if I could hear the DX without having to close JTDX. If I didn't hear the DX I just pressed the Band button again to move back to the FT8 frequency and continue with FT8.
What I have noticed now is that using the same process under 159 when I go to the CW section to check if I can hear the DX spotted 159 changes the mode to USB! this didn't happen in 156 and I have gone back to make sure and 156 sits quite happily on CW with JTDX open as long as I want to stay there listening.
I assume something has changed in the new version, to make the mode change that wasn't happening in 156.
Is this design or a bug?
it was very useful just to be able to do a quick QSY to the CW section to check the DX without having to close JTDX.
Thanks
73
Pete
G4RRM
|
|
|
|
Post by w9mdb on Mar 7, 2022 13:49:14 GMT
Please try the latest 32/64-bit DLL as appropriate from here -- I just made a patch yesterday which may fix this problem. New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. n0nb.users.sourceforge.net/dll32/libhamlib-4.dlln0nb.users.sourceforge.net/dll64/libhamlib-4.dll#3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - www.youtube.com/watch?v=AyVqCJrs9dkMike W9MDB |
|
|
|
Post by Rob G4UJS on Mar 7, 2022 15:00:19 GMT
Hi Mike,
I have the same problem as Pete and I just tried the new hamlib file...... unfortunately it didnt fix it for me. Rig here is FTdx101mp
73 Rob G4UJS
|
|
|
|
Post by Arvo ES1JA on Mar 7, 2022 15:12:17 GMT
"""Is this design or a bug?""" I believe it is design when You have Configured jtdx to control Mode then it does. Attached configuration, If there mode set to USB or Data/Pkt then jtdx try to keep mode when running,design. If Mode set to None then it is jtdx-s bug. |
|
|
|
Post by w9mdb on Mar 7, 2022 15:32:12 GMT
Download the debug version of JTDX MS Windows, 64bit cloud.mail.ru/public/7ksV/ihDgYKHgCchecksum jtdx-2.2.159-rc4-debug-win64.exe SHA-256: BB46D1531DF3FCA63F7FA1CE9E5A08AE418685988A2488490A730E8B2D00FBAA Two logs will be recorded: in %TEMP% directory, file name is JTDX_trace.log in JTDX QSO log directory, file name is jtdx_debug.txt Duplicate the problem and send me the logs Mike W9MDB |
|
|
|
Post by Rob G4UJS on Mar 7, 2022 16:39:39 GMT
Thanks Arvo, I have a mode set in JTDX...so by design, understood now.
But Pete's point in first post is that it doesn't behave like this in 156.
Thanks
Rob
|
|
|
|
Post by w9mdb on Mar 7, 2022 16:58:26 GMT
I'm waiting for the debug log.
|
|
|
|
Post by Rob G4UJS on Mar 7, 2022 19:19:23 GMT
Debug file sent Mike
|
|
|
|
Post by w9mdb on Mar 7, 2022 19:37:32 GMT
Sent where?
mdblack98@yahoo.com is my address
|
|
|
|
Post by w9mdb on Mar 7, 2022 21:13:53 GMT
On your band stack do you have the FT8 settings on the 1st band stack? That's what hamlib is recalling (or should be) now on band change and you may be seeing different behavior. That was added Jan 2021
|
|
|
|
Post by Rob G4UJS on Mar 7, 2022 22:31:43 GMT
hmmmmm. I've no real idea of what number the band stack is...they are not numbered. I think whatever stack it is on when jtdx starts it puts the mode to data/pkt.
73
|
|
|
|
Post by w9mdb on Mar 7, 2022 22:51:26 GMT
It's based on pushing the band button -- there's a timeout involved but I don't know what it is.
1 push give 1st band stack.
2nd push quickly gives 2nd band stack
3rd push quickly gives 3rd band stack
Hamlib defaults to the 1st band stack so you should put your CW and other on stack 2 & 3.
I could make a setting for which band stack to use but nobody has exposed such an option on their software yet. So for now easiest to set stack#1 to FT8.
Mike
|
|
|
|
Post by w9mdb on Mar 8, 2022 21:43:13 GMT
159 definitely does keep trying to set mode which it should not do until Enable, transmit or band change is done.
Those 3 condition should also set VFOB if rig split is enabled.
|
|
|
|
Post by Arvo ES1JA on Mar 9, 2022 5:21:41 GMT
159 definitely does keep trying to set mode which it should not do until Enable, transmit or band change is done. Those 3 condition should also set VFOB if rig split is enabled. This is Your opinion, mine is, jtdx should be keep its rig configuration all the time, to avoid delays (or even seen some faults) on going to transmit. |
|
|
|
Post by w9mdb on Mar 9, 2022 5:27:55 GMT
Not an opinion...an observation...
Problem is this makes it impossible to use JTDX with any other software like FLDigi, DM780, CW Skimmer, MMTTY, and on and on.
At least make it an option.
|
|
