01-23-2008 12:16 PM
01-25-2008 01:40 PM
01-28-2008 07:05 AM
It is worth spending some time familiarising yourself with the camera file since this is crucial to how you configure your camera and some of the camera files obtained from NI contain errors.
The camera file provides a 'high level' command set for adjusting the camera settings to the IMAQ user, either via MAX or programmatically. The IMAQ application interfaces directly with the camera using the 'lower level' command set defined in your camera manual. The commands used for this are defined in the camera file. You should therefore familiarise yourself with the command interface defined in your camera manual and relate this to the camera file.
For each 'high level' command there is a current and default value defined in the camera file. By changing the camera settings in MAX and saving the file, the current values should change. If the original camera file is valid and loads up okay there shouldn't be a problem saving new settings. If this is failing, you could try modifying the 'current value' parameter directly in the camera file then reloading in MAX.
Hope this helps.
02-01-2008 11:04 AM
02-04-2008 01:09 PM
02-04-2008 01:55 PM
What I think is really happening is that When MAX reads the current values from the camera to generate the camera file, the camera tells MAX some value that is out of range. Since MAX only tries setting these values when they are changed, or when saving the camera, this is why you can acquire images in MAX, but when you save you have a problem. To narrow down which attribute is bad, try changing each attribute in MAX. Make sure you display all attributes. Some are read only, so don't worry about those, but hopefully this will return an error when you try changing the attribute that has the problem. Once you know which attribute the camera is returning that's wrong, you can adjust it in MAX to a valid value and then be able to save the camera file.
Hope this helps,
Brad
02-11-2008 11:57 AM
03-24-2008 01:25 PM
03-25-2008 11:57 AM