I'm using an FT-817 and FT-818 for satellite ops, and whilst it's possible to work linear satellites without computer aided rig control I'd like to see if it makes operation that much easier.
I'm using Gpredict as the front end, and whilst I can get rigctld running for the FT-817 using:
$ rigctl -m 120 -r /dev/ttyUSB0
attempting to use:
$ rigctl -m 120 -r /dev/ttyUSB1
for the FT-818 just crashes the attempt.
Now line 409 of README.developer states: "The rule is one backend per protocol family." So does this mean that supporting two FT-81# radios can't work even if an FT-818 module (duplicate of the FT-817) was added to the code?
Is there another option?
Thanks.
Ciemon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The "one backed per protcol family" doesn't mean one rig per instance of rigctl.
Probably better said said as "one backend per manufacturer or protocol" since manufacturer is the biggest grouping.
And you should be able to do what you want.
1 - Please add "-vvvvv -Z" to the command line so we can see better what's going on.
2 - Can you compile the lastest hamlib from https://github.com/Hamlib/Hamlib and test that too?
de Mike W9MDB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With gpredict you should be running rigcltd, not rigctl.
And the 2nd rigctld needs a different port.
rigctld -m 120 -r /dev/ttyUSB0
rigctld -m 120 -r /dev/ttyUSB1 -t 4533
de Mike W9MDB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was already using rigctld rather than rigctl, that was a bad copy paste. But I hadn't found anything that referred to -t 4533, that prevented the crash and everything subsequently works. Now to go back through the man pages to find the -t that I missed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using an FT-817 and FT-818 for satellite ops, and whilst it's possible to work linear satellites without computer aided rig control I'd like to see if it makes operation that much easier.
I'm using Gpredict as the front end, and whilst I can get rigctld running for the FT-817 using:
$ rigctl -m 120 -r /dev/ttyUSB0
attempting to use:
$ rigctl -m 120 -r /dev/ttyUSB1
for the FT-818 just crashes the attempt.
Now line 409 of README.developer states: "The rule is one backend per protocol family." So does this mean that supporting two FT-81# radios can't work even if an FT-818 module (duplicate of the FT-817) was added to the code?
Is there another option?
Thanks.
Ciemon
The "one backed per protcol family" doesn't mean one rig per instance of rigctl.
Probably better said said as "one backend per manufacturer or protocol" since manufacturer is the biggest grouping.
And you should be able to do what you want.
1 - Please add "-vvvvv -Z" to the command line so we can see better what's going on.
2 - Can you compile the lastest hamlib from https://github.com/Hamlib/Hamlib and test that too?
de Mike W9MDB
With gpredict you should be running rigcltd, not rigctl.
And the 2nd rigctld needs a different port.
rigctld -m 120 -r /dev/ttyUSB0
rigctld -m 120 -r /dev/ttyUSB1 -t 4533
de Mike W9MDB
Fixed instantly. Thank you Mike.
I was already using rigctld rather than rigctl, that was a bad copy paste. But I hadn't found anything that referred to -t 4533, that prevented the crash and everything subsequently works. Now to go back through the man pages to find the -t that I missed.