SICK IVP C50 camera and LabVIEW

[BruceAmmons]

Has anybody used a SICK IVP C50 camera with LabVIEW?  How did you set up the interface between the two?

For those that don't know, the C50 is a very cool camera that is used to measure 3D profiles of objects.  You project a laser line onto your part, and the camera processes the profile of the laser line and converts it to height measurements.  If the part is moved underneath the laser line, you get a 3D height map of your part.

Thanks,

Bruce

[BullDozier]

Hey Bruce,

I have read your post and done a little research for you.  I have found out that the Sick Ranger-C50 camera acquires an image with its pixel values actually representing the distance that the object is from the camera (measured by a sensor).  I searched our camera file database for a camera file for this camera and found out that there is not one.  Since Sick lists LabVIEW as a compatable machine vision interface, I would imagine they might have a camera file already.  You could try contacting them to get this file.  If they do not have a camera file for this camera, you could generate one yourself using our camera file generator found here.  With a correct camera file, our framegrabbers would be able to acquire this image.  However, the image's pixel values actually represent distance, and our Vision tools do not include any functions that will convert these distance values into the 3D image that the distance values represent.

So yes, we will be able to acquire an "image" whose pixel values represent distance from the camera.  But since these pixel values actually represent distance, our Vision processing functions may not be best suited for these images because our functions are traditionally used with 2D images.

I hope this helps out.  Let me know if I can help you out further.

Take Care,

[BruceAmmons]

Evan,

I am pretty sure I can acquire from the camera.  My main concern right now is figuring out the serial commands for configuring the camera.  I am hoping Sick will provide a list of commands with syntax and all that good stuff.  This way, it would be very easy to create a configuration file using the generator.

I think the IMAQ tools will be pretty useful still.  I can find edges, measure gradients, and do a bunch of other things.  Don't underestimate the power of the NI tools!!!

Bruce

[BullDozier]

Hey Bruce,

That sounds great.  I am anxious to see how this turns out.  Hopefully you can get a list of serial commands from Sick that work with the C50.  Our IMAQ tools can definately still help you out.  I guess what I meant earlier was that they were designed to work with 2D images with pixel values for color instead of depth.   With a little ingenuity, I suppose one could do some amazing stuff with this camera.  If you don't mind, post back here if you hear back from Sick.  I will be monitoring this post to see what happens.

Thanks,

[BruceAmmons]

Evan,

Right now it doesn't look like I will get the serial commands from Sick.  However, it does look like it will be relatively easy to configure the camera.  There is a DLL that comes with the camera that has standard C functions that will configure the camera through a serial port.  By configuring the CameraLink serial to emulate a COM port, it should be pretty easy.  I just have to create a bunch of wrapper VIs for all the different functions in the DLL.

I am told that NI has one of these cameras for examination, and Rob G. was the main contact with the vendor.  I am wondering if any of the NI engineers have already developed the wrappers for the DLL.  Could you look into this for me?

Thanks,

Bruce

[BullDozier]

Hey Bruce,

I will see what I can find.  I'll let you know as soon as I find something.

Take Care,

[Tavi]

I am actually looking into using the same camera for one of my applications, i would be interested in how this turns out.

Thanks,

[BruceAmmons]

The wrapper concept is working pretty well.  I used the import DLL function in LV 8.5 to create all the wrappers.  I haven't finished testing them, though.  Once I feel confidant in the drivers I will probably post them.  Along with the drivers I am using a ICD file that NI developed for the camera.

The camera itself is pretty good, but it suffers from the same sort of problems that other laser measurement devices have.  For optimum measurements, you need minimal background light and low variations in reflectivity and opacity of the target.  For uniform surfaces it works very well.  Nonuniform surfaces need a little more tweaking.  You can only get the advertised frame rates in ideal conditions using the simplest algorithms.  Typically you need more exposure time or more analysis time.

Bruce

[Epsilon]

Hi Bruce!

I am not sure if this is of much help, but we sell a very similar product to the IVP Ranger, more as an OEM 3D Vision Sensor.
Our cameras have either a camera link interface or a GigE and are fully compatible with NI hardware and software.

Additionally, our sensors have a higher scan rate (up to 60 Million 3D points/sec). The height profiles are being processed in real-time with the help of a high-speed FPGA. You can choose between different laser detection algorithms, such as threshold method and center of gravity method. The center of gravity (C.O.G) method is the most precise method but also the most processor intensive one. Since our sensor is doing all the pre-processing in the camera with the FPGA, you don't have to worry about that in your software.
The sensor outputs true 3D profiles.

We have OEM board based versions, camera based versions and complete ruggedized sensor versions.

http://www.movimed.com/3D_Systems.htm


Best,
Markus Tarin
www.movimed.com


Below some illustrations.

Measurement Principle:


Camera and laser line generator scanning a printed circuit board:




Ruggedized compact sensor with optics, sensor and 3D camera.