Skip to content
New issue

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

RigCtl fails to return valid result when setting FT-991 into C4FM mode #1027

Closed
rpoulin opened this issue May 13, 2022 · 3 comments
Closed
Labels
bug fixed Issue has been fixed
Milestone

Comments

@rpoulin
Copy link

rpoulin commented May 13, 2022

This issue impacts my logging software (Log4OM2) that disconnects my CAT interface due to a timeout or error code returned from HamLib. I downloaded and tested RigCtl from the command line on Windows with the following observations:


PS C:\Program Files (x86)\hamlib-w64-4.4\bin> .\rigctl.exe -m 1035 -r COM4 -C stop_bits=2 -v -Z -o
Opened rig model 1035, 'FT-991'

Rig command: \get_vfo_info VFOA
Freq: 145690000
Mode: FM
Width: 16000
Split: 0
SatMode: 0

<<--------- Set FT-991 to C4FM mode here ---------->>

Rig command: \get_vfo_info VFOA
Freq: 145690000
Mode: None
Width: 0
Split: -425705312
SatMode: 0
get_vfo_info: error = Protocol error
rig.c(6961):rig_get_vfo_info return(-8)
rigctl_get_vfo_info: vfo=VFOA
rigctl_parse.c(2304):rigctl_get_vfo_info return(-8)


It appears that the C4FM mode may not be implemented. The man pages indicate that it is not implemented but that "AMS" is a valid mode token, C4FM is missing from the list of valid modes. In the real world, AMS is an "Automatic Mode Select" option for the FT-991 when C4FM is the selected mode. C4FM is the digital mode supported by the radio not AMS.

@vk4tux
Copy link

vk4tux commented May 13, 2022 via email

@mdblack98
Copy link
Contributor

mdblack98 commented May 13, 2022 via email

@mdblack98 mdblack98 added the bug label May 13, 2022
@mdblack98 mdblack98 added this to the 4.5 milestone May 13, 2022
@mdblack98 mdblack98 added the fixed Issue has been fixed label May 13, 2022
@rpoulin
Copy link
Author

rpoulin commented May 14, 2022

Mike,

I am sending you a text file containing the trace you requested. I set the rig into C4FM mode before I ran the commands. Hope this is what you needed.

Regards,
trace.txt

Ron (NG7V)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fixed Issue has been fixed
Projects
None yet
Development

No branches or pull requests

3 participants