Balluff MATRIX VISION mvBlueFOX Series, Technical Manual

Page: 37 / 238

1.8 Quickstart 29
The firmware file is a binary part of the device driver
Note
As it can be seen in the image one or multiple firmware files are also a binary part of the device driver.
However it is important to notice that this firmware file will
NOT
be used automatically but only when
the user or an application explicitly updates the firmware on the device and will only become active after
power-cycling the device. Since mvIMPACT Acquire version 2.28.0 every firmware starting from version
49 is available within a single driver library and can be selected for updating! mvDeviceConfigure however
will always update the device firmware to the latest version. If you need to downgrade the firmware for
any reason please get into contact with the MATRIX VISION support to get detailed instructions on how
to do that.
1.8.5.1 FPGA
Until the device gets initialized using the API no FPGA file is loaded in the FPGA on the device. Only by opening
the device through the API the FPGA file gets downloaded and only then the device will be fully operational:
The FPGA file gets downloaded when the device will be opened through the API
As the FPGA file will be stored in RAM, disconnecting or closing the device will cause the FPGA file to be lost. The
firmware however will remain:
The FPGA file will be lost if the device is disconnected or closed
In case multiple FPGA files are available for a certain device the FPGA file that shall be downloaded can be selected
by an application by changing the value of the property
Device/CustomFPGAFileSelector . However the value of this
property is only evaluated when the device is either initialized using the corresponding API function
OR
if a device
has been unplugged or power-cycled while the driver connection remains open and the device is then plugged back
in.
MATRIX VISION GmbH