duerig
commented
6 years ago While there will always be some camera failures, this is more frequent than normal. Just to double check, are you using a USB hub or similar device? I have seen intermittent problems like this on setups that use a USB hub.
I will look through the log and see if I can offer more things to try.
On Sun, Jan 14, 2018, at 12:18 PM, meelash wrote:
My workflow is interrupted with what, I think, is a non ideal frequency of errors during scanning. Here is the log file from a recent scan of approximately 600 pages: https://gist.github.com/meelash/d449ec023bec0bfe9ce5f81861185d52> Errors occur after 45 scans, 80 scans, 10, 27, 16, 25, 74, and 19 scans for an average of one error about every 37 scans. (I'm only getting 433 pages/hour in this run, although it included time taking pictures of the error messages and trying different procedures for clearing errors)> Again, my first question is, are these results typical? Is this something with my setup, or is it a general problem with pi-scan or chdk that I can help to diagnose and fix?> As far as I can see the modes of failure appear to be multiple. There are some times when I get a "Got empty data back when capturing" and I can just hit "ok," rescan, and continue although it seems to have a high likelihood of reoccurring shortly thereafter and requiring more serious measures. Turning the camera in question off and on again seems to always allow me to continue, but sometimes restarting pi- scan, without touching the cameras seems to work. The other evidence I have of multiple modes of failure is the different symptoms on the camera displays. Here are some samples (I can match these up with times in the logs if necessary):> An early error resulted in this memory card error (but I'm not sure if that was there on the initial error, or as a result of restarts and retries to attempt to get past the error without restarting the camera) img_3245> Sometimes the error would result in the screen of the camera displaying L3 or L2:> img_3247 img_3254 I think in these cases, it would seem like chdk was gone, and pressing the menu button would bring up the normal menu instead of the chdk alt menu:> img_3255 A restart of pi-scan would return the camera to chdk mode.
There was an error that resulted in the camera becoming completely unresponsive, with the screen black:> img_3248 Obviously, that required restarting the camera to fix.
Then, there was an error where the camera would make the noise of shutter firing and the display of the camera would show this menu: img_3245> So, assuming these are individual issues and not all a result of some shortcoming in my system setup, any ideas which one might be addressable first/easiest? And are these problems related to pi-scan, or chdk?> If related to chdk, then I guess the question is whether they are typical for the performance of other applications of chdkptp or not.> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub[1], or mute the thread[2].>
Links:
meelash
rramphal
My workflow is interrupted with what, I think, is a non ideal frequency of errors during scanning. Here is the log file from a recent scan of approximately 600 pages: https://gist.github.com/meelash/d449ec023bec0bfe9ce5f81861185d52 Errors occur after 45 scans, 80 scans, 10, 27, 16, 25, 74, and 19 scans for an average of one error about every 37 scans. (I'm only getting 433 pages/hour in this run, although it included time taking pictures of the error messages and trying different procedures for clearing errors)
Again, my first question is, are these results typical? Is this something with my setup, or is it a general problem with pi-scan or chdk that I can help to diagnose and fix?
As far as I can see the modes of failure appear to be multiple. There are some times when I get a "Got empty data back when capturing" and I can just hit "ok," rescan, and continue although it seems to have a high likelihood of reoccurring shortly thereafter and requiring more serious measures. Turning the camera in question off and on again seems to always allow me to continue, but sometimes restarting pi-scan, without touching the cameras seems to work. The other evidence I have of multiple modes of failure is the different symptoms on the camera displays. Here are some samples (I can match these up with times in the logs if necessary):
An early error resulted in this memory card error (but I'm not sure if that was there on the initial error, or as a result of restarts and retries to attempt to get past the error without restarting the camera)
Sometimes the error would result in the screen of the camera displaying L3 or L2:
I think in these cases, it would seem like chdk was gone, and pressing the menu button would bring up the normal menu instead of the chdk alt menu:
A restart of pi-scan would return the camera to chdk mode.
There was an error that resulted in the camera becoming completely unresponsive, with the screen black:
Obviously, that required restarting the camera to fix.
Then, there was an error where the camera would make the noise of shutter firing and the display of the camera would show this menu:
So, assuming these are individual issues and not all a result of some shortcoming in my system setup, any ideas which one might be addressable first/easiest? And are these problems related to pi-scan, or chdk?
If related to chdk, then I guess the question is whether they are typical for the performance of other applications of chdkptp or not.