Hamlib CAT interface - Generated parameter String ERROR

[iz5fsa]

Hi OMs.
During holydays I've spent my time to reach a goal: setup hamlib CAT interface on LOG4OM + FLRIG + WSJT/JTDX. I've spent time handling Configuration / CAT Management / Hamlib / "generated parameter string" by hand with rigctl and rigctld in verbose mode.

Errors found in rigctl/rigctld params:

• "--port=4532" that is not recognized and must be changed with "-t 4532";

• "--rig-file=COMx" must be changed in "-r COMx".

Another error occurs, but it depend on my personal config for the YAESU FTDX101D/FY991A: the "--set-conf=stop_bits=2" is not recognized but can be omitted with no impact on radio use.

Setting up LOG4OM CAT interface with hamlib with right params...

Screenshot 2023-08-21 214318.png (77.15 KiB) Viewed 1369 times

You can set up FLDIGI CAT interface using "Hamlib NET rigctl (Stable)" in Rig definition, with "localhost:4532" string in Device field cleaning Advanced configuration field...

Screenshot 2023-08-22 204407.png (34.47 KiB) Viewed 1351 times

and with other Log4OM/Fldigi setup all woks fine (double click on Log4OM spot set up frequency/mode on radio and also on FLDIGI plus callsign in the spot!

For WSJT/JTDX the "Hamlib NET rigctl" can be used in the rig selection.

Screenshot 2023-08-21 214928.png (34.48 KiB) Viewed 1369 times

Using this setup don't need any serial port splitter added.

I hope this can help users and software / documentation maintainers!

73 de Leo IZ5FSA

[w9mdb]

You've done it the hard way

Set up FLDigi to use FLRig
Set up WSJTX to use FLRig
Set up Log4OM to use FLRig

Screenshot 2023-08-27 160040.png (50.7 KiB) Viewed 1320 times

[iz5fsa]

Yes, it works fine also.

thanks

[iz8ewd]

Problem solved now.
https://github.com/Hamlib/Hamlib/commit ... 1c6d40dfa6

Update to the last Hamlib 4.6 beta snapshot.