New hamlib for installation directions

#1 Shut down WSJTX

#2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of 
WSJTX -- 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 the appropriate WSJTX 
directory
C:\WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there.

http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll

http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll

Linux/Unix/Mac users need to compile the latest tar file from 
http://n0nb.users.sourceforge.net
Note: If compiling on Unix-like systems please uninstall any Hamlib package you 
have before installing the new build

#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 - 
https://www.youtube.com/watch?v=AyVqCJrs9dk

Once installed on Linux do "ldconfig".

rigctl --version should then show a relatively recent date of the download


Then if you still have the problem...
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0

    C:\Users\[username]\AppData\Local\WSJT-X
    The WSJT-X_Rigcontrol.log file will be in the same location

For Linux put it in  
    ~/.config
    The WSJT-X_Rigcontrol.log file will be here:
    ~/.local/share/WSJT-X

For MacOS put it in
    /Users/[username]/Library/Preferences
 
Restart WSJT-X and duplicate the problem.
Shut down WSJT-X

Then send me the WSJT-X_RigControl.log file
Mike W9MDB





On Monday, August 28, 2023 at 02:45:23 AM CDT, Mark Galbraith via wsjt-devel 
<wsjt-devel@lists.sourceforge.net> wrote: 





  


When using Shift-click on the waterfall to set the TX frequency, the “Rig 
Control Error” popup is displayed.  Clicking the “Show Details…” button shows 
the following error information:


Hamlib error: port_wait_for_data_direct(733): timeout=1,0

port_wait_for_data_direct(742): timeout=1,0

read_string_generic(): RX 1 characters, direct=1

0000 3b ; 

newcat_set_cmd_validate: cmd validation failed, 'MD1C;'!=';', try#8

9:newcat.c(10969):newcat_set_cmd_validate returning(-8) Protocol error

 

newcat_set_cmd: set_cmd_validate failed

8:newcat.c(11010):newcat_set_cmd returning(-8) Protocol error

 

7:newcat.c(1528):newcat_set_mode returning(-8) Protocol error

 

6:rig_set_split_mode: elapsed=806ms

6:rig.c(4647):rig_set_split_mode returning(-8) Protocol error

 

5:rig_set_split_freq_mode: elapsed=911ms

5:rig.c(5022):rig_set_split_freq_mode returning(-8) Protocol error

 

Protocol error

Protocol error

while setting split TX frequency and mode

 

Timestamp: 2023-08-28T02:28:24.231Z

 

 

This error has not occurred using WSJT-X 2.6.1.  My configuration is as follows:

Radio: Yaesu FT-710

Software stack:

     
    * Win4YaesuSuite (latest version)
         
        * Software control of the radio.  Also provides virtual COM ports 
(using com0com) to allow additional software to access the CAT control stream.
        * CAT connection to radio on COM3.  Provides CAT virtual CAT 
connections on COM7, COM9, COM11, COM13, and COM15.
        * 3rd party software connections are mentioned below.  COM13 and COM15 
connections are used for unrelated programs not involved in FT8/FT4 operation.
    
    * DXLabs Suite (latest version)
         
        * Has additional software control features for the radio but lacked the 
virtual COM support.  Control program needed to support additional functions of 
the suite.
        * Used for general logging and other functions.
        * Connects to CAT interface on COM9
    
    * N1MM+ (latest version)
         
        * Used for contest logging.
        * Connects to CAT interface on COM11
    
    * WSJT-X
         
        * Normally use 2.6.1.  Downloaded 2.7.0-RC2 to check out some of the 
new features.
        * Connects to CAT interface on COM7
    
    * JTAlert for WSJT-X (latest version)
         
        * Better visual representation of decodes.
    

 

The DXLabs and N1MM+ portions of the stack are not involved in this error as 
they are not in the stack between WSJT-X and the radio.  They are shown for 
completeness. 

 

Please let me know if you have any questions or need more information to help 
track this down.  For now I have reverted back to v2.6.1 so I can continue 
working FT8/FT4.

 

 

73

-.. . / -- .- .-. -.- / -. --... -.-- -..

DE  MARK  N7YD

 



_______________________________________________
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

Reply via email to