Feed aggregator

Heya everyone! I'm Berry a cutesy trans gal! and I created a simple galvanic electrolysis machine from scratch ✨ It runs on a 5V USB power supply (smartphone/power bank/usb brick) , steps up to 30V, and limits current to a safe range (0.13–1.13mA). The total cost of this final interation works out around to roughly less than ₹600 or under $7 Quick specs :3 • Power: 5V USB → XL6009 → 30V • Current range: 0.13–1.13mA (I usually use 0.4–0.6mA) • It uses an LM324 , two 2N2222 , a few resistors, capacitors and two pots! • if built on breadboard then no soldering required Made from really few electronic components ✨ You can check out the whole document about it with the link here https://drive.google.com/drive/folders/1Q0zdHmhQ3L9I2UA0SnqAUSbfd it includes , schematic, parts list, build guide and more!! I also diy-ed the probe holder , and ermm the needle! but that's another thing on itself and not something I would recommend but yeah! I do have a design for a diy probe holder for commercial needles though if anyone is interested in that! If anyone has any questions then feel free to ask them 🫶✨ Edit:- yes i've tried it on myself!! And treated 65+ follicles in my second time using the machine on myself \^\^ r/diyelectrolysis https://cdn.imgchest.com/files/597c77d60eee.jpg [Schematic](https://cdn.imgchest.com/files/3bd2baf37d40.jpg) submitted by /u/BlueberryCultural361 [link] [comments]

Олександр Чорний (05.12.1989 – 13.03.2022) kpi сб, 09/12/2026 - 21:04

💎 Набір до команди «Формула Студент КПІ» kpi сб, 09/12/2026 - 20:49

submitted by /u/AutoModerator
[link] [comments]

submitted by /u/Curious_Deal5981 [link] [comments]

submitted by /u/Linker3000 [link] [comments]

submitted by /u/m4rkw [link] [comments]

CVD Equipment Corp (CVDE) of Central Islip, NY, USA (a designer and maker of chemical vapor deposition, thermal processing, physical vapor transport, gas and chemical delivery control systems, and other equipment and process solutions for developing and manufacturing materials and coatings) has announced a restructuring plan and leadership transition, following a thorough evaluation of strategic alternatives for its CVD equipment business by its board of directors...

Доповідь ректора КПІ ім. Ігоря Сікорського Анатолія Мельниченка на сесії професорсько-викладацького складу 2026 Інформація КП пт, 09/11/2026 - 17:00

Hey guys! I got into electronics and computers during the pandemic, but could not continue it further due to school work (and being a broke 14yo lol). Finally 6 years later I managed to save up and get myself some components to put something together that felt like an actual project. I will be happy to get any feedback! Github link for details submitted by /u/OjasZ [link] [comments]

Reporting the results of its Flight-1 ‘Mission Asimov’, Washington DC-based Besxar (which is developing the manufacturing of advanced semiconductor materials in space) says that, on 5 July, two of its ‘Clipper-class’ canisters flew from Space Launch Complex 40 (SLC-40) at Cape Canaveral Space Force Station in Florida aboard a SpaceX Falcon 9 first-stage booster and were recovered intact after the booster returned to land...

Goldilocks and the Three Bears (and their porridge, beds and chairs) have got nothing on this high voltage design challenge.

Sometimes a client gets into areas of technology that go way over my head, but I manage to pick up a snippet here or there. This is one such case.

The requirement was to create an electron beam for which the beam energy would be precisely known. The measurement technique is diagrammed as follows (Figure 1).

Figure 1 Fairy tales and their application to electron beam energy (if-necessary reference)

Two curved metal channels were arranged in a circular path through which the electron beam was to be directed. Equal but opposite polarity high voltages would be applied as shown. When an electron source was aimed into one end of this structure, the path of that beam, i.e., the beam’s radius of curvature, would vary as a function of the applied high voltages.

By dint of equations that left me in the dust, when the high voltages and beam energy were a proper match, the electron beam would emerge at the output end where it would go on to serve its intended purpose. The beam’s radius of curvature under the electrostatic field would be just right, and the beam energy would be precisely known. If there was a mismatch, the electron beam would impinge instead on one metal plate or the other and not appear at the output.

The high voltage and voltage precision requirements for this thing were quite demanding. The dual power supply we made for this setup went from zero to 25 kV on each side and had a room temperature versus voltage temperature coefficient on the order of 1 ppm per °C.

Happily, it worked very well.

John Dunn is an electronics consultant and a graduate of The Polytechnic Institute of Brooklyn (BSEE) and of New York University (MSEE).

Related Content

• Researchers develop electron-based Airy Beam

The post Electron beam energy appeared first on EDN.

📰 Газета "Київський політехнік" № 29-30 за 2026 (.pdf) Інформація КП пт, 09/11/2026 - 13:56

As systems grow, the knowledge needed to safely change them becomes harder to retrieve quickly, even when the design itself is sound. Models increasingly encode not just algorithms, but also assumptions, trade-offs, and system-level intent that accumulate over time. As ownership changes hands, understanding that intent becomes the bottleneck.

Consider a common engineering handoff: you are new to an existing project and are asked to update the braking system to support a heavier vehicle variant. The system works. The architecture looks intentional. But you were not part of the original design decisions, and before touching anything, you need to understand what is safe to change and why.

Compared to reading thousands of lines of code, being given a model offers a clear advantage. It exposes structure, makes data flow visible, and captures behavior in a form engineers can reason more quickly. For years, this has been a core strength of model-based design.

However, this advantage is now under pressure. Today’s software-defined systems are larger, more interconnected, and built across distributed teams, suppliers, and release cycles. Even with a well-structured model, engineers still need to reconstruct why signals flow a certain way, which subsystems own specific behaviors, which parameters are safe to modify, and where hidden constraints exist.

So, when that context is hard to recover, teams slow down. Review cycles expand. The risk of validation failures or schedule delays increases. This is not because the design is wrong, but because its underlying rationale is difficult to access quickly. Over time, this becomes an engineering scalability problem: critical knowledge lives inside the design but becomes harder to retrieve as systems grow more complex.

The challenge is no longer simply one of scalability, but of how engineers recover that context quickly enough to make the right change. This is the gap that shows up most clearly in engineering handoffs.

Walkthrough: Recover context in the ABS braking model

To see how this challenge appears in practice, consider an anti-lock braking system (ABS) model. The system runs, but the engineer has been asked to update the braking system to support a heavier vehicle variant. Before making that change, engineers first need to understand where the wheel-speed behavior lives and how it interacts with the rest of the design.

Figure 1 ABS demo regulating wheel slip (Desired Relative Slip) via a bang-bang controller (Controller) drives vehicle/brake dynamics (Vehicle Dynamics) with visualization (Visualization). Source: MathWorks

This opens sldemo_absbrake, a model that simulates vehicle dynamics under braking with a bang-bang controller. The example is small enough to follow end to end, but it raises the same questions that appears in production handoffs: What are the major pieces? Where does the behaviour live? Which blocks should be inspected before changing it?

Get the big picture

Start by building a system-level understanding of the model. Before inspecting individual blocks, click “Simulink Copilot Chat” on the “Simulation” tab of the toolstrip, and type: Give me an overview of this model.

Simulink Copilot returns a structured breakdown of the four top-level subsystems (Controller, Vehicle Dynamics, Visualization, and More Info), the high-level signal flow from slip reference to controller to braking dynamics to visualization, and the control strategy: bang-bang control on the slip error. Every block name in the response is a clickable hyperlink, so the explanation remains tied to the model canvas rather than floating apart from it.

Figure 2 Simulink Copilot generates a grounded overview of the open model, with hyperlinks to each subsystem and block. Source: MathWorks

Instead of digging through the model block by block, a working mental map is established. The model’s behaviour, major connections, and the part of the design worth inspecting before making a change are now clear.

Drill into a subsystem

The overview points to “Vehicle Dynamics” as the subsystem that handles braking physics. If a change could affect wheel motion, stopping distance, or slip, that is the area to drill down next. Instead of opening the subsystem and reading every block manually, right-click the “Vehicle Dynamics” block on the canvas and choose “Explain with Simulink Copilot” in the Simulink context menu.

Figure 3 Right-click any block and choose “Explain with Simulink Copilot” for a contextual explanation without typing a prompt. Source: MathWorks

Simulink Copilot generates a contextual explanation of the subsystem: its purpose, its inputs and outputs, and the internal structure that connects tire forces, brake pressure, wheel speed, vehicle speed, and relative slip. This is not a generic block description. It explains how Vehicle Dynamics is connected to this specific design, which is the context needed before deciding what to modify.

Find where a feature lives

Now suppose the design change requires extending or reviewing the wheel-speed calculation. There is no longer a need to start at the top of the model or guess which subsystem owns that behaviour. Ask the question directly: What components handle wheel-speed calculation?

Figure 4 Simulink Copilot identifies the specific blocks that implement wheel-speed calculation, each hyperlinked for one-click navigation. Source: MathWorks

Simulink Copilot returns the specific blocks involved, including sldemo_wheelspeed_absbrake, the integrator that computes wheel angular velocity, and the gain block that converts angular velocity to wheel speed. Each result is hyperlinked to a model element, enabling navigation from a design question to the implementation detail.

What this looks like in practice

Generate an overview, drill down into subsystems, and perform a targeted search: this becomes a repeatable three-step pattern for working with an inherited Simulink model. Start broad enough to understand the architecture, narrow the conversation around the subsystem that owns the behaviour, and then ask targeted questions that lead to the blocks that may need modification.

From there, follow-up questions can move from orientation to change impact:

• How does the bang-bang control strategy work within the context of this model?
• What outputs are visualized during simulation, and how do they reflect braking performance?
• What adjustments can be made to controller parameters to enhance braking response time?

Each response references the model itself: block names, signal paths, subsystem boundaries, and parameter values. The conversation builds on itself, so by the time the first edit is made, the process is no longer based on a disconnected search result. Instead, it provides a model-specific explanation of what the design does, how the relevant pieces fit together, and why they matter to the requested change.

Tips for better handoff questions

• Be specific about scope. “Explain the braking control logic” works better than “explain this model” once the relevant part of the inherited design has been identified.
• State the goal, not just the question. “I need to extend the wheel-speed calculation” gives Simulink Copilot context to focus on the behaviour that is changing.
• Reference blocks by name when possible. “Explain the Sum block labelled slip_error” is more useful than “explain the Sum block” because it anchors the question in the design.
• Use Deeper Insights for questions that require sophisticated reasoning. Reserve the more thorough analysis for decisions about design intent, subsystem responsibilities, or change impact.

Now return to the engineer at the start: you inherited a model, and you were asked to update the braking system to support a heavier vehicle variant, and the risk was not that the model lacked structure. The risk was acting before understanding the intent behind that structure.

A grounded conversation changes that first hour. The architecture can be mapped, the subsystem that owns the behaviour can be inspected, and the relevant blocks can be identified before making the change. That does not replace engineering judgment or validation, but it provides a faster, more defensible way to inform decisions for the next design change.

Amal Jayarajan Phillai is a product manager at MathWorks.

Related Content

• Accelerating development with model-based design
• Model-based design and early verification aid designers
• Early verification and validation using model-based design
• Understanding the specific use cases for Simulink and Stateflow
• Plan strategies for adopting Model-Based Design for embedded applications

The post You just Inherited a Simulink model you have never seen before. Now what? appeared first on EDN.

У КПІ ім. Ігоря Сікорського створено унікальну дослідницьку інфраструктуру TRIUMPH! kpi пт, 09/11/2026 - 12:21

India’s premier video security brand PRAMA showcased advanced security products and smart security solutions for the MSME sector at the first edition of Bharatiya Vyapar Mahotsav (BVM) from August 12-15, 2026 at Bharat Mandapam, New Delhi. At the exhibition, traders, MSMEs, manufacturers, innovators, businesses and other industry stakeholders came together to showcase their products, services, and solutions. The inaugural event was attended by Union Minister for Commerce & Industry Piyush Goyal, Minister of State for Commerce and Industry Jitin Prasada and former Union Minister Smriti Irani along with leaders and representatives from Confederation of All India Traders (CAIT), Swadeshi Jagran Manch and other organisations.

PRAMA management representative said, “The Bharatiya Vyapar Mahostav is a great platform for Pan India Trade bodies and entrepreneurs of MSME sector. The Indian security market is poised for a new growth phase due to the exponential growth of Micro, Small and Medium Enterprises (MSME) sector. MSME sector is the backbone of India’s economy. We are glad to serve the needs of India’s Medium and Small enterprises. We find Bharatiya Vyapar Mahotsav (BVM) event, a highly valuable exhibition platform to connect with the key stakeholders and ecosystem partners. We showcased the latest products and solutions in this expo. We appreciate CAIT’s proactive role in organizing Bharatiya Vyapar Mahotsav event to spur innovation and engagement with key industry stakeholders.”

He further elaborated, “PRAMA, being India’s premier indigenous security brand holds, great significance. The spectacular growth that India security industry has achieved, PRAMA’s evolution as a leading security brand is the manifestation of Indian spirit and ingenuity. We are taking indigenous manufacturing to the next level. We are here to offer best-in-class products with cutting edge technologies that can deliver solutions as per the MSME Sector’s evolving requirements as per the business cases and application scenarios.”

The elaborately designed spacious PRAMA booth was center of attraction for the trade and industry specific visitors. PRAMA booth showcased the latest products and MSME sector’s solutions, including Ai technology, Interactive Display Panel, Perimeter and Defence Solution, Ranginview IP Series with Built-in MiC, Safe City Solution, Transportation Solution, Mobile enforcement Solution, Networking and Transmission and many more.

PRAMA booth displayed the latest video security products, including Ai Solution. PRAMA’s AiSense technology, powered by advanced AI Algorithms, takes surveillance to the next level. This technology intelligently distinguishes people and vehicles from other moving objects, reducing false alarm caused by animals or environmental factors. With AiSense Technology one can focus on the real threats, optimize resources and build on an intelligent security system. The AI Sense Technology can be very helpful in the various application scenarios in the retail segment for the MSME sector.

PRAMA’s Interactive Display Panel (IDP) was displayed at the booth, it is an all-in-one large display panel which integrates features of a computer, whiteboard, and projector, all in one device, making it a versatile tool for education, corporate training and business video conferencing scenarios. It is a great communication and training tool for the MSME sector.

PRAMA’s booth showcased Safe City Solution, which provides sound, stable and reliable public security. It features a suite of advanced technologies and security subsystems to safeguard industries, centralise operations, and integrate security platforms. These integrated technologies enable rapid and effective responses to security needs and events.

Bharatiya Vyapar Mahotsav (BVM) 2026 is India’s largest Make-In-India multi-sectoral trade expo, designed to bring together India’s diverse business ecosystem under one roof, connecting traders, MSMEs, manufacturers, industry leaders, institutions, and policymakers from across the country. The mega event was organized by Confederation of All India Traders (CAIT) & ITPO.

The Bharatiya Vyapar Mahotsav (BVM), 2026 was a four day event, which was successfully concluded. The event helped to create awareness about the latest innovations and products in the myriad trade segments. The discussions and deliberations were done with various key stakeholders on the core trade and MSME issues. The event was attended by the key trade and business professionals, Government officials and key stakeholders from the Trade and MSME sectors.

The post PRAMA Showcases Smart Security Solutions for MSMEs at Bharatiya Vyapar Mahotsav 2026 appeared first on ELE Times.

Midsummer AB of Järfälla, near Stockholm, Sweden and Indonesian technology industrial company PT Metalogika Rekayasa Sistem have signed a binding investment and industrialization framework agreement for the establishment of a manufacturing platform in Indonesia for Midsummer’s lightweight, flexible copper indium gallium diselenide (CIGS) thin-film solar cell and photovoltaic module technology...

GSAS Micro Systems inaugurated its new manufacturing and expanded R&D facility in Doddaballapur, Bengaluru Rural, marking a significant step in the company’s journey from embedded engineering and technology integration toward a stronger in-house product development and manufacturing footprint in Karnataka.

Located in the Doddaballapur 3rd Phase Industrial Area, the new facility brings GSAS’s product development, engineering, manufacturing and project activities together under one roof. It will serve as a working hub for hardware manufacturing, assembly, integration, quality testing, R&D and new-product development.

The expansion comes as Karnataka continues to strengthen its electronics and semiconductor ecosystem, building on its established capabilities in electronic design and semiconductor R&D. According to the Karnataka Digital Economy Mission (KDEM), the state contributes 10% of India’s electronics output and nearly 40% of the country’s electronic design output. Karnataka also accounts for more than 22% of India’s electronics exports and hosts more than 100 fabless semiconductor design companies.

For GSAS, the Doddaballapur facility is both a business milestone and the culmination of a much older ambition. The company’s founder has carried the vision of building a dedicated electronics manufacturing base since the 1990s. Bringing that ambition to life in Karnataka gives the company a permanent home for developing and building more of its own products while expanding the engineering infrastructure available for customer-specific programmes.

“This is a deeply personal milestone for me. I have wanted to build a dedicated electronics manufacturing home since the 1990s. Karnataka gave our generation of electronics entrepreneurs the engineering talent, industry networks and ecosystem to build companies here. With this facility, we now have a place where our team can take more ideas from engineering and R&D into real products and manufacturing. For us, this is not the end of a dream; it is the foundation for what GSAS wants to build next.” said Satya Gopalam, Chairman and Managing Director , GSAS Micro Systems.

“Our engineering work has been moving deeper into the FPGA space, with vision AI and edge AI projects, board bring-up support for automotive programmes, and PCBA test automation. This new 12,000 square foot facility gives that work a manufacturing home: we will build the new Genesis series here, essentially embedded development kits and FPGA development kits, manufactured and assembled on site, alongside test automation and integration work for the automotive, aerospace and satellite space. We have been working towards this for the last few years, and I am proud to see it finally established. If you are curious, reach out; we are happy to give you a tour of the facility.” said Anvesh Gopalam, Executive Director , GSAS Micro Systems.

The post GSAS Micro Systems Expands Manufacturing and R&D Operations with New Doddaballapur Facility appeared first on ELE Times.

Col Sandeep Rao (Retd) is a veteran Indian Army Artillery officer with more than two decades of military service. His career includes experience in combat operations, counter-terrorism and high-altitude operations along the Line of Control. An alumnus of the National Defence Academy and Don Bosco High School, Matunga, Mumbai, he brings military leadership and field experience to his role as Advisor at Tirupati Forge.

Within India’s defence acquisition framework, Col Rao served as programme coordinator for the country’s first indigenously designed and developed 155 mm advanced artillery gun system, managing requirement formulation, trials, and execution. His domain expertise includes artillery platforms, counter-UAS systems, defence robotics, ammunition manufacturing, and Defence Acquisition Procedure (DAP 2020) implementation.

Following his military service, Col Rao acts as a strategic advisor to defence manufacturers, technology enterprises, and investment platforms. He guides companies on market positioning, technology transfer, and institutional procurement pathways while advising defence-tech start-ups on investor readiness and government acquisition. As a technology scout and strategy consultant, he collaborates across the Ministry of Defence, DRDO, and industry channels to bridge operational military requirements with commercial delivery and advance defence indigenisation.

The post Col Sandeep Rao (Retd): From Indian Army Artillery to Defence Industry Leadership appeared first on ELE Times.