From: Paul G. <pa...@co...> - 2010-11-24 22:35:16
|
Interesting isn't quite what I call it :) -----Original Message----- From: Nate Bargmann <n0...@n0...> To: Paul Graham <pa...@co...> Cc: Hamlib Developers <ham...@li...> Subject: Re: [Hamlib-developer] show_error: hamlib_init: IO error Date: Wed, 24 Nov 2010 15:48:01 -0600 * On 2010 24 Nov 15:28 -0600, Paul Graham wrote: > Hello Nate, > > This is the output I get, I have to Ctrl+c to exit. That's interesting. After the timeout rigctl should not be hanging up like that. > ft897:ft897_init called > rig:rig_open called > ft897:ft897_open called > Opened rig model 123, 'FT-897' > Backend version: 0.3.3, Status: Beta > > Rig command: f > ft897: cache invalid > TX 5 bytes > 0000 00 00 00 00 03 ..... > read_block: timedout after 0 chars > get_freq: error = Communication timed out Just to confirm, your radio is set for 38400 baud on the RS-232 interface, correct? I presume that your manual also specifies 2 stop bits (Hamlib default). Does the FT-897 have a CAT icon that flashes when it receives a command? Some of the models did, but my FT-817 does not, for example. > Rig command: q > rig:rig_close called > ft897:ft897_close called > ^C Very odd. In other words, I've not seen that before. 73, de Nate >> |