Delivering quality telemetry data from all types of machinery, trucks and vehicles
Open IoT stack for CAN/CAN-FD/J1939 data logging, edge execution and cloud orchestration with Core, Cloud and API integration
AutoPi Cloud
Control plane for logging,
events and fleet operations.
AutoPi Cloud provides a unified control plane for channel configuration, logger lifecycle management, decoder setup, output routing, frame listeners and event reactors - configurable remotely per device, group or project. Templates apply repeatable configuration at fleet scale. Cloud access is included with every AutoPi device.
Channel logging and decoder control
Configure named loggers per channel (can0/can1) with pass/block ID filters, rollover size and S3 sync interval. Select Standard (CSV/JSONL/LOG) or ASAM (MDF4) decoding per logger and import DBC files with per-signal selection. J1939 PGN/SPN and 29-bit identifiers handled natively.
decoder: asam | output: mdf4 | filter: pass
Docker and workflow hook deployment
Deploy containerized applications to devices via Cloud - versioned per project or fleet. Attach workflow hooks (handler, converter, trigger, filter, enricher, returner) to frame listeners for on-device event-driven processing. No hardware changes required to scale from filtering to local inference.
hook types: handler · converter · trigger · filter · enricher · returner
Centralized configuration at scale
Define and apply device templates across groups or projects - covering channel config, logger setup, output workers, upload policies and advanced settings fields. Changes propagate via SaltStack on next device connection. Configuration is auditable and version-tracked in Cloud.
scope: device · group · project · template
Remote firmware and application rollout
Push firmware updates, base images and Docker containers to devices without physical access. Cloud tracks rollout progress per device and supports rollback. Output worker intervals, retry counts and sync behavior are tunable per update policy - critical for fleets spanning multiple sites and time zones.
strategy: incremental · rollback supported · progress tracked
Full API parity with the Cloud UI
Every Cloud operation - device config, logger setup, template application, event queries, trip retrieval - is available via the REST API at api.autopi.io. Use the API to integrate AutoPi into existing backends, CI/CD pipelines or infrastructure-as-code tooling. MQTT available for real-time data streams.
api.autopi.io | REST + MQTT | UI parity
Event stream, trip correlation and diagnostics
Monitor device health, trip telemetry and the live event stream from one dashboard. Filter events by tag and time window - including autodetect results, logger state changes and S3 sync confirmations. Correlate CAN logging behavior with trip records and trigger targeted diagnostics for devices that deviate from baseline.
filter: tag · time · device · trip
J1939 Ready
Connect AutoPi devices to heavy machinery with J1939 adapters
Purpose-built J1939 adapter cables give direct access to the heavy-duty network on trucks, excavators and construction equipment - including connectors for Cummins, Caterpillar, Komatsu and other major OEMs. The standard adapter range covers OBD-II, power cables, splitters and vehicle-specific connectors for light-duty fleets.
This keeps installation straightforward across vehicle types, preserves access to existing diagnostic ports and avoids custom hardware for each project.
Female CAN bus cable with open wires
OBD-II to dual DB9 adapter
Cummins-Komatsu truck 12-pin J1939 to 16-pin OBD-II adapter
Cummins 9-pin J1939 (J1708) to 16-pin OBD-II adapter cable
Caterpillar (538-5051) truck 9-pin J1939 to 16-pin OBD-II adapter
AutoPi Solutions
Three platforms. One operational model.
AutoPi Core, AutoPi Cloud and the REST API behave identically across all hardware - enabling a single integration and deployment pattern regardless of vehicle type or protocol. Choose the platform that matches the bus, compute and environmental requirements of each project.
Consistent operational model across all devices
AutoPi Core runs on standard Linux with SocketCAN, Python and SaltStack. AutoPi Cloud and REST API configuration is identical across device types. CE, FCC and RoHS certified. Designed and produced in Denmark.
In stock | Order now → Ships tomorrow.
Engineering Workflow
From protocol discovery
to production telemetry
The same workflow runs across pilots and full fleet deployments. Every step is configurable from the Cloud UI or REST API.
// faq
Frequently asked questions
// contact
Still have questions?
Get in touch with us - we're ready to answer any and all questions.