This manual is based on a modular concept and contains several individual books. That means like in many objectoriented programming languages for each specific functionality you will have your own "class". Instead of classes,
you have books. For example, if you want to know anything about the GUI based applications, then you have to go
to the Application Usage (p. 77) book. If you want to know how images are acquired with your device, have a look
in the respective programming language chapter.
Here is a short summary about all books that form this manual:
• The manual starts with technical data about the device like sensors (for cameras) or electrical characteristics
as well as a quick start chapter.
Afterwards, you will find the different books:
• The installation package comes with a couple of tools offering a graphical user interface (GUI (p. 77)) to
control mvIMPACT Acquire compliant devices.
– wxPropView (p.77) can be used to capture image data and to change parameters like AOI or gain
– mvDeviceConfigure (p. 116) can be used to e.g. perform firmware updates, assign a unique ID to a
device that is stored in non-volatile memory or to configure to log-message output.
• HRTC - Hardware Real-Time Controller (p. 124)
– It is possible to define sequences of operating steps to control acquisition or time critical I/O. This FPGA
built-in functionality is called Hardware Real-Time Controller (short: HRTC).
• DirectShow developers (p. 133)
– This is the documentation of the MATRIX VISION DirectShow_acquire interface.
• Use cases (p. 139)
– This book offers solutions and explanations for standard use cases.
For C, C++, .NET developers, there are separate mvIMPACT Acquire manuals describing the API. Please refer to
the Programming (p.6) section
These documents can either be downloaded from http://www.matrix-vision.com or come as part of an
installation package. The manuals e.g. contain information about
• how to link and build applications using mvIMPACT Acquire
• how the log output for mvIMPACT Acquire devices is configured and how it works in general
• how to create custom client installers packages for Windows and Linux
• the API itself
1.2How to get started?
This chapter gives you a short overview, how to get started with your device and where to find the necessary
information in the manual. It will also explain or link to the concepts behind the driver and the image acquisition.
Furthermore it explains how to get started programming own applications.
MATRIX VISION GmbH
1.2 How to get started?3
1.2.1 Installation
To install the mvBlueFOX properly you have to follow these steps:
(Please follow the links for detailed descriptions.)
• Windows:
– Check the system requirements (p.24).
– Install the software and driver (p. 25).
– Install the hardware (p.27).
– Configure the mvBlueFOX (p. 77)
e.g. make a white balance (p. 102) (color sensors).
*
• Linux:
– Check the system requirements (p.31).
– Install the software and driver (p. 33).
– Install the hardware (p.39).
– Configure the mvBlueFOX (p. 77)
e.g. make a white balance (p. 102) (color sensors).
*
1.2.2 Driver concept
The driver supplied with the MATRIX VISION product represents the port between the programmer and the
hardware. The driver concept of MATRIX VISION provides a standardized programming interface to all image
processing products (excluding mvBlueLYNX) made by MATRIX VISION GmbH.
The advantage of this concept for the programmer is that a developed application runs without the need for any
major modifications to the various image processing products made by MATRIX VISION GmbH. You can also
incorporate new driver versions, which are available for download free of charge on our website: http://www.←-
matrix-vision.com.
The following diagram shows a schematic structure of the driver concept:
MATRIX VISION GmbH
4CONTENTS
Figure 1: Driver concept
• 1 Part of any mvIMPACT Acquire driver installation package (Windows).
• 2 Separately available for 32 bit and 64 bit. Requires at least one installed driver package.
• 3 See 2, but requires an installed version of the mvBlueFOX driver.
• 4 Part of the NeuroCheck installer but requires at least one installed frame grabber driver.
• 5 Part of the mvIMPACT SDK installation. However, new designs should use the .NET libs that are now part
of mvIMPACT Acquire ("mv.impact.acquire.dll"). The namespace "mv.impact.acquire" of
"mv.impact.acquire.dll" provides a more natural and more efficient access to the same features
as contained in the namespace "mvIMPACT_NET.acquire" of "mvIMPACT_NET.dll", which is why
the latter one should only be used for backward compatibility but NOT when developing a new application.
• 6 Part of Micro-Manager.
1.2.2.1 NeuroCheck support
A couple of devices are supported by NeuroCheck. However between NeuroCheck 5.x and NeuroCheck 6.x there
has been a breaking change in the internal interfaces. Therefore also the list of supported devices differs from one
version to another and some additional libraries might be required.
For NeuroCheck 5.x the following devices are supported:
DeviceAdditional software needed
mvTITAN-G1mvSDK driver for mvTITAN/mvGAMMA devices
mvTITAN-CLmvSDK driver for mvTITAN/mvGAMMA devices
mvGAMMA-CLmvSDK driver for mvTITAN/mvGAMMA devices
mvBlueFOXmvIMPACT Acquire driver for mvBlueFOX devices, "NCUSBmvBF.dll"
MATRIX VISION GmbH
1.2 How to get started?5
For NeuroCheck 6.0 the following devices are supported:
DeviceAdditional software needed
mvTITAN-G1mvIMPACT Acquire driver for mvTITAN/mvGAMMA de-
vices
mvTITAN-CLmvIMPACT Acquire driver for mvTITAN/mvGAMMA de-
vices
mvGAMMA-CLmvIMPACT Acquire driver for mvTITAN/mvGAMMA de-
vices
mvHYPERION-CLbmvIMPACT Acquire driver for mvHYPERION devices
Every other mvIMPACT Acquire compliant devicemvIMPACT Acquire driver for the corresponding device
family,"mv.impact.acquire.NeuroCheck6.←-
dll" (comes with the driver package, but the driver
package must be installed AFTER installing NeuroCheck 6
For NeuroCheck 6.1 the following devices are supported:
DeviceAdditional software needed
mvTITAN-G1mvIMPACT Acquire driver for mvTITAN/mvGAMMA de-
vices
mvTITAN-CLmvIMPACT Acquire driver for mvTITAN/mvGAMMA de-
vices
mvGAMMA-CLmvIMPACT Acquire driver for mvTITAN/mvGAMMA de-
vices
mvHYPERION-CLbmvIMPACT Acquire driver for mvHYPERION devices
Every other mvIMPACT Acquire compliant devicemvIMPACT Acquire driver for the corresponding device
family,"mv.impact.acquire.NeuroCheck6_←-
1.dll" (comes with the driver package, but the driver
package must be installed AFTER installing NeuroCheck
6.1
1.2.2.2 VisionPro support
Every mvIMPACT Acquire driver package under Windows comes with an adapter to VisionPro from Cognex. The
installation order does not matter. After the driver package and VisionPro has been installed, the next time VisionPro
is started it will allow selecting the mvIMPACT Acquire device. No additional steps are needed.
MATRIX VISION devices that also comply with the GigE Vision or USB3 Vision standard don't need any software
at all, but can also use VisionPro's built-in GigE Vision or USB3 Vision support.
1.2.2.3 HALCON support
HALCON comes with built-in support for mvIMPACT Acquire compliant devices, so once a device driver has been
installed for the mvIMPACT Acquire device, it can also be operated from a HALCON environment using the corresponding acquisition interface. No additional steps are needed.
MATRIX VISION devices that also comply with the GigE Vision or USB3 Vision standard don't need any software
at all, but can also use HALCON's built-in GigE Vision or USB3 Vision support.
As some mvIMPACT Acquire device driver packages also come with a GenTL compliant interface, these can also
be operated through HALCON's built-in GenTL acquisition interface.
MATRIX VISION GmbH
6CONTENTS
1.2.2.4 LabVIEW support
Every mvIMPACT Acquire compliant device can be operated under LabVIEW through an additional set of VIs which
is shipped by MATRIX VISION as a separate installation ("mvLabVIEW Acquire").
MATRIX VISION devices that also comply with the GigE Vision or USB3 Vision standard don't need any additional
software at all, but can also be operated through LabVIEW's GigE Vision or USB3 Vision driver packages.
1.2.2.5 DirectShow support
Every mvIMPACT Acquire compliant device driver package comes with an interface to DirectShow. In order to be
usable from a DirectShow compliant application, devices must first be registered for DirectShow support. How to
this is explained here (p.134).
1.2.2.6 Micro-Manager support
Every mvIMPACT Acquire compliant device can be operated under https://micro-manager.org when
using mvIMPACT Acquire 2.18.0 or later and at least Micro-Manager 1.4.23 build AFTER 15.12.2016. The
adapter needed is part of the Micro-Manager release. Additional information can be found here: https←-
The image acquisition is based on queues to avoid the loss of single images. With this concept you can acquire images via single acquisition or triggered acquisition. For detailed description of the acquisition concept, please have
a look at "How the capture process works" in the mvIMPACT_Acquire_API manual matching the programming
language you are working with.
1.2.4 Programming
To understand how to control the device and handle image data you will have a good introduction by reading the
main pages of the corresponding mvIMPACT Acquire interface reference. Additionally, please have a look at the
example programs. Several basic examples are available. For details please refer to
• the C API (p. 126) section
• the C++ API (p. 127) section
• the .NET API (p. 128) section
• the Python API (p. 129) section
depending on the programming language you will use for your application.
MATRIX VISION GmbH
2 Imprint7
2Imprint
MATRIX VISION GmbH
Talstrasse 16
DE - 71570 Oppenweiler
This document assumes a general knowledge of PCs and programming.
Since the documentation is published electronically, an updated version may be available online. For this reason we
recommend checking for updates on the MATRIX VISION website.
MATRIX VISION cannot guarantee that the data is free of errors or is accurate and complete and, therefore, assumes no liability for loss or damage of any kind incurred directly or indirectly through the use of the information of
this document.
MATRIX VISION reserves the right to change technical data and design and specifications of the described products
at any time without notice.
Copyright
MATRIX VISION GmbH. All rights reserved. The text, images and graphical content are protected by copyright
and other laws which protect intellectual property. It is not permitted to copy or modify them for trade use or
transfer. They may not be used on websites.
• Windows® XP, Windows® Vista, Windows® 7 are trademarks of Microsoft, Corp.
• Linux® is a trademark of Linus Torvalds.
All other product and company names in this document may be the trademarks and tradenames of their
respective owners and are hereby acknowledged.
The manual has been generated with Doxygen (Website: http://www.doxygen.org).
Parts of the log file creation and the log file display make use of Sarissa (Website: http://dev.←-
abiss.gr/sarissa) which is distributed under the GNU GPL version 2 or higher, GNU LGPL version
2.1 or higher and Apache Software License 2.0 or higher. The Apache Software License 2.0 is part of this
driver package.
MATRIX VISION GmbH
8CONTENTS
3Revisions
DateDescription
21. December 2016Updated Setting up multiple display support and/or work with several capture set-tings in parallel (p. 91).
15. December 2016Added Micro-Manger in Driver concept (p. 3).
23. August 2016Added measured frame rates of sensors mvBlueFOX-[Model]200w (0.4 Mpix [752 x
480]) (p. 231)
mvBlueFOX-[Model]202b (1.2 Mpix [1280 x 960]) (p. 237)
mvBlueFOX-[Model]202d (1.2 Mpix [1280 x 960]) (p. 241)
mvBlueFOX-[Model]205 (5.0 Mpix [2592 x 1944]) (p. 244).
01. August 2016Extended use case Take two images with different expose times after an external
trigger (HRTC) (p. 184).
11. May 2016Added Quick Setup Wizard (p. 77).
02. December 2015Updated CE declarations (p.14).
25. November 2015Added Troubleshooting (p. 138).
27. October 2015Added Command-line options (p. 115).
04. August 2015Added Windows 10 support.
19. June 2015Restructured chapter Use cases (p. 139).
23. April 2015Added use case Edge controlled triggering (HRTC) (p. 186).
16. April 2015Updated supported Windows versions.
15. April 2015Added lens protrusion.
11. March 2015Added chapter Accessing log files (p. 100).
26. February 2015Moved Creating double acquisitions (HRTC) (p. 183) to HRTC Use Cases.
27. January 2015Added use case Using VLC Media Player (p. 140). Renewed Order code nomencla-ture (p. 19).
09. January 2015Extended sample Using 2 mvBlueFOX-MLC cameras in Master-Slave mode (p. 173).
10. December 2014Corrected Order code nomenclature (p. 19) : mvBlueFOX cameras without filter have
the order code 9 (excluding mvBlueFOX-MLC).
01. December 2014Extended use case Using 2 mvBlueFOX-MLC cameras in Master-Slave mode
(p. 173).
25. November 2014Corrected the possible HRTC - Hardware Real-Time Controller (p. 124) steps to 256.
21. October 2014Added description about the record mode in How to see the first image (p.82).
17. July 2014Added use case Introducing LUTs (p.168).
25. April 2014Added description about Working with the hardware Look-Up-Table (LUT) (p.113).
25. March 2014Added use case Correcting image errors of a sensor (p.143).
10. March 2014mvDeviceConfigure (p.116) extended.
Added S-mount lensholder for mvBlueFOX-MLC in Order code nomenclature (p. 19).
18. February 2014Updated Characteristics (p.243) of mvBlueFOX-[Model]202d (1.2 Mpix [1280 x 960])
(p. 241).
13. January 2014Changed figure 3 in Using 2 mvBlueFOX-MLC cameras in Master-Slave mode
(p. 173).
12. December 2013Changed figure in Using 2 mvBlueFOX-MLC cameras in Master-Slave mode (p. 173).
06. December 2013Added information about Changing the view of the property grid to assist writingcode that shall locate driver features (p. 99).
22. November 2013Extended information in Adjusting sensor -x00w (p. 161) and Adjusting sensor -x02d(-1012d) (p. 165).
30. October 2013Enhanced cable description in 12-pin Wire-to-Board header (USB 2.0 / Dig I/O) (p. 60).
15. October 2013Added Webcasts (p. 12) links.
Added chapter Bit-shifting an image (p. 98).
09. October 2013Added information about Positioning tolerances of sensor chip (p. 69).
02. September 2013Updated Order code nomenclature (p. 19).
MATRIX VISION GmbH
3 Revisions9
22. April 2013Added chapter Sensor's optical midpoint and orientation (p. 60) and corrected feature
table in CMOS sensors (p.72) (software trigger).
19. March 2013Update Figure 4 in chapter Dimensions and connectors (p.45) and added Figure 5.
24. January 2013Added information about image error counts and disabling CPU sleep states: How todisable CPU sleep states a.k.a. C states (< Windows 8) (p. 120).
16. January 2013Added status LED description of the mvBlueFOX-MLC (p. 66).
14. December 2012New version of technical documentation.
07. December 2012All parts of the manual to do with programming are available as a separate manual now:
• "mvIMPACT_Acquire_API_CPP_manual.chm",
• "mvIMPACT_Acquire_API_C_manual.chm", and
• "mvIMPACT_Acquire_API_NET_manual.chm". These manuals can be download from http://www.matrix-vision.com.
30. September 2012Moved Working with the Hardware Real-Time Controller (HRTC) (p. 179) to Usecases (p. 139).
20. September 2012Added chapter "Porting existing code written with versions earlier then 3.0.0".
17. August 2012Added use case Adjusting sensor -x02d (-1012d) (p. 165).
16. July 2012Extended "Characteristics of the digital inputs" in D-Sub 9-pin (male) (p. 45).
21. June 2012Added description, how to install the Linux driver using the installer script (Installing themvIMPACT Acquire driver (p. 33)).
21. June 2012Added information (electrical characteristic, pinning (p. 59)) about LVTTL version
(mvBlueFOX-MLC2xxx-XLW).
02. April 2012Enhanced chapter Output sequence of color sensors (RGB Bayer) (p. 73) and
added chapter Bilinear interpolation of color sensors (RGB Bayer) (p. 74).
17. February 2012Renewed chapter wxPropView (p.77).
09. November 2011Added Settings behaviour during startup (p. 42) in chapter Quickstart (p. 24).
EventHandling. See "Porting existing code written with versions earlier then 2.←-
0.0".
11. July 2011Added chapters
"Callback demo".
08. Juli 2011Added chapter Using 2 mvBlueFOX-MLC cameras in Master-Slave mode (p.173).
06. June 2011Added chapters
"Porting existing code written with versions earlier then 2.0.0".
31. May 2011Added chapter Creating double acquisitions (HRTC) (p. 183).
26. April 2011Added chapter Using external trigger with CMOS sensors (p.160).
Updated chapter Dimensions and connectors (p. 59) (digital inputs TTL, digital outputs
TTL) of mvBlueFOX-MLC version.
18. January 2011Added chapter Setting up multiple display support and/or work with several capturesettings in parallel (p. 91).
29. Nov. 2010Added ADC resolutions in Sensor overview (p. 70).
19. October 2010Added chapters
"Chunk data format".
07. Oct. 2010Added High-Speed USB design guidelines (p. 14).
22. Sep. 2010Added suitable for mvBlueFOX-MLC What's inside and accessories (p. 22).
26. Aug. 2010Added cable end color of board-to-wire cable in Dimensions and connectors (p. 59).
Added chapter about Creating user data entries (p. 171).
02. Aug. 2010mvBlueFOX-200W and mvBlueFOX-MLC100W support flash control output: CMOSsensors (p.72).
Added chapter Import and Export images (p. 90).
MATRIX VISION GmbH
10CONTENTS
21. Jun. 2010Included exposure modes in the frame rate calculator of the Sensor overview (p. 70).
31. May 2010Added chapter Single-board version (mvBlueFOX-MLC2xx) (p.59).
19. Apr. 2010Added new example ContinuousCaptureDirectX.
01. Apr. 2010Added Use cases (p. 139) about high dynamic range (p. 161) of sensor mvBlueFOX-[Model]200w (0.4 Mpix [752 x 480]) (p. 231).
10. Feb. 2010Added note about Windows XP Embedded in System Requirements (p.24).
28. Jan. 2010Added chapter Copy grid data to the clipboard (p. 90).
13. Jan. 2010Added chapters
"Porting existing code written with versions earlier then 1.12.0".
11. Jan. 2010Due to a software update, documentation of CMOS sensor (-x00w) (p.231) updated.
10. Nov. 2009Added Windows 7 as supported operating system.
22. Oct 2009Updated sensor data (p. 70).
19. Oct 2009Updated wxPropView (p. 77) description about handling settings.
17. Sep. 2009Updated frame rate calculator of CCD sensors (p.70).
05. May 2009Added figures which shows "how to connect flash to digital output".
05. May 2009Added book Use cases (p. 139), which offers solutions and explanations for standard
use cases.
22. Jan. 2009Added information about how to test the gerenal trigger functionality of the camera Set-ting up external trigger and flash control (p.105).
26. Nov. 2008Added chapter Setting up external trigger and flash control (p.105).
28. Oct 2008Added mvBlueFOX-M accessory Accessories mvBlueFOX-Mxxx (p.56).
21. Jul. 2008Added power supply note in 4-pin circular plug-in connector with lock (USB 2.0)
(p. 45).
11. Jun. 2008Added preliminary sensor data of -105 in Sensor overview (p. 70).
10. Jun. 2008Updated sensor data of -121 in Sensor overview (p.70).
09. Apr. 2008Corrected Figure 4: DIG OUT mvBlueFOX-1xx in Dimensions and connectors (p. 45).
25. Feb. 2008Added note about EEPROM of mvBlueFOX-M in Dimensions and connectors (p.51).
19. Feb. 2008Corrected sensor data in Sensor overview (p.70).
30. Jan. 2008Added note about the obsolete differentiation between 'R' and 'U' version in chapter
Dimensions and connectors (p.45).
01. Oct 2007Update sensor data in chapter Order code nomenclature (p. 19).
20. Aug. 2007Added part number of JST connectors used on the mvBlueFOX-M (see: Dimensionsand connectors (p.51)).
31. Jul. 2007Rewritten "How rto use this manual". This book now includes a getting started chapter
(see: Composition of the manual (p. 2)).
11. Jun. 2007Updated images in digital I/O description of mvBlueFOX-M (see: Dimensions and con-nectors (p.51)).
29. May 2007Added an attention in chapter Quickstart (p. 24) section Installing the hardware (p. 27)
(Windows) and Installing the hardware (p. 39) (Linux).
23. May 2007Added calculators to calculate the frame rate of the sensors (see specific sensor
documentation: Sensor overview (p. 70)).
23. Apr. 2007Updated sensor description and added description of Micron's CMOS 1280x1024 (-102a) (p. 234) sensor.
02. Apr. 2007Updated description of mvBlueFOX-M1xx digital I/O in chapter Dimensions and con-nectors (p.51).
24. Nov. 2006Added attention to the DigI/O description of the mvBlueFOX-M (see: Dimensions andconnectors (p.51)).
14. Nov. 2006Updated Linux installation documentation (see: Quickstart (p. 24)).
20. Oct 2006Updated Linux installation documentation (see: Quickstart (p. 24)).
11. Sep. 2006Devided the Quickstart chapter into Linux® and Windows® (see: Quickstart (p. 24)).
MATRIX VISION GmbH
3 Revisions11
8. Sep. 2006Updated CCD timing in CCD 640 x 480 (1/3") documentation (see: mvBlueFOX[Model]220a (0.3 Mpix [640 x 480]) (p. 198)).
5. Sep. 2006Updated the sensor data (see: Sensor overview (p. 70)).
23. Aug. 2006Added general tolerance of the housing (see: Technical data (p.45)).
28. Jul. 2006Removed some linking errors.
19. Jul. 2006Added WEEE-Reg.-No. (see: European Union Declaration of Conformity statement
(p. 14)).
Added ambient temperature of the mvBlueFOX standard version (see: Components
(p. 50)).
17. Jun. 2006New chapter "Configure the log output using mvDeviceConfigure" (see: "Configure thelog output using mvDeviceConfigure").
07. Jun. 2006Extended the HRTC documentation (see: How to use the HRTC (p. 124)).
02. Jun. 2006Fixed image errors in CCD 640 x 480 (1/3") documentation (see: mvBlueFOX-[Model]220a (0.3 Mpix [640 x 480]) (p. 198)).
01. Jun. 2006Updated the chm index.
18. May 2006Sensor description: Changed black/white to gray scale (see: Sensor overview (p. 70)).
14. Feb. 2006Added CCD 640 x 480 (1/3") (see: mvBlueFOX-[Model]220a (0.3 Mpix [640 x 480])
(p. 198)).
13. Feb. 2006Corrected the image of the "4-pin circular plug-in connector" (see: Dimensions and
connectors (p.45)).
MATRIX VISION GmbH
12CONTENTS
4Graphic Symbols
4.1Notes, Warnings, Attentions
Note
A note indicates important information that helps you optimize usage of the products.
Warning
A warning indicates how to avoid either potential damage to hardware or loss of data.
Attention
An attention indicates a potential for property damage, personal injury, or death.
All due care and attention has been taken in preparing this manual. In view of our policy of continuous product
improvement, however, we can accept no liability for completeness and correctness of the information contained in
this manual. We make every effort to provide you with a flawless product.
In the context of the applicable statutory regulations, we shall accept no liability for direct damage, indirect damage
or third-party damage resulting from the acquisition or operation of a MATRIX VISION product. Our liability for intent
and gross negligence is unaffected. In any case, the extend of our liability shall be limited to the purchase price.
4.2Webcasts
This icon indicates a webcast about an issue which is available on our website.
MATRIX VISION GmbH
5 Important information13
5Important information
We cannot and do not take any responsibility for the damage caused to you or to any other equipment
connected to the mvBlueFOX. Similarly, warranty will be void, if a damage is caused by not following
the manual.
Handle the mvBlueFOX with care. Do not misuse the mvBlueFOX. Avoid shaking, striking, etc. The
mvBlueFOX could be damaged by faulty handling or shortage.
Use a soft cloth lightly moistened with a mild detergent solution when cleaning the camera.
Never face the camera towards the sun. Whether the camera is in use or not, never aim at the sun or
other extremely bright objects. Otherwise, blooming or smear may be caused.
Please keep the camera closed or mount a lens on it to avoid the CCD or the CMOS from getting
dusty.
Clean the CCD/CMOS faceplate with care. Do not clean the CCD or the CMOS with strong or abrasive
detergents. Use lens tissue or a cotton tipped applicator and ethanol.
Never connect two USB cables to the mvBlueFOX even if one is only connected to a PC.
The mvBlueFOX is bus powered < 2.5 W.
The mvBlueFOX meets IP40 standards.
Using the single-board or board-level versions:
MATRIX VISION GmbH
• Handle with care and avoid damage of electrical components by electrostatic discharge (ESD):
– Discharge body static (contact a grounded surface and maintain contact).
– Avoid all plastic, vinyl, and styrofoam (except antistatic versions) around printed circuit
boards.
– Do not touch components on the printed circuit board with your hands or with conductive
devices.
14CONTENTS
5.1High-Speed USB design guidelines
If you want to make own High-Speed (HS) USB cables, please pay attention to following design guidelines:
• Route High-Speed (HS) USB signals with a minimum number of vias and sharp edges!
• Avoid stubs!
• Do not cut off power planes VCC or GND under the signal line.
• Do not route signals no closer than 20 ∗ h to the copper layer edge if possible (h means height over the
copper layer).
• Route signal lines with 90 Ohm +- 15% differential impedance.
– 7.5 mil printed circuit board track with 7.5 mil distance result in approx. 90 Ohm @ 110 um height over
GND plane.
– There are other rules when using double-ply printed circuit boards.
• Be sure that there is 20 mil minimum distance between High-Speed USB signal pair and other printed circuit
board tracks (optimal signal quality).
5.2European Union Declaration of Conformity statement
The mvBlueFOX complies with the provision of the following European Directives:
• 2014/30/EU (EMC directive)
• 2014/35/EU (LVD - low voltage directive)
• For EN 61000-6-3:2007, mvBlueFOX-IGC with digital I/O needs the Steward snap-on ferrite
28A0350-0B2 on I/O cable.
• For EN 61000-6-3:2007, mvBlueFOX-MLC with digital I/O needs the Würth Elektronik snap-on
ferrite WE74271142 on I/O cable and copper foil on USB.
MATRIX VISION corresponds to the EU guideline WEEE 2002/96/EG on waste electrical and electronic equipment and is registered under WEEE-Reg.-No. DE 25244305.
MATRIX VISION GmbH
5.2 European Union Declaration of Conformity statement15
MATRIX VISION GmbH
16CONTENTS
MATRIX VISION GmbH
5.3 Legal notice17
5.3Legal notice
5.3.1 For customers in the U.S.A.
MATRIX VISION GmbH
18CONTENTS
Class B
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part
15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference
when the equipment is operated in a residential environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. However there is no guarantee that interferences will not occur in a particular
installation. If the equipment does cause harmful interference to radio or television reception, the user is encouraged
to try to correct the interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the distance between the equipment and the receiver.
• Use a different line outlet for the receiver.
• Consult a radio or TV technician for help.
You are cautioned that any changes or modifications not expressly approved in this manual could void your authority
to operate this equipment. The shielded interface cable recommended in this manual must be used with this
equipment in order to comply with the limits for a computing device pursuant to Subpart B of Part 15 of FCC Rules.
• To be compliant to FCC Class B, mvBlueFOX-IGC requires an I/O cable with an retrofittable ferrite to be used
such as
– Company: Steward Type: 28A0350-0B2
5.3.2 For customers in Canada
This apparatus complies with the Class B limits for radio noise emissions set out in the Radio Interference Regulations.
5.3.3 Pour utilisateurs au Canada
Cet appareil est conforme aux normes classe B pour bruits radioélectriques, spécifiées dans le Règlement sur le
brouillage radioélectrique.
MATRIX VISION GmbH
6 Introduction19
6Introduction
The mvBlueFOX is a compact industrial CCD & CMOS camera solution for any PC with a Hi-Speed USB (USB
2.0) port. A superior image quality makes it suited for most applications. Integrated preprocessing like binning
reduces the PC load to a minimum. The standard Hi-Speed USB interface guarantees an easy integration without
any additional interface board. To make the cameras flexible to any industrial applications, the image processing
tools mvIMPACT as well as different example solutions are available
Figure 1: mvBlueFOX
The mvBlueFOX is suitable for following tasks:
• machine vision
• robotics
• surveillance
• microscopy
• medical imaging
With the name mvBlueFOX-M1xx, the industrial camera mvBlueFOX is also available as a single-board version.
6.1Order code nomenclature
6.2mvBlueFOX
The mvBlueFOX nomenclature scheme is as follows:
mvBlueFOX - A B - (1) (2) (3) (4)
- A: Sensor model
220: 0.3 Mpix, 640 x 480, 1/4", CCD
220a: 0.3 Mpix, 640 x 480, 1/3", CCD
200w: 0.4 Mpix, 752 x 480, 1/3", CMOS
221: 0.8 Mpix, 1024 x 768, 1/3", CCD
202a: 1.3 Mpix, 1280 x 1024, 1/2", CMOS
223: 1.4 Mpix, 1360 x 1024, 1/2", CCD
224: 1.9 Mpix, 1600 x 1200, 1/1.8", CCD
205: 5.0 Mpix, 2592 x 1944, 1/2.5", CMOS
- B: Sensor color
G: Gray scale version
C: Color version
The mvBlueFOX-IGC nomenclature scheme is as follows:
mvBlueFOX-IGC A B - (1) (2) (3) (4)
- A: Sensor model
200w: 0.4 Mpix, 752 x 480, 1/3", CMOS
202b: 1.2 Mpix, 1280 x 960, 1/3", CMOS
202d: 1.2 Mpix, 1280 x 960, 1/3", CMOS
202a: 1.3 Mpix, 1280 x 1024, 1/2", CMOS
205: 5.0 Mpix, 2592 x 1944, 1/2.5", CMOS
- B: Sensor color
G: Gray scale version
C: Color version
MATRIX VISION GmbH
6.5 mvBlueFOX-MLC21
- (1): Lensholder
1: CS-mount without adjustable backfocus (standard)
2: C-mount without adjustable backfocus (CS-mount with add. 5 mm extension ring)
3: C-mount with adjustable backfocus
mvBlueFOX-MLC200wC-XOW-5111752 x 480, CMOS 1/3", color, single-board, without Mini-USB, 1x IN +
1x OUT opto-isolated, board-to-wire, CS-mount (w/o backfocus adjustment)
1
: -1111 is the standard delivery variant and for this reason it is not mentioned.
6.6What's inside and accessories
Due to the varying fields of application the mvBlueFOX is shipped without accessories. The package contents:
• mvBlueFOX
• mvIMPACT CD-ROM or DVD-ROM with example application and manual
• instruction leaflet
For the first use of the mvBlueFOX we recommend the following accessories to get the camera up and running:
• A USB 2.0 cable
Attention
According to the customer and if the mvBlueFOX-MLC is shipped without lensholder, the mvBlueFOX-MLC
will be shipped with a protective foil on the sensor. Before usage, please remove this foil!
Accessories for the mvBlueFOX:
Part codeDescription
ADAPTER CS-MOUNTLens fixing for mvBlueFOX to match with CS-mount lenses
KS-USB2-AA-EXT 05.0USB 2.0 extension, activeUSB2 A plug to USB2 A jack, length 5m