Українською
  In English
Feed aggregator
Cyient DLM and Hindustan Shipyard Sign MoU to Advance Indigenous Maritime and Defence Electronics
Partnership to Focus on Indigenous Electronics, Advanced Manufacturing and Lifecycle Support for Maritime and Defence Applications
Cyient DLM and Hindustan Shipyard Limited (HSL) have signed a Memorandum of Understanding (MoU) to explore collaboration in advanced electronics manufacturing and technology solutions for the maritime and defence sectors. The partnership aims to identify opportunities to develop indigenous electronics, strengthen manufacturing capabilities and provide technology support for maritime and defence applications.
The partnership combines HSL’s expertise in shipbuilding, ship repair and system integration with Cyient DLM’s capabilities in mission-critical electronics, embedded systems, power electronics, precision manufacturing, testing and product lifecycle support. Through this collaboration, both companies will explore opportunities to develop more indigenous technologies and strengthen India’s domestic manufacturing capabilities, supporting the Government of India’s Atmanirbhar Bharat initiative.
Under the framework, the two organizations will evaluate potential areas of cooperation across electronics, embedded systems, power electronics, testing, manufacturing and lifecycle support for maritime and defence applications. The companies will also explore opportunities in areas such as indigenization, obsolescence management, test and support systems, autonomous and unmanned maritime platforms, power electronics and AI-enabled maintenance solutions.
Speaking about the partnership, Rajendra Velagapudi, Managing Director & Chief Executive Officer, Cyient DLM, said, “India’s maritime and defence ecosystem presents a significant opportunity to build stronger indigenous technology and manufacturing capabilities. Our engagement with Hindustan Shipyard Limited brings together complementary strengths in shipbuilding and platform integration with Cyient DLM’s expertise in mission-critical electronics and manufacturing. We look forward to exploring opportunities where our combined capabilities can support indigenization, technology development and long-term lifecycle requirements for maritime and defence platforms.”
“This MoU provides a framework for Hindustan Shipyard Limited and Cyient DLM to explore areas where our respective capabilities can complement each other. As India strengthens its indigenous maritime and defence ecosystem, collaboration across shipbuilding, electronics, technology and lifecycle support can play an important role. We look forward to evaluating opportunities that can contribute to greater self-reliance and technology development,” said, R Adm C Raghuram, VSM (Retd,), Chairman and Managing Director, Hindustan Shipyard Limited.
The post Cyient DLM and Hindustan Shipyard Sign MoU to Advance Indigenous Maritime and Defence Electronics appeared first on ELE Times.
Molex High-Radix OCS: 544×544 optical switching for hyperscale AI
The move to fully optical data centre networks is already under way, but AI training clusters are growing faster than the switches that connect them. The next generation of Optical Circuit Switch (OCS) platforms has to go well beyond today’s port counts, while keeping strict limits on insertion loss and guaranteeing system-level reliability.
By replacing the traditional electronic packet process with direct, physical paths of light, optical circuit switching radically changes how data moves through the network. This shift to an all-optical core has already proven its value at hyperscale, with deployments delivering 40% energy savings and 50 times less downtime compared with traditional electronic switching (The rise of optical switching).
However, while OCS removes the bottleneck of electrical switching, it concentrates new complexity directly in the physical layer.
The AI scaling curve has quickly outgrown the first generation of OCS products. As training clusters expand to support pods with tens of thousands of GPUs, the physical layer must handle routing and density demands with no precedent in optical routing. Operators are publicly calling for switch matrices that go far beyond the 300-port limit of most current vendor capabilities.
The four attributes that define hyperscale optical circuit switching performanceThe question for data centre architects is a very practical one: can OCS platforms scale their port count and manufacturing maturity quickly enough to match the pace of AI infrastructure build-out? Solving this means treating the switch and the surrounding physical layer as a single, holistic platform.
As AI training clusters expand towards hundreds of thousands of accelerators, the optical circuit switches at the centre of the network need a proportionally larger switching matrix. Port count determines the network architecture, but four attributes determine whether a high-radix switch can actually work at hyperscale.
The radix problemThe latest AI superpods require almost 14,000 optical ports each, driving demand for individual switches with more than 300 ports. To minimise network tiers across tens of thousands of GPU pods, hyperscale data centre operators are actively asking for switch matrices with thousands of ports. Scaling to this level introduces a secondary physical challenge: balancing ultra-dense optical cabling with practical field maintenance and mean time to repair (MTTR).
Insertion lossEvery decibel of loss counts when the optics double up in an OCS architecture. Standard far-reach (FR) optics have link budgets limited to roughly 4 dB to 6 dB depending on the module. Any internal switch loss eats directly into those tight margins, reducing reach and the usable optical margin. Keeping to these strict budgets at scale relies on embedded testing and telemetry to continuously monitor performance and validate the optical paths.
Reliability at scaleThe whole-system impact, or blast radius, of a failure in one optical switch can stall an entire AI training job. At this scale, even 99.999% component reliability can translate into unacceptable system-level downtime. High component ratings only count if they translate directly into an acceptable mean time between failures (MTBF) and overall availability. Fast recovery from failures also plays a key role, since switching latency determines whether dynamic workloads can continue without interrupting active AI jobs.
Manufacturing readinessA lab prototype and a production-grade platform are two very different things. Hyperscale operators require vendors able to deliver thousands of units on schedule, through proven, high-volume manufacturing processes. Moving from initial designs to high-volume production depends on consistent assembly techniques and rigorous test protocols to maintain production levels.
The Molex High-Radix Optical Circuit Switch platformMolex has developed the High-Radix Optical Circuit Switch (OCS) platform to solve the scalability limits of a major global hyperscaler. The design builds on almost twenty years of micro-electromechanical systems (MEMS) technology deployments and on more than two million devices shipped into optical networking applications.
Inside a modern data centre: the environment where Molex’s High-Radix Optical Circuit Switch platform is used for next-generation optical networks.
At 544×544, the Molex solution is the highest-radix MEMS-based OCS announced to date. The higher radix lets architects build flatter superpod architectures with fewer switches and fewer hops. Reaching this density relies on a patented optical design that uses the full MEMS tilt range. This approach reduces the required MEMS deflection angle by 50%, allowing the system to scale massively using a proven, highly stable structural design.
Optical and switching performanceThis high-radix switch maintains stable, low insertion loss across all paths, with a typical insertion loss of 3 dB. Keeping loss predictable preserves tight optical link budgets across the whole network. The 544×544 switch also supports predictable switching behaviour for dynamic reconfiguration and failure recovery, operating with a maximum switching time of under 150 ms, with development under way aiming at 100 ms. This sub-second performance lets operators quickly reroute traffic and bypass hardware failures to keep the cluster running continuously.
Designed for production deploymentBecause the MEMS operates in the optical domain with no active media in the light path, the Molex High-Radix OCS platform stays agnostic to protocols and data rates, supporting from 800Gbps to 1.6Tbps and beyond without hardware changes. Operating entirely in the photonic domain keeps power consumption surprisingly low, drawing 245 watts to handle more than 500 ports. Molex supports the 544×544 switch with global optical manufacturing and advanced assembly capabilities. The assembly process relies on a mechanical build combined with software-guided calibration to establish and align all the optical connections.
A complete optical ecosystem for AIA high-radix optical circuit switch solves the core routing challenge, but it is only one node in a vast physical network. Building a fully optical network at hyperscale requires a complete physical interconnection infrastructure.
Terminating more than a thousand fibres on a single front switch, using up to 600 pairs of LC-APC or LC-UPC adapters to keep insertion loss low, creates enormous physical density and routing demands. The ecosystem extends well beyond the chassis itself. Maintaining strict link budgets across the whole data centre floor rests on high-performance optical cable assemblies, advanced fibre management and rigorous end-to-end testing.
Building a fully optical data centre requires manufacturing depth in both the core switch and the surrounding physical layer infrastructure. By owning the entire interconnect path, Molex gives architects the complete physical ecosystem needed to build and scale fully optical data centre networks.
Discover how the Molex High-Radix OCS Platform delivers the scaling, reliability and performance required by next-generation AI data centres.
Oliver Lu, company executive, whose photo accompanies this article on Molex’s High-Radix Optical Circuit Switch platform for next-generation AI data centres.
The post Molex High-Radix OCS: 544×544 optical switching for hyperscale AI appeared first on Open Electronics.
A 1980s-style Bluetooth handset to fight smartphone addiction
Kevin Noki has built a 1980s-style handset that works as a Bluetooth audio peripheral. The goal is to reduce smartphone dependence, not replace the phone. In fact, the project contains no cellular modem at all: real telephony stays with a professional, regulatorily approved device. Bringing custom hardware to VoLTE is impractical in many countries anyway. So the 1980s Bluetooth handset becomes a functional retro object that sidesteps the regulatory constraints of cellular telephony.
The maker starts from an ESP32, which he already had on hand and which integrates Bluetooth. The audio quality he got, however, turned out too ‘crunchy’. So he moved to a dedicated Bluetooth module with the Hands Free Profile (HFP), designed specifically for this kind of application. HFP is the profile that hands-free systems use to handle calls and audio together, so it is the natural choice when you want a handset that behaves like a real handset.
The XPS foam case and the display with bent acrylicThe 1980s ‘brick’-style case is prototyped with XPS foam and a hand-operated hot wire cutter. No CAD, then, at least in the initial phase: the maker follows a traditional industrial design approach, the one that starts from the physical volume and refines it by hand. For the display he instead uses an acrylic bending jig, with which he applies a black LED acrylic over the screen. This way the front glass takes on the right curvature and the black hides the parts that must not emit light.
- ESP32 as the starting point, with integrated Bluetooth
- Dedicated Bluetooth module with Hands Free Profile (HFP) for audio
- XPS foam case cut with a hand-operated hot wire
- Acrylic bending jig for the display, with black LED acrylic
Anyone who wants to rebuild the project will find several useful pointers. The first is that the Bluetooth module with HFP is the critical part: it is what determines whether the voice comes out clean or ‘crunchy’. The second is that the case does not require expensive equipment, because XPS foam and a hot wire are enough to get to a solid prototype. The third is that a display with heat-bent acrylic can be made with a simple jig, as long as you do a few tests before gluing everything together.
Where to find the details to rebuild the handsetThe project is sold on the maker’s site, but the video shows so many details that you can recreate your own version. So even those who do not buy the finished object can study the construction choices and adapt them. Kevin Noki’s project page on Hackaday.io collects the story of the work, and it is the place to start to understand how the trickiest steps were solved. In particular, there you can see how the maker tackled the audio problem and how he modelled the case.
For anyone who would like to approach a similar project, a convenient starting point is a development board with integrated Wi-Fi and Bluetooth, such as this ESP32 board with Wi-Fi and Bluetooth, the same family the maker starts from. The choice of audio module, however, remains the real crux: without a component with the HFP profile the handset does not behave like a hands-free unit. In short, the electronics side is within reach of a maker, while the mechanical side requires patience and a few tests with foam and acrylic.
Source: https://hackaday.io/contests
Related productsThe post A 1980s-style Bluetooth handset to fight smartphone addiction appeared first on Open Electronics.
Muse Gadgets: an open source SDK for gadgets that connect to the Muse AI agent
Muse Gadgets is an open source SDK for building devices that can connect to Meta’s Muse AI agent. The starting point is a commercial ESP32 board, or a Raspberry Pi or a Linux box. The resulting gadget displays images, handles audio input and output, and interfaces with displays, buttons, sensors and actuators. Anyone who wants to rebuild the project will find everything in the code repository published on GitHub, with both SDKs and the firmware.
Meta also pushed the project on the hardware side. It produced 5000 Muse Home Link devices and gave them away free to Muse subscribers in the United States, in the following weeks, until stocks ran out. The Muse Home Link is based on an ESP32-C5 wireless microcontroller, with dual-band WiFi 6, BLE and 802.15.4 for Zigbee and Thread. On board there are 8 MB of flash and 8 MB of PSRAM.
The Muse Home Link device
The development path splits into two tracks. The ESP32 Device SDK is loaded onto a commercial board and adds image display, audio input and output, and the connection of sensors, actuators and buttons. The Linux Device SDK, on the other hand, turns a Raspberry Pi or a Linux box into a Muse gadget, with custom commands for sysadmin tasks or for Home Assistant.
- ESP32 Device SDK: images, audio input and output, sensors, actuators and buttons on commercial boards.
- Linux Device SDK: Raspberry Pi or Linux box as a Muse gadget, with custom commands for sysadmin and Home Assistant.
- Third directory of the repository: skills for hardware of various kinds, such as Apple HomePod Mini, Brother and Epson printers, ESPHome devices, 3D printers and various TVs.
The Waveshare ESP32-S3-Touch-AMOLED-1.75C devkit is one of the boards mentioned as a starting point: it mounts a 1.75-inch AMOLED touchscreen, speaker, microphone and battery. For those who prefer the Linux route, the catalogue offers a Raspberry Pi 5 starter kit with power supply and microSD, ready to be set up with the Linux Device SDK. On the ESP32 side, the catalogue also has a round HMI display with touch knob and LVGL graphics, based on ESP32-S3, useful for anyone who wants a physical interface to connect to the gadget.
SDK token and pairing with the Muse appBefore flashing or pairing a gadget, two mandatory steps are required: getting an SDK token and accepting the Gadget SDK Terms. Only then do you move on to pairing with the Muse app on iOS and Android. The procedure is carried out from Settings, Devices, after enabling developer mode. The app looks for devices with the MuseGadget prefix and connects them to the agent.
There is quite a lot of software involved. On the ESP32 side you work with ESP-IDF and with LVGL for the graphical interface; on the Linux side SDL comes into play. Integration with Home Assistant and with ESPHome devices is provided by the skills included in the third directory of the repository, together with Muse Code. Anyone who wants to understand how the project is built will find the SDKs, the firmware and the ready-to-use skills in the code repository on GitHub.
The picture is clear: Muse Gadgets is not a single device, but a set of tools for building your own. You start from an ESP32 board or a Raspberry Pi, choose the right SDK, get a token and pair everything with the Muse app. Sensors, actuators and the skills you decide to load do the rest.
Source: https://github.com/facebookincubator/muse-gadget-sdk
Related products- Raspberry Pi 5 Starter Kit with 27 W Power Supply and 64 GB microSD
- ESP32-S3 Round HMI Display with Touch Knob and LVGL Graphics
The post Muse Gadgets: an open source SDK for gadgets that connect to the Muse AI agent appeared first on Open Electronics.
Партнерство із чеською компанією Prusa Research
Посилення української експертизи в адитивних технологіях і розроблення інноваційних рішень для медицини та протезування — таку мету має нове міжнародне партнерство КПІ ім. Ігоря Сікорського та Наукового парку адитивних технологій Sikorsky Challenge (AMSP) із чеською компанією Prusa Research — відомим світовим розробником і виробником 3D-принтерів.
День спільнодії «Софійність. Сила жити й діяти»
Де знаходити сили жити, діяти й підтримувати одне одного? У КПІ шукали відповіді на ці питання під час Дня спільнодії «Софійність. Сила жити й діяти».
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.
Trick Shot II Runs on a Nokia 3310 With a Custom Board
Hoani has recreated the Nokia 3310 gaming experience on a custom board, fitted inside the shell of a real phone that has been emptied out. The board runs Trick Shot II, a ball-bouncing game, through a graphics engine written in Go. The idea came from a game jam where the goal was to write a game while respecting the constraints of the Nokia 3310 user interface. Those constraints are a 94 x 48 pixel greyscale LCD, a buzzer and a numeric keypad.
The result is not a software emulation: it is a custom board that fits into the original shell. On top of it sit a Pi Pico, the Nokia 3310 LCD and a key layout that mirrors the phone’s. So the game runs on real hardware, with the real screen and the real keys.
The Go game engine and the graphics and sound APIsThe software heart of the project is a game engine written in Go. The engine provides APIs for both graphics and sound, so the game does not talk directly to the screen or the buzzer. This keeps the Trick Shot II code separate from the hardware side. What’s more, anyone who wants to write another game can reuse the same engine and the same APIs.
The interface constraints are rigid and this shows in the code. The Nokia 3310 LCD has a resolution of 94 x 48 pixels, so every sprite and every screen has to be drawn within that space. The buzzer adds sound, the numeric keypad provides the controls. Trick Shot II uses exactly these few elements for the ball bouncing.
The build: Pi Pico, LCD and keypad in the emptied shellThe custom board holds the Pi Pico, the Nokia 3310 LCD and the keys. The shell of a real Nokia 3310 is emptied out to house all of it, so the board has to follow the internal shapes of the phone. The first prototype did not fit perfectly because the board was 1.6 mm thick instead of 1 mm. A detail that seems minor, but decisive when the space is that of a twenty-year-old shell.
- Pi Pico as the brain of the board
- Nokia 3310 LCD at 94 x 48 pixels
- keypad with the Nokia key layout
- 1 mm board to fit the original shell
- Go game engine with graphics and sound APIs
- Trick Shot II as a ball-bouncing game
Anyone who wants to start from a ready base for the firmware can use a Raspberry Pi Pico, the board that acts as the brain in the project: it is worth testing the game engine on the Pico before soldering the final board.
The project came out of a game jam, so the starting point was the constraint, not the hardware. The challenge was to write a game that fit inside a 94 x 48 pixel greyscale LCD, with a buzzer and a numeric keypad. From there came the decision to rebuild the phone entirely, shell included. If you want to see how Hoani’s work is put together, the project page on Hackaday.io collects the story of the project and its evolution.
Rebuilding this project means working on three fronts at once. The first is the board, which has to stay under one millimetre thick. The second is the firmware on the Pi Pico, with the Go engine and its APIs. The third is the shell, to be recovered and emptied without breaking the fittings. Finally there is the game, Trick Shot II, to run on all of this.
Source: https://hackaday.io/contests
Related productsThe post Trick Shot II Runs on a Nokia 3310 With a Custom Board appeared first on Open Electronics.
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.
Майбутні управлінці виростають із реальних завдань
На початку жовтня я отримала лист від свого колишнього студента групи АМ-11 Олега Горохов'янка (випуск бакалавртау 2025 р.), який нині навчається за кордоном. Він дякував за науку й поділився цікавим спостереженням: українська вища освіта цілком витримує порівняння із закордонною. А от відчутну різницю він помітив у мотивації студентів та усвідомленні тих можливостей, що їх дає університет. Цей лист змусив мене замислитися над тим, як саме ми готуємо управлінців для публічного сектору, і нагадав одну особливу студентську історію.
🏓 Турнір з настільного тенісу для співробітників!
Профком КПІ імені Ігоря Сікорського запрошує працівників університету взяти участь у турнірі з настільного тенісу!
📅 24 листопада 2026 року
📍 Спортивно-оздоровчий комплекс КПІ, корпус № 24, ігровий зал #1
🕞 Реєстрація учасників — о 15:30
🏓 Початок змагань — о 16:00
KPI Career beAhead Expo 2026. Autumn: познайомся з топовими роботодавцями на ринку
Із 24 до 27 листопада 2026 року в КПІ ім. Ігоря Сікорського відбудеться осінній KPI Career beAhead Expo 2026 — масштабна кар’єрна подія, що об'єднує студентів університету та представників провідних компаній-партнерів. Цьогоріч захід пройде у змішаному форматі та поєднає три дні онлайн-лекцій із можливістю особисто поспілкуватися з потенційними роботодавцями під час Career Speed Recruiting.
A 3D-printed case for the TFT module with EC11 encoder and ESP32-C3
A knob that turns, a button that clicks and a display that responds. The project brings all of this together in a 3D-printed case that houses a 1.8-inch module with a TFT display, an EC11 rotary encoder and a pushbutton, plus an ESP32-C3 module. The example code shows the encoder count and the pressed state of the encoder and the button on screen. So anyone looking for a physical interface for an ESP32 board finds a ready-assembled starting point here.
The 1.8-inch module is not a bare display: it integrates the ST7735S driver, the EC11 encoder and a pushbutton on the same PCB. Instead of wiring three separate components, you connect a single module. The display works at 160 pixels wide by 128 high, values that the code sets directly in its configuration.
1.8-inch TFT module with ST7735S driver and EC11 encoder
The case consists of three printed parts: front, back and a mount for the ESP32-C3. The TFT module with encoder and button is screwed to the front panel with four 4mm M3 screws. The mount holds the board in the right position, so the connections are not under strain. As a result, assembly needs no glue and no improvised brackets.
For the electronics you need a compact development board with integrated Wi-Fi and Bluetooth radio, from the same family as the module used here. Assembly stays simple: four holes, four screws and the module is fixed in place.
Screw the PCB to the front panel with the mount for the ESP32-C3
The code is uploaded from the Arduino IDE with the ESP32 board package installed. To enter boot mode, hold the BOOT and RESET buttons down together, then compile and upload the sketch. The serial port runs at 115200 baud. The firmware uses interrupts on the ENC_A pin for movement and on the ENC_S pin for the encoder press, while the SWITCH button is read with a 10-millisecond software debounce.
The screen updates with a 500-millisecond timeout, so it does not redraw on every pulse. The encoder counter starts at 50 and is clamped between 0 and 99. The display also shows the pressed state of the encoder and the button, so you can immediately check whether everything responds.
- TFT module display: 1.8 inches
- Resolution set in the code: 160 x 128 pixels
- Encoder counter: starts at 50, clamped between 0 and 99
- Screen refresh timeout: 500 milliseconds
- Serial port speed: 115200 baud
- Button debounce: 10 milliseconds
- Mounting screws: four 4mm M3
Anyone who wants to rebuild the project will find the starting point for the code and the assembly on the project page on Hackster.io. The libraries to install are Adafruit_GFX, Adafruit_ST7735 and SPI. The ESP32 board package for the Arduino IDE completes what is needed.
The result is a single unit with a knob, a button and a screen, driven by an ESP32-C3. There is no need to solder three separate modules, because the 1.8-inch module already contains them. And the test firmware is ready: upload it, turn the knob and watch the number change.
Source: https://www.hackster.io/john-bradnam/interfacing-a-1-8in-tft-display-rotary-enc-switch-module-c5f8a6
Related productsThe post A 3D-printed case for the TFT module with EC11 encoder and ESP32-C3 appeared first on Open Electronics.
<new>
Rohde & Schwarz, Connektica Develop Automated RF Test Systems for Satellite and Radar Applications
Rohde & Schwarz and Connektica will showcase a joint demonstration of automated testing solutions for passive and active RF components, including low-noise amplifiers (LNAs), and satellite payloads at Space Tech Expo Europe 2026. The demonstration will take place at the Connektica booth (D9-05, Hall 5) in the Occitanie Region pavilion.
The demonstration highlights the results of several projects that Rohde & Schwarz and Connektica have worked on over the past year to test satellite payloads and radar systems during qualification and production. The system combines Rohde & Schwarz’s R&S SMW vector signal generator, FSW signal and spectrum analyser, and R&S NGP power supply with Connektica’s Manufacturing Execution System (MES) platform for automated Assembly, Integration and Testing (AIT). This integrated solution helps space and NewSpace manufacturers automate testing across a wide range of products, from passive and active RF components to complete satellite payloads.
The joint demonstration builds on the partnership between Rohde & Schwarz and Connektica, following their earlier demonstration at the Rohde & Schwarz booth in Salt Lake City. The system was integrated by Rohde & Schwarz’s team in Madrid, while Connektica’s team in Toulouse remotely prepared the complete software setup. This shows how teams working from different locations can collaborate to set up and operate automated test systems.
Bridging the Gap Between Lab and ProductionIn the lab, engineers typically set up each instrument individually, export measurements one instrument at a time and manually copy results into spreadsheets or report templates. When the first working unit is ready and production scaling begins, industrialisation teams look for complete test systems rather than individual instruments. Lab setups that were never capitalised on then make the transition slow and risky, especially when teams lack internal RF automation resources or are under pressure to decide quickly.
Rohde & Schwarz and Connektica address this gap with a joint approach, first presented at the Rohde & Schwarz annual event in Munich earlier this year:
- Start together at the lab phase: both companies engage from the first instrument sale, before production procurement is shaped.
- Off-the-shelf software test sets: pre-built test sequences, instrument drivers and report templates, so every new customer starts from a proven foundation rather than a blank page.
- COTS test systems: pre-characterised configurations that shorten decision cycles and give customers a complete solution.
The two companies encourage space manufacturers to engage Rohde & Schwarz and Connektica early, already in low-TRL development phases. Test engineers organise their data from day one, automate their own scripts and build modular test blocks. As the product matures, these blocks are reused and assembled like a Lego set into a complete AIT flow, allowing the Manufacturing Readiness Level (MRL) to rise alongside the TRL rather than after it. Because quality is built in from the ground up, with traceable test data from the earliest phases, manufacturers are also better prepared for EN9100 compliance later on.
Jeremy Perrin, CEO of Connektica, said: “Most test benches are rebuilt from scratch when a product moves from the lab into production. With Rohde & Schwarz, we help engineers capture their lab work as reusable test blocks from the earliest development phases. By the time they scale, their production test flow is already largely built, and the quality foundations needed for EN9100 compliance are already in place.”
Ralph Kirchhoff, Global Business Development Manager Space at Rohde & Schwarz, added: “As satellite manufacturers scale from prototype AIT to qualification and series production, they need reproducible RF tests with shorter throughput and higher efficiency. Early integration of Rohde & Schwarz instrumentation with Connektica’s AIT automation lets programmes grow test capacity in step with manufacturing volume and deliver qualified satellite payloads and subsystems to market faster.”
The demonstration will be shown at Space Tech Expo Europe in Bremen from November 17 to 19, 2026, at the Connektica booth in the Occitanie Region pavilion, stand D9-05 in Hall 5.
The post Rohde & Schwarz, Connektica Develop Automated RF Test Systems for Satellite and Radar Applications appeared first on ELE Times.
A cycle-accurate BBC Micro emulator runs on a $1.20 RP2350
A cycle-accurate BBC Micro emulator runs on a single $1.20 Raspberry Pi RP2350 chip, mounted inside a Pimoroni Presto with a 480×480 touchscreen, WiFi and an SD card slot. The device boots straight into Elite. It also accepts other disks and a BBC keyboard over WiFi from a phone, tablet or laptop. The porting and optimisation took less than a day, going through twelve measured steps.
Behind it is beebjit, Chris Evans’ BBC Micro emulator, ported to the RP2350’s Cortex-M33 cores with a new JIT backend for Thumb-2. The JIT compiles each 6502 code sequence into host code once, in a fixed slot for every 6502 address. The slots live in the lower part of the 4 MB of PSRAM, 64 bytes per 6502 address, and execute through the chip’s 16 KB XIP cache.
A just-in-time compiler was ported to the RP2350.
Emulated memory is a single flat 64 KB space in SRAM. Writes to ROM are discarded in software. Every store compiled by the JIT checks a byte for the page written: this way it invalidates the slot if it contains compiled code, or signals an image change if the page is read by the CRTC. The page check costs four instructions.
Self-modifying code and code that changes every time run in beebjit’s “inturbo”, an interpreter generated with one handler per opcode, also in PSRAM. Hardware register accesses, BCD arithmetic, reset and interrupts instead fall back on beebjit’s C interpreter copied into SRAM at boot.
Two cores, the PIO and the ST7701 panelThe load is split between the two cores. Core 0 runs the 6502 and the hardware and sends the drawing to core 1 through a “render wire”. The PIO state machines scale, scan out and time the panel without CPU help. The result shows in the numbers: Elite runs at 7.6 times real speed at full tilt. At real speed core 0 is busy 13% of the time and core 1 11%.
The jump from the first attempts is stark. The first JIT build ran Elite at 1.45 times real speed, with core 0 busy 69% of the time. The final JIT build is 5.2 times the first JIT build. Before the JIT, beebjit’s C interpreter ran the BASIC prompt at 0.57 times real speed. All measurements were taken on the Elite title screen at 250 MHz.
- RP2350: 520 KB of SRAM and 16 KB XIP cache
- Pimoroni Presto: 480×480 touchscreen and 8 MB of PSRAM
- JIT: lower 4 MB of PSRAM for compiled code
- JIT: 64 bytes reserved for each 6502 address
- Emulated memory: a single flat 64 KB space in SRAM
The web panel offers a BBC keyboard with CAPS LOCK, SHIFT LOCK and tape motor LEDs. It accepts uploading .ssd, .dsd or .zip disks, even from a link or from the SD card. It also shows status with per-core load, emulation speed, clock and chip temperature. So you can control the device from a phone, tablet or laptop without touching the board.
The device can be controlled through a web interface.
Rebuilding the project requires the Pico SDK and the Arm toolchain. The firmware is called presto_beebjit.uf2, while scripts/setup.sh and tools/presto.py handle preparation and flashing. The AGENTS.md file and the GXR graphics ROM complete the picture. The code and instructions are in Dominic Pajak’s repository, which is the starting point for rebuilding everything.
Anyone who wants to experiment with the same RP2350 without going through the Presto can start from a starter kit with Pico 2, the board based on that very chip. The $1.20 RP2350 chip remains the heart of the whole project anyway.
The result shows that a cycle-accurate emulator of an 8-bit computer can run on a $1.20 microcontroller. The Thumb-2 JIT, the 64-byte slots in PSRAM and the four-instruction page check do the work. Wobble Colours by the Bitshifters, a 256-byte intro, is just one of the tests the system can handle once the right disk is loaded.
Source: https://github.com/8bitkick/rp2350-bbc-micro
Related productsThe post A cycle-accurate BBC Micro emulator runs on a $1.20 RP2350 appeared first on Open Electronics.
Driving Motion Precision: How Physical AI is Converting Data into Action
Autonomous manufacturing is entering a new phase where robotics, Physical AI, and semiconductor innovation converge to transform how factories sense, decide, move, and adapt. In a detailed conversation with Anwesh Koley of ELE Times, Allan Lagasca, Director, Smart Industrials Segment, Robotics Segment Strategic Program, STMicroelectronics, delved into how robots have evolved into intelligent physical systems combining perception, edge AI, motion control, actuation, power management, connectivity, and functional safety.
ELE Times: Share your thoughts on physical AI and how you see it transforming machine operation?
Allan Lagasca: Physical AI is the bridge that converts data into action. It brings together AI, sensing and control so machines can act in the physical world. The challenge is evident in a robotic hand that resembles a human hand. With six motors controlling the robot and 21 data points generated by the hand, AI, sensing, processing and control must work together precisely, even as the hand moves constantly. This is what the machines do when they sense, reason and respond in real-time, rather than executing a predetermined sequence of instructions.
ELE Times: What is the vision of STMicroelectronics towards Smart Industrials?
Allan Lagasca: Our vision for Smart Industrials is to advance from individual products to modules and system-level solutions. Our Robotics Segment Strategy integrates sensing, edge AI, processing, motor control, power, connectivity and safety to support robotic hands, joints and cameras within a coherent architecture. Through reference designs and collaboration with module and ecosystem partners, we help customers simplify integration, improve motion precision and energy efficiency, reduce system cost and accelerate deployment. This positions ST as a system-level technology partner, addressing customer applications rather than simply supplying components.
ELE Times: How is STMicroelectronics translating AI language into practical robotics applications for the Indian market?
Allan Lagasca: We translate AI into practical robotics through development platforms and ecosystem collaboration. Our compact 6DoF Robotic Hand with AI Gesture Recognition Control demonstrator, powered by the STM32N6 MCU, combines motion sensing and processing. For India, the opportunity is to strengthen the robotics supply chain around precision joints, hands and modules, while developing datasets for robotic AI training and building on emerging prosthetics capabilities. We aim to connect Indian start-ups, new robotics players and manufacturers with the global robotics ecosystem, helping them develop practical applications and participate in global supply chains.
ELE Times: How does automotive-grade electronics apply to robotics? How do you ensure safety, real-time control, harsh environments, and high uptime?
Allan Lagasca: Both cars and robots need to operate reliably around people. Proven quality, long service life, endurance and suitability for challenging environments are all hallmarks of automotive-grade electronics. Because humanoids are also mobile and interact directly with humans, safety becomes an even more important consideration. Safety needs to be designed into the system because even if a robot meets a particular standard, a sensor failure or an incorrect AI system decision can still create a safety risk.
Automotive-grade components do not replace application-specific safety assessment and system validation. Cybersecurity is also very important and we are incorporating it into our product strategy, along with other requirements like Europe’s Cyber Resilience Act. This is why real-time control and intelligence close to the point of action are important in robotics.
ELE Times: How have key robotic architectures evolved over the years?
Allan Lagasca: The first robots were centrally controlled machines. Today centralized processing and distributed intelligence work together. The central processor provides overall coordination for the system, while time-critical decisions, such as adjusting grip, can be made locally. This is important because even a few milliseconds of delay can affect the precision of coordinated joint movements. Humanoid robotics is still emerging, so we want to stay close to customers at this stage.
ELE Times: Humanoid robots are fast becoming socially visible. How do you see this technological progress augmenting human life across the globe? What are the future trends in humanoids we can look forward to?
Allan Lagasca: Humanoid robots can augment human capabilities by taking on repetitive and dangerous tasks in manufacturing and logistics, with potential applications in healthcare and daily life. Looking ahead, space exploration could extend this role to supporting astronauts, inspecting equipment and preparing infrastructure in hazardous environments.
Progress will depend on greater autonomy, dexterity, energy efficiency and reliable operation. More integrated modules and lower costs could accelerate adoption, but battery life, safety, regulation and public confidence remain critical. The goal is not simply more capable robots, but trusted systems that compliment people on Earth and beyond.
ELE Times: Tell us more about high-precision surgical robots and the complexity involved in their application.
Allan Lagasca: There is virtually no room for error in surgery. A surgical robot must replicate the surgeon’s handling and move the tools with a “natural” and smooth motion desirable for passing through the surgical site, while preserving vital information at all times even during constant motion. That requires accurate current sensing to maintain torque and to detect any faults as early as possible. ST’s robotics portfolio provides building blocks that can support these functions, spanning from the intelligent motor driver to current sensor, motion sensor and microcontroller for real-time control.
ELE Times: Describe the penetration of robotic applications in the medical industry. How do you address the criticality required in this domain?
Allan Lagasca: Medical robotics is a growing area within Smart Industrials. ST also addresses established rehabilitation and assistive applications, including prosthetics, exoskeletons and assistive robots. Our collaboration with NVIDIA supports physical AI development across humanoid, industrial, service and healthcare robotics. For systems interacting with patients and clinicians, safety is paramount.
Our building blocks support system-level safety and cybersecurity, while local processing can limit sensitive data transmission, depending on system design. We help medical device companies focus on innovation, while application-specific safety and medical-device validation remain the manufacturer’s responsibility.
ELE Times: With Artificial Intelligence making its way into every sphere of application, what are the innovations we can expect robotics to undergo in the foreseeable future?
Allan Lagasca: Robotics will see closer integration of AI, semiconductors, sensors, power electronics, software and mechanics. AI will require more diverse real-world data to support robotic learning and reliable operation. Edge intelligence will enable faster responses, while local processing—as in our camera demonstration—can help protect privacy.
Privacy, safety and cybersecurity must be critical design priorities throughout AI development and deployment, supported by responsible data handling and system validation. Integrating more functions into fewer components will also help reduce costs and improve efficiency, making capable, trusted robotics more accessible.
ELE Times: Describe the integration of ST’s technologies such as microcontrollers, sensors, and actuators into robotics systems.
Allan Lagasca: Sensors provide a robot’s “eyes” and “balance”; microcontrollers and processors act as its “brain”; motor control and power devices act as its “muscles”. ST’s portfolio spans more than 500 parts, covering approximately $600 of a robot’s bill of materials. Our module-to-system strategy integrates these technologies through reference designs and module partners, connecting hands, joints and cameras within a coherent architecture. We start with application requirements: for one customer’s 6DoF robotic hand, integrating six motors on a 6 cm × 6 cm board required a more compact system-level design using ST’s latest compact system-in-package motor drivers.
ELE Times: Finally, how does STMicroelectronics intend to shorten the path from concept to deployment for professional service robots?
Allan Lagasca: Our Robotics Segment Strategic Program is part of ST’s strategy to address the robotics market, advancing a module-to-system approach to help customers move from concept to deployment. Rather than simply selling individual components, we are bringing more of the building blocks together through reference designs and working with module partners. With integrated modules and demonstrated designs for hands, joints and cameras from ST and its ecosystem partners, customers can avoid building everything from scratch. This can simplify integration and manufacturing and help reduce system cost.
Our collaboration with NVIDIA aims to further shorten this journey by helping developers simulate and test robotics systems before building the physical hardware. The collaboration includes work to integrate ST sensors and motor-control solutions with the NVIDIA robotics ecosystem, including NVIDIA Isaac Sim, to support design and simulation before real-world deployment. In a market that is evolving this quickly, we want to be early and stay close to customers so we can help move promising concepts towards deployment faster.
The post Driving Motion Precision: How Physical AI is Converting Data into Action appeared first on ELE Times.
My first FM transmitter!
| I made it using a 27 MHz crystal oscillator and tuning the LC tank to the third harmonic multiple of the crystal (81 MHz), and i got a very very stable transmission and got a *somewhat* decent range with a crude dipole antenna i made (i got about 15 meters of transmission range in a crowded city.) [link] [comments] |
GÖPEL Electronic Joins Automotive SerDes Alliance to Support ASA-ML Automotive Networking
High-speed communication technologies are becoming increasingly important in modern vehicles. ASA-ML (ASA Motion Link) is developing as an open, vendor-neutral standard for in-vehicle networking. GÖPEL electronic, a specialist in automotive measurement technology, has now joined the Automotive SerDes Alliance (ASA), which was established in 2019 to develop an open standard based on high-speed SerDes (Serializer/Deserializer) technology. Through this membership, GÖPEL electronic aims to contribute its technical expertise, support the development of the standard and help advance solutions for automotive communication systems.
ASA-ML is designed to transmit large amounts of data from high-resolution cameras, LiDAR and radar sensors to vehicle control units. With data speeds of up to 16 Gbps per lane, it can support the high communication demands of Level 3 and higher autonomous driving systems. As modern vehicles use more sensors and generate increasing amounts of data, this technology offers a reliable way to transfer information quickly. GÖPEL electronic is already preparing its automotive measurement solutions for ASA-ML. For example, its Video Dragon frame grabber and generator, used to test and validate industrial cameras, displays and electronic control units (ECUs), already supports the standard.
The post GÖPEL Electronic Joins Automotive SerDes Alliance to Support ASA-ML Automotive Networking appeared first on ELE Times.
Благодійні середи та Родинні суботи в ДПМ
"Музей як простір життєствердження та радості буття", – саме з таким задумом в Державному політехнічному музеї імені Бориса Патона при КПІ ім. Ігоря Сікорського з 2024 року діють дві програми – Благодійні середи та Родинні суботи.



