CANedge2: 2x CAN Bus Data Logger (SD + WiFi)

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.

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 will quickly be worthwhile. In particular, if you need to collect data across a fleet of vehicles or machines, the CANedge2 is far more practical and cost effective.

The CANedge2 also 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.

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

Next, you can e.g. set up your own server and configure the CANedge2 to connect to your WiFi to auto-upload log files. When the device is connected, it'll automatically upload log files when they are available on the SD card. Once successfully uploaded, log files are deleted from the SD card.

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.

In addition to the above, the CANedge2 enables automatic upload of log files via WiFi to your own server:

• SD + WiFi: Auto-upload your data via WiFi - and buffer them on the SD when no WiFi is available
• Your server: Retain 100% ownership and control of your data by uploading data to your cloud/self-hosted server
• Security: The CANedge2 enables E2E enterprise grade security

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

Yes, you can use our step-by-step guide to setting up 100% free, customizable telematics dashboards for visualizing your CAN bus data in your browser. The integration uses our free Python API to DBC decode raw CAN data (from local disk or your S3 server) and push it to a time series database. From here, the data can be visualized via the popular dashboard tool, Grafana, enabling fully custom dashboards - e.g. for J1939 telematics, OBD2 telematics, marine telematics, predictive maintenance and more.

For specific examples, see below playgrounds:

J1939 telematics

OBD2 telematics

Marine telematics

UDS telematics

The CANedge2 can upload log files to any S3 server. This includes cloud servers like AWS, Google Cloud, Wasabi, Digital Ocean and more. It also includes self-hosted open source S3 servers like MinIO.

Self-hosting a MinIO S3 server on Windows/Linux (or a Pi) is simple - see our intro. MinIO is a 100% free, open source and lightweight solution. Simply download and start it up - and you're ready to setup your WiFi CAN bus data transfer.

Yes, the CANedge2 WiFi CAN logger is designed for easy CAN-to-cloud integration.

For AWS, Google Cloud, Wasabi S3 and DigitalOcean the setup can be done in < 5 min as they natively support the S3 interface - letting you quickly get started with your WiFi CAN bus data transfer.

For Azure (and other non-S3 cloud servers), you simply need to run an S3 gateway (e.g. Flexify.io) on the server. This is a bit more extensive vs. e.g. AWS/Google Cloud - but is still simple to set up.

For details, see our S3 cloud setup guide.

Generally, S3 cloud storage is low cost - and for this reason we recommend to use a cloud S3 server for most use cases as it simplifies deployment and scalability.

The cost of your cloud storage of course depends on how much data you upload - and how much you decide to retain. In most realistic scenarios where you've optimized your log file size via filters/prescalers/compression, a single CANedge would upload ~1 GB per month. Assuming you wish to retain the last year of data for each device, that means storing ~12 GB/device.

As an example, AWS S3 costs 0.023$ / GB / month - i.e. < 0.3$ / device / month for storing the latest 12 months of data.

Yes, you can easily automate your CANedge data processing through various tools:

• Python API: Our Python API lets you easily list, load and DBC decode your data (from local disk or your server). It is ideal for big data processing, database integration, predictive maintenance and more
• MATLAB: You can easily load your data in MATLAB's Vehicle Network Toolbox to leverage their data processing tools
• S3 API: You can use the S3 API to automate handling of files stored on your S3 server

To get started with automation, we recommend to check out our API examples on github.

The CANedge lets you fully customize which CAN IDs you record - and at what frequency. It also supports data compression and 'triggers' (to start/stop logging under certain conditions). Together, these features typically let you reduce your log file size by 90%+ - and it is highly recommended that you make use of them to minimize storage costs.

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 series is generally superior when it comes to logging data to the SD card vs. the CLX000. However, the CANedge does not support real-time streaming via USB. For this type of use case, we would recommend e.g. the CL2000. We may later on add new products focused on wireless real-time streaming.

No, the CANedge2 has an 8-32 GB SD card and will simply operate as a standalone CAN logger if no WiFi is available. For most CAN bus applications, 8-32 GB will provide several months of data capacity. Further, if the SD card is full the device deletes the oldest log files to free up space via cyclic logging.

When the WiFi is available again, the CANedge2 automatically starts pushing the accumulated log files to your server. Once a log file is successfully uploaded, it is deleted from the SD card.

The CANedge2 can split files every 10 - 86400 seconds or every 1 - 512 MB. When a new log file is created, it is automatically transferred to your server if the CANedge2 is connected to a WiFi access point. As such, you can get a steady stream of incoming files - and by using e.g. AWS Lambda and our Python API, you can auto-process the incoming data in 'near real-time'.

We have various users that deploy the CANedge2 for near real-time upload, see e.g. this automotive predictive maintenance case study. However, setting this up for effective use requires a slightly more advanced use of the data processing tools available.

For most intents and purposes, however, we recommend to use medium/larger log file sizes (e.g. 5-20 MB) to avoid an excessive amount of log files in your server.

MQTT (Message Queuing Telemetry Transport) is a light weight messaging protocol, which is used by many IoT devices. As such, it is also supported by some cloud server IoT services for enabling e.g. statistics and analytics.

We originally considered the MQTT protocol as an option for uploading data via the CANedge2, but found that it is less suited for "big data" uploading. The protocol is ideal for very small packets at low resolution sent by e.g. streaming devices (with no local storage capability). However, for logging the full CAN bus load from e.g. a vehicle, the MQTT protocol would quickly get overloaded - resulting in very poor performance. For example, the protocol would make it practically impossible to "offload" all the data recorded on the CANedge2 SD card after e.g. a period with no coverage as new data would be recorded at a higher rate than it could be uploaded.

Instead, the CANedge2 utilizes the S3 REST interface with the HTTP(S) protocol. This combination is ideal for uploading large log file packets to either local/dedicated servers like MinIO or cloud servers like e.g. AWS, Google Cloud and Azure. In particular, it allows for uploading data from the CANedge2 much faster rate than new data is recorded - meaning that the device can stay offline for longer periods and still offload all log files when it regains coverage.

The CANedge2 currently supports 'Station Mode' with automatic upload of log files to your server via an S3 interface. As an alternative to the S3 interface, you can configure the device to use the web server interface. Here, you can pull data selectively by accessing the device SD card via your browser (like a web page) or via the REST API (e.g. via Python scripts). The CANedge2 can connect to an existing WiFi router - or you can use your laptop as the WiFi access point, thus practically enabling a form of 'Access Point' connectivity directly between your PC and the CANedge2.

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.

Yes, we actively seek to collaborate with partners - in particular 'system integrators'. The CANedge2 is designed to be easy to work with (plug & play cloud integration, open source file format, S3 interface, APIs, ...). The aim is that the device can serve as a plug & play hardware platform for companies focused on integrating the device in specific industries.

Please contact us to discuss further.