Depending on the applets you are running on the board, you may need to enable the PoCL support via microDiagnostics. The automatic PoCL detection is disabled per default on marathon VCLx/deepVCL when running standard applets version 2.0 or higher, or when running individual applets created with VisualApplets version 3.0.6 or higher. When you use PoCL cameras together with such applets, you must enable automatic PoCL detection. This is possible in microDiagnostics (Framegrabber SDK version 5.5.1 or higher). For details, see Enabling PoCL Support.
To install the marathon VCLx/deepVCL in your computer, plug it into a PCIe Gen. 2 x4 slot or higher. The following image shows a marathon VCLx/deepVCL with two Camera Link cameras connected:
Product Variant deepVCL#
marathon VCLx is technically fit for CNN-based deep-learning applications. However, in order to actually run the deep learning applications provided by Basler, you need a specific Framegrabber SDK license on the frame grabber. Product variant marathon deepVCL comes already equipped with the license required for running CNN-based deep learning applications provided by Basler.
In addition, marathon deepVCL offers the full functionality of marathon VCLx.
Applets for marathon deepVCL#
On marathon deepVCL, you can run all applets available for marathon VCLx (see topic Acquisition Applets for mE5 marathon VCLx ).
Deep learning applications are provided by Basler in form of an applet file, too (*.hap file). Deep learning applets are individually developed by Basler to meet the purposes of your deep learning application. To get information about how to specify and order such an applet, contact our sales department or sales representative.
marathon deepVCL comes with the CNN runtime license. The license is already loaded onto marathon deepVCL. When you get hold of marathon deepVCL, you can run the deep learning applets Basler has developed for you. However, in case you erroneously erase the CNN runtime license on the board, you are provided with a back-up file containing your CNN license, so that you can re-license your marathon deepVCL frame grabber any time. For details on how to re-license your marathon deepVCL, see Licensing a Programmable Frame Grabber.
What is a Runtime License?
A runtime license is written directly into a dedicated memory space on your frame grabber. Before an applet that requires a runtime license is executed on the board, the system checks if the according runtime license is stored in the dedicated memory space. The frame grabber can only run those applets if the runtime license is available on the board.
In addition to the image acquisition and image processing functions that are included in the delivery, marathon VCLx/deepVCL can be programmed to fulfill highly specific image processing tasks that are required by a specific application. The programming can be done by Basler/ a certified partner, or by yourself using the easy-to-use graphical FPGA programming environment VisualApplets.
Production Line Integration#
For integration into a production line, marathon VCLx/deepVCL offers multiple general purpose inputs and outputs. 4 to 20 of the GPIOs (depending on the hardware add-ons used) are galvanically isolated.
These GPIOs enable you to do the following:
- Control peripheral devices by sending trigger signals, e.g. lighting signals and cameras signals.
- Receive various trigger signals from peripheral devices, e.g., shaft encoders and light barriers.
- Synchronize multiple marathon VCLx/deepVCL frame grabbers.
- Synchronize connected devices.
Communication between camera and marathon VCLx/deepVCL is realized via four CC signals per Camera Link cable.
Software Programming and Configuration Interface#
marathon VCLx/deepVCL offers an easy-to-use API. The Framegrabber API allows to integrate the frame grabber into any image processing application. You can use the Framegrabber API to write code in the following languages:
- C# (wrapper available)
- Python (wrapper available)
For more information about the Framegrabber API, see the Framegrabber API documentation.
Alternatively, you can use Basler's GenTL Interface to develop your application in form of a GenTL consumer. For more information about the Basler GenTL Interface, see GenTL Interface documentation.
Connectors and LEDs#
marathon VCLx/deepVCL has the following connectors:
In addition to its ports, marathon VCLx/deepVCL offers an on-board configuration switch for activating a fall-back FPGA configuration, called SAVE configuration. For details regarding the SAVE configuration, see FPGA Fall-Back Configuration.
LEDs on the Board#
marathon VCLx/deepVCL provides the following LEDs on the board:
|LED Name||LED Color||Meaning|
|TRG_PWR||Green||Front GPIO is connected to external power (power IN).|
|SAVE||RED||SAVE configuration is used for FPGA configuration|
|READY||Orange||The FPGA has been configured successfully and is ready for operation. LED READY also gives light when SAVE configuration is used on FPGA.|
|PGOOD||Orange||PGOOD=Power Good |
All voltages are applied correctly.
|CL A||Orange||Port A is connected to a camera that provides a clock.|
|CL B||Orange||Port B is connected to a camera that provides a clock.|
|PoCL A||Green||Power over Camera Link active on port A: Camera on port A is provided with power by frame grabber via Camera Link cable.|
|PoCL B||Green||Power over Camera Link active on port B: Camera on port B is provided with power by frame grabber via Camera Link cable.|
|USR1||Orange||User-defined. The LEDs can be controlled via software. They aren't related to camera connectors and can be used for any purpose.|
|USR2||Orange||User-defined. The LEDs can be controlled via software. They aren't related to camera connectors and can be used for any purpose.|
|PWR||Green||Frame grabber gets 12 VDC IN via PCIe interface.|
|Order Number marathon VCLx||2200000360|
|Order Number marathon deepVCL||108094|
|Host Interface||PCIe Gen 2 x4 (Direct Memory Access)|
|Bandwidth (typ./max.)||Up to 1.8 GB/s sustainable data bandwidth (maximal Camera Link data rate 850 MByte/s)|
|On-Board Memory||2 GByte DDR3-RAM|
|Power Supply (Input) / Current PCIe Slot||12 VDC (±5 %) / <1.5 A (actual values depend on processing)|
|Power Supply (Input) / Current PCIe 6-pin Connector||12 VDC (±5 %) / <6.5 A (actual values depend on connected PoCL cameras)|
|PoCXP Supply (Output)||4 W of 12 VDC regulated power per each Camera Link connector|
|Power Consumption||Typ. current 1.4 A @12 VDC (actual values depend on processing)|
|Size (L x H)||PCIe standard height |
Half length card:
167.64 mm x 111.15 mm
|Camera Interface||2 x Camera Link 2.0 standard (2 * SDR 26) (mini CL)|
|Ambient Temperature||50 °C (0 LFMa) |
60 °C (100 LFMa)
An adequate airflow in the computer is recommended.
|FPGA Operating Temperatureb||0–85 °C at 100 LFMa|
|Storage Temperature||-50–80 °C|
|Humidity during Operation||5–90 % non-condensing|
|Humidity during Storage||5–95 %|
LFM = Linear Feet per Minute, unit for measuring airflow velocity.
Temperature being measured directly on the FPGA. You can read out the measured value in all applets that are available for marathon VCLx/deepVCL via the applet parameter
The PCIe bus data throughput depends on the mainboard, the chip set, and the BIOS configuration of the host computer. The number of installed PCIe boards also affects the throughput, e.g. a PCIe x8 connector may support only x4 performance. Always check the mainboard manual thoroughly to be sure.
The Front GPIO Connector#
The front GPIO connector covers the basic trigger setup of your frame grabber. Its trigger connector allows you to control peripheral devices (PLC) and to synchronize multiple marathon VCLx/deepVCL boards.
The socket is located directly on the slot bracket:
In default configuration, the trigger connector of the front GPIO connector offers:
- 3 differential input signals or 2 differential and 1 single-ended input signal in pull-up mode
- 2 TTL output signals
You can configure the pin assignment of the front GPIO connector to provide different input signals, e.g.:
- 4 single-ended signals (and no differential signals).
To change the GPIO configuration, use the command line tool installed with the Framegrabber SDK.
Pin Layout of the Front GPIO Connector#
|PIN Number (3P FPGA)||Galvanically Isolated||Signal||Reference Signal|
|1||No||GPO 0 (TTL)||5 VDC / global GND (pin 6)|
|2||No||GPO 1 (TTL)||5 VDC / global GND (pin 6)|
|3||No||Reserved for RS 485 (GND)|
|4||No||Reserved for RS 485|
|6||No||GND (global GND)|
|7||No||5 V_OUT (0.5 A max)|
|8||Yes||GPI 2 (if used for differential signal)||GPI voltage IN (pin 10) / GPI GND (pin 15)|
|9||Yes||GPI 3 (if used for differential signal)||GPI voltage IN (pin 10) / GPI GND (pin 15)|
|10||Yes||GPI voltage IN (4.5–28 VDC)|
|11||Yes||GPI 0+||GPI voltage IN (pin 10) / GPI GND (pin 15)|
|12||Yes||GPI 0-||GPI voltage IN (pin 10) / GPI GND (pin 15)|
|13||Yes||GPI 1+||GPI voltage IN (pin 10) / GPI GND (pin 15)|
|14||Yes||GPI 1-||GPI voltage IN (pin 10) / GPI GND (pin 15)|
Extra Voltage IN/GND for Galvanically Isolated Circuit#
All General Purpose Inputs (GPIs) of the front GPIO connector are galvanically isolated. The incoming signals are transferred to the frame grabber via digital isolators. This way, the frame grabber is securely protected against high incoming voltages.
However, to operate the internal GPI circuits, you must connect a voltage source and ground: On pin 10, you apply the voltage (GPI voltage IN) that serves as operating voltage for the internal operational amplifiers. On pin 15, you connect the according ground (GPI GND).
Supply Voltage Required
The marathon VCLx/deepVCL trigger system needs to get supply voltage on the GPI Voltage IN pin (pin 10). If you want to connect devices that have no PWR pin, you must provide the power supply to the GPI Voltage IN pin (pin 10) from an external source.
You can operate marathon VCLx/deepVCL as follows:
|Number of Cameras||Number of Camera Ports||Number of Frame Grabber Ports||Mode||Topology|
When connected to the computer power supply via the PCIe 6-pin connector, which always provides 12 V, marathon VCLx/deepVCL supports Power over Camera Link (PoCL).
If you are going to use multiple marathon VCLx/deepVCL boards in one host computer, make sure you have one PCIe Gen. 2.0 x4 slot or higher per board available in the host computer. For more information, see the following topics:
To ensure optimum use of system resources, not all image acquisition and processing features designed for marathon VCLx/deepVCL are loaded onto marathon VCLx/deepVCL simultaneously.
Instead, Basler provides various compilations of specific image acquisition and processing features that are combined to meet the requirements of a specific application field. These compilations are called applets, since they work like apps on mobile devices.
Typically, an applet supports a specific camera interface standard and topology, specific image acquisition features, and possibly specific image (pre-)processing features.
Applets come in .dll files.
Refer to Acquisition Applets for marathon VCLx/deepVCL for more detailed information about the standard applets delivered with your frame grabber and their dependency on the topology used.
In addition to the acquisition applets that are included in the delivery, marathon VCLx/deepVCL can be programmed to fulfill highly specific image processing tasks that are required by a specific application. The programming can be done by Basler/ a certified partner, or by yourself using the easy-to-use graphical FPGA programming environment VisualApplets.