Point Grey Chameleon Exposure Parameter

I am completely new to labview and want to control the basic parameter Exposure of my point grey Chameleon camera, but I have had no luck. I looked at this thread and the VI they presented, but I dont see any property for exposure control.
https://forums.ni.com/t5/LabVIEW/capturing-chameleon-raw-data/td-p/2270666
Then I read in another thread that we use the FlyCapture software to set the exposure through there and set the camera default, but this seems so roundabout for a simple parameter.
http://ni.i.lithium.com/t5/Machine-Vision/PointGrey-Chameleon-USB-camera-not-working-in-Vision-Assis...
Has anyone had any luck of interfacing with Chameleon so I can access the exposure?
Thank you!
Attachments:
Low-Level Grab Raw Data To Image & file.vi ‏61 KB

Hi Richelle,
The errors that you mentioned usually occur after the host PC's USB controller reports a USB transaction error. According to Intel's specification, a transaction error is any error that caused the host controller to think that the transfer did not complete successfully.
Since you've already tried the device on another computer, we know that it's not a problem with the USB controller in the computer. Do you have another USB cable you could try to see if that's what's causing the disconnection issues?
David S.

Similar Messages

Point grey chameleon camera

Hi,
I'm trying to talk to a point grey chameleon USB camera with Labview using ActiveX.
I was able to register the DLL and display the live image and change the settings (shutter, gain, etc.). When I tried to get the image data using the "GetImageData" method, Labview crashed with the error message "Exception: Access violation" (See the attached figure). I also tried to using the "SaveImage" method. It sometimes crashed, too. But it can only save 8-bit pgm files and we need to have 16-bit (12-bit actual resolution).
I'm using Labview 2011 SP1 (32-bit) on windows 7 (64-bit). The camera model is CMLN-13S2M with the Flycapture 2.3.1.8.
Does anyone get the camera to work properly to be able to get the image data in 16-bit?
Thanks,
Joseph
Attachments:
point grey error.png ‏29 KB

Hi,
I have two suggestions for you. First I would like to recommend you follow these steps to verify that there is no problem with your dll and project configuration:
Make sure you are using the same calling conventions as the DLL. When using C calling conventions, the caller is responsible for cleaning up the stack. When using Standard calling conventions, the called function is responsible for cleaning up the stack. If the caller (LabVIEW) and the called function (your DLL) don't have the same calling conventions, then they will either both take things off the stack or neither of them will. Either situation will certainly cause LabVIEW to crash when your DLL function returns.
Make sure that all inputs on both sides of your Call Library Function Node are wired. If the left side is not wired then the DLL will write over unallocated memory. If the right side is not wired up, LabVIEW will assume that your DLL does not need or use that allocated memory and will use it for something else. Your DLL will then overwrite reserved LabVIEW memory space, causing LabVIEW to crash.
Make sure your DLL is not overwriting LabVIEW memory.Frequently DLL functions will take allocated memory as input, write to this memory, and return it. If not enough memory is allocated or the DLL writes more than has been allocated, the DLL will overwrite reserved LabVIEW memory space and cause LabVIEW to crash. For example, consider the following function: double *Waveform (double *waveform, uInt32 size); The proper way to allocate the memory in this case is to initialize the array with the appropriate size prior to calling the DLL. The image below demonstrates the proper method.
Make sure that LabVIEW is passing parameters to your DLL in the format that your DLL is expecting. If LabVIEW and your DLL do not agree on how a parameter is being passed (by value, reference, handle, etc.), then it is possible for your DLL to unintentionally point to some random place in memory. This can cause faulty data at best and LabVIEW or Windows crashing at worst.
If you built the DLL in LabVIEW and you are showing the front panel of the DLL, then there are two strict requirements to make it work.
The Call Library Function must be set so that the DLL call is Reentrant. This is set by changing the execution category (under the Browse button) from Run in UI Thread to Reentrant.
The calling VI (the VI from the LabVIEW development environment that is calling the LabVIEW built DLL) must not be running in the User Interface execution system. This can be checked by selecting File»VI Properties»Execution and making sure that the execution system is standard, instrument i/o, data acquisition, other 1, or other 2 (same as caller may run in the user interface system if the parent VI calling this VI is running in the user interface system).
My second advice is to use the National Instruments Vision and Acquisition software to interface LabVIEW with you camera.
Warm Regards,
Miguel Fonseca
National Instruments - Applications Engineering

How to get Point Grey Dragonfly firewire cameras to work with LabVIEW 2010

We recently got a new computer. The O.S. is Windows 7, 64-bit. It has LabVIEW 2010 (also 64-bit) and the Vision Development Module, as well as the Vision Acquisition Driver. We also have Point Grey Dragonfly Express cameras. The first trial of using LabVIEW to get images from one of the cameras yielded greyscale images (they are color cameras). We then installed the Point Grey drivers (flycapture2.1.3.4_x64). After installing the drivers, the camera was is no longer recognized in MAX. Does anyone have pointers or advice? Thanks.

It's been a bit since I've messed with camera settings. But I think LabVIEW requires the NI-IMAQdx driver and the greyscale was from not setting the bayer filter. I can't poke around my camera settings right now, so I can't double check.

Why Levels mid-point slider and Exposure Gamma Correction slider not the same?

Both the mid-point slider in Levels and the Gamma Correction slider in Exposure adjustment appear to modify Gamma. They even use the same numeric scale.
When Gamma <= 1, both sliders appear to produce the same results (confirmed with a couple of random sample settings and using the Difference blend mode).
When Gamma > 1, however, the results are very different. Levels produces more what one would expect in terms of moving the Gamma curve without moving the white and black points but the Exposure Gamma Correction slider seems to do something very different, either moving the black point or applying a very different curve the produces much brighter tones in the dark shadows.
Can anyone explain why and how these two adjustments produce different results?
Is this a bug with the Exposure adjustment?
By the way, in my limited tests of this I was just using a standard RGB file in 16-bit mode - nothing fancy like 32-bit or LAB or anything like that. Also, Photoshop CS6 Extended. Both 32- and 64-bit versions show the same behavior.
Thanks.

The differing gamma adjustment results also occur in the OS X version of Ps 13.0.1
The situation is worse than you realize, Dennis. Test with a linear grayscale gradient in 16-bit or 8-bit RGB mode instead of arbitrary images. Remember to view at 100% zoom for an accurate display.
Gamma adjustments of less than 1 performed by Levels adjustment layer and Exposure adjustment layer do differ but to a less obvious extent than when the adjustment is greater than 1. Differences can be seen in histograms, and low level differences when differencing layers can be made more obvious by adding an Exposure adjustment layer with the exposure increased.
You'll get further different results by using the gamma adjustment in the "Exposure and Gamma" method of Image > Adjustment > HDR Toning. Notice that the gamma value there has to be specified as the inverse of that in Levels and Exposure.
I haven't bothered to calculate which, if any, of the three gamma adjustment controls gives correct results because that is Adobe's responsibility.
It's quite ridiculous that a common routine giving consistent and correct results isn't being used for all these gamma adjustments. Code re-use makes software more robust, simpler to test, simpler to correct, leaner and overall easier to manage. But what do I know.

Point Grey Gazelle Cameralink with NI-1429 Integration Question

Has anyone used a Gazelle GZL-CL-41C6M camera with an NI-1429 grabber? I find that some camera serial commands work and some don't. I need to change the integration time using the eraw command and it just does not work. I also tried to update the firmware, but the updater utility can't find the cameralink serial port. I can grab images in free-running mode, but I really need to increase the integration time programmatically. I hate to change to a Matrox frame-grabber since our image processing software is geared towards NI hardware. Help!

Testing in IMAQ: I am able to see the camera in Automation Explorer, attach the camera file, create an iid file and acquire images. In IMAQ I can free run the camera or go into bulb trigger mode. If I enable "Additional Commands", then everything stops working. So free-running works and bulb-mode works, but I can't change the integration time in free running mode or gain.
Using our own software: My main problem is that when I use our own software to acquire images and talk to the camera lots of commands work, but many do not. There are many status commands that are not in the camera file that work (temperature, voltage, firmware version etc.). Commands that change the integration time or clock frequency read back that they are changed, but the images stay the same. I don't understand why a command has to be in the camera file when we are just sending serial strings to the camera over the cameralink port.
Point Grey says they do not supply any software with this camera and want me to contact NI. They have never used an NI grabber with this camera, but we always use NI hardware and there are camera files and a compatibility report for the camera (GZL-CL-41C6M) so I think all the commands in the manual ought to work. Also I cannot update the firmware because the Point Grey updater program cannot find the cameralink serial port.
I tried using the Camera File Generator to add extra commands, but they don't work. Either the acquisition fails with "FIFO overflow caused acquisition to halt" or I get a message like: "serial termination string not found" etc.
Sorry this is so convoluted and any advice is appreciated.

Best settings for Point Grey Flea camera

Hi
Can anyone using Point Grey Camera(Flea) find out the best settings(Hue, White Balance U, White balance V, Saturation....) for best image quality.
Regards
Abhishek Verma

chucknoris501
What version of Premiere Elements are you using on Mac?
Export your Timeline content to a .mp4 file, using export settings which have been customized under the Advanced Button/Video Tab of the export's preset.
See Publish+Share/Computer/AVCHD and .mp4 category. The exported file is then uploaded to YouTube at the YouTube web site.
If you post the properties of your source video and project settings, I will suggest the settings for the Timeline content export to file saved to the computer
hard drive for upload to YouTube at the YouTube web site.
ATR

HT1338 6 point grey on grey type in Software update

Do any other non-teengers have any trouble seeing the 6 point grey on grey type in Software update?? Come on Apple, make it readable please

Always clone your startup drive before doing any updates or upgrades. I clone my startup drive to a second internal drive using carbon copy cloner so I'm able to get back to work immediately if any problems occur.

Import power point greyed out

Can anyone tell me why the inport power point slides is greyed out? Could it be because I'm using PP 2003 and Captivate 5?
Thank you
Beau

Yes, it is a strange relationship Captivate with Powerpoint
Glad it is solved.
Lilybiri

Pointer to structure in parameter list of DLL

I want to use the CALL_LIBRARY_FUNCTION to access a function in a DLL
which returns a pointer to a structure in its parameter list. How can I
access this structure under LabVIEW 6.02? What is the parameter type I
have to select in the CALL_LIBRARY_FUNCTION configuration window - there
is no STRUCTURE or CLUSTER entry?
Any help is very much appreciated. Thanks, Frank

You may select "Adapt to Type" as a type of the parameter of the function, and then connect appropriate cluster to the output of the "Call Library" node.
Oleg Chutko.

Vanishing point greyed out

Hi I am trying to us the vanishing point and its greyed out...no matter what I do?
C

I believe it only works with 8 and 16 bit files and the image can't be hidden...Does everything meet those requirements?
Benjamin

Imaqdx registers returning errors on point grey cameras

I am trying to control Pt Grey Flea3 USB3 cameras. Mostly these have been excellent, but I have come unstuck trying to access certain trigger modes. THe trigger modes that Pt Grey claims are accessible, do not appear to be available as attributes, so I tried accessing registers directly. Turns out I can read registers (in steps of 4) at offsets up to 20Ch, but after that I consistently get the same (rather unhelpful) error message "Unknown USB3 Vision error" (-1074360261 xBFF6903B). This maximum offset is well shy of anything interesting in the registers. I can revert the drivers back so I can use the native FlyCap software and this does allow me to access the registers at the offsets I expect (e.g. 803h). I have seen similar posts to this problem, but don't see anything directly related. Anyone got any ideas?

Hi bostonscot,
What version of LabVIEW and NI-IMAQdx do you have on your machine? Would it be possible for me to receive a screenshot of the error message you are receiving?
How are you configuring the IMAQdx Read Register VIs? Would it be possible to receive a screenshot or VI snippet of the code where the reading from the register is taking place?
Regards,
Jordan G
Applications Engineer
National Instruments

USB/DirectShow camera not showing in NI-MAX

I've got a Point Grey Chameleon CMLN-13S2M USB 2.0 camera and it is not showing up in NI-MAX.
I'm well aware of the Directshow registration problems with the PGR cameras, and as far as I can tell the camera is properly registered. It shows up with no problems in AMCAP, a simple Directshow viewer, and also in Skype.
I just uninstalled the PGR drivers and spent a while going through the registry to delete all references I could to Point Grey and PGR. I then reinstalled the 32 bit version of the latest drivers, v2.5 beta 2. I also upgraded the camera firmware to the latest.
I'm running
Labview 2012 SP1 f2, 12.0.1
Vision development module 12.1.0
MAX 5.4.0f0
NI-IMAQ 4.7.2
NI-IMAQdx 4.1.0
Any ideas? This is a side project and I've been working on it off and on now for more than a year and I've got to get this camera working.
Solved!
Go to Solution.

Yes, I still see the camera with other DirectShow viewers after the reinstall. The latest Point Grey drivers give the option to register the directshow drivers during the installation. I assumed that this worked since the camera shows up with the other DirectShow viewers, but I also manually registered the files according to the instructions in your links just in case.
I believe that a year or more ago ago when I was running an old version of LV (2009, I think) it did show up in MAX. I had upgraded a few of the LV components piecemeal, but when my university upgraded to 2012 I decided to uninstall and reinstall with the latest versions of everything. I have never seen it listed in MAX, red x or not, since I uninstalled the old version to upgrade.
I have used a camera from a different company and it worked fine.
I found that the 32bit directshow cameras are listed in the registry at
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{860BB310-5D01-11d0-BD3B-00A0C911CE86}\Instance
and I verified this by modifiying the "FriendlyName" registry key for the camera that does show up and observing that the name changes in MAX. The point grey camera is listed here in the registry but does not show up in MAX.

NIMAX acquisition attributes missing

Hello,
i am working with point grey camera "Chameleon". Everything works but one thing. In NIMAX under camera attributes there are some missing ones. The main problems is that as the attribute control is mising every time the labview try to capture an image it obtains default parameters from NIMAX and therefore set the attribute to 0. Which prevents me from obtaining any data. So the question is : is there are way to fix NIMAX or should i try to somehow set camera atributes within labwiev?

Bjanu,
This issue is actually a result of how the Point Grey Chameleon interfaces with the computer. In order to successfully have the DirectShow compatible camera work with LabVIEW, you will need to manually register the DirectShow DLL's on your computer. A more descriptive link on how you can actually do this can be found on the Point Grey website here:
http://www.ptgrey.com/support/kb/index.asp?a=4&q=310&ST=directshow
Hopefully this gets you up and running and allows you to change your camera attributes.
Regards,
Keith M.
Applications Engineering

How to interface with Chameleon camera

Hi everyone,
I am trying to use Labview to control Chameleon camera, which is from Point Grey Research. I am using the ActiveX control interface and I have encounter a problem of using "Call Library Function" node. I am using that node to get the image array from a pointer and trying to display. However, the "Call Library Function" node doen't work.
I am wondering how can I get the image array from a pointer that is used by the FlyCapture?
Was there anyone experience the same thing?
Thanks.
Carson

CarsonZ,
Please check to see if your camera is supported by the Industrial Camera Advisor. Also, when you say that the Call Library Function node does not work, does it return a specific error message or just not return any data?
Lastly, is the FlyCapture application an ActiveX enabled application? If so you should be able to register for events and also pull the information from the application by running through this help document.
Logan H
National Instruments
Applications Engineer

When I select the lab color mode, many options are greyed out?

Can anyone help me . When I select Lab color, many options are grey out. The following are greyed out: exposure,vibrance, black and white, channel mixer, and selective color. It worked perfectly the first time I used it but will not work now. Do I need to reset something. I have tried everything I can think of. I use a PC and PS 5.
Thanks for the help.

I'm working on the Mac versions of CC and CC 2014. If I select Lab, those very same options are grayed out.

Point Grey Chameleon Exposure Parameter

Similar Messages

Maybe you are looking for