Українською
  In English
EDN Network
Audio AI in wearables: Enabling smarter, more responsive devices

Advances in AI are turning wearables into intelligent companions that understand users, interpret their surroundings, and respond naturally in real time. From smartwatches and earbuds to smart glasses, hearing devices, smart rings, AI-enabled necklaces, and wearable pins, these devices are increasingly able to understand spoken language, recognize environmental sounds, and provide contextual assistance.
Instead of waiting for users to tap a screen or press a button, audio AI combined with edge AI processing and ultra-low-power MEMS microphone technology enables wearable devices to listen intelligently, recognize meaningful sounds, and interact with users in ways that are effortless. Rather than functioning as passive electronics, wearables are becoming active assistants that help organize information, improve accessibility, enhance safety, and simplify everyday tasks.

Figure 1 Audio AI enables wearable devices to listen intelligently, recognize meaningful sounds, and interact with users in an effortless way. Source: TDK InvenSense
Delivering these experiences requires much more than simply adding a microphone. Audio quality, power consumption, processing architecture, and sensor integration all play critical roles in determining whether an AI-powered wearable feels genuinely useful or quickly becomes frustrating.
Why audio is becoming the natural interface for wearables
Wearable devices don’t have large displays or physical keyboards. They rely on voice as human to machine interface. Emerging wearable categories like AI-enabled pins, necklaces, and other “AI jewelry” may not include a display at all.
Voice commands, wake words, spoken reminders, AI assistants, and handsfree control bridge the gap. Voice provides a more natural interface between the user and the device. Speaking is faster than typing, more intuitive than navigating menus, and allows users to interact while performing various activities.
Audio also adds a new layer of contextual awareness. No longer limited to recognizing commands like “play music” or “set a timer,” modern audio AI allows devices to interpret both user intent and the surrounding environment. Imagine speaking a shopping list into your wearable while preparing dinner.
Instead of opening an app to type in each item, the device records the information conversationally and later reads it back while you’re shopping. Simple interactions like these reduce cognitive load because users can communicate naturally instead of adapting their behavior to the technology.
Audio AI can also recognize important environmental sounds, allowing wearables to become more aware of the world around them. Future devices may detect emergency vehicle sirens, smoke alarms, glass breaking, approaching traffic, or someone calling the wearer’s name, providing notifications about important sounds that might otherwise go unnoticed.
These capabilities are also valuable for improving accessibility. For example, the WeWalk Smart Cane 2 combines microphones with multiple sensor technologies to provide richer environmental awareness for people with visual or hearing impairments. Rather than relying on a single sensing modality, these devices combine audio with additional sensor inputs to create more useful contextual information for the user.

Figure 2 WeWalk Smart Cane 2, powered by Gemini, allows users to ask questions about their surroundings, learn about landmarks, or get everyday information. Source: TDK InvenSense
MEMS microphones: The front end of the audio AI experience
No matter how advanced an AI model may be, its performance depends heavily on the quality of the audio it receives. Poor signal quality reduces speech recognition accuracy, increases false activations, and ultimately creates a frustrating user experience. MEMS microphones have become the preferred solution for wearable audio AI because they combine strong acoustic performance with exceptionally small size, low weight, and minimal power consumption.
Size, weight, and style
For wearable designers, physical dimensions matter enormously. Every cubic millimeter saved creates room for larger batteries, additional sensors, or more processing capability while helping create products comfortable enough for all-day wear. Size also affects aesthetics. Bulky designs limit industrial design flexibility, making it harder to create wearables people actually want to wear.
Power consumption and privacy
Consumers increasingly expect wearable devices to remain available throughout the day—or even multiple days—without charging. Continuous listening has traditionally been a significant drain on battery life, making truly natural voice interaction difficult to achieve. This is where ultra-low-power microphone architectures become critical to enabling “always-on” functionality without requiring always-on power consumption.
The acoustic activity detection (AAD) feature available in TDK microphones enables continuous monitoring of the environment for relevant acoustic activity while consuming only a fraction of the power required by the primary processor. Rather than keeping the entire AI system awake continuously, the microphone itself identifies meaningful audio events and wakes the application processor only when necessary. Data is processed locally improving battery life and privacy.
Instead of pressing buttons or manually activating voice assistants, users simply begin speaking, a much more natural user experience. The device remains responsive while preserving battery life for the activities that matter most.
Low power microphones and AAD features are also important in enabling increased privacy, when combined with edge computing, by processing information locally in the device.
Moreover, processing speech locally allows many interactions to remain entirely on the device instead of being uploaded to external servers. This minimizes unnecessary data transmission while giving users greater confidence that sensitive conversations remain private.
By allowing, via the microphone’s AAD feature, only relevant sounds to wake higher-level processing, and by performing AI inference locally, wearable devices achieve faster responses, longer battery life, and greater privacy.
Ultrasonic
Some MEMS microphones also extend beyond the normal range of human hearing by detecting ultrasonic frequencies. This expands the range of sensing applications beyond conventional speech recognition, enabling additional human-machine interaction methods while opening opportunities for sensing applications that conventional microphones cannot address.
Multimodal sensing creates richer contextual awareness
The most capable wearable devices combine data from microphones with information collected by motion sensors and magnetic sensors. This multimodal approach creates a much richer understanding of user activity, surrounding conditions, and device functionality.
Rather than simply recognizing spoken commands, a wearable can understand when to interrupt, when to remain silent, and how best to present information based on what the user is doing. These systems interpret multiple environmental inputs to provide more useful guidance and situational awareness.
This type of sensor fusion is also important for immersive experiences. Motion sensors can continuously track head movement while microphones capture spatial audio information, allowing hearables and smart glasses to maintain realistic three-dimensional sound fields that move naturally with the wearer.
Edge AI enables real-time, personal, and unobtrusive experiences
Once a wearable has detected speech or another meaningful sound, it must quickly interpret what it has heard and determine how to respond. Edge AI processes AI workloads locally on or near the wearable rather than transmitting every interaction to the cloud. Rather than transmitting every interaction to cloud-based servers, it improves responsiveness and maintains privacy, while increasing battery life, thus addressing many practical concerns associated with connected AI devices.

Figure 3 Edge AI processes AI workloads locally on or near the wearable rather than transmitting every interaction to the cloud. Source: TDK InvenSense
Speed and Connectivity
Processing voice commands locally eliminates network latency, allowing users to receive answers or execute commands almost instantly. Whether dictating a reminder, asking a question, controlling music playback, or interacting with a digital assistant, the experience feels significantly more natural when responses occur in real time.
Edge processing also enables wearables to continue functioning even when network connectivity is limited or unavailable.
Smart glasses show us where wearable AI is heading
Smart glasses are a perfect example of the possibilities and challenges that arise for wearable design. They must remain lightweight enough for all-day wear, operate for extended periods on compact batteries, and integrate microphones, speakers, wireless connectivity, cameras, motion sensors, and processors within an extremely small form factor. Smart glasses may also prove to be one of the easiest wearable categories to integrate into everyday life because millions of people already wear prescription glasses or sunglasses daily.
Smart glasses rely on multiple forms of interaction rather than visual overlays alone. Audio, haptics, motion sensing, and environmental awareness will often provide less intrusive, more natural, and more useful ways to communicate information than continuously displaying graphics within the user’s field of view.
Audio AI, enabled by advanced MEMS microphones and edge intelligence, will be central to achieving that balance as voice interaction feels especially natural for these devices. It allows users to ask questions, capture notes, receive reminders, or request contextual information without reaching for another device.

Figure 4 Audio AI in smart glasses allows users to ask questions, capture notes, receive reminders, or request contextual information. Source: TDK InvenSense
A microphone’s low power and AAD extend usability and enable local processing enhancing privacy. Plus, audio feedback allows the glasses to provide assistance discreetly while minimizing visual distractions.
The future of wearable intelligence
As AI capabilities continue advancing, natural interaction will become increasingly important, making audio AI one of the defining technologies shaping the next generation of wearable devices. Achieving that vision depends on more than powerful AI models that can run continuously with adequate privacy for user data.
Success requires high-quality audio capture, ultra-low-power sensing, intelligent edge processing, and seamless integration with complementary sensing technologies. MEMS microphones form the foundation of this experience by delivering the reliable, always-available audio input that modern AI requires, while features such as acoustic activity detection enable continuous responsiveness without compromising battery life.
The challenge is no longer simply creating smaller, more powerful devices. It is creating wearables that understand people naturally while remaining responsive, energy efficient, and unobtrusive. By combining ultra-low-power MEMS microphones, edge AI, and multimodal sensing, wearable devices are becoming faster, more context-aware, more respectful of user privacy, and better suited to everyday life.
Calin Miclaus is senior director of product marketing at InvenSense, a TDK group company.
Related Content
- Soundhawk: new wearable tech enhances hearing
- Audio processing IPs tailored for power-savvy wearables
- Powering Audio with Edge AI – Pawpaw’s Hidden Strength
- Hearing is Believing: The Unsuspected Key to Smart Glasses Innovation
- MEMS Speakers Enable Full-Range Audio in Wearables with Ultrasound
The post Audio AI in wearables: Enabling smarter, more responsive devices appeared first on EDN.
In-space MOSFET failure mitigation

This Design Idea describes how a critical in-flight power supply unit issue was analyzed and resolved successfully.
The circuit described in this Design Idea is part of a spacecraft power supply unit designed to operate in the harsh radiation environment of Jupiter, where the level of cosmic radiation is exceptionally high. The block diagram of the power supply system is shown in Figure 1.

Figure 1 This blog diagram describes the power supply for a spacecraft designed for high cosmic radiation environments such as in proximity to Jupiter.
The unit contains two IRHNJ57024 N-channel MOSFETs. A radiation-hardened version of this device is the JANSR2N7480U3. The power supply provides the regulated voltages required by the onboard sensors. The nominal 28 V input voltage is converted into +5 V, +3.3 V, and −5 V output voltages to satisfy the sensors’ power requirements.
Wow the engineering world with your unique design: Design Ideas Submission Guide
The most critical section of the power supply circuit is shown in Figure 2. This section is responsible for the primary power conversion and must maintain reliable operation under the extreme environmental conditions encountered during the mission.

Figure 2 This schematic details the most critical section of the power supply circuit.
The PWM controller drives two N-channel MOSFETs via a gate-drive transformer. These MOSFETs control the power delivered to transformer T1501, which provides energy to the load. Galvanic isolation between the PWM controller and the switching stage protects the input circuitry against failures in the power stage.
During the turn-off interval of the MOSFETs, energy stored in leakage inductances of transformer T1501 is recovered and returned to the DC-link (buffer) capacitors, thereby improving the converter’s efficiency.
The power ground (NIM_PGND) and the PWM ground (DGND_DPU) are galvanically isolated from each other. This isolation protects the PWM circuitry from voltage spikes and electrical noise generated in the power stage, preventing disturbances that could affect its operation.
The switching of the MOSFETs can generate high-amplitude voltage spikes and transient noise on the power ground due to parasitic inductances and high di/dt currents. The snubbers were optimized based on measurements to suppress the effects of leakage inductance and parasitic capacitance.
The PWM controller includes a voltage-feedback input (VFB) and a current-sense input (ISEN), which are used to regulate the output voltage and implement current limiting. The RAMP_NIM2 signal is proportional to the total output current and is fed back to the PWM controller.
And now we come to the critical event alluded to in the earlier subhead. After launch, additional testing of the MOSFETs was performed. The results showed that the manufacturing lot of the N-channel MOSFETs used in the design was sensitive to high-dose-rate (HDR) radiation. Degradation was observed when the dose rate exceeded 50 rad(Si)/s, even though the devices were qualified for a total ionizing dose (TID) of up to 100 krad(Si).
Exposure to HDR radiation resulted in a reduction of the MOSFET threshold voltage (Vth) of approximately 45%. According to the datasheet, the VGS(th) gate threshold voltage is between 2.0 and 4.0 V. With a nominal threshold voltage of 2.0 V, a 45% reduction would lower Vth to approximately 1.1 V.
The resulting impact on the switching behavior and reliability of the circuit therefore needed to be evaluated. The investigation was based on PSpice simulations of the circuit, in which the MOSFET threshold voltage parameter, VGS(th), was varied over a wide range and reduced down to 0.5 V (Figure 3).

Figure 3 Simulation with VGS(th)=0.5V shows that the +5 V, +3.3 V, and −5 V supply voltages are nominal (upper section), while the lower section graphs the gate voltages of the MOSFETs.
The simulation results fortuitously demonstrated that the circuit continued to operate correctly without failure even at significantly lower VGS(th) values. Specifically, since the MOSFETs operate here as switching devices, the reduction in VGS(th) does not prevent proper circuit operation. However, if the MOSFETs were operated in a linear application, the impact of the threshold-voltage shift could be significantly different.
Janos Nagy is a senior electronics engineer specializing in scientific instrumentation, embedded systems, power electronics and space hardware. Beginning in 1977, he has worked at the KFKI Institute for Particle and Nuclear Physics, now part of the Wigner Research Centre for Physics. And since 2021, he has also been affiliated with the Centre for Energy Research.
Related Content
- Choosing power supply components for New Space
- Space-rated analog ICs are increasingly standard catalog items
- Rad-hard GaN converters: Design insights for space hardware
The post In-space MOSFET failure mitigation appeared first on EDN.
Capacitor ESR challenges high-current, fast-transient power sources

One of the first things that a beginning EE student encounters is a brief overview of the three passive components: resistor, capacitor, and inductor. Each has a simple schematic-diagram symbol and is defined by a correspondingly simple equation (Figure 1).

Figure 1 Along with the concept of voltage and current, the role of the three passive components and their defining equations are part of any “Introduction to Electronics” class. Source: LinkedIn
These entry-level courses sometimes mention that in the real world of actual physical components, the equivalent models of these vital components are more complicated. Each has tiny amounts of parasitic inductance and capacitance, which is usually only a concern when operating frequencies reach into the tens and hundreds of kilohertz and then upward from there.
But for capacitors and inductors, there’s also unwanted resistance. For the inductor, DC resistance is primarily due to the wire or material of the inductor. It is seen as reduced Q (quality factor) and “sharpness” in addition to IR dissipative loss.
For the capacitor, the issue is equivalent series resistance (ESR), which is due to leads and wiring as well as the internal construction of the capacitor. A better model of a capacitor, shown in Figure 2, adds stray inductance (ESL), internal resistance (IR), and ESR.

Figure 2 This more-realistic model of a real capacitor shows the ESR, IR, and ESL imperfections. Source: Murata Manufacturing
Keep in mind that capacitance indicates how much energy is stored, while ESR indicates how effectively that energy can be delivered.
ESR is an increasingly critical parameter as power banks at data centers of all types draw huge amounts of power and they also have sharp spikes in demand that require the capacitor array to suddenly provide current. It’s a concern for both conventical bulk capacitors as well as supercapacitors (more formally called electric double layer capacitors or EDLCs), even though their ESR is on the order of a milliohm.
Note that high-frequency bypass capacitors have a different structure using different materials and can have an ESR in the order of tens of milliohms. However, they are used in a very different role and relatively high ESR is not an issue.
A capacitor bank with excessive ESR will have higher power losses, more heat-induced degeneration, and accelerated degradation. During a sharp power-demand transient, the power subsystem may even fail to deliver the needed current, leading to brownouts and system-level instability.
ESR tells a lot about the power subsystem. For supercaps, it’s a figure of merit that summarizes the combined effects of electrode material, electrolyte conductivity, and contact-path resistance. As a marker for capacitor unit-to-unit consistency and overall state of health, it enables proper cell matching and uniformity, which is critical in the large series and parallel capacitor arrays. Small differences in ESR across a large array can be amplified at the system level, resulting in reduced performance.
What about test?
It’s one thing to talk about ESR, but how do you measure it? No, you can’t just use an ordinary multimeter, as that provides only a DC current source. Accurate ESR calculation requires fully capturing the transient voltage drop that occurs at the moment the current switches.
Instead, an AC-driven test is needed, usually performed at different frequencies, as series resistance is a function of that factor as well. There are three common approaches for evaluating EDLC ESR (Figure 3).

Figure 3 Take your pick: there are three widely accepted ways to measure ESR, each with somewhat different perspectives. Source: Chroma ATE
- IEC 62391: Fixed electric double-layer capacitors for use in electric and electronic equipment (Part 1) is generic specification that focuses on measuring voltage drop at the instant of constant-current discharge.
- The Maxwell Six-Step method derives ESR from voltage changes during discharge and rest periods.
- QC/T 741 is a Chinese standard that applies primarily to supercapacitors in traction applications such as electric vehicles and includes evaluation under pulse power conditions.
Not only does each test yield slightly different results, but there are subtle issues related to use of fast sampling rate to capture the fast-moving signals versus use of moving averages to smooth out noise. Fortunately, there are commercial test systems designed to measure ESR alone or in combination with battery-pack performance.
For example, Zurich Instruments offers the MFIA 500 kHz/5 MHz impedance analyzer that applies frequency-dependent technique to characterize ESR from millihertz to kilohertz (Figure 4). They maintain it is superior to the Maxwell Six-Step process which facilitates values of ESR as a static value.

Figure 4 A supercapacitor is connected to the MFIA via an impedance test fixture for ESR test. Source: Zurich Instruments
Their advanced instrumentation and associated test fixture compensate for the effect of series impedances in the cables, connectors, and soldering points, and is also factory-calibrated to compensate for its internal parasitics.
Although every capacitor type is different, the test results for one 3,000 Farad supercapacitor show realities versus its frequency and sub-milliohm ESR at about 50 Hz (Figure 5).

Figure 5 A screenshot showing data taken on the 3000-F capacitor. The graph shows the capacitance (red trace) as a function of frequency, and the absolute impedance Z (blue trace). The floor of the absolute impedance represents the ESR. The light blue trace is the phase between Re(Z) and Img(Z). Source: Zurich Instruments
For a larger-scale test, Chrome ATE offers the Chroma 17010 battery reliability test system, a high-precision, multifunctional charge/discharge rack-mount testing platform designed for lithium-ion battery cells, EDLCs, and lithium-ion capacitors. It offers two system architectures: a linear circuit series offers minimal output noise and highest accuracy for development of small and medium-sized energy-storage components, while the regenerative AC/DC bidirectional series is for testing and life evaluation of larger arrangements.
What’s next?
There are two take-away lessons here. First, ESR is an important parameter, especially in high-current, fast-switching power subsystems. Second, making meaningful ESR measurements is not easy.
But once you have stopped worrying about ESR, you can start worrying about its complement: equivalent series inductance (ESL). ESL is the parasitic inductance within a supercapacitor, which also becomes significant when dealing with rapidly changing currents.
As with ESR, low value is important for maintaining performance in applications where the current changes and as with ESL, high value can lead to inefficient energy transfer and limit the response time of the device.
Bill Schweber is a degreed senior EE who has written three textbooks, hundreds of technical articles, opinion columns, and product features. Prior to becoming an author and editor, he spent his entire hands-on career on the analog side by working on power supplies, sensors, signal conditioning, and wired and wireless communication links. His work experience includes many years at Analog Devices in applications and marketing.
Related Content
- Looking at Hybrid Supercapacitors
- Don’t let ESR waste power and cook capacitors
- Would better electrolytic capacitors reduce e-waste?
- A short primer on X- and Y-capacitors in AC power supply
- Infused concrete yields greatly improved structural supercapacitor
The post Capacitor ESR challenges high-current, fast-transient power sources appeared first on EDN.
Building AI SoCs with a continuous hardware verification strategy

For many years, hardware emulation was reserved for the largest semiconductor companies and the most demanding system-on-chip (SoC) programs. That model no longer fits the way advanced ICs are designed. AI accelerators, edge devices, networking silicon, and data-center processors combine enormous hardware complexity with software stacks that define much of the product’s behavior.
As a result, verification can no longer stop after individual RTL blocks function correctly. Design teams need a coordinated environment that exposes interactions among hardware, firmware, operating software, and workloads before tape-out.
Hardware-assisted verification (HAV) has expanded to meet that need. A modern HAV flow combines emulation, enterprise prototyping, and FPGA prototyping. Each platform serves a different phase and execution-speed requirement, but the greater value comes from using them as a connected methodology. Engineers can move from deep RTL debug to early software development and then to system-level validation without abandoning the design context established earlier in the project.
The pressure is particularly intense for AI products. New models and algorithms appear quickly, while the underlying hardware must deliver best throughput within strict power and thermal limits. Performance per watt has become a central design target for devices operating at the edge and for accelerators deployed at the heart of data centers. Reaching that target requires architectural choices to be tested against realistic software workloads, not only synthetic vectors or isolated block-level tests.
Verification must include the workload
Traditional SoC development often treated hardware and software as sequential activities. Hardware teams verified the RTL, handed the design downstream, and software teams began serious integration later. That approach creates risk when software exposes bottlenecks, memory behavior, scheduling conflicts, or power/thermal characteristics that were not visible during conventional RTL verification. On an AI SoC, the workload can reveal that an apparently correct architecture is inefficient for the computations it must execute.
A more effective flow allows hardware and software development to progress concurrently. Early in the project, engineers still lint and debug SystemVerilog and other RTL descriptions at the IP level. The verified blocks are then assembled on a logic emulator, where teams can run large designs with high visibility into internal behavior. This stage is critical for finding functional errors across subsystems and for validating that the complete SoC behaves as intended before manufacturing commitments make changes extremely expensive.
Emulation also supports more meaningful validation when real firmware, drivers, and application workloads are introduced. Instead of asking only whether the logic produces the expected value, engineers can investigate how the design behaves under sustained traffic, software-controlled corner cases, and realistic data movement. Those observations give architects evidence for refining accelerator blocks, interconnects, memory hierarchies, and power-management logic while the design is still changeable.

An integrated HAV flow connects emulation, enterprise prototyping, and FPGA-based software prototyping. Source: Siemens EDA
Three platforms, one development continuum
Emulation provides capacity, deterministic execution, and very fast detailed debug for complex RTL. FPGA prototyping shifts the emphasis toward execution speed and software availability. Hardware teams can map a functional representation of the SoC into an FPGA-based platform, so software developers can begin work well before silicon returns. Middleware/firmware, AI runtimes, algorithms, and applications can be exercised against a live target rather than waiting for a physical chip.
Enterprise prototyping fills the space between deep emulation debug and individual FPGA prototyping. It offers higher execution speed than emulation while supporting larger, shared use across hardware, software, and systems teams. Enterprise prototyping can run three to five times faster than emulation. That additional performance makes longer software sequences and broader system scenarios practical while preserving a closer connection to the verified design.
The three technologies should not be viewed as competing choices. Emulation is suited to finding difficult hardware defects and examining internal signals in the IC design. FPGA prototyping gives software engineers rapid access to an early target. Enterprise prototyping supports collaborative validation of hardware-software behavior at greater speed. Together, they create a faster path from RTL bring-up through workload execution and system qualification.
A unified environment shortens debug loops
Earlier HAV implementations often forced teams to treat emulation and prototyping as separate islands. Different user interfaces, compilers, and setup procedures made design movement difficult. When a failure appeared after transitioning to another platform, engineers first had to determine whether the problem came from the design, the mapping flow, or the verification system itself. That uncertainty consumed engineering time and often required specialists who understood the quirks of each environment.
Current integrated platforms reduce that friction by sharing core software infrastructure. For instance, Veloce CS family brings Veloce Strato CS emulation, Veloce Primo CS enterprise prototyping, and Veloce proFPGA CS FPGA software prototyping under a common operating environment and unified compiler. Consistent flow makes it easier to reproduce failure across platforms, distinguish design defects from platform issues, and carry a validated configuration from hardware debug into software development.
For design teams, this continuity matters as much as raw execution speed. A bug discovered by a software workload can be traced back toward emulation, where engineers have finer visibility into the RTL. After the correction, the updated design can return to a faster prototyping platform for broader regression and application testing. Shorter transitions help teams repeat this loop more often before tape-out.
From chip verification to the system digital twin
An SoC rarely operates in isolation. AI processors are installed in boards, racks, vehicles, industrial equipment, medical systems, and aerospace platforms. Electrical behavior interacts with thermal conditions, mechanical constraints, power delivery, cooling, and software control. Validating the IC within a broader digital twin allows engineering teams to study those interactions before all physical elements are available.
In-circuit use of emulation can connect the developing SoC and its software to a larger system model. A data-center team, for example, can examine power consumption while the modeled device experiences thermal stress in a rack configuration.
Automotive and other mission-critical programs can use similar techniques to investigate reliability and system responses across electrical, thermal, and mechanical conditions. The objective is not simply to prove that the RTL is correct, but to determine whether the complete product behaves acceptably in its intended environment.
This system perspective also supports power-performance optimization. When engineers run representative software through a digital twin, they can identify whether an undesirable result is best addressed in the microarchitecture, firmware, compiler, runtime, or application. The ability to trade hardware and software changes against the same scenario is essential when performance per watt is a primary product requirement.
Capacity and deployment must match next-generation designs
Growing gate counts have historically forced companies to purchase highly customized emulation installations. Special rooms, racks, power arrangements, and operational expertise increased both cost and deployment time. Modern systems address those constraints with greater capacity and packaging designed for conventional data-center infrastructure.
Cloud access further changes who can use advanced HAV. Rather than purchasing a full platform, a startup or smaller design group can lease emulation or enterprise prototyping capacity for the periods when a project needs it. Flexible consumption does not remove the need for careful planning around security, data transfer, compilation, and queue availability, but it broadens access to verification resources that were once limited to the largest semiconductor companies.
The most important shift is methodological. HAV is no longer only a late-stage appliance for proving that a large RTL design runs. It’s an engineering continuum that connects architecture, functional verification, software enablement, power/performance analysis, and system validation. Teams gain the strongest benefit when they plan platform transitions early, define which workloads must run at each stage, and preserve a consistent debug path from application behavior back to RTL.
For engineers designing next-generation ICs, that approach provides earlier evidence about whether the architecture can meet its real product goals. Logic may be functionally correct yet fail to provide adequate throughput, power efficiency, software compatibility, or behavior under system stress. Integrated emulation and prototyping expose those gaps while engineers still have options.
As AI SoCs continue to grow in scale and software dependence, tape-out confidence will increasingly depend on the quality of hardware-software validation. A connected HAV environment gives teams the capacity scalability, speed, observability, and system context needed to make design decisions before fabrication. The result is not merely fewer bugs. It’s a better opportunity to deliver an IC whose hardware, software, and operating environment work together as engineered.
Vijay Chobisa is senior director of product marketing for hardware-assisted verification at Siemens EDA.
Related Content
- The Hardware-assisted Verification Imperative
- Time to rethink EDA flows and tool infrastructure
- The Growing Use of Hardware-Assisted Verification
- Four ways to build a CAD flow: In-house design to custom-EDA tool
- Enhancing SoC HW/SW co-verification with FPGA-based prototyping
The post Building AI SoCs with a continuous hardware verification strategy appeared first on EDN.
Inspecting a DOCSIS 3.1 cable modem’s internals: Part 1

The version publication ordering might not be as originally envisioned, but this two-part teardown of NETGEAR’s CM1000 still aspires to be technically (and otherwise) interesting.
Having recently wrapped up a four-part series on how I’d determined (and resolved) the underlying reasons for my flaky Comcast broadband service, with the concluding entry focusing specifically on the cable modem portion of the transmission-and-reception chain, I thought it’d next be interesting to take apart a DOCSIS 3.1 modem (roughly four years subsequent to dissecting its DOCSIS 3.0 precursor) and see what was inside.
That said, I wasn’t particularly motivated to tear down either my in-use primary or spare NETGEAR Nighthawk CM1100, for perhaps obvious service-downtime reasons.


Instead, I decided to tackle the CM1000 sibling, which looks identical from the front save for a metal tint variance (silver vs rose gold) and the absence of a second LAN connection status LED.

That latter variation is reflected in the inclusion of only a single RJ45 connector in the back.

In researching the CM1000 in advance of surgery, I learned that two device versions existed, the original and a subsequent v2. I wasn’t able to uncover any specifics on the deviation(s) between them, however, save for vague references to “slight hardware changes.” And I couldn’t find an already published teardown of either version to see those “slight hardware changes” for myself, either.
So, I decided to tackle my own teardowns of both versions. I first purchased a (claimed) v1, judging from the published eBay photos (to reiterate: the blurry one that follows was not taken by yours truly). Absent a power supply and claimed “malfunctioning”, randomly rebooting every few minutes, it was therefore perfect for dissection purposes.

And then I bought a v2, complete with a PSU and in an eBay-advertised “untested” state.

The thing is, though, what was supposed to be a v1 ended up being a v2, too, and I didn’t realize the discrepancy until I sat down to start the teardown, after the eBay return period had expired, of course.

The eBay seller had multiple units available for purchase and (I realized in retrospect) didn’t explicitly identify them as v1 models in the description; I was relying solely on the post’s pictures. So, I’m guessing the seller had a version mix in inventory, and I was unlucky with the one randomly (presumably) shipped to me.
I’ve kept the “untested” v2 CM1000 intact as a potential additional spare since, as noted previously, Comcast doesn’t allow enable of the CM1100’s second LAN port anyway, and in the hope that “untested” doesn’t translate into “nonfunctional” or, for that matter, “blacklisted”. That said, here are a couple of closeups of the “untested” unit’s wall wart (which I also won’t be taking apart) so you can see what the power supply for a v2 CM1000 looks like.

I’ve ordered another v1 (I hope) CM1000 off eBay, which is en route as I type these words. I’m planning on taking it apart for publication next month. And for today, in reverse order versus my original plans, you’re getting the teardown of a “malfunctioning” (or not) PSU-less v2 CM1000, starting with some overview shots of the actual device versus the earlier “stock” shots.
Front.

Left side.

Back.

Right side.

Top.

And bottom, a closeup version of which you’ve already seen.

Time to get inside. Have you already noticed the notably visible screw head in those earlier bottom views? Well, you won’t notice it anymore.


Here’s what the CM1000 looks like with the base now removed.


Next up, two more screw heads, this time around back (one at the top of the back panel, the other at the bottom).

And after releasing a few clips, the two halves of the device cleanly separate, revealing the inside of the left side of the enclosure (complete with a plethora of light pipes that route the PCB’s LEDs’ outputs to the outside world) and our first glimpse of the PCB itself.


Two more screws to go.

Ladies and gentlemen, the PCB is now free.


Before flipping the PCB over, let’s get the left side heat sinks off. The smaller silver one toward the top is the first to pop off after using a flat head screwdriver as a lever on it.
Clean off the thermal paste and…it’s blank. Not quite, actually; the markings that remain are quite faint, as you can see, but I hope you’ll take my word that they reference a Macronix MX30LF1G18AC (PDF) 1 Gbit SLC NAND flash memory, presumably holding system firmware.
Now for the larger black heat sink toward the bottom of that same side.
That’s a whole lotta not much, although I’d wager a bet that there’s heat-generating stuff on the PCB’s other side, which this heat sink (imperfectly, but better than nothing) deals with.
Let’s see.
Up top is an even larger black heat sink, held in place by not only a thermal pad but also mounting pins, and with Broadcom’s BCM3390 DOCSIS 3.1 SoC underneath it.
And location-associated with the aforementioned black heat sink on the other side is a sizeable Faraday Cage, containing an assortment of both ICs and discretes.
At lower left is the largest, square chip, Analog Devices’ MAX3522B DOCSIS 3.1 programmable-gain amplifier; directly underneath it is the copper-color heat-transfer “landing pad” on the PCB’s other side (see, told you so!). To its far right is a pSemi (formerly Peregrine Semiconductor) PE42722 SPDT RF switch. And above and to the right of the MAX3522B, in the other section of the Faraday Cage, is a chip marked as follows (readers?).
3432
KMLG 10
EE1852
0403 W (I “think” that last character’s correct, but I’m not positive).
All of this plus, as already alluded to, a whole mess o’surface mount capacitors, inductors, resistors, transformers and transistors, and such. An RF engineer’s dream (or maybe nightmare).
Zooming out on this same right side of the PCB, what else do we see?
To the left of the Broadcom SoC is an Elite Semiconductor Memory Technology (ESMT) M15T1G1664A 1 Gbit DDR3(L) SDRAM, interestingly with another (unpopulated) site above it. To the right of the BCM3390 is, unsurprisingly given its proximity to the RJ45 connector, a Bothhand GST5009 LF surface-mount 1000BASE-T magnetic module and pulse transformer.
That’s it for today; next month, we’ll see what if anything we can find regarding “slight hardware changes” in the v1 CM1000 design. Until then, please share your thoughts in the comments on what I’ve uncovered so far!
—Brian Dipert is the associate editor, as well as a contributing editor, at EDN.
Related Content
- Debugging intermittent Comcast, part 1: Scenario-setting
- Debugging intermittent Comcast, part 2: Remediation details
- Debugging intermittent Comcast, part 3: Retrospective analysis
- Debugging intermittent Comcast, part 4: Broadband diagnostics
- Cisco Linksys’ DPC3008: A DOCSIS 3 cable modem that worked great
The post Inspecting a DOCSIS 3.1 cable modem’s internals: Part 1 appeared first on EDN.
The shocking science (and art) of plastic welding

Electrical engineers often treat plastic like a mysterious black box—something to be specified, ordered, and ignored once the circuit is safely tucked inside. Metal gets all the glory: TIG welding stories, custom sheet‑metal chassis, and aluminum heat sinks dominate the conversation.
Yet the reality is that modern electronics live inside thermoplastics—whether injection‑molded, 3D‑printed, or rotationally molded. And here’s why you should care: mastering plastic welding means you can rapidly prototype, repair lab gear, modify off‑the‑shelf enclosures, and fix rugged field equipment without resorting to messy glues.
Polymer physics: Why glues fail and welds work
Glues rely on surface adhesion, but plastics demand molecular continuity. Thermoplastics such as ABS, PETG, HDPE, and polycarbonate soften, melt, and resolidify reversibly, making them weldable. Thermosets like epoxies, cross‑linked resins, and Bakelite, however, char and degrade when reheated, so they can’t be welded.
True welding isn’t just “melting”—it’s about heating polymers past their glass transition (Tg) or melting point (Tm) so long chains diffuse across the joint boundary and re‑entangle as they cool. This molecular handshake is what gives a weld its strength. Adhesives struggle because many plastics—HDPE, PP, PTFE—have extremely low surface energy (around 31 mN/m), which prevents chemical wetting and causes glues to peel off like painter’s tape.
And the golden rule of compatibility: you cannot weld ABS to polypropylene. Without matched solubility parameters, the interface resists entanglement, leaving the joint weak or non-existent.
The benchtop toolkit: From rework stations to irons
Not all heat sources are created equal when it comes to plastic welding. Grab your trusty Weller soldering iron and you’ll quickly ruin the tip and char the polymer—because soldering irons are designed for tin‑lead alloys, not polymers. Specialized plastic welding irons use flat, spade‑shaped brass tips that spread heat uniformly, allowing the polymer to soften and fuse without burning.
Hot‑air rework stations, the same ones used for SMD desoldering, can double as precision hot‑gas welders when set to 300–350 °C with a narrow 3–5 mm nozzle. And here’s a clever hack: those rolls of 1.75 mm and 2.85 mm PLA, ABS, or PETG filament you keep for your 3D printer make perfect, high‑purity filler rods. With these tools, your electronics bench transforms into a capable plastic welding station.

Figure 1 Hot iron plastic welding tool melts and fuses plastic components using a heated triangular brass tip. Source: Weldi Plast
Heavy duty field engineering: Water tanks, septic systems, and extrusion
Cracks in rotomolded HDPE or polypropylene tanks aren’t cosmetic—they’re structural nightmares. Hydrostatic pressure (P=ρgh) and hoop stress mean even small fractures can propagate under load. For thick‑walled parts (greater than 1/4″), a hot‑air pencil simply doesn’t deliver enough thermal mass. That’s where handheld extrusion welders come in: they feed filler rod into a heated barrel and auger screw, pumping molten plastic directly into a pre‑heated joint.
Field repair follows a strict protocol. First, crack arrest: drill 3-mm relief holes at the crack tips to eliminate stress concentrations. Second, V‑grooving: gouge a 60°–90° channel along the fault line to create a weld pocket. Third, scraping oxidation: remove the UV‑degraded outer skin, because welding onto oxidized polymer produces brittle, worthless joints. Done correctly, extrusion welding restores structural integrity to tanks and systems that would otherwise be scrapped.

Figure 2 Handheld extrusion welder extrudes molten plastic rod while preheating the substrate to form structural seams in heavy plastic sheets. Source: Author
Advanced industrial techniques
At the cutting edge of polymer joining, welding moves far beyond hot irons and filler rods. Ultrasonic welding operates in the 20–40 kHz range, converting high‑frequency electrical signals into mechanical vibrations through piezoelectric transducers. These vibrations drive acoustic horns that melt tiny “energy directors” inside the joint in milliseconds—an EE goldmine for precision assembly.
Laser and infrared welding take a different route: transmission welding uses a laser‑transparent top layer (like clear polycarbonate) over a laser‑absorbent bottom layer (carbon‑black filled PC), fusing parts internally with zero surface flash. And then there’s spin and vibration welding, where friction itself becomes the thermal energy source, generating heat at the interface until polymers soften and bond.
Together, these industrial techniques form the high‑tech spectrum of plastic welding, enabling clean, rapid, and highly reliable joints in modern manufacturing.
Joint design cheat sheet for product designers
Smart joint design is the hidden backbone of reliable plastic welding. Energy directors are perfect for ultrasonic welding of small enclosures, concentrating acoustic energy into a triangular point that melts instantly. Shear joints shine in hermetic seals for waterproof sensors and modules, creating a continuous interference‑fit melt along vertical walls.
For manual hot‑air or extrusion repair of tanks, single or double V‑grooves maximize surface area, ensuring deep thermal penetration through thick walls. Together, these joint geometries give designers practical tools to match welding technique with application, guaranteeing strength and durability where it matters most.
The overlooked essentials
Beyond the core welding methods, a few practical details make the difference between a strong seam and a failed joint. Precise temperature control—often via PID‑regulated irons or hot‑air stations with thermocouple feedback—prevents overshoot and ensures polymers reach the right rheological state without scorching.
Filler material selection matters too: while 3D printer filament is a handy hack, commercial filler rods are resin‑matched and color‑matched to the base polymer, preserving both strength and aesthetics. Proper surface preparation goes beyond scraping oxidation; oils, dust, and mold release agents must be removed with abrasion or solvents like isopropyl alcohol to guarantee chain entanglement. Once welded, mechanical testing—from simple peel and tensile pulls to ultrasonic inspection—validates joint integrity.
And don’t forget safety: hot‑gas welding produces fumes, so fume extraction and PPE are non‑negotiable. Finally, smart designers think ahead with design for repair, choosing joint geometries that allow re‑welding rather than locking assemblies permanently. These overlooked essentials elevate plastic welding from a bench trick to a disciplined engineering practice.

Figure 3 Green polypropylene (PP) plastic welding rods supply filler material to form strong, heat-fused bonds during thermal enclosure repair and prototyping. Source: Author
Plastic welding is the intersection of thermal dynamics, mechanical joint design, and material science, offering engineers a practical way to create durable bonds where adhesives fail. To appreciate its power, you don’t need an industrial setup—your own bench is enough.
Take a scrap 3D print, dial your hot‑air station to 320 °C, feed in a strand of PLA filament, and run your first seam. That simple experiment transforms abstract theory into hands‑on skill, proving that plastic welding is not just an industrial technique but an accessible craft waiting to be mastered.
T. K. Hareendran is a self-taught electronics enthusiast with a strong passion for innovative circuit design and hands-on technology. He develops both experimental and practical electronic projects, documenting and sharing his work to support fellow tinkerers and learners. Beyond the workbench, he dedicates time to technical writing and hardware evaluations to contribute meaningfully to the maker community.
Related Content
- A look at spot welding
- How To Solder BGA on PCB Board?
- Hand-Soldering Surface-Mount Devices
- How 3D printing is revolutionizing production and design
The post The shocking science (and art) of plastic welding appeared first on EDN.
Physical AI: Where AI meets the physical world

Artificial intelligence (AI) is moving beyond the cloud and into machines that must perceive, understand, and interact with the physical world. Unlike AI systems that primarily process digital information, physical AI must enable machines to sense their surroundings, make decisions, and act in real time.
That shift introduces new engineering challenges. A robot may recognize an object through computer vision, but knowing how tightly to grip it requires additional sensing, physical-world training data, and processing that can respond to changing conditions.
At Synaptics Tech Day 2026, EE Times executive editor Nitin Dahad explored these challenges with Satish Ganesan, senior VP and GM of Edge Interface & Sensing at Synaptics; Aashish Mehta, CEO of TacnIQ; George Chowdhury, principal analyst for robotics at ABI Research; Vincent Duchaine, co-founder and CTO of Robotiq; and Andrew Herson, head of ecosystem development for physical AI at Nvidia.

The discussion examined how physical AI is evolving, why tactile sensing matters, and what it will take to move intelligent machines from experimentation to practical deployment.
The following Q&A has been edited and condensed for clarity.
Where is physical AI creating value?
Nitin Dahad, EE Times: Where do you see physical AI creating value?
Satish Ganesan, Synaptics: Physical AI is fundamentally about enabling an inanimate object to sense, perceive, adapt, and act. The opportunity is to bring those capabilities into everyday applications, from industrial systems to humanoid robots, using multiple sensing modalities and processing information at the edge.
Andrew Herson, Nvidia: Manufacturing is one of the areas where I expect significant impact. It’s an environment with complex requirements, repetitive activities and large amounts of data, making it well suited for physical AI.
Vincent Duchaine, Robotiq: We’re starting to see a shift toward deployment. The opportunity is in automating tasks that were previously too complex or variable for conventional programming. Physical AI is beginning to make it possible to automate applications that require greater flexibility.
What does touch add that vision alone cannot provide?
Dahad: A key part of physical AI is touch sensing. What does touch add that vision alone can’t?
Ganesan: Think about gripping a glass, handling fruit, or picking up an egg. Each task requires a different amount of force. Touch sensing allows a robot to detect an object’s properties and apply the appropriate pressure. The goal is to translate physical interactions into information that processors can use to make decisions.
Duchaine: Vision has made tremendous progress, but advanced manipulation requires information that pixels alone cannot capture, including friction, texture, stiffness, and force. Touch also improves training data by showing not just whether a grasp succeeded, but whether an object was slipping or the grip was stable.
Aashish Mehta, TacnIQ: With vision alone, you can’t directly measure force feedback. Even determining finger position while holding a cup can be difficult because the hand and object obscure each other.
We’re exploring how to build three-dimensional force maps that capture deformation, soft and hard points, and other physical characteristics. That information could help robotic systems manipulate objects without relying entirely on vision.
What’s the biggest challenge in training robots for the physical world?
Dahad: What’s the hardest data problem in training robots to interact with the physical world? What data is needed to make dexterity reliable.
Duchaine: We’re not capturing enough information about physical interactions, including tactile sensing, force, and torque. We also need better annotation. It’s not enough to recognize objects. Models need to understand the relationships between objects and actions.
Mehta: We’re approaching this in three stages. First, we’re collecting large amounts of tactile data to characterize physical interactions, similar to how a baby learns through touch. We’ve collected approximately 6,000 hours of data across five industries, representing more than 10 million contacts.
Next, we’re organizing that information into physical characteristics such as slip, shear, contact duration, and material properties. Finally, we’re translating those characteristics into applications. The goal is to understand the underlying physics, so we don’t have to train a separate model for every task.
Herson: Self-annotating data will be critical. We can’t expect humans to manually annotate every interaction. By combining information from tactile sensors, inertial sensors and motor currents, robotic systems can generate data that reinforces and validates itself. That could help make dexterity more reliable.
Which applications are likely to benefit first?
Dahad: What will make robotic dexterity reliable enough for practical applications?
George Chowdhury, ABI Research: Humanoid robots represent a longer-term opportunity, but there are applications today in warehousing and manufacturing. Touch and force feedback are particularly useful for manipulating deformable or irregular objects that are difficult to handle through conventional programming. These are applications that existing system integrators can support.
Ganesan: Industrial customers need to handle everything from glass bottles to fruit and eggs, often using mechanical or vacuum-based grippers that require uniformity.
I see a parallel with autonomous vehicles. Driver-assistance features reached the market before fully autonomous driving. Similarly, individual robotic capabilities will be adopted before fully capable humanoid robots. I expect industrial applications to see more rapid adoption around 2028 and 2029.
How will multimodal sensing and edge processing improve robotic performance?
Dahad: How should sensing, perception, and processing be organized so robots can respond appropriately?
Ganesan: The future will involve multimodal sensing, combining vision with other sensors. To achieve low latency, some processing needs to happen close to the sensing elements, whether that’s in a robotic hand or elsewhere in the body.
It’s similar to the human nervous system, where nerve endings handle immediate sensing functions while more complex decisions happen elsewhere. We expect robotic architectures to evolve in a similar way, with local processing for immediate responses and central processing for higher-level decisions.
Duchaine: One challenge is the amount of visual data robots must continuously process, which can introduce delays and contribute to jerky movements. Touch and force sensing provide lower-dimensional signals that can simplify the problem.
It’s not about choosing vision over touch. The two complement each other, and physical feedback can help robots respond more quickly and smoothly.
What will signal that physical AI is ready for broader deployment?
Dahad: What’s one realistic deployment milestone you expect the industry to reach next, and what needs to happen to get there?
Herson: I’d point to lights-out manufacturing. A major milestone would be a large warehouse operating without employees on site. To get there, we need greater standardization of robotic functions and a broader ecosystem that makes deployment economically viable.
Duchaine: We’re beginning to see deployments in tasks such as packaging, where cycle time isn’t the primary requirement. The next step will be robots that are more dexterous than conventional industrial systems but don’t necessarily need to be humanoid. As they become faster and more reliable, they’ll address a wider range of applications.
Chowdhury: Broader adoption requires making robotics accessible beyond companies with enormous R&D resources. Agentic workflows could help system integrators and smaller manufacturers coordinate different robotic assets and reduce integration challenges.
Ganesan: Industrial environments will lead the adoption because robots can perform tasks independently without immediately needing to interact with people in complex settings. Those applications will establish the foundation for broader deployment and, eventually, more capable humanoid robots.

Related Content
- Connecting AI to the Physical World
- Physical AI in action at OktoberTech Silicon Valley 2026
- Missing sense: Why physical AI can see everything and feel nothing
- Physical AI Isn’t Just Bigger AI; It’s a Systems Architecture Challenge
- From edge AI to physical AI in smart factories: A shift in how machines perceive and act
The post Physical AI: Where AI meets the physical world appeared first on EDN.
The tchotchke

Things aren’t always as useless as they seem (and are claimed by others) to be. All it takes is a bit of engineering imagination.
There was a Candid Camera episode many years ago where Alan Funt showed what was said to be a useless machine. It was a Bud box with nine NE-2 neon lamps mounted three-by-three in rubber grommets, and with each lamp blinking on and off at its own individual rate.
Each lamp was part of a relaxation oscillator. Since the oscillators were not synchronized to each other, the blinking pattern of the nine lamps looked random.
You remember what a relaxation oscillator is/was, right? Typically, it was a 90 volt battery, a 0.1 µF capacitor in parallel with an NE-2, and a multi-mega-ohm resistor feeding them (Figure 1).

Figure 1 The circuit for a relaxation oscillator is simplicity exemplified.
Alan Funt and Durwood Kirby explained to viewers that this box was utterly and absolutely useless, and that it served no purpose of any kind. So they took it out to the street and asked passersby what it might be good for.
The big joke was that as useless as this thing supposedly was, people still tried very hard (but without success) to envision a purpose for it. That was the big joke. Ha ha ha. Let’s laugh at all these silly people with their silly ideas.
What nobody came up with was the possibility that this thing might serve, say, as a children’s night light, for example, or a blinky little friend sitting on a night table near the crib or bed. I don’t know for sure, but just maybe this thing wasn’t really the useless tchotchke it was cracked up to be.
Seen any truly useless things lately? And got any other ideas for this particular supposedly useless one? Reader thoughts are as-always welcomed in the comments!
John Dunn is an electronics consultant and a graduate of The Polytechnic Institute of Brooklyn (BSEE) and of New York University (MSEE).
Related Content
The post The tchotchke appeared first on EDN.
Google’s Fitbit Air: Another display-less option for tech you wear

Minimal- and no-display device value propositions aren’t unique to wearables. But they’re uniquely optimal for the needs and desires of wearable device users.
My wife is admittedly not as passionate about technology as I am…then again, for that matter, very few people are! Tech is much more of a means to an end for her, versus an end in and of itself (in my case). That said, there have been a few things in particular that I’ve added to our residence tech “stable” over the years which she’s been notably enthused about.
The Pandora music streaming service, for one, more recently supplemented with (but not supplanted by) Sirius XM and Amazon Music Unlimited. Dropbox also comes to mind. A Blink video doorbell I installed a few weeks back shows early potential to be another.
And then there are wearable health and fitness tracking devices, which I’ve been covering for well over a decade at this point (and using myself for much longer than that). A minimal-display band from Microsoft that I tore down in late 2015, for example, followed by a display-less Sketchers band dissection 1.5 years later, both mentioned (along with others) in an October 2018 state-of-the-market summary, augmented by further coverage in subsequent years.

By means of analogy, earlier this year I disassembled a display-less hygrometer from TP-Link, contrasting it to my earlier conceptual coverage of its display-inclusive sibling. The primary motivation for the former’s development and production, I’m assuming, was to offer a lower-priced alternative to the latter for consumers who were content to proactively monitor (and reactively respond to alerts from) the multi-sensor widget using only their wirelessly tethered mobile device. Plus, of course, the absence of a display made the resulting product more compact and power consumption-stingy than would otherwise be the case.


Cost-effectiveness, compactness, and power-stinginess are also motivations for display-less wearable devices, along with the consequent usage model of data logging and display via a paired smartphone or tablet, usually over Bluetooth Low Energy. But in this case, there’s another key consideration that my wife’s repeated embrace of the concept exemplifies.
Last week, I covered my experiences with my own latest wearable, a Google Pixel Watch 3. It’s a full-blown smartwatch, capable of standalone operation in many situations, thanks in no small part to its integrated connectivity over not only Bluetooth and Wi-Fi but also GPS and LTE cellular.
Note, however, that I repeatedly referred to it as my “daily driver”. To be precise, it’s on my wrist near-constantly, replaced by my Garmin fēnix 5 only when the Pixel Watch 3 is on the charger, replenishing its cache of battery-stored electrons.
My wife’s different; she’s a longstanding watch aficionado and regularly rotates between multiple timepieces on her wrist, some of them (heaven forbid…I jest…) even “dumb” analog models. But regardless of what’s keeping time for her at any particular point in time, she still wants her health being monitored.
Smart rings: Not her thingWhat about a smart ring, then? Here’s what I wrote in September 2025, regarding the “key motivations behind my recent interest in the rapidly maturing smart ring product category”.
Such devices typically tout ~1 week (or more) of between-charges operating life, and they also recharge rapidly, courtesy of their diminutive integrated cells. A smart ring also affords flexibility regarding what watches (including traditional ones) I can then variously put on my wrist. And, as noted within my 2025 CES coverage:
This wearable health product category is admittedly more intriguing to me because unlike glasses (or watches, for that matter), rings are less obvious to others, therefore it’s less critical (IMHO, at least) for the wearer to perfectly match them with the rest of the ensemble…plus you have 10 options of where to wear one (that said, does anyone put a ring on their thumb?).
Due in no small part to recent health hiccups, I always also have a smart ring on my finger for data capture-and-analysis redundancy purposes. But although she’s a ring fan, she’s not (yet, at least) a smart ring fan. They’re still too bulky, for one thing. And then there’s my observation at the end of last year’s overview.
The lack of multi-ring support is a frequent cause of complaints on Reddit, from folks who want to accessorize multiple smart rings just as they do with normal rings, varying color and style to match outfits and occasions.
Oura has subsequently added the ability to associate two rings with a given account, but not at the same time, and the switching process is cumbersome (and I’m being kind in using that word, versus other adjectives I could have chosen). But, of course, there’s also the qualifier that “none of these devices are particularly inexpensive”, either.
A display-less device historyA slim, economically priced and wrist-based (either the same one her watch is also on, or the other) wearable with long battery life is more her “cup of tea”. And a half-decade-plus ago, we’d found the seemingly perfect device for her, actually…at least for a while. In August 2020, Amazon had rolled out its Halo Health ecosystem, including the display-less Halo Band device, followed a year-plus-later with a minimalistic OLED display sibling, the Halo View.


She loved the Halo Band, in spite of the fact that among other things it embedded two microphones to monitor for snoring during sleep (apnea symptoms, don’cha know) and other relevant ambient audio information. Audio capture could be disabled via an integrated button, at least supposedly…the value to Amazon of a user’s full suite of health data was obvious to both of us from the beginning, but she decided to roll the dice and take a chance anyway.
With the mics muted, battery life was up to a week between recharges, which took only 90 minutes. And the Halo Band cost only $64.99, bundled with six months’ worth of the Halo Health subscription service, with the Halo View only $79.99. Both devices were presumably subsidized by forecast recurring subscriptions for many years to come. But they didn’t apparently manifest, at least as fast as Amazon management demanded. By the end of July 2023, Halo was no more.
Fitbit’s concept resurrectionImagine her happy surprise, therefore, when earlier this year I caught wind of (and passed on to her) news of Fitbit’s pending release of a display-less wearable, coined a month later with the “Air” moniker.

She’d long been a Fitbit user through multiple product form factors and generations, as I’d also noted back in October 2018. To that point, by the way, I feel compelled to point out at least one other key differentiator between her various Fitbit devices and my multiple Pixel Watch generations. My Pixel-branded wearables are Android-only, while her Fitbit ones have all been multi-platform compatible, a convenient capability given that she’s a longtime iPhone user.
Also, by the way, I was reminded of at least one other wearable teardown I’d done while searching just now through my past-published-content archive. Prior to its acquisition by Google, Fitbit had released a display-less band (this one sensors-integrated) called the Fitbit Flex, which I’d disassembled in March 2020. What’s old is new again, eh?

That said, one key advantage of the Fitbit Air is that it’s detachable (and re-attachable) for use with a variety of different bands in different colors and styles (and not just from Google, either). Enterprising folks have even figured out how to mount the Fitbit Air to the strap of a conventional watch.
It costs $99.99 baseline, including a three-month Health Premium subscription, which (unlike Whoop’s competitive offerings) is not necessary for ongoing use (speaking of smart ring—Oura, specifically—analogies). And since I bought it for her as soon as it was announced, we also got $35 in promo Google Store credit which…no surprise…she used on another band. A week’s use between full charges, which take 90 minutes. A day’s worth of use after only 5 minutes of charge time.
And for those of you who really want an integrated display, there’s also the more recently (like mid-October recently) unveiled Fitbit Edge, the seeming successor to the longstanding Fitbit Charge line, albeit this time (and first-time) with a user-replaceable battery.
No obsolescence by design here; nice! Although the $179.99-and-up price tag is admittedly a bit salty. And no NFC support this time; limited past Google Wallet usage apparently didn’t justify an ongoing bill-of-materials cost impact caused by the feature’s inclusion.

As with many product categories I cover, the wearables segment is an always-interesting case study in how manufacturers strive to develop, productize, price (including both initial upgrades and ongoing services and other revenue sources), and promote the fewest possible device options that service the varying needs of the largest possible potential customer base, hopefully stacking up successfully against competitors’ offerings in the process.
If you’re employed by a wearables supplier, I’d welcome any insights you’d be able to share (anonymously, if necessary) as to how your company strives to achieve those objectives. And even if you’re “only” an end user, I welcome your thoughts into what features are most important to you, versus being irrelevant, and what ecosystem and device(s) within it you’re currently going with. Let me know your feedback in the comments, please!
—Brian Dipert is the associate editor, as well as a contributing editor, at EDN.
Related Content
- Teardown: Fitness band hardware
- Wearable trends: a personal perspective
- A belated Google Pixel Watch update: In retrospect, why’d I wait?
- The Smart Ring: Passing fad, or the next big health-monitoring thing?
- Teardown: Fitbit Flex doesn’t easily give up its secrets
The post Google’s Fitbit Air: Another display-less option for tech you wear appeared first on EDN.
MCU revitalizing SDVs with diverse compute, virtual prototyping

A new automotive microcontroller incorporates physical AI traits while boosting compute and memory content to support zonal architecture in software-defined vehicles (SDVs). It also introduces a digital twin of the target hardware, letting software engineers write, run, and debug unmodified production software long before chips or evaluation boards exist.
Infineon’s AURIX RC1 microcontroller, unveiled at electronica 2026 in Munich, Germany, aims to redefine real-time compute and control for SDVs and extend it to physical AI. It aims to do so by leveraging ample compute content and the modular nature of the open RISC-V architecture.

Figure 1 The AURIX RC1 microcontroller aims to redefine real-time compute and control for SDVs and to extend this to physical AI applications. Source: Infineon
These high-end MCUs aim to simplify SDV development with a single, scalable device that supports multiple automotive domains, rather than point solutions. These MCUs also offer a robust software ecosystem designed to reduce migration effort and accelerate software development for engineering teams.
Let’s first see how these automotive MCUs revisit the long-held promise of SDVs.
Another stab at SDVs?
First and foremost, AURIX RC1, the company’s first RISC-V-based MCU, aims to support functions and software that have been distributed across many electronic control units (ECUs) in the car. In SDVs, they are increasingly integrated into central car computers and zone controllers.

Figure 2 SDVs will drive massive changes in vehicle architecture, with MCUs at the heart of this tectonic design shift. Source: Infineon
AURIX RC1 enables scalable cross-domain computing by supporting applications ranging from zone, body, and chassis control to battery management systems (BMS) and powertrains, as well as cockpit and safety management for driver assistance. Here, RISC-V helps optimize specific AURIX RC1 lineups for individual applications.
For this broad range of applications, AURIX RC1 integrates up to 12 32-bit processing cores, an advanced parallel processing unit for edge AI, and up to 40 megabytes of embedded memory. This caters to higher computing demand as well as functional safety, future-proof cybersecurity, and high-speed in-vehicle networking, which are foundational requirements in SDVs.
In addition to complying with global regulations such as ISO/SAE 21434 and the Cyber Resilience Act, the MCU provides hardware mechanisms for physical protection and crypto agility. Next, to move data efficiently across the vehicle, it supports connectivity technologies such as CAN-XL, 10BASE-T1S, and multi-Gigabit Ethernet.
Software ecosystem ready from day one
As automotive design complexity increases with the emergence of SDVs, OEMs and Tier 1s need to start software development long before hardware is delivered. To support this, Infineon claims to provide a software ecosystem around AURIX RC1 microcontrollers, DRIVECORE, that combines Infineon’s toolsets with pre-integrated software bundles from ecosystem partners.
DRIVECORE provides support for AUTOSAR, open-source software, functional safety, and cybersecurity. It also supports virtual prototyping with the Synopsys Virtualizer Development Kit (VDK), allowing design engineers to start software development and validation before hardware is available. TASKING also supports the entire development lifecycle for AURIX RC1 microcontrollers, helping OEMs and Tier-1s starting new designs or migrating from TriCore and Arm.

Figure 3 AURIX RC1 MCUs complement In-house toolchains with pre-integrated software bundles from ecosystem partners. Source: Infineon
Synopsys’ VDK equips automotive design engineers with a virtual prototype of the AURIX RC1 MCU, enabling them to develop, verify, and validate software across a variety of domains. This reduces integration risk and accelerates time to market. It’s a digital twin that shifts more automotive engineering to virtual environments to manage software development and integration complexity, cost, and time-to-market pressures.
“VDK for AURIX RC1 MCUs enables OEMs and Tier 1 suppliers to start software development before silicon is available and scale system validation from virtual ECUs to complete electronics digital twins,” said Marc Serughetti, VP of product management at Synopsys. “These digital twins help teams validate software across the vehicle’s electronics architecture and catch issues early, reducing costs, accelerating time to market, and improving software quality.”
TASKING, a supplier of embedded software development tools, will also let design engineers compile, debug, and verify AURIX RC1-based systems with a unified toolchain that incorporates built-in agentic AI to accelerate development of complex, multicore automotive systems. For instance, compiling, debugging, and verification in one unified development environment will help engineers deliver software that meets ISO 26262 and ISO/SAE 21434 requirements more efficiently.
Infineon targets to provide AURIX RC1 microcontroller samples in the first half of 2027.
Related Content
- Accelerating the shift to next-gen SDVs with zonal MCUs
- Making the case for MRAM in software-defined vehicles
- Unveiling the Transformation of Software-Defined Vehicles
- Software-defined vehicle (SDV): A technology to watch in 2025
- Why Holistic Digital Twins are Needed to Accelerate SDV Development
The post MCU revitalizing SDVs with diverse compute, virtual prototyping appeared first on EDN.
Amazon’s fall 2026 smart home and business thoughts: Enter the drones and robots?

Incremental tweaks to existing products, as well as a few new derivative devices, are all par for the course. But autonomous security, both ground- and air-based, is something else entirely.
Within my late-October coverage of Amazon, Apple and Microsoft’s latest mobile computing-related announcements, I penned the following foreshadowing:
Speaking of October Amazon coverage, by the way, the company chose today, at the tail-end of competitor Apple’s three-day announcement cadence, to roll out this year’s collection of Echo speakers (one even complete with a camera? SMH), smart displays and such. I won’t be covering them in this particular piece, so to tide you over until I have time to discuss them, I’ll hand you over to Engadget (or any of the other usual suspects, for that matter) for coverage purposes.

The aforementioned additional Amazon announcements had arrived in my inbox only one penned paragraph prior to when I then wrote the above coverage quote, in fact. The late October piece’s already sizeable length (not to mention the fact that I was motivated to publish it in a timely manner) prompted my decision to defer in-depth coverage of the additional Amazon hardware until later.
Later is now. And what ended up motivating me to translate aspiration into action wasn’t the “Echo speakers, smart displays and such” in and of themselves, but in combination with additional, even more compelling, products launched by Amazon’s Ring subsidiary yesterday.

Hold that thought. Let’s first rewind two weeks, back to October 28, to be precise.

As with its predecessors, the latest 5th generation of the now-spherical Echo Dot can act as an extender (with wireless-only backhaul capabilities, perhaps obviously) for an (Amazon-owned) Eero mesh Wi-Fi network. And speaking of generational consistency, while Amazon’s claims that “We’ve built a smart home hub directly into Echo Dot for the first time” are, I suppose, strictly accurate, my research suggests that support for Matter, Thread and Zigbee has also been retrofitted to the prior two Echo Dot generations via post-release software updates. That said, none of them can work as a full-blown Thread border router; for that, you’ll need a mainstream Echo or, for that matter, any of several Eero devices.
Amazon also touts the improved full-range speaker built into this latest Echo Dot, claiming that delivers “more back volume for crisp vocals and 50% more bass than the last generation.” The company has added a fourth microphone for enhanced ambient noise suppression and 360° voice command (and other meaningful sound-capture…hold that thought…) capture purposes. Speaking of commands, specifically the device’s response cadence and accuracy, the onboard “edge” processor is upgraded as well, to Amazon’s custom-designed AZ3 silicon. And of course, there’s also a version for kids.

Since we’re all about constraints-driven price increases nowadays, I also feel compelled to note that the 5th generation Echo Dot is $20 more than its 2020-introduced predecessor: $99.99 vs $79.99. Echo Dot for Kids is $10 more: $109.99. And an optional stand is a further $39.00 adder.
Smile for the (Echo Studio with) camera
Next, let’s delve into my earlier SMH rebuke. The “with Camera” variant of last year’s also-now-spherical latest-generation Echo Studio costs $30 more than its visual intelligence-bereft sibling, $249.99 vs $219.99. Again, there’s also an optional $39.99 stand upgrade. The camera itself has 13 Mpixels of resolution. And regarding SMH, the device’s relevance (to Amazon, albeit not necessarily to Amazon’s customers) became much more obvious subsequent to yesterday’s announcements. Again, hold that thought…really, I’m not (just, at least) trying to be a tease…
A smart display upgrade
Next up is the Echo Show 16 (versus its 15” predecessor from 2021), complete with the same enhanced display technology (in both standard and anti-glare Nanomatte options) found in last month’s Alexa Tablet 12 Pro. To simply call this iteration of the concept a “smart display” is something of a misnomer, as “Fire TV” support is first-time built in, along with commensurate updates to the audio architecture: eight custom micro woofers and two tweeters, to be precise. It’s wall-mountable by default, with display variant-dependent pricing starting at $499.99. Both static ($69.99) and swivel-and-tilt ($124.99) optional stands are also offered.
Derivations of existing foundations
Echo Time is a function-optimized (and display-inclusive) variant of the conventional Echo or, if you prefer, a richer-information rethink of the Echo Spot predecessor, priced (for adults) at $199.99 and (kids) at $10 more, in both cases (I bet you already know what I’m about to say) with an optional matching adjustable stand for a $39.99 increment.

Unsurprisingly, it’s both voice-commandable and the display is touch-controllable. Intended to be an alternative to the smartphone that likely currently takes up residence at the bedside nightstand each evening for many of you, its user-optional capabilities include a “smart” alarm clock that gently (cautiously?) begins to wake you up ahead of the preset time if it senses you’re (definitively, back-referencing the earlier “cautiously”) beginning to stir early. How exactly it does this is unclear; Amazon’s announcement only provides the following hand-waving.
It’s powered by Omnisense, our sensor fusion technology: room temperature sensors and presence detection build your sleep routine, while ultrasound detects breathing and proximity—all without a wearable.
That all is in seeming contrast to the low-energy radar-based Halo Rise sleep tracker, announced in late 2022 and subsequently EOL’d by the company (hold that thought until tomorrow).

And then there’s the equally function-optimized Alexa Photo frame, priced starting at $199.99, depending on what color option you prefer.

Take an Echo Show, defeature it via software neuter, make it look like a matte- and wood frame-surrounded real picture, and…well, that’s about it. But hey, the detachable magnetic stand is bundled this time!
Security: unleash the mobile autonomy!
And now I finally get around to addressing the “tease” from yesterday. Mobile robots first: does anyone remember Amazon’s Astro, which I’ve previously mentioned at least twice: in 2022 and again (admittedly replete with no shortage of snark) a year later?

First unveiled in late 2021, it was originally intended for consumer use in the home, as this stock shot suggests, but never exited invite-only limited (and customer-paid, mind you) beta status:

Well, it’s now broadly available for preorder (albeit not shipping until December 16, and then only in the U.S.), renamed the Ring Rover Cam and priced at $999.99 (plus, presumably, an unmentioned ongoing service subscription fee), albeit repositioned for business use cases, as you may have already noticed from the GIF at the top of this writeup. Roomba robot vacuum cleaner analogies follow:
- Self-docking charger included
- Initially self-maps a space up to 5000 sq ft.
Some of the initial coverage I’ve seen elsewhere indicates that company spokesperson talking points explicitly recommend it for use on single-floor structures with only hard surfaces. Translation: no shag carpet, and no stairs…further to my Roomba analogies, I wonder if this was at least part (along with price) of what was behind the business-use reposition?
Once the robot-on-rollers understands its surroundings, you can configure it to periodically patrol a predetermined path around that space, complete with a motorized “periscope” camera extending upward to nearly 4 ft. max above the robot on a mast, to see over counters, desks, retail shelving and other obstacles. Plus, if a Ring sensor (cameras, microphones, doors and windows, etc., along with, I suspect and to my earlier allusions, broader Blink and other Amazon-branded and -affiliate gear in the future) is triggered, it can relocate itself to that location to 360° audio- and video-record the goings-on. Speaking of audio, it also integrates an alert siren feature (along with a light tower), and its two-way sound capabilities let you remotely join in on the yelling-at-hooligan, too, if you desire.
Presumably safe from FCC interference(potentially obscure subhead reference)
Sound farfetched (or, then again, maybe not)? You ain’t seen nuthin’ yet. Meet the Ring Drone Cam, this time not shipping until January 27 (again, U.S.-only), not yet available for preorder, and priced at $249.99 (the same likely service subscription adder as before also applies here).

Similar to its “grounded” sibling, you can optionally set it up to periodically patrol the premises (the home, this time) complete with a security guard-reminiscent flashlight to give outside folks considering an invasion of your otherwise dimly lit residence (and unable to hear its identity-giveaway propellers) second thoughts. And it’ll also respond to activation triggers from other (Ring-only, at least for now) sensors in your smart home ecosystem.
Eight minutes of flight time. Followed by an hour in the dock for a full recharge (40 minutes for a 5-minute jaunt). Is it just me, or does it also remind you (aside from the color) of a DJI Neo?

Yeah, I thought so, too. Ring has apparently been dabbling with the technology for a decade now, even before its acquisition by Amazon, but only now was capability (and pricing) apparently up for meeting the challenge. In part, particularly interestingly to me since I just published an editorial suggesting the converse, battery-sucking (along with wallet-contents-sucking, I assume) local “edge” inference was avoided in favor of the “cloud” bidirectional-data-transfer alternative. I only hope that if the drone doesn’t get a response from the “cloud” in time, it’ll be smart enough to stop itself before it smacks into a wall…
In all seriousness, I’ll close with an excerpt of Engadget’s coverage, including quotes from Ring founder Jamie Siminoff, eerily echoing “engineering tradeoff” points I made a few years back.

Siminoff said at a media briefing in New York this week that previous iterations of the Drone Cam simply weren’t good enough to launch to the public. After the first drone was announced in 2021, the company put products in boxes but never shipped them out, because, according to Siminoff, they “just didn’t work well enough.” Another false start happened in 2025, and the company was finding problems that required more sensors and “more compute,” which then demanded more power and bigger batteries.
With the added weight, the drone had to “fly harder,” which created safety concerns that led to larger shrouds. That then impacted flight performance as less air could get through. Finally, to do all that in a device would probably drive its retail price up past $5,000, Siminoff said. That would mean it wouldn’t really be right for consumers. What allowed Ring to drop the Drone Cam’s weight and price was cloud-processing and what Siminoff calls “intelligence.” And it sounds like the company is calling it the “AI Pilot,” which powers both the Ring Drone Cam and the Rover Cam.
That system basically “maps the space, suggests patrol points, and autonomously navigates around obstacles,” according to a Ring press release. This is basically cloud processing to tell the drone where to go when a motion detector goes off, for instance. So instead of requiring a local AI model and the processors to run those, the Drone Cam is mostly reliant on Wi-Fi.
Fascinating. At least to me. What think you? Please share your thoughts in the comments!
—Brian Dipert is the associate editor, as well as a contributing editor, at EDN.
Related Content
- Amazon, Apple and Microsoft: New mobile computing platforms take off
- Amazon and Google: Can you AI-upgrade the smart home while being frugal?
- Amazon, Microsoft and Google: Services, software and system launch events for the fall (but not for the frugal)
- Fall tech events twain: Apple’s (potential) loss is Amazon and Google’s gain
- Cloud to edge AI: If and when, to what degree, and how and why
The post Amazon’s fall 2026 smart home and business thoughts: Enter the drones and robots? appeared first on EDN.
PMIC boosts efficiency in 1.6T optical modules

Jeju is a custom multiphase PMIC from MaxLinear designed for DSP-based 1.6T pluggable optical modules used in AI infrastructure. Compatible with 3-nm and 4-nm CMOS optical PAM DSPs, the device achieves peak power efficiency of up to 95% and saves up to 0.5 W per 1.6T PAM4 DSP compared with conventional PMICs.

Optimized for MaxLinear’s Rushmore 1.6T PAM4 DSP, Jeju also targets 1.6T module designs across the industry. By reducing power consumption and heat dissipation, the PMIC can lower thermal management costs and improve manufacturing yield, according to the company.
Tight DSP rail regulation during load transients minimizes required output capacitance, while 0.5% typical DC output-voltage accuracy, low-noise power delivery, and remote voltage sensing help reduce operating voltage margins and DSP dynamic power consumption. The PMIC comes in a small 54-ball WLCSP package for high-density pluggable optical modules.
Jeju (MxL77904) is expected to begin sampling to customers in February 2027.
The post PMIC boosts efficiency in 1.6T optical modules appeared first on EDN.
NXP simplifies robotics system development

NXP’s unified robotics platform speeds robotic-system development with a modular, open-source SDK and prototype-ready reference designs. It is built on the NXP Neural Axis Architecture, a distributed foundation that securely connects sensing, real-time control, AI processing, and communications across robotic systems.

The hardware and software ecosystem lets developers scale from individual functions to complete physical AI systems. Its SDK and reference designs cover autonomy, sensing, flight control, and motor control applications for drones, autonomous mobile robots (AMRs), and humanoid robots.
Designed to work with industry-standard robotics frameworks, the SDK integrates established open-source technologies such as PX4, Zephyr, and ROS 2. It also provides supported drivers, middleware, reference applications, configuration tools, and reusable software components. NXP’s reference designs draw on its broad hardware portfolio, combining secure processing, deterministic real-time control, and safety-ready system architectures.
The unified robotics platform is available now, with initial reference designs targeting drones. Additional enablement for service robots, AMRs, and other autonomous systems is expected in 2H 2027.
The post NXP simplifies robotics system development appeared first on EDN.
Isolated gate drivers serve power-switching needs

Diodes’ API21550 and API21552 dual-channel isolated gate drivers provide high-voltage isolation for power-switching applications such as motor drives and solar inverters. They use a silica-based capacitive isolation barrier rated for breakdown voltages up to 13 kV. According to the company’s isolation reliability calculations, the barrier has a predicted lifetime exceeding 40 years.

The API21550 has separate high- and low-side outputs with adjustable deadtime for shoot-through protection in isolated half-bridge applications. The API21552 has dual independent outputs for dual low-side, dual high-side, or half-bridge configurations. Both achieve a minimum CMTI of 150 V/ns to help maintain signal integrity in the presence of fast voltage transients.
Peak source and sink currents reach 4 A and 6 A, respectively, with output-side supply voltage up to 30 V and input-side voltage of 3 V to 5.5 V. Both devices feature 40-ns typical propagation delays, 7-ns maximum pulse-width distortion, and external disable functions. Depending on package type, reinforced isolation provides up to 5.7 kV withstand voltage and 12.8 kV surge voltage.
The API21550 and API21552 are available in small-outline (SO) packages for $0.99 each in 1,000-piece quantities.
The post Isolated gate drivers serve power-switching needs appeared first on EDN.
Automotive LED driver advances animated lighting

The Melexis MLX81132 automotive LED driver supplies 24 constant-current channels for high-pixel-count RGB animated interior lighting. Based on the Melexis Light Bus (MeLiBu 2.0), the programmable driver multiplexes its 24 channels, allowing a single IC to control up to 48 individual LEDs or 16 RGB pixels. By sharing processing and driver functionality across multiple pixels, the MLX81132 reduces the cost per pixel in applications such as dashboards, doors, seats, center consoles, and roof lighting.

Operating from a 5-V supply, the MLX81132 provides configurable LED currents up to 80 mA and 16-bit PWM control. Its integrated 16-bit MCU handles pixel control and color calculations locally, while individual LED diagnostics and temperature compensation help maintain consistent color and intensity.
The MeLiBu 2.0 interface provides data rates up to 4 Mbps and individually addresses each IC for synchronized control of distributed lighting nodes. The MLX81132 was developed according to ISO 26262 and supports safety-related applications up to ASIL B.
Samples of the MLX81132 are available now. For more information, contact a Melexis representative or visit the product page.
The post Automotive LED driver advances animated lighting appeared first on EDN.
Wideband switch eases RF front-end design

A reflective SPDT RF switch, the PE423213 from pSemi, operates from 0.3 GHz to 10.6 GHz with a typical supply current of just 95 nA. It supports multiple wireless standards, including ISM, WLAN, Wi-Fi, Bluetooth, and UWB, simplifying RF front-end design. Its broad frequency coverage and ultra-low current consumption make it well-suited for secure access control, smart-home automation, wearables, and industrial IoT.

The PE423213 is built on pSemi’s UltraCMOS+ silicon-on-insulator process. Typical insertion loss is 0.4 dB at 6 GHz, 0.5 dB at 8.5 GHz, and 0.7 dB at 10.6 GHz. Isolation at the same frequencies is 28 dB, 25 dB, and 18 dB, respectively. A typical switching time of 100 ns enables responsive RF path selection.
Operating from -40°C to +105°C, the PE423213 combines a 2-kV ESD rating with a compact 1.6×1.6-mm DFN package for space-constrained, battery-powered, and temperature-sensitive applications.
pSemi will showcase the PE423213 for the first time at Electronica 2026. Visit the product page for additional product and ordering information.
The post Wideband switch eases RF front-end design appeared first on EDN.
Doubly twisted DPOT ganged programming

Select and set one or both channels of a dual digipot with a twist of the wrist.
Tandem potentiometers (i.e., pots that share a common control shaft) have been around for an extremely long time. That’s because they can be extremely handy. Adjusting the volume on a stereo sound system, tuning time constants in a multiple pole filter, or setting the output frequency of a Wien bridge sinewave oscillator…these are just a few obvious examples (of many) of their utility.
But of course, when mechanical pots share a common shaft, they share it forever, and therefore must turn together, likewise forever. This reality remains equally true when it suits the application at hand and when it doesn’t.
Wow the engineering world with your unique design: Design Ideas Submission Guide
This Design Idea (with the circuit shown in Figure 1) implements a variable frequency oscillator circuit that programs the sections of a dual dpot with easily controllable up/down steps. It generates step rates from zero to 20 Hz together with an up/down step direction signal. Both are controlled by simply (and quickly) twisting one knob on an inexpensive linear manual potentiometer a fraction of a single turn.
Three-position (center off) SPDT switch S1 controls the pots’ chip select inputs, which determines which, either individually or collectively, pot section(s) respond(s).

Figure 1 The 256-step (8-bit resolution) dual-channel DPOT U2 can be programmed up/down by a partial turn of R1, with either channel X or Y responding alone (per switch S1’s position on X or Y), or with both ganged together (per S1 in the X and Y position).
Here’s how it works.
Current to frequency converter U1 generates dpot clock pulses at 20 Hz-0-20 Hz, controlled by the sum of Q1+Q2 collector currents set ~100 nA to 5 µA by R1. The Vpp amplitude of the sawtooth waveform on C1 is set by the R7/R8 and 555 internal dividers to ~250 mV. A1 sets the up/down step direction.
When the sum of collector currents is less than 500 nA, R4 forces the step frequency to zero. This condition corresponds to R1’s wiper centered at (or near) the midpoint of travel, acting with the antilog behavior of the transistor collector current vs Vbe. Meanwhile, 5 µA yields 20 Hz. This occurs when R1 approaches either its clockwise or counterclockwise limit.
Figure 2 shows the relationship of step rate vs R1 position.

Figure 2 This graph shows the dpot step rate and direction as a function of R1.
Comparator A1 sets the dpot step direction to UP if R1’s wiper is clockwise of midpoint, DOWN for counterclockwise. Q1 sources the majority of current to U1 for UP steps, with Q2 taking over for DOWN.
Programming a desired setpoint is accomplished thusly:
- Turn R1 in the desired direction until stepping begins at a rate appropriate to the size of the intended setpoint change.
- As the new setpoint is approached, gradually slow the step rate to a dead stop by returning R1 toward the midpoint.
With a “bit” of practice, a U2 setpoint change of 256 steps can be accurately completed in less than 20 seconds. If you need more speed than that, the necessary modification is trivial. Just reduce C1:
Max step rate = 20Hz/C1 for C1 in µF.
If more ganged channels are needed, additional pots can obviously be added, virtually ad infinitum. Thus concluding with the highfalutin Latin phrase of the day. You’re welcome.
Stephen Woodward‘s relationship with EDN’s DI column goes back quite a long way. Over 200 submissions have been accepted since his first contribution back in 1974. They have included best Design Idea of the year in 1974 and 2001.
Related Content
- Finger-friendly DPOT pushbuttons do ups, downs, and dittos
- Push to increase, decrease a digital potentiometer
- Synthesize precision Dpot resistances that aren’t in the catalog
- Op-amp wipes out DPOT wiper resistance
- Digital potentiometer simulates log taper to accurately set gain
- Push to increase, decrease a digital potentiometer
- Synthesize precision bipolar Dpot rheostats
The post Doubly twisted DPOT ganged programming appeared first on EDN.
Agentic AI streamlines embedded software development for MCUs

Texas Instruments is pairing standard AI agents and models with its resource library to bolster embedded designs that incorporate its microcontrollers, wireless connectivity devices, and radar system-on-chips (SoCs). TI claims that by strengthening the agentic AI capabilities of its CCStudio ecosystem, it provides a purpose-built skillset for embedded developers, reducing software migration time from months to days.
Agentic AI capabilities in CCStudio dramatically shorten every stage of embedded development while moving beyond generative AI code assistance toward autonomous development in which an agentic AI framework injects device-specific knowledge directly into the AI tools engineers already use.

CCStudio strengthens agentic AI capabilities to streamline embedded software development across MCUs. Source: Texas Instruments
Amichai Ron, senior VP for embedded processing and DLP products at TI, calls embedded software development an incredibly manual and time-consuming process. But he also acknowledges that it has been significantly changing over the last few years with agentic AI. Device migration, system configuration, and debugging are all integrated with agentic AI built specifically around embedded expertise.
For the past two years, design engineers have used generative AI tools to write code faster. But they often struggle to complete complex embedded development tasks because they lack hardware-specific context. Agentic AI frameworks can help address this challenge.
How it works
An agentic AI framework injects device-specific knowledge—including software development kits (SDKs), pin configurations, and peripheral data—directly into the workflow through Model Context Protocol (MCP) servers. Next, the AI models improve accuracy, reduce hallucinations, and produce implementation-ready outputs.
Moreover, CCStudio’s IDE exposes its core capabilities to industry-standard AI agents, letting them autonomously generate code, configure peripherals, build the application, flash it to the device, and debug it. Developers can also use simple language to move through the full development workflow in CCStudio IDE or CCStudio for VS Code without switching tools or rebuilding context.

Agentic AI in the CCStudio IDE allows developers to autonomously generate code, configure peripherals, build the application, flash it to the device, and debug it. Source: Texas Instruments
When a design engineer prompts a preferred AI tool to migrate code, the agentic AI model autonomously navigates the full migration process, while preserving the developer’s existing software investment. Here, specialized subagents handle a distinct phase of code migration automatically. They analyze the source project, configure peripherals, update code and API calls, and iterate through build errors to resolution.
That’s how an agentic AI framework offloads repetitive, time-consuming migration tasks to a specialized skillset. This enables developers to accelerate complex design tasks from months to days and focus on system-level design and innovation.
Agentic AI capabilities in CCStudio are available today across TI’s general-purpose and real-time MCUs, wireless connectivity devices, and radar SoCs. However, with a modular architecture spanning task-specific skills, MCP server integrations, and context injection, agentic AI in CCStudio is designed to continuously expand support for new devices, updated SDKs, and emerging edge AI development workflows.
TI is demonstrating agentic AI workflows in CCStudio IDE and CCStudio for VS Code at electronica 2026. These live demonstrations at its booth in Hall C4 cover end-to-end application development from system configuration to debugging.
Related Content
- Scaling Down Is the New Scaling Up
- When Engineering Apps Need Agentic AI
- A Look at Agentic AI in the EDA Engineering Workflow
- Can Agentic AI Solve the Embedded Software Problem?
- How Agentic AI Accelerates Edge AI Software Development
The post Agentic AI streamlines embedded software development for MCUs appeared first on EDN.
LTE Cat 1bis or 5G RedCap? RF design decisions behind an IoT modem refresh

Replacing an IoT modem is rarely a drop-in component change. The new module may fit the same product category and promise lower power or longer network support, but its band set, receive architecture, and certification path can force changes to the antenna, PCB, and enclosure. The choice among LTE Cat 1bis, LTE-M, NB-IoT, and 5G Reduced Capability (RedCap) should therefore be made as an RF system decision, not from a modem datasheet alone.
RedCap has now moved beyond specifications and demonstrations. A growing range of Release 17 chipsets, modules, and industrial devices is commercially available. So, operators are enabling the technology on 5G standalone networks, and Global Certification Forum (GCF) has established a certification route for RedCap products. The engineering question is therefore shifting from what RedCap is to what adopting it changes in the finished device.
Define the deployment requirements
Before asking whether 4G or 5G is the better fit, the design team needs to establish where the product must connect, which operators it must support, and how long it’s expected to remain in service. Cat 1bis uses ordinary LTE infrastructure and retains Cat 1’s nominal 10-Mbps downlink and 5-Mbps uplink while reducing the receiver to one-antenna path.
LTE-M and NB-IoT trade data rate for narrow bandwidth, coverage enhancement, and low-power operation. RedCap, introduced in 3GPP Release 17, occupies a different tier: it brings a reduced-complexity device onto 5G NR, with a maximum 20 MHz bandwidth in FR1 and without carrier aggregation.
Although they are often presented as generations on a roadmap, these technologies are not successive rungs on a migration ladder: LTE-M and NB-IoT remain appropriate for low-data, long-life endpoints, while RedCap addresses applications needing more throughput or lower latency than LPWA can provide. It also depends on 5G standalone network support. A global or roaming product may therefore obtain a more predictable footprint from Cat 1bis, whereas a product for a known private 5G network can make a much stronger case for RedCap.
Once the deployment footprint is clear, the next step is to define the bands required by the target countries, operators, and module variants. Low-band coverage around 600 to 960 MHz is often decisive for range and in-building service, but it also sets the most difficult physical requirement.
The wavelength is long, so a small antenna and short PCB ground plane pay an efficiency and bandwidth penalty. A RedCap design may also add NR bands above the range covered by an established LTE antenna, including mid-band. “Sub-6 GHz” on two datasheets does not make them interchangeable.

The above table provides an overview of RF design implications of LTE Cat 1bis, LTE-M, NB-IoT, and 5G RedCap. Source: Taoglas
Compare antenna configurations
Much of Cat 1bis’s appeal comes from its single-antenna architecture, which can eliminate a diversity antenna, its RF feed and the associated placement problem, although this simplicity comes at the cost of reception diversity. Comparisons put the resulting sensitivity or coupling-loss penalty at roughly 3 to 4 dB relative to Cat 1, which matters in basements, metal cabinets, and at the cell edge. A one-antenna product is simpler, but it can lead to mediocre efficiency.
At the lower-throughput end of the design spectrum, LTE-M and NB-IoT usually offer a similarly simple single-antenna configuration, with coverage-enhancement mechanisms that can add link margin through repetitions at the cost of rate, latency, and energy. A utility sensor may therefore favor NB-IoT, while a mobile tracker may favor LTE-M or Cat 1bis. Compare the complete traffic and coverage profile, not sleep current alone.
The antenna decision becomes less straightforward with RedCap because, in FR1, the standard allows either one or two receive branches. A one-Rx implementation supports one downlink MIMO layer; an implementation with two receive branches can support two. Not every RedCap design therefore has the same antenna configuration. The module’s supported bands, Rx branches, and fallback modes define the actual RF architecture.
Where the selected RedCap module uses two receive branches, the mechanical design must accommodate both antennas from the outset, including separation, isolation, and pattern diversity. Quarter-wavelength spacing at the lowest band is usually unrealistic in a compact IoT device. Orthogonal placement, opposite PCB edges, and careful cable routing can reduce coupling, but they do not replace measurement. Poor isolation and highly correlated patterns can erase the expected MIMO benefit.

RF design dependencies are shown in a cellular modem refresh. Source: Taoglas
Account for the complete RF design
Because an embedded cellular antenna does not perform independently of its host, the PCB forms part of the radiating structure, and changes to the ground-plane dimensions can shift resonance and reduce efficiency. The keep-out region must remain clear on every copper layer, while batteries, displays, shields, connectors, fasteners, and cables can detune the antenna even when they sit outside the nominal PCB clearance.
Reusing the existing mechanical design may appear to reduce the cost of a modem refresh, but it can conceal significant RF changes. An LTE antenna that was matched on the previous board may move when the module, power supply, or enclosure changes. Provide a feed matching network, maintain a controlled 50-ohm line, and tune the antenna on the production-intent PCB with the battery and housing installed. A return-loss plot from an open evaluation board is not evidence that the finished product will radiate efficiently.
Where a compact device must cover widely separated bands, a tunable antenna may offer another route; the Taoglas and Telit Cinterion Cat 1bis reference design, for example, pairs an ELS62-W module with a PCS.50.A tunable antenna and uses active switching to extend coverage in a small form factor. This recovers flexibility but adds control logic and every tuning state to the RF test plan.
Antenna efficiency affects more than the RF specification because, in weak coverage, an inefficient design can force the modem to transmit harder or for longer and can trigger repeated connection attempts. Peak gain is a poor selection metric: total efficiency, radiation pattern, feed loss, and the installed environment determine the useful link. For a battery endpoint, better radiated performance may deliver more life than a small difference in the modem’s headline sleep current.
Manage coexistence and interference
Since a refreshed modem rarely operates in isolation, its cellular antenna may have to share a small enclosure with GNSS, Wi-Fi, and Bluetooth antennas, as well as switching regulators, processors, displays, and high-speed buses that generate broadband noise. The problem is reciprocal: cellular transmission can desensitize GNSS, and digital noise can degrade cellular total isotropic sensitivity even with a good antenna match.
Coexistence testing should therefore cover every antenna pair across its operating bands, followed by active testing of the assembled device. Force cellular transmission on known troublesome bands while monitoring GNSS carrier-to-noise density, Wi-Fi throughput, and cellular sensitivity. Mitigation may require more spacing, a different orientation, rerouted cables, shielding, cleaner return paths, or targeted filtering. Reserve those options in the layout rather than discovering self-interference during certification.
Plan testing and certification
Although a pre-certified module reduces the amount of compliance work, it does not certify the host product’s antenna implementation, and the finished device may still require regulatory approval, PTCRB or GCF certification, and operator-specific acceptance. Over-the-air performance is assessed using total radiated power (TRP) and total isotropic sensitivity (TIS), which expose losses and desense hidden by conducted modem tests.
Certification planning is best started while the RF architecture can still change, with a matrix covering the radio technology, module variant, regions, operators, bands, antenna type, and number of RF paths. Schedule passive measurements and active OTA pre-scans on production-intent hardware before tooling is locked. Test low, middle, and high channels in each required band, and include realistic operating modes and accessories.
GCF introduced RedCap certification in 2023 and certified the first RedCap module in 2024, giving device makers an established compliance route. The finished product may still require regulatory approval and operator acceptance, however, so early coordination with the module vendor, test lab, and operator remains valuable.
Release 18 eRedCap is intended to reduce 5G device complexity further, but with commercial chipsets and devices expected in early 2027, it remains a roadmap consideration rather than a direct option for most modem refreshes starting today.
In practice, the choice depends on which constraints carry the most weight: Cat 1bis is a strong option where ordinary LTE coverage, mobility, moderate data rate, and a single antenna are the priorities. LTE-M or NB-IoT remains better suited to small, infrequent payloads where coverage enhancement and battery life dominate.
RedCap makes sense when 5G SA availability, higher throughput, lower latency, private-network integration, or product lifetime justify the new bands, possible second receive path, and new certification campaign. When commercial eRedCap hardware becomes widely available, it’s likely to be most relevant to designs seeking Cat 1bis-class throughput and complexity with a longer-term path onto 5G standalone networks.
The modem may be the line item that starts the refresh, but the antenna system determines whether it works outside the lab. Lock the deployment map and bands first; then make the modem, antenna, PCB, enclosure, and certification strategy an engineering decision.
Baha Badran is global head of engineering at Taoglas.
Related Content
- How 5G Has Changed Engineering Design
- Designer’s guide: 5G RF chips and modules
- 5G RF front-ends: Design challenges and their solutions
- How 5G wireless is impacting the PCB design and manufacturing
- 5G chips and modules power phones, wearables, IoT, and vehicles
The post LTE Cat 1bis or 5G RedCap? RF design decisions behind an IoT modem refresh appeared first on EDN.
Simple circuit detects sequence errors and failure in three-phase power supplies

All-phases presence and correct phase sequencing are both critical conditions for proper three-phase line-powered equipment operation.
Three-phase line-powered equipment is sensitive to phase sequence. For example, if two of the power connections are inadvertently interchanged, a motor will rotate in the reverse direction, which may damage connected equipment such as a pump or the compressor of an air conditioner.
Similarly, if one phase is missing due to, say, a cut wire or a blown fuse while the motor is running, it will overheat and may be damaged in the process. This situation is called single phasing and occurs due to phase failure. Hence monitoring both phase sequence and phase failure are important in three-phase systems. However, inexpensive motor starters such as the Direct on Line (DOL) approach may not offer such protections.
Wow the engineering world with your unique design: Design Ideas Submission Guide
The circuit shown in Figure 1 monitors for both incorrect phase sequence and phase failure. Relay RL1 is energized only if the phase sequence is correct and there is no phase failure. This relay contact can be connected to the starter’s “stop” button (as described in greater detail further in this Design Idea). Any time a fault occurs, it will then switch off the motor.

Figure 1 Use a common transformer to generate a 5 V DC supply voltage for all elements of this phase sequence-and-failure circuit.
The circuit uses a star-connected three-phase transformer. Individual phase voltages are rectified by D1, D2 and D3, and the resultant waveforms are applied to transistors Q1, Q2 and Q3. The waveforms at transistor collectors are square waves, and are further shaped by U1 Schmidt trigger inverters.
How does the phase sequence detector work? U1C sets flip-flop U5A when the R phase comes first. When the Y phase then arrives, it resets U5A through U1A. Its Q output is connected to the D input of flip-flop U5B. The B phase, which comes last, loads the D input to its Q output. Hence, if the phase sequence is correct (R-Y-B in this particular case), the Q output of U5B will be LOW. Conversely, if the phase sequence is reversed to R-B-Y, for example, U5B’s Q output will go HIGH.
And how does the phase loss detector work? The U1A, U1B and U1C outputs are connected to OR gate U2A. If all phases (R, Y and B) are present, the OR gate output will be HIGH. This output is connected to retriggerable monostable U3A. Since the input is just a DC voltage, the U3A output will remain LOW. However, if any phase is missing, the output of the OR gate will instead be a pulse train. This pattern repeatedly triggers U3A, and its output is therefore held HIGH. With the RC values shown, for example, the monostable pulse width is approximately 12 msec.
If the outputs of both sections of the circuit are LOW, this condition translates to both correct phase sequence and no phase failure. The U2B output becomes LOW, Q1 saturates and Relay RL1 gets energized. Its contact can be connected in series with the OFF button of a motor starter, so that the motor trips when this relay de-energizes, thereby sensing a fault.
This simple and low-cost circuit can be added to a DOL or other feature-deficient starter for motor protection purposes. Power supply and ground pins are not shown in Figure 1. These must be connected to VDD and VSS (ground). The same three-phase transformer can be used to generate the 5 V supply voltage needed for all portions of this circuit using a LM7805 voltage regulator. The three-phase power input is connected to terminal block (TB) J1, with the relay outputs connected to TB J2.
This circuit can be implemented as-is in countries such as India, which uses a 230 V, 50 Hz line power supply. The transformer rating may be changed to 110 V/5 V and 60 Hz to use the circuit in other countries such as the United States, while keeping the other components the same.
Jayapal Ramalingam has over three decades of experience in designing electronics systems for power & process industries and is presently a freelance automation consultant.
Related Content
- Motor Starter – Types & Application
- Driving 3-Phase induction motors
- Measure the AC mains frequency with an ordinary counter
The post Simple circuit detects sequence errors and failure in three-phase power supplies appeared first on EDN.














