TECHNOLOGY IN ACTION
V ADVERTORIALS
Silicon Labs Unveils BG2B, Its Lowest-Power Bluetooth LE SoC
Innovator in low-power wireless connectivity, Silicon Labs, today (4 August) announced the BG2B, its next Series 2 Bluetooth Low Energy (LE) wireless SoC designed to help developers build smaller, more secure and longer-lasting battery-powered IoT devices by providing the indus- try’s best combination of power efficiency, security and integrations. As Bluetooth LE applications become more sophisticated, developers are challenged to add capabilities such as secure ranging, location awareness, advanced security and richer peripheral integra- tion while preserving battery life and compact designs expected of today’s wireless IoT devices. BG2B addresses these demands with Silicon Labs’ lowest-power Bluetooth architecture, a complete feature set for Bluetooth Channel Sounding, Secure Vault High security and integrated peripherals including CAN-FD, LED drivers and dual ADCs, in a single highly integrated platform.
Designed for applications including secure ranging, asset tracking, electronic shelf labels (ESLs), smart home, industrial monitoring and vehicle diagnostics, BG2B helps developers extend battery life while preparing for more demanding Bluetooth LE applications. “Bluetooth LE is moving beyond basic connectivity into secure ranging, proximity awareness and location-aware experiences, while customers still need the low power, small form factor and cost efficiency that made Bluetooth the foundation of battery-powered IoT,” said Daniel Cooley, SVP and CTO, Silicon Labs. “BG2B brings these requirements together in a single platform, combining our lowest-power Bluetooth LE architecture to date with advanced Channel Sounding, Secure Vault High security and integrated peripherals that help customers build more capable, connected products with fewer external components.”
A new standard for ultra-low-power bluetooth
Battery life remains one of the biggest challenges for battery-powered IoT devices as products continue adding more sensing, intelligence and wireless capabilities. BG2B features a dual-output DC-DC power architecture and multi-core design that significantly improves efficiency across active, receive and sleep modes.
BG2B is the lowest-power Bluetooth LE device in Silicon Labs’ portfolio, delivering 14 per cent-15 per cent lower MCU active current, lower Bluetooth receive current and 1.1 µA EM2 sleep current with RAM retention as compared to the Silicon Labs’ previous lowest power Bluetooth LE SoC, enabling longer battery life for sleepy products such as wireless sensors, asset tags, smart locks, remotes, wearables and electronic shelf labels.
Enhanced channel sounding with expanded peripherals For developers building location-aware products today, BG2B supports advanced Bluetooth Channel Sounding capabilities including Mode 3, Normalized Attack Detector Metric (NADM), and Inline Phase Correction Term (Inline PCT). Designed to meet Apple and Google Bluetooth Channel Sounding specifications, BG2B helps developers build interoperable products across the industry’s leading mobile ecosystems, supported by Silicon Labs’ complete Channel Sounding development solution, including a royalty-free ranging library, software, tools and engineering support.
Building on previous Silicon Labs Channel Sounding solutions, BG2B delivers even lower energy per ranging event through shorter Channel Sounding step timings, lower active current and lower Bluetooth LE receive current.
SILICON LABS
https://www.silabs.com/
Why Rust Is Emerging in Safety-Critical Systems –
And Why It Matters Now Cybersecurity is no longer a feature that can be layered onto a system later. In safety-critical industries like automotive, defense, robotics, and industrial automation, security is now foundational to functional safety.
That reality is driving a major shift in how modern systems are built – and increasingly, organizations are turning to the Rust programming language.
Rust’s memory-safe architecture helps eliminate entire classes of vulnerabilities before code even runs. In fact, memory-related issues are estimated to account for roughly 70% of critical security flaws in systems software. For teams building distributed, real-time systems, that statistic is difficult to ignore.
When your architecture already depends on proven, production-grade communication infrastructure, you want every element of that system to support development velocity.
But real-world adoption is rarely a flip of a switch. Teams face challenges when they try to move to Rust inside existing, often large systems based on the Data Distribution Service (DDS®) standard. These challenges include:
• Training and ramp-up time, • Integration friction with existing C/C++ stacks, • Differences in serialization and code-generation tooling, and • The organizational risk of rewriting production components all at once.
In short – teams want the safety benefits of Rust, but they also need a safe, low-risk path to get there. That’s why we built the RTI Connector for Rust.
A Practical Bridge Between Rust and DDS To help developers begin the journey, RTI is introducing Connector for Rust – an early-access entry point that allows teams to experiment with Rust and DDS-based messaging, together, through RTI Connext.
RTI is taking a pragmatic approach: providing a lightweight, configuration-driven Connector that enables developers to publish and subscribe using familiar DDS semantics while minimizing integration complexity.
The goal is simple: Make it easy to learn, evaluate, and experiment – without forcing production commitments. By exposing the Connector source code, developers gain transparency into how the integration works and the flexibility to extend it for their own environments.
RTI
https://www.rti.com/ JULY/AUGUST 2026 | ELECTRONICS FOR ENGINEERS 41
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46
