configure in 2 mins, then "connect & forget" (<1W power usage)
log CAN data to 8-32GB SD card for months - no pc needed
configure your CL1000, stream data & convert log files
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
For a quick CLX000 intro, check out our 90s video below:
About the CL1000 CAN Logger
The CL1000 is an easy-to-use, low cost CAN bus data logger (and CAN interface) with an 8-32 GB SD card.
What can you use it for? You can use it to record CAN bus data from practically any vehicle (cars, trucks, tractors, …) and many other CAN applications (machinery, robotics, EV batteries, ...). This includes SAE J1939, OBD2 and CANopen applications.
To get started, simply connect the CL1000 to your application. The device automatically starts recording data to the SD card in a simple *.CSV format. This data can then be extracted via USB for post processing.
The CL1000 is compact and stand-alone (no PC needed). Further, you can use our free software CANvas to configure the CL1000 and convert raw data via *.DBC files.
You can also work directly with the CONFIG.INI and log file formats.
Feel free to download a sample of J1939 data from the CL2000 and a J1939 *.DBC sample. Note that the CL1000's data format is similar, except that the real-time clock & date timestamp is replaced by a milisecond index that counts from the beginning of the log session. You can load both in CANvas to try out the data conversion.
When Do You Need the CL1000 CAN Logger?
The CL1000 is suited for short-duration standalone data logging and ad hoc data streaming.
Below we outline some of the typical applications for the CL1000 - also, check our CASES section for real customer use cases.
Should you upgrade? If you aim to log data over longer periods, we strongly recommend the CL2000 with date & real-time clock timestamps. Further, if you need to get data frequently or from many loggers, we suggest that you check out our CL3000 with WiFi.
Reverse Engineering Proprietary Data
Want to reverse engineer proprietary data parameters?
If you're not the vehicle manufacturer, you may need to reverse engineer certain proprietary CAN data. Maybe you simply wish to hack your car - or maybe you need to add custom functionality in a J1939 test setup. By using a combination of data logging and Wireshark streaming, it's possible to identify what CAN IDs relate to what parameters - as well as how to offset and scale the data. Note, however, that this is an area that requires some expertise and skill.
Use case example: DDR - Reverse Engineering Proprietary J1939 Data
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 CL1000 is a great low cost solution: With an 8-32 GB SD and cyclical logging you can log all the CAN, OBD2, FMS or J1939 data you need - and collect it on a case-by-case basis.
Vehicle Development & Field Testing
Need to develop, debug or optimize your vehicles?
The CL1000 provides OEM teams with a powerful tool for collecting vehicle data. In particular, the CL1000 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. Similarly, the CL1000 is great for gathering user ride profiles and the low cost ensures you can data from far more vehicles than with other CAN loggers.
Use case example: Tribine - Logging a Full Harvest Season of Data
Rare Issue Identification
Need to identify a an issue that only occurs e.g. every 3 months?
A non-standalone solution is simply not feasible for rare issue identification. However, with the CL1000 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
Real-Time Streaming in Wireshark
The CLX000 series supports real-time streaming via USB:
Raw data is streamed live to the PC in a machine-friendly format - and can be viewed easily in Wireshark.
Below guides detail some of the popular use cases:
Streaming OBD2 Data: Analyse and plot human-readable OBD2 data in real-time - ideal for analyzing cars
Reverse Engineering: Use our free plugin streaming tools to aid in reverse engineering raw CAN bus data
Streaming *.DBC Converted Data: Load your *.DBC file and stream human-readable data in real-time
Free CANvas Software
With the CL1000 you also get our free CANvas software. This lets you easily configure your CL1000, stream data and convert logged data.
In particular, CANvas gives you multiple powerful conversion features:
- Convert log files with *.DBC & OBD2 support
- Merge log files - or append to an existing output file
- Re-format log files to Vector's ASCII format or PEAK's PCAN format
- Customize output format - creating e.g. Excel pivot ready formats
For additional feature details see the end of this section.
- A 2-in-1 CAN analyzer: CAN logger + real-time CAN interface via USB
- Huge capacity: 8 GB SD card included for stand-alone CAN bus recording (optional 32 GB)
Simple To Use
- Plug & play: Log data out of the box with bit-rate auto-detection support
- High Speed CAN: Log any ISO-11898-2 data (e.g. J1939, CANopen, OBD2, …)
- Regular & extended: Supports 11-bit (CAN 2.0A) and 29-bit (CAN 2.0B) identifiers
- Compact: Small robust enclosure the size of a matchbox
- Easily power: Power via USB or CAN bus (via DB9 or a J1939 or OBD2 adaptor)
- Low power usage: ~1 watt in default logging mode - no risk of battery drainage
- LEDs: Logger status easily visible via 3 external LEDs
Free Powerful Software
- Free CANvas software: Easy configuration, streaming & data conversion (*.DBC support)
- Wireshark plugin: Powerful Wireshark plugin for wired live-streaming (incl. *.DBC support)
- Conversion options: Process log files with re-structuring, merging & downsampling
- Re-format: Option to convert raw log files to PEAK or Vector CANalyzer formats
- Advanced configurations: Filters, data transmitting, cyclic logging & more
- High quality: Designed in Denmark; Made in USA (CE, FCC, IC, RoHS certified)
- Warranty: 2-year warranty as per Danish law
- Support: Free, high quality and fast technical support from our Danish team
- Updates: Free firmware/software upgrades
Check out our Tech Specs, FAQ or Reviews above - or go back to the top to buy!
For more detailed information, please refer to the product manual.
The logger firmware is regularly updated with new features & improvements. For latest updates cf. the changelog.
||Data logger and real-time CAN interface
||Logger status via three externally visible LEDs
||Supports free firmware updates for adding features
||Free CANvas software for configuration, streaming & conversion
||CE, FCC, IC, RoHS certified
||Compliant with physical layer standard ISO 11898-2
||Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID)
||Bit rates up to 1 Mbps (manually configured or automatically detected)
||Protocol independent (i.e. able to log J1939, CANopen, OBD2, ...)
||Advanced message filtering on four configurable channels
||Yes (does not affect CAN-bus transmission)
||The device does not terminate the CAN-bus internally
||Replaceable 8 GB SD card (optional 32 GB)
||No (see instead the CL2000 or CL3000)
||Logging state (enabled/disabled) can be changed run-time using a CAN-bus control message
||Supports heartbeat signal to periodically indicate logger status
||Supports cyclic logging mode (oldest log file is deleted when file system is full)
||CAN ID specific message down-sampling to reduce frequency of logged messages
||Transmit up to 20 customized CAN bus messages (e.g. for OBD2 queries)
||Standard FAT file system
|Power via CAN-bus
||Power can be supplied from CAN-bus or from the USB
|Via CAN bus
||Power supplied by the CAN bus (+7.0V to +36V DC)
||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)
||The logger's power consumption is approximately 1 W
||Robust, small enclosure
||66.7 x 42.7 x 23.5 mm (L x W x H)
||Standard D-sub 9 (DB9) connector (OBD2, J1939, "generic" adaptor optional)
||Operating temperature: -20degC to +80degC
||IP Rating 30
The 8GB SD card provides an enormeous capacity. While space consumption varies depending on your application, 8 GB will provide many weeks worth of continuously logged data. As most vehicles are not running continuously, this typically corresponds to months of data.
If you need to log data for very long durations, you can either upgrade to a 32 GB SD card - or pre-sample your data to a lower frequency (e.g. logging only every 10th or 100th message). Finally, you can add filtering to restrict your logging to certain CAN IDs or J1939 PGNs. For more details on this, see the product manual.
The CLX000 series can record data from any high speed CAN bus application (ISO 11898-2). In practice, this includes raw data from almost all vehicles (cars, trucks, tractors, forklifts, buses, motorcycles, ...) - as well as various production machinery, EV batteries and more. Most planes and boats also use CAN bus. In terms of protocols, this encompasses e.g. J1939, CANopen, NMEA, FMS, OBD2 and more.
For the specific case of OBD2, the CLX000 can transmit up to 20 custom CAN messages periodically, which means it can be used as an OBD2 data logger. Note, however, that you need to verify that your car uses CAN as basis for the OBD2 communication (this is the case for all US cars produced after 2008 e.g.). Also, note that all cars differ in the amount of OBD2 parameters they support - and the CLX000 is of course only able to record the supported data.
The CLX000 series can be powered via the CAN bus. This means that you simply connnect the device via the DB9 connector to power it. In cars, you'll typically need a DB9-OBD2 adaptor, while for e.g. trucks you may use a DB9-J1939 adaptor.
Once connected, the CLX000 will start recording data - and due to the extremely low power consumption, you can simply leave it in your vehicle. In most vehicles, the CLX000 will power off when the vehicle is powered off. If this is not the case, the power draw of the logger itself is still not an issue in regards to battery drain.
However, if you're requesting e.g. OBD2 data in this scenario, the polling may wake up the car's ECUs. In this case, you should avoid leaving the CLX000 powered on in an unused car for more than a few days.
Note that the CLX000 can also be powered via USB when it enters 'mass storage device mode' - this lets you configure the logger on your PC without a separate power source.
At CSS Electronics we are truly passionate about delivering great products - and fast, quality service!
BUSINESSES USE THE CLX000
"We loved it! And I can put 5 of the CLX000 CAN loggers on our test fleet for the price of one Memorator logger"
Bryan Cady, Battery Specialist at Zero Motorcycles, Inc
"We used the CL2000 for months now - despite rough environments we found the device sturdy and reliable"
Caspar van Zon, Senior Software Developer at Kverneland Group (Netherlands)
"The CL2000 is very easy to setup, the software is intuitive and the *.DBC feature is nice - highly recommend it!"
Curtis Steele, Manager, Product Development at ProAll
"Never used a tool like this before
- the support was exceptional!”
Jason Le, Technical Specialist at SunSource
"The CLX000 worked perfectly for reverse engineering proprietary J1939 data"
Daan de Roos, owner of DDR Engineering & Marine Projects