Skip to content
This repository has been archived by the owner on Mar 23, 2019. It is now read-only.

Sleeping 15 seconds leads to no image available to be retrieved #1

Open
roncapat opened this issue Feb 5, 2018 · 2 comments
Open

Comments

@roncapat
Copy link

roncapat commented Feb 5, 2018

Hi, I downloaded your script, and it worked on a Canon Maxify MB2350 from Ubuntu 16.04 by removing line 56. I suggest you to make a test without that line.

I'm then keen on developing full WDS support either as a standalone application or as a SANE backend (better, but much complicated). Are you still interested in WSD? Would you like to evolve your project, maybe with my support, or do you have no free time for this repo? Unless you are interested in actively developing a robust application, I'd fork, but usually I prefer to ask before declaring a repo "dead" by myself.

Thank you for the code provided, it helped me a lot to bootstrap with the basics of this protocol and general python HTTP/XML handling.

@al42and
Copy link
Owner

al42and commented Feb 23, 2018

Hi Patrick,

Yeah, you are right. I used this sleep(15) as an alternative to checking for scan progress, but it turns out just asking for the image and waiting for reply also works. Fixed it in f987a57. Thank you.

Are you still interested in WSD? Would you like to evolve your project, maybe with my support, or do you have no free time for this repo?

Unfortunately, I don't have enough time to dig deep into this whole mess of XML and SOAP right now.
I can help with some testing and stuff, but I'm unable to commit to a full-on participation :(

So far, I tried running your wsd_discovery.py, and it had some troubles working on my network: I had to increase TTL to 2 and explicitly specify an interface to use for multicasting.
I will try to send a proper patch some time next week.

@roncapat
Copy link
Author

Hi :) yes, there should be to do some work with interfaces selection and stuff like this, in fact I used my time mainly to grow the library and left the "main" routines as drafts of actual tools that need to be built in a more robust manner. I recently managed to implement almost all wsd-scan protocol, event handling included (except the runtime), and now I'm working for establishing a better API, moving things around, refactoring and tools/cli development.

Feel free to comment/submit issues/PRs of course! Testers are needed also, so if you can tell me your scanner model/vendor, and sometimes do some tests, it would be great. Wireshark dumps (I can give you a filter that works for me for easy selection of WSD only packets) and/or xml requests/response logs would be very helpful too. In my scripts, setting "debug=True" before a WSD API call will print to console requests/response pairs.

Thank you again for considering my project, and I surely look closer to the issue you have already told me :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants