Capture Module

Capture Modules use an internal buffer to store incoming frames. Frames may be lost only if the data logger startup is delayed long enough to fill the internal buffer, or if the logging system cannot keep up with the required logging speed. In normal operation, the logging bandwidth is higher than the maximum input bandwidth, so no frames should be lost.

CM CAN and CM LIN can log frames approximately 100 ms after power-up. CM 1000High Evo requires approximately 250 ms until the network link is established.

Power consumption depends on active ports, SFP modules, and operating temperature.CM 1000 High Evo can consume up to 20 W in the worst-case configuration. All Capture Modules support sleep mode, with current consumption typically below 500µA.

Advanced filtering can match the incoming interface and the content of the captured frame. CM 1000 High Evo can inspect the first 78 bytes of an Ethernet frame, enabling filtering on protocol headers, identifiers, MAC addresses, IP addresses, and UDP/TCP port numbers.

Yes. The devices provide a remote API to configure and monitor the modules withoutusing the web UI. The API exposes all parameters and status information available through the web interface.

CAN and LIN Capture Modules support time-aware frame injection. The application sends the frame data and timestamp, and the Capture Module transmits the frame whenthe internal timestamp counter reaches the specified value.

For CAN and LIN, the Capture Module operates passively. For Ethernet, it is inserted between two communicating devices. CM 1000 High Evo has constant latency of approximately 6 µs, which is fixed, predictable, and can be compensated by PTP.

TECMP and ASAM CMP provide built-in diagnostic and monitoring capabilities.Capture Modules can transmit status messages and generate event notifications such as link up/down events and loss of time synchronization.