-
Notifications
You must be signed in to change notification settings - Fork 2
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
Timing issues #6
Comments
Hey Cam - I remember this happening during development, but it was ironed out pretty quickly. I think it was an OS overhead issue. Are you running from the terminal in the OS? I think that would cause this behavior, but if you setup the autorun on boot without loading the OS GUI it should be okay. Even rebooting to terminal only would probably be enough. |
@Camac881 - Did that solve your problem? |
Hi John - Thanks for checking in on me. No, it is still acting the same. Plus I had to change the setup to run 'safe' mode on the video or I get a blank screen. I don't even get to the second series, or at least after five minutes my patience ran out and I hit escape. I get three errors; in photoButtonPress fname = takePhoto() , in takePhoto camera.capture(path) , and in camera.py in capture 'Timed out waiting for capture to end' Then it explains picamera.exc.PiCameraRuntimeError: Timed out waiting for capture to end The errors are consistent with or without the GUI. My hardware is a Raspberry Pi 2 Model B running the latest Raspbian 4.4.16-v7+, if that matters. |
Have you updated all of the packages? I'd run |
Hi John, OK I ran update and upgrade and got three minor updates. I wrote and ran the camera tests and got multiple photos to the desktop and the video file recorded and played fine. I ran it all from the GUI and the timing and screen were fine. The reason I mention the screen is that I changed the resolution from 'safe' to normal hdmi. What should I look at next? Thank you so much for helping me with this! |
Ok - I’m a bit confused. The Photo Booth program ran fine with normal HDMI? Is this the newest version of the Pi Camera? They recently increased the resolution and it could be something odd there, but I don’t think that is the most likely cause. What kind of monitor and what resolution are you using?
|
Hi John, No, the Photo Booth program only runs in safe mode. The example programs ran in HDMI. |
Have you tried changing the the resolution on line 364? |
OK, I changed the resolution to 1920 x 1080 and the program now comes up in normal mode. I don't have to change to safe mode. (Progress!) The timing is still off and it hung on the third photo. I escaped out after five minutes and got the same errors that I have been getting. Thanks for your help, I really appreciate it. |
No problem - It is progress. What power adapter are you using? This is beginning to sound like a power issue.
|
@Camac881 Any progress? |
Hi John, No, I had to give up as I was running out of time. I tried another project, PiPhoto, and that had its own set of issues, although the timing was fine. I dropped the Pi platform and went with a PC approach that went off without a hitch. |
Sorry to hear that. Since I can't reproduce it on my end, I'm going to close this, but if you run into it again and are having issues, please reopen. |
Hi John, I have built your wonderful project, coincidentally for a wedding, but I'm having an issue. Everything comes up as it should, except the countdown doesn't work correctly. The issue is random in length, but it can take from 20 seconds to a full minute to do the 5 second count. The led flashes in a random pattern with differing lengths of on and off time. I also get a capture timeout error on the third photo.
I have commented out different things and shortened some of the sleep times, but it doesn't improve. There is also about a 5 second delay for it to notice that the BRB is being pressed. I have rebuilt the flash from scratch to make sure something didn't glitch, but it didn't make any difference. Any ideas on how I can debug this?
Thanks, Cam
The text was updated successfully, but these errors were encountered: