Balluff MATRIX VISION mvBlueNAOS, Technical Manual

Page: 40 / 292

32
• On Windows the driver will not look for a matching XML file during start-up automatically as the native
storage location for settings is the Windows Registry. This must be loaded explicitly by the user by using the
appropriate API function offered by the SDK. However, under
Linux
XML files are the only setting formats
understood by the driver framework thus here the driver will also look for them at start-up. 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.
• 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, where descriptions for all properties relevant for the user (grouped together
in classes sorted by topic) can be found. As mvPropView doesn't introduce new functionality but simply
evaluates the list of features offered by the device driver and lists them any modification made using the
GUI controls just calls the underlying function needed to write to the selected component. mvPropView also
doesn't know about the type of component or e.g. the list of allowed values for a property. This again is
information delivered by the driver and therefore can be queried by the user as well without the need to have
special
inside information . One version of the tool will always be delivered in source so it can be used as a
reference to find out how to get the desired information from the device driver.
MATRIX VISION GmbH