Advanced triggering and multi card synchronization of ADLINK PCIe-CPL64V image acquisition card

DelayBufferCount/Overflow: Each trigger delay module has an internal buffer that records the number of trigger events that have not yet been output. If the overflow exceeds 255, it indicates that the triggering frequency is too high or the delay setting is too long, and the parameters need to be adjusted.

EventCount/DropCount: Each trigger source and output channel has independent event and dropout counts. A non-zero DropCount indicates that the trigger signal has been lost, and it is necessary to check the quality of the front-end signal or increase the buffer.

Camera Link Configuration: Real time display of the currently detected configuration (Base/Medicine/Full/Error), corresponding to the status of LED7.

By utilizing these states, engineers can quickly diagnose bottlenecks in the trigger chain without the need for an oscilloscope, significantly reducing the debugging cycle.

Common Problems and Troubleshooting Guide

1. Collecting images with blurred screens or incorrect lines

Check if TapPlacement matches the actual output of the camera (such as double tap odd order, starting center, etc.).

Verify if SensorWidth meets the alignment requirements (see warning in section 5.1.2).

Check if the LVAL/DVAL/FVAL polarity settings match the camera timing (can be adjusted through LVALPolarity, DVALPolarity).

2. Trigger no response

Confirm that the trigger source is correctly connected (DI/encoder) and the voltage level meets the specifications (DI high level 3-24V, low level<0.8V).

Check if the source of the corresponding output channel in TriggerOutputTrigSrc is configured correctly.

Confirm that AVS_SrameGrabberStartAcquisition has been called, and the triggering function only takes effect after the collection starts.

Observe whether the corresponding event count (such as DI0EventCount) increases. If not, check the front-end signal and debounce settings.

3. Encoder direction is opposite

Swap the wiring between encoder A+and A - or B+and B -, or select CW/CCW reverse through Encoder Input. Mode.

4. The image is not synchronized after multi card synchronization

Check the synchronization cable connection sequence of all cards to ensure that the main card output is connected to the first slave card input and connected in series to subsequent slave cards.

Confirm that the MultiCardSync.Mode configuration for all cards is correct and that the trigger source signal for the main card is stable (if using the same external sensor).

Measure whether the synchronization signal on the main card CN4 is output (requires an oscilloscope). If not, check the main card configuration and trigger source.

5. Firmware update failed

Use the Firmware Update tool provided by ADLINK, select the correct. bin file, and after the update is complete, perform a cold start (completely power off and then power on), otherwise the new firmware will not take effect.

Key points of development environment and API calling

PCIe-CPL64V adopts a brand new AVS SDK (not compatible with the old version CPL64), supports Windows 10/11 64 bit,. NET Framework 4.8 or above, and VC++Redistributable 2015 or above. The programming process is as follows:

Call AVS_LetDeviceCount to enumerate devices.

AVSOpenDevice opens the specified card number and channel.

AVS_CameraLinkImportCamFile loads CAM files.

If a callback is used, the AVS-FrameGrabberSetcallback will register the frame ready callback; If using blocking, loop call AVS_SrameGrabberGetFrame.

AVS_SrameGrabberStartAcquisition starts the acquisition process (triggering logic takes effect at this time).

Process the image in the callback or main loop and return the buffer through AVS-FrameGrabberQueueBuffer.

Stop collecting and turn off the device.

Special note: GetFrame and callback modes cannot be mixed; Dynamic modification of trigger parameters must be performed after stopping the collection process; AVS_FrameGrabberSetBufferCount can adjust the number of buffers before startup (default: 4, maximum: 100). Increasing the buffer will help smooth burst frame traffic.

Selection and application suggestions

For a single Full configuration camera (80 bit, 85MHz), PCIe-CPL64V is an ideal choice with ample bandwidth margin.

If four Base cameras need to be synchronized, it can be achieved by combining four cards with multiple cards for synchronization. Each card controls one camera, which is suitable for parallel detection of multiple workstations.

The encoder trigger mode is suitable for equidistant acquisition in continuous motion, such as defect detection on the surface of a coil. Comparing Count and Interval need to be calculated to ensure uniform line spacing.

The anti-interference ability (± 7V common mode range) of isolating I/O and encoder inputs enables it to adapt to the motor frequency converter environment, but it is still recommended to use shielded twisted pair and single ended grounding.