Hi Yoshi,
Try the following. 1. Revert WSJTX to v2.5.2. 2. Copy the file "libhamlib-4.dll" (usually in C:\WSJT\wsjtx\bin) to any other place of your computer (or simply rename it to "libhamlib-4.dll_2.5.2". 3. Update WSJTX again to v2.5.4 4. Rename the "libhamlib-4.dll" file from v2.5.4 (usually in C:\WSJT\wsjtx\bin) to "libhamlib-4.dll_2.5.4" 5. Copy the v2.5.2 version of "libhamlib-4.dll" (=the file you saved during step 2) to C:\WSJT\wsjtx\bin, so that you have again a file "libhamlib-4.dll" within this bin directory. 6. Launch WSJTX v2.5.4 and see if it works now for your rig. Alternatively you can also try the latest "libhamlib-4.dll" file from here: http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll (for 64-bit WSJTX) http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll (for 32-bit WSJTX) The file "libhamlib-4.dll" contains the hamlib libraries (=the “drivers” for all the rigs). To implement "drivers" for new rigs or improve performance, or simply to fix errors, Hamlib is updated daily. As long as your rig works well, there is no reason for you to update hamlib, but in case of troubles it’s worth either to try a slightly older hamlib version or the latest one. The technology we use allows you to easily perform such hamlib updates yourself. Just replace the file "libhamlib-4.dll". 73 de Uwe DG2YCB -----Ursprüngliche Nachricht----- Von: Yoshi,I via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Gesendet: Sonntag, 9. Januar 2022 07:44 An: wsjt-devel@lists.sourceforge.net Cc: Yoshi,I Betreff: [wsjt-devel] WSJT-X 2.5.4 RIG control error when using FTDX-3000 + USB Port. Hi there, CAT control fails on FTDX-3000 + USB Port. If you use the FTDX-3000+USB port, two RS232C ports are created. No matter which one you use, it will not work, the RIG control error and TEST CAT will turn red. Of course I tried all the speeds of RS232C, but it remained an error. I renamed WSJT-X.ini, started WSJT-X again and started from the initial settings, but it is the same. There is no station around me using FTDX-3000 + USB, so I'm stopping here. Reverting to WSJT-X 2.5.2 and using the old WSJT-X.ini does not give any errors and is working fine. Are there any stations in a similar state? -- 73s de JH8XVH Yoshi -- このEメールはアバスト アンチウイルスによりウイルススキャンされています。 https://www.avast.com/antivirus _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
