STICKY: Foundation (old) Camera Board information

[jamesh]

The camera is already fixed focus.

[0xFF]

The camera lens is fixed focus.

[peepo]

there is no autofocus,
as focus is fixed.

lens can be physically unscrewed, once glue is removed, to enable macro facility.

[RaTTuS]

there is no autofocus,
as focus is fixed.

lens can be physically unscrewed, once glue is removed, to enable macro facility.

and works very well

see

for a still that I did

[strobie]

Camera fans might be interested in this article I've just posted, documenting a project using the Pi as a secure webcam: http://franklinheath.co.uk/2013/08/16/r ... e-version/

[SnowLeopard]

Is there a roadmap and known issues list somewhere?
How are the items on those lists (whether explicit or not) prioritized? Are things that can only be done in the closed GPU firmware given higher priority than things that can be done by anyone with access to other sources (ie userland)?

Specifically, I am interested in higher frame rates for video recording.

[jamesh]

Git hub has the issue list.

The order in which they get done is whatever I decide to do next. Which is usually determined by how much time I have and how difficult the task is. For example, stuff like frame rate I've been putting off as its going to take ages, and I don't have ages, so I've been picking lower hanging fruit.

Since very few contributions have come in for changes to the apps, despite the code being available for some time, I've been doing those as they are usually quicker/easier.

[SnowLeopard]

Git hub has the issue list.

I wasn't sure it was the right place, considering none of the 30 open issues in userland have even been labelled.
I created a new issue requesting higher framerates.

The order in which they get done is whatever I decide to do next. Which is usually determined by how much time I have and how difficult the task is. For example, stuff like frame rate I've been putting off as its going to take ages, and I don't have ages, so I've been picking lower hanging fruit.

I appreciate that, but it becomes a catch-22 doesn't it? Don't get me wrong, I'm grateful all the work you've done -- I've been having lots of fun with low shutter speeds and splashing water droplets.
It's just the first post in this thread is 10 months old and mentions higher framerates... If you haven't had time since then, it seems like you might never have time...?

[jamesh]

Git hub has the issue list.

I wasn't sure it was the right place, considering none of the 30 open issues in userland have even been labelled.
I created a new issue requesting higher framerates.

The order in which they get done is whatever I decide to do next. Which is usually determined by how much time I have and how difficult the task is. For example, stuff like frame rate I've been putting off as its going to take ages, and I don't have ages, so I've been picking lower hanging fruit.

I appreciate that, but it becomes a catch-22 doesn't it? Don't get me wrong, I'm grateful all the work you've done -- I've been having lots of fun with low shutter speeds and splashing water droplets.
It's just the first post in this thread is 10 months old and mentions higher framerates... If you haven't had time since then, it seems like you might never have time...?

Don't worry about labelling in the github issues, I always dig out the camera ones.

As for timescales, note that this thread predates the release of the camera board by some time, so its less than 10 months, but even so, it would be better if I had more time (or there was someone else to do the work - there isn't), but I have to squeeze in the Raspi work in to my usual Brcm work schedule. There are three related issues I do want to look at soon, the problems with long exposure, the field of view of video, and the higher framerates.

[peepo]

Hey, keep those frame rates at the head!

glad they're not forgotten

~:"

[bubnikv]

Hello James,

We plan to use the Raspberry Pi & Camera combo for tracking of hands / tools in an augmented reality system. Therefore we need high frame rate, high resolution and low latency. Yes, we want it all. Ideally, we would like to synchronize frames of multiple cameras, which we were able to do with our older hardware setup.

I learned, that the system communicates with the camera through the GPU only. I found source code of the user space driver, but the kernel driver and the GPU firmware are closed source. While I understand the reasons for keeping these parts closed, it makes difficult to us to estimate the effects of these building blocks on the image quality and latency. Ideally, we would do our processing during the read out from the camera and then stream a ROI over the ethernet. Also we would process the Bayer image ourselves, if possible.

1) What is the latency of the still camera capture? What is the frame latency of the movie capture? What are the effects of the preview on the frame latency? What would be the settings for achieving the lowest latency possible? Are there paths of lower latency than the mmal interface?

2) What operations are performed on the raw image during the video capture? Is there any sharpening done? Is there any processing done on two or more successive frames of a video capture sequence, that would delay the video capture by one or more frames?

3) Is there a schematic of the camera board available? Is there a way to hardware synchronize the video capture of multiple cameras?

Thank you for your time,
Vojtech

[adayforgotten]

I would like to use i2c for switching camera LED, is it possible?

No, the LED is on its own separate GPIO line and can not be controlled through the I2C.
Also you do NOT wan to mess with the I2C whilst the camera is running.
You are likely to interfere with the normal command flow.

Can you please clarify this statement? I haven't seen anywhere in the camera docs that using the camera means I can't use i2c. This is integral for a monitor that uses the camera and i2c for additional sensors like temp/humidity/etc.

Can you provide a complete and comprehensive list of the components that are affected by the camera module being in use?

[jamesh]

IIRC, the Raspi uses the CSI-2 port for incoming frame data and I2C 0 to communicate with the camera.

[adayforgotten]

IIRC, the Raspi uses the CSI-2 port for incoming frame data and I2C 0 to communicate with the camera.

So then anything on I2C 1 is unaffected? Is this different for the rev. 1 models (I have an assortment of both revisions)? And with respect to the I2C channel which the camera is using, shouldn't it only use a single address allowing other I2C devices to work on the same bus simultaneously?

Also, slightly unrelated, but is CSI-1 usable for anything?

Thanks for all your help and hard work on the drivers.

[jamesh]

Not sure about the other questions, but CSI-2 is the name of the protocol, not the number of the port. Although there are 2 CSI-2 Ports on the SoC, only one is brought out to the Raspi.

[SteveDee]

.... There are three related issues I do want to look at soon, the problems with long exposure, the field of view of video, and the higher framerates....

I've been making good progress with my bird box project for next season (February-June 2014) but I've just realised I have a problem.

My selected board lens is giving the right angle of view when using raspistill, but is way too small when using raspivid (or Motion).

I see you mention this on your to-do list, which I'm guessing has dozens of other issues listed. Are you able to advise whether this is likely to have a solution in the next couple of months....or should I get myself a wide-angle lens?

[jamesh]

.... There are three related issues I do want to look at soon, the problems with long exposure, the field of view of video, and the higher framerates....

I've been making good progress with my bird box project for next season (February-June 2014) but I've just realised I have a problem.

My selected board lens is giving the right angle of view when using raspistill, but is way too small when using raspivid (or Motion).

I see you mention this on your to-do list, which I'm guessing has dozens of other issues listed. Are you able to advise whether this is likely to have a solution in the next couple of months....or should I get myself a wide-angle lens?

I really don't know. I have a lot of paid work to do, but I do hope to have a look at some new modes in the next month.

[SteveDee]

Thanks for your swift response.

I reckon you need to concentrate on the paid stuff, especially with xmas less than 3 weeks away!

I can get a cheap lens in the meantime.

[jamesh]

Thanks for your swift response.

I reckon you need to concentrate on the paid stuff, especially with xmas less than 3 weeks away!

I can get a cheap lens in the meantime.

I've been able to do a lot of Raspi work during my normal work time over the last year (Thanks boss!), but the work I actually need to do has caught up a bit, so I've had to stop all work on it till I clear some backlog.

[payal]

Hi,

I used 3-4 raspi camera board but no one worked. I replace camera many times but red led lit up did not solve.

anybody tell me what is the problem in raspi- camera board?

[jamesh]

There is a very recent firmware fix for an obscure camera startup problem. Try sudo rpi-update to get the latest fixes.

[Jay1100]

Hi,

I used 3-4 raspi camera board but no one worked. I replace camera many times but red led lit up did not solve.

anybody tell me what is the problem in raspi- camera board?

I had one camera that didn't work right away and the problem was that the little ribbon cable on the camera board itself, just below the camera lens had come unattached in shipping. It's so tiny I didn't notice it, but once I popped it back into the board, voila, it worked great.

[SteveDee]

.... There are three related issues I do want to look at soon, the problems with long exposure, the field of view of video, and the higher framerates....

I've been making good progress with my bird box project for next season (February-June 2014) but I've just realised I have a problem.

My selected board lens is giving the right angle of view when using raspistill, but is way too small when using raspivid (or Motion).

I see you mention this on your to-do list, which I'm guessing has dozens of other issues listed. Are you able to advise whether this is likely to have a solution in the next couple of months....or should I get myself a wide-angle lens?

I really don't know. I have a lot of paid work to do, but I do hope to have a look at some new modes in the next month.

Many thanks to James & co for sorting this out and adding the 90fps feature.

Before firmware upgrade:-

BlueTit_3Mar14.jpg (27.49 KiB) Viewed 35530 times

After firmware upgrade:-

GtTit_1.jpg (35.67 KiB) Viewed 35530 times

More: http://captainbodgit.blogspot.co.uk/201 ... -wild.html

[gama_1206]

Excuse me
can the raspicam camera take pictures at 15 fps really?

what is the way this can be obtained?

I tried many ways and I have not been able to make. Someone can help me?

[peepo]

raspivid -fps 15

see: http://elinux.org/Rpi_Camera_Module#RaspiVid