Dear Sane developers > Make some scans with the scanner on windows, and capture the USB > packets with wireshark. Then put the wireshark logs up on the web for > others to look at, while you attempt to make sense of them too :)
Thanks Allan for your advice. I've finally managed to capture some logs. I'm trying to make sense of them now using Wireshark. Any help/pointers would be much appreciated, as I'm pretty new to this. I've uploaded them to here: https://mdvthu.com/files/Scanner_output.pcap https://mdvthu.com/files/Scanner_output.tif Best wishes Mark > > On Fri, Oct 13, 2017 at 12:46 PM, Mark Thurston <m...@mdvthu.com> wrote: > > Dear developers > > > > I've got an obscure scanner which I really need to get working and I'm > > prepared to get my hands dirty but I can't find much documentation. > > > > Any tips/pointers would be very helpful. > > > > It's a Vidar Diagnostic Pro digitizer -- used in radiology to scan X-rays > > from old radiographic film. As you can imagine, it's quite a niche > > product. > > > > Output: > > > > # dmesg > > [ 179.813929] usb 1-2: USB disconnect, device number 6 > > [ 181.783329] usb 1-2: new high-speed USB device number 7 using xhci_hcd > > [ 181.933595] usb 1-2: New USB device found, idVendor=0c58, > > idProduct=0100 > > [ 181.933599] usb 1-2: New USB device strings: Mfr=1, Product=2, > > SerialNumber=3 > > [ 181.933602] usb 1-2: Product: VIDAR Film Digitizer > > [ 181.933605] usb 1-2: Manufacturer: VIDAR > > [ 181.933607] usb 1-2: SerialNumber: 300000 > > > > ~ # sane-find-scanner > > > > # sane-find-scanner will now attempt to detect your scanner. If the > > # result is different from what you expected, first make sure your > > # scanner is powered up and properly connected to your computer. > > > > # No SCSI scanners found. If you expected something different, make sure > > that > > # you have loaded a kernel SCSI driver for your SCSI adapter. > > > > found USB scanner (vendor=0x0c58 [VIDAR], product=0x0100 [VIDAR Film > > Digitizer]) at libusb:001:007 > > # Your USB scanner was (probably) detected. It may or may not be > > supported by > > # SANE. Try scanimage -L and read the backend's manpage. > > > > # Not checking for parallel port scanners. > > > > # Most Scanners connected to the parallel port or other proprietary > > ports > > # can't be detected by this program. > > > > unfortunately it is not listed on # scanimage -L > > > > If I make any progress (with or without help), I would like to submit my > > work back to the project. I have some experience in C and Python and am > > prepared to learn as needed. > > The alternative is a very expensive proprietary closed source vendor > > solution with unreliable support and a poor security update record. > > > > Best wishes > > > > Mark > > > > > > > > > > > > -- > > sane-devel mailing list: sane-devel@lists.alioth.debian.org > > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > > Unsubscribe: Send mail with subject "unsubscribe your_password" > > to sane-devel-requ...@lists.alioth.debian.org > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" > -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
