Re: Acquiring Dental RVG on Linux
Am Tue, Dec 29, 2020 at 03:10:37PM +0530 schrieb Sonali Warunjikar:
> On Mon, Dec 28, 2020 at 06:48:47PM +0530, Sonali Warunjikar wrote:
> > Right now I am stuck with 'Timeout error' when processing Ii event
> > (interrupt read). Have written to pyusb mailing list as well. Any help
> > here will be great as well.
>
> Still stuck there... Any idea from the following trace about why S Ii
> (first event's) response comes after so many Ci/Co interactions in between?
This sequence of events might be some sort of syncronisation
and/or further setup of interchange parameters.
> Trying to playback Ii by reading from the endpoint causes timeout
> exception. usbmon shows timeout exception itself as "No such file or
> directory". So if I do usbmon on my own code the response to playing back
> 'S Ii' event is same as the Windows driver. The only difference is, in
> Windows driver's case it comes after those Ci/Co events in between and in
> my case it comes immediately.
Can you try inserting a delay before this:
> 1.007.001 S Ii 0002
and running the init sequence up to here in a loop with
increasing delays until, hopefully, this happens:
> 1.007.000 S Ci 0342 c0 83 0008 0000 0342
> 1.007.000 C Ci 0342 OK
> 20 20 44 <snip>
> 1.007.000 S Ci 0001 c0 8e 0000 0000 0001
> 1.007.000 C Ci 0001 OK
> 01
> 1.007.000 S Ci 000a c0 83 0199 0000 000a
> 1.007.000 C Ci 000a OK
> 30 32 2f 31 30 2f 32 30 31 35
> 1.007.000 S Ci 0001 c0 83 0198 0000 0001
> 1.007.000 C Ci 0001 OK
> 00
> 1.007.000 S Co 0000 40 81 0000 0000 0000
> 1.007.000 C Co 0000 OK
> 1.007.000 S Co 0000 40 8f 0000 0000 0000
> 1.007.000 C Co 0000 OK
> 1.007.000 S Ci 0001 c0 85 0000 0000 0001
> 1.007.000 C Ci 0001 OK
> 01
> 1.007.000 S Co 0000 40 81 0000 0000 0000
> 1.007.000 C Co 0000 OK
> 1.007.000 S Co 0000 40 8f 0000 0000 0000
> 1.007.000 C Co 0000 OK
> 1.007.000 S Co 0000 40 81 0000 0000 0000
> 1.007.000 C Co 0000 OK
> 1.007.000 S Co 0000 40 8f 0000 0000 0000
> 1.007.000 C Co 0000 OK
> 1.007.000 S Co 0000 40 81 0000 0000 0000
> 1.007.000 C Co 0000 OK
> 1.007.001 C Ii 0000 No such file or directory (2)
>
> After this initial interaction it enters a loop. In this loop S-Ii and C-Ii
> are back to back.
>
> 1.007.001 S Ii 0002
> 1.007.001 C Ii 0000 No such file or directory (2)
> 1.007.001 S Ii 0002
> 1.007.001 C Ii 0000 No such file or directory (2)
This sounds like
>give me a file (the DICOM data stream)
<I don't have a file
>give me a file
<...
until eventually:
> On Windows, this loop gets broken as Ii now draws a response when the
> sensor gets x ray exposure and then Bi interaction starts:
the data stream is sent:
> 1.006.001 S Ii 0002
> 1.006.001 C Ii 0002 OK
> 00 02
> 1.006.001 S Ii 0002
> 1.006.001 C Ii 0002 OK
> 00 00
> 1.006.001 S Ii 0002
> 1.006.002 S Bi 1e00
> 1.006.002 C Bi 1e00 OK
> <snip>
> In my case even on x ray exposure the loop keeps repeating. Probably the
> above difference (gap between S-Ii and C-Ii with Ci-Cos in between) has
> something to do with it as that is the only difference left between the two
> traces (Windows and mine).
I agree. It seems quite likely to be more setup of the device.
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
Reply to: