I'm using a Raspberry Pi 3 Model B. I'm running Jessie and programming with Python. I have two USB devices that give me data input. They act like keyboards, "typing" numbers and then sending a "carriage return". Problem is, I need to discern which device is sending which information. Is there any wa...

Boy, the change in lens aspect between V1 and V2 sure confused matters. I was hoping for more resolution in the existing FoV, but it seems I've got effectively the same resolution, or maybe even less? Not sure. I'm finding that to get the same image results with the V2 camera, I have to crop the ima...

Maybe un-stick this, or at least describe it as the old camera board?

Love the new V2 camera, many thanks for your hard work. White balance is much better, but I'm trying to figure out how to make the use of the higher resolution in my microscope application. The PiCamera documentation (https://picamera.readthedocs.io/en/release-1.10/fov.html) did a great job of expla...

Excellent, nice and simple. Thank you Dougie. For amateurs like me, Pcmanfm is simply the default file manager that comes with Raspbian. Can someone help with my second question... Are there simple Python commands to dismount each time a picture is saved (assuming the user is going to pull the stick...

Just began using Jessie, and am happy to see simple USB memory stick functionality without complex mounting, etc. First: In my application, the user will insert a memory stick, to write a captured photo to the stick. When the stick is inserted, a dialog box pops up asking the user what to do with th...

Through trial and error, I arrived at an acceptable exposure_speed of about 15,000. Multiples of any value made no difference. As I mentioned, fixing the exposure_speed takes away much of the camera's ability to adjust to changes in lighting. Is there a way to define a minimum value, and allow the c...

OK, making progress! I queried the camera settings with a "good" and "bad" light source. With the offending LED source: shutter_speed = 0 exposure_speed = 2895 Result: preview image looks like jelly With another (badly) offending halogen source: shutter_speed = 0 exposure_speed = 1470 Result: previe...

I've eliminated RF interference as the cause. With the offending light source turned on, I can block (and unblock) the offending light from hitting the camera while leaving the source running. The effect occurs only when the light hits the camera. If I block the light (but leave the source running),...

Here's a YouTube video that better shows the effect.
http://www.youtube.com/watch?v=hzrZuNwBYCo

Thanks for your help.

Thanks for the quick response. I should have said, I'm in the US (60 Hz) Here are YouTube links to a few 5 second videos showing the effect: LED Back light plus dimmable Halogen top light: http://www.youtube.com/watch?v=abvGcqWmxPQ [Halogen toplight only, non-dimmable: http://www.youtube.com/watch?v...

I've built a microscope system based upon the PiCamera; it works very well. Problem is, when in preview mode, the rolling shutter reacts very badly with certain light sources (dimmable halogen and non-dimmable LED). Even though the image is stationary, I get a horrible swimming "jello" effect. I und...

Mystery solved... The image went into my array as BGR, and I used it as if it were RGB. The subject under the microscope was not strikingly different colors, so it wasn't obvious that it was simply a color swap.

I've created a microscope application using a Raspberry Pi 2 and a Raspberry Pi camera board. I'm programming in Python using PyGame, cv2 and picamera 1.10. Works great, with one exception. Previewing to the screen looks great, with a very responsive image, good colors and excellent reaction to chan...