2 Legal Notice and Contact...............................................................................................................................3
5 Important Information.................................................................................................................................15
5.1 Important safety instructions...........................................................................................................15
5.3 European Union Declaration of Conformity statement..................................................................16
6 About this Manual........................................................................................................................................19
6.1 Goal of the manual..........................................................................................................................19
6.2 Contents of the manual...................................................................................................................19
10 Filter and Lenses.........................................................................................................................................79
12 First Start.....................................................................................................................................................91
20 Use Cases....................................................................................................................................................181
20.1 Using a mvBlueFOX-MLC USB 2.0 camera with mvBlueLYNX-X........................................181
20.2 Acquiring a number of images....................................................................................................181
20.3 Controlling external strobe or flash............................................................................................183
20.3.1 Compensating delay of strobe or flash..............................................................................184
20.4 Using the HDR mode with sensor -x00w...................................................................................185
24 Table of Figures.........................................................................................................................................221
VII
VIII
1 mvBlueLYNX-X
Technical Manual
MATRIX VISION GmbH22 April 2016 Version - 1.491
mvBlueLYNX-X Technical Manual
222 April 2016 Version - 1.49MATRIX VISION GmbH
2 Legal Notice and Contact
Post address
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.
Windows® XP, Windows® Vista, Windows® 7 are trademarks of Microsoft, Corp.•
Linux® is a trademark of Linus Torvalds.•
2.1 Introduction
MATRIX VISION GmbH22 April 2016 Version - 1.493
mvBlueLYNX-X Technical Manual
The mvIMPACT Acuire SDK and its underlying libraries and drivers as well as some of the applications
shipped with the mvIMPACT Acquire packages make use of a couple of third party software packages that
come with various licenses. This section is meant to list all these packages and to give credit to those whos
code helped in the creation of the mvIMPACT Acquire SDK.
2.2 wxWidgets
Most of the applications offering a graphical user interface have been written using wxWidgets
(http://www.wxwidgets.org/).
wxWidgets is a C++ library that lets developers create applications for Windows, OS X, Linux and Unix on
32-bit and 64-bit architectures as well as several mobile platforms including Windows Mobile, iPhone SDK
and embedded GTK+. Please refer to the wxWidgets website for detailed license information.
The source code of the applications provided by MATRIX VISION GmbH (http://www.matrix-vision.com)
using wxWidgets is either part of the packet this document was taken from or can be obtained by contacting
MATRIX VISON GmbH.
2.2.1 wxPropGrid
Some of the applications based using wxWidgets make also use of a modified version of an additional control
written by Jaakko Salli called \a wxPropGrid. The latest stable version can be obtained from here:
http://wxpropgrid.sourceforge.net/cgi-bin/index.
2.3 Sarissa
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.
2.4 Komponenten.GenICam
At least one driver package shipped under the product family name mvIMPACT Acquire makes use of the
GenICam reference implementation, which is hosted by the EVMA and can be downloaded from their
website: http://www.emva.org. All license files belonging to the GenICam reference implementation are
shipped with the libraries belonging to the GenICam runtime.
2.5 libusb
The Linux version of the \b mvBlueFOX driver package makes use of a modified version of libusb
(http://www.libusb.org/), which comes under LGPL 2.1. The full license text is included in the Linux
distribution of the \b mvBlueFOX driver package. The source code for the modified version of libusb can be
obtained by contacting MATRIX VISION GmbH or it can be downloaded from here:
http://gpl.matrix-vision.com (navigate to \a others/libusb).
2.6 libusbK
The USB3 Vision implementation currently makes use of libusbK (http://libusbk.sourceforge.net) written by
Travis Lee Robinson who owns all rights for the source code of all modules belonging to the libusbK
framework.
422 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
2.6.1 libusbK license
APPLICABLE FOR ALL LIBUSBK BINARIES AND SOURCE CODE UNLESS OTHERWISE
SPECIFIED. PLEASE SEE INDIVIDUAL COMPONENTS LICENSING TERMS FOR DETAILS.
NOTE: Portions of dpscat use source code from libwdi which is licensed for LGPL use only. (See dpscat.c)
NOTE: libusbK-inf-wizard.exe is linked to libwdi which is licensed for LGPL use only.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that
the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the
•
following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
•
the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Travis Lee Robinson nor the names of its contributors may be used to endorse or
•
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL TRAVIS ROBINSON BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
2.7 Doxygen
All the documentation belonging to the mvIMPACT Acquire framework has been generated using Doxygen
(http://www.doxygen.org/) written by Dimitri van Heesch.
Permission to use, copy, modify, and distribute this software and its documentation under the terms of the
GNU General Public License is hereby granted. No representations are made about the suitability of this
software for any purpose. It is provided "as is" without express or implied warranty. See the GNU General
Public License for more details.
Documents produced by doxygen are derivative works derived from the input used in their production; they
are not affected by this license.
2.8 SHA1 algorithm
Parts of this framework make use of an open source implementation of the SHA1 algorithm written by
Dominik Reichl (http://www.dominik-reichl.de).
MATRIX VISION GmbH22 April 2016 Version - 1.495
mvBlueLYNX-X Technical Manual
2.9 minizip, zlib
Parts of this framework make use of minizip (http://www.winimage.com/zLibDll/minizip.html) or zlib
respectively. The Zlib library allows to deflate compressed files and to create gzip (.gz) files. Zlib is free
software and small. The minizip package has been written by Gilles Vollant.
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held
liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and
to alter it and redistribute it freely, subject to the following restrictions:
The origin of this software must not be misrepresented; you must not claim that you wrote the original
1.
software. If you use this software in a product, an acknowledgment in the product documentation
would be appreciated but is not required.
Altered source versions must be plainly marked as such, and must not be misrepresented as being the
2.
original software.
This notice may not be removed or altered from any source distribution.3.
Jean-loup Gailly, jloup@gzip.org•
Mark Adler, madler@alumni.caltech.edu•
2.10 Expat
Expat is used to parse XML strings within the SDK.
2.10.1 Expat Copyright
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and
to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of
the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
622 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
2.11 OpenSSL
OpenSSL is used to perform license authentification.
2.11.1 OpenSSL License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the
original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are
BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact
openssl-core@openssl.org.
2.11.2 OpenSSL License
Copyright (c) 1998-2000 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that
the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the
1.
following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
2.
the following disclaimer in the documentation and/or other materials provided with the distribution.
All advertising materials mentioning features or use of this software must display the following
3.
acknowledgment: "This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit. (http://www.openssl.org/)"
The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote
4.
products derived from this software without prior written permission. For written permission, please
contact openssl-core@openssl.org.
Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in
5.
their names without prior written permission of the OpenSSL Project.
Redistributions of any form whatsoever must retain the following acknowledgment: "This product
6.
includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product
includes software written by Tim Hudson (tjh@cryptsoft.com).
2.12 CppUnit
The C and C++ code is tested using the CppUnit (http://cppunit.sourceforge.net) framework, which come
under GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999.
MATRIX VISION GmbH22 April 2016 Version - 1.497
mvBlueLYNX-X Technical Manual
2.13 NUnit
The .NET code is tested using the NUnit (http://www.nunit.org/) framework.
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held
liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and
to alter it and redistribute it freely, subject to the following restrictions:
The origin of this software must not be misrepresented; you must not claim that you wrote the original
2.
original software.
This notice may not be removed or altered from any source distribution.3.
822 April 2016 Version - 1.49MATRIX VISION GmbH
3 Revisions
DateRev.AuthorDescription
22 April 20161.49LANRemoved sensor -102d.
15 April 20151.47LANAdded lens protrusion data.
2 February 20151.46LANRemoved Gigabit Ethernet cables from accessories.
10 July 20141.46LANCorrected distance of the mounting holes on the back in
Dimensions of mvBlueLYNX-X.
02 July 20141.45LANAdded new troubleshooting solution How can I find my
mvBlueLYNX-X in the network?.
27 March 20141.44GRA
LAN
19 March 20141.43LANAdded accessory KS-BLX-PWR.
05 February 20141.42LANAdded use case for linescan mode.
04 December 20131.41LANAdded information about mvBlueLYNX-X option -xx9x
29 November 20131.40LANCorrected nomenclature concerning module version and added
25 November 20131.39RIN
LAN
7 November 20131.38LANAdded White balance with pixel format YUV422Packed.
22 October 20131.37LANAdded webcast about XForwarding on Windows.
21 October 20131.36LANUpdated chapter First Start.
15 October 20131.35LANAdded webcast links which are indicated by following symbol:
14 October 20131.34LANUser Set Default Selector is deprecated and will be replaced by
Corrected info about OpenGL® ES and added glossary term.
Added color code of cable KS-BLX-PWR in Circular connector
male.
(mvBlueLYNX-X without housing) in Technical Data.
order sample.
Information about file .gdbinit for the eclipse gdb debugger
Updated scope of supply.
.
Added chapter Bit-shifting an image.
User Set Default.
02 October 20131.33LANAdded max current consumption of the digital inputs.
12 September 20131.32GRA
LAN
23 July 20131.31LANAdded note about Power over Ethernet (PoE). With the POE
19 June 20131.30LANAdded figure in add-on board BLX-IO.
13.06.20131.29LANAdded information about add-on board BLX-IO.
26 April 20131.28GRAAdded information about the mvimpact-acquire-dotnet-apps
18 April 20131.27LANAdded chapter Using the serial port.
28 March 20131.26LANUpdated use case Creating a debouncing filter at the inputs.
19 February 20131.25LANAdded section MonoDevelop (IDE) for .NET developers.
MATRIX VISION GmbH22 April 2016 Version - 1.499
Added note about the need to install the recommended packages
when debugging threaded applications.
Corrected dimensional drawing in Dimensions of
mvBlueLYNX-X.
option, the camera is a class 2 compliant PoE device.
IPK.
Added new chapter X11.
mvBlueLYNX-X Technical Manual
GRAExtended section CPU throttling policy.
4 February 20131.24GRA
LAN
29 January 20131.23LANAdded table with summary of technical data.
16 November 20121.22GRA
LAN
14 November 20121.21LANUpdated Characteristics of the digital inputs.
22 October 20121.20LANAdded CE conformity declaration.
21 September 20121.18GRA /
LAN
6 September 20121.17LANClarified view of connectors (top view) in Technical Data.
5 September 20121.16LANAdded new troubleshooting solution "mvBlueLYNX-X boots
3 September 20121.15LANAdded line number in Circular connector male.
17 August 20121.14LANAdded use case Using the HDR mode with sensor -x02d.
16 August 20121.13LANAdded description about LLA.
18 July 20121.12LANAdded use case Creating a debouncing filter at the inputs.
Added section with List of mvIMPACT Acquire packages.
Added protection class and storage temperature to the table
summary of technical data.
Updated Nomenclature for PoE -Option.
Removed copy & paste note in Trigger.
Added sensors in Nomenclature.
Added note about network setup dialog box.
Added new sensors -X120d, -X102b and -X102d.
but there is no display".
4 July 20121.11LANAdded Index and Table of Figures.
25 June 20121.10LANCorrected dimensional drawing in Dimensions of
mvBlueLYNX-X.
8 May 20121.9LANAdded note about µSD card handling section in µSD card slot
(under the small metal plate) and Storing Data On µSD Cards or
USB Devices
20 April 20121.8GRA /
LAN
16 April 20121.7GRAAdded new section: Storing Data On µSD Cards or USB Devices
3 April 20121.6GRAAdded new section: Debug messages
21 March 20121.5LANRearranged chapter Application Installation and Usage and
Added new section: Application Desktop Files
Added new section: Autostart Applications
Added new section: Linescan mode (-102e)
Added new section: Device or resource busy debug messages
Added new section: Still seeing resource busy debug messages
Added new section: Restarting the camera
added section about wxPropView.
Added chapter Settings behavior during startup.
Added entry in glossary about Overlapped / pipelined transfer.
Added chapter GenICam and Advanced Features.
Added use case Reset timestamp by hardware.
Added use case Acquiring a number of images.
Added use case Controlling external strobe or flash.
Added use case Using the HDR mode with sensor -x00w.
Added use case External trigger by incremental encoder.
Added use case Creating different exposure times for
consecutive images.
Added use case Synchronized acquisitions using timers.
Added use case Generating a pulse width modulation (PWM).
Added use case Outputting a pulse at every other external
1022 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
trigger.
Added section Building the MATRIX VISION samples without
Eclipse
12 March 20121.4LANAdded frame rate benchmark of sensor -X102e (SXGA 1280 x
1024).
Added description how to handle mvBlueLYNX-X as a
peripheral device.
06 March 20121.3LANAdded note about the short circuit protection of the digital
outputs in Characteristics of the digital outputs
01 March 20121.2GRAAdded Installing the LiveDVD. Changed all references of
LiveCD to LiveDVD
28 February 20121.1LANAdded KS-BLX-VGA-USB 05.0 and MicroSD card to the
accessories.
23 February 20121.0LANChanged manual revision to 1.0
20 February 20120.14bGRAAdded mvIMPACT SDK Installation on PC/VM
01 February 20120.13bLANChanged mvIMPACT SDK - Virtual Machine to mvIMPACT
SDK - Ubuntu based LiveCD
30 January 20120.12bGRAAdded proxy information for opkg
27 January 20120.11bLANNow, all Eclipse explanations are in a separate chapter
24 January 20120.10bLANUpdated the Virtual Machine description
23 January 20120.9bGRAUpdated and corrected VGA, digital I/O and network connector
descriptions and pinouts in Technical Data
19 December 20110.8bLANAdded mvIMPACT SDK - Virtual Machine description. Added
chapter Use Cases
09 December 20110.7bGRAAdded Mounting Windows® Shares
03 November 20110.6bLANAdded mvIMPACT SDK description
13 October 20110.5bLANAdded -X102e sensor data.
06 October 20110.4bLANAdded delays of digital input and output.
05 October 20110.3bLANAdded MV-X I/O-BOX to the accessories.
26 September 20110.2bLANUpdated CMOS sensor data. Added sensor orientation figures.
August 20110.1bLANInitial version.
MATRIX VISION GmbH22 April 2016 Version - 1.4911
mvBlueLYNX-X Technical Manual
1222 April 2016 Version - 1.49MATRIX VISION GmbH
4 Graphic Symbols
4.1 Notes, 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
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.
An ATTENTION indicates a potential for property damage, personal injury, or
death.
4.2 Webcasts
WEBCAST This icon indicates a webcast about an issue which is available on our website.
MATRIX VISION GmbH22 April 2016 Version - 1.4913
mvBlueLYNX-X Technical Manual
1422 April 2016 Version - 1.49MATRIX VISION GmbH
5 Important Information
5.1 Important safety instructions
We cannot and do not take any responsibility for the damage caused to you or to any other equipment
•
connected to the mvBlueLYNX-X. Similarly, warranty will be void, if a damage is caused by not
following the manual.
Handle the mvBlueLYNX-X with care. Do not misuse the mvBlueLYNX-X. Avoid shaking, striking,
•
etc. The mvBlueLYNX-X could be damaged by faulty handling or shortage.
Do not use accessories not recommended by the product manufacturer as they may cause hazards.•
The product should be situated away from heat sources such as radiators, heat registers, stoves, or
•
other products (including amplifiers) that produce heat.
5.2 Operating considerations
5.2.1 Important safety notes
Use this camera with a 12V to 24V DC power supply with following specifications: 12V, 2.5A ± 5%
•
or 24V, 1,25A, ± 5%. MATRIX VISION offers a suitable power supply with part # MV-DC1201
BLX IO.
Observe that flammable objects, water or metal do not enter the camera interior. These may lead to
•
failure or accident.
Do not modify the camera or use the camera with external covers removed. These may cause failure,
•
void any warranties and pose a safety hazard.
Stop using the camera at the approach of electrical storm (thunder audible). Protect the camera from
•
rain if using it outdoors.
In event the camera shows any abnormality, switch off the camera and disconnect the power cord.
•
Contact MATRIX VISION.
5.2.2 Handling and cleaning
Do not attempt to disassemble camera.•
When installing or removing a lens, take care that water or dust does not enter the inside of the
•
camera.
5.2.3 Installing
Avoid installing or storing the camera in the following environments:
•
Environments exposed to direct sunlight, rain or snow.♦
Environments where combustible or corrosive gas exists.♦
Excessively warm or cold environment (Operating ambient temperature: 0 to 50 °C)♦
Humid or dusty environment.♦
Place subjected to excessive vibration or shock.♦
Environment exposed to strong electric or magnetic field.♦
It is recommended to mount the camera on a thermoconducting surface such as aluminum or other
•
metals rather than plastic or wood.
Please contact manufacturer or local distributor if you want to use additional enclosures for higher
•
ingress protection.
Do not aim the camera lens at the sun or other very strong light sources.•
CCD phenomenon: Smearing: Vertical smearing may appear in the image. However, this is not a
MATRIX VISION GmbH22 April 2016 Version - 1.4915
mvBlueLYNX-X Technical Manual
failure of the camera, but a technical fact of a CCD sensor.
5.2.4 Optimizing performance and life time
If the camera is used continuously for long time under high ambient temperature, the inside electrical parts
may deteriorate, resulting in shorter life span. Additional cooling by e.g. air convection is recommended.
5.2.5 Connectors
Confirm the power is off before connecting or disconnecting a signal cable. Handle connectors by the body,
not by the attached wires.
5.2.6 Cleaning
Use a blower or a lens brush to remove dust on the lens or the optical filter.•
Do not disassemble front flange.•
Clean case with dry soft cloth. Use neutral detergent liquid if needed; wipe the cover with dry cloth.•
Do not use benzene, thinner, alcohol, liquid cleaner or spray-type cleaner.•
If dust or other debris is located between the CCD and optical filter, consult dealer for cleaning by an
•
optical technician.
5.3 European Union Declaration of Conformity statement
The mvBlueLYNX-X is in conformity with all applicable essential requirements necessary for
CE marking. It corresponds to the EU EMC guideline 2014/30/EU based on the following
harmonized standards
Electromagnetic compatibility (EMC)
- Interference emmision EN 61000-6-3 / 2007
- Interference immunity EN 61000-6-2 / 2005
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.
1622 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
MATRIX VISION GmbH22 April 2016 Version - 1.4917
mvBlueLYNX-X Technical Manual
1822 April 2016 Version - 1.49MATRIX VISION GmbH
6 About this Manual
6.1 Goal of the manual
This manual gives you an overview of the mvBlueLYNX-X, MATRIX VISION’s next generation smart
camera family, its technical data and basic operation of the mvBlueLYNX-X. Programming the device is
detailled in a separate documentation, which will be available in an online format.
6.2 Contents of the manual
At the beginning of the manual, you will get an introduction to the possible usages of the smart camera. The
further chapters contain general information about the mvBlueLYNX-X including:
technical data•
sensor data•
filters and lenses•
The general information is followed by the description of the
delivered default configuration and•
how to start with the mvBlueLYNX-X for the first time.•
Afterwards, it describes how to install and use software on the mvBlueLYNX-X followed by a general
description about the software developement kit. A troubleshooting chapter shows how to detect damages and
other inconveniences. Last but not least, a glossary explains abbreviations and technical terms.
MATRIX VISION GmbH22 April 2016 Version - 1.4919
mvBlueLYNX-X Technical Manual
2022 April 2016 Version - 1.49MATRIX VISION GmbH
7 Introduction
Figure 1: mvBlueLYNX-X
The mvBlueLYNX-X is the next generation intelligent (a.k.a. smart) camera product line. The CPU core from
Texas Instrument's DaVinci™ 37 series of digital media processors is based on
the state-of-the-art ARM Cortex-A8 technology with up to 1 GHz target clock and1.
image processing acceleration by an 800 MHz DSP coprocessor for parallel handling of multiple pixel
2.
and float data.
Using a modular approach, the mvBlueLYNX-X can be combined with the same image sensors as the
mvBlueCOUGAR family of cameras, creating an unprecedented flexible product spectrum.
The main aim of the system is to offer a freely programmable smart vision system with a standard OS. For
this reason, a Linux distribution called Ångström, which is available and maintained for a variety of
embedded devices is running on the mvBlueLYNX-X. A graphical user interface based on X window system
called Enlightenment is provided. By connecting a standard VESA display (e.g. 1024 x 768 resolution, 24 bit
color depths and 60 Hz), you can work with the mvBlueLYNX-X like any other PC with LINUX as operating
system.
The mvBlueLYNX-X is ideally suited for all classical areas of machine vision, the large processing power
and high-end display and graphics capability make it perfect for even higher end applications. The hardware
capabilities can be teamed with MATRIX VISION's machine vision library mvIMPACT or third party
libraries such as MVTec Halcon™, EVT EyeVision, or OpenCV.
mvBlueLYNX-X - Installing HALCON Embedded
Possible uses for the mvBlueLYNX-X include:
an image acquisition device,•
an image acquisition and processing device displaying results on a display,•
an image acquisition and processing device controlling a machine or system via PLC (e.g. a
•
packaging machine or sorter) or its own I/O,
a decentral intelligent image processing device in
•
single camera applications or♦
multiple camera applications.♦
By connecting a USB camera (e.g. mvBlueFOX-IGC), it is also possible to create a stereo vision system.
Like many other MATRIX VISION hardware with an Ethernet interface, the mvBlueLYNX-X is a GenICam
compliant smart camera, using SFNC for the names of the camera features. The mvBlueLYNX-X uses
MATRIX VISION GmbH22 April 2016 Version - 1.4921
mvBlueLYNX-X Technical Manual
GenICam inside as a software API but does not have a Gigabit interface and does not use the GigE Vision®
protocol over its Fast Ethernet interface.
The following figure shows the software concept of the mvBlueLYNX-X and the other MATRIX VISION
camera devices:
Figure 2: Software concept of mvBlueLYNX-X
As shown in figure 2 the mvIMPACT Acquire interface is stacked on the GenICam layer. The mvIMPACT
Acquire interface internally uses the GenICam runtime libs, so that it can be considered as an user application
written with the GenICam interface.
7.1 Nomenclature
The mvBlueLYNX-X nomenclature scheme is as follows:
mvBlueLYNX-X(A)(B)(C)(D)-yyy-(1)(2)(3)(4)
- yyy: possible interface options
POE: Power over Ethernet, PoE class 2
2222 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
- (A): mvBlueLYNX version
1. Standard Version
- (B): Sensor type
0: CMOS
2: CCD
- (C): Sensor resolution
0a: 640 x 480, 1/3"
0b: 640 x 480, 1/2"
0d: 776 x 580, 1/2"
0w: 752 x 480, 1/3"
2 : 1280 x 964, 1/3"
2b: 1280 x 960, 1/3"
2d: 1280 x 960, 1/3"
2e: 1280 x 1024, 1/1.8"
3 : 1360 x 1024, 1/2"
4 : 1600 x 1200, 1/1.8"
5 : 2592 x 1944, 1/2.5"
5a: 2448 x 2050, 2/3"
- (D): Sensor color
G: Gray scale
C: Color
- (1): Lensholder
1 = C-Mount (standard = landscape)
2 = CS-Mount (landscape)
3 = C-Mount without back focus adjustment (landscape)
4 = CS-Mount without back focus adjustment (landscape)
5 = C-Mount (alternative = portrait)
6 = CS-Mount (portrait)
7 = C-Mount without back focus adjustment (portrait)
8 = CS-Mount without back focus adjustment (portrait)
The difference between (1) and (5), (2) and (6), (3) and (7) or (4) and (8) is the orientation of the
sensor.
-1111 is the standard delivery variant and for this reason it is not mentioned (see sample 1).
7.2 What's inside and accessories
Due to the varying fields of application the mvBlueLYNX-X is shipped with following accessories:
mvBlueLYNX-X (2 in figure 5)• mvBlueLYNX-X SDK DVD with SDK and tool chain•
2422 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
Figure 5: mvBlueLYNX-X - recommended scope of the order
Additionally, to use the mvBlueLYNX-X you will need at least:
MV-DC1201 BLX IO (1 in figure 5, power supply with digital I/O on separate cable)•
KS-BLX-VGA-USB 01.0 (3 in figure 5, VGA and USB "Y" cable)•
a lens (by default, the mvBlueLYNX-X is shipped without lens)•
a mouse and a keyboard, if you require local input and control•
a VGA display if you require a local HMI (human machine interface)•
MATRIX VISION GmbH22 April 2016 Version - 1.4925
mvBlueLYNX-X Technical Manual
Accessories for the mvBlueLYNX-X
Part codeDescription
MVBL-X I/O-BOXI/O-Box to connect and test a mvBlueLYNX-X camera, to loop the camera into an existing system, and to mix both connection variants selectively.
Manual:
http://www.matrix-vision.com/smart-vision-sensor-mvbluelynx-x.html?file=tl_files/mv11/support/Manuals/MV-X_IO-BOX_technical_manual_en.pdf
KS-BLX-IO6 02.0I/O cable for additional I/Os.
KS-BLX-PWRReady-made connection cable for power and I/O, length up to 20 m.
KS-BLX-VGA-USB
01.0
KS-BLX-VGA-USB
05.0
MICRO SD CARD
8GB
MV-DC1201 BLXIOPower supply 12V for mvBlueLYNX-X with digital I/O on separate cable, length: power 3 m, I/O: 0.5 m.
USB 2.0 cable and VGA cable for mvBlueLYNX-X, Hirose 12pin to USB2-A and VGA, length 1 m.
USB 2.0 cable and VGA cable for mvBlueLYNX-X, Hirose 12pin to USB2-A and VGA, length 5 m.
External MicroSD memory card with 8 GB.
2622 April 2016 Version - 1.49MATRIX VISION GmbH
8 Technical Data
8.1 Dimensions of mvBlueLYNX-X
Figure 6: mvBlueLYNX-X dimensions and connectors
LengthCMOSIS sensorsRemaining sensors
Y32 mm30 mm
Lens protrusionC-MountCS-Mount
X8 mm (9.5 mm with max. Ø 20
mm)
C-MountCS-Mount
Wapprox. 15 mm (C-mount)approx. 10 mm (CS-mount)
Z17.526 mm (in air)12.5 mm (in air)
6 mm
Figure 7: mvBlueLYNX-X dimensions and connectors order option -xx9x
Connector (camera side): AlysiumTech, type 61-W-30-1112 12 pins or equivalent•
Plug (matching cable plug): AlysiumTech, type 61-W-01-1112 12 pins or equivalent•
Plug (matching cable plug for mainboard connection header): Molex 0510211200•
8.3.1.1 Characteristics of the digital inputs
The digital inputs have inverse-polarity protection. If you are using negative voltage at the positive
input (e.g. sinusoidal signals), you do not have to connect a protective diode in series at the positive
input line.
High level+3 to +24 V
MATRIX VISION GmbH22 April 2016 Version - 1.4929
Low level0 to +0.3 V
mvBlueLYNX-X Technical Manual
Threshold (Low -->
High / High -->
Low)
I
max.
8.3.1.1.1 Delay
2.5 V ± 0.5 V
5mA
Figure 9: DigIn mvBlueLYNX-X
Figure 10: DigIn mvBlueLYNX-X Delay
CharacteristicsSymbolTest conditionsTyp.Unit
Turn-On timet
Storage timet
Turn-Off timet
ON
S
OFF
R = 2 kOhm, Output voltage
5V, IF = 16mA
2us
25
40
8.3.1.2 Characteristics of the digital outputs
High level+12.0 V to +24 V
I
out
4x 0.7 A max. short circuit
Low levelmax. +1 V
Each output has a short circuit protection between 1 A and 1.7 A (generally 1.3 A). So if you combine
two outputs with one load, the short circuit protection can have an effect.
3022 April 2016 Version - 1.49MATRIX VISION GmbH
The high-side switches feature:
undervoltage detection•
current limitation•
overtemperature protection•
short circuit protection•
mvBlueLYNX-X Technical Manual
Figure 11: DigOut mvBlueLYNX-X
8.3.1.2.1 Delay
Figure 12: DigOut mvBlueLYNX-X Delay
CharacteristicsSymbolTyp.Unit
Turn-On timet
Rise timet
Fall timet
Turn-Off timet
8.3.1.2.2 Example circuit 1: High-side switch uses power supply of the camera
ON
R
F
OFF
20us
10
8
30
In this case you have to bridge pin 2 (external power supply) with pin 10 (the supply of the outputs):
MATRIX VISION GmbH22 April 2016 Version - 1.4931
mvBlueLYNX-X Technical Manual
Figure 13: Bridge circuit between Pin 2 and Pin 10
8.3.1.2.3 Example circuit 2: High-side switch uses external (higher) power supply
Following figure shows, how to connect, for example, high power flash LEDs in series at the direct drive
output at Pin 3:
Figure 14: LEDs connected in series to Pin 3 powered externally via Pin 10
A 24 V power supply is connected at Pin 10. To protect the LEDs a series resistor is needed, which can be
calculated in this way:
Voltage: UHS - (n * UF) = U
D
Series resistor: R = UD / 0.7 A
Power: P = dutycycle * UD * I
The duty cycle is a coefficient < 1, which defines the power of the resistor. It is the ratio of the time period
while current flows compared to the total time. If the current always flows, P = U * I will be the
determining factor. If the current only flows a hundredth of time (duty cycle 1%), a resistor with a hundredth
of power will be enough.
For the connected LEDs and the ground of the external power supply, you have to use the ground of the
camera at Pin 1.
The series resistor has to handle the power, which depends on the duty cycle and the frequency.
8.3.1.3 Using the serial port
The external serial port appears as a Linux standard device with the name /dev/ttyO0. It may be
programmed using usual Linux methods like the termios library. The port has no hardware handshake and
may be used with baudrates of up to at least 115200 baud.
The name of the serial port is /dev/ttyO0 (character O, digit 0).
8.3.2 Circular connector female (VGA / USB)
3222 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
Figure 15: AlysiumTech 12-pin (female; top view), VGA / USB
Connector (camera side): AlysiumTech, type 61-W-31-1112 12 pins or equivalent•
Plug (matching cable plug): AlysiumTech, type 61-W-00-1112 12 pins or equivalent•
Plug (matching cable plug for mainboard connection header): Molex 0510211200•
The USB connector that is part of the "Y"-cable KS-BLX-VGA-USB 01.0 may be used to connect
USB 2.0 peripheral devices. At the moment it will not support USB 1.1 devices correctly. If you
connect a USB 1.1 device the USB port will turn off and you will need to restart the camera. To
connect both a mouse and keyboard at the same time it will be necessary to use a USB 2.0 hub.
The maximum VGA resolution depends on the pixel clock which cannot exceed 75MHz e.g. WXGA
1280 x 800 @ 60 Hz (=71MHz pixel clock) is possible.
MATRIX VISION GmbH22 April 2016 Version - 1.4933
mvBlueLYNX-X Technical Manual
8.3.3 Circular connector female (Digital I/O; via add-on board BLX-IO)
With the order reference "BLX-IO", the mvBlueLYNX-X can be extended by additional digital inputs and
outputs.
Figure 16: AlysiumTech 6-pin (female; top view), Digital I/O
Pin.Signal
1VCC_HSD
2GND
3IO_8
4IO_7
5IO_6
6IO_5
Connector (camera side): AlysiumTech, type 61W-21-0106 6 pins or equivalent•
Plug (matching cable plug): AlysiumTech, type 61W-00-0106 6 pins or equivalent•
8.3.3.1 Characteristics when used as digital inputs
There are four inputs parallel with the outputs with both
Figure 17: wxPropView - setting the addiitional digital I/Os
As shown in the figure, via LineMode you can set the mode of the I/O - either Output or Input. When
choosing Input, you can set the mv Input Threshold either to TTL or PLC.
8.3.3.2 Characteristics when used as digital outputs
The high-side switches has the same characteristics as the digital outputs of the circular connector male
(Power / Digital I/O). Additionally,
the outputs are protected against loss of ground,•
an external power supply is necessary (VCC_HSD signal) either via
•
pin 1 of this female connector or♦
pin 10 of the circular connector male (Power / Digital I/O) (which powers the output 1..4 as
With the -POE option, the camera is a class 2 compliant PoE device and pin 4,5 (V+) and 7,8 (V-) are
connected.
MATRIX VISION GmbH22 April 2016 Version - 1.4935
mvBlueLYNX-X Technical Manual
Figure 19: RJ45, LAN
Pin.SignalI/OCommentPin. on the mainboard connection
header
1D1+bidata positive
2D1-bidata negative
3D2+bidata positive
4NC-reserved for PoE
5NC-reserved for PoE
6D2-bidata negative
7NC-reserved for PoE
8NC-reserved for PoE
The pinout above corresponds to the standard TIA/EIA-568 for 100BASE-TX.
To use the Ethernet network connector please insert the appropriate cable.
A crossover cable is not needed. The camera supports autosensing of the cable polarity.
The camera has been set up to use a DHCP client to obtain an IP address. The camera has a unique MAC from
MATRIX VISION's assigned series. The Ethernet connector uses 100 Mbit/s FDX by default but should
auto-negotiate a lower rate or if needed.
8.3.5 USB-OTG (under the small metal plate)
The USB-OTG port is located under the small metal plate and is not restricted to USB 2.0 only. You can open
the metal cover with a 1.5 mm Allen key.
Using a USB "A" adapter, the OTG port will act like a host device. You can connect USB 2.0 or USB
•
1.1 peripherals like a mouse or keyboard or a memory stick. However, the maximum current
requirement of the connected device must not exceed 100 mA. You may connect a powered USB 2.0
hub to the OTG port to enable high-power devices such as hard disks to be used.
Using a USB "B" adapter or cable the OTG port will act like a peripheral device and may be used, for
•
example, for Ethernet-via-USB.
To use the mvBlueLYNX-X as a peripheral device as described in the second point, you will need a
configuration file usb-gagdet in /etc/default/.
The following content of this file ensures that the mvBlueLYNX-X will act like a
network adapter (RNDIS)•
serial interface (CDC ACM no further settings necessary) and•
The sample file /home/root/userdata.disk will be displayed as the USB storage resource. For
example, to create a FAT disc with 32 MB, the file should be like this:
cd
dd if=/dev/zero of=userdata.disk bs=1M count=32
sync
mkfs.vfat userdata.disk
If you want to have read/write access to userdata.disk on the mvBlueLYNX-X, you have to be
sure that the resource is not used on the host PC. Disconnect the mvBlueLYNX-X from the host PC and
mount the resource on the mvBlueLYNX-X locally:
cd
mkdir -p /media/disk
mount -n -t vfat -o loop userdata.disk /media/disk
The settings for the network adapter can be look like this in the /etc/network/interfaces files:
Now, the USB gadget will start while the system is booting. Manually, you can unload and start the additional
driver like this:
modprobe -r g_multi to unload it and1.
usb-gadget to start it.2.
At the host's side there is a difference between Linux and Windows system:
8.3.5.1 Linux
You will not have to install any drivers. After connecting, you have to configure the new network device
usb0:
sudo ifconfig usb0 up
sudo ifconfig usb0 192.168.0.203
The serial interface is available as /dev/ttyACM0.
The USB storage resource will be available as a normal USB stick.
8.3.5.2 Windows
Using Windows, you have to install the drivers of the serial interface and the network adapter after the initial
connecting of the mvBlueLYNX-X. In the device manager, the
CDC serial needs linux-cdc-acm.inf and•
RNDIS network adapter needs linux.inf.•
The USB storage does not need any driver installations.•
MATRIX VISION GmbH22 April 2016 Version - 1.4937
mvBlueLYNX-X Technical Manual
Both inf files can be found on the DVD.
8.3.6 µSD card slot (under the small metal plate)
The µSD card port is also located under the small metal plate. You can open the metal cover with a 1.5 mm
Allen key.
The µSD card slot supports cards of up to 32 GB capacity.
You can easily damage the µSD card or the mechanics of the mvBlueLYNX-X by improper operation.
Please be careful when inserting, removing, or handling the µSD card. Keep the µSD card at right
angles to the backplate when inserting it into the slot!
8.3.7 Power LED
ColorDescription
1. OffNo power or no bootloader found.
2. RedBootloader was recognized and FPGA is booting-up. N.B. The LED remains turned off for
approx. 10 seconds after applying power.
3. GreenLinux OS is running.
8.3.8 Status LEDs
The status LEDs can be used or set by the user. A standard Linux LED driver is used which can be controlled
by pseudo files in the /sys directory. I.e., the LEDs can be control by a script or by an application.
8.3.8.1 How to use the LEDs
For each LED there is a pseudo directory:
root@mvblx:~# ls -l /sys/devices/virtual/leds/
total 0
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:green:power
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:green:usr1
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:green:usr2
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:green:usr3
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:red:power
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:red:usr1
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:red:usr2
drwxr-xr-x 3 root root 0 Aug 5 16:20 mvblx:red:usr3
Under it, there is a pseudo file called brightness. In this folder you write either "0" (turn off) or another value
FrameStart
TriggerMode = On
TriggerSource =
TriggerActivation
= AnyEdge
Each rising edge of trigger signal acquires one image, integration
time corresponds to pulse width.
Each falling edge of trigger signal acquires one image,
integration time corresponds to pulse width.
Start the exposure of a frame when the trigger input level
changes from high to low or from low to high.
9.2.1.2 Exposure
After an active trigger, the integration phase starts with a maximum jitter of t
. If flash illumination is
trig
enabled in software the flash output will be activated exactly while the sensor chip is integrating light.
Exposure time is adjustable by software in increments of treadline.
9.2.1.3 Readout
When integration is finished, the image is transferred to hidden storage cells on the CCD. Image data is then
shifted out line-by-line and transferred to memory. Shifting out non active lines takes tvshift, while shifting
out active lines will consume treadline. The number of active pixels per line will not have any impact on
readout speed.
The CMOS sensors offer two different modes of operation:
Free running mode (Overlapping integration and readout)1.
Snapshot mode (Sequential integration and readout)2.
9.3.1.1 Free running mode
In free running mode, the sensor reaches its maximum frame rate. This is done by overlapping erase,
integration and readout phase. The sensor timing in free running mode is fixed, so there is no control when to
start an acquisition. This mode is used with trigger mode Continuous.
9.3.1.2 Snapshot mode
In snapshot mode, the image acquisition process consists off several sequential phases:
Trigger1.
Erase, exposure and readout2.
9.3.1.2.1 Trigger
Snapshot mode starts with a trigger. This can be either a hardware or a software signal.
The CMOS sensors used in mvBlueLYNX-X cameras support the following trigger modes:
Mode / Setting
(Device
Specific)
ContinuousTriggerSelector =
OnDemandTriggerSelector =
Setting (GenICam)Description
Free running, no external trigger signal needed.
FrameStart
TriggerMode = Off
Image acquisition triggerd by command (software trigger).
FrameStart
TriggerMode = On
TriggerSource =
Software
ExposureMode =
Timed
To trigger one frame
execute the
TriggerSoftware
command then.
OnLowLevelTriggerSelector =
FrameStart
TriggerMode = On
MATRIX VISION GmbH22 April 2016 Version - 1.4965
As long as trigger signal is Low camera acquires images with
own timing.
If an external trigger signal occurs (e.g. high or low), the sensor will start to expose and readout one image.
Now, if the trigger signal is still available, the sensor will start to expose and readout the next image (see
figure 36, upper part). This will lead to an acquisition just like using continuous trigger.
As long as trigger signal is High camera acquires images with
own timing.
Each rising edge of trigger signal acquires one image, integration
time corresponds to pulse width. (only with -X105)
Figure 36: External Trigger with CMOS sensors
If you want to avoid this effect, you have to adjust the trigger signal. As you can see in figure 36 (lower part),
the possible period is small.
The high level of the trigger has to be shorter than the frame time. In this case, the sensor will
make one image exactly. If the high time is longer, there will be images with the possible
frequency of the sensor as long as the high level takes. The first image will start with the
low-high edge of the signal. The integration time of the exposure register will be used.
OnLowLevel:
♦
The first image will start with the high-low edge of the signal.
OnHighExpose
♦
This mode is like OnHighLevel, however, the exposure time is used like the high time of
the signal.
9.3.1.2.2 Erase, exposure and readout
All pixels are light sensitive at the same period of time. The whole pixel core is reset simultaneously and after
the exposure time all pixel values are sampled together on the storage node inside each pixel. The pixel core is
read out line-by-line after integration.
Exposure and read out cycle is carry-out in serial; that causes that no integration is possible during read
out. The step width for the exposure time is 1 µs. Image data is then shifted out line-by-line and
transferred to memory.
MATRIX VISION GmbH22 April 2016 Version - 1.4967
mvBlueLYNX-X Technical Manual
9.3.2 Models
9.3.2.1 mvBlueLYNX-X100w (WVGA 752 x 480)
The sensor uses a full frame shutter (ShutterMode = FrameShutter), i.e. all pixels are reset at the same
time and the exposure commences. It ends with the charge transfer of the voltage sampling.
FeatureDescription
ManufacturerAptina
Sensor nameMT9V034
Max. frames
117
per second
Device
CMOS image sensor with HDR
Structure
SNR
DNR (normal /
55 dB / > 110 dB
HDR)
Image sizeType 1/3
Number of
752 (H) x 480 (V)
effective pixels
Chip size4.51 (H) x 2.88mm (V)
Unit cell size6µm (H) x 6µm (V)
ADC
The sensor uses a pipelined global snapshot shutter, i.e. light exposure takes place on all pixels in parallel,
although subsequent readout is sequential.
FeatureDescription
ManufacturerAptina
Sensor nameMT9M021
Max. frames
40.6
per second
Device
CMOS image sensor
Structure
SNR40 dB
DNR (normal /
> 61 dB /
HDR)
Image sizeType 1/3
Number of
1280 (H) x 960 (V)
effective pixels
Unit cell size3.75µm (H) x 3.75µm (V)
ADC
The sensor uses a full frame shutter (ShutterMode = FrameShutter), i.e. all pixels are reset at the same
time and the exposure commences. It ends with the charge transfer of the voltage sampling.
FeatureDescription
ManufacturerE2V
Sensor nameEV76C560
Max. frames
60
per second
Device
CMOS image sensor
Structure
SNR41 dB
DNR (normal /
62 dB /
HDR)
Image sizeType 1/1.8
Number of
1280 (H) x 1024 (V)
effective pixels
Unit cell size5.3µm (H) x 5.3µm (V)
ADC
10 bit (10-8 companding) → 10, 8 bit
resolution /
output
9.3.2.3.1 Spectral Sensitivity
9.3.2.3.1.1 Spectral response and quantum efficiency
Figure 43: mvBlueLYNX-X102e
MATRIX VISION GmbH22 April 2016 Version - 1.4973
9.3.2.3.2 Timings
NameValue
InternalLineLength944
InternalADCClock118.75
9.3.2.3.2.1 Free running mode
mvBlueLYNX-X Technical Manual
To calculate the maximum frames per second (FPS
ReadOutTime = RowTime * (ImageHeight + 10) / 1000
) in free running mode you will need following formula:
max
If exposure time is lower than frame time:
1000
FPS_max = ------------ ReadOutTime
If exposure time is greater than frame time:
1
FPS_max = ------------- ExposureTime
9.3.2.3.2.2 Snapshot mode
To calculate the maximum frames per second (FPS
ReadOutTime = RowTime * (ImageHeight + 10) / 1000
) in snapshot mode you will need following formula:
The sensor offers also a usage as a line scan sensor. One (gray scale sensor) or two lines (in terms of color
sensor) can be selected to be read out of the full line height of 1024 lines. This or these lines are grouped to a
pseudo frame of selectable height in the internal buffer of the camera.
The camera then outputs these frames which contain multiples of the same scan line(s) without gaps or
interruptions.
To operate in line scan mode, use the following properties:
In Setting -> Base -> Camera -> GenICam -> Device Control, please change the Device Scan Type
1.
to Linescan.
In Setting -> Base -> Camera -> GenICam -> Image Format Control, please set Width and Height.
2.
Height specifies how often the same line(s) will be used to reach the height of the image.
Use Offset X to shift horizontally the starting point of the exposed line.
Use Offset Y to shift the scan line vertically (typically to 512 which represents the optical center).
The sensor will not get faster by windowing in x direction.
7422 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
Finally, in Setting -> Base -> Camera -> GenICam -> Acquisition Control, please adapt the
3.
Exposure Time.
For high linescan rates the exposure time has to be proportionally low. To achieve the maximum
linescan rate of 12.6 kHz (gray scale sensor) the exposure time has to be set to approx. 60 us.
You may use longer exposure times at the expense of scanning frequency.
You can use either Continuous or a trigger mode as Acquisition Mode in Setting -> Base -> Camera ->GenICam -> Acquisition Control. However, if an external (line) trigger will have to be used, it is
absolutely required that the external trigger is always present. During a trigger interruption, controlling
or communication to the camera is not possible!
MATRIX VISION GmbH22 April 2016 Version - 1.4975
mvBlueLYNX-X Technical Manual
9.3.2.4 mvBlueLYNX-X105 (5MP 2592 x 1944)
This sensor uses two acquisition modes:
rolling shutter (ShutterMode = ElectronicRollingShutter) and•
global reset release shutter (ShutterMode = GlobalResetRelease).•
With the rolling shutter the lines are exposed for the same duration, but at a slightly different point in time:
Figure 44: CMOS sensor -X105 - rolling shutter
Moving objects together with a rolling shutter can cause a shear in moving objects.
The global reset release shutter, which is only available in triggered operation, starts the exposure of all rows
simultaneously and the reset to each row is released simultaneously, too. However, the readout of the lines is
equal to the readout of the rolling shutter: line by line:
Figure 45: CMOS sensor -X105 - global reset release shutter
This means, the bottom lines of the sensor will be exposured longer! For this reason, this mode will
only make sense, if there is no extraneous light and the flash duration is shorter or equal to the exposure
time.
Global reset release will only make sense, if a flash is used which is brighter than the ambient light. The
settings in wxPropView will look like this:
In this case, DigOut0 gets a high signal as long as the exposure time (which is synchronized with the
GlobalResetRelease). This signal can start a flash light.
FeatureDescription
ManufacturerAptina
Sensor nameMT9P031
Max. frames
11.7
per second
Device
CMOS image sensor
Structure
SNR> 38 dB
DNR (normal /
> 70 dB /
HDR)
Image sizeType 1/2.5
Number of
2592 (H) x 1944 (V)
effective pixels
Chip size5.70 (H) x 4.28mm (V)
Unit cell size2.2µm (H) x 2.2µm (V)
ADC
MATRIX VISION offers three filters for the mvBlueLYNX-X camera. The hot mirror filter is part of the
standard delivery condition.
10.1.1 Hot mirror filter
The hot mirror filter FILTER IR-CUT 20X1 FE has great transmission in the visible spectrum and blocks out
a significant portion of the IR energy.
10.1.1.1 Technical data
Diameter20.0 mm
Thickness1.0 mm
MaterialBorofloat
Characteristics T = 50% @ 650 ± 10 nm
T > 92% 390-620 nm
R
> 95% 700-1150 nm
avg
AOI = 0 degrees
ground with protection chamfer
Surface quality Polished on both sides P4
Surface
irregularity
5/3x0.06 on both sides
Figure 49: IR-CUT 20X1 FE wavelengths and transmission diagram
10.1.2 Glass filter
It is also possible to choose the glass filter Glass-20x1 with following characteristics:
10.1.2.1 Technical data
Glass thickness 1.0 mm
MATRIX VISION GmbH22 April 2016 Version - 1.4979
mvBlueLYNX-X Technical Manual
MaterialBorofloat without coating
ground with protection chamfer
Surface quality polished on both sides P4
Surface
irregularity
5/3x0.06 on both sides
10.2 Lenses
MATRIX VISION offers a high-quality selection of lenses. If you have questions about our accessories,
please contact our sales team: info@matrix-vision.com.
8022 April 2016 Version - 1.49MATRIX VISION GmbH
11 Initial Delivery Configuration
11.1 Booting
By default, the mvBlueLYNX-X boots
from the external µSD card slot,1.
then from the internal one.2.
It is not possible to boot from USB instead of µSD card.
11.2 Linux OS environment
The mvBlueLYNX-X has an internal FLASH memory (SD card, single level 1) with two partitions:
LINUX (886.4 MB, 54% allocated by Linux OS)1.
BOOT (70.6 MB, 6% allocated by bootloader)2.
Approximately 350 MB remain free for user applications. An external µSD card or a USB memory stick may
be used to add extra space for user applications.
MATRIX VISION offers special single level µSD cards. These cards allow more write and read cycles than
typical multi level cards. If you think the internal µSD card in not working properly, please have a look at the
Troubleshooting section.
By default, there are two users:
root:matrix (only with this user wxPropView is running at the moment)1.
matrix:matrix (no camera access at the moment)2.
11.3 Keyboard layout
By default the keyboard layout is set to US English.
For German keyboards this may be a better solution:
MATRIX VISION GmbH22 April 2016 Version - 1.4981
mvBlueLYNX-X Technical Manual
Open a terminal window.1.
setxkbmap -model pc105 -layout de2.
You could put the above line in a file in the directory /etc/profile.d in order to set the keyboard after
rebooting.
(You might need to install setxkbmap from the stable feed like this: opkg install setxkbmap)
11.4 VGA resolution
By default, the mvBlueLYNX-X has been pre-configured at a resolution of 1024 x 768 pixels, 24 bit @ 60
Hz. DDC - I²C lines are available, however, they are not used for the automatic resolution detection.
If you want to change the resolution permanently, you have to edit the /media/mmcblk0p1/uEnv.txt.
By default, the following line can be found there: dvimode=1024x768-24@60
The maximum possible resolution depends on the pixel clock not exceeding 75MHz i.e. a resolution of
WXGA 1280 x 800 @ 60Hz (=71MHz) is possible.
11.5 Network configuration
By default, the mvBlueLYNX-X gets its IP address via DHCP automatically.
Depending on the configuration of the network or the mvBlueLYNX-X (more precisely: if DHCP is used or
not), the following IP addresses are assigned:
If the mvBlueLYNX-X is configured to use a static IP address, the mvBlueLYNX-X will use this one.
1.
In this case, the mvBlueLYNX-X will only be accessible if the IP address is valid for the current
network.
With DHCP, the mvBlueLYNX-X will get an IP address from the DHCP server (default).2.
Without DHCP, the mvBlueLYNX-X will start with a logical link address (LLA) / zero configuration
3.
class B IP address ("169.254.X.X", netmask 255.255.0.0).
8222 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
Figure 50: Boot sequence of mvBlueLYNX-X
You can change settings like the static IP address to your needs as follows:
Open the following file /etc/network/interfaces.
1.
At the moment it looks like this:
...
...
auto eth0
iface eth0 inet dhcp
...
...
Now change it to this, replacing the values with ones that match you network, e.g.:
Some versions of the graphical Network Setup dialog box (Click on desktop: Menu Applications ->
Settings -> Network Setup) are known to write incorrect information to the file
/etc/network/interfaces. If you do use this dialogbox then please check the file
/etc/network/interfaces and remove any line that starts with the word iface static
(e.g. like this: iface static loopback dhcp) before rebooting.
Alternatively, use zeroconf networking. In this case the mvBlueLYNX-X will use an IP address in the range
169.254.0.0/255.255.0.0 if it cannot obtain a dynamic address from a DHCP server.
It is not possible to wake up the mvBlueLYNX-X using wake-on-LAN magic network packets.
MATRIX VISION GmbH22 April 2016 Version - 1.4983
mvBlueLYNX-X Technical Manual
11.6 Storing Data On µSD Cards or USB Devices
Write cycles of Flash memories like SD card or memory sticks are limited. To extend the life cycle of
the internal µSD card, we suggest not to use it for logging. For logs, please use a mounted network
directory, a USB stick or an external µSD card.
You can easily damage the µSD card or the mechanics of the mvBlueLYNX-X by improper operation.
Please be careful when inserting, removing, or handling the µSD card. Keep the µSD card at right
angles to the backplate when inserting it into the slot!
11.6.1 Powering Down The Camera
The mvBlueLYNX-X is a small computer with a file system stored on µSD card. Just like desktop PCs it
usually makes sense to power down the camera in a controlled manner instead of removing power suddenly.
The journaling file system used for the internal µSD card is designed to ensure that the file system is not
permanently damaged by a power outage but the individual files being written at the time may not be
complete. If you are certain that data is not being written to the internal µSD card and that all previously
written data is already stored on the card (see below for a method to confirm this), then removing power from
the camera in an uncontrolled manner is permitted.
11.6.2 Precautions
The following precautions may be useful to preserve data integrity if applications do write data to a µSD card:
Wherever possible make use of the standard GNU/Linux commands halt, reboot or shutdown
1.
instead of suddenly removing power from the camera.
After installing software or updating the camera with the opkg command or writing any data to a
2.
µSD card or USB memory device always use the sync comand before removing power.
In user applications that must write data to a µSD card or to a USB memory device ensure that a
3.
sync function call is made to flush all write buffers to the card before removing power to the camera.
Avoid writing data to the internal SD card. If this is not possible then ensure that the write buffers are
4.
not written to the card more than is absolutely necessary. e.g. if you write log messages every second
but flush the buffers (with sync) only every 30 seconds, you may improve the lifetime of the µSD
card at the cost of losing up to 30 seconds of data due to a power outage. Depending on your
application this may be an acceptable compromise.
Consider using an external USB memory device or a µSD card in the external SD-slot or a network
5.
directory for application data or logs. In this way the camera's system files will not be affected by a
power outage or data loss on the storage device used.
For data that does not need to be preserved after a power outage or camera restart consider using a
6.
RAM disk to store data e.g. use the /tmp directory.
8422 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
If you are unsure whether all write buffers have been written to a storage device or whether your
application is flushing buffers correctly please examine the number of dirty memory buffers in use like
this:
If this value is greater than 0 kB then it is necessary to issue a sync command or to wait for a
sufficient time (usually > 30 seconds!) before removing power, otherwise data loss is certain.
A reboot, halt or shutdown command implies a sync command.
umount of an external file system (e.g. USB device) will flush data for that device automatically.
11.7 X11
By default, the X window systems a.k.a. X-server is activated. To deactivate the server,
X window systems like Enlightenment support X windows forwarding to access the camera's desktop via
Linux or Windows PC's.
By default, the X11Forwarding is disabled.
To use this functionality, you have to
Edit the file /etc/ssh/sshd_config on the mvBlueLYNX-X.1.
Change the line X11Forwarding no to read X11Forwarding yes2.
Now create an empty authority file:
3.
touch /home/root/.Xauthority
Restart the mvBlueLYNX-X and4.
then login via ssh like this: (substituting the camera's IP address as appropriate):
5.
ssh -X root@192.168.65.55
If you use this form then the data will be compressed using a fast Blowfish algorithm which might be
useful on a narrow bandwidth link:
ssh -X -c blowfish root@192.168.65.55
MATRIX VISION GmbH22 April 2016 Version - 1.4985
mvBlueLYNX-X Technical Manual
Now start the X application e.g. wxPropView or LiveSnapFLTK -sLX* -pMono86.
mvBlueLYNX-X - XForwarding on Windows
11.8 FTP
By default, the mvBlueLYNX-X provides ftp connections with SSH encryption (pre-installed ipk package
openssh-sftp-server).
However, if you want to use another ftp server like vsftpd, you install the ipk package like this (with sensible
defaults):
opkg install vsftpd
The configuration file (with comments) will be found at /etc/vsftpd.conf. The new directories
/var/lib/ftp/ and /var/lib/ftp/in will be created and the server started. Full documentation of
the configuration options may be found at the vsftpd website.
11.9 CPU throttling policy
By default, when the camera is idle, the CPU frequency automatically steps down to 300 MHz. When the
CPU is heavily used, the CPU frequency will automatically increase in steps up to 1GHz.
If the performance of the camera is not a limiting factor and the small delay involved in the automatic
changeover of CPU frequency does not adversely affect your application we recommend leaving the default
CPU throttling scheme unchanged in order to save power and prolong the life of the components.
Otherwise, you may change the CPU throttling policy if your application requires a constant CPU frequency.
For this, you can use the CPU frequency widget in the toolbar on the desktop or you can use the following
commands in a terminal or console:
Now your camera will always run at 1GHz after booting.
If you are running performance tests or benchmarks don't forget to fix the CPU frequency to the
maximum of 1GHz before testing!
11.9.1 Green Automation!
The following table gives approximate power consumption values for a mvBlueLYNX-X100wG camera
when wxPropView is running, images are being captured and also displayed (i.e. at high CPU load). It
shows power consumption differences of up to approx. 0.6 W depending on the CPU frequency.
8622 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
Fixed CPU Frequency (MHz) Power Consumption (W)
3002.64
6002.88
8003.00
10003.24
Power consumption is very dependent on the sensor type fitted. In general, CCD and sensors with a
larger resolution will need consume much more power than small, CMOS sensors.
11.10 Mounting Windows® Shares
To access shared resources on a Windows® PC you will need the cifs kernel module and the user space
application mount.cifs. Install them using the following commands:
In the example above //triton/vision is the name of the Windows® PC and shared resource and /mnt
is the mount point on the mvBlueLYNX-X. Username and password are given using the options shown
above. Please substitute your own values.
There are more options available e.g. you can also specify a Windows® domain name. To see more details
just type mount.cifs .
If you need to access your shared resource regularly it makes sense to load the kernel module automatically
after every new start. To do this, please enter the following comands (once only):
echo "cifs" > /etc/modutils/cifs
update-modules
Now cifs will be loaded every time after booting.
To make things more comfortable add a line like this to the file /etc/fstab on the camera. Here, the same
share, user name & password as in the example above are shown. Please substitute your own values.
Now you can mount your shared resource at any time like this:
mount /mnt
At the moment automatic mounting of network resources will not work since the network is initialized
too late. We hope to provide a solution to this problem soon. For the same reason it is necessary to
unmount your network resources before rebooting the camera i.e. issue the umount /mnt command.
If you do not do this then a reboot will only proceed after a timeout of several minutes.
MATRIX VISION GmbH22 April 2016 Version - 1.4987
mvBlueLYNX-X Technical Manual
11.11 Mounting USB Sticks
USB sticks will normally be mounted automatically after you connect them to the camera. In order to identify
different USB sticks Ångström will choose the mount point automatically according to the volume label of the
USB stick. For example, if you have a USB stick manufactured by SanDisk it may well be supplied with a
volume label SANDISK. In this case the data on the stick can be accessed from the camera in the directory
/media/SANDISK. A stick without a volume label will be found at /media/disk. If the subdirectory of
/media already exists (e.g. because a USB stick has already been inserted and you wish to insert a second
stick with the same volume label or a stick has more than one partition on it) then a number will be
automatically added to the name of the new directory e.g. /media/SANDISK-1 or /media/disk-1.
If camera users are likely to use different USB sticks with unknown volume labels thereby making it difficult
for software on the camera to identify the directory containing the stick's data then it is possible to override
this behaviour by adding a new hal XML file called
/etc/hal//etc/hal/fdi/policy/50-usbstorage.fdi and containing exactly these lines:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<!-- find all removable, hotpluggable USB devices that contain a valid,
known filesystem and force the volume's label to a be a known
name - this will determine the mountpoint under /media
MATRIX VISION / GRA 12.12.2011
In addition please add the following line to the end of file /etc/udev/mount.blacklist if it does not
already exist:
/dev/sd*
Now any USB sticks will always be found at /media/usbmem , /media/usbmem1, ... You may, of
course, choose a different default name by altering the XML file shown above.
11.12 Application Desktop Files
To create a desktop file for an application click on the desktop and select: Settings -> All -> Apps -> New
Application or
Settings -> Settings Panel then Apps -> New Application
8822 April 2016 Version - 1.49MATRIX VISION GmbH
mvBlueLYNX-X Technical Manual
Figure 51: Application Menu
Here you can enter the details for any application, choose an icon etc. Applications entered here can be added
to menus or used as autostart applications (see below).
Desktop files will be stored in the directory /usr/share/applications and have the file
extension .desktop . Use the file wxPropView.desktop as a good example for the entries required if you
would like to create or edit a *.desktop file by hand.
11.13 Autostart Applications
11.13.1 GUI Applications
The Enlightenment GUI provides a mechanism for starting an application automatically as soon as the
desktop runs. Click on the desktop and select Settings -> All -> Apps -> Startup Applications or
Settings -> Settings Panel then Apps -> Startup Applications
MATRIX VISION GmbH22 April 2016 Version - 1.4989
mvBlueLYNX-X Technical Manual
Figure 52: Autostart Application Menu
Here you can add any known applications (i,e, those with *.desktop files, see above) and also determine their
order.
The list of autostart applications is stored in the file
/home/root/.e/e/applications/startup/.order, which will be created by the GUI.
You can also create and edit this file yourself.
11.13.2 Console Applications
You can, of course, start a console application by using the Enlightenment GUI method described above.
However, if you want to start a console application (i.e. an application that does not need the GUI) earlier or
at a specific point in the boot-up sequence then you can use the standard Linux/Ubuntu/Debian way: write a
start-up script e.g. /etc/init.d/myapp. Then put a symbolic link to this script in one of the /etc/rc*.d/ directories,
depending on where in the sequence you want the program to start.
e.g.
Create an executable script called /etc/init.d/myip.sh. Assume it looks like this:
1.
/sbin/ifconfig eth0 > /tmp/myip.txt
Now create a symbolic link like this:
2.
cd /etc/rc5.d
ln -s ../init.d/myip.sh S51myip
This will call the script just once after booting but after the network has been set up. It will create a temporary
file called /tmp/myip.txt containing the camera's IP address.
The exact position of the script in relation to other services that are being started e.g. networking can be
chosen by the number used. In this case S51 means that the script will be started after all scripts with a
lower number and before all scripts with a higher number in the same directory.
9022 April 2016 Version - 1.49MATRIX VISION GmbH
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.