Difference between revisions of "AcerScan 620UT"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(now using internal link for drivers)
(a bit of clarification from recent experience)
Line 6: Line 6:
 
# Get a copy of the scanner's driver (for any OS, as far as I can tell). This will contain .bin files, which are the firmware for various versions of the scanner. (Ours was U64V120.bin.)
 
# Get a copy of the scanner's driver (for any OS, as far as I can tell). This will contain .bin files, which are the firmware for various versions of the scanner. (Ours was U64V120.bin.)
 
# Stash all the .bin files (or, if you know which one is the right one, just that one) in /usr/share/sane/snapscan
 
# Stash all the .bin files (or, if you know which one is the right one, just that one) in /usr/share/sane/snapscan
# edit /etc/sane.d/snapscan.conf so that the "firmware" line refers to the .bin file which is correct for your scanner. If you don't know which one, then try each one -- make the edit, save snapscan.conf, run [[sane-find-scanner]] and then:
+
# edit /etc/sane.d/snapscan.conf so that the "firmware" line refers to the .bin file which is correct for your scanner.  
<bash>scanimage -x 100 -y 100 --format=tiff >image.tiff</bash> When this command doesn't give an error, you've got the right one. (There may be other steps to take in between trying each firmware, possibly turning the scanner off, but I seem to remember that it just started working when I found the right .bin file.)
+
#* If you don't know which one, then try each one -- make the edit, save snapscan.conf
 +
#* After modifying the snapscan.conf file, you will probably need to turn the scanner off and then back on again (this tells SANE that it needs to re-send the firmware).
 +
# Run [[sane-find-scanner]] to see if communication with the scanner has been established.
 +
# If that seems to have happened, then run this as a quick test:
 +
#: <bash>scanimage -x 100 -y 100 --format=tiff >image.tiff</bash> When this command doesn't give an error, you've got the right one, and regular GUI scanning applications should now work.
 
==Files==
 
==Files==
 
* [[:File:AcerScan drivers.tar.gz]]: all .bin firmware files included in the driver
 
* [[:File:AcerScan drivers.tar.gz]]: all .bin firmware files included in the driver
 
==Links==
 
==Links==
 
* <s>[http://www.benq.us/support/downloads/downloads.cfm?product=161&page=downloads&dtype=D manufacturer's drivers] at [[Benq]]'s web site</s> as of 2010-06-19, they don't seem to be available from Benq; I've uploaded them [[:File:AcerScan drivers.tar.gz|here]]
 
* <s>[http://www.benq.us/support/downloads/downloads.cfm?product=161&page=downloads&dtype=D manufacturer's drivers] at [[Benq]]'s web site</s> as of 2010-06-19, they don't seem to be available from Benq; I've uploaded them [[:File:AcerScan drivers.tar.gz|here]]

Revision as of 01:30, 5 March 2017

Overview

The AcerScan 620UT is a color USB page scanner.

Linux

It can be made to work with Linux, although some tinkering is required because of the proprietary firmware driver file which has to be uploaded each time the scanner is turned on. The firmware file must be copied from the manufacturer's driver set and SnapScan (Linux scanning software) must be configured to upload it, which fortunately is pretty easy.

  1. Get a copy of the scanner's driver (for any OS, as far as I can tell). This will contain .bin files, which are the firmware for various versions of the scanner. (Ours was U64V120.bin.)
  2. Stash all the .bin files (or, if you know which one is the right one, just that one) in /usr/share/sane/snapscan
  3. edit /etc/sane.d/snapscan.conf so that the "firmware" line refers to the .bin file which is correct for your scanner.
    • If you don't know which one, then try each one -- make the edit, save snapscan.conf
    • After modifying the snapscan.conf file, you will probably need to turn the scanner off and then back on again (this tells SANE that it needs to re-send the firmware).
  4. Run sane-find-scanner to see if communication with the scanner has been established.
  5. If that seems to have happened, then run this as a quick test:
    <bash>scanimage -x 100 -y 100 --format=tiff >image.tiff</bash> When this command doesn't give an error, you've got the right one, and regular GUI scanning applications should now work.

Files

Links