|
|
Post by Peter DL7PJ on Mar 1, 2022 21:53:25 GMT
Hello OMs, unfortunately the RIG ON function no longer works for FTDX1200 in the new version. I make clean install , unfortunately without success. before that in version156 it worked .someone has an idea ? 73 de Peter
|
|
|
|
Post by Peter DL7PJ on Mar 2, 2022 5:31:39 GMT
now there is the fact that the transceiver is sometimes simply switched off and no longer transmits, i.e. the transciver control behaves more and more strangely
|
|
|
|
Post by w9mdb on Mar 2, 2022 14:20:04 GMT
And if you go back to 156 does it work OK?
Switching off on it's own is very strange...
|
|
|
|
Post by Peter DL7PJ on Mar 2, 2022 15:08:13 GMT
unfortunately I can't go back to the 156 because I also uninstalled it and couldn't find any more 156 setup files. Where can it be that the CAT connection is spinning. Sometimes even the 2 VFOs get mixed up or CAT commands sometimes don't arrive. Completely inconsistent. In 156 everything was great
|
|
|
|
Post by w9mdb on Mar 2, 2022 15:18:43 GMT
|
|
|
|
Post by Peter DL7PJ on Mar 2, 2022 16:34:37 GMT
Thanks Mike for the help, installed 156 right away and it's working fine. Can I maybe use some old DLL for the new 159 version to run?
|
|
|
|
Post by Peter DL7PJ on Mar 2, 2022 16:56:22 GMT
I tried the original libhamlib-4.dll from github.com/Hamlib/Hamlib/releases/tag/4.4 as a test, so it works optimally the way it looks, what is the difference to JTDX Hamlib? The only thing that doesn't work with it is rig split but fake split works |
|
|
|
Post by Peter DL7PJ on Mar 3, 2022 8:09:40 GMT
A summary of the original HamLib.DLL, after a long break in transmission, the CAT connection is lost, only restarting the program helps.
Is it possible to download the HamLib.DLL somewhere that was implemented in the 156? It worked perfectly with an FTDX 1200
|
|
|
|
Post by Igor UA3DJY on Mar 3, 2022 10:40:57 GMT
|
|
|
|
Post by Peter DL7PJ on Mar 3, 2022 11:19:32 GMT
hello Igor, first of all thank you for this wonderful software, I have made over 15000 QSOs with it, I don't want to miss it anymore. I will test the DLL tonight. Thank you for the help and I look forward to future developments
|
|
|
|
Post by w9mdb on Mar 3, 2022 12:54:05 GMT
If it's working for normal QSOs for the most part then I suspect something else is going on.
Have you turned off all the sleep options on ALL your USB devices?
Mike W9MDB
|
|
|
|
Post by Peter DL7PJ on Mar 3, 2022 17:58:01 GMT
I am now testing the 158 HamLib, the transceiver starts and is working without errors so far, Rig Split does not work, I will now make a few QSOs and observe
|
|
|
|
Post by Peter DL7PJ on Mar 4, 2022 16:58:23 GMT
Hello Igor and Mike , it looks like the HamLib 158 works with Yaesu FTDX1200, what doesn't work at all is split with 2 VFOs which worked in the 156. Otherwise the new 159 version is just great, uses minimal resources and recognizes the signal. Will the Rig Split for 2 VFOs be fixed? Top, 73 de Peter |
|
|
|
Post by Peter DL7PJ on Mar 5, 2022 15:14:10 GMT
So it is definitely the case that the 156 HamLib is the only one that still worked perfectly.
All other versions have errors, either the transciver does not turn on or, despite the USB energy-saving mode being switched off, the connection to the transciever is lost and I have to press Test CAT in the settings, Test PTT does not work, I then have to press the Tune button only then does TX work anyway, then the most important thing the split mode doesn't work anymore and sometimes the VFO A RX LED in the transciver flickers. VFO B works no more.
What just happened between 156 and 158/159 that the communication to my transciver is completely defective?
is there somewhere in the archive the 156 HamLib version to download?
I start between the JTDX 156 because everything always works immediately.
73 de Peter
|
|
|
|
Post by w9mdb on Mar 5, 2022 15:55:03 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 |
|
