hamlib-developer

[Hamlib-developer] IC737 in hamlib-1.1.4-cvs-021128

[Sid B. <sb...@bl...>]

	I get the usual "timed out messages". If I change ic775.c ID to "0x3c",
I can display/set mode and frequency - just as before. If you need any
further information, please shout.

	Error messages when I select IC737 as the rig.
-----------------------------------------------------------
barrabas:/usr1/HAMRADIO/hamlib-1.1.4-cvs-021128 # grig&
[4] 17283
barrabas:/usr1/HAMRADIO/hamlib-1.1.4-cvs-021128 # rig:rig_init called
rig: loading backend icom
icom: _init called
rig_register (309)
rig_register (310)
rig_register (311)
rig_register (313)
rig_register (319)
rig_register (321)
rig_register (330)
rig_register (326)
rig_register (327)
rig_register (347)
rig_register (334)
rig_register (344)
rig_register (335)
rig_register (340)
rig_register (342)
rig_register (304)
rig_register (307)
rig_register (352)
rig_register (353)
rig_register (351)
rig:rig_open called

** WARNING **: gnome_hamlib_rig.c: Could not get power status from RIG.


** WARNING **: gnome_hamlib_rig.c: Could not get mode and pbwidth from
RIG.

read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not get frequency.


GnomeUI-WARNING **: Could not open help topics file NULL
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character
read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not get mode and pbwidth.

read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not set mode. Trying to reset.

read_string: timedout without reading a character
read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not get mode and pbwidth.

read_string: timedout without reading a character

** WARNING **: gnome-hamlib-rig.c: Could not set mode. Trying to reset.

read_string: timedout without reading a character
rig:rig_close called
rig:rig_cleanup called

GConfClient-WARNING **: Directory `/apps/gpredict' was not being
monitored by GConfClient 0x80aa518
Regards
Sid.
-- 
Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot
Linux only shop

Re: [Hamlib-developer] IC737 in hamlib-1.1.4-cvs-021128

[<al...@ph...>]

Hi Sid,

> GConfClient-WARNING **: Directory `/apps/gpredict' was not being
> monitored by GConfClient 0x80aa518

It looks like you even caught a silly bug in grig... Thanks.

Alex
OZ9AEC

Re: [Hamlib-developer] IC737 in hamlib-1.1.4-cvs-021128

[Sid B. <sb...@bl...>]

	rigctl is also telling me the same story.
Regards
Sid.

On Sun, 2002-12-01 at 20:52, al...@ph... wrote:
> Hi Sid,
> 
> > GConfClient-WARNING **: Directory `/apps/gpredict' was not being
> > monitored by GConfClient 0x80aa518
> 
> It looks like you even caught a silly bug in grig... Thanks.
> 
> Alex
> OZ9AEC
-- 
Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot
Linux only shop

Re: [Hamlib-developer] IC737 in hamlib-1.1.4-cvs-021128

[Stephane F. <f8...@fr...>]

On Sun, Dec 01, 2002 at 06:14:10PM +0000, Sid Boyce wrote:
> 	I get the usual "timed out messages". If I change ic775.c ID to "0x3c",
> I can display/set mode and frequency - just as before. If you need any
> further information, please shout.

Sorry, grig does not give enough debug information. Can you try again
with "rigctl -vvvvvv -m 321 -r /dev/ttySx"  and report traces?

Also make sure you've setup the right baud rate. As a default,
Hamlib uses the highest possible, which is believed to be 19200 (please
correct me if wrong). If you've setup something different for your rig,
try passing to rigctl "-s 9600" or whatever speed you choosed.

73
Stephane