Knowledge base

Get from install to live telemetry

A practical guide to DPM Agent, device pairing, game telemetry, dashboard surfaces, reports, and the fixes that solve most connection problems.

Documentation preview Source reviewed 15 November 2026 Feature coverage matrix published

Start here

Quick start

DPM uses two parts for live telemetry and controls: the Windows DPM Agent reads the simulation and performs PC actions; the Android app displays telemetry and sends your control presses back to the Agent. Quick Demo runs locally on Android without a PC or Agent.

Release note: DPM Agent User Edition is available free from Microsoft Store, and DPM Adaptive Button Box is available from Google Play. Use these verified public listings for installation and updates.
  1. Install DPM Agent on the gaming PC. Get the free DPM Agent User Edition from Microsoft Store.
  2. Put the PC and Android device on the same trusted local network. Avoid guest Wi-Fi or client isolation.
  3. Launch DPM Agent, then open the Android app. The app normally discovers the Agent without manual IP entry.
  4. Pair the new device. Enter the 8-digit numeric code shown by DPM Agent while its pairing window is open, or use the optional QR scanner.
  5. Start a supported simulation. Select a dashboard, Button Box, Flags, MAPSCOTT, or another available surface.

01 — Installation

Install the two DPM components

Windows PC

  1. Install the free DPM Agent User Edition from Microsoft Store.
  2. Confirm the Microsoft Store listing identifies DPM876 Studios as the publisher.
  3. Launch DPM Agent. Keep it running in the tray while using DPM.
  4. If Windows Firewall asks, allow DPM Agent on your trusted private network only.

Microsoft Store provides the supported public Windows package, current requirements, installation, updates, and uninstall management for DPM Agent User Edition.

Android device

  1. Install DPM Adaptive Button Box from Google Play.
  2. Allow notifications when requested so Android can show the required connection-service status.
  3. Keep Wi-Fi enabled and connect to the same private network as the PC.
  4. Open the app and continue to pairing.
Current development source declares Android 8.0 (API 26) or newer. The final public device and Android-version support matrix remains a release-readiness decision.

02 — Trust your device

Pair the Android app with DPM Agent

DPM normally discovers Agents on the local network. A previously unknown device must pair before it can receive telemetry or send controls.

  1. Open the Android app. Choose the PC shown in the Agent picker if more than one is discovered.
  2. Check DPM Agent. Open its pairing window and locate the 8-digit numeric code, shown as ####-####.
  3. Enter or scan the code on Android. The code expires after five minutes and authorizes one device. QR scanning is optional; manual entry remains available.
  4. Wait for the connected state. The device stores a protected credential for future reconnections.
What pairing protects: the app and Agent use a challenge-response proof so an unknown client cannot use Agent commands. The Android secret is protected with Android Keystore; the Agent protects its copy with Windows DPAPI.
Keep DPM on a trusted private network. Current Android-to-Agent telemetry, commands, and launcher artwork use the authenticated encrypted wss:// connection. Do not expose Agent ports through your router or use DPM on an untrusted public network.

If pairing is rejected

  • Request a fresh code; old codes expire and a used code cannot pair another device.
  • Make sure the app is connecting to the intended PC, especially if multiple Agents are visible.
  • If DPM Agent says the device is no longer trusted, remove the saved device entry on both sides and pair again.
  • Check that the PC clock is correct and that security software is not blocking local traffic.

03 — Simulation setup

Supported game integrations

DPM supports the games below, but feature coverage varies with the telemetry and controls each title exposes. See the current Game Support at a Glance matrix for the published status of Analytics, Button Box / ButtonRowe, Dashboard, rosters, MAPSCOTT, and Flags.

Shared memory

Assetto Corsa EVO

Telemetry, adaptive dashboard data, control mapping, car/track data, and supporting Agent workflows are present in current source.

Shared memory

Assetto Corsa Competizione

The current matrix lists Analytics, Button Box / ButtonRowe, Dashboard, car and track rosters, MAPSCOTT, and Flags as supported.

Shared memory

Assetto Corsa Rally

Button Box / ButtonRowe, Dashboard, and Car Roster are supported. Analytics, Track Roster, and MAPSCOTT are planned; Flags are not currently supported.

Shared memory

Le Mans Ultimate

The current matrix lists all seven major feature groups as supported, including Analytics, rosters, MAPSCOTT, and Flags.

UDP telemetry

Forza Horizon 4 / 5 / 6

The Forza-family adapter receives Data Out packets. Button Box / ButtonRowe and Dashboard are supported, Flags are partial, and Analytics, car and track rosters, and MAPSCOTT are not currently supported.

Shared memory

Automobilista 2

Analytics, Button Box / ButtonRowe, Dashboard, and Flags are listed as supported. Car Roster, Track Roster, and MAPSCOTT are planned.

Published

Compatibility matrix

The live Game Support at a Glance matrix shows current coverage by title. The Android Welcome & Help area also includes a native Game Support view and a combined Features & How-tos library.

Forza Data Out

  1. Open DPM Agent Settings and note the UDP telemetry port. The default is 20067.
  2. In the game, enable Data Out and set the destination IP to the gaming PC's local IPv4 address.
  3. Set the Data Out port to the same Agent value. Do not use ports 5200–5300 for DPM's receive port.
  4. If another telemetry app also needs the data, configure DPM Agent's optional UDP forwarding instead of trying to make both apps bind the same receive port.

04 — App surfaces

Choose the right screen for the session

The app's available destinations include the following surfaces. What appears can depend on the active game, car, app state, and release entitlement.

Dashboard

Six dashboard modes—Race, Race II, Sim, Sim II, Cruise, and Cruise II—present live driving information in different layouts.

Button Box

Contextual touch controls for the active game and car, routed through DPM Agent.

BUTTON ROWE

A dedicated control surface designed around an alternate button-row layout.

Flags

A focused flag and race-control display for a dedicated secondary device.

MAPSCOTT

A dedicated track-map and session-information surface.

DPM Analytics

Session scoring, coaching categories, and report history driven by Agent analytics snapshots.

Input Telemetry

A two-dimensional input trace for inspecting steering and pedal behavior.

Libraries

Car roster, track roster, profiles, and car setups can provide reference and setup workflows outside an active drive.

Some instrument surfaces use a fixed authored canvas, while libraries and settings use adaptive layouts. Final supported-device and orientation coverage is being verified during Android readiness work.

05 — Commands

Controls and button mapping

Touch actions travel from the authenticated Android device to DPM Agent, which applies the corresponding game or Windows command. Available actions vary by title.

  1. Start the target game and confirm DPM Agent identifies it.
  2. Open Button Mapping in the Android app or the relevant command-mapping page in DPM Agent.
  3. Choose the game action, then record or assign the keyboard/wheel input requested by that page.
  4. Save the mapping and verify the resulting action in the live game.
Seeing a button in the app is not proof that a game accepted or persisted its binding. Test every mapped action in the target game and inspect the game's saved binding when persistence matters.

DPM Agent also contains selected PC controls such as volume, media/recording, launcher, mouse, and system actions. Their availability can depend on Windows permissions, Agent edition, and release configuration.

06 — More than one display

Use multiple Android devices

Each authenticated device can select a different surface—for example Dashboard, Button Box, and Flags. At app launch, DPM can show screens already occupied on other connected devices and disable those choices.

  • Pair every Android device with the same DPM Agent.
  • Launch or reconnect all participating devices so their active-screen state reaches the Agent.
  • Choose a different available screen on each device.
  • If occupancy looks stale, reconnect the affected device rather than assuming another screen is still active.
Current Agent source accepts up to seven authenticated clients. The smaller public support limit and tested device matrix will be set after multi-device release validation, so plan conservatively until that evidence is complete.

07 — Driver performance

Analytics and session reports

In current development source, DPM Agent processes each telemetry frame once and sends synchronized analytics snapshots to connected Android devices. The app presents control, pace-efficiency, and safety/discipline feedback and can display detailed session reports.

  • Control: steering corrections, braking phases, throttle application, wheel slip, and related stability signals.
  • Pace efficiency: lap and sector context plus supported shift-timing evidence.
  • Safety and discipline: supported track-limit, road-departure, spin, collision/damage, pit, and lap-validity signals.
  • Reports: self-contained HTML breakdowns, history, filtering, comparison, sharing, and deletion workflows are represented in current source.
Analytics is coaching information, not an official steward, safety system, or guaranteed measure of driving ability. Signal coverage and calibration vary by game. LMU calibration work is still in progress, so scores should not yet be compared as if every title supplies identical evidence.

08 — Fix a connection

Troubleshooting checklist

The app cannot find DPM Agent

  1. Confirm DPM Agent is running on the gaming PC.
  2. Confirm both devices are on the same private network and subnet.
  3. Disable guest Wi-Fi/client isolation or move both devices to the primary LAN.
  4. Allow DPM Agent through Windows Firewall on private networks.
  5. Refresh the Agent picker. If the PC changed IP address, choose the current discovered entry.
  6. As a diagnostic only, enter the PC's current local IPv4 address and Agent WebSocket port manually.

The Agent appears, but pairing never completes

  • Open a new pairing window and use the newest code within five minutes.
  • Confirm you are pairing with the intended PC.
  • Revoke the old device trust entry, remove the saved Android credential, and pair again.
  • Check security software for blocked local connections on TCP 9876.

DPM connects, but there is no live telemetry

  • Confirm the game is running and DPM Agent shows the correct active title.
  • For Forza, enable Data Out and match the PC IP and UDP port.
  • For shared-memory games, verify the game/Agent versions are included in the current compatibility matrix.
  • Restart the game integration after changing telemetry settings.

Telemetry works, but a control does not

  • Verify the command is supported for the active game and car.
  • Re-save the mapping and test it in the game.
  • Check for conflicting keyboard, wheel, or game bindings.
  • Do not treat an on-screen press animation as proof that the game accepted the command.

Default network ports

PortProtocolPurposeChangeable?
9876TCP / secure WebSocketAuthenticated Android connection, telemetry, commands, and current launcher artwork deliveryYes, in Agent settings
9877TCP / HTTPLegacy/local launcher-artwork endpoint retained in Agent settings; the current Android app receives artwork through the authenticated WSS sessionYes, in Agent settings
20067UDPGame telemetry input, currently used by the Forza familyYes; match the game setting
20066UDPDefault optional forwarding target for another local telemetry consumerYes; forwarding can be disabled

If you change a port, update every matching sender/receiver and firewall rule. Never port-forward these services to the public internet.

09 — Data boundaries

Privacy, diagnostics, and security

DPM's live telemetry and control path is designed for the local network between your Android device and PC. Current source uses authenticated pairing, protected device secrets, and an encrypted wss:// session for Android-to-Agent telemetry, commands, and launcher artwork.

Local

Telemetry & commands

Move between DPM Agent and paired Android devices on your LAN. Do not expose Agent ports publicly.

Protected at rest

Pairing secrets

Protected with Android Keystore on Android and Windows DPAPI in DPM Agent.

Bounded files

Connection diagnostics

The Android app writes app-private connection events to four rotating JSONL files of up to 2 MB each. These are not telemetry payload recordings and are not automatically uploaded.

Store verification

Website, scanner & backup

The optional QR pairing scanner is provided by Google Play services without a DPM camera permission; manual code entry is available. Ordinary preferences and user-created content may follow Android backup, while credentials, billing cache, diagnostics, launcher cache, and setup-sync data are excluded.

Read the current Privacy Policy. A release must keep the website policy, in-app link, Google Play Data Safety answers, Agent behavior, Android backup rules, and support procedures consistent.

Contact support

Email support@dpm876.app with:

  • Android app version and DPM Agent version.
  • Game and game version.
  • Android device and Windows version.
  • Whether discovery, pairing, connection, telemetry, or control is the first failing step.
  • The exact time the issue occurred and the troubleshooting steps already tried.

Do not email passwords, pairing codes, private keys, or unredacted personal files. Diagnostics should be shared only through an approved support workflow.