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/
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
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 USB
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: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 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
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
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
17 matches
Mail list logo
