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

Whenever storing a device family specific setting, the device specific or product specific setting of the
device used for storing will be deleted (if existing). See above to find out why.
XML files are the only setting formats understood by the driver framework thus here the driver will
also look for them at startup. The device specific setting will be an XML file with the serial number of
the device as the file name, the product specific setting will be an XML file with the product string as
the filename, the device family specific setting will be an XML file with the device family name as the
file name. All other XML files containing settings will be ignored!
Restoring of settings previously stored works in a similar way. After a device has been opened the settings
will be loaded automatically as described above.
All the information about storing and restoring of settings that have been given so far will bind settings for a
certain device to a certain computer or file. So the same device connected to a different system might work
with different settings. GenICam compliant devices also offer a way to permanently store and restore settings
inside the device. To find out more about this mechnism please have a look at the latest SFNC document in
the User Set Control section.
A detailed description of the individual properties offered by a device will not be provided here but can
be found in the C++ API reference (mvIMPACT_Acquire_API_CPP_manual.chm), where descriptions
for all properties relevant for the user (grouped together in classes sorted by topic) can be found.
mvBlueLYNX-X Technical Manual
MATRIX VISION GmbH 22 April 2016 Version - 1.49 97