Decibic

Browser-exposed DualSense diagnostics

PS5 controller test

Inspect the buttons, sticks, triggers, touch points, and rumble capability that this browser actually exposes from a PS5 DualSense or another connected controller.

This page does not identify hardware with certainty, alter calibration, or unlock DualSense features. Labels and capabilities can change with browser, OS, cable, Bluetooth, drivers, and mapping.

How to use

  1. Connect by USB or Bluetooth, choose Start monitoring, then press a controller button so the browser can expose it.
  2. Press each control slowly. Move both sticks around their edges, release them, and compare raw values and recent trails.
  3. With sticks untouched, take a neutral sample. Repeat unexpected observations in a game or official platform utility.

Local Gamepad API access

Starting reads browser-provided controller IDs, mappings, button values, axes, active touch points, and reported haptic support. The Gamepad API normally has no permission prompt, but a button press may be required before a controller appears.

  • Gamepad API only
  • No external requests
  • No stored readings
  • No firmware writes

Ready. Connect a controller and choose Start monitoring.

Live browser readings

Raw indexes remain visible even when the browser cannot supply a standard mapping. “DualSense” labels below are positional references, not device detection.

Browser-reported ID
—
Mapping
—
Buttons
—
Axes
—
Layout labels
Waiting for a controller.
Touch surface
No touch position reading yet.
Rumble output
Availability has not been checked.
Extra buttons
Raw B17+ inputs will be listed if exposed.
Motion and adaptive triggers
Motion sensors and adaptive-trigger output are not standardized readings in this Gamepad API view.
Audio, light, battery
Microphone, speaker, headset, mute light, light bar, and battery are not tested or inferred here.

Connect a controller to check whether the browser reports the standard layout required for the DualSense reference diagram.

No standard-mapped controller is active. Use the raw button and axis panels when a controller appears.

Left stick · axes 0 / 1 Raw: — Neutral preview: no sample Waiting for standard-mapped axes. Observed range: —
Right stick · axes 2 / 3 Raw: — Neutral preview: no sample Waiting for standard-mapped axes. Observed range: —

L2 / R2 input history

Recent render-frame values · not adaptive-trigger force
L2 B6: — R2 B7: —

All browser buttons

Raw index, value, pressed, and touched state

No button readings yet.

All browser axes

Raw normalized values from −1 to 1

No axis readings yet.

Neutral sample and comparison dead zone

The sample summarizes raw axes 0–3 for this page session. “Neutral preview” only subtracts the sampled mean in the readout; it does not calibrate the controller, OS, firmware, or a game.

No neutral sample yet. Keep the page visible and the sticks untouched when sampling.

A short, user-triggered dual-rumble command is available only when the active browser/controller path exposes it. It does not test adaptive triggers or measure strength.

Practical checks

  1. Buttons: press and release each control once. Confirm the expected raw index changes and returns.
  2. Triggers: squeeze L2 and R2 gradually. When standard-mapped, B6/B7 should show an analog 0–1 input if the browser supplies it.
  3. Stick travel: trace slow circles and cardinal directions. Clear history and repeat to compare paths, gaps, and observed range.
  4. Rest position: release both sticks, sample without touching the controller, and repeat. Compare raw offsets rather than treating one sample as a verdict.

DualSense and browser limits

  • A standard mapping describes positions, not the controller brand. Non-standard mappings use raw indexes only.
  • Touchpad click can appear as an extra button, but its index is not assumed. Touch positions appear only when Gamepad.touches supplies active points.
  • Motion sensors, adaptive-trigger output, speaker, microphone, headset, mute light, light bar, battery, and firmware are not inferred from axes or IDs.
  • Browser timing, OS drivers, USB/Bluetooth transport, remapping software, and games can change readings. This page does not measure polling rate or input latency.
  • History and neutral samples support comparison only; they cannot certify drift, dead-zone shape, circularity, repair need, or warranty status.

For a suspicious result, reconnect the controller, close software that may remap inputs, repeat over another supported connection, and compare with the current PlayStation Accessories app or console settings before considering repair.