Page review information
Edition covered
NFPA 79 / IEC 60204-1 (wiring-practice chapters); IEC 61000 series at overview level — NFPA 79:2024, IEC 60204-1:2016+AMD1:2021
Content status
Reviewed
Coverage
Coupling mechanisms, separation classes, coil suppression, shield/twisted-pair practice, and panel EMC layout; separation distances and filter selections are deliberately not tabulated — verify against vendor and cabling-standard tables
Last reviewed
August 2026
Primary reference
The official published standard — required for final decisions

Confirm the governing edition, jurisdiction, and project-specific requirements before applying anything on this page.

Safety. Perform all wiring work de-energized and verified, by qualified personnel, under your site’s LOTO procedures and the device manufacturer’s manual. This guide is educational reference material, not a work instruction.

Overview

Noise problems feel random, but the physics is small: a source (something switching current or voltage fast), a victim (something listening to small signals), and a coupling path between them. There are only four paths:

flowchart LR
    subgraph SRC["Sources"]
        VFD["VFD output cable<br/>(high dV/dt)"]
        COIL["Contactor / solenoid coils<br/>(inductive kick)"]
        WELD["Welders, starters<br/>(high dI/dt)"]
    end
    subgraph PATH["Coupling paths"]
        CAP["Capacitive"]
        IND["Inductive"]
        CI["Common impedance"]
        RAD["Radiated"]
    end
    subgraph VIC["Victims"]
        AN["Analog inputs, TC/RTD"]
        ENC["Encoders"]
        COM["Comms / networks"]
        SAF["Safety circuits"]
    end
    SRC --> PATH --> VIC

The strategy hierarchy — generally accepted practice, ordered by cost-effectiveness:

  1. Separate first. Distance and routing discipline are nearly free at design time and impossible to retrofit cheaply.
  2. Suppress and shield second. Kill noise at the source (coil suppressors, shielded motor cable) and armor the victims (twisted pair, shields).
  3. Filter third. Line filters, ferrites, and RC input filters treat what separation and shielding didn’t.
  4. Fix at the receiver last. Software debounce and averaging are legitimate final polish — never the first response to a wiring problem.

This guide owns the general EMC story for panels and field wiring. Drive-specific filtering and motor-cable detail live in the VFD wiring guide; the physics of shield landing lives in Grounding & Bonding.

Before You Start

Two inventories, made from the drawings before any tray or duct is routed:

Source inventory — everything that switches significant energy:

Victim inventory — everything that listens to small signals:

Also confirm the upstream decisions: enclosure zoning (where drives sit vs. where the PLC sits), tray and duct routes, and whether shielded VFD cable was specified. If those were decided badly, no amount of ferrite fixes it later.

Separation & Routing Classes

NFPA 79 Chapter 13 (wiring practices) and IEC 60204-1 Clause 13 both address routing, ducts, and segregation of circuits of different types and voltage classes — consult the current edition text for the specific provisions; this guide cites them at chapter level only.

On top of that, industry converged on a signal-class scheme — generally accepted practice, verify for your installation:

Class Contents Character
1 Analog, TC/RTD, encoder, comms Quietest, most sensitive
2 24 V DC discrete I/O, suppressed control Quiet
3 120/230 V AC control, unsuppressed coils Noisy
4 AC power, motor circuits, VFD output, braking resistor Noisiest

The rules of the scheme (all generally accepted practice — verify for your installation):

Unlike the conductor-sizing guides, there is no cst calculator for this section — separation is a routing decision, not a computation. The wire sizing walkthrough covers the ampacity side of the same drawings.

Power Wiring — Source Suppression

The cheapest noise to mitigate is the noise that never leaves the source.

Suppress every switched coil. Contactor and relay coils generate a large inductive voltage kick at every drop-out; unsuppressed, that kick couples into everything sharing the duct. Fit suppression directly at the coil (suppression at the far end of the wire leaves the whole wire radiating):

The flyback-diode caveat. A plain diode gives the gentlest suppression but the slowest coil decay — it measurably delays contactor drop-out, sometimes by tens of milliseconds. Where drop-out time is part of a safety function’s response-time budget (ISO 13849-1 / IEC 62061 assessments), a bare diode can quietly consume margin. Use a diode + zener, varistor, or RC suppressor on safety-related coils, and verify the measured response time with suppression fitted. Generally accepted practice — verify against your safety validation.

Solenoid valves get the same treatment as coils; large AC solenoids are notorious PLC-input chatter sources when unsuppressed.

VFDs are the dominant source in most plants, and their suppression toolkit — input reactors, EMC filters, dV/dt and sine filters, shielded symmetrical motor cable glanded at both ends — is vendor- and installation-specific. That material is owned by the VFD wiring guide; from this page’s perspective the rule is simply: treat the VFD output as Class 4 and keep everything else away from it.

Control / Signal Wiring — Victim Hardening

What survives separation and suppression is handled at the victim.

Grounding, Shielding & EMC — Panel-Level Practice

All items in this section are generally accepted practice — verify against your drive vendor’s EMC installation guide and your panel standard. The underlying grounding theory is in Grounding & Bonding.

Common Mistakes

  1. Analog and VFD output in the same duct. The classic. Reads fine at commissioning (drive not running), then process values wander whenever the drive loads up. Shows up as analog noise correlated with drive state — exactly the pattern in the intermittent I/O case study.
  2. Unsuppressed coils chattering PLC inputs. Every contactor drop-out fires a voltage kick into the parallel input wiring; inputs flicker for one scan, counters miscount, sequence logic takes phantom steps. Fix at the coil, not in software.
  3. Shield pigtails on drive and network cables. The shield is “connected” and the drawing is satisfied — but at high frequency the pigtail’s inductance makes the shield nearly useless. Shows up as noise problems that persist despite “everything being grounded.”
  4. Both-ends grounding of low-frequency analog screens across a ground-potential difference. The screen becomes a ground-loop conductor and injects 50/60 Hz hum into the measurement. Shows up as a steady offset or ripple that tracks plant load. (The nuance — why both-ends is right for high-frequency cables — is in Grounding & Bonding.)
  5. Software filters before wiring fixes. Averaging and debounce make the symptom disappear while the coupling path stays — and the same path later corrupts something a filter can’t hide (comms, safety inputs). Filter last, after the path is found and broken.
  6. Ferrites everywhere instead of finding the path. A bag of clamp-on ferrites sprinkled over every cable is diagnosis by superstition. One ferrite on the identified coupling path is engineering; twenty on unidentified cables is hope.
  7. Right-angle rule ignored “just for this one crossing.” A single long parallel detour of a Class 1 cable along a Class 4 route — added during a late change, absent from the drawings — routinely explains noise that appears only after a modification.

Verification Checks

Standards References

Trust Boundary — Engineering Judgment Required

This site is an independent educational reference for industrial automation standards. It paraphrases and organizes guidance in original language; it is not a substitute for the official published standards, professional engineering judgment, or legal review, and content has not been independently verified against current published editions.

Items marked Review pending await technical review against the identified edition. Items marked Planned have no reviewed source material behind them. Do not rely on this site for compliance determinations, safety-critical design decisions, or legal interpretation.