How to Connect a Vehicle to the DIMO Network

Connecting a vehicle to the DIMO network splits drivers down two distinct tracks: a paid hardware installation or an entirely digital, free onboarding process for Tesla owners.

Drivers of non-Tesla vehicles must buy the DIMO LTE R1 adapter, a physical OBD-II diagnostic dongle that costs $99.99 upfront per vehicle. That purchase includes a one-month trial of the platform's connectivity service. Tesla owners bypass physical hardware entirely, onboarding for $0 through an API integration that includes a two-week trial.

Once promotional windows expire, both integration paths carry the same ongoing operational cost: a mandatory recurring network fee of $8.99 per month.

Installing the LTE R1

For standard gas, hybrid, and non-Tesla electric vehicles, onboarding relies on the physical R1 adapter.

The installation takes three steps:

1. Locate the vehicle cabin's standard diagnostic port and plug in the LTE R1 unit.
2. Launch the DIMO mobile application on a smartphone to initiate device pairing.
3. Complete the in-app prompts to pair the device, register the car as an on-chain asset, and open access to telematics data and vehicle insights.

The R1 adapter relies on dedicated cellular connectivity—broadband LTE backed by a 2G fallback—to transmit telematics directly to the platform independently of the driver's phone.

However, DIMO does not publish an exhaustive list of supported international territories or partnered regional carriers for the R1. Drivers outside primary launch markets will need to independently verify local cellular support before purchasing the physical unit.

Setting Up Native Tesla Integration

The Tesla integration requires no physical tools, port adapters, or shipping waits.

Instead of transmitting data through an external cellular modem, this path hooks directly into Tesla’s native software environment through the car's app integration. Drivers open the DIMO application, choose the native integration route, and authenticate using their standard Tesla account credentials.

Granting these permissions links the vehicle directly to the platform over the car's existing factory cellular connection, bringing the asset online immediately upon authentication without requiring upfront hardware.

Token Drops and Qualification Rules

Connecting the vehicle is only the baseline; the car will not earn passive token distributions simply by sitting parked in a garage.

DIMO issues its token rewards weekly, distributing allocations on Mondays. To qualify for a given Monday payout, a connected vehicle must complete at least one drive during that calendar week. This single trip creates the necessary telematics payload, proving to the network that the client—whether the LTE R1 or the direct Tesla software link—is online and actively transmitting data.

For developers looking beyond simple client onboarding, this telematics pipeline feeds directly into DIMO Build. Through a dedicated Developer Console, builders can query incoming telematics streams, handle data access permissions across fleets, and build automated operational workflows.

Undocumented Network Parameters

While DIMO makes its baseline participation rules clear, several technical and financial mechanics remain unaddressed in its documentation:

• Reward calculation mechanics: DIMO confirms that driving once per calendar week qualifies an account for Monday distributions, but its core onboarding documentation does not publish the precise underlying formulas. It remains unestablished how token yields scale against variables like mileage driven, engine runtime, or total telemetry volume transmitted.
• Network-level node infrastructure: For operators wanting to support network infrastructure directly rather than as driving clients, DIMO has not published hardware requirements, backend system specifications, or staking thresholds for operating network-level validator or processing nodes distinct from end-user vehicle tracking devices.