Compare all our devices

AutoPi offers three main device families: the AutoPi Mini, the AutoPi TMU CM4, and the AutoPi CAN-FD Pro.

The Mini is designed for quick deployments where you want a compact unit for tracking and vehicle parameter data (OBD/OEM signals depending on the vehicle). The TMU CM4 is a Raspberry Pi Compute Module 4 based platform intended for projects that require customization, integrations, and running your own software on-device. The CAN-FD Pro is intended for high-volume CAN/CAN-FD logging workflows where dense bus traffic and raw frame capture matter.

All devices can be used with AutoPi Cloud for fleet and device management, and they can also be integrated into existing systems depending on your requirements.

Start with what you need to collect and how you plan to use the data.

Choose the Mini when you mainly need GPS tracking and vehicle parameters via standard interfaces, and you want a simple install. Choose the TMU CM4 when you need control over the software stack (custom services, integrations, edge logic), or when your project requires a Raspberry Pi base. Choose the CAN-FD Pro when you need high-volume raw CAN/CAN-FD frame logging, dense bus capture, or workflows where timestamp precision and storage matter.

If your project depends on specific OEM signals, the practical answer is usually: validate on a representative vehicle early. Availability can vary by make, model, and ECU configuration.

The available data depends on the device and the vehicle.

On many vehicles you can collect position (GPS), power and ignition related data, and standard OBD-II parameters. On some vehicles you can also extract OEM-specific signals, including EV-related values, but this depends on what the vehicle exposes and what protocols are available.

For CAN/CAN-FD projects, raw frame collection is typically the right approach when you need full control over decoding and post-processing. For parameter-style collection, the device reads and reports values that the vehicle makes accessible through supported interfaces.

Yes, but not all devices are intended for the same CAN workflows.

The CAN-FD Pro is designed for high-volume CAN/CAN-FD logging and raw frame capture. The TMU CM4 provides CAN-FD interfaces and is well-suited for telematics and custom integrations, but whether it is the right choice for heavy raw logging depends on the logging approach and requirements. The Mini is generally used for OBD-style parameter collection and tracking rather than full CAN/CAN-FD bus logging.

If your goal is a full bus dump or dense CAN-FD traffic capture, the CAN-FD Pro is typically the correct starting point.

This depends on the device family.

The TMU CM4 is the main platform for custom software, since it is built around a Raspberry Pi Compute Module 4 and is intended for running your own services and integrations. Depending on your workflow, this can include containerized workloads and device-side logic that interacts with vehicle interfaces and cloud services.

The CAN-FD Pro focuses on logging workflows and is usually used as a dedicated logger integrated into a broader pipeline. The Mini is designed for simpler deployments and is not intended as a general-purpose edge compute platform.

Yes, in many projects the devices can be integrated into existing systems, but the level of effort depends on your use case.

AutoPi Cloud provides device management, fleet management, configuration, and monitoring features that reduce implementation work. If you already have your own backend, you can typically integrate at the data level and manage devices in a way that matches your architecture.

For teams that want the fastest path to production, Cloud is usually the practical default. For teams with existing infrastructure, integration is often the better fit.

Yes. In addition to standard customer support, we also offer development hours for teams that want help with integration, configuration, or device-side development.

This is typically used for things like: validating data availability on a target vehicle, building a proof-of-concept pipeline, setting up logging or storage workflows, or integrating device data into an existing application.

Many teams start with a small scoped engagement to remove early technical risk before scaling a deployment.

Plan for a quick validation step on a representative vehicle.

OEM and EV signals vary significantly across vehicle platforms, model years, trim levels, and ECU configurations. Even when a protocol is supported, the specific signals you need may require OEM PID access, UDS workflows, or raw CAN decoding with DBC definitions.

The most reliable process is to define a short list of required signals, test against a real vehicle, and confirm the extraction path (parameter-based vs raw frames). If needed, we can support this step through development hours.

Hardware support means the interface exists physically on the device (for example CAN-FD, USB, Ethernet, GNSS, modem). Software support means the feature is available as a shipped capability in the device stack or platform.

Some features also fall into a third category: available through configuration. That typically means the capability exists, but you must enable it, configure it, or implement parts of the workflow (for example decoding, filtering, uploading, or storage strategy).

This distinction matters most for advanced vehicle access and high-volume logging projects, where the interface is only one part of the complete solution.

Orders are typically shipped within a few business days, and most items are kept in stock. When your order is dispatched, you receive tracking information so you can follow the shipment.

Delivery time depends on destination and carrier service. If your project has a hard deadline, it is usually best to place the order early and plan time for a short validation phase before scaling.

If you need help choosing a device or validating a specific data requirement, the fastest approach is to contact us with (1) the vehicle type, (2) the signals you need, and (3) what you plan to do with the data (logging, streaming, dashboards, exports, integrations).

You can reach out to us and we will help you narrow down the device choice and identify the right validation steps before you commit to a larger rollout.