FYI: The last time I tried to use it was Sept of 2016. It functioned on
this debian linux machine at that time using SANE.
On 2/9/23 14:24, Mike Hansen wrote:
I am head of development at Ambir, the manufacturer of this scanner.
That model has been out of production for over a decade. It’s likely
the unit is EOL and that clicking you are hearing is coming from the
motor. There are no belts, only gears in the unit and sure it’s
possible the gears could be broken(not sure we’ve ever seen this
failure mode) but more likely the motor is EOL.
If the SANE driver worked for it in the past and it’s not working now,
it’s an EOL unit. The control board is over a decade old and the
SANE code is likely to be the same or older.
Also note that the SANE code did not come from Ambir nor do we endorse
or support SANE development on those models. I know that we have had
discussions in the past about supporting SANE with the current models
and may do so in the future.
I am supplying the above information so that you do not continue to
put effort into the codebase for that model. Also, if you want to
check if the unit is EOL you are free to download the Windows drivers
from docketport.com.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows
*From: *Ralph Little <mailto:[email protected]>
*Sent: *Thursday, February 9, 2023 2:13 PM
*To: *Miss Tori <mailto:[email protected]>
*Cc: *[email protected]
*Subject: *Re: [sane-devel] DocketPORT 487 - Making loud noises
Hi,
On Thu, Feb 9, 2023 at 11:07 AM Miss Tori <[email protected]> wrote:
Update to my mailing below (I deleted it before it was approved to
the list)....
It definitely has to do with what's going on during the sane_read
API function.
If I issue scanimage -T, it will start clicking instantly
There are a couple of things that I can think of:
1 - The scan head is hitting the end of travel and is slipping the
belt or gear, or
2- Whatever motor settings being specified are out of spec for the motor.
Can you confirm is this happens when the scan head is at the end of
travel?
If not, then I suspect that the motor is having some problems with the
settings used by the backend to drive the motor.
Cheers,
Ralph
