Backend
EMT Modeling and Coordinated Mode-Transition Ride-Through Control of Modern Data Centers
arXiv cs.SY0 views
arXiv:2611.08614v1 Announce Type: new Abstract: Large data centers are emerging as power-electronic loads whose response to grid voltage disturbances can affect bulk-system stability. This paper presents the composition and control characteristics of a proprietary electromagnetic transient (EMT) model of a modern data center comprising an uninterruptible power supply (UPS) with battery energy storage, induction-motor cooling loads, a computer room air handler (CRAH) driven by a variable-frequency drive (VFD), and an aggregated server load. A voltage-based state machine coordinates three aspects of the facility response: the UPS operating mode (eco, double conversion, or battery), the supply path of the CRAH, and a ramped reconnection of the grid-side UPS converter after the disturbance clears. A 100 MW facility is implemented in PSCAD/EMTDC and benchmarked against the PSSE PERC1 aggregate data center model under a symmetrical three-phase fault and low- and high-voltage ride-through (LVRT/HVRT) events. The two models agree closely in their voltage and active-power trajectories, while the EMT model also resolves the converter and motor-reacceleration transients that the phasor-domain model cannot.
Source:https://arxiv.org/abs/2611.08614PreviousTraining-Free Generative Sampling via Moment-Matched Score SmoothingNextMulti-objective Electric Vehicle Charging Strategies at Energy Hubs with Justice-informed Profit Distribution among Users
Related posts

Dans osFoundry, chaque agent IA a un département et un rôle, et vous n'avez plus qu'à vérifier et approuver
0dev.to AI

What Cursor Live Apps Handles and Where a Local Setup Still Wins
0dev.to AI

I Ran a Real Internal Tool Through Cursor Live Apps. Here Is the Part That Actually Helped
0dev.to AI

An agent that stops paying for data it already learned was useless
0dev.to AI
Karaoke for songs nobody has sung before: what broke, and what we learned
0dev.to AI
I priced transactional email at 10k, 50k and 200k a month. The recommended plan is often the wrong one
0dev.to AWS