[sane-devel] Canon DR-3060
Theodore Kilgore
kilgota at banach.math.auburn.edu
Sun Sep 15 16:56:21 UTC 2013
On Fri, 13 Sep 2013, m. allan noah wrote:
> This machine is SCSI :)
Ah. Then how is one supposed to log the traffic, anyway? To my uninformed
mind, that might possibly make the problem of logging even worse.
Sorry again to hijack the thread -- and possibly to reveal my ignorance of
how to log SCSI traffic on Windows -- but how does one go about that? If
you or anyone else happens to know, perhaps a discussion of the methods
(or some pointers to appropriate web pages?) might be of general interest.
Theodore Kilgore
>
> allan
>
> On Fri, Sep 13, 2013 at 5:12 PM, Theodore Kilgore
> <kilgota at banach.math.auburn.edu> wrote:
> >
> > Hi,
> >
> > Not meaning to get in the middle here, but as I understand there is a
> > problem with logging USB traffic on recent versions of Windows.
> > Specifically, the various Free Software logging programs which used to be
> > the favorites of all of us do not work properly on anything later than
> > WinXP. I would infer that all of this traffic is now considered
> > "privileged" and/or access to it is blocked by the DRM schemes on
> > later versions of Win. There do exist logging programs, but the ones I
> > have inspected (none recently) either
> >
> > (1) do not reproduce all traffic (so obviously useless)
> >
> > Or
> >
> > (2) The program is proprietary, Windows-certified, costs a lot of
> > money, and produces logs in some special format which can only be read by
> > the same program. The log file can be copied to another computer, but its
> > format is unknown and proprietary, too.
> >
> > Feel free, anybody, to correct any of the above if the situation has
> > recently improved. But this is the way it has been for a while.
> >
> > Consequently, one really needs to keep an XP machine around and to hope
> > that the hardware comes with an XP driver. My response to the OP is
> > therefore to use an XP machine for this if it is at all possible to do so.
> >
> > Good luck.
> >
> > Theodore Kilgore
> >
> >
> > On Fri, 13 Sep 2013, m. allan noah wrote:
> >
> >> This machine comes up occasionally. Unfortunately, I don't have docs
> >> from canon, so the the protocol is reverse engineered. It is similar
> >> to other Canon DR scanners, but does not like some command that we
> >> send. Users have tried on a couple occasions to get a log of the
> >> windows driver making a scan, but every time, the logs do not contain
> >> the outgoing packets, only the scanner's response. Perhaps you will
> >> have better luck if you try?
> >>
> >> allan
> >>
> >> On Fri, Sep 13, 2013 at 4:35 AM, lelive <o.huc at info-evolution.com> wrote:
> >> > I all,
> >> > i have a problem with a CANON DR-3060 SCSI scanner.
> >> > scanimage -L is ok but when i want start the scan with command line
> >> > root at debian:~/dev/sane-backends-git20130912# scanimage
> >> > --batch="tmp/test%d.pnm" --batch-start=1 --source "ADF Front"
> >> > Scanning -1 pages, incrementing by 1, numbering from 1
> >> > Scanning page 1
> >> > scanimage: sane_start: Invalid argument
> >> >
> >> > root at debian:~/dev/sane-backends-git20130912# scanimage -L
> >> > device `canon_dr:/dev/sg2' is a CANON DR-3060 scanner
> >> >
> >> > scanimage -h :
> >> > ------------------------------------------------------------------------------------------------------------------
> >> > root at debian:~/dev/sane-backends-git20130912# scanimage -h
> >> > Usage: scanimage [OPTION]...
> >> >
> >> > Start image acquisition on a scanner device and write image data to
> >> > standard output.
> >> >
> >> > Parameters are separated by a blank from single-character options (e.g.
> >> > -d epson) and by a "=" from multi-character options (e.g.
> >> > --device-name=epson).
> >> > -d, --device-name=DEVICE use a given scanner device (e.g. hp:/dev/scanner)
> >> > --format=pnm|tiff file format of output file
> >> > -i, --icc-profile=PROFILE include this ICC profile into TIFF file
> >> > -L, --list-devices show available scanner devices
> >> > -f, --formatted-device-list=FORMAT similar to -L, but the FORMAT of the
> >> > output
> >> > can be specified: %d (device name), %v (vendor),
> >> > %m (model), %t (type), %i (index number), and
> >> > %n (newline)
> >> > -b, --batch[=FORMAT] working in batch mode, FORMAT is `out%d.pnm' or
> >> > `out%d.tif' by default depending on --format
> >> > --batch-start=# page number to start naming files with
> >> > --batch-count=# how many pages to scan in batch mode
> >> > --batch-increment=# increase page number in filename by #
> >> > --batch-double increment page number by two, same as
> >> > --batch-increment=2
> >> > --batch-prompt ask for pressing a key before scanning a page
> >> > --accept-md5-only only accept authorization requests using md5
> >> > -p, --progress print progress messages
> >> > -n, --dont-scan only set options, don't actually scan
> >> > -T, --test test backend thoroughly
> >> > -A, --all-options list all available backend options
> >> > -h, --help display this help message and exit
> >> > -v, --verbose give even more status messages
> >> > -B, --buffer-size=# change input buffer size (in kB, default 32)
> >> > -V, --version print version information
> >> >
> >> > Options specific to device `canon_dr:/dev/sg2':
> >> > Standard:
> >> > --source ADF Front|ADF Duplex [ADF Front]
> >> > Selects the scan source (such as a document-feeder).
> >> > --mode Lineart|Gray [Gray]
> >> > Selects the scan mode (e.g., lineart, monochrome, or color).
> >> > --resolution 200|240|300dpi [300]
> >> > Sets the resolution of the scanned image.
> >> > Geometry:
> >> > -l 0..215.872mm (in steps of 0.0211639) [0]
> >> > Top-left x position of scan area.
> >> > -t 0..279.364mm (in steps of 0.0211639) [0]
> >> > Top-left y position of scan area.
> >> > -x 0..215.872mm (in steps of 0.0211639) [215.872]
> >> > Width of scan-area.
> >> > -y 0..279.364mm (in steps of 0.0211639) [279.364]
> >> > Height of scan-area.
> >> > --page-width 0..255.999mm (in steps of 0.0211639) [215.872]
> >> > Specifies the width of the media. Required for automatic centering
> >> > of
> >> > sheet-fed scans.
> >> > --page-height 0..364.02mm (in steps of 0.0211639) [279.364]
> >> > Specifies the height of the media.
> >> > Enhancement:
> >> > --brightness -127..127 (in steps of 1) [0]
> >> > Controls the brightness of the acquired image.
> >> > --contrast -127..127 (in steps of 1) [0]
> >> > Controls the contrast of the acquired image.
> >> > --threshold 0..255 (in steps of 1) [inactive]
> >> > Select minimum-brightness to get a white point
> >> > Advanced:
> >> > --df-thickness[=(yes|no)] [no]
> >> > Detect double feeds using thickness sensor
> >> > --df-length[=(yes|no)] [no]
> >> > Detect double feeds by comparing document lengths
> >> > --rollerdeskew[=(yes|no)] [no]
> >> > Request scanner to correct skewed pages mechanically
> >> > --swdeskew[=(yes|no)] [no]
> >> > Request driver to rotate skewed pages digitally
> >> > --swdespeck 0..9 (in steps of 1) [0]
> >> > Maximum diameter of lone dots to remove from scan
> >> > --swcrop[=(yes|no)] [no]
> >> > Request driver to remove border from pages digitally
> >> > --stapledetect[=(yes|no)] [no]
> >> > Request scanner to halt if stapled pages are detected
> >> > --dropout-front None|Red|Green|Blue|Enhance Red|Enhance Green|Enhance
> >> > Blue [None]
> >> > One-pass scanners use only one color during gray or binary scanning,
> >> > useful for colored paper or ink
> >> > --dropout-back None|Red|Green|Blue|Enhance Red|Enhance Green|Enhance
> >> > Blue [None]
> >> > One-pass scanners use only one color during gray or binary scanning,
> >> > useful for colored paper or ink
> >> > --buffermode[=(yes|no)] [no]
> >> > Request scanner to read pages async into internal memory
> >> > Sensors:
> >> >
> >> > Type ``scanimage --help -d DEVICE'' to get list of all options for DEVICE.
> >> >
> >> > List of available devices:
> >> > ------------------------------------------------------------------------------------------------------------------
> >> >
> >> > Can you help me to solve this problem please ?
> >> >
> >> > Olivier
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context: http://sane.10972.n7.nabble.com/Canon-DR-3060-tp18023.html
> >> > Sent from the SANE - Dev mailing list archive at Nabble.com.
> >> >
> >> > --
> >> > sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
> >>
> >>
> >>
> >> --
> >> "The truth is an offense, but not a sin"
> >>
> >> --
> >> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
> >>
>
>
>
> --
> "The truth is an offense, but not a sin"
>
More information about the sane-devel
mailing list