Controller Calibration Test

Introduction

The DeviceHub Controller Calibration Test is a free online axis rest-and-range checker that records browser-visible stick and trigger values at rest and at physical extremes, without pretending to be the Windows Game Controllers calibration wizard or macOS controller utility. Technicians documenting drift for RMAs, players comparing deadzone complaints to raw numbers, and developers choosing default deadzones for browser games use this page to capture concrete floats the Gamepad API returns. Open the tool, wake the pad, sit untouched for a rest sample, then push each axis to its stops while the UI stores floors and peaks. Calibration here means measuring browser axis values at rest and extremes, not OS recalibration UI, DeviceHub will not write new calibration blobs into the operating system. The Gamepad API only reports what the browser and OS expose after their own filters, and mapping may differ for non-standard pads, so always confirm axis indices via Controller Mapping Test when numbers seem attached to the wrong stick. Because the workflow is install-free, school and corporate machines can still produce drift evidence. Parents get printable-in-spirit numbers (“left X rest 0.14”) for marketplace disputes. Repair shops photograph rest panels beside the physical pad serial.

What this tool does

The page samples axes (and trigger values when exposed as buttons with analog value) during guided rest and extreme phases, displaying current, min, max, and rest snapshots. Visual cues tell you when to leave controls alone versus when to deflect fully. Reset clears the capture set for a fresh pass after cleaning. It does not apply deadzones, save profiles, or invoke OS calibration APIs. Pair with Joystick Test for live plotting, Trigger Test for LT/RT meters, Mapping Test for index identity, and Gamepad Test for digital buttons. Guidance repeats that non-zero rest is diagnostic data for drift conversations, while clipped extremes inform wear or firmware limit discussions. Exporting is manual via screenshot or notes, nothing is auto-uploaded. Multi-pad setups require selecting the correct Gamepad index before capture. The mental model is a structured clipboard for axis evidence, not a replacement for manufacturer hall-effect tuning software.

When to use it

Use Calibration Test when stick drift is subtle on live plots, when you need rest/extreme numbers for a warranty ticket, after attempting OS calibration and wanting to see browser-visible outcomes, and when tuning deadzone defaults in your own web game. Prefer Joystick Test for qualitative circle watching, and OS utilities when you intentionally need to write calibration. Run a rest capture after the pad warms in your hands, some modules drift more after heat. Esports staff can log loaner pad rest values before and after an event to catch emerging drift. After remappers change, recapture, virtual Standard pads often show different noise floors. Kids’ sticky residue cases should capture before and after careful cleaning. Bluetooth versus USB rest noise can differ; capture both if the complaint is wireless-only creep. Developers should record browser name with captures because clamping behavior is not identical across engines. Marketplace sellers can attach rest screenshots to listings as transparency for used pads. After replacing stick modules, capture a new baseline before the customer walks away. Classroom sets benefit from a laminated “max acceptable rest” threshold tied to numbers from this page rather than vague “feels drifty” reports. Tournament gear managers should recapture after shipping cases, mechanical shock often shifts rest before players notice in-game creep.

How it works

Samples come from getGamepads() axis and trigger value fields polled while you follow on-screen phases. Rest statistics may average several frames to reduce single-frame noise; extremes track min/max across the sweep window. DeviceHub cannot access OS calibration APIs to reset centers, that requires platform settings outside the browser. Honest copy states this boundary so users do not expect a “Apply calibration” button that web security would not allow anyway: calibration here is browser axis values at rest/extremes, not OS recalibration UI. No Permissions API prompt is needed. Safari/mobile gaps may prevent complete axis lists. Steam Input and vendor tools can alter rest offsets before values reach the page; capture with remappers disabled for hardware-faithful numbers. HTTPS is standard for DeviceHub; gamepad reads need no media permissions. Data remains local. Mapping non-standard pads may place sticks on unexpected indices, verify first. Timestamp fields are not used as USB poll proofs. If rest values change after you open the OS wizard, recapture here to see what the browser now receives; that delta is often the entire point of the exercise. The Gamepad API only reports what the browser and OS expose after their filters, DeviceHub will not subtract a deadzone you wish existed. Keep the tab foregrounded during capture so background throttling does not undersample noisy rest channels. Compare captures only on the same connection mode and remapper state, or the numbers become stories about software stacks rather than modules.

Step-by-step instructions

1. Open Controller Calibration Test over HTTPS, connect the pad, press a button to wake it, and select the correct Gamepad if more than one is present.
2. Follow the rest phase: do not touch sticks or triggers while the page records resting axis and trigger values, then note any channel far from zero.
3. Follow the extremes phase: slowly move each stick to all cardinal limits and fully pull triggers, allowing min/max capture to update to the browser-visible peaks.
4. Compare left versus right and stick versus trigger channels; screenshot or write down rest and extreme sets for your RMA, deadzone config, or support call.
5. If indices look wrong, open Controller Mapping Test, then optionally try OS calibration utilities separately, return here afterward to see whether browser values changed.
6. Close the tab when finished; no permission revoke is required because the Gamepad API never prompted for a privileged grant.

Common problems

Non-zero rest is usually drift, debris, or remapper offset, not a failure of DeviceHub math. Extremes below ±1 are common with deadzones and wear; report the actual peaks. Expecting an OS-style “save calibration” button misunderstands browser capabilities, use system settings for that. Wrong axis labels mean mapping confusion. Bluetooth noise inflates rest variance, prefer USB for RMA evidence. Mobile browsers may omit axes. Two devices connected lead to capturing the idle pad, watch live values while you move. After OS calibration, if browser values are unchanged, the wizard may not apply to the path the browser uses (especially with remappers). Fight sticks without analog sticks will show empty or flat stick axes, that is expected. Do not confuse this tool with DualSense adaptive trigger calibration apps. Touching the stick during the rest phase contaminates floors, restart that phase. Sweeping too fast can miss true peaks if polling is coarse; move deliberately to each cardinal and corner. If Joystick Test looks centered but rest capture shows offset, you may be averaging noise differently, trust the numeric rest panel for tickets and the live plot for intuition.

Privacy explanation

Rest and extreme samples stay in your browser session. DeviceHub does not upload calibration captures, drift histories, or controller identifiers. No microphone or camera permission is requested. Closing the tab clears on-page statistics. Shared workshops can run captures for hardware triage without accounts. Private windows help avoid remapper interference. When sharing screenshots publicly, you may crop id strings if desired. Nothing continues sampling axes after you navigate away. Clearing site data is unnecessary for “revoking” access because the Gamepad API never stored a privileged permission grant for this diagnostic.