CANedge1: 2x CAN Bus Data Logger (SD + RTC)

You can optionally select a CANedge that includes GNSS/IMU.

Effectively, this lets you record GNSS/IMU data in timesync with your 2 x CAN/LIN data.

The GNSS/IMU signals include position, speed, distance travelled, attitude (roll, pitch, heading), altitude, acceleration and more. This data is added as a 'separate CAN channel' internally in the data log files - and you can configure the inclusion/frequency of each message. For details, see the CANedge options incl. GNSS/IMU.

Note: The internal GNSS/IMU produces roughly the same end result as connecting a CANmod.gps to the 2nd port of the CANedge. However, by internalizing the GNSS/IMU inside the CANedge, the overall size and price is drastically reduced - while enabling a simpler installation and configuration. It also frees up a CAN channel on the CANedge.

The CANedge is the 2nd generation of the CLX000. We generally recommend to use the CANedge for data logging use cases, while the CLX000 is mainly recommended if you need to stream data via USB.

Key improvements in the CANedge vs. CLX000 include:

Mechanical

• Extractable SD: The SD can be extracted to transfer data at 80 MB/s (vs 0.5 MB/s for the CLX000 via USB)
• Industrial SD: The CANedge uses an industrial SD card, improving performance, life time, temperature range & more
• Channels: 2 x CAN/LIN channels, enabling logging of 2 x CAN + 2 x LIN in parallel
• Aluminum enclosure: New enclosure is as compact as the CLX000, but far more robust and offers flanges for mounting
• Power out: Power external modules via the 2nd port, e.g. a GPS-to-CAN or Temperature-to-CAN module
• Rugged protection: The CANedge comes with a stronger protection spec against e.g. voltage spikes

Log files & software/API

• MDF4 log files: Popular binary MDF4 format - more compact than CSV, faster to process, supported by many CAN tools
• Configuration: Open source configuration editor can be used either online/offline via your browser
• JSON Schema: Config files are based on the standardized JSON Schema concept, supported by many open source tools
• Converters: Open source light-weight converters enable drag & drop/CLI conversion of MDF4 into e.g. *.csv and *.asc
• asammdf GUI: Enables user-friendly MDF4 log file editing, DBC-conversion (incl. OBD2/J1939), graphical plots & more
• Python API: Easily process your data at scale and automate the creation of e.g. reports/databases/dashboards
• MATLAB: Log files integrate natively with MATLAB's Vehicle Network Toolbox
• Dashboards: Easily visualize your data in free customizable Grafana dashboards

Data logging

• Lossless: The CANedge can log full bus loads with zero message loss (the CLX000 is limited to ~800-1000 frames/sec )
• Compression: Optional compression lets you reduce file size by up to 80% vs. the CLX000
• Encryption: Optional encryption lets you encrypt log files on the SD card for added security
• Advanced configuration: More advanced filters & transmit lists (e.g. up to 128 filters vs. 8 on CLX000)
• Precision: 20x higher RTC resolution (50 micro seconds) - with advanced RTC sync options
• Boot time: Much faster boot time vs the CLX000 (~1 sec vs. ~10 sec)
• CAN FD: The CANedge supports CAN FD (Flexible Data-Rate), making it future proof
• Triggers: Control when to start/stop logging/transmission based on custom CAN signal thresholds
• Error frames: The CANedge supports CAN/LIN error frame logging
• LIN slave/master: The CANedge can both serve as a LIN slave or LIN master (publisher)

GNSS/IMU + connectivity

• GNSS/IMU: The CANedge supports optional built-in GNSS/IMU functionality
• WiFi: The CANedge2 supports WiFi data transfer to your own cloud/self-hosted server (incl. OTA updates)
• 4G LTE: The CANedge3 supports 4G LTE data transfer to your own cloud/self-hosted server (incl. OTA updates)

The CANedge1 and CANedge2 are 100% identical, except for the WiFi functionality in the CANedge2. Similarly, the CANedge1 and CANedge3 are identical except for the 4G LTE functionality of the CANedge3. Note also that the CANedge1/CANedge2 supports optional GNSS/IMU, while this is by default part of the CANedge3.

If you only need to collect your CAN data rarely and the device is physically accessible with ease, then the CANedge1 is typically enough. However, if you need to collect your data frequently and ideally remotely, the CANedge2/CANedge3 will quickly be worthwhile. In particular, if you need to collect data across a fleet of vehicles or machines, the CANedge2/CANedge3 are far more practical and cost effective.

A WiFi/LTE connected CANedge has the added advantage that you can fully automate your data collection, as well as your data processing workflow. For example, you can set up automated Python API scripts to modify your data, DBC decode it - and e.g. setup telematics dashboards. The CANedge2 is also easier to manage in the field as you can monitor the status via the CANcloud telematics platform and e.g. perform over-the-air configuration and firmware updates.

For use cases where a WiFi network is available, we recommend the CANedge2. If you need to upload data via 4G LTE (cellular), we recommend the CANedge3.

The size of a raw MF4 log files depends on the application - and how much data you wish to record.

The below overview shows a typical example for a heavy duty truck (J1939 data), exhibiting 700 frames/second. As evident, if you record everything, an 8 GB SD card will let you record data 24/7 for ~7 days - while the 32 GB would enable ~26 days.

However, the CANedge supports powerful options for optimizing the log file size. As a result, a more realistic scenario is shown below in which e.g. a 32 GB SD lets you record 800+ days.

Below we list some of the key features that let you optimize your logging:

• Compression: Enable compression to reduce the data size by 50-80%
• Filters: Specify which CAN IDs to record/ignore (via ranges and masks)
• Prescalers: Instead of recording frames at their 'raw' frequencies, you can customize the frequency by CAN ID
• Control signal: Specify when to start/stop logging based on specific CAN signal thresholds

If the SD is full, cyclic logging lets the CANedge CAN logger continue recording data by deleting the oldest log files first.

The CANedge1 CAN logger is superior when it comes to logging data to the SD card vs. the CL2000. However, the CANedge1 does not support real-time streaming via USB. For this type of use case, we would recommend e.g. the CL2000.

For an overall intro to CAN logging with the CANedge, see our 45 min webinar.

In the below, we outline the basics of how you can start logging raw CAN data:

• Connect the CAN logger to your CAN bus (optionally using our adapter cables)
• The device powers on, detects the bit rate and starts logging raw data to the SD card
• Disconnect the device, extract the SD and insert it into your PC
• Open the raw log files in e.g. the asammdf GUI/API for DBC decoding and visualization

For more details on getting started, see the CANedge Intro and Docs - or contact us if any questions.

The CANedge is designed to offer the best value/cost ratio in the 'pro specs' CAN/LIN logger market.

In particular, below factors differentiate it vs. similar devices:

• Pro specs: The CANedge offers specs on par with the best loggers available
• Compact: The CANedge is 50-80% smaller vs. similar devices
• Low cost: The CANedge is 50-80% lower cost vs. similar devices
• Easy-to-use: The device can be used out-the-box with no configuration
• FOSS: All software/API tools are 100% free and open source
• Interoperable: Open standards and tools enable integration into any system - with no lock-in
• Free support: We offer free best-in-class technical support

Don't take our word for it, though - check out our 50+ case studies from companies like VW, Siemens, Bosch, Cummins and more.

The above makes the device an excellent choice for e.g. automotive/industrial OEM engineers.

The CANedge1 CAN bus analyzer 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, electric vehicles, ...) - as well as various production machinery, EV batteries/BMS and more. Most planes and boats also use CAN bus. In terms of protocols, this encompasses e.g. SAE J1939, CANopen, NMEA 2000, FMS, OBD2 and more.

For the specific case of OBD2 vehicle data, the CANedge1 can transmit up to 64 custom CAN messages periodically, which means it can be used as an OBD2 data logger. Note 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 CANedge1 is of course only able to record the supported data.

For use cases where you need to add GNSS/IMU we recommend selecting a CANedge with built-in GNSS/IMU.

For other sensor inputs (temperature, analog, digital, pulse, ...), you can connect external sensor-to-CAN modules to the device. In particular, our CANmod sensor-to-CAN modules can be easily combined with the CANedge.

Specifically, the CANedge 2nd port can supply 5V DC to external modules - enabling easy installation. Data from the connected sensor-to-CAN modules is recorded in the CANedge log files along with data from the other CAN/LIN channels.

Consider e.g. our CANmod.temp temperature-to-CAN module or CANmod.input analog/digital/pulse to CAN module.

The CANedge requires the use of a specific industrial SD card model in order to guarantee the performance and power safety. You can select an 8 or 32 GB SD card as an option during check-out (or as a separate purchase).

You should not use 3rd party SD cards as these may result in data corruption and other forms of non-functional behavior.