Skip to content
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

Newbie : how does it work ? #3

Closed
gittynick opened this issue May 5, 2023 · 7 comments
Closed

Newbie : how does it work ? #3

gittynick opened this issue May 5, 2023 · 7 comments

Comments

@gittynick
Copy link

Hello

I have a synology nas with latest DSM 7.1 and a brother MFC-L7910DW. I would like to scan to my NAS so your script is a perfect fit for my needs ! Thanks for sharing :-)

Reading your instructions, i tweaked the run.sh file so to fit my config :

docker run -d -v /volume1/scanner:/scans -v script:/opt/brother/scanner/brscan-skey/script/ -e "NAME=Scanner" -e "MODEL=MFC-L2710DW" -e "IPADDRESS=192.168.1.55" --net=host brother

I then launched the script (via the "Scheduled tasks/user defined script")... but nothing happened :-/
Did i miss something obvious ?

Thanks for helping ;-)

@gittynick
Copy link
Author

A small follow-up : i managed to get around my install difficulties by using a ready-made container : https://registry.hub.docker.com/r/unverbraucht/brother-scanner

Unfortunately, I don't manage to mount my scanner directory... i tried "-v /volume1/scanner:/scans" and "-v /volume1/scanner:/root/brscan"
(FYI my docker log shows "/home/gittynick/brscan/brscan_2023-05-05-14-31-58.tif is created.")

How can i mount this brscan directory to my nas's Volume1/scanner directory ?
How can i create a PDF instead of a TIF ?

Thanks for helping ;-)

@gittynick
Copy link
Author

...I'm progressing ;-)
I mounted "-v /volume1/scanner:/home/gittynick/brscan" and can now retrieve my scans as TIFF files :-)
But still my last hurdle : how can i create a PDF file instead of a TIFF ?
Thanks for helping ;-)

@PhilippMundhenk
Copy link
Owner

Hi @gittynick and sorry for the late reply, busy days. Synology's are always a bit fiddly with Docker, as many implementation details are not standard. Nevertheless, it should work, I also run it on my DS.

On your first issue: Try building it, but don't use the run script, this is more for testing. Better set it up through the GUI. I run it through Portainer. It will then automatically start, as well (might be a dedicated option in the GUI, not sure).
But good to know someone published an image out of it, I didn't even know that!

The mointing point in your second comment (-v /volume1/scanner:/scans) looks much better. The PDFs get created automatically and should be in /scans inside the container. You may want to check your permissions, maybe the user in the container does no have write permission for the mounted folder /volume1/scanner

@gittynick
Copy link
Author

gittynick commented May 9, 2023

Ok, thanks 👍

It's strange :

  • when i mount /home/gittynick/brscan i can get the (raw ?) tiff image but the /scans folder remains empty (i browsed via the console to check)
  • when i try to directly mount /scans, the scanner gets unresponsive and does not start scanning at all (i checked that the permissions for both mounted folders and the container have read/write access - is there something in the environment variables that i'm missing ?)

Anyhow, i can live with the tiffs 😉

@PhilippMundhenk
Copy link
Owner

PhilippMundhenk commented Aug 3, 2023

Sorry @gittynick , this dropped off my radar "a little".

Not quite sure where the .tiff are coming from. The scripts use scanadf to scan .pnm files, which in turn are converted to .pdf. Did you managed to figure this out in the meantime?

@PhilippMundhenk
Copy link
Owner

Aaaah, is it possible you used the default scripts, rather than the ones in this repository? Until the current version, you had to specifically mount the given scripts into the container with -v.

I now included them in the container. Maybe use the newest version (you can now directly use the created container, see README, and don't need to manually build). This should resolve all your issues.

@PhilippMundhenk
Copy link
Owner

Closing this for inactivity. Feel free to reopen, if issues persist.

PhilippMundhenk pushed a commit that referenced this issue Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants