VisionBox .NET Library  1.7.10.0 (2024-04-16)
VisionBox .NET Library Documentation

AGEXTypes.jpg
Supported hardware platforms

From left to right:

  • VisionBox AGE-X1, standard and with PCIe option
  • VisionBox AGE-X2 "Tiger" and "Leopard" (not shown: "Wildcat", "Cheetah", "Panther"...)
  • VisionBox AGE-X3 "Tigrillo"
  • Machine Vision Controller (PCIe card)
  • VisionBox AGE-X4 "Serval+"
  • PCIe Camera Link card
  • VisionBox AGE-X5
  • Machine Vision Manager (external USB device)

Overview

The VisionBox .NET Library gives the user access to interfaces and special features of the IMAGO VisionBox, VisionBoards and Machine Vision Manager. The library is based on the underlying VisionBox Interface Library for C++.

Real-Time Communication Controller

The Real-Time Communication Controller (RTCC) is the central device controlling the different interfaces. The major part of the controller is implemented by a FPGA. It provides user-programmable logic and internal units operating independent from the operating system. Many time-critital applications can be realized without using a real-time operating system.

The Library

All classes and functions for this library reside in the namespace VIB_NET.

Please take a look at the Devices and Examples pages on how to use the API.

Hardware support

The following table list the supported devices / classes for the different hardware platforms. Please note that the actual presence of devices depends on the actual hardware configuration and installed options:

Supported device classes for different hardware platforms
Platform Hardware component Supported device classes
(hover for description)

This class contains functions associated with the hardware component or the whole system

This class represents the LED Strobe Controller. This class controls the digital camera trigger output. This class controls the status LEDs. This class represents a group of optically coupled input signals. This class controls the optically isolated output signals. This class controls the RS-422 interface. This module controls the FPGA Trigger Unit. This class controls the Multiplexer unit which connects signal sources and sinks with each other. This class controls the I/O Scheduler which allows to store and emit output signals in hard real-time. This class represents the PowerOverEthernet (PoE) module, which allows gathering information about the current state of attached PoE devices. This class represents the TriggerOverEthernet (ToE) module which allows the generation of GigE Action Commands. This class represents the Camera Link grabber module. This class represents the RS232 which allows sending and receiving data over a RS232 port. This class controls the status display of the Machine Vision Controller.
VisionBox AGE-X1 Mainboard with RTCC yes yes yes yes yes yes no no no no
VisionBox AGE-X2 Mainboard with RTCC yes yes yes yes no yes yes no no no
Smart NIC yes no no no no no no yes no no
Camera Link yes no no no yes no no no yes no
VisionBox AGE-X3 I/O board with RTCC yes yes yes yes no yes yes no no no
VisionBox AGE-X4[1] Mainboard without RTCC yes no no no no no no no no no
VisionBox AGE-X5 Mainboard with RTCC yes yes yes yes no yes yes no no no
Smart NIC yes no no no no no no yes no no
Camera Link yes no no no yes no no no yes no
VisionBoards (PCIe cards) Machine Vision Controller (RTCC) yes yes no yes yes yes yes no no yes
Smart NIC yes no no no no no no yes no no
Camera Link card yes no no no yes no no no yes no
Machine Vision Manager USB device with RTCC yes yes yes yes yes yes yes no yes no no

  1. The VisionBox AGE-X4 additionally uses VisionBoards. It generally includes the PCIe Machine Vision Controller card, because the RTCC is not present on the mainboard.

Please note that each factory can provide multiple devices of the same type and each device can have multiple I/O channels.
For example, the VisionBox AGE-X1 has a single VIB_NET::CameraTrigger devices which controls two output channels.
The VisionBox AGE-X2 "Tiger" has four devices, each controlling one output.
The number of channels can be read with VIB_NET::CameraTrigger::NumberOfOutputs or similar properties for other devices.