[sane-devel] usbsniff

[Roland Graf]

Hello Pierre,

I tried the testprog under root. I think in root I must have the permission 
for the device. I controlled the the line 86 for the device and vendor ID. The 
vendor ID and the device ID are correct.

Every time the same error: Device not found

I have an other question. For thus I programmed in the past only under ATARI 
ST 520 and Windows on programming environments and under Linux only some 
shell-scripts or ebuilds is there under Linux the possibility to do a line by 
line debugging like in Turbo Pascal or Visual Basic for applications? Can you 
give me some hint?

I had in past errors that my E-Mail didn't reach you directly. Please let me 
know whether you read my mails from pierre at pirsoft.dnsalias.org or sane-
devel at lists.alioth.debian.org?

Last but not least I have a final question. Are you reachable maybe under IRC 
or VoIP? In special cases we may contact us directly, if you agree.

Thanks 

Roland
















Am Sonntag 08 Februar 2009 16:49:12 schrieb Pierre Willenbrock:
> Roland Graf schrieb:
> > Hallo Pierre,
> >
> > the testprogram gives me only an:
> >
> > roland roland # /home/roland/Doku/G4010/testprog
> > Fatal: Device not found!
> > roland roland #
> >
> > With #lsusb I can see the scanner. I
> > Best regards
> >
> > Roland
>
> Hello Roland,
>
> either my guess for your device-id was wrong(0x03f0:0x4505, see
> usb_con.c:86), or you are lacking permissions to access the device.
>
> Regards,
>   Pierre
>
> > Am Samstag 07 Februar 2009 21:55:11 schrieben Sie:
> >> Roland Graf schrieb:
> >>> Hallo Pierre,
> >>>
> >>> was it possible to decode my log?
> >>>
> >>> Thanks
> >>>
> >>> Roland
> >>
> >> Hello Roland,
> >>
> >> try this "small" program. If i got it right, this should replay your
> >> usbsniff. It will dump any data received on stdout, so it should
> >> probably be redirected into a file. All you need is a working libusb and
> >> compilation environment, compilation is done by the usual "make".
> >>
> >> A quick way to view the resulting data is to convert it into a
> >> portable-gray-map(.pgm) by prepending "P5 <width> <height> 255 " or "P5
> >> <width> <height> 65535 " (note the final space), depending on whether
> >> you want to see the data interpreted as 8 bit or 16 bit. If the byte
> >> order is not correct for 16 bit, just add another space before the
> >> "real" data(the least significant byte can be ignored for now). For
> >> <width> and <height> you need to experiment. "xv" and "display" are able
> >> to show 16 bit pgm.
> >>
> >> I did not have a close look at the actual mode the gl843 is programmed
> >> to, but for cis sensors, color information is transfered in three lines,
> >> each line taken with one of the three led colors, for ccd sensors the
> >> usual per pixel color information is used.
> >>
> >> Regards,
> >>   Pierre