Українською
  In English
Microelectronics world news
Compact LEDs expand multi-color lighting options

Cree’s smallest ceramic multi-color LEDs, the XLamp X21 series combines four different-color LED dice in a 2.1 × 2.1-mm surface-mount ceramic package. The compact design enables lighting manufacturers to reduce luminaire size and weight while maintaining beam quality and visual performance. XLamp X21 devices also offer the broadest range of color combinations in Cree’s multi-color portfolio, with 11 different LED die colors across 14 product configurations.

The X21’s compact light source and optimized optical profile enable smaller, lighter, and lower-cost secondary optics for intense, tightly controlled beams. Cree LED testing shows that an X21 paired with a 38-mm color-mixing optic (29% smaller area) delivers a tighter beam angle, higher candela/lumen conversion, and better color mixing than an XLamp XP-L color LED using a 45-mm optic.
The flexibility of the X21 series gives designers greater control over color quality, visual impact, and system design for indoor directional, architectural, entertainment, automotive, and specialty lighting applications.
Samples of XLamp X21 LEDs are available now, with production quantities offered at standard lead times.
The post Compact LEDs expand multi-color lighting options appeared first on EDN.
Cree LED files two patent infringement lawsuits in the USA
DIY ESP32 walkie-talkie: two-way voice and text messaging over radio
A self-built ESP32 walkie-talkie that brings two-way voice and text messaging into a single handheld device. Two identical units talk directly to each other over radio, with no mobile network and no internet. Inside each unit there is an ESP32, an INMP441 digital microphone, a MAX98357A amplifier with a 3 W speaker, a 0.96-inch OLED display, a 4×4 keypad and an nRF24L01 module with an RF antenna. The PCB is designed to measure so it sits comfortably in the hand. The project is by Md Mizanur Rahman, known as ElectroSurgeon, and is rated Advanced: it takes about 3 days of work.
The radio side is handled by the nRF24L01 module, so communication stays direct between the two units and does not go through any infrastructure. The firmware is also programmed with the Arduino IDE, so anyone who has already worked with the ESP32 finds a familiar environment. The code and project files are in Md Mizanur Rahman’s code repository, which is the starting point for rebuilding the two units.
I2S voice and T9 messages on the 4×4 keypadIn voice mode you select Walkie Talkie / Voice Mode from the menu and press the PTT button. Voice is captured by the INMP441 digital microphone over I2S. The ESP32 processes the digital audio and transmits it over radio through the nRF24L01 module to the other unit. The receiving ESP32 reconstructs the audio and sends it to the MAX98357A I2S amplifier, which drives the 3 W speaker. The result is two-way voice communication between the two handhelds.
In message mode you open Messages from the menu and type the text with the 4×4 keypad, using a T9/multi-tap scheme. Then you confirm and the ESP32 sends the data over radio. The receiving device shows the message on the 0.96-inch OLED display. The keypad is also used to navigate the menus, select characters, open the communication modes, confirm commands and control the device. So a single input block handles everything.
What you need to build the two unitsThe basic bill of materials is made up of a few parts, but each one has a precise role in the audio chain and in the radio chain. Here is the list of main components:
- ESP32, the microcontroller that processes audio and messages
- INMP441, digital microphone read over I2S
- MAX98357A, I2S amplifier for the speaker
- 3 W speaker
- 0.96-inch OLED display
- 4×4 keypad
- nRF24L01 module with RF antenna
- 0805 SMD LEDs for the PCB
Assembly revolves around the custom-designed PCB, which holds the board, radio, display and keypad together in a portable battery-powered format. Soldering the 0805 SMD LEDs is the finest part of the job, because the components are small and demand a steady hand. For the audio chain an INMP441 I2S MEMS microphone breakout is enough, while for the link between the two units the catalogue has a 2.4 GHz transceiver module with nRF24L01. For testing the display you can use a 0.96-inch I2C OLED display, handy for trying out menus and messages before moving to the final PCB.
The firmware is written and uploaded with the Arduino IDE. So the work sequence is this: prepare the PCB, solder the components, connect the microphone, amplifier, display, keypad and radio, then upload the firmware to both units. Finally you test short-range communication and check that voice and messages arrive correctly. The project is rated Advanced and takes about 3 days of work, between assembly and hardware debugging.
Related products- I2S MEMS Microphone Breakout – INMP441
- 2.4 GHz Transceiver Module with nRF24L01
- OLED Display I2C 0.96” – VCC/GND/SCL/SDA
The post DIY ESP32 walkie-talkie: two-way voice and text messaging over radio appeared first on Open Electronics.
eInfochips demonstrates end-to-end turnkey ASIC capability
eInfochips, an Arrow Electronics company and a provider of semiconductor and product engineering services, has announced that it has successfully demonstrated its end-to-end turnkey ASIC design capability for the development, fabrication, packaging and realisation of a test chip.
Architecture and features of the test chipThe architecture includes an integrated microcontroller for current and voltage monitoring, intelligent programmable control, diagnostics and software configurability. By combining these functions in a single device, the overall framework reduces component count and board complexity while improving system-level monitoring, protection and control.
Some of the electronic chips developed with the end-to-end turnkey design flow described in the article.
“Customers developing custom silicon often have to coordinate across design, foundry, packaging and the manufacturing ecosystem. This result demonstrates our ability to take greater responsibility along that path, helping customers reduce handoffs, improve accountability and move more efficiently from concept to working silicon.” – Sumit Sethi, Vice President and General Manager, Engineering Services, eInfochips
Expertise and programme supporteInfochips has supported automotive, industrial and semiconductor programmes for more than two decades, with capabilities spanning architecture, IP development, analog and mixed-signal design, verification, DFT, physical design, signoff, post-silicon engineering and manufacturing ecosystem coordination.
This demonstration reinforces eInfochips’ role as an engineering services provider able to support customers across the entire custom silicon development cycle, while adapting the underlying technical expertise to the customer’s specific requirements.
To learn more about eInfochips’ turnkey chip design services, visit: https://www.einfochips.com/services/silicon-engineering/turnkey-chip-design/
The post eInfochips demonstrates end-to-end turnkey ASIC capability appeared first on Open Electronics.
Guerrilla RF announces uplisting to Nasdaq Capital Market
Significantly simpler synchronous square wave circuit for frequency division by even numbers

8-bit synchronous counter divides a frequency counter’s chip count down to 2.
Some weeks ago, EDN published my Design Idea for a square-wave output 100:1 frequency divider requiring only two chips. It prompted some interesting reader comments.
Some folks expressed concern that the asynchronous design, shown in Figure 1, suffers from questionable reliability. Their criticism was credible because the design does rely on timing relationships that, while solidly plausible, are still not explicitly guaranteed by the almighty datasheet.

Figure 1 The datasheet doesn’t guarantee that the reset pulse from U2 pin 6 to U1 pin 2 will always be long enough to reliably clear U1a.
Wow the engineering world with your unique design: Design Ideas Submission Guide
The consensus was that a synchronous design could better adhere to datasheet margins and thus embody better engineering practice and inspire (and deserve) greater confidence.
Fair enough.
But the downside was that synchronous designs also seemed likely to increase circuit complexity. I didn’t really like that, so I scratched around until I found an alternative.
Figure 2 shows the result: a design incorporating a (very) legacy yet (very) capable device, the SN74ALS86x 8bit bidirectional synchronous counter, that evades both the complexity and asynchronicity complications. It implements division ratios up to and exceeding 200:1, produces the desired 50:50 square wave output, and still requires just two chips.

Figure 2 This synchronous divider reliably implements many useful even number ratios between 2 and 242.
Here’s how it works.
As described in the 867/869 datasheet (PDF), U1 is an 8-bit up/down counter with a single synchronous clock input. Positive-going edges of the clock increment, decrement, or parallel-load the counter according to the state of the four mode control bits: S0, S1, -ENT, and –ENP.
Figure 2’s circuit enables U1 to count up until a terminal state is detected by U2a. Then U2 pin 6 goes to zero, enabling U1’s parallel load, which makes two interesting things happen on the next positive-going clock edge.
- Bits A through G are reset, beginning a new counting cycle. The connections between U1’s 7 lower order outputs and U2a’s inputs (see examples in Table 1 below) will determine the division ratio. Additional ratios can be implemented by connecting selected U1 inputs to +5 instead of ground.
- Due to the logic inversion supplied by U2b, bit H is loaded with its previous complement, thus toggling it once every counting cycle and resulting in the promised 50:50 square wave.
Obviously, with only four bits participating in U2a’s decode of U1’s 7-bit state, not all 128 theoretically possible division ratios combinations can be detected and used.
But many of them can be. Table 1 shows several useful examples.
| Divide by 2 = 2 * (0 + 1) | +5 to J, K, L, and M |
| Divide by 10 = 2 * (4 + 1) |
Qc to J |
| Divide by 48 = 2 * ( 16 + 4 + 2 + 1 + 1) |
Qa to J |
| Divide by 100 = 2 * ( 32 + 16 + 1 + 1) |
Qa to J |
| Divide by 200 = 2 * ( 64 + 32 + 2 + 1 + 1) |
Qa to J |
Table 1 Five examples of U1 — U2 connections that implement selected division ratios.
The moral of the story: sometimes a little insurance is a good thing, so long as the premium isn’t too high.
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
- Significantly simpler square wave circuits for frequency division by even numbers
- Frequency division by any even number, with a 50% duty cycle output
- A 50 MHz 50:50-square wave output frequency doubler/quadrupler
- Frequency divider from 1 to 4096 in increments of 1
The post Significantly simpler synchronous square wave circuit for frequency division by even numbers appeared first on EDN.
ASMPT Introduces SIPLACE V L to Expand SMT Placement Platform Capabilities
ASMPT SMT Solutions has expanded its SIPLACE V placement platform with a new variant called SIPLACE V L. The new model offers additional feeder slots, a compact and easily replaceable tray unit, and the ability to handle taller components. These features make the machine suitable for a wider range of electronics manufacturing applications.
ASMPT’s SIPLACE V is a new generation of component placement machines designed to deliver high production speeds, flexibility and consistent quality while protecting manufacturers’ investments. Depending on the application, the platform can improve production performance by up to 30% under actual factory conditions. This is made possible by its rigid machine frame, shorter movement paths and fast-moving main axes, which can accelerate up to 6 G.
By basing the new SIPLACE V L on the same platform architecture as the SIPLACE V, but with additional capabilities, ASMPT follows its proven platform concept. Instead of developing placement machines for specific applications, it based the SIPLACE V on a modular toolbox that makes different machine configurations possible depending on product mix, performance needs and production environment, with the SIPLACE V and SIPLACE V L as model variants.
120 Feeder Slots for Efficient Material SupplyFor the supply of components, the SIPLACE V L features 120 feeder slots – 30 more than the SIPLACE V. This means that extensive component ranges can be kept on the machine, which is particularly advantageous in environments with lots of variants and frequently changing products. The additional feeder slots provide more line configuration leeway and may help to reduce setup costs. To supply components from trays, a feeder table and a Tray Unit SIPLACE V can be combined on each side of the machine. The compact and easily interchangeable Tray Unit is significantly narrower than previous solutions, making it possible to supply components via feeders and trays at high speeds in a compact footprint.
Broad Component SpectrumThe SIPLACE V L also expands the platform’s capabilities in terms of its component spectrum. It processes components with heights of up to 55 millimetres, making it suitable even for demanding odd-shaped components.
Overall, the SIPLACE V platform handles a broad spectrum of components ranging from the smallest 016008M parts to large and heavy components. Various placement heads are available. The CP20 high-speed collect-and-place head places up to 52,500 components per hour with an accuracy of ±25 µm @ 3σ. The highly flexible CPP head for mixed placements switches between collect-and-place, pick-and-place and mixed modes based on software commands. For large and heavy components measuring up to 200 × 150 × 55 mm, the TWIN VHF head with a placement force of up to 100 N is available.
Investment Protection from the StartDespite the essentially new platform architecture, ASMPT placed great emphasis on compatibility. Existing SIPLACE X-Feeders can continue to be used, as can SIPLACE SX changeover tables. Software solutions from ASMPT such as the applications of the WORKS Software Suite and the Factory Solutions continue to be usable as well. As a result, both variants of the SIPLACE V platform fit seamlessly into existing production environments.
With Gigabit Ethernet and free-space optical communication, the SIPLACE V also features a powerful communication architecture that enables the speedy exchange of large data volumes while providing the foundation for further automation advances and the integration of AI-based applications. Standardized interfaces such as IPC-HERMES-9852 and IPC-CFX connect the SMT line with higher-level software systems.
One Platform for Changing Requirements“With the SIPLACE V we have created a platform that is flexibly expandable. The SIPLACE V L represents the next step. It features more feeder slots, more material supply options, and an expanded component spectrum. It allows us and our customers to put together the line configuration that best suits their products and their production requirements while remaining on the same technology platform,” explains Sven Buchholz, VP Product & Product Portfolio Management at ASMPT SMT Solutions.
The post ASMPT Introduces SIPLACE V L to Expand SMT Placement Platform Capabilities appeared first on ELE Times.
EPC Space expands rad-hard GaN HEMT portfolio with plastic QFN and hermetic packaging options
Home automation with the ESP32: managing loads through a web server
We manage loads through relays, remotely, using a smartphone, tablet or PC connected to the network on which a web server is installed.
Home automation is usually described as a set of automated electromechanical systems that, in the home environment, improve the quality of life of the occupants by eliminating human intervention as far as possible; but there is actually something more to it, because home automation includes selected forms of intelligence, a home network and/or a centralised distributed network, logic or a specific control unit. The simplest home automation system is based on an approach in which the functionality is hard-wired and integrated into the system and cannot be changed automatically without the intervention of an expert technician. Modern sensor technology, with the evolution of wireless solutions, expands the possibilities of sensing by connecting communication networks and the physical world, and enables wide-ranging home automation applications.
To introduce you to the potential of control systems in home automation, in this article we propose a simple practical project for controlling relays remotely through a web server.
The projectThe goal of our project is to demonstrate how relatively simple it is to control one or more relay modules remotely using a smartphone, tablet or PC connected to the network on which a web server is installed. The relays can be used to switch electrical loads such as lamps, power sockets, actuators in general, and so on, on and off from a distance. The circuit uses the ESP32 NodeMCU development board (Fig. 1) and a set of 5 relays controlled by the ESP32 through the digital outputs GPIO02, GPIO26, GPIO27, GPIO25 and GPIO33, connected respectively to the relay inputs IN1, IN2, IN3, IN4 and IN5.
Fig. 1 ESP32 NodeMCU development board.
In Fig. 2 you can see the basic block diagram of the relay controller we will implement, while in Fig. 3 we propose the corresponding wiring diagram, that is, the one for the complete system, complete with an 8-channel relay board.
Fig. 2 Basic block diagram of the relay controller.
Fig. 3 Electrical schematic of the relay control system, in this case paired with an 8-relay board.
The ESP32 NodeMCU development board is an IoT platform based on the Espressif Systems ESP-WROOM-32 module; in Fig. 4 you can see its pinout. The ESP-WROOM-32 is a powerful WiFi and Bluetooth BLE 4.2 microcontroller that can be used in a wide range of applications, from low-power sensor networks to more demanding uses such as voice coding, audio streaming and MP3 decoding. The module integrates the ESP32-D0WD chip, which belongs to the ESP32 chip series. The embedded chip is designed to be scalable and adaptive.
There are two CPU cores that can be controlled individually; the CPU clock frequency is adjustable from 80 MHz to 240 MHz. It is also possible to turn off the CPU and use the low-power coprocessor to constantly monitor the peripherals in order to detect any changes. The ESP32 integrates a rich set of peripherals, including capacitive touch sensors, Hall effect sensors, SD-Card, board interface, Ethernet, high-speed SPI, UART, I²S and I²C.
Fig. 4 Pinout of the ESP32 NodeMCU development board.
The integration of Bluetooth, Bluetooth LE and WiFi guarantees a wide range of applications. Using WiFi allows long range and a direct connection to the Internet through a WiFi router, while using Bluetooth lets the user connect conveniently to a phone or transmit at low energy so that other Bluetooth devices can detect it. The sleep current of the ESP32 chip is less than 5 µA, which makes it suitable for battery-powered electronic applications and wearable devices.
The module supports a data transmission rate of up to 150 Mbps and has an antenna output power of 20 dBm, guaranteeing a wide range for the RF signal. The module proves highly suitable for IoT applications, offering advanced specifications and the best performance in terms of electronic integration, range, power consumption and connectivity. The operating system chosen for the ESP32 is freeRTOS with integrated hardware acceleration. It also supports secure (encrypted) OTA (Over The Air) updates, so that users can update their products even after installation, with minimal cost and expenditure of time and effort.
Technical specifications and programming of the boardFig. 5 shows the block diagram of the ESP32 module. The ESP32 NodeMCU development board, being equipped with a micro USB connector, is programmable through a cable connected to the PC (USB-A/micro USB-B), which is also the path used for programming. As for connectivity, it is compatible with the WLAN 802.11 b / g / n and Bluetooth 4.2 / BLE protocols.
The CPU is a 32-bit dual-core Tensilica L108 running at 160 MHz, with 512 kB SRAM and 16 MB of Flash memory. It has 32 digital I/O pins (3.3 V logic levels), 6 analog-to-digital pins and various communication interfaces: 3 UARTs, 2 SPI ports, 2 I²C interfaces and a USB-to-UART interface through the CP2102 chip integrated on the board. The ESP32 NodeMCU development board can be programmed using Arduino code, Lua or MicroPython. Table 1 lists the technical specifications of the ESP32 NodeMCU board.
Fig. 5 Internal block diagram of the ESP32.
Table 1 Technical specifications of the ESP32 NodeMCU development board.
This project uses 5 relays; for convenience these relays can be split across relay boards that can be activated with TTL logic levels, like the ones for Arduino, so several two-relay boards such as the one shown in Fig. 6, one 4-relay board plus one 2-relay board, or an 8-relay board.
These boards typically have a common 5 Vdc supply line, and the control inputs each go to the base (with a limiting resistor in between) of an NPN transistor connected in common-emitter configuration, with the collector driving the coil of a relay.
Fig. 6 Two-relay module.
As a result of this configuration, when an input is taken to a high logic level the corresponding transistor saturates and effectively brings the relay coil to ground; since the other end of the coil is connected to the supply, the relay itself is energised, moving its moving armature and connecting together the Normally Open contact (NA or NO) and the common (C).
On the side near the relays there are three-terminal blocks (high-voltage section up to 250 VAC) for each relay, for connecting electrical loads: Common (COM), Normally Closed (NC), Normally Open (NO); on the opposite side there are pins for powering the relays and for the activation and deactivation command of each relay (inputs). Usually one of the two conductors of the power source of the load to be controlled (for example, one of the two mains voltage conductors) is connected to the COM terminal (common, otherwise indicated as C), breaking it; the piece of cable going to the load is instead connected to the NC or NO (NA) terminal, depending on the application.
NC and NO configurationsThe NC (Normally Closed) terminal is used when you want the relay to be closed at rest. In this mode, NC and COM are connected, that is, the conductor of the power source is common with NC. Conversely, NO (Normally Open) is not connected to COM, so the conductor of the power source connected to COM is not common with NO. Each module has a status LED for each channel (powered in parallel with the coil of the corresponding relay), whose lighting indicates that each relay is activated. Relay boards often have opto-isolated inputs, that is, coupled to the transistor bases through an optocoupler; in this case, with a LOW level applied to input IN1, the optocoupler LED will conduct, the status LED of the corresponding channel will light up, and the transistor inside the optocoupler will conduct, saturating the transistor that will activate the relay.
Having the full changeover contact for each relay, the following scenarios are possible:
- Normally closed configuration (NC): with an input signal at a high logic level, current flows between COM and NC of the relay, while when the input is at a low level the current is interrupted;
- Normally open configuration (NO): with an input signal at a high level the relay is at rest and the current is interrupted, while with a logic zero input the current flows between COM and NO.
There are also relay boards that provide two supply lines: one for the control logic and the other for the relay coils; for this purpose they have a jumper to choose what the coil supply is connected to, that is, whether to the 5V of the logic or to the dedicated contact. The latter configuration is used to electrically isolate the relay from the control circuit (the ESP32, in our case).
Programming the ESP32Having finished describing the hardware of the project, let’s move on to the software side: to program the ESP32 board you first need to install the driver that allows the board to communicate with the PC over USB; for this purpose, the ESP32 microcontroller uses the CP2102 chip for the USB serial interface to the PC.
Connect the ESP32 board to the computer with a USB-to-micro USB cable. If the computer’s operating system does not automatically recognise the CP2102 chip, you need to download the driver from http://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers and unzip it. On Windows, it is enough to install it by running “CP210xVCPInstaller_x86.exe” or “CP210xVCPInstaller_x64.exe”, depending on whether the operating system is 32- or 64-bit; on Mac, you install the DMG file in the uploaded archive. For Windows XP and Vista operating systems you need to install the driver from https://www.silabs.com/community/interface/knowledge-base.entry.html/2017/01/10/legacy_os_softwarea-bgvU .
After disconnecting and reconnecting the ESP32 board, in the list of communication peripherals in Windows a COM port should appear, identifiable as “Silicon Labs CP210x USB to UART Bridge”.
Installing the ESP32 board in the Arduino IDEThe next step is installing the Arduino software from the official site www.arduino.cc (in this article we refer to Arduino software version 1.8.9). When the program starts, from the Arduino IDE you need to install the ESP32 board. From File > Preferences, under “Additional Boards Manager URLs” enter the link https://dl.espressif.com/dl/package_esp32_index.json.
Then, with Tools > Board > Boards Manager, type “esp32” in the search bar; select and install the management firmware for the ESP32 board “ESP 32 by Espressif Sistems”. An image like the one shown in Fig. 7 will appear. Once the installation of the ESP32 board is complete, from Tools > Board, select the “ESP32 Dev Module” board or equivalent, then the upload speed of 115200, and finally select the COM port (on Windows) or ttyUSB (on Mac) corresponding to the CP210x USB to UART Bridge VCP driver. In order to verify that the ESP32 board works, we will test it with an example sketch.
Fig. 7 installation of the ESP32 board.
From the Arduino IDE, with File -> Examples -> WiFi -> WiFiscan, a new sketch called WiFiscan will open. Upload the code to the ESP32NodeMCU board by clicking the “->” (Upload) button. When the compilation and upload of the code are finished, open the Arduino serial monitor and set it to a baud rate of 115200 on the corresponding COM port: on the screen you will see something similar to what is shown in Fig. 8.
Having successfully verified the execution of the WiFiscan example program, we are certain that the ESP32 board works correctly, so we can proceed with the software for the relay controller. In this project a web server is implemented that allows you to control 5 relays via a smartphone, tablet or Personal Computer. By modifying a few lines of the web server code you can define the number of relays you want to control and the assignment of their control pins.
Fig. 8 Result of the WiFiScan sketch on the serial monitor.
To implement the web server we use the ESPAsyncWebServer library, which we will install following these steps: first of all, download the ESPAsyncWebServer.zip library from https://github.com/me-no-dev/ESPAsyncWebServer and copy it into a folder. In the Arduino IDE, with Sketch -> #include library -> Add library from .ZIP file, select the ESPAsyncWebServer.zip library that you downloaded and copied into a folder.
Installing the Async TCP library for ESP32The ESPAsyncWebServer library requires the AsyncTCP library, which we will install following these steps: download the AsyncTCP.zip library from https://github.com/me-no-dev/AsyncTCP and copy it into a folder. In the Arduino IDE, with Sketch -> #include library -> Add library from .ZIP file, select the AsyncTCP.zip library that you downloaded and copied into a folder.
Listing 1 shows the code of the relay controller.
Listing 1
/********* Rui Santos Complete The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. *********/
// Import required libraries #include “WiFi.h” #include “ESPAsyncWebServer.h”
// Set to true to define Relay as Normally Open (NO) #define RELAY_NO true
// Set number of relays #define NUM_RELAYS 5
// Assign each GPIO to a relay int relayGPIOs[NUM_RELAYS] = {2, 26, 27, 25, 33};
// Replace with your network credentials const char* ssid = “REPLACE_WITH_YOUR_SSID”; const char* password = “REPLACE_WITH_YOUR_PASSWORD”;
const char* PARAM_INPUT_1 = “relay”; const char* PARAM_INPUT_2 = “state”;
// Create AsyncWebServer object on port 80 AsyncWebServer server(80);
const char index_html[] PROGMEM = R”rawliteral( <!DOCTYPE HTML><html> <head> <meta name=”viewport” content=”width=device-width, initial-scale=1″> <style> html {font-family: Arial; display: inline-block; text-align: center;} h2 {font-size: 3.0rem;} p {font-size: 3.0rem;} body {max-width: 600px; margin:0px auto; padding-bottom: 25px;} .switch {position: relative; display: inline-block; width: 120px; height: 68px} .switch input {display: none} slider {position: absolute; top: 0; left: 0; right: 0; bottom: 0; background-color: #ccc; border-radius: 34px} .slider:before {position: absolute; content: “”; height: 52px; width: 52px; left: 8px; bottom: 8px; background-color: #fff; -webkit-transition: .4s; transition: .4s; border-radius: 68px} input:checked+.slider {background-color: #2196F3} input:checked+.slider:before {-webkit-transform: translateX(52px); -ms-transform: translateX(52px); transform: translateX(52px)} </style> </head> <body> <h2>ESP Web Server</h2> %BUTTONPLACEHOLDER% <script>function toggleCheckbox(element) { var xhr = new XMLHttpRequest(); if(element.checked){ xhr.open(“GET”, “/update?relay=”+element.id+”&state=1”, true); } else { xhr.open(“GET”, “/update?relay=”+element.id+”&state=0″, true); } xhr.send(); }</script> </body> </html> )rawliteral”;
// Replaces placeholder with button section in your web page String processor(const String& var){ //Serial.println(var); if(var == “BUTTONPLACEHOLDER”){ String buttons =””; for(int i=1; i<=NUM_RELAYS; i++){ String relayStateValue = relayState(i); buttons+= “<h4>Relay #” + String(i) + ” – GPIO ” + relayGPIOs[i-1] + “</h4><label class=\”switch\”><input type=\”checkbox\” onchange=\”toggleCheckbox(this)\” id=\”” + String(i) + “\” “+ relayStateValue +”><span class=\”slider\”></span></label>”; } return buttons; } return String(); }
String relayState(int numRelay){ if(RELAY_NO){ if(digitalRead(relayGPIOs[numRelay-1])){ return “”; } else { return “checked”; } } else { if(digitalRead(relayGPIOs[numRelay-1])){ return “checked”; } else { return “”; } } return “”; }
void setup(){ // Serial port for debugging purposes Serial.begin(115200);
// Set all relays to off when the program starts – if set to Normally Open (NO), the relay is off when you set the relay to HIGH for(int i=1; i<=NUM_RELAYS; i++){ pinMode(relayGPIOs[i-1], OUTPUT); if(RELAY_NO){ digitalWrite(relayGPIOs[i-1], HIGH); } else{ digitalWrite(relayGPIOs[i-1], LOW); } }
// Connect to Wi-Fi WiFi.begin(ssid, password); while (WiFi.status() != WL_CONNECTED) { delay(1000); Serial.println(“Connecting to WiFi..”); }
// Print ESP32 Local IP Address Serial.println(WiFi.localIP());
// Route for root / web page server.on(“/”, HTTP_GET, [](AsyncWebServerRequest *request){ request->send_P(200, “text/html”, index_html, processor); });
// Send a GET request to <ESP_IP>/update?relay=<inputMessage>&state=<inputMessage2>
server.on(“/update”, HTTP_GET, [] (AsyncWebServerRequest *request) {
String inputMessage;
String inputParam;
String inputMessage2;
String inputParam2;
// GET input1 value on <ESP_IP>/update?relay=<inputMessage>
if (request->hasParam(PARAM_INPUT_1) & request->hasParam(PARAM_INPUT_2)) {
inputMessage = request->getParam(PARAM_INPUT_1)->value();
inputParam = PARAM_INPUT_1;
inputMessage2 = request->getParam(PARAM_INPUT_2)->value();
inputParam2 = PARAM_INPUT_2;
if(RELAY_NO){
Serial.print(“NO “);
digitalWrite(relayGPIOs[inputMessage.toInt()-1], !inputMessage2.toInt());
}
else{
Serial.print(“NC “);
digitalWrite(relayGPIOs[inputMessage.toInt()-1], inputMessage2.toInt());
}
}
else {
inputMessage = “No message sent”;
inputParam = “none”;
}
Serial.println(inputMessage + inputMessage2);
request->send(200, “text/plain”, “OK”);
});
// Start server
server.begin();
}
void loop() {
}
Customising the softwareYou can set the relay configuration to normally open (NO) or normally closed (NC) by changing the variable “#define RELAY_NO true”: true for NO, false for NC. By changing the variable “#define NUM_RELAYS 5”, you can define the number of relays you want to include in the project.
Of course, the number of relays set by the NUM_RELAYS variable must match the number of GPIOs assigned in the relayGPIOs array; in fact, with the array variable “int relayGPIOs [NUM_RELAYS] = {2, 26, 27, 25, 33};”, you can define the ESP32 GPIO relay control digital ports. Finally, you need to enter the WiFi network credentials in the following variables:
const char * ssid = “REPLACE_WITH_YOUR_SSID”;
const char * password = “REPLACE_WITH_YOUR_PASSWORD”;
After installing the required libraries and making the desired software changes in the code, copy the code into a new sketch and upload it to the ESP32 board.
Practical buildAt this point, with all the necessary software installed, you can go ahead and assemble the components of the relay controller prototype, that is, the ESP32 board, five relays, some jumpers and an experimental breadboard, following the connections of the wiring diagram shown in Fig. 3.
For the power supply of the circuit it is advisable not to use the PC’s USB ports, so the prototype can be powered by connecting an external 5V power supply to the micro USB connector of the board, or by connecting an external power supply with a voltage from 7 to 12 V to the 5V (Vin) and GND pins of the board; in both cases, the external power supply must be able to deliver a current of at least 150 mA.
Be careful that the ESP32 board must be powered by only one of the above voltages. Using more than one power supply at the same time could irreparably damage the board and the corresponding power supplies.
Testing the systemOpen the serial monitor set to a baud rate of 115200 and press the RESET button. On the monitor you will be able to read the IP address of the ESP32 board, which you should note down.
Now, open a browser on a device connected to the local WiFi network and type the IP address of the ESP32 you noted down earlier to access the web server.
If everything has been done correctly, on the display of the mobile device or on the PC monitor you should see buttons in a number corresponding to the number of relays defined in the code (Fig. 9). Well, with this we are done.
Fig. 9 Web server on a smartphone (Source: Random)
The post Home automation with the ESP32: managing loads through a web server appeared first on Open Electronics.
Vishay Introduces 550 V and 600 V Snap-in Power Capacitors for High-Voltage Applications
Vishay Intertechnology has expanded its 259 PHM-SI series of snap-in power aluminum electrolytic capacitors by introducing new 550 V and 600 V versions. Developed by Vishay BCcomponents, these capacitors are designed for high-voltage applications in industrial equipment, energy systems and medical devices. The new options can help designers use fewer components, save circuit board space, reduce costs and improve the reliability of power systems.
Traditionally, engineers have needed to connect three 400 V to 450 V capacitors in series to handle DC bus voltages between 800 V and 1100 V. This arrangement requires additional balancing resistors, increases circuit complexity and creates more potential points of failure.
With the new 550 V and 600 V capacitors, designers can use fewer components in series and reduce or eliminate the need for voltage-balancing circuits. This helps save circuit board space, lower component costs and improve system reliability and service life by providing greater voltage-handling capacity.
The new 550 V and 600 V capacitors offer high capacitance and voltage ratings in a range of compact sizes. Available configurations include 330 µF / 550 V and 330 µF / 600 V in the 35 mm x 45 mm case, and 470 µF / 550 V and 390 µF / 600 V in the 35 mm x 55 mm case. At these values, the 259 PHM-SI series offers ripple current ratings from 2.14 A to 2.58 A, allowing the capacitors to withstand the demanding switching currents of today’s high power converters. Featuring a cylindrical aluminum case insulated with a blue sleeve, the RoHS-compliant devices are also available with 3-pin keyed polarity snap-in terminals.
As polarized aluminum electrolytic capacitors with a non-solid electrolyte, 259 PHM-SI series devices are ideally suited for buffering, filtering, and energy storage in compact power applications. These include wallboxes and stationary electric vehicle (EV) chargers; industrial motor drives, heating and cooling systems, lamp drivers for UV water treatment systems, plasma cutters, switch cabinets, and UPS; wind turbines and solar panel inverters; and medical instrumentation. With their useful life of more than 3000 h at +105 °C, the capacitors provide more than 10 years of lifetime in ambient temperatures up to 60 °C for these applications.
Device Specification Table:
| Part number | 259 PHM-SI | |
| Case size (D x L in mm) | 22 x 25 to 35 x 60 | |
| Capacitance range | 39 µF to 2200 µF | |
| Tolerance | ± 20 % | |
| Ripple current at 100 Hz and +105 °C | 0.53 A to 4.42 A | |
| Rated voltage | 200 V to 450 V | 500 V to 600 V |
| Category temperature range | -40 °C to +105 °C | |
| Useful life at +105 °C | > 3000 h | |
| Max. ESR at 100 Hz | 80 mΩ to 3.31 Ω | |
| Max. impedance at 10 kHz | 60 mΩ to 2.44 Ω | |
| Sectional specification | IEC 60384-4 / EN 130300 | |
| Climatic category IEC 60068 | 40 / 105 / 56 | 25 / 105 / 56 |
The post Vishay Introduces 550 V and 600 V Snap-in Power Capacitors for High-Voltage Applications appeared first on ELE Times.
Infineon introduces HybridPACK HD power module for electric commercial vehicle drivetrain inverters
Gartner Reveals Top Software Engineering Trends as AI Transforms the Software Development Lifecycle
Gartner has identified the key technology trends expected to shape software engineering in 2026 and the coming years. The company’s analysts presented these trends at the Gartner IT Symposium/Xpo, being held in Kochi from November 16–18, 2026.
“The rapid advancement of AI is reshaping the software development life cycle (SDLC), forcing software engineering leaders to balance immediate productivity gains with longer-term investments in operating models, skills and governance,” said Manjunath Bhat, Distinguished VP Analyst at Gartner. “By understanding these trends and their impact, software engineering leaders can maximize AI’s value across the SDLC, enabling teams to deliver AI-powered applications faster, at greater scale and with sustainable business outcomes.”
Software engineering leaders should assess how these six trends could influence their AI strategies, development practices and work processes in 2026 and beyond. Gartner divides these trends into two main areas: using AI in the software development lifecycle (SDLC) and developing software systems for AI applications. For CIOs, AI-powered software development can help update older applications, speed up IT modernisation and reduce the cost of maintaining software.
Software engineering leaders should evaluate how these six trends will affect their AI strategies, engineering practices and operating models in 2026 and beyond. Gartner groups the trends into two themes: AI in the SDLC and SDLC for AI. For CIOs, AI SDLC capabilities are a key lever for reengineering legacy software applications, accelerating IT modernization and reducing application maintenance costs.

AI-native development platforms provide the foundation for AI-native software engineering and help reduce friction across the SDLC. These platforms range from vibe-coding tools that enable software creation without deep technical expertise to AI coding agents orchestrated by professional developers.
Gartner predicts by 2030, enterprise application portfolios will include 40% custom applications built using AI-native development platforms, up from 2% in 2025. To prepare for this shift, software engineering leaders should adopt an AI first approach and establish the platform capabilities and governance needed to enable secure, scalable AI-native development.
Harness EngineeringHarness engineering enables organizations to configure AI coding agents with the context, standards and guardrails needed to execute software engineering tasks reliably. By using agent harnesses to ground AI agents in organizational knowledge, governance and workflows, organizations can improve the quality, consistency and scalability of AI generated outputs.
Gartner predicts that by 2028, organizations with AI coding harness infrastructure will experience 60% fewer post deployment defects than those without. As performance differences between frontier AI models narrow, harness engineering will become a more important determinant of output quality than the choice of model itself.
Agent SandboxingAgent sandboxing uses trusted agent execution environments with strong isolation controls to reduce business and security risks associated with AI coding agents. Gartner predicts that by 2030, 70% of enterprises will sandbox agentic development workflows in preproduction environments, up from 10% in 2026.
“Organizations are increasingly looking to scale AI agents beyond experimentation and into production,” said Bhat. “Agent sandboxing provides a secure foundation for this shift, enabling teams to experiment while protecting systems from unintended agent-driven actions, untrusted code execution and privilege escalation.”
Local AILocal AI is a deployment strategy that enables organizations to run AI models and agents within their own infrastructure rather than relying primarily on vendor-hosted application programming interfaces (APIs). As AI moves from experimentation to production, organizations are adopting local AI to address data sovereignty concerns, manage rising inference costs and support latency-sensitive workloads.
Gartner predicts that by 2028, 60% of regulated enterprises will migrate AI workloads to local infrastructure after discovering that provider headquarters location, rather than data location, determines government access.
Eval-Driven DevelopmentEval-driven development uses task-specific evaluations to assess GenAI and agentic AI applications against predefined quality criteria, helping organizations quantify, measure and improve accuracy, safety, trust and explainability. Gartner predicts that by 2028, 70% of software engineering teams will adopt an eval-driven development approach to build responsible and trustworthy AI, up from less than 20% in 2026.
Forward-Deployed EngineersForward-deployed engineers (FDEs) work directly with business and technology teams to accelerate deployment of AI solutions in real-world customer environments. By combining software engineering expertise with domain knowledge and business context, FDEs help organizations move faster from AI concepts to production outcomes.
Gartner predicts that by 2028, more than 70% of AI technology and service providers will leverage FDEs to accelerate AI solution adoption, up from 10% today.
The post Gartner Reveals Top Software Engineering Trends as AI Transforms the Software Development Lifecycle appeared first on ELE Times.
Microchip Launches LAN9324x and LAN9322x Automotive Ethernet Switch Families for Next-Generation Vehicles
As automakers move towards centralised computing and zonal network architectures, vehicle communication systems need to handle more than just data transfer. They must respond quickly to changing requirements while ensuring reliable performance, safety and cybersecurity. To support this shift, Microchip Technology has announced the sampling of its new LAN9324x and LAN9322x automotive-qualified Ethernet Time-Sensitive Networking (TSN) switch families. These switches are designed to support next-generation in-vehicle communication networks.
Scalable, Dynamic and Self-Managed Networking for Software-Defined VehiclesBoth Ethernet switch families share similar features, hardware architecture and standards-based software, but serve different vehicle networking needs. The LAN9322x family is designed for compact zonal and edge applications, while the LAN9324x family supports higher port counts and greater bandwidth for advanced zonal networks, central computing systems and gateways.
The switches also offer different connectivity options, including integrated 10BASE-T1S, 100BASE-T1 and 1000BASE-T1 physical layer (PHY) interfaces, along with SerDes connections supporting speeds from 10 Mbps to 10 Gbps. This allows automotive designers to choose the required number of ports, data speeds and package size based on their vehicle network requirements.
Fully self-managed and ready to configure, the LAN932xx families can eliminate the need for customers to develop and maintain proprietary, device-specific switch software. The VelocityDRIVE Software Platform provides standards-based management using IETF/IEEE YANG data models and CORECONF for local or remote configuration, monitoring and dynamic updates, enabling software and engineering reuse across compatible switches.
Beyond static configuration, the LAN932xx families support dynamic runtime reconfiguration, enabling vehicle networks to respond in real time to evolving functional safety, cybersecurity and resource requirements. This capability also accelerates development and validation, providing a future-ready foundation even for static production networks.
“Software-defined vehicles require networks that are programmable, scalable and ready to adapt,” said Charles Forni, corporate vice president of Microchip’s networking and connectivity business unit. “With our LAN9324x and LAN9322x switches and the VelocityDRIVE Software Platform, customers can adopt a standards-based, easily configurable approach that reduces software development and maintenance effort, cost and risk.”
Advanced, Secure and Resilient by DesignThe LAN932xx families combine high-performance TSN switching, advanced security and precision time synchronization, scaling to 18 external ports and up to 30 Gbps switching capacity. With integrated automotive Ethernet PHYs, MACsec on every port and ISO 26262 ASIL B compliant, the devices are designed to deliver the performance, safety and security required for next-generation vehicle networks.
A fully integrated dual-core Arm Cortex-R52+ processor with lockstep operation and on-chip SRAM is complemented by a dedicated Arm Cortex-M33 embedded Hardware Security Module (eHSM) with hardware isolation. An extensive Deep Packet Inspection (DPI) engine provides advanced packet filtering, intrusion detection and protection. The switches are AEC-Q100 Grade 2 qualified, with an ambient operating temperature range of −40°C to +105°C and a maximum junction temperature of 150°C.
The supply chain for the automotive industry is increasingly complex. The LAN932xx families support resilient automotive sourcing, with multiple geographically diverse wafer fabrication locations and back-end assembly and test options.
Microchip offers a broad portfolio of automotive Ethernet solutions, including PHYs, switches, bridges, endpoints and software designed to support Ethernet-based in-vehicle networks for zonal, gateway, central compute and telematics applications. VelocityDRIVE solutions combine hardware and software designed to simplify the development of next generation in-vehicle networks.
The post Microchip Launches LAN9324x and LAN9322x Automotive Ethernet Switch Families for Next-Generation Vehicles appeared first on ELE Times.
WSO2 Changes Name to Choreo Labs as Enterprises Expand AI Agent Deployment
WSO2, an open-source technology company whose software handles an estimated 60 trillion transactions annually and manages 2.5 billion identities, has announced that it is changing its name to Choreo Labs.
As businesses move AI agents from testing to real-world operations, they need ways to monitor and control how these agents access APIs, systems and user identities. Choreo Labs aims to address this growing need by helping enterprises manage and govern AI agents. The company says the new name reflects its expanded role, moving beyond connecting enterprise systems to supporting businesses in managing and controlling AI-driven operations.
Founded in 2005, WSO2 got its name during the early days of web services technology. Today, its API management, system integration and identity management products are used by more than 950 customers across over 90 countries. Its customers include banks, government organisations, hospitals and telecommunications companies. Leading technology research firms have also recognised the company for its products and ability to meet enterprise requirements. Over the past two decades, enterprise technology has evolved from web services to cloud computing and APIs, and now to AI agents that can perform tasks independently. WSO2 has continued to adapt its products and services to keep pace with these changes.
Through each of those shifts, the company’s mission has stayed the same: connecting systems and controlling what moves between them. AI agents raise the stakes.
“For over 2 decades, our mission has been to make sure enterprise systems talk to each other safely at scale,” said Harry Ault, CEO of Choreo Labs. “AI agents don’t change that mission. In fact, they make it far more urgent. Enterprises won’t put agents into production until they can see, govern, and trust every action those agents take. That is the problem we were built to solve, and our new name says so.”
“WSO2 was the right name for the company we started in 2005,” Ault added. “We’ve grown a lot since then, and so have the problems our customers bring us. Choreo Labs reflects the company we are today, and the principles we’ve always built on.”
“Choreo” comes from choreography. Inside every enterprise, agents, APIs, integrations, identities, and services each have their own part to play, and none of them ever stops moving. Choreo Labs gives organizations both the freedom for each part to move and the control to keep them in step. Choreo, the company’s platform, brings APIs, integration, identity, agents, and the internal developer platform that runs them together in one place.
“Labs” reflects the company’s research and engineering culture. It has long innovated in open source and open standards, from its integration programming language to its latest agent management product. Technical staff make up more than 75% of its 850-plus employees, and the same engineers who design the platform work alongside customers to deploy it.
Driving Governance and Control in the Agentic AgeCloudflare said in August that non-human, agentic traffic overtook human traffic on the internet in May 2026, a year ahead of its own forecast. Every agent that calls an API, reads a customer record, or triggers a workflow needs an identity, a policy, and an audit trail. Enterprises can’t govern an agent without governing what it touches: the APIs it calls, the systems it connects to, and the identity it acts under. It is this command and control layer that is where AI governance lives.
The company already ships this control layer and now offers it under one single platform: Choreo. Choreo Agent Manager (formerly WSO2 Agent Manager), released as open source under the Apache 2.0 license, gives every agent a verifiable identity, enforces more than 40 built-in guardrails mapped to the OWASP Top 10, and can suspend any agent with one click, across frameworks such as LangChain, CrewAI, AWS Strands, and Microsoft Agent Framework. Choreo AI Gateway (formerly WSO2 AI Gateway) applies the same controls to model and MCP traffic, and Choreo Agent ID (formerly WSO2 Agent ID) treats every agent as an identity in its own right, with scoped access, instant revocation, and its own comprehensive audit trail.
The company’s global systems integrator partners are similarly addressing the new demands of AI with their clients.
“Our telecom, banking, and public sector clients run some of the most complex systems in the world, and AI agents now need access to all of them. Before an agent goes live, those clients want to know who it is, what it’s allowed to touch, and what it did. Choreo Labs gives our engineers an open, standards-based way to answer all three, across every system those agents reach,” said Chockalingam Subramanian, global business unit head for integration services at Tech Mahindra.
“Our clients are now asking how to run AI agents safely across systems they’ve spent decades building, and Choreo Labs’ focus on governance gives our teams a strong foundation for taking those agents into production,” said Vinay Hegde, global practice head for agentic integration and orchestration at LTM.
Looking AheadExisting customers don’t need to take any action. Products, contracts, support, and open source licenses continue as they are, and other product names will move to the new brand over the coming months.
The company will make its first appearance under its new name at AWS re:Invent in Las Vegas, November 30 to December 4, 2026, where it will showcase its unified platform. Ault will also deliver a keynote at apidays Paris, December 1 to 3, 2026.
The post WSO2 Changes Name to Choreo Labs as Enterprises Expand AI Agent Deployment appeared first on ELE Times.
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.
The ePlane Company Adopts LYNX MOSA.ic for Mixed-Criticality Software in e200X eVTOL
A single computing platform will run Vehicle Management and Enhanced Situational Awareness software on shared hardware, supporting air ambulance, cargo and passenger operations.
Lynx announced at eVTOL Show USA on November 18, 2026, that The ePlane Company has selected its LYNX MOSA.ic software platform to handle mission-critical computing tasks on its e200X electric vertical take-off and landing (eVTOL) aircraft. The platform is designed to run multiple software applications with different safety and security requirements on the same computing system.
The e200X is a three-seat eVTOL aircraft designed to carry one pilot and two passengers. Its modular design allows it to serve different purposes, including air ambulance services, urban cargo delivery and passenger transport. Each version uses different payloads, sensors and software, while maintaining reliable and safety-compliant flight control.
LYNX MOSA.ic partitions the e200X’s onboard compute so flight-critical software, such as the vehicle and energy management systems, runs in ARINC 653 partitions, isolated from lower-criticality mission functions that handle sensor data processing and situational awareness inference. Heavy AI processing runs on a separate platform, and the mission system supplies the controlled interfaces between that platform and the rest of the aircraft, ensuring clear cybersecurity and safety isolation.
“A multi-role aircraft asks more of its computers than a single-mission design, because the mission software keeps changing while flight control cannot,” said Tim Reed, Chief Executive Officer of Lynx. “LYNX MOSA.ic lets ePlane keep flight-critical software isolated and certifiable while its pilot assist software evolves with each role.”
LYNX MOSA.ic is a mixed-criticality operating environment built around a separation kernel-based type 1 hypervisor. It gives each software subject its own space and time partition, so applications at different levels of criticality can share one platform, and it is certifiable to DO-178C DAL A.
“Urban air mobility is as much a computational challenge as it is an aerodynamic one. Operating high-density routes safely across emergency response, logistics, and passenger transit requires mission computing that is both certifiably safe and functionally modular. LYNX MOSA.ic gives us the deterministic partitioning required to isolate safety-critical systems while our engineers build cutting-edge aircraft functionalities on familiar tools. It is a foundational technology for delivering scalable, multi-role electric aviation.” Prof. Satya Chakravarthy, Founder and Technical Lead, The ePlane Company.
Lynx will take the stage at eVTOL Show USA on Tuesday, November 17, at 11:35 a.m. in the Gateway Ballroom at the Santa Clara Convention Centre to present “Building the Certifiable Software Behind Electric Flight.” Attendees are also invited to connect with the Lynx team at Booth #33.
The post The ePlane Company Adopts LYNX MOSA.ic for Mixed-Criticality Software in e200X eVTOL appeared first on ELE Times.
DNS blocking on ESP32-C3: ad-free browsing without PSRAM
An open source Pi-hole-style DNS blocker runs on a 2-dollar ESP32-C3 Super Mini module and filters ads and trackers for every device on a home or small office network. The firmware answers 0.0.0.0 to queries for domains on the blocklist and forwards the rest to an external DNS server. What sets it apart from the usual network adblockers is the method: the domain strings are not kept in RAM, but in flash as sorted 40-bit FNV-1a hashes. That way more than 140,000 domains take up about 0.7 MB of flash and only about 50 KB of RAM, with no need for PSRAM. The project is by Zed (M-Abozaid) and the code lives in a public repository.
The heart of the system is the ESP32-C3FH4 module: single-core 32-bit RISC-V CPU up to 160 MHz, 400 KB SRAM, 4 MB of flash, 2.4 GHz WiFi 4 and a USB Type-C port for programming. Power comes in at 5V over USB and needs a stable source to avoid radio brownouts. In the minimal version, all you need is a compact ESP32-C3 module with USB Type-C plugged directly into a router’s USB port, as shown in the photo below.
DNS blocker on an ESP32-C3 SuperMini connected directly to a router’s USB port
When a UDP DNS query arrives, the C++ firmware extracts the domain, computes its hash including the parent suffixes and does a binary search in the hash table in flash. If the domain is on the blocklist it answers 0.0.0.0; otherwise it forwards the query upstream and returns the response to the client. A DNS lookup takes about 10 ms, including roughly 18 flash reads and the Wi-Fi round-trip. The blocklist check alone costs 50 microseconds.
The capacity figures depend on the partition chosen. With 40-bit hashes you get about 141,000 domains with almost no collisions, about 250,000 domains with dual-app partitions for firmware OTA, or up to about 537,000 domains with a single-app partition and about 1 collision. On a 4 MB ESP32-C3 board, OTA firmware updates require two application slots, leaving about 1.3 MB of flash for the blocklist. With 32-bit hashes you save flash space, but you would get about seven collisions at 250,000 domains.
- ESP32-C3 Super Mini with 4 MB of flash: over 140,000 domains in about 0.7 MB, 50 KB of RAM, 50 microseconds per check
- ESP32-S3 with 8 MB PSRAM: holds the current blocklist, checks in 50 microseconds, about twice as fast as the ESP32
- ESP32 with 4 MB PSRAM: truncates the current blocklist, checks in 100 microseconds
- ESP32-S3 with 16 MB: about 2.7 million domains with 40-bit hashes, versus about 466,000 domains as strings in 8 MB of PSRAM
The web dashboard is reachable at c3adblock.local and shows blocked and allowed DNS requests per client, lets you block specific devices and add custom domains to the blocklist. Initial Wi-Fi configuration happens through a captive portal, so there is no need to put the credentials in the code. Firmware and blocklist OTA updates are also supported, with scheduled automatic updates that download precompiled blocklist files from a specified URL.
The software is built with an Arduino sketch (ESP32_AdBlocker), esp32 arduino core minimum v3.1.1 and PlatformIO. For automatic blocklist updates the firmware uses a WebDAV client with HTTP Basic Auth. Anyone who wants to rebuild the project will find the code to compile and the files to upload in Zed’s (M-Abozaid) repository.
The minimal build needs no soldering: you plug the module into the router’s USB port, configure the captive portal and point the router’s DHCP to the board’s address. For a wired variant, the project also provides for a W5500 Ethernet controller and a WS2812 RGB LED for status: the catalogue includes the mini Ethernet board with W5500 chip and the WS2812B addressable RGB LED.
Source: https://github.com/s60sc/ESP32_AdBlocker
Related products- Mini ESP32-C3 module
- Mini Ethernet Board with W5500 chip
- Addressable SMD5050 RGB LED with WS2812B chip – NEOPIXEL
The post DNS blocking on ESP32-C3: ad-free browsing without PSRAM appeared first on Open Electronics.
Arrow Electronics to Showcase Intelligent Edge AI Solutions at EdgeTech+ 2026
Arrow Electronics is showcasing its technologies and engineering expertise for intelligent edge AI systems at EdgeTech+ 2026, being held from November 18–20 at Pacifico Yokohama in Yokohama, Japan. The company is exhibiting at Booth CC-21 alongside technology partners NXP, YAGEO Group, Longsys, Bourns, Same Sky and Toshiba.
As AI processing moves closer to the devices and machines that generate data, its use is growing in connected products and industrial systems. This is creating a greater need to combine computing, connectivity, memory and power technologies while ensuring that systems deliver good performance, use energy efficiently and operate reliably.
“Bringing intelligent edge AI systems to market requires more than choosing the right technologies,” said Dr. Raphael Salmi, president of Arrow Electronics’ semiconductor business for South Asia, Korea and Japan. “Arrow brings together technology, engineering and supply chain expertise to help customers address integration challenges and turn ideas into scalable, market-ready solutions.”
Arrow’s showcase will bring together capabilities and offerings across its technology ecosystem, including digital sourcing and BOM management through Arrow.com and Verical; product engineering from eInfochips; component data, analytics and lifecycle management from SiliconExpert; RF, wireless, IoT and power technologies from Richardson RFPD; and supply chain solutions from Converge. Participating suppliers will showcase technologies spanning edge AI processing, memory and storage, power management, sensing, circuit protection, connectivity and thermal management.
On Nov. 19 from 14:05 in room A, Uday Mohandas, vice president and APAC head of eInfochips, an Arrow company, will deliver the keynote “From Silicon to Intelligent Products: Engineering the Next Generation of AI Systems.” The session will explore how edge AI, physical AI, embedded software and hardware-software integration can help turn advanced silicon and AI technologies into intelligent, production-ready products.
The post Arrow Electronics to Showcase Intelligent Edge AI Solutions at EdgeTech+ 2026 appeared first on ELE Times.
RECOM Introduces 300W DC/DC Converters with Wide Input Voltage Ranges and 92.5% Efficiency
RECOM’s new RP300H-(R)W series features isolated 300W DC/DC converters designed for railway, industrial and automation applications. These converters come in a compact half-brick package and support three wide input voltage ranges: 9–36VDC, 18–75VDC and 40–160VDC. They deliver efficiency of up to 92.5% and are available in seven output voltage options ranging from 5VDC to 54VDC. This flexibility allows them to be used in different DC power supply systems.
The 24VDC and 48VDC models offer basic isolation, while the 110VDC models provide reinforced isolation for additional protection. All versions support 3kVDC input-to-output isolation. Measuring 61.0 × 57.9 × 12.7mm without a heat sink, the converters are compact enough to fit into equipment with limited installation space. They can operate at temperatures ranging from -40°C to +105°C, depending on the required power derating. Models with a pre-installed heat sink are also available.
The post RECOM Introduces 300W DC/DC Converters with Wide Input Voltage Ranges and 92.5% Efficiency appeared first on ELE Times.



