Considerations for ground-fault protection for low-voltage variable-frequency drive circuits supplied by high-resistance-grounded power-distribution systems
Bibliographic record
Abstract
Many low-voltage (LV) adjustable speed drives (ASD's) have a built-in ground-fault function that is not capable of detecting a low-level ground fault and may require the use of a suitable supplemental protection relay for reliable detection. While high resistance grounding (HRG) has become the norm, over recent decades, in many industrial facilities the surge in application of ASD's has challenged designers and end users to manage the attendant risks associated with achieving the intended safety and reliability of LV HRG systems, while managing the inevitable growth of loads that incorporate high-speed electronic switching equipment. Using a zero-sequence current transformer (ZSCT), connected to a ground-overcurrent relay, to detect small values of fault current in ASD circuits is accepted as a reliable approach; but where to locate the CT, upstream or downstream of the drive, is a matter of some debate. This paper reports the unsettling discovery in an industrial installation that the ground-fault-protection of low-voltage ASD's was incompatible with the HRG systems, discusses appropriate HRG design considerations, describes the selection of a retrofit- and new-installation solution, and offers a suggestion for the optimal ZSCT location.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.008 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".