The plug & play CL2000 CAN logger records CAN bus data to an 8 GB SD card and timestamps it with a real-time clock.
This CAN logger is ideal for vehicle fleet management (trucks, buses, harvesters, cars, …), prototype field testing, diagnostics or reverse engineering.
Configure in 2 min. Power via CAN connector. Auto-detect bit-rate
Log CAN data to 8-32GB SD card for months - no pc needed
Date & timestamp your data - vital for post analysis
Easily stream raw & DBC converted CAN data in Wireshark
Fits the palm of your hand (6.6 x 4.3 x 2.4 CM) & weighs <50g
The value/cost of the CL2000 is unbeatable
|Functionality||Data logger and real-time CAN interface|
|LEDs||Logger status via three externally visible LEDs|
|Firmware||Supports free firmware updates for adding features|
|Software||Free CANvas software for configuration, streaming & conversion|
|Safety||CE, FCC, IC, RoHS certified|
|Standard||Compliant with physical layer standard ISO 11898-2|
|Identifiers||Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID)|
|Bit Rate||Bit rates up to 1 Mbps (manually configured or automatically detected)|
|Protocol Support||Protocol independent (i.e. able to log J1939, CANopen, OBD2, ...)|
|Filters||Advanced message filtering on four configurable channels|
|Silent Mode||Yes (does not affect CAN-bus transmission)|
|Fail-Safes||The device does not terminate the CAN-bus internally|
|SD Card||Replaceable 8 GB SD card (optional 32 GB)|
|Real-Time Clock||Yes (CAN messages are time-stamped with 1ms resolution)|
|Control Signal||Logging state (enabled/disabled) can be changed run-time using a CAN-bus control message|
|Heartbeat Signal||Supports heartbeat signal to periodically indicate logger status|
|Cyclic Logging||Supports cyclic logging mode (oldest log file is deleted when file system is full)|
|Down Sampling||CAN ID specific message down-sampling to reduce frequency of logged messages|
|Transmit||Transmit up to 20 customized CAN bus messages (e.g. for OBD2 queries)|
|File System||Standard FAT file system|
|Power via CAN-bus||Power can be supplied from the CAN connector (log/stream) or via USB (data extraction)|
|Via CAN bus||Power supplied by the CAN bus (+7.0V to +36V DC)|
|Protection||Reverse voltage protection on CAN-bus supply|
|Transient voltage pulse protection on CAN-bus supply|
|Power via USB||Power supplied by USB (+5.0V DC)|
|Consumption||The logger's power consumption is approximately 1 W|
|Enclosure||Robust, small enclosure|
|Dimensions||66.7 x 42.7 x 23.5 mm (L x W x H)|
|Connector||Standard D-sub 9 (DB9) connector (OBD2, J1939, "generic" adaptor optional)|
|USB||Standard mini USB connector for extracting data & streaming (cable not included)|
|Temperature||Operating temperature: -20degC to +65degC|
|Real-Time Clock||Built-in real-time-clock with calendar and battery backup|
|Date and time information are added to log files|
|Battery backup with more than two years of battery capacity|
|IP Rating||IP Rating 40|
The CL2000 is ideal for medium to long-term standalone data logging and ad hoc data streaming.
Below we outline some of the typical applications for the CL2000 - also, check our CASES section for real customer use cases.
Need to develop, debug or optimize your vehicles?
The CL2000 provides OEM teams with an easy tool for collecting vehicle data. In particular, the CL2000 is useful for late-stage development. Here, the compact standalone functionality means that it can be added to large fleets of prototype vehicles for long-duration logging. After a few weeks or months, the data can be collected and analyzed for optimization and diagnosis.
Use case example: Tribine - Logging a Full Harvest Season of Data
Need to identify a an issue that only occurs e.g. every 3 months?
A non-standalone solution is simply not feasible. However, with the CL2000 you can log months of data from one or multiple vehicles or machines at low cost. With cyclical logging, the most recent data is prioritized if no space is left. Once the rare behavior is observed, you'll have all the data you need to troubleshoot it.
Use case example: Xcerra - Diagnosing Rare Machine Errors
Need to record and register vehicle data for compliance?
In some scenarios, you'll need to collect compliance or insurance related data - e.g. emissions (e.g. NOx, CO, HC, PM, ...). You may need to legally log this data from your fleet - even if you do not intend to use it actively. In such a setup, the CL2000 is the optimal solution: With an 8-32 GB SD, cyclical logging and RTC you can log all the CAN, OBD2, FMS or J1939 data you need - and collect it on a case-by-case basis.
Reverse engineering proprietary data
Want to reverse engineer proprietary data parameters?
If you're not the vehicle OEM, you may need to reverse engineer certain proprietary CAN data. Maybe you want to hack your car - or maybe you need to add custom functionality in a J1939 test setup. Through data logging, Wireshark streaming and analysis it is possible to identify what CAN IDs relate to what parameters - and how to offset/scale the data. Learn more in our CAN sniffer intro.