Attribute Value Out of Range Error only on second update of value every time.

[mr. smithers]

I've been trying to create an interface to alter my camera's attributes during acquisition. I created a cluster which has controls for BinningX&Y, frame rate, exposure, and position. When running the VI everything works fine except when changing the binning value more than once, I'll always get an error on the second attempt. The range is 1-9, and at the start of the VI I can change it to any value in that range, but if I try to change it to anything else after, even back to 1, I get an error that the value is out of range. Any idea what could be causing this?

Attached is a screenshot of the portion of my VI which handles changing the values.

Thanks!

[toto26 · Accepted solution]

Change the order in wich you pass the parameters. I had this problem several times.

In fact, if the ROI you define is out of the sensor area you will get this error.

Also don't forget that Offset X + Width can't be greater than Sensor Width and Offset Y + Height can't be greater than Sensor Height.

Hope this helps

[mr. smithers]

Awesome, yea, after playing with it for a while I realized the problem was the width being set to 480 pixels when binning the image would make it smaller and so there would be a conflict, ill have to work on that. Do you know if there's a way to make it automatically use the current sensor width/height as the max?

[toto26]

It depends on the manufacturer of your camera, but you should get it with a property node, and select Sensor Witdh or something like this. Once you've got these informations, it's up to you to compute and pass the right vaues...

Regards