Feed aggregator

Sirojudin Munir has released an open-source FOC driver for BLDC and PMSM motors. The project includes firmware for STM32, hardware designed in KiCad, Gerber files, a BOM, and a Python GUI for control and monitoring. It is a complete resource for anyone who wants to build or study the vector control of a brushless motor. The permissive MIT license and the stated component cost of $28.58 make it accessible to many makers.

The heart of the system is the STM32F405 microcontroller, which runs the Field-Oriented Control calculations. The ADC reads current, the PWM drives the inverter, and SPI communicates with the magnetic encoder. The DRV8323RH gate driver manages the MOSFETs and also acts as a voltage regulator. The AS5047 encoder detects the rotor position, while the INA240A1 amplifier measures current with precision. All these components work together for efficient and responsive control.

How FOC control works

The firmware implements the Field-Oriented Control algorithm to manage motor torque and speed. The self-commissioning process measures motor resistance and inductance and calibrates the encoder. This way, the driver adapts to the connected motor without manual intervention. Several control modes are available: current, speed, position, open-loop, and motor disable. This flexibility makes the project suitable for many practical applications.

• Current control to manage torque
• Speed control with encoder feedback
• Position control for precision applications
• Open-loop mode for quick tests
• Full motor disable for safety

The PyQt/PyQtGraph GUI allows real-time data visualization and sending commands to the driver. The Python tools include functions for calibration and monitoring. Additionally, the improved client written by Munir simplifies system tuning. The project is designed to be studied and modified, with clear documentation and well-organized files.

Hardware and main components

The schematic and PCB are made in KiCad, with Gerber files ready for production. The board operates with voltages from 6 to 24 V and current up to 1 A. The 3-pin connector with 1.25 mm pitch makes motor connection easy. Those who want to study brushless control starting from something ready-made can look at a brushless motor driver with a Hall sensor: it does not do vector control, but it lets you see the inverter and power MOSFETs in action before making your own board. For testing, you will need a brushless motor.

The DRV8323RH gate driver is a key component: it drives the inverter MOSFETs and integrates a voltage regulator. The AS5047 magnetic encoder offers high resolution for rotor position. The INA240A1 measures current with a dedicated amplifier. These components are chosen to ensure reliable performance and good value for money.

Software tools and commissioning

The firmware compiles with PlatformIO in Visual Studio Code, starting from the STM32CubeMX configuration. The project board includes all the steps for commissioning. Self-commissioning automates the measurement of motor resistance and inductance. Encoder calibration is guided, reducing errors. Finally, the Python GUI lets you test the different control modes in real time.

Munir’s project is an excellent example of open-source technical documentation. It includes demonstration videos and clear instructions for reproduction. For those taking their first steps with brushless motors, this driver offers a solid foundation. Even those with experience can find interesting ideas in the design and firmware.

In summary, this is a complete, well-documented FOC driver with a permissive license. The component cost is low and the build quality is high. For anyone wanting to delve into brushless motor control, this is a project worth studying carefully. The combination of STM32, DRV8323RH, and AS5047 delivers remarkable performance in a compact format.

Source: https://github.com/sirojudinMunir/sf-motion

Related products

• Brushless motor

The post Open-Source FOC Driver for BLDC Motors: Sirojudin Munir’s Project appeared first on Open Electronics.

Sirojudin Munir has released an open-source FOC driver for BLDC and PMSM motors. The project includes firmware for STM32, hardware designed in KiCad, Gerber files, a BOM, and a Python GUI for control and monitoring. It is a complete resource for anyone who wants to build or study the vector control of a brushless motor. The permissive MIT license and the stated component cost of $28.58 make it accessible to many makers.

The heart of the system is the STM32F405 microcontroller, which runs the Field-Oriented Control calculations. The ADC reads current, the PWM drives the inverter, and SPI communicates with the magnetic encoder. The DRV8323RH gate driver manages the MOSFETs and also acts as a voltage regulator. The AS5047 encoder detects the rotor position, while the INA240A1 amplifier measures current with precision. All these components work together for efficient and responsive control.

How FOC control works

The firmware implements the Field-Oriented Control algorithm to manage motor torque and speed. The self-commissioning process measures motor resistance and inductance and calibrates the encoder. This way, the driver adapts to the connected motor without manual intervention. Several control modes are available: current, speed, position, open-loop, and motor disable. This flexibility makes the project suitable for many practical applications.

• Current control to manage torque
• Speed control with encoder feedback
• Position control for precision applications
• Open-loop mode for quick tests
• Full motor disable for safety

The PyQt/PyQtGraph GUI allows real-time data visualization and sending commands to the driver. The Python tools include functions for calibration and monitoring. Additionally, the improved client written by Munir simplifies system tuning. The project is designed to be studied and modified, with clear documentation and well-organized files.

Hardware and main components

The schematic and PCB are made in KiCad, with Gerber files ready for production. The board operates with voltages from 6 to 24 V and current up to 1 A. The 3-pin connector with 1.25 mm pitch makes motor connection easy. Those who want to study brushless control starting from something ready-made can look at a brushless motor driver with a Hall sensor: it does not do vector control, but it lets you see the inverter and power MOSFETs in action before making your own board. For testing, you will need a brushless motor.

The DRV8323RH gate driver is a key component: it drives the inverter MOSFETs and integrates a voltage regulator. The AS5047 magnetic encoder offers high resolution for rotor position. The INA240A1 measures current with a dedicated amplifier. These components are chosen to ensure reliable performance and good value for money.

Software tools and commissioning

The firmware compiles with PlatformIO in Visual Studio Code, starting from the STM32CubeMX configuration. The project board includes all the steps for commissioning. Self-commissioning automates the measurement of motor resistance and inductance. Encoder calibration is guided, reducing errors. Finally, the Python GUI lets you test the different control modes in real time.

Munir’s project is an excellent example of open-source technical documentation. It includes demonstration videos and clear instructions for reproduction. For those taking their first steps with brushless motors, this driver offers a solid foundation. Even those with experience can find interesting ideas in the design and firmware.

In summary, this is a complete, well-documented FOC driver with a permissive license. The component cost is low and the build quality is high. For anyone wanting to delve into brushless motor control, this is a project worth studying carefully. The combination of STM32, DRV8323RH, and AS5047 delivers remarkable performance in a compact format.

Source: https://github.com/sirojudinMunir/sf-motion

Related products

• Brushless motor

The post Open-Source FOC Driver for BLDC Motors: Sirojudin Munir’s Project appeared first on Open Electronics.

Infineon Technologies AG introduces the TDA235E5 and TDA235E0, a dual-phase smart power stage family designed to meet the rapidly growing power density requirements of next-generation AI accelerators and vertical power delivery modules. Integrating Infineon’s OptiMOS 6 MOSFETs and a dual-phase driver IC in a compact 6 x 6 x 0.8 mm³ package, the new family delivers benchmark power density exceeding 2 A/mm², setting a new reference point for power stage performance in high current AI processor applications. As hyperscalers and datacenter operators continue to scale AI infrastructure, the demand for power delivery solutions that combine higher current capability with shrinking physical footprints is becoming a critical bottleneck.

“Infineon customers are designing AI systems that will define the next decade of computing infrastructure,” said Rakesh Renganathan, Vice President Power ICs at Infineon. “The TDA235E5 and TDA235E0 power stages give designers the power density, thermal performance, and design flexibility to move faster and build with confidence, backed by Infineon’s full AI server power delivery ecosystem.”

The two devices support up to 300 A peak current and 120 A total design current (TDC), making them well suited for next generation AI xPU accelerators as well as conventional server CPUs in datacenter environments. Both lateral and vertical power delivery configurations are supported, providing the design flexibility required as the industry transitions toward vertical power module architectures in advanced AI processor packages. Superior thermal impedance from junction to top side enables efficient liquid cooling integration, a characteristic that is increasingly important as power levels per processor socket continue to rise and traditional air-cooled thermal budgets are exhausted. Combined with Infineon’s digital multiphase controllers, the power stages support flexible, scalable multi-rail architectures that reduce time to deployment in fast-evolving AI server platforms.

The TDA235E5 and TDA235E0 integrate into Infineon’s end-to-end AI server power delivery ecosystem, spanning the full power chain from grid interface to processor core rails. By combining the complementary strengths of silicon, silicon carbide, and gallium nitride, Infineon provides datacenter customers with a proven, scalable path to the highest efficiency, robustness, and power density available for AI-optimized infrastructure. The datacenter power delivery market is one of the semiconductor industry’s fastest-growing demand segments, driving Infineon’s continued product investment to serve this opportunity at the component level where power density requirements are most critical. 

The post Infineon Sets New Power Benchmark for AI accelerators and Vertical Power Delivery with 2 A/mm² Dual-Phase Smart Power Stages appeared first on ELE Times.

Hello everyone, Six months ago I set upon the journey of making my own AWG, with frequencies of up to 1MHz. 6 months later I present you my very own awg. Full Repo I set out to build my own function generator after finding commercial units both too expensive and more general-purpose than I needed, and it looked like a good excuse to work through analog synthesis, filtering, and mixed-signal PCB design end to end. The sine path is an 8-bit R-2R ladder driven by a Raspberry Pi Pico W (overclocked to 225MHz) generating samples via a DDS phase accumulator; the square wave comes from the same chip’s PIO hardware. I started off with a breadboard and tried sallen key filters for noise but they amplified the noise aswell. I also tried discrete components for the sauare wave before replacing it outright with a TC4427 gate driver. The sine chain settled on a 5th-order doubly-terminated LC Butterworth reconstruction filter, replacing an earlier cascaded-RC design that was capping amplitude, followed by LM318 gain and buffer stages. Three PCBs went out; two came back dead. V1.0 was completely non-functional because a BOM matcher substituted 2.21Ω resistors for 2.21kΩ across the entire R-2R ladder. V1.1 moved to an all-SMD board with the LC Butterworth filter but came up dead silent; testing the square path first (it worked) narrowed the fault to the sine chain, which traced to a KiCad-to-Altium migration that had silently shorted two LM318 input pins onto one net. V1.2 fixed that short, soldered the Pico directly to the board in place of a socket, and came up working: sine characterised from 0Hz to 1MHz and square to 2MHz, with AM, FM, and noise modes added on top in firmware, all controllable from a Python desktop UI over USB. Looking at it now, a redesign with some improvements (better op-amps and also fewer) would be better but I also want to work on other stuff, so for now this is it. To be clear, I made every schematic and protoype and thought up everything myself. As such this may not be the best way to do this. My main goal, was experience after all. full webpage submitted by /u/S4vDs [link] [comments]

In Yole Group’s White Paper ‘Photonics at the Speed of AI’ (part of the firm’s AI White Papers Collection), it argues that optical transceivers — once a supporting piece of data-center infrastructure — have become a system-level requirement for scaling artificial intelligence...

Phil Underwood has spent twenty years mapping underground caves. His work has produced a series of open hardware devices that increase the speed and accuracy of surveys. The journey starts with tools based on 8-bit microcontrollers and arrives at a complete photogrammetry system. Each generation solved a specific problem, improving the design incrementally.

The first version, presented in 2008, used an accelerometer and a magnetometer to determine direction and angle. Distance, however, was still measured manually. The heart of the system was a PIC18LF2550, an 8-bit microcontroller. This approach proved that part of the survey could be automated, but human intervention was still needed for linear measurements.

The turning point came in 2020. Phil added a laser rangefinder and a 32-bit microcontroller. This allowed the device to calculate distances autonomously and handle more complex operations. Data collection also became faster and less error-prone. The move from 8 to 32 bits made it possible to process more information directly in the field.

Improved design and community

In 2023 the project received special attention. The enclosure was 3D-printed, with silicone buttons resistant to water and dust. The firmware moved to CircuitPython, a language that makes community contributions easier. Many makers were able to modify the code without deep electronics knowledge. This accelerated development and made the project more open.

Choosing CircuitPython made the code more readable and easier to maintain. 3D printing also allowed custom enclosures for each environment. The modular design made it simple to replace damaged components. As a result, the device became a reliable tool for cavers.

• 2008: accelerometer, magnetometer, PIC18LF2550 8-bit
• 2020: laser rangefinder and 32-bit microcontroller
• 2023: 3D-printed enclosure and CircuitPython firmware

Latest version: Raspberry Pi 5 Compute Module and photogrammetry

The latest generation represents a technological leap. The system uses a Raspberry Pi 5 Compute Module and two low-light cameras. The cameras capture images of the cave interior, then the software processes them to create textured 3D models. This approach eliminates the need to measure every point manually. The result is a detailed and realistic map.

For those wanting to experiment with similar sensors, a 9-axis module with accelerometer, gyroscope, and magnetometer combines in one unit the two measurements that supported the 2008 version. For processing, a Raspberry Pi 5 with 4 GB of RAM handles photogrammetry without strain, and a 5-megapixel camera for Raspberry Pi is the cheapest way to try dual capture.

Phil Underwood’s project shows a methodical approach to hardware design. Every choice, from materials to computing power, was guided by the real needs of cavers. The lessons learned apply to any rugged instrumentation. In particular, modularity and ease of maintenance are essential in extreme environments.

Lessons for makers

The story of this project teaches that incremental evolution works. You start with a simple prototype, test it in the field, then improve it. Each generation solved a concrete problem. Moreover, openness to the community accelerated the process. Documentation and code are available for anyone who wants to contribute.

Cave mapping with photogrammetry is just the latest milestone. The complete system, with Raspberry Pi 5 Compute Module, is an example of how open source hardware can tackle complex challenges. The device is called Shetland Attack Pony, and the sixth generation (SAP6) is fully documented: schematics, component list, and CircuitPython code are public.

Source: https://stic.readthedocs.io/

The post Mapping Caves with Photogrammetry and Raspberry Pi appeared first on Open Electronics.

Phil Underwood has spent twenty years mapping underground caves. His work has produced a series of open hardware devices that increase the speed and accuracy of surveys. The journey starts with tools based on 8-bit microcontrollers and arrives at a complete photogrammetry system. Each generation solved a specific problem, improving the design incrementally.

The first version, presented in 2008, used an accelerometer and a magnetometer to determine direction and angle. Distance, however, was still measured manually. The heart of the system was a PIC18LF2550, an 8-bit microcontroller. This approach proved that part of the survey could be automated, but human intervention was still needed for linear measurements.

The turning point came in 2020. Phil added a laser rangefinder and a 32-bit microcontroller. This allowed the device to calculate distances autonomously and handle more complex operations. Data collection also became faster and less error-prone. The move from 8 to 32 bits made it possible to process more information directly in the field.

Improved design and community

In 2023 the project received special attention. The enclosure was 3D-printed, with silicone buttons resistant to water and dust. The firmware moved to CircuitPython, a language that makes community contributions easier. Many makers were able to modify the code without deep electronics knowledge. This accelerated development and made the project more open.

Choosing CircuitPython made the code more readable and easier to maintain. 3D printing also allowed custom enclosures for each environment. The modular design made it simple to replace damaged components. As a result, the device became a reliable tool for cavers.

• 2008: accelerometer, magnetometer, PIC18LF2550 8-bit
• 2020: laser rangefinder and 32-bit microcontroller
• 2023: 3D-printed enclosure and CircuitPython firmware

Latest version: Raspberry Pi 5 Compute Module and photogrammetry

The latest generation represents a technological leap. The system uses a Raspberry Pi 5 Compute Module and two low-light cameras. The cameras capture images of the cave interior, then the software processes them to create textured 3D models. This approach eliminates the need to measure every point manually. The result is a detailed and realistic map.

For those wanting to experiment with similar sensors, a 9-axis module with accelerometer, gyroscope, and magnetometer combines in one unit the two measurements that supported the 2008 version. For processing, a Raspberry Pi 5 with 4 GB of RAM handles photogrammetry without strain, and a 5-megapixel camera for Raspberry Pi is the cheapest way to try dual capture.

Phil Underwood’s project shows a methodical approach to hardware design. Every choice, from materials to computing power, was guided by the real needs of cavers. The lessons learned apply to any rugged instrumentation. In particular, modularity and ease of maintenance are essential in extreme environments.

Lessons for makers

The story of this project teaches that incremental evolution works. You start with a simple prototype, test it in the field, then improve it. Each generation solved a concrete problem. Moreover, openness to the community accelerated the process. Documentation and code are available for anyone who wants to contribute.

Cave mapping with photogrammetry is just the latest milestone. The complete system, with Raspberry Pi 5 Compute Module, is an example of how open source hardware can tackle complex challenges. The device is called Shetland Attack Pony, and the sixth generation (SAP6) is fully documented: schematics, component list, and CircuitPython code are public.

Source: https://stic.readthedocs.io/

The post Mapping Caves with Photogrammetry and Raspberry Pi appeared first on Open Electronics.

Заслужений професор КПІ Юрій Лукач. До 100-річчя від дня народження Інформація КП пн, 09/07/2026 - 17:00

Here is my project repo https://github.com/fredriknk/chatgpt_astra_test2 I saw the Chatgpt Astra kicad demo, and wanted to try it out myself and im pretty damn impressed...! I only have a openai 20$/mo plus subscription so i had to use the lowest setting, but i got this design in 3 hours with 5 prompts in total and ate up my 3 usage resets. My only contributions to the design was to create the empty kicad template project, and the initial prompt: "Lets test a esp32 design with a 24v input voltage which can output and read 4-20ma signals. Lets start planning!" All design choices, component choices, design, schematics and, layout and documentation was done by the chatgpt astra 6 low through codex cli. So final verdict? Its actually pretty damn usable.... Like, its not perfect by any means. some examples: There are a quite a few routing decisions i dont agree with, especially the USB routing and unneccesarry internal layer routing. The schematics are very hard to read as it doesnt use GND/Power symbols, and only use global labels instead of wires. But as far as i can tell from the schematic, this is a working design and i do agree with a lot of its component choices. I feel it is pretty much where AI coding was in around 2024 (on its lowest setting), so im wondering where this will be in a year or two..! submitted by /u/Gjfiyfyifiyf [link] [comments]

The simplest explanation is likely the best, even if its validity isn’t always intuitively obvious in advance.

Speaking of USB-C, and the cables (including splitters) that connect to it to other things…

My long-in-the-tooth Intel-based 2018 Apple Mac mini is still sitting on my desk, humming to my right, even though its M2 Pro Apple Silicon-based successor has been sitting downstairs in storage awaiting its turn in the spotlight for going on three years now. The legacy hardware is no longer a candidate for new Apple operating system releases, but it’s still receiving bug fixes and security patches, until sometime in the second half of next year, if past-history trends remain valid. And as the saying goes, “if it works, don’t touch it” (I’d also be tempted to haul out the “a penny saved is a penny earned” quote, but since I’ve already bought its replacement…).

In conjunction with my transition to it from its 2014-era Mac mini predecessor roughly 2.5 years ago, I upgraded the two-display suite above it to a set of Dell P2415Q 4K LCDs.

The Mac mini leverages the displays’ HDMI inputs; a “Project Volterra” Windows-on-Arm dev kit 2023 stacked above it connects to those same LCDs over their DisplayPort connections, and front panel buttons toggle the displays between the two systems when running concurrently.

Look back at that 2018 Mac mini rear panel “stock” photo a couple of paragraphs ago, however, and you’ll only see one HDMI output, into which I’ve plugged a “straight” HDMI cable running directly to one of the LCDs. How, then, did I connect the system to the other display’s HDMI input? That’s where today’s teardown victim enters the picture.

It’s an Anker A8730 6’ USB-C to HDMI adapter cable; I’d bought and pressed it into immediate service way back in mid-2021. I sourced from Anker’s outlet store on eBay, where it cost $25.90 as a refurb. So, you can say I’ve gotten my money’s worth out of it! Speaking of fiscal topics, there’s a 0.75′′ (19.1 mm) diameter U.S. penny alongside in the second (and non-stock) image that follows, along with subsequent others, for size comparison purposes.

A multimedia-centric repurpose

How it works is (at least to me) an interesting story in and of itself. It fundamentally leverages a DisplayPort technology called “Alt Mode”, which repurposes USB 3.x’s “SuperSpeed” data and Configuration Channel (CC) lines to transport dedicated audio and video streams sourced from the graphics and sound subsystems. The CC leverage explains why, among other implementation reasons, it’s only applicable to USB-C, not also to prior-generation USB physical connector standards.

Macs don’t additionally support DisplayPort’s Multi-stream Transport (MST) mode, either in the operating system (generally) or in hardware (for newer Apple Silicon-based systems). If MST support had existed, it would have conceivable enabled me to extended-mode tether both displays to a single USB-C (or Thunderbolt 3, aka TB3, in this case) system connector, in combination with a separate inter-display connection. But again, per the system back panel photo, I had plenty of spare connector candidates available, not even counting those on the separate expansion hubs (the latter added subsequent to the snap of the earlier “stack” picture).

But what’s with all this DisplayPort talk? I thought we were discussing connecting the computer to a display’s HDMI input! We are, and that’s where the bulge surrounding the adapter cable’s HDMI connector end comes in. Conceptually, and I hope to definitively confirm today, inside is likely a DisplayPort to HDMI protocol-converting bidirectional transceiver; a particularly robust one, it seems, since the Anker A8730 touts 4K 60 Hz specs. HDMI once also had an “Alt” mode for USB-C, at least on specification paper, although actual products never made it to market.

Erratic function = dissection rationalization

Since the adapter cable had been operational in my abode since mid-2021 (and, considering it was a refurb, maybe even earlier than that with its original owner), why’d I decide to take it apart? Curiosity was as always one motivation, although I generally hold that particular urge at bay for as long as the gear remains operational. But this one had eventually failed, in another story-in-and-of-itself, through whose telling I aspire to also rationalize the “Occam’s Razor” title reference.

As previously mentioned, the 2018 Mac mini is still receiving periodic patches for its last-supported MacOS 15 “Sequoia” operating system release. A few updates ago, the left-side display of the pair (the one leveraging the Anker adapter) was no longer recognized by the system after the upgrade and subsequent reboot. Online research revealed that mine wasn’t a unique post-update quirk, and swapping the adapter cable to a different TB3 system connector got the display going again.

So, I figured that an obscure “Alt Mode” bug (specifically, since the first TB3 port still worked fine for generic data) introduced along with the upgrade had made it through Apple’s pre-release QA checks. This purported scenario was unsurprising albeit still disappointing, given that Intel-based Macs in general, and this system in particular, were on their “last legs” and likely no longer receiving their fair share of QA attention. Why my surmised bug only affected one TB3 port but not another wasn’t clear, but…

The next time I did an update, however, the exact same thing happened, this time to the second TB3 connector. Swapping the cable adapter back to the first TB3 connector didn’t resurrect the display. And I no longer had any other spare TB3 ports on the system available to try. At this point, I began to fear I had a fundamental system hardware degradation issue on my hands.

But after unplugging the cable adapter from the Mac mini and trying it with the “Project Volterra” system instead, where it also didn’t work, I was reassured by the now-nonfunctional repetition across multiple systems (and O/Ss) that a dead cable adapter was the likely culprit. An “Amazon Basics” cable adapter replacement fired up fine, sealing the Anker A8730’s fate.

What was behind the cable adapter’s initial failure, temporary resurrection, and eventual permanent demise? I hoped the pending teardown might provide visual Achilles’ Heel evidence (hold that thought). But I suspect it has something to do with MacOS’s use of display-supplied Extended Display Identification Data (EDID) information for software interface purposes versus Windows’ leverage of (when available) display-specific drivers.

My guess is that EDID (re-) enumeration in MacOS happens both when a display is first-time plugged into a new system connector and after each sufficiently impactful operating system update. In this particular case, the aforementioned DisplayPortHDMI bidirectional protocol translator in-between the system and display initially began operating erratically and eventually failed completely. But that’s just my conjecture; reader theories in the comments are as-always also welcomed!

Eyes-on conceptual validation (or not)

Speaking of tearing down, let’s dispense with further abstract chit-chat and get to dissecting, shall we? Here are a few more real-life device photos as prep. Packaging is long gone at this point, along with any potential originally accompanying literature. The USB-C end, to start.

With a product-code sticker behind it.

Intermediary cable markings next.

And now the bulge-augmented HDMI other end, starting with the seam-less cable-intro side.

The connector side conversely does have a visible seam at its circumference.

But attempts to surmount it with hair dryers and heat guns, along with spungers and such, were for naught. So, I escalated my attack by breaking out the hacksaw with hopeful deft technique.

That’s what I’m talking about!

For anyone following in my footsteps who prefers a less Neanderthal-reminiscent dissection approach, here’s the HDMI connector-surrounding piece I was unsuccessfully trying to extract earlier. Note specifically the locations of the retention tabs.

Finally, what you’re all most interested in, the PCB. As I’ve mentioned before, “top”, “bottom” and other orientation terms are particularly nebulous where HDMI is concerned. So instead, here’s the side corresponding to the wider HDMI connector edge.

Now zooming in for a closer look.

I was admittedly surprised to encounter a preponderance of passives, given that the most common adapter-usage orientation would have put this side on top, with the remaining (and proportionally higher heat-generating) stuff you’ll see next on the other side and below it. Given that heat rises (don’cha know), and that there’s no passive ventilation venting available, that’s a seeming premature failure-inducing decision. But not in my case, since the HDMI connector points downward with this display, not horizontally straight out the back as with many others.

Components of particular note include a five-lead SOT23-packaged step-down (buck) DC-DC converter at lower left, marked as follows.

JWA5J
91D5T

There’s also a “2R2” (2.2 µH) inductor to its immediate left, and a 27 MHz oscillator to its right. And what does that clock chip likely drive? Let’s flip the PCB over to the other side.

Now that’s more like it (unless you’re into passives, that is). Again, we zoom in for a closer look.

At lower left is Via Labs’ VL100, a (surprise, surprise…not…) DisplayPort USB-C Alt-mode controller. To its right is (surprise, surprise…truly, this time, at least a bit…) another oscillator, 24 MHz this time. Continuing to the right is, I’m guessing (readers?), a serial interface nonvolatile memory for code and data storage purposes, marked as follows.

125S40
BG17K8
P19030

In the lower right corner is another JWA5J DC/DC converter. Above it is (once again, no surprise) Paradise Technologies’ PS176 DisplayPort to HDMI video interface converter. And again for the passives fans among you, there are plenty more examples to see on this side of the PCB, too!

That’s a “wrap” for today, folks. Share your thoughts with me and your fellow readers in the comments, please!

—Brian Dipert is the associate editor, as well as a contributing editor, at EDN.

Related Content

• USB-C’s lingering incompatibilities and other complexities, part 1: Direct-connect complications
• USB-C’s lingering incompatibilities and complexities, part 2: Splitter issues
• The 2025 WWDC: From Intel, Apple’s Nearly Free, and the New Interfaces Are…More Shiny?
• Connecting systems to displays with DVI, HDMI, DisplayPort: What we got here is failure to communicate
• USB: Deciphering the signaling, connector, and power delivery differences

The post Occam’s Razor and a USB-C to HDMI adapter appeared first on EDN.

Synopsys, COEP Technological University and CADFEM India have setup the “Ansys Digital Twin & Multiphysics Lab” on the COEP campus, Pune to support advanced engineering education, research, and strengthen the industry-academia partnerships. This program holds huge significance in an ecosystem for automotive and electrical vehicle industry which utilizes the technologies for vehicle system’s product development and validation processes.

The laboratory was established as a part of Memorandum of Understanding (MoU) signed during the 2026 Symposium. It will provide students, researchers, and faculty members access to Ansys digital-twin technologies and advanced high-end multiphysics simulation tool that have been acquired by Synopsis. The lab will host industry training and certification, technical seminars and research.

Multiphysics simulation has a potential role in analysis of different physics domains in development process of the vehicle or component within EV industry. Engineers are able to investigate on battery thermals, electric motor efficiencies, power electronics functionality, structural strength, electromagnetic phenomenon and thermal management by simulation work-flows prior build physical prototype. Digital-twin methodology can create bridge between physics-based models and actual data taken from sensors and operation data so to monitor and predict system behaviours.

The post Synopsys, COEP Tech University and CADFEM Establish Digital Twin and Multiphysics Lab in Pune appeared first on ELE Times.

«Драйвова осінь» 2026 kpi пн, 09/07/2026 - 14:42

​India’s rapidly growing EV industry faces a capability gap in developing and producing high-technology components that can meet modern technology demands because about 80% of component manufacturers are small businesses built for traditional mechanical parts rather than advanced electronics and software. The capability gap involves areas such as batteries, power electronics, embedded software, advanced electronics, and system integration.

India is shifting more towards electric vehicles as its automotive supply chain expands. Original Equipment Manufacturer (OEM) sourcing of auto-components is expected to increase by 16% to 6.6 lakh crore by FY26 against components’ exports valued at around 2.1 lakh crore. However, import charges rise at a greater rate, with China covering about 36% of all the auto component imports India uses.

The capability challenge is particularly significant for small and medium-scale enterprises (MSMEs), which constitute almost 80% of Indian auto-parts producers. Though electronics, embedded software, advanced engineering, and system integration are key factors for competitiveness, a lesser than half the small and medium scale enterprises lack the capabilities required to develop and manufacture components as per the modern industry demands. Embedded software capability is estimated to be found in only 10% of domestic suppliers, whereas system integration, and product-development capabilities are around 14%.

The post India’s EV Component Industry Faces Technology Capability Gap as Imports Rise appeared first on ELE Times.

There is growing demand from Indian electronics manufacturers for alternatives to expensive copper such as aluminium, and a more widespread adoption of other cheaper materials due to increased cost pressure and lower profit margins as copper prices rocket. Companies are also encouraged to boost domestic procurement and re-engineer product and component designs to reduce dependence on these raw materials.

Copper is widely used across the electronics industry because of its electrical conductivity, robustness, and reliability. Due to recent surge in copper prices has increased manufacturing costs, creating challenges for companies especially those already facing a competitive market that might not be able to fully pass the rising input costs to consumers.

A recent report stated that the copper price has risen by around 45%, thereby decreasing manufacturers’ profit. Because of this, some Indian electronics manufacturers are now considering aluminium as an alternative to copper in applications whether it’s electrical, mechanical, and thermal properties are highly required to meet product specifications. Aluminium is being considered as a substitute of copper because it is lighter and cheaper.

The product design needs modification when using aluminium as a substitute to achieve performance comparable to that of copper. Using aluminium as a substitute for copper is not easy to practically implemented across all electronics applications. It is important for manufacturers to consider properties like electrical conductivity, thermal performance, resistance to corrosion, joining techniques, and product lifespan before adopting alternate materials.

The post Indian Electronics Makers Turn to Aluminium as Rising Copper Costs Squeeze Margins appeared first on ELE Times.

Pi-Ener-lite is a compact UPS power supply designed by ACE design studio for the Raspberry Pi Zero. It connects to the board via 7 spring-loaded pogo pins, which handle both power delivery and data reading. The project integrates an 18650 battery, a CW2015 fuel gauge chip, and a DS1307 RTC chip, offering a complete uninterruptible power supply in a small footprint.

Operation is simple and reliable. When external power is lost, the system automatically switches to battery power. It also supports simultaneous charging and discharging, so you can use the Raspberry Pi Zero while the battery recharges. The whole setup is protected against overcharge, over-discharge, overcurrent, and short circuits.

Battery measurement and RTC

The CW2015 fuel gauge chip measures battery voltage and remaining capacity with ±2% accuracy. The DS1307 RTC chip, powered by a CR1220 coin cell, keeps time even when the main battery is removed. This combination makes Pi-Ener-lite a truly complete UPS for applications that require operational continuity.

Fuel gauge and RTC data are read over I2C, so you can access them easily from Python. The project includes Python examples and detailed documentation. An optional open-source 3D-printable case protects the entire system. Total cost is around $35.

Why choose Pi-Ener-lite

Pi-Ener-lite is a compact UPS specifically for the Pi Zero. Unlike other solutions, it leaves the GPIO connector free, so you can attach other modules without issues. It also adds battery measurement and an RTC, two features often missing from DIY UPS builds. The open-source 3D-printable case adds versatility.

The project is designed for those who want a reliable backup power supply without taking up space. The board connects in seconds thanks to the spring-loaded pogo pins. The CW2015 fuel gauge lets you monitor remaining charge precisely, avoiding sudden shutdowns. If you need a professional solution for your Pi Zero, this project fits the bill.

• Connection via 7 spring-loaded pogo pins, no soldering
• 18650 battery with CW2015 fuel gauge for charge monitoring
• DS1307 RTC with CR1220 battery to keep time
• Protection against overcharge, over-discharge, overcurrent, and short circuits
• Open-source 3D-printable case

To build the project, you need an 18650 battery and a CR1220 coin cell. The rest of the components are already mounted on the board. If you want to power the system from a higher voltage, you can use a 12V DC-DC step-up converter to adapt the input. Alternatively, for industrial applications, consider a DC-DC converter with 36-48V input and 24V output.

Getting started with Pi-Ener-lite

The first step is to connect the board to the Raspberry Pi Zero via the pogo pins. Then install the drivers for the CW2015 and DS1307. Finally, write a simple Python script to read voltage and time. The project board includes ready-to-use examples.

If you want a more powerful system, you can pair Pi-Ener-lite with a Raspberry Pi 5. In that case, you must adapt the power supply, because the Pi 5 requires more current. For the Pi Zero, the solution works perfectly as is. The project is designed to be simple, compact, and reliable.

In conclusion, Pi-Ener-lite is a well-designed UPS with quality components and clear documentation. The ability to print a 3D case makes it even more versatile. If you’re looking for a backup power supply for your Raspberry Pi Zero, this project deserves attention.

The post Pi-Ener-lite: Compact UPS with Fuel Gauge and RTC for Raspberry Pi Zero appeared first on Open Electronics.

Pi-Ener-lite is a compact UPS power supply designed by ACE design studio for the Raspberry Pi Zero. It connects to the board via 7 spring-loaded pogo pins, which handle both power delivery and data reading. The project integrates an 18650 battery, a CW2015 fuel gauge chip, and a DS1307 RTC chip, offering a complete uninterruptible power supply in a small footprint.

Operation is simple and reliable. When external power is lost, the system automatically switches to battery power. It also supports simultaneous charging and discharging, so you can use the Raspberry Pi Zero while the battery recharges. The whole setup is protected against overcharge, over-discharge, overcurrent, and short circuits.

Battery measurement and RTC

The CW2015 fuel gauge chip measures battery voltage and remaining capacity with ±2% accuracy. The DS1307 RTC chip, powered by a CR1220 coin cell, keeps time even when the main battery is removed. This combination makes Pi-Ener-lite a truly complete UPS for applications that require operational continuity.

Fuel gauge and RTC data are read over I2C, so you can access them easily from Python. The project includes Python examples and detailed documentation. An optional open-source 3D-printable case protects the entire system. Total cost is around $35.

Why choose Pi-Ener-lite

Pi-Ener-lite is a compact UPS specifically for the Pi Zero. Unlike other solutions, it leaves the GPIO connector free, so you can attach other modules without issues. It also adds battery measurement and an RTC, two features often missing from DIY UPS builds. The open-source 3D-printable case adds versatility.

The project is designed for those who want a reliable backup power supply without taking up space. The board connects in seconds thanks to the spring-loaded pogo pins. The CW2015 fuel gauge lets you monitor remaining charge precisely, avoiding sudden shutdowns. If you need a professional solution for your Pi Zero, this project fits the bill.

• Connection via 7 spring-loaded pogo pins, no soldering
• 18650 battery with CW2015 fuel gauge for charge monitoring
• DS1307 RTC with CR1220 battery to keep time
• Protection against overcharge, over-discharge, overcurrent, and short circuits
• Open-source 3D-printable case

To build the project, you need an 18650 battery and a CR1220 coin cell. The rest of the components are already mounted on the board. If you want to power the system from a higher voltage, you can use a 12V DC-DC step-up converter to adapt the input. Alternatively, for industrial applications, consider a DC-DC converter with 36-48V input and 24V output.

Getting started with Pi-Ener-lite

The first step is to connect the board to the Raspberry Pi Zero via the pogo pins. Then install the drivers for the CW2015 and DS1307. Finally, write a simple Python script to read voltage and time. The project board includes ready-to-use examples.

If you want a more powerful system, you can pair Pi-Ener-lite with a Raspberry Pi 5. In that case, you must adapt the power supply, because the Pi 5 requires more current. For the Pi Zero, the solution works perfectly as is. The project is designed to be simple, compact, and reliable.

In conclusion, Pi-Ener-lite is a well-designed UPS with quality components and clear documentation. The ability to print a 3D case makes it even more versatile. If you’re looking for a backup power supply for your Raspberry Pi Zero, this project deserves attention.

The post Pi-Ener-lite: Compact UPS with Fuel Gauge and RTC for Raspberry Pi Zero appeared first on Open Electronics.

Pi-Ener-lite is a compact UPS for Raspberry Pi Zero with a CW2015 fuel gauge, DS1307 RTC, and 18650 battery support, all connected via spring-loaded pogo pins.

Electronics will make up 50% to 55% of a car’s total manufacturing cost by 2030, growing significantly from 30% to 35% in 2020, creating a growth opportunity for Indian automotive component manufacturers in high-value electronic systems, according to a recent report by the Boston Consulting Group (BCG) and the Automotive Component Manufacturers Association of India (ACMA).

As per the report, increasing adoption of ADAS, infotainment, connected vehicle technologies, sensors, and ECUs in both ICE and EV vehicles are driving higher content of electronics.

However, India’s electrical and electronics segment was expected to be around 12% of domestic component supply in FY2025, highlighting significant scope for localization. Indian suppliers could capture a share of this emerging value pool, while also developing new capabilities in automotive electronics and other associated technologies.

Some technologies such as sensors, Electronic Control Units (ECUs), power electronics, connectivity systems, and Battery Management Systems (BMS) are gaining more consumer attraction as cars evolve into software-defined and highly connected products.

To capture this localisation opportunity, Indian component manufacturers need to move beyond traditional mechanical and manufacturing capabilities. They need to invest more in engineering, research and development, electronics design, software, testing, and technology development to compete in advanced technology that can be easily adopted by consumer mature automotive supply chains.

The post ​Automotive Electronics Could Account for 50–55% of Car Cost by 2030, Enhancing Localisation Opportunities appeared first on ELE Times.

The defence minister, Rajnath Singh, has authorized the transfer of technologies, including conventional missile systems developed by DRDO, to eligible Indian defence manufacturers to set up indigenous production. In this process, mature and proven missile technologies are being moved from development to industrial-level mass production. The manufacturers will need to have applicable technical qualifications, certification levels, and regulatory requirements in place.

The scope for wider participation in the missile production chain would occur to some extent also due to technology transfer, where state-owned manufacturers, private firms, MSMEs & specialized manufacturers could develop expertise and participate in components and sub-components, electronics, propellants, guidance systems and associated mechanisms, launch systems and integration with greater depth.

There is scope for increased industrial involvement, which could bring about a higher level of domestic production and value addition, thereby lowering defence imports reliance. Increased industrial involvement could enable DRDO labs to focus more on research in newer and advanced technologies, while existing and developed systems may be produced industrially. A drastic policy shift, as it marks a change in treating private Indian companies as long-term technology and production partners in defence manufacturing. Its success hinges on technological absorption capability, quality testing procedures, test facilities, and orders.

The post India Approves Industry Production of DRDO-Developed Missile Systems appeared first on ELE Times.