Matrix Vision mvBlueLYNX-X, Technical Manual, Page: 122 / 236

TCameraTriggerMode and TCameraTriggerSource (Please have a look at the API manual for
more details: mvIMPACT_Acquire_API_CPP_manual.chm (C++))
•
13.4.1.2.4 Testing the digital inputs
For performance reasons, device drivers will not automatically update their digital input properties if nobody
is interested in the current state. Therefore, in order to check the current state of a certain digital input, it is
necessary to manually refresh the state of the properties. To do this please right-click on the property you are
interested in and select Force Refresh from the pop-up menu.
Some devices might also offer an event notification if a certain digital input changed its state. This event can
then be enabled
via the EventSelector in Setting -> Base -> Camera -> GenICam -> Event Control. •
Afterwards, a callback can be registered by right-clicking on the property you are interested in again. •
Now, select Attach Callback from the pop-up menu and switch to the Output tab in the lower right
section of wxPropView (Analysis tabs). •
Whenever an event is send by the device that updates one of the properties a callback has been attached to, the
output window will print a message with some information about the detected change.
Figure 71: wxPropView - Call refresh
13.4.1.2.5 Saving user settings in the non-volatile flash memory
The mvBlueLYNX-X camera offers the possiblity, to save up to 4 user sets in the camera's flash memory
directly. This means that all camera specific settings you've adjusted via wxPropView can be saved in a
non-volatile memory.
Example : You have connected a flash via exposure out of the camera and you want to avoid an overload of
the flash by maloperation, you can save a suitable shutter time, with which the camera will start.
mvBlueLYNX-X Technical Manual
112 22 April 2016 Version - 1.49 MATRIX VISION GmbH