Industrial MIPI camera for Raspberry Pi

[GeT-Cameras]

Hello everyone,

We have started with the development of our own embedded MIPI camera module for the Raspberry Pi with an industrial image sensor. Currently we are in the specification phase and we are interested in your preferences so we will develop a product that does fit your requirements. If you have some time, please consider filling in this 4-question questionnaire.

 

Edited October 16, 2018 by GeT-Cameras

[hutha]

Is it similar or any additional feature compare with this toolkit ?

CameraCV is working with standard USB 2.0 camera and Raspberry Pi (CSI) camera module. 

QwaveCameraCV is a LabVIEW Camera Driver library for Raspberry Pi 3B/3B+ (LinuxRT)

https://githu b.com/QWaveSystems/QwaveCameraCV

[GeT-Cameras]

We are doing hardware development. You are talking about software. Our camera hardware module will be compatible with the raspberry pi and from the driver side uses the same drivers as the original module. I hope this answers your question

[Benoit]

Cool.

Here are some suggestions:

-Unique serial number that can be accessed by software

-Allow possibility to have more than one lens. (Be able to have 3 cm from the lens can be good for inspection) Having low distortion lens is good to.

-Adaptable to standard lens on the market (stay low cost if possible)

-Having a microbolometer camera would be amazing.

-Having multiple choice for resolution 1MP to 24 MP

-Add distortion correction by software according to the lens

-If you ever be able to create a 3D (imply using double camera) would be amazing (one frame on 2 for each side)

-Some of your option in the survey should be all possible. (software or hardware triggered)

-Having the option to buy or not the housing

What will be the maximum length for the cable?

Benoit

[Rolf Kalbermatter]

On 12/3/2018 at 11:32 AM, Benoit said:

What will be the maximum length for the cable?

Benoit

From my limited experience with MIPI this is very critical. The differential serial lanes of a MIPI connection need all to be within a few mm of length to guarantee proper signal transmission. That means that if you design a PCB you generally have to use meander microstrips to make sure that every connection has exactly the same length. In addition the MIPI standard is designed as a chip to chip interface and is not meant to be routed through long cables. The D-PHY specification defines the maximum lane flight time to 2 ns. so that means that on an FR-4 PCB using matched microstriplines you get at most 25 to 30 cm of trace length. The typical FPC flex cable used to connect a camera module to a board does have similar electrical characteristics and is therefore not that much different. That includes the traces from the chip to the FPC cable connector, the FPC cable itself and the traces from the FPC connector to the framegrabber chip.

[Benoit]

Thanks, I'm not a specialist on MIPI.

Those information are very useful.

Benoit

[GeT-Cameras]

Hi Benoit,

Currently you can already connect all our USB3 machine vision cameras to the raspberry pi. You have then all option you require.

Currently our Mipi camera design of the Raspberry Pi is in the proof of concept stage. Our target is to have a working concept in 2 months. Then the hardware design will start. Initially we will start with a 5MP and 20MP sensor. With these sensors you can user ROI to reduce resolution so we can cover all resolutions. We will keep you posted on our progress. Concerning cable length, we will probably specify it to max 10cm. It will have an m12 mount and cs and c-mount option so you can connect all lenses.

[BonniCase]

Hi...i would also use this. But i will use High sensitivity sensors/cameras with the right pixel size (not too small) are in demand in the astro imagery crowd, finder scope cameras, polar alignment cameras, all sky cameras, deepsky cameras, even cameras to monitor the mount remotely.  Most use ASCOM software to run them.

surface mount assembly

Edited June 26, 2020 by BonniCase