On Thu, 2012-08-30 at 10:23 +0200, Frode V. Fjeld wrote: > Louis Lagendijk <louis at fazant.net> writes: > > > I will have a look at this when I get some time. I have seen this once > > on my own scanner, but thought that the latest git version fixed it. > > This could be a timing issue that shows up on wlan only (I use a wired > > network connection). Just to be sure: did you power off/on the > > scanner? It looks as if the protocol stack in Canon devices get > > confused sometines..... > > I did have a go at debugging this myself (but I have basically zero > knowledge of sane or canon protocols), and have powercycled the scanner > many tens of times doing so. It could be wlan-specific, but like I said > I have gotten it to work fairly reliably over wlan before. I'll try > later to wire the scanner to the wlan router and see if that makes a > difference.
I found an error in reading the data from the scanner: your log was pretty clear. Thanks for that. Can you please try the latest git? Kind regards, Louis
