PC interface card for CAN (1 x CAN), top-entry, galv. isolated
Item number 1.01.0237.90001
The Ixxat CAN-IB120/PCIe Mini is a passive PCI Express Mini interface card with one CAN channel, galvanic isolation and top-entry CAN socket. It is an easy and cost-efficient way to connect computers to a CAN bus network. Thanks to its very compact dimensions, the card is especially suitable for applications with limited space.
Connects computers and embedded systems to industrial Ethernet networks
Item number 1.01.0340.20151
The Ixxat INpact CE Slave PCIe Mini Bracket Kit is a versatile and efficient solution to connect embedded systems and PCs to industrial networks. This Common Ethernet variant offers both preinstalled and downloadable protocols, enabling flexible multi-network communication in a compact PCIe Mini format. The kit includes an Ixxat INpact PCIe Mini, a connection cable, a bus coupling unit and a bracket plate.
PC interface adapter (2 x CAN, LIN), galv. isolated
Item number 1.01.0283.22042
The Ixxat USB-to-CAN V2 automotive is an easy, versatile and cost-efficient way to connect computers to fieldbus networks, enabling seamless integration into diverse industrial setups and various CAN applications. It offers two switchable CAN interfaces, one of which can be switched to CAN low-speed, and a LIN interface, each galvanically isolated.
PC interface adapter (2 x CAN, LIN), galv. isolated
Item number 1.01.0283.22042
The Ixxat USB-to-CAN V2 automotive is an easy, versatile and cost-efficient way to connect computers to fieldbus networks, enabling seamless integration into diverse industrial setups and various CAN applications. It offers two switchable CAN interfaces, one of which can be switched to CAN low-speed, and a LIN interface, each galvanically isolated.
PC interface card for CAN (1 x CAN)
Item number 1.01.0231.11000
The Ixxat CAN-IB100/PCIe is a passive PCI Express interface card with one CAN channel. It is an easy and very cost-efficient way to connect computers to a CAN bus network, enabling simple integration into diverse industrial setups, supporting various CAN applications.
Connects computers and embedded systems to industrial EtherCAT networks
Item number 1.01.0340.21101
The Ixxat INpact ECT Slave PCIe Mini Kit is a versatile and efficient solution to connect embedded systems and PCs to EtherCAT networks. This preconfigured EtherCAT variant features a compact PCIe Mini format and is ideally suited for real-time control and automation applications in demanding industrial environments. The kit includes an Ixxat INpact PCIe Mini, a connection cable and a bus coupling unit.
PC interface card for CAN (2 x CAN), galv. isolated
Item number 1.01.0293.22001
The Ixxat CAN-IB400/PCI is an active PCI interface card with two CAN channels and galvanic isolation. It is an easy and cost-efficient way to connect computers to a CAN bus network. Based on a modular design, the card enables simple integration into diverse industrial setups, supporting various CAN applications.
Connects computers and embedded systems to PROFINET IRT networks
Item number 1.01.0320.24110
The Ixxat INpact PIR Slave PCIe is a versatile and efficient solution to connect embedded systems and PCs to PROFINET IRT networks. This preconfigured PROFINET IRT variant features a robust PCIe format and delivers precise, isochronous real-time data exchange, ideal for motion control tasks.
PC interface card for CAN (1 x CAN), galv. isolated
Item number 1.01.0232.12001
The Ixxat CAN-IB100/PCIe is a passive PCI Express interface card with one CAN channel and galvanic isolation, equipped with a low-profile slot bracket. It is an easy and cost-efficient way to connect computers to a CAN bus network. Based on a modular design, the card enables simple integration, supporting various CAN applications.
PC interface card for CAN FD (1 x CAN FD), galv. isolated
Item number 1.01.0237.12010
The Ixxat CAN-IB520/PCIe Mini is a passive PCI Express Mini interface card with one CAN/CAN FD channel, galvanic isolation and a back-entry CAN socket. It is an easy and cost-efficient way to connect computers to a CAN/CAN FD bus network. Thanks to its compact dimensions, the card is especially suitable for applications with limited space.
PC interface card for CAN (1 x CAN), galv. isolated
Item number 1.01.0232.12001
The Ixxat CAN-IB100/PCIe is a passive PCI Express interface card with one CAN channel and galvanic isolation, equipped with a low-profile slot bracket. It is an easy and cost-efficient way to connect computers to a CAN bus network. Based on a modular design, the card enables simple integration, supporting various CAN applications.
Connects computers and embedded systems to industrial EtherCAT networks
Item number 1.01.0320.21110
The Ixxat INpact ECT Slave PCIe is a versatile and efficient solution to connect embedded systems or PCs to EtherCAT networks. This preconfigured EtherCAT variant features a robust PCIe format and is ideally suited for real-time control and automation applications in demanding industrial environments.
Connects computers and embedded systems to PROFINET IRT networks
Item number 1.01.0340.24153
The Ixxat INpact PIR Slave PCIe Mini Bracket Kit is a versatile and efficient solution to connect embedded systems and PCs to PROFINET IRT networks. This preconfigured PROFINET IRT variant features a compact PCIe Mini format and delivers isochronous real-time data exchange, ideal for motion control tasks. The kit includes an Ixxat INpact PCIe Mini, a connection cable, a bus coupling unit and a mini bracket plate.
PC interface card for CAN FD (2 x CAN FD), galv. isolated
Item number 1.01.0239.22010
The Ixxat CAN-IB630/PCIe is an active PCI Express 104 interface card with two CAN/CAN FD channels and galvanic isolation. It is an easy and cost-efficient way to connect computers to a CAN/CAN FD bus network. Based on a modular design, the card enables simple integration into diverse industrial setups, supporting various CAN applications.
PC interface adapter (2 x CAN), galv. isolated
Item number 1.01.0288.22003
The Ixxat USB-to-CAN V2 Plugin with two CAN channels and galvanic isolation enables the simple and fast implementation of CAN interfaces into customer devices. Its compact design and economic pricing make it an ideal choice for space-limited applications and series production.
PC interface adapter (1 x CAN), galv. isolated
Item number 1.01.0281.12002
The Ixxat USB-to-CAN V2 compact with a RJ45 CAN interface and galvanic isolation is an easy and cost-efficient way to connect a computer to a CAN bus network. It enables simple integration into diverse industrial setups, supporting various CAN applications, from testing and development to maintenance and control tasks.
PC interface card for CAN (2 x CAN), galv. isolated
Item number 1.01.0231.22001
The Ixxat CAN-IB100/PCIe is a passive PCI Express interface card with two CAN channels and galvanic isolation. It is an easy and cost-efficient way to connect computers to a CAN bus network. Based on a modular design, the card enables simple integration into diverse industrial setups, supporting various CAN applications.
PC interface card for CAN FD (1 x CAN FD), galv. isolated
Item number 1.01.0233.12010
The Ixxat CAN-IB600/PCIe is an active PCI Express interface card with one CAN/CAN FD channel and galvanic isolation. It is an easy and cost-efficient way to connect computers to a CAN/CAN FD bus network. Based on a modular design, the card enables simple integration into diverse industrial setups, supporting various CAN applications.
Item number 1.01.0352.12001
The Ixxat USB-to-CAN FD embedded is a USB PC interface with one CAN channel. It is designed without a housing and comes with a slot board and adapted USB cable for installation into a computer. It is used to connect PCs and applications with CAN-based networks.
PC interface adapter (2 x CAN FD, LIN), galv. isolated
Item number 1.01.0353.22012
The Ixxat USB-to-CAN FD automotive is an easy, versatile and cost-efficient way to connect computers to fieldbus networks, enabling seamless integration into diverse industrial setups and various CAN applications. It offers two switchable CAN/CAN FD interfaces and one LIN interface, each galvanically isolated.
PC interface adapter (2 x CAN), galv. isolated
Item number 1.01.0288.22003
The Ixxat USB-to-CAN V2 Plugin with two CAN channels and galvanic isolation enables the simple and fast implementation of CAN interfaces into customer devices. Its compact design and economic pricing make it an ideal choice for space-limited applications and series production.
PC interface adapter (2 x CAN, LIN), galv. isolated
Item number 1.01.0283.22042
The Ixxat USB-to-CAN V2 automotive is an easy, versatile and cost-efficient way to connect computers to fieldbus networks, enabling seamless integration into diverse industrial setups and various CAN applications. It offers two switchable CAN interfaces, one of which can be switched to CAN low-speed, and a LIN interface, each galvanically isolated.
All-in-one set with USB-to-CAN interface and useful accessories
Item number 1.03.0283.00001
The Ixxat USB-to-CAN V2 Starter Kit offers a ready-to-go solution for connecting CAN networks to computers, perfect for getting started with CAN applications. This kit includes the USB-to-CAN V2 professional interface, two RJ45 to Sub-D9 adapter cables, a ribbon cable with four D-Sub 9 connectors, two termination resistors, and a gender changer for a quick and easy setup right out of the box.
PC interface adapter (1 x CAN FD), galv. isolated
Item number 1.01.0351.12001
The Ixxat USB-to-CAN FD compact with a D-Sub 9 CAN/CAN FD interface and galvanic isolation is an easy and cost-efficient way to connect a computer to a CAN/CAN FD bus network. It enables simple integration into diverse industrial setups, supporting various CAN applications, from testing and development to maintenance and control tasks.
PC interface adapter (1 x CAN)
Item number 1.01.0281.11001
The Ixxat USB-to-CAN V2 compact with a D-Sub 9 CAN interface is an easy and cost-efficient way to connect a computer to a CAN bus network. It enables simple integration into diverse industrial setups, supporting various CAN applications, from testing and development to maintenance and control tasks.
PC interface adapter (1 x CAN), galv. isolated
Item number 1.01.0282.12001
The Ixxat USB-to-CAN V2 embedded with galvanic isolation is an easy and cost-efficient way to connect a computer with an internal USB connection to a CAN bus network. It enables simple integration into diverse industrial setups, supporting various CAN applications, from testing and development to maintenance and control tasks.
PC interface adapter (1 x CAN), galv. isolated
Item number 1.01.0288.12003
The Ixxat USB-to-CAN V2 Plugin with one CAN channel and galvanic isolation enables the simple and fast implementation of a CAN interface into customer devices. Its compact design and economic pricing make it an ideal choice for space-limited applications and series production.
PC interface adapter (1 x CAN)
Item number 1.01.0288.11003
The Ixxat USB-to-CAN V2 Plugin with one CAN channel enables the simple and fast implementation of a CAN interface into customer devices. Its compact design and economic pricing make it an ideal choice for space-limited applications and series production.
PC interface adapter (2 x CAN), galv. isolated
Item number 1.01.0283.22002
The Ixxat USB-to-CAN V2 professional with two CAN interfaces and galvanic isolation is an easy, versatile and cost-efficient way to connect a computer to CAN bus networks. It enables simple integration into diverse industrial setups, supporting various CAN applications, from testing and development to maintenance and control tasks.
PC interface card for CAN (1 x CAN), galv. isolated
Item number 1.01.0293.12001
The Ixxat CAN-IB400/PCI is an active PCI interface card with one CAN channel and galvanic isolation. It is an easy and cost-efficient way to connect computers to a CAN bus network. Based on a modular design, the card enables simple integration into diverse industrial setups, supporting various CAN applications.
Piggyback module for CAN interface cards
Item number 1.01.0242.22000
The MultiCAN expansion board for the Ixxat CAN-IB series enhances the card’s capabilities by providing two additional high-speed CAN channels. Acting as a piggy-back module, it doubles the number of available high-speed CAN channels on a D-Sub 9 connector and reduces slot requirements, making it ideal for expanding CAN networks efficiently.
PC interface card for CAN (1 x CAN), galv. isolated
Item number 1.01.0231.12001
The Ixxat CAN-IB100/PCIe is a passive PCI Express interface card with one CAN channel and galvanic isolation, equipped with a standard profile slot bracket. It is an easy and cost-efficient way to connect computers to a CAN bus network. Based on a modular design, the card enables simple integration, supporting various CAN applications.
PC interface card for CAN FD (2 x CAN FD), galv. isolated
Item number 1.01.0233.22010
The Ixxat CAN-IB600/PCIe is an active PCI Express interface card with two CAN/CAN FD channels and galvanic isolation. It is an easy and cost-efficient way to connect computers to a CAN/CAN FD bus network. Based on a modular design, the card enables simple integration into diverse industrial setups, supporting various CAN applications.
PC interface adapter (1 x CAN), galv. isolated
Item number 1.01.0281.12001
The Ixxat USB-to-CAN V2 compact with a D-Sub 9 CAN interface and galvanic isolation is an easy and cost-efficient way to connect a computer to a CAN bus network. It enables simple integration into diverse industrial setups, supporting various CAN applications, from testing and development to maintenance and control tasks.
Bandwidth: 100MHz-500MHz
Differential Voltage: Up to 7000Vpk
Accuracy: ±2%
CMRR: >-80dB
Dual-Range Switching
5MHz Bandwidth Limiting
Interface: BNC
The Micsig DP Series High-Voltage Differential Probes offer selectable bandwidths ranging from 100MHz to 500MHz, with a maximum differential input voltage of 7000Vpk.A standard BNC interface ensures compatibility with all major oscilloscope brands. Built-in metal shielding enhances anti-interference performance. With a compact 2cm-thin design, the probes save workspace and feature one-click auto-zero for quick setup. Additional functions include overload protection alarms and power-off memory for seamless operation. A high-impedance input and low input capacitance minimize loading effects, delivering ±2% measurement accuracy and excellent common-mode rejection (CMRR). Ideal for EV power systems, solar inverters, switching power supplies, and floating or isolated high-voltage signal testing.
BNC Interface
Standard BNC interface, work with any oscilloscope.
● Induction heating, induction cooker
● CRT display design
● Low-voltage electrical appliances
● Electronic power and electric drive experiments
Bandwidth：200MHz
Sampling Rate：1GSa/s
Memory Depth：110Mpts
Analog Channels：4
Display：8 inches, 1280*800
Battery：3.7V 16000mAh
Micsig MHO1 series is an ultra-portable professional-grade high-resolution oscilloscope, equipped with a 12-bit high-precision ADC, featuring a bandwidth of up to 200MHz, 4 analog channels, a real-time sampling rate of 1GSa/s, and a storage depth of 110Mpts. These high-performance parameters ensure that every measurement is accurate and provides a solid foundation for in-depth signal analysis. With a body thickness of only 3.1 cm, it can be easily placed in a backpack for efficient testing anytime, anywhere. It is equipped with an 8-inch high-definition anti-glare touch screen with a resolution of up to 1280*800, offering a delicate and clear picture and responsive touch, bringing users an ultimate operating experience.
Bandwidth：500MHz
Sampling Rate：3GSa/s
Memory Depth：360Mpts
Analog Channels：4
Vertical Resolution：12bit
The MO3 series of high-resolution modular oscilloscopes boasts impressive performance, with a chassis thickness of only 3cm. It is not a traditional virtual oscilloscope and can be connected to any display device (including LCD TVs, projectors, etc.) for direct use via an HDMI interface. It can also be connected to a computer via an Ethernet port or SFP+ optical port for remote control and data acquisition and analysis. The MO3 series has an analog bandwidth of up to 500MHz, a sampling rate of 3GSa/s, and a memory depth of 360Mpts, with 4 analog channels. The user-friendly UI design and a rich set of measurement functions offer a completely new user experience.
High Resolution Oscilloscope MHO 3 Series has 500MHz bandwidth, 3GSa/s sampling rate, 4 analog channels, 360Mpts memory depth and 12 bits vertical resolution; 3.58cm ultra-thin body support wall /arm mounting; 14-inch integrated touch screen with resolution of 1920 x 1200 brings unmatched waveform display.
Bandwidth：250MHz-500MHz
Sampling Rate：3GSa/s
Memory Depth：360Mpts
Analog Channels：4
Display：14 inches, 1920*1200
FEATURES:
KEY SPECIFICATIONS:
Bandwidth：350MHz-1GHz
Sampling Rate：6GSa/s
Memory Depth：1800Mpts
Analog Channels：8
Display：16 inches, 1920*1200
The MHO high-resolution oscilloscope 6 series features a 1GHz bandwidth, 6GSa/s sampling rate, 8 analog channels, a storage depth of 1800 million points (Mpts), and a 12-bit vertical resolution. Its high bandwidth and 8-channel capability are suitable for faster circuit analysis and more synchronized signal testing. Its ultra-thin design of 3.52 cm can save a lot of your precious desk space; a 16-inch touch screen with a resolution of 1920*1200 provides you with a super clear waveform display for a more comfortable visual experience.
FEATURES:
Bandwidth：200MHz
Sampling Rate：1GSa/s
Memory Depth：50Mpts
Analog Channels：4
Bandwidth：100MHz-200MHz
Sampling Rate：1GSa/s
Memory Depth：70Mpts
Analog Channels：2/4
Display：8 inches, 800*600
The SATO Series Automotive Diagnostic Oscilloscope is a specialized oscilloscope designed for automotive maintenance and diagnostics. It features a variety of professional functions tailored for automotive diagnostics, an 8-inch 800*600 resolution high-definition screen, a built-in lithium battery with a runtime of over five hours, and 2/4 channel options with a maximum bandwidth of 200MHz and a sampling rate of 1GSa/s. The storage depth reaches up to 70Mpts. Equipped with an integrated automotive software package, it allows for one-click setup of various test projects, ensuring a worry-free diagnostic and measurement experience for your automotive work.
The ATO series automotive diagnostic oscilloscope is a specialized tool designed for automotive maintenance and diagnostics. It comes equipped with a variety of professional automotive diagnostic functions, a 10.1-inch large high-definition screen, and a built-in lithium battery with a duration of over five hours. The oscilloscope features 2/4 channel options, a maximum bandwidth of 300MHz, a maximum sampling rate of 2GSa/s, and a maximum memory depth of 220Mpts. It is powered by the SigtestUI™ multitasking system, which offers a user interface designed specifically for test instruments, allowing for operation as intuitive as using a smartphone, thereby making automotive diagnostics much easier.
Bandwidth：100MHz-300MHz
Sampling Rate：2GSa/s
Memory Depth：220Mpts
Analog Channels：2/4
Display：10.1 inches, 1280*800
Micsig SigOFIT MOIP Series
Offers bandwidths from 100 MHz to 1 GHz with common-mode rejection ratios up to 180 dB. Differential voltage ranges from ±25V to ±6250V, depending on the attenuation tip. Ideal for power device evaluation, EMI troubleshooting, and high-voltage applications.
An optical-fiber isolated probe is a specialized sensor that uses optical fiber technology to provide electrical isolation between the probe and the measurement system. Here’s a breakdown of its use and purpose:
🔌 Main Purpose: Electrical Isolation
📡 How It Works
🛠️ Common Applications
Bandwidth：100MHz-1GHz
Common Mode Voltage：85kVpk
DC Accuracy：1%
CMRR：up to 180dB
Interface: BNC
* Design of motor drive, power converter, electronic ballast
* Design of GaN, SiC, IGBT Half/Full bridge devices
* Design of inverter, UPS and switching power supply
* Safety test for high voltage, high bandwidth applications
* Power device evaluation
* Current shunt measurements
* EMI & ESD troubleshooting
* Floating measurements
Key Specifications
| Model* | MOIP100P | MOIP200P | MOIP350P | MOIP500P | MOIP800P | MOIP1000P |
|---|---|---|---|---|---|---|
| Bandwidth | 100MHz | 200MHz | 350MHz | 500MHz | 800MHz | 1GHz |
| Rise Time | ≤3.5ns | ≤1.75ns | ≤1ns | ≤700ps | ≤438ps | ≤350ps |
| CMRR | DC: 180dB 100MHz: 128dB | DC: 180dB 200MHz: 122dB | DC: 180dB 350MHz: 118dB | DC: 180dB 500MHz: 114dB | DC: 180dB 800MHz: 110dB | DC: 180dB 1GHz: 108dB |
| Differential Voltage Range | Standard OP20(MMCX), ±25V Optional OP50(MMCX), ±62.5V Optional OP200(MCX), ±250V Optional OP1000(MCX), ±1250V Optional OP2000(MCX), ±2500V Optional OP5000(LCX), ±6250V | Standard OP20(MMCX), ±25V Optional OP50(MMCX), ±62.5V Optional OP200(MCX), ±250V Standard OP1000(MCX), ±1250V Optional OP2000(MCX), ±2500V Optional OP5000(LCX), ±6250V | Optional OP20(MMCX), ±10V Standard OP50(MMCX), ±25V Optional OP100(MMCX), ±50V Standard OP2000(MCX), ±1000V Optional OP5000(MCX), ±2500V Optional OP10000(LCX), ±5000V | |||
| Noise | <0.45mVrms | |||||
| DC Gain Accuracy | 1% | |||||
| Common Mode Voltage Range | 85kVpk | |||||
| Interface | Universal BNC | |||||
* Note: Current model names updated on March 20, 2024, previous model names referred as MOIP01P, and OIP100 (e.g. 100MHz bandwidth).
* Design of motor drive, power converter, electronic ballast
* Design of GaN, SiC, IGBT Half/Full bridge devices
* Design of inverter, UPS and switching power supply
* Safety test for high voltage, high bandwidth applications
* Power device evaluation
* Current shunt measurements
* EMI & ESD troubleshooting
* Floating measurements
Key Specifications
| Model* | MOIP100P | MOIP200P | MOIP350P | MOIP500P | MOIP800P | MOIP1000P |
|---|---|---|---|---|---|---|
| Bandwidth | 100MHz | 200MHz | 350MHz | 500MHz | 800MHz | 1GHz |
| Rise Time | ≤3.5ns | ≤1.75ns | ≤1ns | ≤700ps | ≤438ps | ≤350ps |
| CMRR | DC: 180dB 100MHz: 128dB | DC: 180dB 200MHz: 122dB | DC: 180dB 350MHz: 118dB | DC: 180dB 500MHz: 114dB | DC: 180dB 800MHz: 110dB | DC: 180dB 1GHz: 108dB |
| Differential Voltage Range | Standard OP20(MMCX), ±25V Optional OP50(MMCX), ±62.5V Optional OP200(MCX), ±250V Optional OP1000(MCX), ±1250V Optional OP2000(MCX), ±2500V Optional OP5000(LCX), ±6250V | Standard OP20(MMCX), ±25V Optional OP50(MMCX), ±62.5V Optional OP200(MCX), ±250V Standard OP1000(MCX), ±1250V Optional OP2000(MCX), ±2500V Optional OP5000(LCX), ±6250V | Optional OP20(MMCX), ±10V Standard OP50(MMCX), ±25V Optional OP100(MMCX), ±50V Standard OP2000(MCX), ±1000V Optional OP5000(MCX), ±2500V Optional OP10000(LCX), ±5000V | |||
| Noise | <0.45mVrms | |||||
| DC Gain Accuracy | 1% | |||||
| Common Mode Voltage Range | 85kVpk | |||||
| Interface | Universal BNC | |||||
* Note: Current model names updated on March 20, 2024, previous model names referred as MOIP01P, and OIP100 (e.g. 100MHz bandwidth).
The OBD2 DBC file contains conversion rules for decoding raw OBD2 data to human-readable form (km/h, %, …).
DBC is the standard CAN database format used in most CAN tools – incl. our CANedge software/APIs.
This OBD2 DBC contains ~150 of the standard Mode 01 PIDs – and you can easily extend it with e.g. proprietary PIDs.
The database is 100% free and can be used natively with the CANedge series through the asammdf GUI/API.
The OBD2 protocol is used across practically all passenger cars today. Because OBD2 is standardized, you can use the OBD2 DBC file to decode OBD2 PID data across different car brands/models/years OBD2 data logging and telematics.
For basics on OBD2 data logging, see our OBD2 telematics intro.
The SAE J1939 DBC file contains decoding rules for converting raw J1939 data to ‘physical values’ (km/h, %, …). This lets you easily decode data from heavy duty vehicles (trucks, buses, tractors, …).
DBC is a CAN database format used in most automotive tools – incl. our CAN software/APIs.
The download includes a legal J1939 DBC & license, based on the J1939 Digital Annex Excel file (also included). We offer this in collaboration with SAE. For company-wide quotes, contact us.
The DBC revision is 2024-12.
Tip: Contact us for a free ‘sample conversion’ of a CLX000/CANedge log file.
New: Check out the 4 min intro video.
| GENERAL | |
|---|---|
| Standard(s) | J1939 Digital Annex – corresponds mainly to J1939-71 |
| #PGNs | 1800+ |
| #SPNS | 12000+ |
| Multipacket | Multipacket syntax is used for the multipacket PGNs included in the DBC |
| Multiplex | Some multiplexed messages are included, but with “regular” syntax (not multiplex) |
| Descriptions | Partial SPN descriptions included in DBC (full included in Digital Annex) |
| Attributes | SPN ID, VFrameFormat |
| Value tables | Not included |
| Network nodes | Not included |
The plug & play 2x CAN/LIN logger records timestamped CAN data (Classical/CAN FD) to the extractable 8 GB industrial SD card.
The compact device uses 3G/4G to securely push data to your own server – with OTA update support.
The device includes GNSS/IMU, adding data like position, speed, attitude, acceleration and more.
Ideal for telematics, R&D field tests, diagnostics and predictive maintenance.
Software/APIs are 100% free & open source – with no subscription fees or vendor lock-in.
Incl. antennas and optional ‘Super SIM’.
| GENERAL | |
|---|---|
| Functionality | Standalone CAN bus data logger with SD card, 2xCAN/LIN channels, 3G/4G LTE 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 CANcloud telematics platform for managing devices & data via your browser | |
| Multiple tools for mounting your S3 server as a local drive for easy access | |
| Free open source asammdf software & API for editing, DBC converting & plotting MF4 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-RED, FCC, IC, RoHS (see Docs), RCM (Australia), ICASA (South Africa) |
| Tested for voltage transients (emissions/immunity), ISO 7637-2:2011, by TUV SUD (see the Docs) | |
| 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 5 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 i |
| 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) |
| The RTC can be configured to match local time zones (default: UTC) | |
| The RTC can be auto-synced via 3G/4G LTE or 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 compression (~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 | 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 (incl. integrity check) |
| 3G/4G LTE | |
| SIM Slot | SIM card slot for external micro SIM cards (mid size) |
| SIM Card | Use your own SIM card or activate the ‘Super SIM’ that ships with the device (with 90% discounted rates) |
| Note: Verizon SIM cards are not supported | |
| 3G/4G LTE Module | Professional-grade u-blox LARA-R6001D LTE Cat1 |
| Coverage | Global |
| Frequency (Bands) | 4G LTE FDD bands: 1, 2, 3, 4, 5, 7, 8, 12, 13, 18, 19, 20, 26, 28 |
| 4G LTE TDD bands: 38, 39, 40, 41 | |
| 3G bands: 1, 2, 5, 8 | |
| Frequency (MHz) | 4G LTE FDD: 700, 800, 850, 900, 1700, 1800, 1900, 2100, 2600 |
| 4G LTE TDD: 1900, 2300, 2600 | |
| 3G: 850, 900, 1900, 2100 | |
| Certifications | CANedge3: PTCRB (antenna >20 cm from device), AT&T |
| Protocol | HTTP/HTTPS: Stable and secure transfers – ideal for big data telematics |
| Over-The-Air (OTA) | Configuration & firmware over-the-air (COTA/FOTA). Configurable sync rate. Optionally disable |
| Heartbeat | If enabled, the CANedge3 periodically “checks-in” by uploading a small device status file |
| Data Upload State | Optionally disable/enable upload of log files (e.g. via over-the-air configuration) |
| Antenna | External (SMA). Can be extended or replaced by e.g. a 2-in-1 antenna (3G/4G LTE + GNSS) |
| S3 Server Interface | Upload data to your own cloud server (e.g. Amazon, Google, Azure) or self-hosted server (e.g. MinIO) |
| 3G/4G LTE SECURITY | |
| HTTPS | Data & over-the-air updates can be sent via HTTPS (TLS 1.2) for secure transfer to server |
| Credential Encryption | S3 server credentials can be encrypted in the config on the device SD card |
| Signed Firmware | Firmware updates are digitally signed to verify that they are from a trusted source |
| User Policies | Fully customize access rights across CANedge devices and end users through S3 policies |
| 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 start: ~30-120 seconds from device boot |
| 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: 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. from the vehicle/machine power supply) |
| Power Consumption | Very low (~1 W in normal operation, ~2.5 W during 3G/4G transfer) – 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 & antenna connector). 100 grams |
| Antennas | 3G/4G LTE antenna and 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 6 external LEDs: Power, CH1, CH2, Memory, LTE, GNSS |
| Temperature | Operating temperature (parts): -25degC to +70degC |
| IP Rating | IP Rating 40 |
The plug & play 2x CAN/LIN logger records timestamped CAN data (Classical/CAN FD) to the extractable 8 GB industrial SD card.
The compact device connects via WiFi access points to securely push data to your own server – with support for over-the-air updates.
The device includes GNSS/IMU, adding data like position, speed, attitude, acceleration and more.
Ideal for telematics, R&D field tests, diagnostics and predictive maintenance.
Software/APIs are free & open source – with no subscription fees or vendor lock-in.
Tip: See also the CANedge3 with 3G/4G.
Price includes GPS antenna.
| GENERAL | |
|---|---|
| Functionality | Standalone CAN bus data logger with SD card, 2xCAN/LIN channels, WiFi 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 CANcloud telematics platform for managing devices & data via your browser | |
| Multiple tools for mounting your S3 server as a local drive for easy access | |
| Free open source asammdf software & API for editing, DBC converting & plotting MF4 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-RED, FCC, IC, RoHS (see Docs), WPC ETA (India), RCM (Australia), ICASA (South Africa) |
| For Korea/Japan, a certified ‘PB’ variant with internal WiFi antenna is used (KC, GITEKI) | |
| Tested for voltage transients (emissions/immunity), ISO 7637-2:2011, by TUV SUD (see the Docs) | |
| Variant certified for South Korea, Japan & more is available on-request (contact us) | |
| 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 5 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 i |
| 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) |
| The RTC can be configured to match local time zones (default: UTC) | |
| The RTC can be auto-synced via WiFi or 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 compression (~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 | 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 (incl. integrity check) |
| WIFI | |
| Transfer Modes | Station mode: Connects to a WiFi access point to transfer data |
| Protocol | HTTP/HTTPS: Stable and secure transfers – ideal for big data telematics |
| Access Points | Add 1-4 WiFi access points. Prioritized order. Condition on signal strength |
| Over-The-Air (OTA) | Configuration & firmware over-the-air (COTA/FOTA). Configurable sync rate. Optionally disable |
| WiFi Heartbeat | If enabled, the CANedge2 periodically “checks-in” to your server by uploading a small device status file |
| Data Upload State | Optionally disable/enable upload of log files (e.g. via over-the-air configuration) |
| Range | Strong range via external WiFi antenna |
| LAN Standard | IEEE 802.11 b / g / n |
| Frequency | 2.412-2.472 GHz (power output of 18.5dBm, 802.11b 11Mbps) |
| Antenna | External (SMA, <2 dBi gain). Can be extended or replaced by e.g. a WiFi rooftop antenna |
| S3 Server Interface | Upload data to your own cloud server (e.g. Amazon, Google, Azure) or self-hosted server (e.g. MinIO) |
| Web Server Interface | Pull data from SD via WiFi (through browser web page or REST API) – no server required |
| WIFI SECURITY | |
| HTTPS | Data & over-the-air updates can be sent via HTTPS (TLS 1.2) for secure transfer to server |
| WPA/WPA2 | Supports WPA/WPA2 |
| Credential Encryption | WiFi access point & S3 server credentials can be encrypted in the config on the device SD card |
| Signed Firmware | Firmware updates are digitally signed to verify that they are from a trusted source |
| User Policies | Fully customize access rights across CANedge devices and end users through S3 policies |
| 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: 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. from the vehicle/machine power supply) |
| 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 & antenna connector). 100 grams |
| Antennas | WiFi antenna and 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 6 external LEDs: Power, CH1, CH2, Memory, WiFi, GNSS |
| Temperature | Operating temperature (parts): -25degC to +70degC |
| IP Rating | IP Rating 40 |
The plug & play 2x CAN/LIN logger records timestamped CAN data (Classical/CAN FD) to the extractable 8 GB industrial SD card.
The compact device connects via WiFi access points to securely push data to your own server – with support for over-the-air updates.
Ideal for telematics, R&D field tests, diagnostics and predictive maintenance.
Software/APIs are free & open source – with no subscription fees or vendor lock-in.
See also the CANedge2 incl. GPS/IMU or CANedge3 with 3G/4G.
| GENERAL | |
|---|---|
| Functionality | Standalone CAN bus data logger with SD card, 2xCAN/LIN channels (incl. CAN FD) and WiFi |
| 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 CANcloud telematics platform for managing devices & data via your browser | |
| Multiple tools for mounting your S3 server as a local drive for easy access | |
| Free open source asammdf software & API for editing, DBC converting & plotting MF4 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-RED, FCC, IC, RoHS (see Docs), WPC ETA (India), RCM (Australia), ICASA (South Africa) |
| For Korea/Japan, a certified ‘PB’ variant with internal WiFi antenna is used (KC, GITEKI) | |
| Tested for voltage transients (emissions/immunity), ISO 7637-2:2011, by TUV SUD (see the Docs) | |
| Variant certified for South Korea, Japan & more is available on-request (contact us) | |
| 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 5 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 i |
| 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) |
| The RTC can be configured to match local time zones (default: UTC) | |
| The RTC can be auto-synced via WiFi or a CAN message (e.g. from a precise 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 compression (~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 | 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 (incl. integrity check) |
| WIFI | |
| Transfer Modes | Station mode: Connects to a WiFi access point to transfer data |
| Protocol | HTTP/HTTPS: Stable and secure transfers – ideal for big data telematics |
| Access Points | Add 1-4 WiFi access points. Prioritized order. Condition on signal strength |
| Over-The-Air (OTA) | Configuration & firmware over-the-air (COTA/FOTA). Configurable sync rate. Optionally disable |
| WiFi Heartbeat | If enabled, the CANedge2 periodically “checks-in” to your server by uploading a small device status file |
| Data Upload State | Optionally disable/enable upload of log files (e.g. via over-the-air configuration) |
| Range | Strong range via external WiFi antenna |
| LAN Standard | IEEE 802.11 b / g / n |
| Frequency | 2.412-2.472 GHz (power output of 18.5dBm, 802.11b 11Mbps) |
| Antenna | External (SMA, <2 dBi gain). Can be extended or replaced by e.g. a WiFi rooftop antenna |
| S3 Server Interface | Upload data to your own cloud server (e.g. Amazon, Google, Azure) or self-hosted server (e.g. MinIO) |
| Web Server Interface | Pull data from SD via WiFi (through browser web page or REST API) – no server required |
| WIFI SECURITY | |
| HTTPS | Data & over-the-air updates can be sent via HTTPS (TLS 1.2) for secure transfer to server |
| WPA/WPA2 | Supports WPA/WPA2 |
| Credential Encryption | WiFi access point & S3 server credentials can be encrypted in the config on the device SD card |
| Signed Firmware | Firmware updates are digitally signed to verify that they are from a trusted source |
| User Policies | Fully customize access rights across CANedge devices and end users through S3 policies |
| 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 & antenna connector). 100 grams |
| Antennas | WiFi 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 5 external LEDs: Power, CH1, CH2, Memory, WiFi |
| Temperature | Operating temperature (parts): -25degC to +70degC |
| IP Rating | IP Rating 40 |
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.
Price includes GPS antenna.
See also CANedge options with WiFi or 3G/4G.
| 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-RED, FCC, IC, KC and RoHS certified (see the Docs) |
| Tested for voltage transients (emissions/immunity), ISO 7637-2:2011, by TUV SUD (see the Docs) | |
| 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 5 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 i |
| 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) |
| The RTC can be configured to match local time zones (default: UTC) | |
| The 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: 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 |
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.
Ideal for recording CAN/LIN data over weeks, months or years – e.g. for diagnostics, OEM development or legal/warranty purposes.
See also CANedge options with GPS/IMU, WiFi and 3G/4G.
| GENERAL | |
|---|---|
| Functionality | Standalone CAN bus data logger with SD card and 2xCAN/LIN channels (incl. CAN FD) |
| 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 Docs) |
| Tested for voltage transients (emissions/immunity), ISO 7637-2:2011, by TUV SUD (see the Docs) | |
| 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 5 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 i |
| 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) |
| The RTC can be configured to match local time zones (default: UTC) | |
| The RTC can be auto-synced via a CAN message (e.g. from a precise 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 |
| 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 |
| 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 |
The plug & play CL2000 CAN logger records CAN bus data to an 8 GB SD card and timestamps it with a real-time clock.
Further, the CL2000 can operate as a CAN bus interface for real-time USB streaming.
The CAN logger is ideal for vehicle fleet management (trucks, buses, harvesters, cars, …), prototype field testing, diagnostics or reverse engineering.
Buy now – or read more below!
| GENERAL | |
|---|---|
| Functionality | Data logger and real-time CAN interface |
| LEDs | Logger status via three externally visible LEDs |
| Firmware | Supports free firmware updates for adding features |
| Software | Free executables for conversion to ASC/TRC [Windows/Linux] |
| Free open source SavvyCAN software for streaming/analyzing CAN data + DBC decoding [Windows/Linux] | |
| The .INI config / .TXT log files can also simply be opened in text editors or scripts [Windows/Linux] | |
| Safety | CE, FCC, IC, RoHS certified |
| CAN BUS | |
| Standard | Compliant with physical layer standard ISO 11898-2 |
| Identifiers | Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID) |
| Bit Rate | Bit rates up to 1 Mbps (manually configured or automatically detected) |
| Bit-rate auto-detection | Yes |
| Protocol Support | Protocol independent (i.e. able to log CAN, J1939, CANopen, OBD2, …) |
| Filters | Advanced message filtering on four configurable channels |
| Silent Mode | Yes (does not affect CAN-bus transmission) |
| Fail-Safes | The device does not terminate the CAN-bus internally |
| DATA LOGGING | |
| SD Card | Replaceable 8 GB SD card (optional 32 GB) |
| Real-Time Clock | Yes (CAN messages are time-stamped with 1ms resolution) |
| Control Signal | Logging state (enabled/disabled) can be changed run-time using a CAN-bus control message |
| Heartbeat Signal | Supports heartbeat signal to periodically indicate logger status |
| Cyclic Logging | Supports cyclic logging mode (oldest log file is deleted when file system is full) |
| Down Sampling | CAN ID specific message down-sampling to reduce frequency of logged messages |
| Transmit | Transmit up to 20 customized CAN bus messages (e.g. for OBD2). Full real-time transmit control via USB |
| File System | Standard FAT file system |
| Frames/Second | The CL2000 can log/stream ~800-1000 frames/sec without loss. For higher busloads, see the CANedge |
| SUPPLY | |
| Power via CAN connector | Power can be supplied from the DB9 CAN connector (log/stream) or via USB (data extraction) |
| Via CAN connector (DB9) | Power supplied by the CAN bus (+7.0V to +32V DC) |
| Protection | Reverse voltage protection on CAN-bus supply |
| Transient voltage pulse protection on CAN-bus supply | |
| Power via USB | Power supplied by USB (+5.0V DC) for data extraction/configuration |
| Consumption | The logger’s power consumption is approximately 1 W |
| MECHANICAL | |
| Enclosure | Robust, small enclosure |
| Dimensions | 66.7 x 42.7 x 23.5 mm (L x W x H) |
| Weight | 45 grams |
| Connector | Standard D-sub 9 (DB9) connector (OBD2, J1939, “generic” adaptor optional) |
| USB | Standard mini USB (B) connector for extracting data & streaming (cable not included) |
| Temperature | Operating temperature: -20degC to +65degC |
| Real-Time Clock | Built-in real-time-clock with calendar and battery backup |
| Date and time information are added to log files | |
| Battery backup with more than two years of battery capacity | |
| IP Rating | IP Rating 40 |
The plug & play CL1000 CAN logger records CAN bus data to an 8 GB SD card. The logger is 100% standalone (no PC required) and data is easily extracted via USB.
The CL1000 is ideal for vehicle development and field testing (cars, heavy duty & more).
Further, the CL1000 doubles as a powerful reverse engineering tool with live-streaming via USB in SavvyCAN or Python.
| GENERAL | |
|---|---|
| Functionality | Data logger and real-time CAN interface (live send/receive) |
| LEDs | Logger status via three externally visible LEDs |
| Firmware | Supports free firmware updates for adding features |
| Software | Free executables for conversion to ASC/TRC [Windows/Linux] |
| Free open source SavvyCAN software for streaming/analyzing CAN data + DBC decoding [Windows/Linux] | |
| The .INI config / .TXT log files can also simply be opened in text editors or scripts [Windows/Linux] | |
| Safety | CE, FCC, IC, RoHS certified |
| CAN BUS | |
| Standard | Compliant with physical layer standard ISO 11898-2 |
| Identifiers | Compliant with CAN specifications 2.0A (11-Bit ID) and 2.0B (29-Bit ID) |
| Bit Rate | Bit rates up to 1 Mbps (manually configured or automatically detected) |
| Bit-rate auto-detection | Yes |
| Protocol Support | Protocol independent (i.e. able to log CAN, J1939, CANopen, OBD2, …) |
| Filters | Advanced message filtering on eight configurable channels |
| Silent Mode | Yes (does not affect CAN-bus transmission) |
| Fail-Safes | The device does not terminate the CAN-bus internally |
| DATA LOGGING | |
| SD Card | Replaceable 8 GB SD card (optional 32 GB) |
| Real-Time Clock | No (see instead the CL2000 or CANedge) |
| Control Signal | Logging state (enabled/disabled) can be changed run-time using a CAN-bus control message |
| Heartbeat Signal | Supports heartbeat signal to periodically indicate logger status |
| Cyclic Logging | Supports cyclic logging mode (oldest log file is deleted when file system is full) |
| Down Sampling | CAN ID specific message down-sampling to reduce frequency of logged messages |
| Transmit | Transmit up to 20 customized CAN bus messages (e.g. for OBD2). Full real-time transmit control via USB |
| File System | Standard FAT file system |
| Frames/Second | The CL1000 can log/stream ~800-1000 frames/sec without loss. For higher busloads, see the CANedge |
| SUPPLY | |
| Power via CAN connector | Power can be supplied from the DB9 CAN connector (log/stream) or via USB (data extraction) |
| Via CAN connector (DB9) | Power supplied by the CAN bus (+7.0V to +32V DC) using pin 9 (supply) and 3 (ground) |
| Protection | Reverse voltage protection on CAN-bus supply |
| Transient voltage pulse protection on CAN-bus supply | |
| Power via USB | Power supplied by USB (+5.0V DC) for data extraction/configuration |
| Consumption | The logger’s power consumption is approximately 1 W |
| MECHANICAL | |
| Enclosure | Robust, small enclosure |
| Dimensions | 66.7 x 42.7 x 23.5 mm (L x W x H) |
| Weight | 45 grams |
| Connector | Standard D-sub 9 (DB9) connector (OBD2, J1939, “generic” adaptor optional) |
| USB | Standard mini USB (B) connector for extracting data & streaming (cable not included) |
| Temperature | Operating temperature: -20degC to +65degC |
| IP Rating | IP Rating 40 |
eSPI Electrical Validation and Protocol Decode Software offers electrical measurements compliance testing and protocol decoding as specified in eSPI specification. PGY-eSPI Electrical validation and Protocol decode software runs in Tektronix Oscilloscope and provides electrical measurements and protocol decode at the click of a button. This allows engineers quickly check for eSPI compliance and flexibility to debug the failure. In addition to this engineer can decode the command and response of eSPI to debug the communication. PGY-eSPI takes advantage of digital channels of MSO and provides the decoding of eSPI data lines.
HDMI Protocol Decode Software offers protocol decoding as specified in the HDMI specification. PGY-HDMI Protocol decode software runs in Tektronix Oscilloscope and provides measurements for protocol decode at the click of a button. This allows engineers to quickly check for HDMI compliance and flexibility to debug the failure. In addition to this, engineers can decode the command and response of HDMI to debug the communication. PGY-HDMI takes advantage of digital channels of MSO and provides the decoding of HDMI data lines.
PGY-PCIe is a PCIe Protocol Decode software that runs inside Tektronix oscilloscope which has windows OS and easily decodes the PCIe Waveforms acquired by the oscilloscope. This reduces the debug and test time for design and test engineers while debugging link bring up challenges in PCIe interface.
RFFE Protocol Decode Software offers protocol decoding as specified in the RFFE specification. PGY-RFFE Protocol decode software runs in Tektronix Oscilloscope and provides measurements for protocol decode at the click of a button. This allows engineers to quickly check for RFFE compliance and flexibility to debug the failure. In addition to this, engineers can decode the command and response of RFFE to debug the communication. PGY-RFFE takes advantage of digital channels of MSO and provides the decoding of RFFE data lines.
I3C Protocol Decode Software offers protocol decoding as specified in the I3C specification. PGY-I3C-PD Protocol decode software runs in Tektronix Oscilloscope and provides protocol decode at the click of a button. This allows engineers quickly check for I3C compliance and flexibility to debug the failure. In addition to this engineers can decode the command and response of I3C to debug the communication. PGY-I3C-PD takes advantage of digital channels of MSO and provides the decoding of I3C data lines.
