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)