- 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
- :
- 2409419_en-US
2409419_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2409419_en-US
2409419_en-US
Following up on the SmartFob power profile — two questions I couldn't resolve from AN14554.
The SmartFob configuration includes a motion sensor alongside BLE, UWB and the secure element. How is motion typically used in the power model? Specifically, does a production smart fob continue BLE advertising while stationary, or is advertising suppressed or slowed until motion is detected?
Second, does the estimator output an integrated standby current for a typical configuration? AN14554's advertising figures are measured at 100 ms, and I'm trying to understand the realistic 24/7 standby budget for coin-cell operation.
Thanks.
Hello, hope you are doing well.
I would recommend checking the "SmartFob BLE(KW47)+UWB(R5) Ranging - Power Consumption Estimator Tool v1.0" which is included under the Kinetis (KW3x/4x) Power Profile Tools for Automotive page.
This tool models the SmartFob power profile across four use cases and defines when BLE advertising is active versus suppressed.
In the "stationary" state (Use Case 1), there is no BLE advertising. The KW47 remains in Deep Sleep 2, while the motion sensor operates in standby mode. BLE advertising resumes after motion is detected, as mentioned for Use Cases 2 and 3.
For standby current information specific to the KW47 + UWB Ranger5 + motion sensor SmartFob configuration, refer to the Consumption Table at the top of the estimator worksheet. The table indicates a system level standby current of approximately 3.77 µA at a 3 V coin-cell supply, with the value broken down by subsystem as well.
Best regards,
Sofia.