Here is a new replacement patch for DR-9050C support.
- It detects the 9050C if you put option model-name DR-9050C in canon_dr.conf;
- It will print a warning to stderr (DBG(0)) if it detects a DR-9050C
in stand-by mode;
- Updated sane-canon_dr.man to mention stand-by mode problems and that
the 75
I'm giving up on the wake from standby mode problem for now. I am
unable to provoke this problem in my application. What's more, if one
adds paper to the scanner in bin, the scanner comes out of standby
mode by itself. And this is what an operator would normally do before
starting a scan.
Anoth
Going through the unsuspend-4.pcap, I see the following:
INQUIRY
INQUIRY
INQUIRY
INQUIRY
TEST_UNIT_READY_code
SEND_code S_LUT_id_unk1 = 0x84
OBJECT_POSITION_code OP_Feed
OBJECT_POSITION_code OP_Feed
0xc5 == ???
TEST_UNIT_READY_code
SEND_code S_LUT_id_unk1
OBJECT_POSITION_code OP_Feed
OBJECT_POSIT
Here are some pcaps of the Windows drivers getting the scanner out of
suspended mode.
http://pied.nu/Sane/
It appears that t10.org no longer allows free access to draft
documents. I am sure some other site will have a cached copy. What you
are looking for is the SCSI-2 spec, it is not scanner specific, but
contains scanner commands. Also, you might find some useful info if
you google for "fujitsu scanne
BTW, I'm searching for "scsi scanner protocol" and variants and
finding nothing useful about the protocol. What is the protocol
definition called?
Here are some pcaps of Capture Perfect sending a cancel command to the scanner :
http://pied.nu/Sane/canon_dr-20120822-a.tar.gz
-Philip
I've tested my patch for -l, -t, -x, -y. It works. Included is a
diff against 1.0.22.
I do notice that when scanning a batch of pages, the scanner pauses
and clicks between each sheet. I suspect this is an artifact of how
scanimage is written.
I'm going to work on the un-suspend problem. The
On Tue, Aug 21, 2012 at 2:44 PM, m. allan noah wrote:
> It is quite possible that there is some option in the driver which is
> on by default, which requires high res or high depth scans.
> Particularly automatic deskew or edge detection type things.
It was late at night and I was pretty much out
It is quite possible that there is some option in the driver which is
on by default, which requires high res or high depth scans.
Particularly automatic deskew or edge detection type things.
It might be possible to use your modified version of sane to see if
the scanner complains when you try to c
On Fri, Aug 17, 2012 at 2:02 PM, Philip Gwyn wrote:
>
> And yes, I figured the Windows driver would be better. I've been resisting
> setting up VirtualBox and a Windows VM because I dislike Windows and it seems
> like an annoying level of effort. I'm going to give USBlyser a spin first.
I tr
On Fri, Aug 17, 2012 at 1:42 PM, m. allan noah wrote:
> It is fairly normal for low-end scanners to do many features in
> software. Given the price of the scanner in question, i would expect
> it to be a little smarter than that. The size of your pcap files
> should vary as you change the x/y val
On Fri, Aug 17, 2012 at 1:37 PM, Philip Gwyn wrote:
> On Fri, Aug 17, 2012 at 1:30 PM, m. allan noah wrote:
>>
>> yes- but more likely that the driver does not send set_window if you
>> don't change any of the params in it. you might need to power cycle
>> the scanner each time.
>
>
> But I do ch
On Fri, Aug 17, 2012 at 1:30 PM, m. allan noah wrote:
> yes- but more likely that the driver does not send set_window if you
> don't change any of the params in it. you might need to power cycle
> the scanner each time.
>
But I do change the params for resolution, mode etc. Without a power
cycl
On Fri, Aug 17, 2012 at 1:12 PM, Philip Gwyn wrote:
>
>
> On Fri, Aug 17, 2012 at 7:54 AM, m. allan noah wrote:
>>
>> The mode/res/size go down to the scanner in the set window command,
>> 0x24. That command is fairly standard across SCSI scanners of all
>> brands.
>
>
> That's what's so strange.
On Fri, Aug 17, 2012 at 7:54 AM, m. allan noah wrote:
> The mode/res/size go down to the scanner in the set window command,
> 0x24. That command is fairly standard across SCSI scanners of all
> brands.
That's what's so strange. There are no 0x24 commands in the pcaps. Is it
possible for wires
The mode/res/size go down to the scanner in the set window command,
0x24. That command is fairly standard across SCSI scanners of all
brands. The 0xe5 is probably only going to change with more esoteric
options, like buffering or multifeed or staple detection. The
canon-provided sane driver may not
OK, now I've looked at the diffs. And I can't figure out what's going on.
The E5 blocks never change. The only difference between all the
resolutions and modes is that sometimes 28 (READ) command changes (read
length).
But the scanner is sending more or less data depending on the resolution,
I poked around some more. I figured out that the binary driver couldn't
open its config file which was why --Size wasn't working.
Here's another batch of tests, where I try different page sizes.
http://pied.nu/Sane/canon_dr-20120816-1115.tar.gz
It seems that --Size and --resolution will not
On Thu, Aug 16, 2012 at 9:05 PM, m. allan noah wrote:
> Wireshark makes things a little more difficult, because it shows all
>
the low level USB stuff, that really does not matter to us. So, you
> have to learn to ignore every other packet in those logs, and the
> first 0x40 bytes of the packets
Thanks for the traces, Philip. I have had sporadic reports of attempts
to use this scanner, but no-one has provided such detailed info.
Basically, the Canon DR series machines are scsi over usb. We add a 12
byte header to a normal scsi command. So, you can download the scsi
spec from many places o
This is annoying: To get the most recent wireshark working, I moved the dev
to a machine with CentOS 6. But it only has USB 1.0 and only works in
32bits. However, it doesn't exhibit the problems I'm having with Canon's
binary blob, specifically not waking up from stand-by mode.
Pcap output of a
Hello,
I have a Canon DR-9050C scanner. The canon_dr driver recognises it, but
can't access it. I see some activity in December about this, but nothing
seems to have been resolved and I see no related patches in GIT.
I also have a binary driver from Canon that my supplier found. This is a
pack
Ok I solved the problem of the installation, now the scanner works with
the following commands, but only if I start xsane as root. Omitting
this, returns this error when I start xsane from a terminal
(xsane:9913): Gtk-WARNING **: GtkSpinButton: setting an adjustment with
non-zero page size is d
Those are warnings from XSane, which has some programming errors. You
could contact the developer about those, or perhaps upgrade to a later
version and see if they are fixed.
The permissions issue is caused by udev or hal or whatever your distro
uses to allow access to hardware. It does not know
In /etc/sane.d/.dll.conf "canon_dr" is listed,
The result of command SANE_DEBUG_DLL=255 scanimage -L 2>9050.log on
terminal is
sudo SANE_DEBUG_DLL=255 scanimage -L 2 > 9050.log
[sanei_debug] Setting debug level of dll to 255.
[dll] sane_init: SANE dll backend version 1.0.12 from sane-backends 1.
"/usr/local/etc/sane.d/dll.d"
you have two copies of sane installed, and the one in /usr/local is
being used, but it has no config files. I would remove that copy, and
re-configure with the proper arguments to overwrite your existing
copy. Something like:
./configure --prefix=/usr --sysconfdir=/e
Mmh, it's same.
The log file is attach.
Luigi
Il 19/11/2010 13:33, m. allan noah ha scritto:
> Ok- as root, run this:
>
> SANE_DEBUG_CANON_DR=30 scanimage -L 2>9050.log
>
> then send 9050.log to the list.
>
> allan
>
> On Fri, Nov 19, 2010 at 2:03 AM, Luigi Carbone
> wrote:
>> With a privilege
The canon_dr backend is not enabled. check /etc/sane.d/dll.conf, and
make sure 'canon_dr' is listed there.
If it is listed, then try this:
SANE_DEBUG_DLL=255 scanimage -L 2>9050.log
and send that log.
allan
On Fri, Nov 19, 2010 at 7:56 AM, Luigi Carbone wrote:
> Mmh, it's same.
>
> The log fi
With a privileges root, this is the result
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ,
Ok- as root, run this:
SANE_DEBUG_CANON_DR=30 scanimage -L 2>9050.log
then send 9050.log to the list.
allan
On Fri, Nov 19, 2010 at 2:03 AM, Luigi Carbone wrote:
> With a privileges root, this is the result
>
> No scanners were identified. If you were expecting something different,
> check tha
Hi all,
I have problem with scanner canon dr-9050C, i have ubuntu 10.04 and
installated driver san version 1.0.21.
I have configured file canon_dr.conf so
# DR-9050C
usb 0x1083 0x1622
the command lsusb returns
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID
as root, run the following command, and send output to us:
scanimage -L
allan
On Thu, Nov 18, 2010 at 7:57 AM, Luigi Carbone wrote:
> Hi all,
> I have problem with scanner canon dr-9050C, i have ubuntu 10.04 and
> installated driver san version 1.0.21.
>
> I have configured file canon_dr.conf s
33 matches
Mail list logo
