CSS CANedge1 (SD, RTC and GNSS/IMU)
2 Ch CANBus Data Logger (SD, RTC and GNSS/IMU)
The plug & play 2x CAN/LIN logger records timestamped CAN data (Classical/CAN FD) to the extractable 8 GB industrial SD card.
It’s easy-to-use: Simply connect the device to your CAN bus to start logging raw CAN data. Next, extract the data and process it using 100% free open source software/API tools – incl. file format conversion, DBC decoding and plot visualization.
The device includes GNSS/IMU, adding data like position, speed, attitude, acceleration and more.
Ideal for recording CAN/LIN data over weeks, months or years – e.g. for diagnostics, OEM development or legal/warranty purposes.
CSS CANedge1 includes an extractable 8-32 GB industrial SD card (Class 10). This ensures e.g. optimal endurance and rapid data transfer (W/R 50/80 MB/s)
CSS CANedge1 enables logging of raw CAN/LIN data incl. CAN FD, J1939, CANopen, OBD2, UDS, ISOBUS, NMEA2000 – across any CAN/LIN application.
CSS CANedge1 is designed to be extremely compact (75 x 47 x 20 mm). Despite the robust aluminium enclosure, it weighs only 100G.
The 2x high speed CAN channels enable time-synced recording of data from two CAN buses – ideal for e.g. many heavy duty vehicle applications
The 2nd port (CH2) provides a configurable 5V power out, letting you easily power e.g. CSS CANmod sensor-to-CAN modules (temperature, analog/digital/pulse)
CSS CANedge1 comes with flanges to enable easy installation at scale. The ‘mounting kit’ includes screws and optional vibration dampeners.
Pro Specs CSS CAN Logger at half the cost
CSS CANedge1 combines innovative design, cutting-edge components, incredibly low costs:
- Dual high speed CAN/LIN (include CAN FD) channels
- Extractable 8-32 GB industrial SD Card (Months of Data)
- Binary MDF4 log file format (Extensive Software Support)
- Advanced message filtering and transmit functionality
- Start/Stop logging triggers based on CAN ID and databytes
- Silent Mode, bit rate auto detection, cyclic logging
- Data Compression and Encryption (E.g. For GDPR, CCPA)
- Support for CAN/LIN error frame logging
- Fast boot time, safely disconnect during use, power safe
GPS & 3D IMU – enrich your data
CSS CANedge1 comes with cutting-edge GNSS/IMU functionality – perfect for automotive/maritime use cases.
- Add 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 precision via sensor fusion – even in GNSS hostile areas
- Signals encoded as ‘internal’ CAN frames (separate channel)
- Configurable message inclusion/frequency (up to 5 Hz)
- DBC file included for easy decoding to human-readable form
- Optionally sync the CSS CANedge RTC via precise GNSS time
- Flexible deployment via external GNSS antenna
Position + sensor fusion
Add time-synced GPS positioning to your CAN/LIN data – with sensor fusion (UDR) for 3x higher accuracy.
Speed
Speed data is useful in e.g. fleet telematics to identify speeding, idle time, asset utilization rates and more.
Altitude
Altitude is key in e.g. analysis of fuel/battery consumption – or e.g. in aerospace applications like drones, planes etc.
Attitude
The GNSS/IMU enables attitude data, giving a 3D view of the asset orientation at any time [automotives].
Trip distance
Odometer data enables easy tracking of the trip distance traveled by the asset (since last module power cycle).
Angular rates
3D IMU angular rates can be used in e.g. the analysis of driving and vehicle dynamics (tire/suspension, drifting).
Acceleration rates
3D IMU acceleration rates can be used in e.g. analysis of driving quality and predictive maintenance.
Geofences
Configurable circular geofences are useful for e.g. theft prevention, safety, automation and more
Timestamp
The high precision epoch timestamp is useful e.g. in syncing the CSS CANedge real-time clock.
Open Source Software/API Naturally
CSS CANedge1 uses open formats (MDF4 data, JSON config, S3 Server) and all software/APIs are 100% free and open source.
The software toolbox includes:
- Editors – Easily modify your device config (online/offline)
- Converters – Convert data to Vector ASC, PEAK TRC, CSV, …
- asammdf GUI – DBC convert, plot and export your data
- Python API – Automate your data processing and integrations
- Dashboards – Visualize data in custom browser dashboards
Technical Specifications
| GENERAL | |
|---|---|
| Functionality | Standalone CAN bus data logger with SD card and 2xCAN/LIN channels (incl. CAN FD) and GNSS/IMU |
| Firmware | Supports free firmware updates for adding features |
| Configuration | Configuration files based on the popular open source JSON schema concept |
| Software | Free open source editor tool for easy device configuration (offline/online version available) |
| Free open source asammdf software & API for editing, DBC converting & plotting MDF4 data | |
| Free open source MF4 converters – drag & drop log files to convert into e.g. CSV, ASC, TRC | |
| Free open source Python API – e.g. for automated data processing, reporting or integrations | |
| Free open source telematics dashboards for visualizing your DBC decoded data in your browser | |
| Safety | CE, FCC, IC, KC and RoHS certified (see the manual) |
| Tested for voltage transients (emissions/immunity), ISO 7637-2:2011, by TUV SUD (see the manual) | |
| Warranty | 1-year warranty |
| Support | Free, fast & high quality support |
| Origin | Denmark |
| CAN BUS | |
|---|---|
| Channels | 2 x CAN channels (incl. CAN FD support) |
| Standard | ISO 11898: Compliant with CAN (up to 1 Mbit/s) and ISO & Bosch CAN FD (up to 4 Mbit/s payload rate) |
| Protocols | Log raw data from CAN based protocols (J1939/FMS, CANopen, NMEA 2000, OBD2, CAN FD, UDS, …) |
| Identifiers | Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID) |
| Bit-Rate Auto-Detect | Bit rate can be auto-detected or set manually |
| Retransmission | Configurable retransmission of frames that have lost arbitration or been disturbed by errors |
| Transceiver Protection | ±16 kV HBM ESD, ±15 kV IEC ESD, ±70 V bus fault, short circuit |
| Common mode input voltage: ±30 V | |
| TXD dominant timeout (prevents network blocking in the event of a failure) |
| LIN BUS | |
|---|---|
| Channels | 2 x LIN channels |
| Publisher/Subscriber | Each LIN channel can be configured as a LIN subscriber/publisher with support for LIN data transmission |
| Custom length | Support for custom frame lengths |
| Standard | Compliant with LIN 2.0 up to 20 Kbit/s (support for Classic & Enhanced checksum format) |
| Transceiver Protection | ±8 kV HBM ESD, ±1.5 kV CDM, ±58 V bus fault |
| TXD dominant timeout (prevents network blocking in the event of a failure) |
| DATA LOGGING | |
|---|---|
| SD Card | 8 GB extractable Class 10 industrial micro SD (SDHC) included (optional 32GB) – read at 80 MB/s |
| Parallel CAN/LIN | Record data from up to 2 x CAN channels + 2 x LIN channels, simultaneously |
| Real-Time Clock | Yes – CAN frames are date & timestamped with 50 microsecond resolution (battery backup) |
| RTC can be configured to match local time zones (default: UTC) | |
| RTC can be auto-synced via a CAN message (e.g. from the internal GNSS timestamp) | |
| Log File Format | Log data in industry standard binary MF4 (easily convert to e.g. CSV, ASC, pandas, MATLAB, …) |
| Data Compression | Configurable embedded log file zipping (~50-80% size reduction) |
| Silent Mode | Configurable silent mode: Restricted (acknowledge only) or monitoring (zero transmission) |
| Filters | 128/64 regular/extended ID filters per channel (range, mask, acceptance, rejection, prescaling) |
| Prescaling | Prescale CAN frames to record e.g. by time (per X ms) or by data (e.g. if byte X or Y changes) |
| Transmit | Transmit lists of CAN frames per channel (single-shot/periodic) – e.g. for OBD2 requests |
| CAN Error Frames | Support for logging CAN error frames (bit-stuffing, form, CRC, bit, acknowledgement) |
| LIN Error Frames | Support for logging LIN error frames (checksum, receive, synchronization, transmission) |
| Remote Frames (RTR) | Support for logging/transmission of remote CAN frames (RTR) |
| Cyclic Logging | Optional cyclic logging mode (oldest log file is deleted when SD card is full) |
| Advanced Triggers | Control signal lets you start/stop logging based on custom CAN IDs & data thresholds |
| CAN Heartbeat | Optionally transmit heartbeat CAN frame with device status, storage used & RTC time |
| File Split | Configurable log file split size (by size: 1-512 MB and/or by time period: 0-86400s) |
| Power Safe | 100% power safe data logging – no file corruption when disconnected |
| Unique Device ID | Each device has a globally unique ID ensuring unique log file naming |
| Data Encryption | Log files can be encrypted at rest on the SD card for security/GDPR/CCPA purposes |
| GNSS & 3D IMU | |
|---|---|
| Module | Professional-grade u-blox NEO-M9V sensor module (92-channel) with built-in gyroscope and accelerometer |
| GNSS | Supports combinations of GPS (USA), Galileo (Europe), BeiDou (China), GLONASS (Russia) |
| Sensor Fusion (UDR) | Enhanced position precision via sensor fusion (UDR) of GNSS and 3D IMU [automotives only] |
| Up to 3x better accuracy vs. GNSS-only receivers | |
| Extended and improved GNSS fix in GNSS hostile areas (e.g. urban environments, tunnels, …) | |
| Accuracy | Position: 2.0 m CEP (Circular Error Probable) |
| Heading: 0.3 deg | Pitch: 0.4 deg | Roll: 0.6 deg (68% at 30 m/s) | |
| Velocity: 0.08 m/s | |
| Sensitivity | Tracking/Navigation: 160 dBm | Cold starts: 148 dBm |
| Acquisition | Cold starts: 25 s |
| GNSS Antenna | Required for GNSS-based data (not for IMU) |
| DATA PARAMETERS | |
|---|---|
| CAN encoding | The GNSS/IMU data is encoded as ‘CAN messages’ within the CANedge log files (on a separate channel) |
| Configuration | GNSS/IMU messages can be filtered/prescaled to enable custom message inclusion and frequency |
| Optionally record GNSS/IMU messages only if valid | |
| Signals | The module adds several GNSS/IMU signals (for a full list, see the Docs or DBC file) |
| GNSS position: Longitude and latitude information [5 Hz] | |
| GNSS time: Precise GNSS based epoch timestamp [5 Hz] | |
| GNSS status: Fix type (NO/UDR/2D/3D/GNSS+UDR) and satellite count [5 Hz] | |
| GNSS speed: Travel speed in m/s and km/h [5 Hz] | |
| GNSS altitude: Altitude in meters [5 Hz] | |
| Attitude/orientation: Roll, pitch, heading [automotives only] [5 Hz] | |
| GNSS odometer: Distance traveled (since power on) [5 Hz] | |
| 3D IMU: Gyroscope-based angular rate (X, Y, Z) and accelerometer-based acceleration (X, Y, Z) [5 Hz] | |
| Geofences: Status of the configured geofences [5 Hz] |
| ELECTRICAL | |
|---|---|
| Input Supply | +7V to +32V DC via the Channel 1 DB9 (e.g. via CAN connector power pin) |
| Power Consumption | Extremely low (~1 W) – no risk of battery drainage |
| Protection | Reverse voltage protection on CAN-bus supply |
| Transient voltage event protection on supply lines |
| MECHANICAL | |
|---|---|
| Enclosure & Weight | Compact aluminium enclosure: 75 x 47 x 20 mm (W x L x H excl. flanges). 100 grams |
| Antennas | GPS antenna included |
| Flanges | Flanges with 4 x M3 screw holes (head diameter < 6 mm) – see also the CANedge ‘mounting kit’ |
| Connector | 2 x Standard D-sub 9 (DB9) connectors (optional OBD2/J1939/… adapters) |
| Pin-Out | See the product manual for the DB9 connector pin-outs |
| Configurable Power Out | Channel 2 can be configured to supply 5V to external modules (e.g. the CANmod sensor-to-CAN modules) |
| LEDs | Logger status via 4 external LEDs: Power, CH1, CH2, Memory |
| Temperature | Operating temperature (parts): -25degC to +70degC |
| IP Rating | IP Rating 40 |