This is something else what distinguishes a good hardware implementation
of a scanner from a lousy one:
A good implementation should not allow moving beyond the end by either
a hardware switch sensing the end-position and stopping the motor this
way, or by a current limit or friction clutch that does not allow
desctructive forces to take effect on the mechanical construction.
Apart from this, there must be a software limitation in the firmware.
You may try to insist on a case of warranty (I don't think that
this case would have been absolutely avoidable with their Windows
software), or try to look yourself if you can find a sensor
(mechanical or optical switch) that may have been in a different
position before. (try to reconstruct the damage case with the
scanner switched off and moving the scanning head manually).
Good Luck !
Andreas.
On Thu, 8 Oct 1998, Anthony Mallet wrote:
> Hi,
> I'm experiencing a (very) strange behavior with my Mustek 1200SP (rev 1.06)
> and sane 0.73 (under linux 2.1.117). I'm not sure if it is a software or a
> hardware bug.
>
> First, everything was ok (cool, isn't it ;)
>
> Two days ago, I began a scan, and the head went too far away (though it
> NEVER EVER did that before, and I did NOT CHANGE ANYTHING to my
> box...). The mustek began to make frightening noise and I swtiched it off
> immediately.
>
> Since that day, the scanning-head does NOT RETURN to the HOME POSITION
> after a scan (but everything else is ok) and I must switch the mustek off
> and on.
>
> So, it looks like a hardware bug since I did not change any software, but
> I'm not sure there is a 'specialized' hardware in the scanner that only
> controls the 'home return' of the head. I sent a mail to mustek-support
> (europe) but they do not seem to answer it, so I'm a bit lost...
>
> If anyone has an idea...
> Anthony
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com