[Hamlib-developer] rotorez configure issue
Library to control radio transceivers and receivers
Brought to you by:
n0nb
From: Randy R. <ran...@gm...> - 2024-06-07 16:55:47
|
Hi, Have attempted to disable rotorsz unstick option. It seems to fail due to attempting to set the option before the port is opened that would send the command to change the option. Am I doing something wrong? Randy KB0NAV /usr/local/bin/rotctl -r /dev/ttyS5 -m 401 -s 4800 -C unstick=0 -vvvvv rotctl Hamlib 4.6~git 2023-12-22T15:15:22Z SHA=c3d489 64-bit Report bugs to <ham...@li...> rot_init called initrots4_rotorez called rot_register (401) rot_register (402) rot_register (403) rot_register (404) rot_register (405) rot_register (406) rotorez_rot_init called rot_token_lookup called lookup unstick rot_token_lookup called lookup unstick rot_set_conf called rot_set_conf: unstick='0' rotorez_rot_set_conf called rotorez_rot_set_conf: token = 4, *val = 0 rotorez_rot_set_conf: c = s, *val = 0 rotorez_rot_set_conf: cmdstr = s, *val = 0 rotorez_send_priv_cmd called write_block: port not open Config parameter error: rot_init called initrots4_rotorez called rot_register (401) rot_register (402) rot_register (403) rot_register (404) rot_register (405) rot_register (406) rotorez_rot_init called rot_token_lookup called lookup unstick rot_token_lookup called lookup unstick rot_set_conf called rot_set_conf: unstick='0' rotorez_rot_set_conf called rotorez_rot_set_conf: token = 4, *val = 0 rotorez_rot_set_conf: c = s, *val = 0 rotorez_rot_set_conf: cmdstr = s, *val = 0 rotorez_send_priv_cmd called write_block: port not open IO error |