[sane-devel] HP Scanjet 3690 support
Hi Did you try sniff-usb 1.8 See http://benoit.papillault.free.fr/usbsnoop/index.en.php Great Idea!! This works perfectly and I can get all the transaction even during and after the previsualisation scan I put here the log (in ascii format this time) of the initialisation of the scanner : usbsnoop_init.log and of a session from initialisation to the and of the preview scan usbsnoop_preview.log.gz (careful, it is 5Mo compressed) I also try to play with sane-find scanner log_sane_find_scanner is the original output log_sane_find_scanner_modify is a bad hack where I remove the return 0; lines in check-usb-chip for the check_gl646 function Don't know if it can give information but it does not seems to say it can not read or write the registers If you have any idea or comments... Mike
[sane-devel] HP Scanjet 3690 support
Hi The logs are in http://www.alezan.org/hp3670/, in SnoopyPro binary format. I tried to use usblogdump in Linux but it doesn't work very well for me. I had to analyze them in Windoze using SnoopyPro. I'll check later. I don't have a working Windows or WINE installation currently. sorry about that, I manage to export once in xml format, but do not manage anymore??? I tried also to use sniffusb-0.13, but the debugger (dbview) failed to connect (can not contact driver???). Maybe because I am using windows XP Home, does someone know a workaround? Another usb sniffer? You can try that for testing. But this can't be used in the published version because control messages like that will confuse non-gl646 scanners. That's the reason we use the descriptor to identify the chipset first and then send specific commands. That's not absolutely safe either but better then writing directly. I will try to test this to see if we can get some informations... Mike
[sane-devel] HP Scanjet 3690 support
On Wed, 2004-01-21 at 09:50, Mickael Profeta wrote: Hi The logs are in http://www.alezan.org/hp3670/, in SnoopyPro binary format. I tried to use usblogdump in Linux but it doesn't work very well for me. I had to analyze them in Windoze using SnoopyPro. I'll check later. I don't have a working Windows or WINE installation currently. sorry about that, I manage to export once in xml format, but do not manage anymore??? I tried also to use sniffusb-0.13, but the debugger (dbview) failed to connect (can not contact driver???). Maybe because I am using windows XP Home, does someone know a workaround? Another usb sniffer? Did you try sniff-usb 1.8 See http://benoit.papillault.free.fr/usbsnoop/index.en.php -- -- m.vr.gr. Gerard Klaver
[sane-devel] HP Scanjet 3690 support
Hi, On Wed, Jan 14, 2004 at 11:44:06PM +0100, adria...@users.sourceforge.net wrote: Henning, could you take a look to the hp3670 SnoopyPro logs? It seems to follow the low level protocol of the gl646; at least the protocol in genesys_bulk_write_register() (genesys_low.c:131): outdata[0] = BULK_OUT; /* 0x01 */ outdata[1] = BULK_REGISTER; /* 0x00 */ outdata[2] = 0x00; outdata[3] = 0x00; outdata[4] = (size 0xff); /* length of the bulk data stuff */ outdata[5] = ((size 8) 0xff); outdata[6] = ((size 16) 0xff); outdata[7] = ((size 24) 0xff); If that were all that's similar I wouldn't be sure. I think I have seen SCSI-over-USB like protocols that are similar. Are the values used for the actual control message the same (they can be found i the setup packet)? Do the register numbers and values make sense according to the gl646 spec? The logs are in http://www.alezan.org/hp3670/, in SnoopyPro binary format. I tried to use usblogdump in Linux but it doesn't work very well for me. I had to analyze them in Windoze using SnoopyPro. I'll check later. I don't have a working Windows or WINE installation currently. So maybe if sane-find-scanner.c ignores device descriptors and just probe the gl646 protocol using the present USB endpoints it will tell us if really HP3690, HP2300, HP2400 and maybe other scanners are based in such chipset? You can try that for testing. But this can't be used in the published version because control messages like that will confuse non-gl646 scanners. That's the reason we use the descriptor to identify the chipset first and then send specific commands. That's not absolutely safe either but better then writing directly. Bye, Henning
[sane-devel] HP Scanjet 3690 support
adria...@users.sourceforge.net wrote: Hi! Henning, could you take a look to the hp3670 SnoopyPro logs? It seems to follow the low level protocol of the gl646; at least the protocol in genesys_bulk_write_register() (genesys_low.c:131): outdata[0] = BULK_OUT; /* 0x01 */ outdata[1] = BULK_REGISTER; /* 0x00 */ outdata[2] = 0x00; outdata[3] = 0x00; outdata[4] = (size 0xff); /* length of the bulk data stuff */ outdata[5] = ((size 8) 0xff); outdata[6] = ((size 16) 0xff); outdata[7] = ((size 24) 0xff); The logs are in http://www.alezan.org/hp3670/, in SnoopyPro binary format. I tried to use usblogdump in Linux but it doesn't work very well for me. I had to analyze them in Windoze using SnoopyPro. So maybe if sane-find-scanner.c ignores device descriptors and just probe the gl646 protocol using the present USB endpoints it will tell us if really HP3690, HP2300, HP2400 and maybe other scanners are based in such chipset? I know this format. It's also used in some other USB scanners to start bulk transfers for image data (haven't been able to look at the other logfiles, they're binary, do you have text files?). You may have some luck searching the archives for canon 630u, hewlett packard hp2300c, hp3300c, hp3400c, hp4300c, pacific image electronics primefilm 1800i, agfa snapscan touch. There are some perl-scripts floating around that can do simple analysis of the original USB snoopy text files, to make them much more readable. I also have a modified version of the original snoopy that does not log USB bulk transfer contents, thereby preventing log overflow. Bertrik
[sane-devel] HP Scanjet 3690 support
--- Henning Meier-Geinitz henn...@meier-geinitz.de wrote: If it is not yet upported is there anything I can do to analize it and (with your help) create a specific configuration for it? (please note that I'm not a C/C++ programmer) Have a look at this page: http://www.sane-project.org/contrib.html and report all the details you can find to us. I just did it, following your suggestiojn. I was not able to findout the chipset... how can I do it without opening it? I can see a couple of chips from the glass: one of it has Elite MT written on it.. is it the right one? Maybe it's possible to find out the chipset used that way. please give me other advices to identify the chipset. regards, Timur __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
