Hardware Desk Breakdown: Axis Pairing, Ranges and SafeSPI in ST's Combo Sensor IC Platform
By Sarah Chen, Tech Daily Hardware Desk
Before any product headline reaches a bench, a motion-sensing design review usually asks four narrow questions: which motion axes does the part actually read, which amplitude class does it survive, do the numbers hold across temperature, and how does the host talk to it. The new combo sensor platform from ST answers all four in silicon rather than leaving them to a board designer who would otherwise have to co-locate, cross-calibrate and fault-check two separate components.
The engineering point here is consolidation: multi-axis accelerometers and angular-rate sensors share one package. The stated commercial point is reach — carrying active and passive safety functions plus driver-assistance features beyond premium vehicles and down into mass-market categories, where bill-of-materials count and board area decide what ships.
Part-level view: what the launch batch pairs together
The launch batch is the first four offerings from ST after its integration of NXP's sensors division, and the differences between them are confined to two variables: which angular-rate axis is on board, and which accelerometer axes plus amplitude class come with it. Read as a matrix instead of a list, the family becomes a simple selection tree.
| Device | Angular-rate axis | Accelerometer axes | Amplitude class |
|---|---|---|---|
| NCS1012BAEP | z-axis (yaw) | xy | low-g |
| NCS1012CAEP | x-axis (roll) | yz | low-g |
| NCS1012EAEP | x-axis (roll) | xy | medium-g |
| NCS10135AEP | z-axis (yaw) | xyz | low-g |
Two observations fall straight out of that table. First, no part in this batch reads yaw and roll simultaneously — the rate sensing is either a z-axis (yaw) channel or an x-axis (roll) channel, so a design that needs both still has to plan for two nodes or accept partial coverage. Second, full three-axis acceleration appears only once, on NCS10135AEP; the other three devices are axis-limited by design.
The specification block: values to quote in a design review
The numbers below are the ones that matter for headroom budgeting, filter placement and thermal assumptions.
| Parameter | Specified value | How to interpret it |
|---|---|---|
| Angular-rate full scale | ±125 dps, ±250 dps or ±350 dps | Three selectable rate ranges on the same device family; dps is degrees per second, so choose against the fastest body rotation your function must resolve without clipping. |
| Rate-channel output filter | Integrated low-pass filtering with 12.5–400-Hz cutoff options | Cutoff is selectable, not fixed — useful when you want to trade response time against vibration-driven noise from the chassis. |
| low-g accelerometer span | ±1.50 g to ±34 g | Tilt, dynamics and rollover-style motion; the sensible starting point for stability and attitude functions. |
| medium-g accelerometer span | ±15.5 g to ±150 g | Crash-pulse territory; the medium-g versions use an independent signal chain to minimize noise, so treat the amplitude class as a different front end, not merely a wider range. |
| Accelerometer behaviour over temperature | Low offset and low drift across the automotive range, with integrated low-pass filtering on both types | Offset and drift, not just span, are the parameters that decide whether a threshold needs field recalibration. |
| Operating temperature | −40°C to +105°C | Cold-start through cabin-bay heat soak; verify your mounting location stays inside that window. |
| Diagnostics and host interface | Built-in diagnostics; SafeSPI support | SafeSPI is a serial peripheral interface specified for automotive safety use, so bus-level self-checking is part of the silicon rather than an external wrapper. |
| Production package | 24-pin QFN packages with wettable flanks | Common footprint across the family, which keeps layout assumptions and solder-joint visibility consistent when you move between axis or amplitude variants. |
Function-to-sensor mapping
The platform is positioned around five use cases. Mapped against the specification block, each one leans on a different parameter:
- Crash protection — amplitude class first: the medium-g path, given the independent signal chain and the ±15.5 g to ±150 g span.
- Rollover detection — roll rate plus lateral acceleration, which points at the x-axis rate variants rather than the z-axis ones.
- Airbag deployment — sustained high-amplitude acceleration; the axis set carried by the part (xy, yz or xyz) determines how much of the crash vector you actually observe.
- Vehicle stability control — yaw rate against the low-g xy pair, with the 12.5–400-Hz filter choice used to reject road vibration while keeping loop delay acceptable.
- Radar beam stabilization — the rate channel as a motion reference for keeping the beam aligned while the host platform rotates or flexes.
Common misconceptions at the parts-selection stage
- “Combo means every axis.” It does not. Combo here means one rate axis plus an accelerometer set in one package, and the pairing differs per device — pick the axis map before the amplitude class.
- “medium-g is just a stretched low-g part.” The two classes are separated by signal chain, not only by range, and noise behaviour is the reason.
- “On-chip filtering means I can skip filtering decisions.” The cutoff is selectable across 12.5–400-Hz, which is a design choice you still have to make against your control loop.
- “Any SPI controller works, so the safety interface is paperwork.” SafeSPI plus internal diagnostics exists so the host can interrogate the sensor's health, not just read samples; that changes firmware scope, not only the bill of materials.
- “Temperature rating is a storage concern.” The −40°C to +105°C figure is the specified operating window, and offset and drift are characterized across it — engine-bay or exterior mounting decisions should be checked against that, not against a nominal bench temperature.
Action recommendations for hardware and procurement teams
- Step 1 — fix the motion axis. Yaw-driven logic narrows you to the z-axis parts; roll-driven logic narrows you to the x-axis parts.
- Step 2 — bound the amplitude. Body dynamics live in the low-g class; impact events live in the medium-g class. Under-specifying here is the most common re-spin.
- Step 3 — count the axes you need to see. If a function must observe vertical acceleration as well, the xy and yz variants will not cover it, and only NCS10135AEP carries an xyz low-g set in this batch.
- Step 4 — validate the bus early. Confirm that your host controller and safety architecture actually exercise SafeSPI and the built-in diagnostics; the interface is the reason these parts are pitched at safety functions.
- Step 5 — lock the mechanical assumptions. All variants currently ship in 24-pin QFN packages with wettable flanks, so footprint, stencil and inspection setups transfer across the family while you consolidate SKUs.
- Step 6 — record the range choice. Log which of ±125 dps, ±250 dps or ±350 dps, and which filter cutoff, your firmware configures, so field returns can be traced to a setting rather than to a device.
Data citation and scope of this breakdown
Every figure quoted above — the angular-rate ranges, the filter cutoff options, the low-g and medium-g spans, the operating temperature window, the package form and the interface support — is taken directly from the platform disclosure carried in the source release from STMicroelectronics. Tech Daily's hardware desk has not added independent lab measurements, pricing, availability dates or certification claims to those values, and readers should treat performance comparison against competing parts as out of scope until first-silicon data exists.
Bottom line
Consolidating a rate channel and an accelerometer set behind one host interface removes real integration work, and the value now hinges on how cleanly a designer can match axis pairing and amplitude class to a single function. For stability and rollover programs the low-g variants are the natural entry point; for crash-related sensing the medium-g path is the one worth evaluating first, precisely because its signal chain is separate. Teams standardizing on SafeSPI-enabled parts should request the diagnostics documentation alongside the datasheet — the interface and self-check behaviour are what separate this class of sensor from generic motion parts on the same footprint.
Questions about this breakdown or hardware coverage in general? Reach the Tech Daily team at hello@techdaily.com.