Electronicseng Semiconductors: Mapping ST's NCS Combo Motion ICs for Automotive Crash, Roll, and Radar Alignment
Motion-sensing decisions in automotive electronics now depend as much on axis pairing and production constraints as on raw measurement capability. ST has introduced an automotive sensor platform that combines multi-axis accelerometers and angular-rate sensors in one package. The stated goal is to broaden active and passive safety and driver-assistance coverage across vehicle categories, from premium models to volume-market vehicles. For engineers reading Electronicseng's Semiconductors column, the useful analysis is how the first four part positions, measurement ranges, interface support, and package format translate into design and procurement choices.
What a combined motion IC changes in vehicle architecture
Classic designs often separated accelerometer functions and angular-rate functions because each sensor type addressed a different part of a vehicle dynamics chain. The platform described here brings those sensing types together in one component package. The disclosed application set includes crash protection, rollover detection, airbag deployment, vehicle stability control, and radar beam stabilization. These are different system paths, but the shared technical challenge is that the correct motion axis, the correct range, and the correct filtering behavior must be available before the host software can make a reliable decision. That is why the axis combination table is more important than the marketing concept of a combo sensor.
For semiconductor integration teams, this also changes the review scope. A combined sensor IC is not only a measurement part; it is also a diagnostics node, an interface endpoint, and a mechanical package. The platform is described as including built-in diagnostics and supporting SafeSPI, an SPI interface intended for automotive safety use. Those statements should be treated as design constraints: the host controller, software startup, fault handling, and board-level testing all need to align with the selected part.
Device map: axis pairing matters more than the family name
After ST's integration of NXP's sensors division, the first four offerings are best understood as a shortlist for system teams that must match yaw or roll rate sensing to the correct accelerometer axes. The part names are not interchangeable: each maps a specific angular-rate axis to a specific accelerometer axis set and range class.
- NCS1012BAEP pairs a z-axis yaw angular-rate sensor with an xy low-g accelerometer.
- NCS1012CAEP pairs an x-axis roll angular-rate sensor with a yz low-g accelerometer.
- NCS1012EAEP pairs an x-axis roll angular-rate sensor with an xy medium-g accelerometer.
- NCS10135AEP pairs a z-axis yaw angular-rate sensor with an xyz low-g accelerometer.
| Part | Rate axis | Accelerometer axes | Range 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 |
Measurement ranges, filtering, and temperature envelope
The disclosed angular-rate full-scale options are ±125 dps, ±250 dps, and ±350 dps. Integrated low-pass filtering is provided with 12.5–400-Hz cutoff options. Temperature operation is specified from −40°C to +105°C. These values form the core selection window. A stability-oriented path may benefit from a narrower range where resolution is prioritized, while a broader dynamic event may need the upper range; the platform leaves that decision explicit instead of hiding it in one generic rate output.
The accelerometer disclosures are split by class. Low-g parts span ±1.50 g to ±34 g. Medium-g parts span ±15.5 g to ±150 g and are described as using an independent signal chain to minimize noise. Both classes are described as maintaining low offset and drift across the automotive temperature range and as including integrated low-pass filtering. For engineers, the range split is the practical takeaway: the same platform label does not mean the same measurement ceiling, nor does it guarantee identical noise treatment across classes.
Diagnostics, SafeSPI, and production footprint
Built-in diagnostics and SafeSPI support are the two interface features highlighted for this initial release. The package information is equally concrete: the combo sensors are currently manufactured in 24-pin QFN packages with wettable flanks. In a manufacturing review, that package choice affects placement density, solder inspection, and the ability to verify wetting behavior after assembly. In a system review, SafeSPI support affects host-side software assumptions, command sequencing, and fault handling. The part selection therefore cannot be separated from the interface and package selection.
Range and configuration comparison table
| Sensing side | Disclosed range or option | Design implication |
|---|---|---|
| Angular rate | ±125 dps, ±250 dps, or ±350 dps | Match range to expected motion event without unnecessarily limiting dynamics. |
| Angular-rate filtering | 12.5–400-Hz cutoff options | Confirm bandwidth against the host control loop and the expected vibration environment. |
| Low-g acceleration | ±1.50 g to ±34 g | Use when the application fits the disclosed low-g range. |
| Medium-g acceleration | ±15.5 g to ±150 g | Use when higher acceleration span is needed; the medium-g versions are described as using an independent signal chain to minimize noise. |
| Temperature | −40°C to +105°C | Validate thermal margin at the mounting location, not only ambient specification. |
Common misconceptions
The first misconception is that a combo sensor platform is one device with one measurement set. The disclosures show multiple angular-rate spans and two accelerometer classes. The angular-rate ranges are ±125 dps, ±250 dps, and ±350 dps; the low-g accelerometer span is ±1.50 g to ±34 g; and the medium-g accelerometer span is ±15.5 g to ±150 g. A team that assumes one range fits every motion function will likely revisit the selection later.
The second misconception is that integrated filtering makes bandwidth review unnecessary. The platform provides 12.5–400-Hz cutoff options on the angular-rate side, and the accelerometer types are also described as including integrated low-pass filtering. Those features help, but they do not remove the need to confirm that the selected cutoff matches the host's control loop and the vehicle's dynamic environment.
The third misconception is that SafeSPI and built-in diagnostics complete the safety path. The parts support SafeSPI, an SPI interface intended for automotive safety use, and include built-in diagnostics, but system behavior still depends on host implementation, startup sequence, software error handling, and integration testing. The component provides part of the architecture; it does not replace validation.
Action recommendations for engineers and buyers
- Start with the required rate axis: yaw or roll. Then confirm the accelerometer axes: xy, yz, or xyz.
- Use NCS1012BAEP, NCS1012CAEP, NCS1012EAEP, or NCS10135AEP as the initial shortlist, and do not substitute one part for another unless the axis pairing and range class both fit.
- Check whether the angular-rate requirement fits within ±125 dps, ±250 dps, or ±350 dps.
- Decide whether the acceleration requirement is low-g or medium-g, remembering that the disclosed spans differ.
- Review the 12.5–400-Hz filtering options against the bandwidth budget and noise environment.
- Validate thermal assumptions against −40°C to +105°C operation at the actual mounting point.
- Confirm SafeSPI integration at the host and software level, including diagnostics and error handling.
- Plan for 24-pin QFN packages with wettable flanks in placement, reflow, and inspection processes.
FAQ for semiconductor and automotive teams
Q: Is this an ST product platform?
A: Yes. The article describes it as an ST automotive sensor platform. The initial offerings follow ST's integration of NXP's sensors division.
Q: What sensing functions are combined?
A: Multi-axis accelerometers and angular-rate sensors are combined in one package.
Q: How many initial devices are named?
A: The first four offerings are named: NCS1012BAEP, NCS1012CAEP, NCS1012EAEP, and NCS10135AEP.
Q: What angular-rate ranges are disclosed?
A: ±125 dps, ±250 dps, or ±350 dps.
Q: What accelerometer ranges are disclosed?
A: Low-g versions span ±1.50 g to ±34 g; medium-g versions span ±15.5 g to ±150 g.
Q: What temperature range is specified?
A: Operation is specified from −40°C to +105°C.
Q: Does the platform support a safety interface?
A: Yes. It supports SafeSPI, described as an SPI interface intended for automotive safety use.
Q: What package is used in current production?
A: The combo sensors are currently manufactured in 24-pin QFN packages with wettable flanks.
Procurement and integration guidance
For hardware buyers and program managers, the key risk is treating the first four part names as a single line item. They are not; each has a distinct axis pairing and, in some cases, a distinct acceleration class. A procurement review should therefore begin with the application function, then confirm the part that matches both axis pairing and range class. A supply-chain discussion that only references a generic combo sensor label may produce samples that are mechanically and electrically usable but systemically wrong for the target function.
For engineering managers, the qualification sequence should be explicit. First, lock the axis requirement. Second, lock the range and temperature requirement. Third, confirm the filtering and diagnostics behavior. Fourth, review the package and manufacturing flow. Fifth, test the SafeSPI path on the host. That sequence keeps the semiconductor component selection aligned with the vehicle function, rather than allowing package or interface details to become late-stage surprises.
Bottom line for Electronicseng readers
The platform is relevant because it provides several clearly separated motion-sensing options inside one automotive combo sensor family. ST's initial release, anchored by NCS1012BAEP, NCS1012CAEP, NCS1012EAEP, and NCS10135AEP, gives system teams a practical decision tree: yaw or roll, low-g or medium-g, one axis set or another, and a 24-pin QFN package with wettable flanks for production. The stated application set—crash protection, rollover detection, airbag deployment, vehicle stability control, and radar beam stabilization—shows why the selection cannot be treated as a commodity substitution.
Data reference: STMicroelectronics