CSS Electronics CANedge1 Can Bus Logger

Yes, this version of the CANedge contains a GNSS/IMU module. If you install the device with an external GNSS antenna, you can optionally record GNSS/IMU data time-synchronised with your 2 x CAN/LIN data.

The GNSS/IMU information is recorded as if the data were being sent over a CAN bus network recorded by the CANedge. To separate it from the CAN/LIN channels, the data is stored in the log files under a separate "internal" pseudo channel.

Previously, adding GNSS/IMU to the CANedge required the connection of a GPS-to-CAN module (such as CANmod.gps ) to the CANedge (e.g. on the 2nd port).

The new internal GNSS/IMU offers a number of advantages:

• It is much more compact - and easier to install
• The overall costs are drastically reduced
• The 2nd CAN channel of the CANedge is "freed up" for logging CAN data
• The internal GNSS messages are available at up to 5 Hz instead of 1 Hz
• The GNSS/IMU is now configured via the CANedge configuration file
• The GNSS timestamp can be used to synchronise the CANedge RTC (avoiding drift).

However, the CANmod.gps is relevant if you need to add GNSS/IMU data to another CAN bus system. In addition, CANmod.gps supports an output rate of 100 Hz for the IMU-based messages (angle and acceleration rates) compared to 5 Hz for the internal GNSS/IMU.

The CANedge is the 2nd generation of the CLX000. In general, we recommend using the CANedge for data logging applications, while the CLX000 is especially recommended if you need to stream data via USB.

The most important improvements to the CANedge compared to the CLX000 include

Mechanical

• Extractable SD: The SD can be extracted to transfer data at 80 MB/s (compared to 0.5 MB/s for the CLX000 via USB).
• Industrial SD card: The CANedge utilises an industrial SD card, improving performance, lifetime, temperature range and more
• Channels: 2 x CAN/LIN channels, enables parallel logging of 2 x CAN + 2 x LIN
• Aluminium housing: The new housing is just as compact as the CLX000, but significantly more robust and offers flanges for mounting
• Power output: Supply external modules with power via the 2nd port, e.g. a GPS-to-CAN or temperature-to-CAN module
• Robust protection: The CANedge has a stronger protection specification, for example against voltage peaks

Protocol files and software/API

• MDF4 log files: Popular binary MDF4 format - more compact than CSV, faster to process, supported by many CAN tools
• Configuration: The open source configuration editor can be used online or offline via your browser
• JSON schema: configuration files are based on the standardised JSON schema concept supported by many open source tools
• Converters : Lightweight open source converters allow drag & drop/CLI conversion from MDF4 to e.g. *.csv and *.asc
• asammdf GUI : Enables user-friendly editing of MDF4 log files, DBC conversion (incl. OBD2/J1939), graphical representations and more
• Python API : Easily process your data at scale and automate the creation of e.g. reports/databases/dashboards
• MATLAB : Log files can be natively integrated into the MATLAB Vehicle Network Toolbox
• Dashboards : Easily visualise your data in free customisable Grafana dashboards

Data acquisition

• Lossless: The CANedge can log full bus loads without message loss (the CLX000 is limited to ~800-1000 frames/sec).
• Compression: With the optional compression, you can reduce the file size by up to 80 % compared to the CLX000
• Encryption: With the optional encryption, you can encrypt log files on the SD card for additional security
• Extended configuration: Extended filters and transmission lists (e.g. up to 128 filters compared to 8 with the CLX000)
• Precision: 20 times higher RTC resolution (50 microseconds) - with advanced RTC synchronisation options
• Boot time: Much faster boot time compared to the CLX000 (~1 sec. vs. ~10 sec.)
• CAN FD: The CANedge supports CAN FD (Flexible Data Rate) and is therefore future-proof
• Trigger: Control when logging/transmission should be started/stopped based on user-defined CAN signal thresholds
• Error frame: The CANedge supports the logging of CAN/LIN error frames
• LIN slave/master: The CANedge can serve as both a LIN slave and a LIN master (publisher).

GNSS/IMU + connectivity

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

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

If you only need to collect your CAN data infrequently and the device is physically easily accessible, then CANedge1 is usually sufficient. However, if you need to collect your data frequently and preferably remotely, the CANedge2/CANedge3 will quickly become worthwhile. Especially if you need to collect data on a fleet of vehicles or machines, CANedge2/CANedge3 are far more practical and cost-effective.

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

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

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

The following overview shows a typical example for a heavy goods vehicle (J1939 data) with 700 frames/second. If you record everything, you can record data around the clock for about 7 days with an 8 GB SD card, while with 32 GB you can record for about 26 days.

However, the CANedge supports powerful options to optimise the log file size. Therefore, a more realistic scenario is shown below, where you can record more than 800 days with a 32 GB SD card, for example.

Below we list some of the key features you can use to optimise your logging:

• Compression: activate compression to reduce the data size by 50-80%.
• Filter: Specify which CAN IDs should be recorded/ignored (via ranges and masks).
• Prescaler: Instead of recording frames with their "raw frequencies", you can adjust the frequency based on the CAN ID
• Control signal: Specify when to start/stop logging based on specific CAN signal thresholds
• When the SD card is full, cyclic logging allows the CANedge CAN logger to continue logging data by deleting the oldest log files first.

The CANedge1 CAN logger is superior to the CL2000 when it comes to logging data to the SD card. However, the CANedge1 does not support real-time streaming via USB. For such an application, we would recommend the CL2000, for example.

You can find a comprehensive introduction to CAN logging with CANedge in the 45-minute webinar .

Below we explain the basics of how you can start logging raw CAN data:

• Connect the CAN logger to your CAN bus (optionally with our adapter cables)
• The device switches on, recognises the bit rate and starts logging the raw data to the SD card
• Disconnect the device, extract the SD card and insert it into your PC
• open the raw log files e.g. in the Asammdf GUI/API for DBC decoding and visualisation

You can find more information on the first steps in the CANedge introduction and in the documents - or contact us if you have any questions.

The CANedge has been developed to offer the best price/performance ratio on the market for CAN/LIN loggers with professional specifications.

In particular, the following factors set it apart from similar devices:

• Professional specifications: The CANedge offers specifications comparable to the best loggers available
• Compact: The CANedge is 50-80% smaller compared to similar devices
• Low cost: The CANedge is 50-80% less expensive compared to similar devices
• Easy to use: The device can be used immediately without configuration
• FOSS: All software/API tools are 100% free and open source
• Interoperable: Open standards and tools enable integration into any system - without lock-in
• Free support: We offer free, first-class technical support
  But don't take our word for it - check out the 50+ case studies from companies like VW, Siemens, Bosch, Cummins and others.

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

The CAN bus analyser CANedge1 can log 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, motorbikes, electric vehicles, ...) - as well as various production machines, EV batteries/BMS and more. Most aeroplanes and boats also use the CAN bus. In terms of protocols, this includes SAE J1939 , CANopen , NMEA 2000 , FMS , OBD2 and more.

For the special case of OBD2 vehicle data, the CANedge1 can send up to 64 customised CAN messages periodically and thus be used as an OBD2 data logger. Note that you need to check whether your car uses CAN as the basis for OBD2 communication (this is the case for all US cars manufactured after 2008, for example). Also note that all cars differ in the number of OBD2 parameters supported - and of course the CANedge1 can only record the supported data.

For applications where you need to add GNSS/IMU, we recommend selecting a CANedge with integrated GNSS/IMU .

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

In particular, the second CANedge port can supply external modules with 5 V DC - which makes installation easy. The data from the connected Sensor-to-CAN modules is recorded in the CANedge log files together with the data from the other CAN/LIN channels.

Think for example of our CANmod.temp temperature-to-CAN module or our CANmod.input analogue/digital/pulse-to-CAN module.