RFOXiA LogoRFOXiA Club
← Back to DevHub

MultiNav Pro+ sensors - accelerometer range/sensitivity config options?

Marie HortonJune 15, 2026
Hey all, working on a vibration monitoring setup for some industrial equipment and I'm trying to figure out how configurable the accelerometer on the sensors module actually is. Specifically wondering if I can switch between different G ranges - like does it support ±2g, ±4g, ±8g, ±16g or is it locked to a fixed range out of the box? The equipment I'm monitoring has some pretty aggressive vibration spikes so I need headroom, but I also want decent sensitivity during idle periods to catch early-onset resonance patterns before they get bad.
💬 2 replies👍 0 likes👁 0 views

💬 Want to join this discussion?

Join the Community on RFOXiA Club →

Replies

Joseph HawkinsJune 15, 2026
The MultiNav Pro+ accel is configurable - you can set it to ±2g, ±4g, ±8g, or ±16g via the sensor config registers, so you're not stuck with a fixed range. For your use case I'd honestly look at switching ranges dynamically based on a threshold if you want the best of both worlds, it's a bit fiddly to set up but totally doable with the SDK. Grab the datasheet from the dev portal if you haven't already, the register map section covers all the sensitivity tradeoffs pretty clearly.
AdamJune 15, 2026
@Marie Horton yeah the dynamic range switching approach is exactly what I'd recommend for your use case — the tricky part is tuning your threshold so you're not flip-flopping between ranges constantly during borderline vibration, which can create noise in your data. A simple hysteresis band around your switch point helps a lot there.
 
One thing worth thinking about for early-onset resonance detection specifically: even at ±16g you'll have enough resolution to catch frequency patterns, but if you're doing FFT analysis on the data you'll want to make sure your sampling rate is high enough to capture the resonance frequencies you care about before they climb. The sensors module runs the accel alongside gyro and magnetometer so just be mindful of how you're scheduling your reads if you're pushing high sample rates.
 
The AI Firmware Builder in the Dev Hub is actually pretty decent for scaffolding this kind of conditional range-switching logic — describe your threshold behavior and it'll get you 80% of the way there without having to wrestle the register map from scratch. Still worth cross-referencing the datasheet for the exact sensitivity values per range though.

💬 Want to join this discussion?

Join the Community on RFOXiA Club →