###### Real-Time Data Streaming # Low-latency vehicle data with deterministic delivery **AutoPi Real-Time Streaming** forwards raw and decoded vehicle signals from the CAN-FD Pro directly to your backend with minimal delay. Data from **CAN 2.0**, **CAN-FD**, **OBD-II**, **J1939** and auxiliary sensors is captured on the device’s isolated CAN controller, timestamped, and transmitted over **4G/LTE**, **WiFi**, or **Ethernet** with adaptive retry and buffering. The CAN-FD Pro is built for high-volume workloads such as EV battery telemetry, powertrain development, and ADAS data capture. A dedicated controller ensures stable arbitration, while kernel-level drivers handle burst traffic without loss. Messages are streamed using **MQTT**, **REST**, or **webhooks**, with guaranteed ordering when reconnecting after offline operation. Configure sampling rates, apply delta streaming, and forward raw frames or decoded signals. TLS device certificates, device-side ACLs, rate limits, and tenant isolation secure large deployments. Integrate with existing platforms through our **open API** and manage OTA updates, parser versions, and configurations centrally. [Contact Us](https://www.autopi.io/general-inquiries/) ###### Feature Highlights ## Real-Time Data, Real-Time Decisions: The Unified Platform AutoPi streams telemetry from vehicles and edge devices into a unified data layer. Events are delivered with low latency to dashboards, webhooks, and back-end systems, so you can automate reactions, feed analytics, and validate behaviour using consistent, time-stamped data rather than manual exports. #### Telematics Data Streaming Layer Use AutoPi as the transport and integration layer between vehicles, edge logic, and your own applications. Normalised payloads, topic structures, and APIs give developers a stable interface for building dashboards, alerts, and downstream services on top of live data. ### Telemetry from devices is buffered and forwarded in near real time to AutoPi Cloud and onward to MQTT, webhooks, or REST endpoints. Typical end-to-end latencies are measured in seconds, making the stream suitable for live dashboards, alerts, and control loops that depend on up-to-date vehicle and sensor states. ### The same architecture supports a handful of test vehicles and large, distributed fleets. Device-side sampling and filtering keep bandwidth predictable, while the backend handles parallel connections, topic fan-out, and backpressure so that stream behaviour remains consistent as you add more units and data sources. ### Consume the stream through REST APIs, webhooks, or message brokers and map it into your own data model. Push events into maintenance platforms, ERP, data lakes, or bespoke applications without re-implementing the device layer. Payload formats are documented so they can be parsed reliably by existing tooling and pipelines. ### Data in transit is protected with TLS and authenticated device connections. Access to streams and APIs is controlled per tenant with keys and roles, and events are stored with audit trails and retention policies. This allows you to expose data to multiple systems while keeping boundaries between customers, projects, and environments clearly defined. ### Work with payload examples, device simulators, and documentation that describe event structures, topics, and API usage. Use dashboards and logs to inspect live and historical messages, verify mappings, and troubleshoot integrations, so you can move from prototype to stable deployment with fewer unknowns in the data path. [Contact Us](https://www.autopi.io/general-inquiries/) ##### Stream Live Vehicle Signals Capture CAN, CAN-FD, OBD-II, and J1939 data in real time. The CAN-FD Pro timestamps and forwards signals with low latency over 4G/LTE, WiFi, or Ethernet. ##### Low-Latency Transport Stream data through MQTT, REST, or webhooks. Kernel-level CAN drivers handle burst loads, ensuring timely and reliable delivery. ##### Scale to Any Volume Handle thousands of messages per second with hardware-backed CAN-FD and adaptive sampling. Ideal for fleet-scale telemetry or engineering-grade data capture. ##### Secure Data End-to-End All streams use TLS device certificates, on-device access control, and tenant isolation to protect data in motion and at rest. ###### Feature Details ## Real-time streaming for vehicle data pipelines Build reliable, low-latency data flows from the AutoPi CAN-FD Pro into your own backend. Control how signals are captured, processed, secured, and delivered for engineering and fleet workloads. ##### Signal-Level Control Configure per-signal logging for **CAN 2.0**, **CAN-FD**, **OBD-II** and **J1939**. Select PIDs, raw frames, and sampling intervals, and tag every message with device, VIN, and monotonic timestamps for precise correlation in your backend. ##### Edge Processing & Filtering Apply filtering, threshold logic, and basic aggregation on-device before sending data upstream. Use configurable rules to forward only deltas, exceptions, or downsampled streams, reducing bandwidth while preserving engineering-grade detail where needed. ##### Flexible Payload Formats Output raw CAN frames or decoded signals as JSON or compact binary payloads. Map fields to your own schema and include metadata such as GPS, driver, and trip identifiers so streams plug cleanly into dashboards, data lakes, or time-series databases. ##### Config Management & Security Manage streaming settings as templates across fleets, with versioned changes and safe rollbacks. All traffic is protected with TLS and device certificates, and access is controlled via roles and per-tenant isolation on the AutoPi platform. ##### Streaming Targets & QoS Deliver data to your systems over **MQTT**, **REST**, or webhooks. Configure QoS levels, retry behavior, and buffering so that temporary connectivity issues do not result in data loss or broken time series. ##### Modular Expansion Extend the CAN-FD Pro with additional HATs and interfaces when your project grows. Add extra CAN channels, digital I/O, or external sensors and stream those signals through the same configuration and monitoring pipeline. ###### Something unclear? ## Frequently asked questions ## Real-time data streaming on AutoPi means continuously sending CAN, CAN-FD, OBD-II, J1939 and GNSS data from the device to your backend as it is generated, so you can analyse and act on it without waiting for batch uploads or manual exports. ## You can stream raw frames or decoded signals from dual CAN/CAN-FD channels, OBD-II and J1939, as well as GNSS position, basic IMU data (if present) and other connected sensors such as digital inputs or external modules. ## Yes. AutoPi exposes open [APIs](https://www.autopi.io/glossary/application-programming-interface/) and supports direct streaming to your own MQTT broker, REST endpoints or webhooks, so you can plug the data into existing dashboards, data lakes or analytics pipelines. ## Yes. The CAN-FD Pro runs Linux with SocketCAN, and Python is fully supported on the device. If you can talk to CAN via SocketCAN in Python, you can run that logic on AutoPi and extend the standard streaming behaviour with your own code. ## When the mobile or WiFi connection drops, the device buffers data locally in a queue. Once connectivity returns, the queue is flushed in order to the configured targets, so you keep a continuous time series without gaps. ## Yes. You can configure filters by CAN ID, PIDs or signals, define sampling intervals, and choose between full-rate streaming, downsampling or delta-only updates to match your bandwidth and analytics requirements. ## Streams are protected with TLS, device certificates and access control at the platform level. Per-tenant isolation and role-based permissions help ensure that only authorised systems and users can configure or consume data streams. ## Yes. You can stream data from internal combustion vehicles and EVs in the same deployment, including engine parameters, battery metrics, DTCs, GPS position and other CAN-based signals across different vehicle brands and protocols. ## Common use cases include fleet tracking with live telemetry, engineering test benches, remote diagnostics, EV battery monitoring, ADAS and powertrain logging, and feeding high-frequency CAN data into analytics or digital twin platforms. ## You own the data generated by your devices. It can be stored in AutoPi Cloud, streamed directly into your own infrastructure, or both, depending on how you configure your project and compliance requirements. // your proof of concept ## Build a PoC for Real-time Data Streaming for Instant Insights Let's find the right hardware for your vehicles, validate the data you need and plan the integration together. ### Choose by integration requirements // fleet data #### AutoPi Mini Verify supported EV/OBD vehicles and parameters for standard fleet data. [Explore Mini →](https://www.autopi.io/hardware/autopi-mini/) // vehicle-bus logging #### AutoPi CAN-FD Pro Evaluate J1939, CAN FD and vehicle-bus data logging. [Explore CAN-FD Pro →](https://www.autopi.io/hardware/autopi-canfd-pro/) // custom edge software #### AutoPi TMU CM4 Develop Docker workloads and custom edge software. [Explore TMU CM4 →](https://www.autopi.io/hardware/autopi-tmu-cm4/) Confirm vehicle power, connectors, adapters and any required external sensors. An accessible connector does not guarantee that every requested signal is available. [Compare device capabilities →](https://www.autopi.io/hardware/compare/) // project scope ### Separate standard capabilities from project work Included The selected device's documented hardware and standard software capabilities. Confirm supplied accessories and Cloud access terms for your order. Configure Supported signals, sampling, trip and geofence rules, data delivery and retention for the selected device and platform. Custom development Proprietary signal decoding, custom applications, external sensor integration and ERP/TMS workflows require an agreed scope. // from testing to rollout ### Explore what's possible on your vehicles [Image: AutoPi vehicle data devices] We'll help you choose devices to purchase for representative vehicles, then work with you to extract the data you need, including reverse engineering where needed. Together, we'll agree the scope and acceptance criteria, validate the captured signals and integration, then decide on rollout. [Discuss your PoC →](https://www.autopi.io/sales-inquiry/?product=compare&intent=proof-of-concept&source=business-real-time-data-streaming) // 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).