We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are issues with Hamlib 4.4 (possibly earlier versions, as well) that prevent rigsync from working correctly when built with it.
If you need Hamlib 4.x to support newer rigs, it is recommended that you use Hamlib 4.x's rigctld to establish a server, eg:
rigctld -m 1022 -r /dev/ttyF0 -s 38400 -t 4533
And rebuild rigsync using Hamlib 3.3 and connect to the server instead of to the rig's serial port.
The text was updated successfully, but these errors were encountered:
Hello Is it possible to sync between two rigctl servers. I didn't find the way to connect rigsync as a client to a server as you posted above.
./rigsync -m 2 -r 192.168.1.42:4235 -m 2 -r 192.168.1.41:4235 -n 1
*** Could not open rig 1: IO error network.c(298):network_open return(-6) iofunc.c(177):port_open return(-6) rig.c(795):rig_open return(-6)
Thanks for your help!
Sorry, something went wrong.
Hello. It works perfect. My mistake. Thanks!! My ports numbers were wrong.
./rigsync -m 2 -r 192.168.1.42:4532 -m 2 -r 192.168.1.41:4532 -n 1
daveriesz
No branches or pull requests
There are issues with Hamlib 4.4 (possibly earlier versions, as well) that prevent rigsync from working correctly when built with it.
If you need Hamlib 4.x to support newer rigs, it is recommended that you use Hamlib 4.x's rigctld to establish a server, eg:
rigctld -m 1022 -r /dev/ttyF0 -s 38400 -t 4533
And rebuild rigsync using Hamlib 3.3 and connect to the server instead of to the rig's serial port.
The text was updated successfully, but these errors were encountered: