ADLINK PCIe GIE7x Poe+Acquisition Card Configuration and Triggering Troubleshooting

ADLINK PCIe GIE7x Poe+Acquisition Card Configuration and Triggering Troubleshooting

In the field of machine vision and industrial inspection, GigE Vision has become one of the mainstream camera interfaces due to its long-distance transmission, high bandwidth, and standardized protocols. And PoE+(Power over Ethernet Plus) technology greatly simplifies on-site wiring by simultaneously supplying power and transmitting data through the same Ethernet cable. The ADLINK PCIe-GIE7x series, as a 2/4-channel PCI Express x4 GigE Vision PoE+frame acquisition card, not only provides a power supply capability of up to 30W/port, but also offers a highly integrated and reliable solution for multi camera systems through hardware level PoE protection, intelligent power management, and the PRO model's unique ToE (Trigger over Ethernet) function. This article will provide engineers with a practical operation guide from the aspects of hardware selection, PoE power management, trigger synchronization mechanism, installation configuration, and common troubleshooting, to help quickly deploy stable visual acquisition systems.

Product series and selection points

The PCIe-GIE7x series includes four models: GIE72 (2-port), GIE72 PRO (2-port+advanced features), GIE74 (4-port), and GIE74 PRO (4-port+advanced features). The core differences are as follows:

Number of ports: 2 or 4 independent Gigabit Ethernet ports, each with a speed of 1 Gb/s, supporting link aggregation and jumbo frames (9KB).

Additional features of PRO version: ToE (firmware based Ethernet trigger) and software license management (integrated SHA256 secure EEPROM for third-party software licensing).

PoE total power: up to 20W when powered solely by PCIe slots; up to 61.6W when connected to external 4-pin or 6-pin Molex (+12V); up to 120W when connected to two Molex interfaces at the same time, supporting high-power multi camera operation.

The selection should be based on camera power consumption, quantity, and whether synchronization or software authorization protection needs to be triggered.

Deep analysis of Poe+power supply

1. Differences between PoE and PoE+standards

IEEE 802.3af (PoE) provides a maximum of 15.4W/port, while 802.3at (PoE+) increases to 30W/port. PCIe-GIE7x automatically identifies the type of connected equipment and adapts to the corresponding power level. The actual available power is affected by cable resistance, for example, Class 3 devices can only obtain about 12.95W at the end of a 100 meter network cable, and a margin needs to be reserved during design.

2. Multiple hardware protection mechanisms

This series is equipped with comprehensive protection circuits to ensure power supply safety:

Overvoltage/Undervoltage Protection (OVP/UVP): Automatically cuts off when the output voltage exceeds the range. The specific threshold can be found in Table 1-2 of the manual.

Overcurrent protection (OCP): Set the current upper limit based on the PoE class (such as 638mA ± 5% for Class 4), and turn off if exceeded.

Over temperature protection (OTP): The default high temperature threshold is 130 ° C, and the low temperature recovery threshold is 90 ° C. Users can adjust it within the range of 80-130 ° C (HT) and 70-120 ° C (LT) through SDK or tools.

When the protection is triggered, the PoE power supply to the corresponding port is interrupted and will be restored after the conditions are restored, effectively preventing damage.

3. Intelligent power budgeting and priority management

PCIe-GIE7x automatically calculates the total budget based on the power supply source:

PCIe slot only: 20W

Only 4-pin or 6-pin connectors: 61.6W

Simultaneous use of 4-pin and 6-pin (PRO version only): 120W

If the total requested power of connected devices exceeds the budget, the system will allocate power according to a fixed priority (Port1>Port2>Port3>Port4), and low priority ports will be powered off until the power is sufficient. Users can monitor the power consumption, classification status, and remaining budget of each port in real-time through the Power Management Utility provided by ADLINK, and can control the switch of each PoE channel through SDK programming to achieve refined power management.

Core features of PRO version: ToE and software license

1. Working principle of ToE (Trigger over Ethernet)

Traditional multi camera synchronous triggering requires additional physical triggering wires, which increases the risk of wiring and interference. The PRO version utilizes the Action Command mechanism in the GigE Vision standard to send broadcast trigger packets over the same Ethernet cable. When an external trigger signal (such as a grating sensor) is input to the onboard isolation trigger input (CN6 or I/O bracket), the firmware sends the pre configured Action Command message to all cameras in the network with a constant delay (without jitter). After receiving the matching DeviceKey, GroupKey, and Mask, the camera performs preset actions such as frame start, capture stop, or timestamp reset. Due to constant latency, the synchronization accuracy between multiple cameras can reach microsecond level without the need for additional hardware, truly achieving a "single cable" solution (data+power+trigger).

2. Key points of ToE configuration

Each channel can independently set the content of ActionCommand, which needs to be consistent with the camera configuration. Suggest using ADLINK Smart GigE Tool for parameter setting and verifying trigger response. The external trigger input is isolated type, supporting differential or single ended signals, and is connected through a CN6 connector (pin definitions are shown in Table 1-19).

3. Software License Management

PRO onboard secure EEPROM (based on SHA256 encryption) can store authorization information for third-party software. Software developers can implement authorization models such as pay per function and node locking through SDKs, without the need for external encryption dongles, which not only protects intellectual property rights but also facilitates distribution. For end users, they only need to purchase licenses for the required functions and import the board to unlock the corresponding functions and reduce costs.

Hardware Layout and Interface Detailed Explanation

1. Board size and installation

Size 167.6mm × 106.6mm, standard PCIe half height card. Requires insertion into x4, x8, or x16 slots, but only uses x4 channels. Before installation, ensure that there is sufficient heat dissipation space inside the chassis, especially when high PoE power output generates significant heat.

2. Power connector

4-pin Molex (CN3): Provides+12V and GND, with a maximum of 6A.

6-pin Molex (CN4): Provides three+12V channels, two GND channels, and one Sense channel (for detecting connections), with a maximum of 6A. Simultaneously connecting both channels can reach 120W (PRO only).

3. Trigger input interface (CN6 and I/O bracket)

Provide 4 isolated trigger inputs (Line 1~Line 4) and a common terminal COM_i, supporting 10~24V levels, which can be used to connect external sensors or PLC signals. Note that CN6 is an onboard 10 pin connector, while I/O bracket is an optional accessory for easy external wiring.

4. Status indicator light

RJ45 port dual color LED: The left side indicates the speed (Off/10M, green/100M, yellow/1000M), and the right side indicates the link and activity (off/no link, green/link, flashing/data activity).

PoE yellow LED: one for each port, constantly lit to indicate PoE power supply.

On board 9 LEDs (LED1~9) indicate PCIe link status, bandwidth, and error conditions (see Table 1-18 for details), used for diagnosing bus connections.

Temperature sensor: located at a specific position on the board, used for OTP monitoring.

5. Configure switch

SW1 (Card ID): 4-digit DIP switch, supports 16 IDs from 0 to 15, must be unique when using multiple cards. Default ID=15 (all ON).

SW3 (PoE switch): Bit1 controls PoE hardware enable (ON=disabled, OFF=enabled, default OFF); Bit2 controls the initial state of PoE after power on (ON=off, OFF=on, default OFF). If automatic power supply is required upon startup, simply leave it at default.

Installation and driver configuration process

1. Physical installation

Turn off the power and turn on the power box, insert the card, and tighten the fixing screws. If high-power PoE is required, be sure to connect the Molex power cord (it is recommended to use a 16AWG or higher cable). Connect the Ethernet cable to the camera and gigabit switch (or directly connect).

2. Driver and SDK installation

Download the Intel I210 network card driver (or official Intel driver) and PCIe GIE7x dedicated driver and SDK package from the ADLINK website. Supports Windows 7/8.1/10 (32/64 bit). After installation, multiple 'Intel I210 Gigabit Network Connections' should appear in the Device Manager, corresponding to each port.

3. Configuration tool

Use the Smart GigE Tool for camera discovery, IP configuration, PoE settings, ToE action configuration, and firmware updates. The Power Management Utility is used to monitor PoE power consumption and temperature. It is recommended to first verify the camera image capture through tools before writing the application.

4. Precautions for multi card and multi camera systems

Each card is assigned a different ID through SW1, and the system can install multiple cards simultaneously.

PoE is independently managed between different cards, but the total power consumption is limited by the power input of each card.

To achieve cross card trigger synchronization, external trigger signals can be used in parallel or ToE broadcasting can be used (but network multicast configuration should be noted).

Common problems and troubleshooting

1. PoE port not powered

Check if SW3 Bit1 is OFF (PoE enabled).

Confirm that the connected camera supports PoE or PoE+, and check if the network cable is compliant (Cat5e or above, and all four pairs of cables are connected).

Check the classification status and power allocation of the port in the Power Management Utility; If the total budget is insufficient, ports with low priority will be closed, and the power input can be adjusted or the load on high priority ports can be reduced.

Check if the temperature is too high to trigger OTP, and improve heat dissipation or increase LT/HT threshold appropriately (but with caution).

2. Trigger no response (PRO version)

Confirm that the external trigger signal level is correct (isolated input supports high level 3~24V), and the polarity (rising/falling edge) is set correctly in the tool or SDK.

Verify that the DeviceKey/GroupKey/Mask of the Action Command matches the camera configuration (most cameras require setting the trigger source to "Action Command" on the camera properties page).

Measure the CN6 pin signal with an oscilloscope and confirm that the trigger pulse has reached the card end.

Check if the firmware version supports ToE and update the firmware if necessary.

3. Image frame loss or unstable network

Check the quality and length of the network cable (recommended<100m) to avoid strong electromagnetic interference.

Turn off the jumbo frame option or adjust the receive buffer size.

Check the CPU load, and if it is too high, enable interrupt modulation or adjust the network card parameters.

Confirm whether the PCIe link is operating in x4 Gen2 (determined by LED5/6 status). If it is in Gen2, the bandwidth will be halved, which may affect simultaneous transmission of multiple cameras.

4. Multiple card ID conflicts result in abnormal recognition

Check the SW1 settings of each card to ensure uniqueness. If the ID is duplicated, the system may only recognize one of them. After readjustment, it is necessary to shut down and restart.

5. Automatic power-off due to overheating of the board

In high-power (120W) mode, the ambient temperature should be below 40 ° C and the chassis should be well ventilated. Can monitor temperature sensor values and install fans if necessary.

Practical skills and maintenance suggestions

Power planning: First, calculate the maximum power consumption of all PoE cameras (refer to the camera manual), and then select the corresponding model and power connection method. If the total demand exceeds 61.6W, GIE74 PRO must be selected and connected to dual Molex.

Trigger cable: Although ToE eliminates the need for physical trigger wires, if the camera does not support Action Command, external triggering is still required. In this case, it is recommended to use shielded twisted pair and single ended grounding.

Firmware Upgrade: Regularly follow the ADLINK official website for the latest firmware to fix potential issues and improve stability. Backup the current configuration before upgrading.

Logging: Use the error callback function in the SDK to record PoE exceptions and trigger loss events for post analysis purposes.