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
Setting the GPIO pin for the CM108 PTT device appears to be broken.
Here's the default configuration:
$> rigctl -L -P CM108 | grep ptt_bitnum -A 2 rig_open: error = (null) No such file or directory ptt_bitnum: "Push-To-Talk GPIO bit number" Default: 2, Value: 0 Range: 0.0..7.0, step 1.0
Setting ptt_bitnum shows the configuration option being set:
ptt_bitnum
$> rigctl -L -P CM108 -C ptt_bitnum=3 | grep ptt_bitnum -A 2 rig_open: error = (null) No such file or directory ptt_bitnum: "Push-To-Talk GPIO bit number" Default: 2, Value: 3 Range: 0.0..7.0, step 1.0
But when the rig is initialized, the default value is used instead of the configured value:
$> rigctl -L -P CM108 -p /dev/hidraw0 -C ptt_bitnum=3 -vvvv 2>&1 | grep cm108_ptt_set cm108_ptt_set called cm108_ptt_set: bit number 2 to state 0 ^C
The text was updated successfully, but these errors were encountered:
Fix CM108 ptt setting
56c87cf
#1203
Update NEWS
3eedc5a
bfc6d19
63f9ac4
Really fix CM108 ptt_bitnum usage
5ebde1c
No branches or pull requests
Setting the GPIO pin for the CM108 PTT device appears to be broken.
Here's the default configuration:
Setting
ptt_bitnum
shows the configuration option being set:But when the rig is initialized, the default value is used instead of the configured value:
The text was updated successfully, but these errors were encountered: