Re: [Hamlib-developer] serial ports and hamlib

[Joop S. <pa...@de...>]

Op ma 24-02-2003, om 20:57 schreef Wilbert Knol:
> On Tuesday 25 February 2003 07:00, Joop Stakenborg wrote:
> 
> <snip>
> > If I remember correctly, someone on the xlog-discussion mailing list
> > reported blocking of the gui when using /dev/usb. This also happens when
> > using tlf. 
> 
> That was me. The interesting thing was that the hamlib rigctl program worked 
> perfectly through the USB port, but XLOG/TLF/GRIG didn't.
> 
> XLOG would grind to a halt, and, from memory, TLF would become errattic with 
> the QRG updates, complaining about time-outs. As a matter of interest: TLF 
> worked OK if I put a TNC on the USB port (for DX-Cluster spots), and have the 
> rig control on the serial port.
> 
> I had a look for time-out values using USBview, but couldn't see anything 
> obvious. If memory serves me, there were references to 50 ms
> 

Woops, I just noticed an inconsistency in the xlog source code. At
program startup, the polling frequency is set at 350 mS, but when hamlib
is activated through the preferences dialog, it is set to 200 mS, which
is too small.

Wilber, if you like we could do an experiment. In the xlog source code,
look for the ocurrence of:

hamlibtimer = gtk_timeout_add (350, (GtkFunction) get_riginfo, NULL);

in src/main.c and change the value of 350 to lets say 1000.

Also, in src/callbacks_preferencesdialog.c, look for:

gtk_timeout_add (200, (GtkFunction) get_riginfo, NULL);

There are 2 lines like this. Change 200 to 1000.

The recompile and see what it does. Maybe we are lucky.

> 
> Wilbert, ZL2BSJ
> 
> 

Regards,
Joop