[Hamlib-developer] Re: GUI blocking

[Wilbert K. <zl...@zl...>]

Hi Joop(and others)

> Do you happen to know the baud rate of the USB hub? 


The notebook I use has a built-in OHCI root hub.
Plugged into that is the Keyspan USB 4-port serial adapter.

Having studied the proc_usb_info.txt file, I reckon the root hub talks to
the kernel at 12 Mbd, and the 4-port serial adapter also runs at 12 Mbd.

Here is the low-down on the root hub:

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 0.00
S:  Product=USB OHCI Root Hub
S:  SerialNumber=c4a7b000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

Funnily enough, the B: tag shows 0% bandwidth.
The E: tag shows a max packet size of 2, and interval time of 255 ms,
which seems a bit slow.

Anyway, hanging off the root hub is the 4-port serial adapter:

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=ff(vend.) Sub=00 Prot=00 MxPS=64 #Cfgs=  4
P:  Vendor=06cd ProdID=010a Rev= 0.00
S:  Manufacturer=Keyspan, a division of InnoSys Inc.
S:  Product=USB 4-port Serial Adapter
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs=14 Cls=ff(vend.) Sub=00 Prot=00 Driver=serial
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=  1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=  1ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=  64 Ivl=  1ms
E:  Ad=84(I) Atr=02(Bulk) MxPS=  64 Ivl=  1ms
E:  Ad=85(I) Atr=02(Bulk) MxPS=  64 Ivl=  1ms
E:  Ad=86(I) Atr=02(Bulk) MxPS=  64 Ivl=  1ms
E:  Ad=87(I) Atr=02(Bulk) MxPS=  64 Ivl=  1ms

Not sure what the 14 'end points' refer to, there are only 4 ports in
the device. Perhaps they are DCD, RTS etc etc, for one port.

It may be easier to grab a scope from work next week and to take a look
at the rig's bus (the CAT CI-V bus) whilst I fiddle with the code.

>It would also be
> interesting to know what kind of rig you are using, so we can check you
> rig's timeout setting.

The radio is an IC-725 (#314) and runs at 1200 bd

> The only reason for collisions I can think of, is the rig still sending
> information while xlog already demands for the next information. So this
> would mean the timing is still too fast. But I might be wrong here....

Yes, I am pretty sure that's what is happening. XLOG polls the rig just
as I tune it, resulting in a bus collision. Anyway, with your new
parameters, XLOG recovers from that, after a second or so.

Come to think of it, you should not have to poll the rig at all. When I
tune around, it will broadcast the new QRG.

I am not sure how you would deal with this. It is really a hamlib issue
:-)

> Thanks for trying. I have to think about finding a neat way to avoid GUI
> blocking in future versions of xlog.

OK...aside from the error messages in the status bar, it's working pretty
well now!


73,

Wilbert, ZL2BSJ