CANedge3: 2x CAN Bus Data Logger (SD + 3G/4G + GPS/IMU)

Yes, this version of the CANedge includes a GNSS/IMU module. If you install the device with an external GNSS antenna, this lets you optionally record GNSS/IMU data in time sync with your 2 x CAN/LIN data.

The GNSS/IMU information is recorded as if the data was being broadcast on 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 connecting a GPS-to-CAN module (like the CANmod.gps) to the CANedge (e.g. on the 2nd port).

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

• It is far more compact - and easier to install
• Total cost is 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 vs. 1 Hz
• The GNSS/IMU is now configured via the CANedge Configuration File
• The GNSS timestamp can be used to sync the CANedge RTC (eliminating drifting)

The CANmod.gps is, however, relevant if you need to add GNSS/IMU data to another CAN bus system. Further, the CANmod.gps supports a 100 Hz output rate for the IMU based messages (angular and acceleration rates) vs. 5 Hz for the internal GNSS/IMU.

Yes, the CANedge3 comes with a built-in cellular 3G/4G LTE module and a SIM card slot. This enables the device to automatically upload CAN/LIN data log files to your own server via 3G/4G LTE - as well as support over-the-air updates.

In most use cases, the device will be continuously connected to your server - meaning that whenever a new log file is available on the SD card, it will be immediately uploaded to your server. Further, if the device is outside coverage for an extended period, no data is lost as the device simply accumulates log files on the 8-32 GB SD card during this period. When it returns to cellular coverage, the log files are offloaded in chronological order.

Generally speaking, you can use any SIM card that is compatible with the device and the supported frequency bands. Some SIM cards, however, may have special requirements/properties that may make them incompatible. We aim to provide a list over time of verified SIM cards as the CANedge3 is deployed globally.

If you do not have a preferred SIM card provider, you can optionally consider the included global 'Super SIM' that ships with the device. This SIM card can be activated upon reception, allowing you to create an account with KORE and handle your data transfer subscriptions through them. KORE is a global provider, specializing in IoT SIM solutions with high performance. Further, due to the global CANedge3 volume, you'll benefit from 90% reduced data transfer rates - even if you only deploy one CANedge3.

The best solution depends on your use case - if any questions, contact us.

The cost of the 3G/4G LTE data transfer depends on a number of parameters:

• What your data provider charges per SIM and MB
• How much data you wish to collect per device per month

The cost per MB depends on your provider and subscription solution - and typically vary dramatically country-by-country.

For example, the included Super SIM provides a rate of 0.005$/MB (5$/GB) for USA, which is a highly competitive solution for low-to-medium transfer volumes. Other countries may offer higher/lower rates through local providers.

The amount of data a CANedge3 generates per month depends entirely on your use case requirements.

If you need to log all CAN IDs at their 'raw' frequency from a vehicle operating 24/7, you could be looking at 10+ or even 50+ GB per month. For such use cases, you'd typically be best off with a flat-rate data solution.

In more realistic scenarios, you will be leveraging the powerful data optimization features of the CANedge3. Specifically, you can filter which CAN IDs to record and at what frequency. Further, you can set up triggers to start/stop logging based on CAN signal thresholds. Finally, you can compress the data to reduce the size before transferring it. As such, most realistic use cases involve uploading 0.1 GB to 5 GB per month per device.

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)
• 3G/4G LTE: The CANedge3 supports 3G/4G LTE data transfer to your own cloud/self-hosted server (incl. OTA updates)

The CANedge1 and CANedge3 are 100% identical, except for the 3G/4G LTE functionality in 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 CANedge3will quickly be worthwhile. In particular, if you need to collect data across a fleet of vehicles or machines, the CANedge3 is far more practical and cost effective.

The CANedge3 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 CANedge3 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 (focused on the CANedge1/CANedge2).

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 CANedge3 to connect to it 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.

Note that you can use the SIM card that comes with the device - or insert your own SIM 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 CANedge3 enables automatic upload of log files via 3G/4G LTE to your own server:

• SD + 3G/4G LTE: Auto-upload your data via 3G/4G LTE - and buffer them on the SD when outside coverage
• Your server: Retain 100% ownership and control of your data by uploading data to your cloud/self-hosted server
• Security: The CANedge3 enables E2E enterprise grade security

Finally, the inclusion of internal GNSS/IMU solidifies the versatility of the device.

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 CANedge3 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 3G/4G LTE CAN bus data transfer. Note that in order to upload data via cellular to a self-hosted S3 server, the server must be 'port forwarded' so that it becomes accessible outside of the host machine's local network (see our documentation for details).

Yes, the CANedge3 3G/4G LTE 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 3G/4G LTE 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.

Due to the inclusion of internal GNSS/IMU in the CANedge, it already lets you record GNSS/IMU data.

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 CANedge3 has an 8-32 GB SD card and will simply operate as a standalone CAN logger if no cellular coverage 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 4G LTE coverage is back, the CANedge3 automatically starts pushing the accumulated log files to your server. Once a log file is successfully uploaded, it is deleted from the SD card. Note also that if the connection is lost mid-transfer, no data is lost.

The CANedge3 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 via 3G/4G LTE. 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/CANedge3 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.

The CANedge3 will in most setups upload data at a rate of around 4-7 MB/minute. This is fully sufficient to enable consistent offloading of the SD card for most use cases.

For example, if you log 2 x CAN from a truck without any size optimization, you would typically generate ~1-3 MB/minute of data. In this case, you will easily be able to offload the log files even if you have periods without coverage.

Further, in more realistic scenarios, you will want to optimize your log file size via filters, prescalers, compression and triggers - see also our guide on this. Enabling such optimizations will normally result in closer to 0.01-0.05 MB/min of data being recorded.

As such, the main situation where the upload speed may become a bottle neck is if you're deploying the CANedge3 to 'record everything' for extended periods where the device is outside cellular coverage (e.g. on a maritime vessel or in a mine). Here, you will need to review how much data you accumulate during periods out-of-coverage vs. how much time the device spends in-coverage.

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/CANedge3, 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 CANedge3 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 CANedge3 utilizes the S3 REST interface with the HTTP(S) protocol. This combination is ideal for uploading large log file packets to either self-hosted servers like MinIO or cloud servers like e.g. AWS, Google Cloud and Azure. In particular, it allows for uploading data from the CANedge3 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 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 CANedge3 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.