Backend
An Enhanced Submodule for Modular Multilevel Converters With DC Fault-Clearing Capability
arXiv eess.SY0 views
arXiv:2606.22469v2 Announce Type: replace Abstract: Modular multilevel converter (MMC) has been successfully applied in various power electronic systems owing to its high efficiency, scalability, and superior output performance. Although the half-bridge submodule (HBSM) is widely used in MMCs for its structural simplicity, it is incapable of handling direct-current (DC) short-circuit faults. The diode-clamp submodule (DCSM) addresses this limitation by providing DC fault ride-through capability. However, because its two identical capacitors are connected in series, the equivalent capacitance is halved. To overcome this drawback, an enhanced SM is proposed in this paper. For the same energy storage capacity, the proposed SM reduces the total required capacitance by 75% compared with the DCSM. In addition, the proposed SM requires one fewer diode than the DCSM, thereby lowering the overall MMC capital cost. The topology and the operating modes of the proposed SM are described in detail, and its functionality is experimentally validated. The results demonstrate that the proposed SM can suppress DC fault currents and restore normal operation without additional external protection devices.
Source:https://arxiv.org/abs/2606.22469PreviousA Realistic Discrete Event Simulation model for Ambulance Location and Deployment within a regional Emergency Medical ServiceNextVoltage Sensitivity-Based Fair Allocation of Operating Envelopes in Distribution Networks
Related posts

284B on 64GB RAM: We Read the Small Print Before Downloading 56 GiB
0dev.to OpenSource
LNbits creators call for immediate shutdown of systems due to attacks
0dev.to OpenSource
Java serialization filters need an allowlist first-run process
0dev.to Java
AI Coding Agents Are Changing Software Engineering. Is Your Architecture Ready?
0dev.to Java
Don't let the model write SQL: designing an MCP server around a semantic layer
0dev.to TypeScript

Tauri 2: Building a Reliable Desktop App — Why the Rust Host Should Own the Lifecycle
0dev.to Rust