The three product types serve different use cases - and are often combined:

• Use the CANedge if you want to record CAN data autonomously to an SD card in the field (with no PC connected) for later analysis, and optionally have it pushed to your own server - ideal as a blackbox or OEM telematics device
• Use the CANsub if you want to interact with a live/real-time CAN bus from your PC via USB or Ethernet - send/receive frames, decode signals in real time, debug or sniff
• Use the CANmod if you want to add data to a CAN bus that is not natively on the CAN bus (GNSS, temperature, analog, ...) - either for ECUs/displays on the bus to consume, or to be picked up by a logger such as the CANedge

In short: log with the CANedge, stream with the CANsub, enrich with the CANmod. The three are designed to complement each other - and our free open source software/APIs work seamlessly across all of them.

If you're in doubt which CAN logger to choose, contact us - we always respond fast with quality sparring.

Below is our 'rule of thumb' guidance:

• CANedge1: If you only need to log timestamped data to an SD card
• CANedge2: If you need to log data to an SD card and transfer it via a WiFi access point to your own server
• CANedge3: If you need to log data to an SD card and transfer it via 3G/4G LTE to your own server

If you need to collect data frequently/automatically/remotely, see the CANedge2/CANedge3.

Our CANedge CAN bus data loggers are plug & play, letting you record raw CAN data out-the-box:

• Connect the device to your CAN bus (optionally using one of our DB9 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 (or extract via USB for the CLX000)
• From here, you can open the raw log files in the free open source software to DBC decode & analyze it

In addition, there are vast configuration options and ways to utilize the software/APIs as part of your CAN data acquisition.

For more details, see the get started guides which go through each step of the CAN logging and data processing.

We also recommend our 1 hour webinar on CAN bus data logging:

Our CANsub CAN-USB/Ethernet interface lets you stream raw CAN data in real-time with zero software installation:

• Connect the device to your CAN bus (optionally using one of our DB9 adapter cables)
• Power the CANsub via USB (or Ethernet/PoE) - the built-in LCD display shows the device URL/IP
• Enter the URL in any browser to instantly open the on-device webCAN app - no installation needed
• From here you can configure bit rates, load DBC files and DBC decode & plot CAN signals in real-time

Beyond webCAN, you can also stream data via Python, SavvyCAN, SocketCAN or build custom web apps using the open OpenAPI/websocket interfaces.

For more details, see the get started guides which go through each step of the CAN bus streaming workflow.

Below we detail what type of data you can record with our CAN bus systems (split by protocol, application and parameters):

Our CAN bus data loggers and interfaces let you record 'raw' CAN bus data, i.e. timestamped CAN frames with CAN IDs, CAN data bytes etc. To enable analysis and visualization of this data, you will typically want to decode it to extract the encoded CAN signals as physical values aka human-readable form - degC, %, km/h etc. This decoding process is done via suitable software/API tools (which we provide for all devices) and a DBC file, which is essentially a text file containing information on how to interpret raw CAN bus data for a specific vehicle/machine/sensor etc.

If you are the manufacturer of the CAN bus equipment you record from, you typically have the relevant DBC file readily available. If not, you can try to request the DBC file from the OEM - though it is not always possible to get. In such cases, however, you can often benefit from industry standardization where a single DBC file can be used across many different manufacturers/brands. We offer such standardized DBC files for the most common use cases:

• J1939 DBC: Decode data from heavy-duty vehicles like trucks, buses and tractors. Includes 2000+ PGNs and 14000+ SPNs
• J1939-73 DBC: Decode J1939 diagnostic messages like DM1 to identify faults in heavy-duty equipment
• NMEA 2000 DBC: Decode marine CAN data from boats and ships. Contains 170+ PGNs and ~1500 signals
• OBD2 DBC: Decode CAN bus data from practically all passenger cars via the standardized OBD2 protocol (100% free)

Our CAN loggers are used in many different use cases - incl. below examples:

See also our 100+ case studies & reviews section with practical use cases from our end users.

Yes, see our overview of free software/API tools - and our recap below:

Free software/API tools (CANedge)

Free software tools (CANsub)

Free software tools (CANmod)

Note: All the above tools are 100% optional - you can use the CANedge/CANsub/CANmod devices without any of the above.

Yes, our devices are designed for easy white labeling:

• The CANedge SD card, configuration files, log files etc. are 'sanitized' by default - i.e. no mention of product/company name
• The CANedge/CANsub/CANmod can be purchased without the front logo silk print and the backside label can be removed
• Software like CANcloud and Grafana dashboards are open source enabling you to customize them to your needs
• You host your own server (with no vendor lock-in) - i.e. we do not charge any subscription fees or similar
• With the open source APIs, it is simple to create e.g. automated reports, dashboards or database integrations

To learn more about our white label options, please contact us.

• We ship within 1-2 work days with express (1-3 days) or free (8-12 days) shipping
• We ship globally - if your country is not listed during check-out, contact us
• Unless otherwise stated, all products are in stock