AutoPi Cloud // CAN Bus Management Platform # Log. Decode. Deliver. CAN Bus data to cloud. AutoPi Cloud manages compatible CAN Bus and CAN-FD data loggers. Configure channels, loggers, DBC decoders, filters and frame listeners, and send data to AWS S3, local disk or an integrated downstream system. Capabilities depend on hardware and software: TMU CM4 requires the CAN-FD variant for CAN-FD networks. Capture rate depends on configuration; see the device datasheet. CAN 2.0 CAN-FD J1939 OBD-II UDS MDF4 BLF JSONL ASC CSV **AutoPi Cloud is included with every AutoPi device.** Whether you choose Mini, TMU CM4 or CAN-FD Pro, your device comes with our cloud solution. Mini includes a required subscription; TMU CM4 is available with or without a subscription; CAN-FD Pro includes Cloud and device software at no extra cost, with SIM and mobile data purchased separately. Planning a standalone or enterprise deployment? [Let's discuss your project](https://www.autopi.io/sales-inquiry/). Explore configuration options and current pricing in the shop. Starting prices exclude taxes, shipping and accessories. [Request a proposal](https://www.autopi.io/sales-inquiry/) [Download Flyer](https://d1ihv1nrlgx8nr.cloudfront.net/static/pdf/autopi_cloud_flyer.pdf) autopi@can-fd-pro ~ logger.status $ autopi logger.status channels: can0: interface: bitrate: 500000 autodetect: any_passive / success loggers: raw: current_fps: 584.95 received_frames: 111101 decoders: type: STANDARD decoded_msgs: 140000 s3_output: uploaded_files: 2 destination: s3://fleet-data/.../can0 can1: bitrate: 500000 current_fps: 586.66 disks: /: free_space: 3 GB housekeeper: active _ can0 live · 585 fps S3 synced · 2 files DBC · 140k msgs Interface CAN 2.0 & CAN-FD 2× channels · up to 5 Mbps Protocols J1939 / OBD-II / UDS PGN, PID & raw queries Frame IDs 11-bit + 29-bit Standard & extended identifiers Output formats MDF4 · BLF · ASC + CSV · JSONL · LOG Decoding DBC Standard + ASAM Per-signal selection, Frame ID Mask Remote access Tailscale · SSH · OTA WireGuard mesh, no port forwarding // integrations & toolchain ## Fits your existing automotive data stack Output formats and integration methods designed for the tools engineers already use. ASAM / MDF4 ### ASAM MDF4 binary output The ASAM decoder writes industry-standard MDF4 files - the format used across automotive OEMs and Tier 1s for storing measurement data. Load directly into post-processing tools without conversion. Vector tools ### BLF + ASC for CANalyzer / CANape Raw output in Vector Binary Logging Format (BLF) and ASCII (ASC) - both natively supported by CANalyzer, CANape, CANoe, and most CANdb++ workflows. No format conversion step required. AWS S3 ### Direct upload to S3 buckets Configure access key, secret, destination path, sync interval, and retry policy per logger. Both raw and decoded data upload independently to separate paths - raw for archival, decoded for analytics. Tailscale / SSH ### Remote device access via WireGuard mesh Tailscale enrollment gives SSH access over a private IP with no port forwarding or public inbound rules. Inspect SocketCAN interfaces, check logger state, and pull local files from anywhere on the mesh. Workflow hooks ### Python-based edge logic Custom handlers, converters, triggers, filters, enrichers, and returners - all Python, all running on-device. Frame listeners react to specific CAN frames and execute any workflow: burst logging, webhook push, or state change. // get started ### Free with the CAN-FD Pro AutoPi Cloud is 100% free with every CAN-FD Pro device - no limits, no subscription required. Start logging immediately on any number of devices. [Contact Us](https://www.autopi.io/sales-inquiry/) [Read the docs →](https://docs.autopi.io/getting_started/autopi_canfd_pro/pro-user-guide/) // recommended device ## The AutoPi CAN-FD Pro - purpose-built for high-speed CAN Bus logging Built on the Raspberry Pi Compute Module 4, the CAN-FD Pro runs the open-source AutoPi Core OS. Two dedicated CAN-FD interfaces up to 5 Mbps, 4G/LTE global connectivity, 32 GB local storage, and direct SSH/Tailscale access for remote diagnostics and programming. 2× CAN-FD · 5 Mbps BCM2711 Quad A72 1.5 GHz 4 GB LPDDR4 · 32 GB eMMC 4G LTE Cat 4 · GPS/GNSS 12 – 35 V DC (cars + trucks) Open source AutoPi Core OS Comes with 4-in-1 external antenna for 2x 4G/LTE, 1x GPS and 1x WiFi/BLE. More memory and more storage with options for external storage. Shipped with our latest AutoPi Core OS, designed for high speed data logging. **AutoPi Cloud and device software are included with your CAN-FD Pro.** Hardware starts at €599. SIM and mobile data are purchased separately. Explore configuration options and current pricing in the shop. Starting prices exclude taxes, shipping and accessories. [Order Now](https://shop.autopi.io/products/autopi-can-fd-pro) [Contact Us →] In stock | Order now -> Ships tomorrow. ###### Processor Broadcom BCM2711 Quad-core Cortex-A72 (ARM v8) 64-bit SoC @ 1.5GHz (RPi CM4) ###### Memory 4GB LPDDR4 SDRAM ###### Storage 32GB on board eMMC (expandable with USB flash drive) ###### Modem Integrated 4G/LTE Cat 4 connection (3G/EDGE fallback) (150Mbit DL / 50Mbit UL) (Global connectivity in a single device) ###### Secure Element Sign and encrypt data ###### GPS/GNSS Integrated GPS + A-GPS (GPS/GLONASS/BeiDou/Galileo/QZSS) ###### Power Line Voltage: 12.5V DC (Car battery power). Up to 35V (Trucks). Support for trucks with up to 35V ###### Expansion 2 x USB, Gigabit Ethernet and HAT ###### Wireless Bluetooth: Bluetooth 5.0 + Bluetooth Low Energy (BLE) WiFi: 2.4GHz and 5GHz IEEE 802.11.b/g/n/ac wireless LAN ###### Accelerometer 3-Axis accelerometer ###### Gyroscope Built in 3-axis gyroscope ###### Automotive Interface 2X CAN-FD interface with up to 5Mbps Data rate with integrated CAN data filters ###### Input Slots SIM Card: Nano SIM - (SIM subscription purchased separately) ###### Audio Built-in speakers ###### Video Out mini HDMI @ 1080p60 Video Output ###### Operating System Raspbian OS with preconfigured AutoPi Core software // can logging features ## 8 layers of control over your CAN data From raw capture to decoded signal export - configure every parameter remotely, per device, per channel. CAN Bus Data Management - - - - - - - - CAN Bus Data Management ##### CAN Bus loggers Loggers define the full data flow on the CAN-FD Pro, what is captured, how it is buffered, and where it ends up. The platform supports multiple loggers on the same device, which is practical in real projects. One logger can run as a full raw recorder for debugging, another can export only selected signals for reporting or monitoring. The two built-in CAN-FD channels can be configured independently, including bit rates, payload handling, and direction. Logger configuration typically includes output format, rotation rules, storage targets, and upload behavior. When cellular conditions vary, buffering and retry logic matters. A logger that uploads data continuously can keep working across temporary dropouts, while local capture continues on internal storage. The CAN-FD Pro is designed to be interoperable with external CAN interfaces. A common extension is a CAN-to-USB interface connected to the USB port, used to add additional channels or to monitor a separate network behind a gateway. In practice, additional networks often show up late in a program, for example a body network, a powertrain segment, or an equipment bus on machinery. ##### DBC files DBC files can be uploaded to the CAN-FD Pro through AutoPi Cloud CAN Bus Management and assigned per channel or per logger. The interface supports selecting specific messages and signals for decoding. This selection step matters because DBCs often contain far more than the signals that are needed for a given test program. DBC-based signal selection can also be used as an input to filtering. Instead of filtering on raw frame IDs only, pass filters can be derived from the chosen signals. This reduces bandwidth usage on 4G/LTE uploads and avoids exporting large quantities of unrelated traffic. DBC files, CAN database files, describe how to interpret a raw CAN payload. They define frame identifiers, byte layout, bit positions, signedness, scaling, offset, and units. OEMs and equipment manufacturers typically maintain these internally, often with multiple versions per model year or ECU software release. The difference between a usable signal and a misleading one is sometimes just a scaling factor, which is why keeping track of the right DBC revision is not optional. In mixed environments it is common to run with multiple DBCs at once, for example a powertrain DBC and a body DBC. Conflicts in message IDs happen, especially when gateways remap IDs or when supplier ECUs share ranges. The management layer helps keep these configurations explicit instead of buried in scripts. ##### CAN Bus channel detection Channel detection supports two approaches: passive and active. Passive detection listens for broadcast traffic and evaluates what is present on the bus. Active detection can transmit requests and wait for a valid response, which is useful for OBD-II polling or confirming that a J1939 network responds to requests in a controlled way. Channel configuration includes standard CAN and CAN-FD bit rates, with support for automatic baud rate detection. When working with CAN-FD, arbitration and data phase settings need to match what the network actually uses. A mismatch can look like “no traffic” even though the bus is active. That is common on bench setups and during early integration. Advanced settings cover termination and transmit permissions. Termination is relevant when a device is added to a bench harness or a short test loop. Transmit permissions are important when the device is used as a passive logger versus a tool that also sends queries (PIDs, PGNs, UDS requests). Many test programs require passive capture only, while others depend on controlled polling. Power environment is treated explicitly. The device is designed for 12 V and 24 V electrical systems, and channel setup can be aligned with heavy-duty use cases such as J1939, where traffic patterns and message sizes differ from passenger-car networks. ##### CAN Bus decoding Decoding translates raw frames into physical values. On the CAN-FD Pro, decoding can run directly on the device, which keeps the pipeline simple when raw logs would otherwise need server-side parsing. Decoders are typically driven by DBC definitions, but Python-based decoding and custom logic are supported where a DBC is not available or where signals require additional post-processing. Output formats include CSV, JSONL, and LOG for general workflows, plus MDF4 for programs that use ASAM tooling. MDF4 is widely used in automotive measurement and fits well with Vector tools such as CANalyzer, CANape, and CANoe. MDF4 output is also a practical choice when timestamps, channel metadata, and signal context need to be preserved for later correlation with other measurement systems. Decoding is not only about human readability. It is also a way to control data volume. A selected set of decoded signals is often smaller than a full raw trace, especially on a busy CAN-FD bus. Projects with multi-hour logging sessions or fleets of vehicles tend to end up with a split approach: raw capture for a limited time window, plus decoded output for longer periods. ##### CAN Bus filters Filters control which frames are logged, decoded, or forwarded. The CAN-FD Pro can record all raw traffic, but most deployments benefit from selective capture once the target signals and events are known. Filters can allow or block messages based on identifier, frame type, and identifier width. Filters can distinguish between data frames, error frames, and remote frames. Identifier handling covers both 11-bit and 29-bit identifiers, including mixed traffic on the same channel. This matters on networks where standard CAN and J1939 traffic coexist, or where gateways forward subsets between segments. Signal-based filtering can be derived from DBC files when decoding is enabled. This avoids hardcoding numeric IDs across multiple projects and ties filtering to a documented signal definition instead. It is common to start with broad ID filtering and later move to signal selection as the dataset stabilizes. Filtering is one of the practical levers for cost control. High-load CAN-FD capture, uploaded over cellular, can become expensive quickly. Keeping raw data local and exporting a limited subset reduces ongoing data transfer without removing the option to retrieve the full trace when needed. ##### CAN Bus frame listeners Frame listeners monitor live CAN traffic and trigger actions when specified conditions occur. This feature is used for event-driven data capture and device-side workflows, where a particular frame indicates a fault, mode transition, or threshold crossing. The action can be as simple as tagging a time window, or as complex as executing custom code and forwarding results to an external system. Frame listeners integrate with AutoPi’s service concepts, including [custom services](https://docs.autopi.io/cloud/device_management/services/create-custom-services/), [custom workers](https://docs.autopi.io/cloud/device_management/services/create-custom-workers/), [custom triggers](https://docs.autopi.io/cloud/device_management/services/create-custom-triggers/), and [returners](https://docs.autopi.io/cloud/device_management/services/create-custom-returners/). These components support Python-based logic on the device and controlled delivery of output to cloud storage, HTTP endpoints, or internal infrastructure. A typical workflow is fault-context capture: a listener detects a specific diagnostic frame and triggers an export of the last 30 minutes of raw CAN traffic. This creates a focused dataset for analysis without uploading raw traffic continuously. Another common workflow is “state-based logging”, where the logger switches profile when a vehicle transitions from ignition-off to ignition-on, or when a machine enters a working mode. Frame listeners are not limited to passenger cars. Machinery networks often have consistent event frames and clear state machines, which makes event-triggered exports practical. The important part is repeatability, the same trigger should yield comparable captures across a fleet. ##### Output control Output control governs how data is stored and exported, including destination, file format, and rotation. The CAN-FD Pro supports local storage on internal flash and can upload to external storage such as AWS S3. This is often combined with filters and decoding, depending on whether the output is raw frame dumps, decoded signals, or both. Local formats include ASC (Vector ASCII), BLF (Vector Binary Logging Format), CSV, DB-backed storage, JSONL, and LOG. ASC and BLF are widely used when working with Vector tooling and protocol analysis. BLF is also useful when storage efficiency matters during long recordings. CSV is a pragmatic choice for quick analysis, JSONL fits logging pipelines and structured ingestion, and LOG gives a plain text view for troubleshooting. File rotation is configurable by maximum file size and maximum age, preventing storage exhaustion during continuous capture. Rotation rules become important in multi-hour logging sessions, where raw CAN-FD traffic can generate large files quickly, depending on bus load and payload usage. For cloud exports, AWS S3 can be configured as a remote destination with access key ID, secret access key, bucket, and folder path. This setup fits environments where a project already uses S3-based workflows for downstream processing, archival, or integration into analytics platforms. Other endpoints can be used via returners when exports need to land in internal systems. Output control is one of the areas where most projects iterate. Raw capture is valuable, but output rules typically evolve once storage, bandwidth, and analysis workflows are known. ##### Tailscale integration The CAN-FD Pro supports native integration with Tailscale, providing encrypted access over a private mesh network based on WireGuard. Devices can be reached without port forwarding or public inbound firewall rules, which reduces operational risk in fleet deployments. Once enrolled, the device can be accessed over a private IP for SSH and controlled diagnostics. This is useful for remote troubleshooting, inspecting SocketCAN interfaces, validating logger state, and reviewing local logs when cellular uploads are delayed. In practical use, remote access often saves a site visit. Tailscale setup is managed from the AutoPi Cloud interface and requires one-time authentication with a Tailscale account. Access control can then be handled through the Tailscale admin console, which is where most teams already manage device-to-engineer access policies. Remote access is not a replacement for logging, but it helps shorten debugging cycles when a device behaves differently in the field than it does on the bench. This is a frequent issue in vehicle programs where bus traffic changes with ECU software versions and gateway configuration. // platform capabilities ## Built for scale - from prototype to production fleet AutoPi Cloud is more than a logger interface - it's a complete edge IoT platform for automotive data. - - - - ### Scale from one logger to an entire fleet - OTA Push logger configs, parsers, and firmware to any number of devices from the cloud - API REST and MQTT APIs for bidirectional integration with your existing toolchain - TLS Per-device authentication, signed payloads, and role-based access - built in [Contact us →](https://www.autopi.io/sales-inquiry/) ### Run custom containers alongside CAN logging - Docker Deploy any containerized workload on the device - preprocessing, ML inference, alerting - OS Open-source AutoPi Core OS on Raspberry Pi CM4 - full SSH and root access - HAT Expandable via USB, Gigabit Ethernet, and HAT - add sensors, CAN-to-USB adapters, and more [Contact us →](https://www.autopi.io/sales-inquiry/) ### Live device status, events, and signal values - Events Full event log: battery, CAN logging, S3 sync, position, motion - filterable by tag and time - Triggers Threshold rules and event reactors fire on DTC, signal anomaly, or frame match - run any workflow - Terminal Cloud terminal and logger.status command for live inspection without SSH [Contact us →](https://www.autopi.io/sales-inquiry/) ### Your data, your format, your destination - S3 AWS S3 upload for raw and decoded data - configurable path, sync interval, and retry logic - MDF4 ASAM MDF4 output compatible with Vector CANalyzer, CANape, and CANoe for direct analysis - SFTP Access local files via WiFi hotspot SFTP/SCP - no cloud upload needed for bench work [Contact us →](https://www.autopi.io/sales-inquiry/) // data pipeline ## From vehicle ECU to your data lake Three-stage pipeline - capture, process, deliver - with every parameter configurable per device, per channel, and per logger from the cloud. [ ECU / Vehicle ] ### Vehicle CAN networks - → CAN 2.0 / CAN-FD bus - → OBD-II · J1939 · UDS - → 11-bit + 29-bit frames - → Passenger · HV · Machinery → ↓ [ CAN-FD Pro ] ### Edge device - capture & process - can0 + can1 - passive or active - Auto-bitrate detect: any / OBD / J1939 - DBC decode: Standard + ASAM MDF4 - Pass/block filters - ID, mask, frame type - Frame listeners - event-driven burst log - 32 GB local buffer · offline-safe → ↓ [ Cloud / Storage ] ### Destinations & tooling - → AWS S3 bucket (raw + decoded) - → MDF4 · BLF · ASC - Vector tools - → JSONL / CSV - data pipelines - → REST / MQTT / Webhooks - → AutoPi Cloud dashboards 01 - CHANNELS ### Bitrate & channel config - Try Bitrates (auto scan) or Fixed - CAN 2.0 and CAN-FD arbitration + data phase - Termination: ~120 Ω enable/disable - Allow-send toggle for passive captures 02 - LOGGERS ### Capture configuration - Run At: startup · ignition · trip · manual - External dump process - high throughput - Multiple loggers per channel - Disk housekeeper - oldest-first purge 03 - DECODERS ### DBC & ASAM decoding - Standard: CSV · JSONL · LOG output - ASAM: MDF4 binary - Vector compatible - Frame ID Mask - J1939: 1FFFFF00 - Per-signal selection from DBC import 04 - OUTPUTS ### Storage & delivery - Local: ASC · BLF · CSV · DB · JSONL · LOG - AWS S3: raw + decoded, configurable path - Rollover by max size or max age - Retry interval + job timeout controls // faq ## Frequently asked questions #### AutoPi Cloud is designed for a wide range of users, including car owners looking to enhance their driving experience, fleet managers aiming to improve fleet management effiiciency, and developers interested in IoT Integrations. Whether you're a tech-savvy individual or managing a large fleet, AutoPi Cloud offers the tools you need. Explore our [Fleet Management System](https://www.autopi.io/business-solutions/fleet-management-system/) solution to see how AutoPi Cloud can benefits your specific use case. #### AutoPi Cloud offers an array of key features, such as real-time vehicle tracking, [remote diagnostics](https://www.autopi.io/business-solutions/features/ota-updates-diagnostics/), customizable alerts, data logging, and seamless integration with various IoT devices and platform. These features help you monitor you vehicle's performance and keep it running smoothly. #### AutoPi Cloud stands out with its user-friendly interface, extensive customization options, robust data measure, and seamless integration capabilities. Unlike other products, AutoPi Cloud provides a comprehensive solution that is both powerful and easy to use. Read more about our unique offerings in our [AutoPi Cloud Blog](https://www.autopi.io/software-platform/cloud-management/). #### Customers often ask about compability with their specific vehicle, the installation and setup, how their data is protected, and the variety of features available. We strive to address these concerns by providing detailed information and exceptional customer support. Visit our [FAQ page](https://www.autopi.io/faq/) and [Documentation page](https://docs.autopi.io/) for more questions and troubleshooting tips. #### Using AutoPi Cloud offers numerous benefits, such as enhanced vehicle safety through real-time diagnostics, improved fleet management efficiency, and customizable alerts that help you stay ahead of potential issues. One of the standout features is our [device configuration management](https://www.autopi.io/business-solutions/features/device-configuration-management/) capability, which allows customers to monitor, update, and control all their connected devices from a single platform. Additionally, we offer extensive customization options to match your business' specific requirements, ensuring that you get the most out of our platform. [Our commitment](https://www.autopi.io/about-us/) to providing exceptional support and building long-term relationships means you can rely on us to assist you every step of the way. #### AutoPi Cloud improves the user experience by providing detailed insights into vehicle performance, timely alerts to prevent issues, and an intuitive platform for managing [vehicle data](https://www.autopi.io/blog/the-meaning-of-vehicle-data/). It helps users stay informed and in control of their vehicles, reducing stress and improving efficiency. #### AutoPi Cloud is compatible with most vehicles that have an [OBD-II port](https://www.autopi.io/blog/what-is-obd-2/). It supports various operating systems and can be accessed through both web and mobile applications, making it versatile and accessible. Check out our [Documentation](https://docs.autopi.io/cloud/cloud-intro/) for detailed compatibility information. #### Installation is straightforward: simply plug the [AutoPi device](https://www.autopi.io/hardware/compare/) into your vehicle's [OBD-II port](https://www.autopi.io/blog/what-is-obd-2/), create an account on the AutoPi Cloud platform, and follow the setup instructions provided. The process is designed to be quick and easy, even for those who are not tech experts. For a step-by-step guide, visit our [getting started guide](https://docs.autopi.io/getting_started/autopi_tmu_cm4/). #### AutoPi Cloud automatically updates to ensure you always have the latest features and security enhancements. We also provide regular maintenance tips and updates through the platform, so you’re always informed about the best practices. Stay updated with our latest news on our [Blog](https://www.autopi.io/blog/). #### AutoPi Cloud offers flexible pricing plans to suit different needs. You can choose between a one-time purchase for a lifetime subscription or opt for a [monthly subscription plan](https://shop.autopi.io/pages/autopi-cloud-and-sim-subscription). Each plan provides access to various features, allowing you to select the best option for your requirements. #### Access roles, account boundaries and encrypted connections are technical controls. Configure permissions and review hosting, retention, administrator access and contractual data-handling requirements for your deployment. These controls are not a claim of regulatory certification. Request relevant security documentation during project scoping. // contact ## Still have questions? Get in touch with us - we're ready to answer any and all questions. // send a message We aim to reply within one business day. Or email [sales@autopi.io](mailto:sales@autopi.io).