ADLINK PCIe-U300 Series USB3 Vision Acquisition Card Deployment Guide

If connecting an external Molex power supply, be sure to connect it properly before turning it on to avoid hot swapping.

2. Card ID setting (SW1)

When installing multiple PCIe-U300 cards in the system, a unique ID (0~15) needs to be assigned to each card through the SW1 4-digit DIP switch, with a default ID of 15 (all ON). ID is used by software to identify different devices and ensure correct API calls. After setting, it needs to be restarted to take effect.

3. Status LED diagnosis

Onboard 9 LEDs (1-9) indicate PCIe link status and USB controller status:

LED 2/6/7/8 (upstream link):

Extinguish: Upstream function disabled (abnormal)

Always on: PCIe x4 Gen2 normal (default)

Blinking: Insufficient bandwidth (possibly due to insertion into x1 slot or high bus load)

LED 1/3/4/5 (downstream link to USB controller):

Extinguish: Downstream function disabled (abnormal)

Always on: Normal

LED 9 (PCIe switch error):

Extinguish: Normal

Always on: An unexpected error occurred in the switch

If the LED flashes or is abnormal, first check if the slot is x4 or above, and confirm the PCIe link speed setting in the BIOS.

Driver and software environment preparation

1. Operating system requirements

Windows 7/10 (64 bit recommended), also supported by Linux.

Windows 7 special requirements: Microsoft Kernel Mode Driver Framework v1.11 and VNet 033929 patch must be installed (otherwise FL1100 driver cannot be installed). It is recommended to use Windows 10 directly to avoid this issue.

2. Driver installation

USB 3.0 Host Driver: Download the FLUSB3.0 driver (applicable to FL1100) from ADLINK or Fresco Logic official website.

Power Management SDK: ADLINK provides AVS-SDK, including USB port power control API, without additional authorization.

Installation sequence: First install the USB controller driver, then install the AVS-SDK. After installation, the device manager should display multiple 'Fresco Logic USB 3.0 Host Controllers' and corresponding root hubs.

Common troubleshooting and solutions

1. The camera cannot recognize or there is no image

Check power supply: Use software to read the port current status (AVS API) and confirm that the voltage/current is normal. If overcurrent protection is triggered, the host needs to be restarted.

Check the cable: USB 3.0 cables must comply with the standard. Poor quality cables may cause a speed drop to USB 2.0 (480Mbps), affecting image transmission. It is recommended to use high-quality cables with shielding, with a length not exceeding 5 meters (limited by USB 3.0 specifications).

Check bandwidth: If multiple high bandwidth cameras are working simultaneously, it may exceed the total bandwidth of a single controller (approximately 400MB/s actual). You can try assigning the camera to ports on different controllers (U304, each port is independent and there is no such problem); U308/U312 should pay attention to port grouping. Insufficient bandwidth can be determined by the flashing status LED.

2. System instability or blue screen

Insufficient power supply: If Molex is not connected and the total load exceeds 20W, it may cause a+12V voltage drop, leading to system restart. Be sure to connect an external power source as required.

PCIe slot limitation: Some motherboard x16 slots actually only support x1 or x2 links, which can be confirmed by LED 2/6/7/8 status. If it flashes, you need to replace the slot or check the BIOS settings.

3. Frequent triggering of overcurrent protection

Check the rated current of the connected camera. If it is close to 1.5A, it is recommended to replace the low-power camera or use external power supply (cut off USB power supply).

Possible port short circuits or cable damage, eliminate them one by one.

4. Resource conflicts when multiple cards are used simultaneously

Each card is assigned a different ID through SW1, and the driver will automatically recognize it. If there is an ID conflict, the system only recognizes one of them.

Multiple cards jointly consume PCIe resources, and it is necessary to ensure that the motherboard chipset supports sufficient PCIe channels (such as using Intel C612/C621, etc.).

5. U312 expansion port is not working

Confirm that the internal 20 pin ribbon cable is securely connected to the expansion bracket and the bracket is well secured.

The current limit of the expansion port is relatively low (900mA). If the camera requires higher voltage, it may cause undervoltage. Please use the front panel port instead.

Performance optimization and maintenance recommendations

Bandwidth allocation: For U308/U312, understand the mapping relationship between ports and controllers (usually every two ports share one FL1100). You can determine the "location" information by viewing it through the device manager. Distribute high bandwidth cameras to different controllers as much as possible.

Firmware update: Regularly visit the ADLINK official website to obtain the latest firmware and drivers, and fix known issues.

Attention to heat dissipation: Under high load, the power conversion circuit on the card may generate heat. Ensure good ventilation of the chassis (working temperature 0~60 ° C).

Cable management: Avoid excessive bending or entanglement of USB cables to reduce signal attenuation and mechanical damage.