-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scanning initiated by scanner buttons starts with a great delay #31
Comments
Sorry if I misunderstood. But you mean that when you trigger the scan directly on the device, the delay occurs? |
Exactly: The delay of cca 30 seconds occurs when I press the scan button directly on the printer. |
My apologies for the late reply, I had a bit of a busy week. tl;dr: No obvious solution, sorry. Interesting...I do observer rather long delays as well, when using the button, especially when using the flatbed, rather than the auto feeder. In my case, this is 8s though, which is much more bearable. With ADF, it is closer to 2s. Thus, 30s is really an extremely long time. I do call the scan commands twice, with some sleep padding, as we otherwise observed issues on some printers, but once scanimage is triggered, timing is outside of my sphere of influence. I have not reverse engineered the scanner driver, it is very much possible, there are issues there. I also don't want to exclude the possibility that the current configuration in this repo is not ideal for every scanner. It is posible that one could reach faster scanning times with better settings, as you did above. A few things I noticed:
Let me think about this a little more, but ad the moment, I don't quite see an easy solution to this, unfortunately... |
out of curiosity: Which scanner are you using? Workflows and buttons seem very different from mine. |
Hi, |
Hi,
The scanner is connected via ethernet cable.
When I use in
scripts/scantofile.sh
:the initiation of the scanning has a great delay of cca 30 seconds ("Connecting to PC" is displayed on the scanner LCD after pressing the scan button on the scanner):
Scanning of subsequent pages within the batch starts promptly after button press (Next = up arrow key on the scanner).
When I run the above
scanimage
command from terminal inside the docker container (i.e. direct scanning initiated from computer), it takes 9 seconds to actually start the scanning. The scanning itself takes just a few seconds as it is 150 dpi only.As per above log, the delay between the scanner button press (19:32:54) and the scanning (cca 19:33:34 less few seconds spent on actual scanning) looks like 3 times the 9 seconds delay. (Could it be that SANE commands are triggered three times for any reason.)
Any ideas what might be wrong with
brother4
driver orbrscan-skey
and if it can be setup to run with shorter initial delay? It makes it impractical to use the scanner buttons now...BTW, I tried to run
scanimage
in terminal inside the container with--device-name=escl:http://10.11.13.11:80
instead and the scanning started immediately without any delay.Unfortunately, when I tried to use this device name in the script, the delay of cca 10 seconds is still there and the command fails eventually (driver is probably not supported by
brscan-skey
?):EDIT: Clarifying that the delay 30 secs is when using the physical scan button on the scanner.
The text was updated successfully, but these errors were encountered: