feat: Hall Effect axis calibration (v1.1)#2
Conversation
Add normalizeAxis/normalizeTrigger pre-step before deadzone/gamma. Defaults are identity — no behaviour change for existing users. HE users set STEER_CENTER/RANGE and GAS/BRAKE REST/MAX to match their controller's actual raw axis values.
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 34 minutes and 37 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Quality Check ✅ Passed
|
1 participant
What
Adds per-axis calibration for Hall Effect controllers. HE joysticks and triggers use magnetic sensors that are more precise than potentiometers but may have a raw rest position that isn't exactly 0.0 and a physical range that doesn't reach exactly ±1.0.
How it works
Two new functions in
lib.luanormalize raw axis values before the existing deadzone/gamma pipeline:normalizeAxis(raw, center, range)— for the steering stick: subtracts the rest offset, divides by the physical range, clamps to [-1, 1]normalizeTrigger(raw, rest, maxVal)— for gas/brake triggers: maps [rest, maxVal] → [0, 1]With all defaults (center=0, range=1, rest=0, max=1) these are identity functions — no behaviour change for existing users.
New parameters
Six new values in
config.lua(and live via the Config app):STEER_CENTERSTEER_RANGEGAS_RESTGAS_MAXBRAKE_RESTBRAKE_MAXConfig app
New Calibration section at the top of the app window. Window height increased from 680 → 800 to fit.
Finding your values
Load AC, open the CM log, and read the
[MyGamepadFX] Axes:startup diagnostic line. The values shown are your raw rest positions. For max values, watchdebug overlaywhile pushing to full deflection.