To Next Page

To Previous Page

Note

There is just a limited set of devices that offer more than one FPGA ﬁle and these additional FPGA ﬁles

serve very special purposes so in almost every situation the default FPGA ﬁle will be the one used by an

application. Before using custom FPGA ﬁles, please check with MATRIX VISION about why and if this

makes sense for your application.

So assuming the value of the property Device/CustomFPGAFileSelector has been modiﬁed while the device has

been unplugged, a different FPGA ﬁle will be downloaded once the device is plugged back into the host system:

A different FPGA ﬁle can be downloaded

1.8.5.2 Firmware

Only during a ﬁrmware update the ﬁrmware ﬁle that is a binary part of the device driver will be downloaded perma-

nently into the device's non-volatile memory.

Attention

"Wrong ﬁrmware"

Until mvIMPACT Acquire 2.27.0 each device driver just contained one speciﬁc ﬁrmware version thus

once a device's ﬁrmware has been updated using a speciﬁc device driver the only way to change the

ﬁrmware version will be using another device driver version for upgrading/downgrading the ﬁrmware

again. Since mvIMPACT Acquire version 2.28.0 every ﬁrmware starting from version 49 is available

within a single driver library and can be selected for updating! mvDeviceConﬁgure however will always

update the device ﬁrmware to the latest version. If you need to downgrade the ﬁrmware for any reason

please get into contact with the MATRIX VISION support to get detailed instructions on how to do that.

→ In order to select the appropriate ﬁrmware version for the device appropriate tools such as mv←-

DeviceConﬁgure (p. 68) should be used.

So assume a device with a certain ﬁrmware version is connected to a host system:

A certain ﬁrmware version is connected to a host system

MATRIX VISION GmbH

Balluff MATRIX VISION mvBlueFOX-200wC User Manual

Questions and Answers: