CANedge1: 2x CAN data logger (SD + RTC + GPS/IMU)
Functional overview：
The CANedge1 is a high performance 2xCAN data logger supporting CAN FD and LIN channels with built-in GNSS and 3D IMU for vehicle testing and diagnostics. The device supports plug-and-play, automatic bit rate detection and silent mode, records 8-32 GB of SD card data, and features 50 µs accuracy RTC and highly accurate GNSS/IMU data fusion. Free open-source tools support data conversion and analysis for a wide range of application scenarios, making it a cost-effective professional solution.
Description
Professional Specification CAN Recorder - halves the cost
CANedge1 combines innovative design, cutting-edge components - and incredibly low cost.
- 8-32 GB industrial SD card withdrawable (= months of data)
- Popular binary MDF4 journal file format
- Advanced Message Filtering and Transmission Features
- CAN ID and data byte based start/stop logging triggers
- Silent Mode, Bit Rate Auto Detection, Cycle Recording
- Data compression and encryption (e.g. GDPR, CCPA)
- Supports CAN/LIN error frame recording.
- Fast start-up time. Safe disconnection during use (power safety)
- Add CANmod, e.g. to record 5 x CAN or temperature/analog data.
GPS and 3D IMU - enriching your data
CANedge1 is equipped with advanced GNSS/IMU functionality - ideal for automotive/marine use cases.
- Add more than 40 GNSS/IMU signals to your 2 x CAN/LIN data.
- Full GNSS support (GPS, Galileo, Beidou, GLONASS)
- Built-in gyroscope (roll, pitch, yaw) and accelerometer (X, Y, Z)
- High accuracy through sensor fusion - even in GNSS-opposed areas
- Signal coding is “internal” CAN frame (separate channel)
- Configurable message inclusion/frequency (up to 5 Hz)
- Includes DBC files that can be easily decoded into a human-readable form
- Optionally synchronize CANedge RTC with precise GNSS time
- Flexible deployment via external GNSS antennas
Open Source Software/API
CANedge1 uses open formats (MDF4 data, JSON settings, S3 server) - all software/APIs are 100% free and open source
This software toolkit provides the following features:
• Editors: Easily modify device configuration (online/offline)
• Converter: Convert data to various formats (e.g. vector ASC, PEAK TRC, CSV, etc.)
• asammdf GUI: Supports DBC conversion, data mapping and export.
• Python API: Automated Data Processing and Systems Integration
• Dashboard: Data visualization through customized browser dashboards
Specification
| Basic Description | |
|---|---|
| functional | Standalone CAN bus data logger with SD card and 2xCAN/LIN channels (including CAN FD) and GNSS/IMU |
| Firmware | Supports free firmware updates to add features |
| configure | Configuration files based on the popular open source JSON schema concepts |
| Software | Free open source editor tool for easy device configuration (offline/online versions available). Free open source asammdf software and API for editing, DBC conversion and drawing MDF4 data. Free Open Source MF4 Converter - Drag and drop journal files to convert to CSV, ASC, TRC and more. Free open source Python API - e.g. for automated data processing, reporting or integration. Free open source remote information processing dashboard for visualizing DBC decoded data in a browser. |
| surety | CE-RED, FCC, IC, KC and RoHS certifications (see documentation). Voltage transient (emission/resistance) test by TUV SUD, ISO 7637-2:2011 (see document). |
| Warranty Policy | 1 year warranty |
| support sth. | Free, fast, high-quality support |
| originate | Denmark |
| CAN bus | |
|---|---|
| channel | 2 CAN channels (including CAN FD support) |
| Standard | ISO 11898: compliant with CAN (up to 1 Mbit/s) and ISO and Bosch CAN FD (up to 5 Mbit/s payload rate) |
| agree | Recording of raw data from CAN-based protocols (J1939/FMS, CANopen, NMEA 2000, OBD2, CAN FD, UDS, etc.) |
| identifier | CAN specification 2.0A (11-bit ID) and 2.0B (29-bit ID) compliant |
| Bit Rate Auto Detection | Bit rate can be detected automatically or set manually. |
| retransmission | Configurable retransmission of lost arbitration or error-disturbed frames. |
| Transceiver Protection | ±16 kV HBM ESD, ±15 kV IEC ESD, ±70 V bus fault, short circuit. Common mode input voltage: ±30V. TXD Display Timeout (prevents network blocking in case of failure). |
| LIN Bus | |
|---|---|
| channel | 2 LIN channels |
| Publisher/Subscriber | Each LIN channel can be configured as a LIN subscriber/publisher to support LIN data transfer |
| Customized Length | Supports customized frame length |
| Standard | LIN 2.0 compliant up to 20 Kbit/s (classic and enhanced checksum formats supported) |
| Transceiver Protection | ±8 kV HBM ESD, ±1.5 kV CDM, ±58 V bus fault. TXD Display Timeout (prevents network blocking in case of failure). |
| Data Logging | |
|---|---|
| SD card | Includes 8 GB of extractable Class 10 industrial micro SD (SDHC) (optional 32GB) - reads at 80 MB/s I |
| Parallel CAN/LIN | Simultaneous data recording for up to 2 CAN channels + 2 LIN channels |
| Real Time Clock | Yes - CAN frames are date and time stamped with 50 microsecond resolution (battery backed). The RTC can be set to match the local time zone (default: UTC). The RTC can be automatically synchronized via CAN messages (e.g., from internal GNSS time stamps). |
| Journal File Format | Record data in industry standard binary MF4 (easy conversion to CSV, ASC, pandas, MATLAB, etc.) |
| Data Compression | Configurable embedded log file compression (size reduction of about 50-80%) |
| Mute Mode | Configurable Silent Mode: Restricted (Confirmation Only) or Monitor (Zero Transmission) |
| filters | 128/64 regular/extended ID filters per channel (range, mask, accept, reject, prescaling) |
| Preshrinking | Pre-scored CAN frames, e.g. recorded by time (every X milliseconds) or by data (e.g. if byte X or Y changes) |
| Send | List of CAN frames transferred per channel (single/regular) - e.g. for OBD2 requests |
| CAN error frame | Supports logging CAN error frames (bit fill, form, CRC, bit, acknowledge) |
| LIN Error Frame | Supports logging of LIN error frames (checksum, receive, synchronize, transmit) |
| Remote Frame (RTR) | Supports remote CAN frame (RTR) recording/transmission |
| Cyclic Record | Optional cyclic logging mode (the oldest log file will be deleted when the SD card is full) |
| Advanced Trigger | Control signals allow you to start/stop recording based on customized CAN ID and data thresholds |
| CAN heartbeat | Optionally transmits heartbeat CAN frames with device status, used storage space, and RTC time. |
| file splitting | Configurable log file split size (by size: 1-512 MB and/or by time period: 0-86400 seconds) |
| Power Safety | 100% Power safety data logging - no file corruption when disconnected |
| Unique Device ID | Each device has a globally unique ID, ensuring that log files are named uniquely |
| Data Encryption | Log files can be encrypted at rest on the SD card for security/GDPR/CCPA purposes. |
| GNSS and 3D IMU | |
|---|---|
| Module | Professional u-blox NEO-M9V sensor module (92 channels) with built-in gyroscope and accelerometer |
| Global Navigation Satellite System | Supports GPS (US), Galileo (Europe), BeiDou (China), GLONASS (Russia) combinations |
| Sensor Fusion (UDR) | Enhanced Positional Accuracy via Sensor Fusion (UDR) with GNSS and 3D IMU [Automotive Only] Up to 3 times more accurate than GNSS-only receivers Expand and improve GNSS positioning in hostile areas such as urban environments, tunnels, etc. |
| Accuracy | Position: 2.0 m CEP (Circular Error Possible) Heading: 0.3 degrees | Pitch: 0.4 degrees | Roll: 0.6 degrees (68% at 30 m/s) Speed: 0.08 m/s |
| sensitivity | Tracking/Navigation: 160 dBm | Cold Start: 148 dBm |
| Get | Cold start: 25 seconds |
| Global Navigation Satellite System Antenna | GNSS-based data needs (not applicable to IMU) |
| Data parameters | CAN coding: GNSS/IMU data coded as "CAN messages" in CANedge log files (on separate channels) Configuration: GNSS/IMU messages can be filtered/pre-scaled to enable customized message inclusion and frequency; recorded only when valid (optional) Signal: Several new GNSS/IMU signals have been added to this module (see documentation or DBC file for details), including: - GNSS position: Latitude and longitude information [5 Hz] - GNSS time: based on precise GNSS epoch timestamps [5 Hz]. - GNSS status: Fixed type (NO/UDR/2D/3D/GNSS+UDR) with satellite count [5 Hz]. - GNSS speed: Travel speed (m/s, km/h) [5 Hz] - GNSS Altitude: Altitude (meters) [5 Hz] - Attitude/Direction: Roll, Pitch, Heading [Vehicle Only] [5 Hz] - GNSS odometer: Travel distance (after power-up) [5 Hz] - 3D IMU: Accelerometer-based X, Y, Z acceleration [5 Hz] - Geofences: status of configured geofences [5 Hz] |
| Electricity | |
|---|---|
| Input Power | +7V to +32V DC via Channel 1 DB9 (e.g. via CAN connector power pins) |
| Power Consumption | Very low (~1 W) - no risk of battery exhaustion |
| Protection | Reverse voltage protection for the CAN bus power supply. Protection from transient voltage events on the power line. |
| mechanical | |
|---|---|
| Casing and Weight | Compact Aluminum Housing: 75 x 47 x 20 mm (W x L x H without flange) 100 grams |
| skyline | Includes GPS antenna |
| France | Flange with 4 x M3 screw holes (head diameter < 6 mm) - see also CANedge “Installation kit” |
| Connectors | 2 standard D-sub 9 (DB9) connectors (optional OBD2/J1939/...) Adapter) |
| Pin assignment | For DB9 connector pinout, please refer to the product manual. |
| Configurable power outputs | Channel 2 can be configured to supply 5V to an external module (e.g., CANmod sensor to CAN module) |
| LED | Indicates recorder status via 4 external LEDs: Power, CH1, CH2, Memory |
| Temperature | Operating temperature (parts): -25°C to +70°C |
| Protection Level | Defense Level 40 |
Frequently Asked Questions
Yes, this version of CANedge includes the GNSS/IMU module. If you install a device with an external GNSS antenna, you can choose to synchronize the recording of GNSS/IMU data with 2 x CAN/LIN data.
GNSS/IMU messages are logged as if the data were broadcast over a CAN bus network recorded by CANedge. To separate it from the CAN/LIN channel, the data is stored in a log file under a separate "internal" pseudo-channel.
Previously, adding a GNSS/IMU to the CANedge required the addition of a GPS-to-CAN module (such as the CANmod.gpsThe CANedge is connected to the CANedge (e.g. on the second port).
The new internal GNSS/IMU has many advantages:
- It's more compact - and easier to install!
- Significant reduction in total costs
- The second CAN channel of the CANedge is "released" to record CAN data.
- Internal GNSS message frequency up to 5 Hz and 1 Hz
- GNSS/IMU is now configured through the CANedge profile.
- GNSS timestamps can be used to synchronize CANedge RTCs (drift elimination)
However, if you need to add the GNSS/IMU data to anotherCANmod.gps is relevant for CAN bus systems. In addition, CANmod.gps supports an output rate of 100 Hz for IMU-based messages (angle and acceleration), while the internal GNSS/IMU supports 5 Hz.
The CANedge is the second generation of the CLX000. we generally recommend using the CANedge for data logging use cases, and primarily recommend using the CLX000 if you need to transfer data via USB.
Key improvements of the CANedge over the CLX000 include:
mechanical
- Captureable SD: Captureable SD to transfer data at 80 MB/s (compared to 0.5 MB/s for CLX000 via USB)
- Industrial SD: CANedge utilizes industrial SD cards for improved performance, life, temperature range, etc.
- Channels: 2 x CAN/LIN channels with parallel recording 2 x CAN + 2 x LIN
- Aluminum housing: The new housing is as compact as the CLX000, but more robust and offers mounting flanges.
- Power output: Power external modules, such as GPS to CAN or temperature to CAN modules, via a second port
- Robust Protection: CANedge has enhanced protection against voltage spikes, etc.
Log files and software/API
- MDF4 log files: popular binary MDF4 format, more compact than CSV, faster processing, supported by many CAN tools
- Configuration: Open source configuration editor can be used online/offline through your browser.
- JSON Schema: The profile is based on the standardized JSON Schema concept, which is supported by many open source tools.
- Converter: Open source lightweight converter to convert MDF4 drag and drop/CLI to e.g. *.csv and *.asc.
- asammdf GUI: Supports user-friendly MDF4 journal file editing, DBC conversion (including OBD2/J1939), graphic drawing, etc.
- Python API: Easy large-scale data processing and automatic creation of reports/databases/dashboards, etc.
- MATLAB: Log files are locally integrated with MATLAB's Vehicle Network Toolbox.
- Dashboards: Easily visualize your data in free customizable Grafana dashboards.
Data Logging
- Lossless: CANedge can record complete bus loads with zero message loss (CLX000 limited to ~800-1000 frames/sec)
- Compression: Optional compression reduces file size by up to 80% compared to CLX000.
- Encryption: Optional encryption allows you to encrypt log files on the SD card for added security.
- Advanced configuration: more advanced filters and transmission lists (e.g., up to 128 filters vs. 8 on the CLX000)
- Accuracy: 20x better RTC resolution (50 microseconds) with advanced RTC synchronization options
- Start-up time: Much faster than CLX000 (approx. 1 sec. vs. approx. 10 sec.)
- CAN FD: CANedge supports CAN FD (Flexible Data Rate), making it future-proof!
- Trigger: Controls when to start/stop recording/transmission based on customized CAN signal thresholds.
- Error frame: CANedge supports CAN/LIN error frame recording.
- LIN Slave/Master: The CANedge can act as both a LIN slave and a LIN master (publisher).
GNSS/IMU + connection
- GNSS/IMU: The CANedge supports optional built-in GNSS/IMU functionality.
- WiFi: CANedge2 supports WiFi data transfer to your own cloud/self-rack servers (including OTA updates)
- 4G LTE: CANedge3 supports 4G LTE data transfer to your own cloud/self-rack servers (including OTA updates)
In addition to CANedge2CANedge1 and CANedge2 100% are identical except for the WiFi feature in CANedge3. Similarly, CANedge1 and CANedge3 are identical except for the 4G LTE feature in CANedge3. Also note that CANedge1/CANedge2 supports optional GNSS/IMU, which by default is part of CANedge3.
If you only need to collect CAN data very rarely and the device is easy to physically access, then the CANedge1 will usually suffice. However, if you need to collect data frequently and ideally remotely, then the CANedge2/CANedge3 will soon pay for itself. In particular, if you need to collect data across fleets or machines, CANedge2/CANedge3 is more practical and cost-effective.
The WiFi/LTE connected CANedge has the added advantage that you can fully automate the data collection as well as the data processing workflow. For example, you can set up automatedPython APIScripts to modify data, perform DBC decoding, such as setting up theRemote Information Processing DashboardThe CANedge2 is also easier to manage in the field. CANedge2 is also easier to manage in the field, as you canCANcloud Remote Information Processing PlatformMonitor status and perform operations such as wireless configuration and firmware updates.
For use cases where a WiFi network is available, we recommend CANedge2. If you need to upload data via 4G LTE (cellular), we recommend CANedge3.
CANedge is designed to provide "professional specification" CAN/LIN recorders in the market.Optimal value/cost ratio.
In particular, it is distinguished from similar devices by the following factors:
- Professional specifications: CANedge offers specifications equivalent to the best available recorders
- Compact: CANedge Smaller than similar devices 50-80%
- Low cost: CANedge costs 50-80% less than similar devices
- Easy to use:Device is ready to use without configuration
- FOSS:All software/API tools are 100% free and open source.
- Interoperability:Open standards and tools can be integrated into any system - no lock-in
- Free support:We offer free first-class technical support
For use cases that require the addition of GNSS/IMU, we recommend the option ofBuilt-in CANedge for GNSS/IMU。
For other sensor inputs (temperature, analog, digital, pulse...) you can connect external sensors to the CAN module to the device. In particular, ourCANmodThe Sensor to CAN module can be easily integrated with the CANedge.
Specifically, the CANedge's second port provides 5V DC voltage to the external module for easy installation. Data from the connected sensor to the CAN module is logged in the CANedge log file along with data from the other CAN/LIN channels.
For example, consider ourCANmod.temp Temperature to CAN module orCANmod.input Analog/digital/pulse to CAN module.
The size of the original MF4 journal file depends on the application and the amount of data you want to record.
The following overview shows a typical example of a heavy-duty truck (J1939 data) with a display speed of 700 frames per second. Obviously, if you record everything, an 8 GB SD card will allow you to record data 24/7 for about 7 days, and 32 GB for about 26 days.
However, CANedge supports powerful options for optimizing the size of log files. Therefore, a more realistic scenario is shown below, where for example a 32 GB SD allows you to log more than 800 days.
Below we have listed some of the key features that will allow you to optimize your journal entries:
- Compression:Enable compression to reduce data size by 50-80%
- Filter:Specify CAN IDs to record/ignore (through range and mask)
- Pre-scaler:Instead of recording frames at their "original" frequency, you can customize the frequency with the CAN ID.
- Control signal:Specify when to start/stop recording based on specific CAN signal thresholds
If the SD is full, cyclic logging allows the CANedge CAN recorder to continue logging data by deleting the oldest log file first.
Compared to the CL2000, the CANedge1 CAN logger is superior at logging data to an SD card. However, CANedge1 does not support real-time streaming over USB. We recommend using the CL2000 for this type of use.
For a general introduction to CAN logging with CANedge, please refer to our45-minute webinar。
Below, we outline the basics of how to get started recording raw CAN data:
- Connect the CAN logger to the CAN bus (optionally with our adapter cable)
- The device boots up, detects the bit rate and starts recording raw data to the SD card.
- Disconnect the device, extract the SD and insert it into the PC.
• In asammdf GUI/APIetc. to open the original log file for theDBC Decodingand visualization
The CANedge1 CAN Bus Analyzer can record data for any high-speed CAN bus application (ISO 11898-2). In practice, this includes almost all vehicles (cars, trucks, tractors, forklifts, buses, motorcycles, electric vehicles, etc.) as well as all kinds of production machinery,Battery/BMS for Electric Vehiclesetc. Most aircraft and ships also use CAN buses. In terms of protocols, this includes SAE J1939、CANopen、NMEA 2000、 FMS、OBD2etc.
For the specific case of OBD2 vehicle data, CANedge1 can periodically transmit up to 64 customized CAN messages, meaning it can be used as an OBD2 data logger. Note that you will need to verify that your vehicle uses CAN as the basis for OBD2 communication (e.g. this is the case for all U.S. vehicles built after 2008). Also note that all cars support a different number of OBD2 parameters - CANedge1 will of course only log the supported data.
CANedge requires the use of specific industrial SD card models to ensure performance and power security. You can select either an 8 or 32 GB SD card as an option at checkout (or aPurchase alone）。
You should not use 3rd party SD cards as they may cause data corruption and other forms of non-functional behavior.
Honghong will provide you with any support you need!
Our professional Honghong team will be the first to respond and provide you with the best service to solve all your problems.
