- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2409674_en-US
2409674_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2409674_en-US
2409674_en-US
Dear NXP Support Team,
Hello,
We are currently working on a project to develop a 100 kW-class PMSM inverter drive module.
Our target specifications are approximately:
DC-link voltage: 800 V
Motor phase current: 250 Arms
Motor type: PMSM
Power level: approximately 100 kW
During our research, we became very interested in NXP's "3-Phase Permanent Magnet Synchronous Motor Control Development Kit with S32K396."
Since we need to develop our own 100 kW power stage, our plan is to use only the S32K396-based control board from the development kit and design the gate-driver and IGBT power stage ourselves.
After reviewing the schematics of the development kit, our understanding is that the control board interfaces with the power stage through external connectors, including:
PWM signals for controlling the three-phase inverter
Resolver-related signals
Three-phase current sensing signals
DC-link voltage sensing
DC-link current sensing
Could you please confirm whether our understanding is correct?
If so, our intended system configuration would be as follows:
Use the NXP S32K396 control board to generate the PWM signals for our custom 100 kW inverter power stage.
Use Hall-effect current sensors for phase-current measurement and feed the corresponding analog signals to the control board.
Implement the resolver interface circuitry by referring to the resolver circuit used in the NXP development kit/power board.
Provide the required DC-link voltage and current sensing signals to the ADC inputs of the control board.
In other words, we would like to use the existing S32K396 control board and motor-control software platform while replacing the original power stage with our own 800 V / 250 Arms inverter hardware.
We would appreciate your advice regarding the following questions:
Is it feasible to use the S32K396 control board in this configuration with a custom high-power inverter stage?
Are there any interface requirements, limitations, or precautions that we should consider when connecting an external gate-driver/power stage to the control board?
Are there any application notes, reference designs, schematics, software examples, or other technical documents that would be helpful for developing a 100 kW-class PMSM inverter based on the S32K396?
Does NXP offer, or can NXP recommend, any reference design or evaluation platform for an approximately 100 kW, 800 V PMSM inverter?
Any additional information or recommendations would be greatly appreciated.
Thank you for your support.
Best regards
Hyeong Mun Seon
Hi,
Your understanding is generally correct. The S32K396 controller can be used independently of the low-voltage inverter included with the MCSPTR2AK396 kit, provided the required feedback signals (phase currents, DC bus voltage/current, rotor position, fault signals, etc.) are adapted to the new power stage interface. The MCSPTR2AK396 kit is primarily intended as a low-voltage motor-control development platform and software enablement kit.
For traction-class applications around 100 kW, you may also want to review NXP's EV traction inverter reference designs (EV-INVERTERGEN1 / EV-INVERTERGEN2), which are intended for high-voltage, high-power electric vehicle inverter applications and provide a more relevant reference point than the MCSPTR2AK396 evaluation kit. The S32K39 family is one of the supported motor-control platforms within NXP's traction inverter ecosystem.
The MCSPTR2AK396 documentation (AN14481) can still be useful as a reference for the PMSM FOC software architecture, peripheral configuration, current sensing, resolver integration, and FreeMASTER/MCAT support.
You can find additional information on the EV traction inverter platforms here: NXP EV Power Inverter Solutions.
BR, Petr