[sane-devel] HP 6300c with ADF, problem using ADF

[Erkki Seppala]

Hello,

I got a Hewlett Packard 6300c with automated document feeder for a
brief test run, to try it out before I shell out the cash ;). It
appears good linux-compatible ADF scanners are hard to come by these
days..

--
This is what lsusb tells me:

Bus 001 Device 011: ID 03f0:0601 Hewlett-Packard ScanJet 6300c

with some choice fields of the -v -output:

  idVendor           0x03f0 Hewlett-Packard
  idProduct          0x0601 ScanJet 6300c
  bcdDevice            1.00
  iManufacturer           1 Hewlett-Packard
  iProduct                2 HP ScanJet 6300C
  iSerial                 3 SG9AP172FKPE

and here's one line from the debug output:
[hp] sanei_hp_is_active_xpa: model=17, active_xpa=1

I'm running SANE frontend 1.0.14 and backend 1.0.17.
--

Judging from the documentation and a few posts it would seem to me it
should work. However, I am only able to scan from sources Normal and
XPA (sidenote: what is that XPA anyway?-)). The documentation states
that I should be able to select ADF when I have paper inserted, which
I have done, but it still doesn't give me the chance to choose source
ADF.

scanadf -s0 -e0 -v --source adf -d hp -o image-%04d.pbm fails with
Operation not supported.

I recompiled the backend with debug output for sane-hp (plus a few
lines to output the status code), and it gives me (first line is
output at backend/hp-option.c:895):

[hp] probe_change_doc: inquire ADF capability
[hp] scsi_flush: writing 6 bytes:
[hp]  0x0000  1B 2A 73 32 34 45                                .*s24E
[hp] sanei_hp_device_info_get: searching libusb:001:011
[hp] sanei_hp_device_info_get: check /dev/scanner
[hp] sanei_hp_device_info_get: check libusb:001:011
[hp] sanei_hp_device_info_get: searching libusb:001:011
[hp] sanei_hp_device_info_get: check /dev/scanner
[hp] sanei_hp_device_info_get: check libusb:001:011
[hp] scsi_read:  8 bytes:
[hp]  0x0000  1B 2A 73 32 34 64 30 56                          .*s24d0V
[hp] probe_change_doc: status = 0, cap = 0         adf cap query -^
                      query ok -^        ^- no such capability?
[hp] sanei_hp_optset_new: unload
[hp] probe_unload: inquire ADF capability
[hp] scsi_flush: writing 6 bytes:
[hp]  0x0000  1B 2A 73 32 34 45                                .*s24E
[hp] sanei_hp_device_info_get: searching libusb:001:011
[hp] sanei_hp_device_info_get: check /dev/scanner
[hp] sanei_hp_device_info_get: check libusb:001:011
[hp] sanei_hp_device_info_get: searching libusb:001:011
[hp] sanei_hp_device_info_get: check /dev/scanner
[hp] sanei_hp_device_info_get: check libusb:001:011
[hp] scsi_read:  8 bytes:
[hp]  0x0000  1B 2A 73 32 34 64 30 56                          .*s24d0V

Removing the check later (I just removed the code in hp_option_imm_set
that called sanei_constrain_value) or forcing the detection function
to always succeed did me little good, as the program then gave me
error 'Invalid argument' instead.

I don't think it ever reached the point where it would start checking
if there's paper in or not.

Am I to decide that the ADF module is busted (unlikely, as the
previous owner had used it with Windows), as the device apparently
states it doesn't support ADF, or that there is no support for this
particular device? I guess it is a possibility that the device did not
arrive with the ADF module, and instead the module was installed
afterwards, but I don't know how that would relate to the capability
fields and controlling the device..

Thanks for any suggestions!
--
  _____________________________________________________________________
     / __// /__ ____  __               http://www.modeemi.fi/~flux/\   \
    / /_ / // // /\ \/ /                                            \  /
   /_/  /_/ \___/ /_/\_\@modeemi.fi                                  \/