[Tom Line]

We have this exact same issue. We've verified it is a camera issue that we can repeatably produce.

We proved this to ourselves by disconnecting the camera from the crio and bridge and going straight to the computer. We logged into the camera using the administrator account, and set and saved the brightness and exposure values to automatic. We then held a flashlight in front of the camera lense, allowed it to darken, then set to 'hold current' and saved. Upon removing the flashlight from the lense the camera retains the darkened settings.

Power cycling the camera causes it to began acting as though the settings have been returned to 'automatic'. Going in through the web interface still shows the settings on both white balance and exposure set to 'hold current'.

We have tried changing these settings in the 'simple' camera GUI interface as well with the same results. We have tried saving the settings using both the 'root' administrator account, and the FRC account added by the FRC camera configuration tool. We have reset the camera to factory defaults and manually configured it without the FRC configuration tool and had the same result. We have tried repeatedly saving the 'hold current settings' and had the same result. We have tried configuring the camera using the Labview code in vision processing at run time and setting an exposure value of zero with no noticeable effect. We have tried setting the code to 'hold current' and permanently deploying with the same issue, and we have tried formatting the cRIO and then running the code from the computer with the same issue.

We have 2 of these cameras, one purchased through AM First Choice, and one purchased from an outside vendor. Both exhibit the same behavior.