Re: [Hamlib-developer] rigctl send_cmd

[Jere S. <k4...@gm...>]

Bill,
See below:

rigctl -m 135 -r /dev/tty.SLAB_USBtoUART -s 9600 -t\; w FA -vvvvv
rigctl, Hamlib 3.0.1
Report bugs to <ham...@li...>

rig:rig_init called 
yaesu: initrigs3_yaesu called
rig_register (121)
rig_register (127)
rig_register (110)
rig_register (105)
rig_register (106)
rig_register (107)
rig_register (109)
rig_register (120)
rig_register (101)
rig_register (122)
rig_register (123)
rig_register (111)
rig_register (115)
rig_register (113)
rig_register (114)
rig_register (128)
rig_register (131)
rig_register (116)
rig_register (103)
rig_register (124)
rig_register (104)
rig_register (125)
rig_register (129)
rig_register (132)
rig_register (130)
rig_register (117)
rig_register (119)
rig_register (118)
rig_register (126)
rig_register (133)
rig_register (134)
rig_register (135)
ft991_init called, version 0.22.4
newcat_init called
rig:rig_open called 
newcat_open called
newcat_open: write_delay = 0 msec
newcat_open: post_write_delay = 50 msec
newcat_set_trn called
newcat_valid_command called
newcat_valid_command AI
cmd_str = AI0;
cmd_str = AI0;
write_block(): TX 4 bytes
0000    41 49 30 3b                                         AI0;            
cmd_str = ID;
write_block(): TX 3 bytes
0000    49 44 3b                                            ID;             
read_string(): RX 7 characters
0000    49 44 30 36 37 30 3b                                ID0670;         
newcat_set_cmd: read count = 7, ret_data = ID0670;
newcat_get_vfo called
newcat_valid_command called
newcat_valid_command VS
newcat_valid_command: 'FT-991' command 'VS' not supported
Opened rig model 135, 'FT-991'
Backend version: 0.22.4, Status: Beta
write_block(): TX 0 bytes
read_string(): Timed out 2.1470 seconds after 0 chars
rig:rig_close called 
newcat_close called
rig:rig_cleanup called 
newcat_cleanup called

Jere

> On Feb 6, 2018, at 1:03 PM, Bill Somerville <g4...@cl...> wrote:
> 
> On 06/02/2018 17:41, Nate Bargmann wrote:
>> * On 2018 06 Feb 08:26 -0600, Bill Somerville wrote:
>>> On 06/02/2018 14:04, Jere Sandidge wrote:
>>>> Thank you for the info, do you have any suggestions on where to look in the rigctl code to determine why I see this?
>>> Hi Jere,
>>> 
>>> in the file I mentioned, test/rigctl_parse.c, look at the handler for the
>>> send_cmd token.
>> That section of code queries the rig_state structure.  I'm wondering if
>> the backend is not populating the structure correctly, or at all?
>> 
>> 73, Nate
> Hi Nate,
> 
> looks ok to me. I think that the important part is the correct command terminator must be set with the rigctl -t command line option, something like (untested and may need more options for serial port):
> 
> rigctl -m135 -t\; w FA
> 
> 73
> Bill
> G4WJS.
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer