Commissioning a DeltaV DCS Cabinet: Power, I/O, Relays

When part of a DeltaV cabinet drops and the controllers keep running, the fault is almost always on one of the two DC rails rather than in the controller pair. The cabinet carries redundancy at the controller, network, and system-power-supply level, but the 24 VDC distribution behind those supplies is segmented, not mirrored: one bulk supply feeds one system power supply plus a single carrier, the other feeds the second system power supply, the remaining carriers, and the discrete-output interposing circuit. Read the symptom against that split first, then trace 120 VAC to 24 VDC to 12 VDC in order.

Reading the Symptom Against the Power Split

The term "system power supply" here means P1 and P2, the modules that take 24 VDC from the bulk supplies and produce the 12 VDC bus the controllers and carrier-mounted cards run on. The term "bulk supply" means PWR1 and PWR2, the 120 VAC to 24 VDC converters downstream of the circuit breaker. Confusing the two costs an hour of meter time, because both are called "the power supply" in most panel drawings.

Symptom	Most likely cause	First measurement
Entire cabinet dead, both controllers dark	Circuit breaker CB tripped or upstream 120 VAC lost	120 VAC across CB output terminals
Carrier 3 cards dark, all other carriers healthy	PWR1 24 VDC branch lost; carrier 3 is fed from PWR1	24 VDC at PWR1 output
All carriers except carrier 3 dark; DO field devices dropped	PWR2 24 VDC branch lost	24 VDC at PWR2 output
One controller offline, its partner takes over	P1 or P2 12 VDC output failed, or controller module fault	12 VDC at the failed controller's supply
DO cards report healthy, commands issued, no field device motion	Fuse F open in the DO intermediate circuit; relay coils unpowered	Voltage across fuse F holder
All AI channels on one card read 0 mA / bad quality	Loop power or field wiring open on that card's transmitters	Series current in the affected loop
Both network paths reported failed from the workstation	Switch AC feeds lost; the switches run on their own AC branch, not the 24 VDC rails	AC at each switch's supply

The asymmetric row — carrier 3 alive while the rest is dark, or the inverse — is the diagnostic fingerprint of this cabinet. A truly mirrored architecture cannot produce it.

Power Chain Mechanism: 120 VAC to 12 VDC

Line power enters through circuit breaker CB, which protects both bulk supplies and is the single point that de-energizes the DC side of the cabinet. PWR1 and PWR2 each convert 120 VAC to 24 VDC. That 24 VDC is the cabinet's working distribution voltage: it powers the system power supplies, it powers the carriers directly on the PWR2 branch, and it powers the DO intermediate circuit through fuse F.

Each system power supply then steps 24 VDC down to 12 VDC. Carriers distribute that 12 VDC to every module seated on them, so a card never sees field-level or bulk-supply voltage on its backplane side. Three distinct voltages therefore exist in the cabinet simultaneously — 120 VAC, 24 VDC, 12 VDC — and a meter reading taken at the wrong tier will look correct while the fault sits one tier away.

The branch assignment is the part that matters during a fault:

• PWR1 feeds system power supply P1 and carrier 3.
• PWR2 feeds system power supply P2, the remaining carriers, and the DO intermediate circuit power through fuse F.
• The two network switches have separate AC supplies and do not depend on either 24 VDC rail.

Losing PWR2 therefore removes most of the I/O and all AC-driven discrete outputs, while the controller pair may still be running on P1's 12 VDC. That combination — controllers healthy, I/O silent — is not a controller problem and should never be answered by swapping a controller.

Network Redundancy and the Two-Switch Path

The workstation carries primary and secondary ports for two separate Ethernet networks, and the cabinet carries one switch per network. Each controller connects to both: primary port to the primary switch, secondary port to the secondary switch, using Cat5e. The redundancy is path redundancy, not load sharing — traffic uses one path and fails over.

Two wiring errors defeat this. Patching both controller ports into the same switch produces a system that passes every functional test and then loses all communication when that switch fails. Cross-connecting the two switches to each other merges the networks into one broadcast domain and destroys the separation the redundancy depends on. Label the primary and secondary trunks at both ends and verify the port map physically before energizing, not from the drawing.

I/O Signal Path and Isolation

I/O modules are the interface between field devices and the controller, and they carry two jobs at once. The first is conversion: A/D converters in analog input cards turn the 4-20 mA field signal into the discrete value the controller reads; D/A converters in analog output cards turn a controller value back into 4-20 mA to drive a positioner or a variable-speed reference. The second job is isolation. Optical isolators separate high-level real-world signals from the low-level I/O bus, so a field-side surge or a miswired 120 VAC conductor damages one channel rather than propagating into the carrier and the controller.

Analog inputs carry every measured process variable — pressure, level, flow, temperature — as 4-20 mA. Where the transmitter has its own power source, use 4-wire AI channels so the field-side power is kept out of the card. Wiring a self-powered transmitter into a loop-powered channel back-feeds the card's loop supply; the symptom is a channel that reads high or erratic and eventually fails hard. Field wiring in this cabinet is 22 gauge, which is adequate for 4-20 mA and dry-contact discrete circuits and is not a power conductor. Do not reuse spare 22 AWG pairs for relay coil power or for any 120 VAC circuit.

DO Cards, Interposing Relays, and Fuse F

DeltaV DO cards in this configuration switch DC loads only. Any AC-powered field device — solenoid valve, motor starter coil, indicator — must be driven through an interposing relay. Coil power for that intermediate circuit comes from PWR2 through fuse F.

The failure mode to recognize: fuse F opens, all eight relay coils lose power, and every DO channel still reports healthy because the card sees a valid output circuit on its own terminals. Nothing in the DO diagnostics will point at the fuse. Check voltage across the fuse holder — a good fuse reads near 0 V with 24 VDC on both sides; an open fuse reads full rail voltage across it.

Connecting an AC device directly to a DO channel is the recurring wrong practice on this class of cabinet. It destroys the channel's output stage and can carry line potential onto the carrier, past the isolation the card was designed to provide.

Energizing Procedure

1. Confirm CB is open and both bulk supply outputs are disconnected or their output terminals isolated.
2. Verify 120 VAC at the CB line side; confirm the neutral and ground landing points before closing anything.
3. Close CB and measure PWR1 and PWR2 outputs independently at their terminals. Both must be at 24 VDC nominal before any module is seated.
4. Seat carriers and confirm 12 VDC at P1 and P2 outputs. Verify P1's output is present with PWR2 removed, and P2's with PWR1 removed, so the branch assignment is proven rather than assumed.
5. Install controllers C1 and C2, then the I/O cards by carrier position, matching the card type to the terminal block wiring already landed. Populate carrier 3 last so the PWR1 branch is proven under load separately.
6. Energize the two network switches from their own AC feeds. Confirm each switch is on a different feed.
7. Land the Cat5e trunks: workstation primary port to primary switch, workstation secondary to secondary switch, and each controller's primary and secondary ports to their matching switch.
8. Land field wiring last: 22 AWG to AI, AO, DI, and DO terminals, and the interposing relay coils to the fused DO intermediate circuit. Verify fuse F is installed and correctly rated before the first DO command.

Verification Checks

Run these in order and record the reading. Each check isolates one tier of the chain.

1. Check 1 — Line: measure at the CB output. Expect 120 VAC nominal, stable while the cabinet is loaded.
2. Check 2 — Bulk rails: measure PWR1 and PWR2 outputs separately. Expect 24 VDC on each with no more than a few hundred millivolts of sag between unloaded and fully loaded.
3. Check 3 — System supplies: measure P1 and P2 outputs. Expect 12 VDC on each; a reading near 24 VDC means the step-down stage is bypassed or the meter is on the input side.
4. Check 4 — Branch proof: remove the PWR1 input. Expect carrier 3 to drop while all other carriers stay powered. Restore, then remove PWR2 and expect the inverse. Anything else means the branch wiring does not match the schematic.
5. Check 5 — Fuse F: measure across the fuse holder with the DO circuit energized. Expect approximately 0 V across the fuse and 24 VDC to common on both sides.
6. Check 6 — Analog input span: inject a loop current with a calibrator on one channel per AI card. Expect the workstation value to track 0% at 4 mA and 100% at 20 mA; an offset at 4 mA points at scaling, a dead reading points at wiring or the wrong AI channel type.
7. Check 7 — Analog output span: command 0% and 100% on one AO channel and read loop current in series. Expect 4 mA and 20 mA respectively at the field device terminals, not just at the card.
8. Check 8 — Discrete output chain: command each DO channel and confirm the corresponding relay R_DO1_x picks up audibly, its contact goes to continuity, and the AC field device operates. A card LED alone is not proof.
9. Check 9 — Network failover: pull the primary Cat5e at the switch with the process idle. Expect both controllers to stay in communication over the secondary path and the workstation to report one path failed with zero controller integrity loss. Reinsert and repeat on the secondary path.

Recurring Pitfalls

Assuming full redundancy from a redundant nameplate is the first one. Two bulk supplies, two system supplies, and two controllers do not make the carrier distribution redundant; the branch split means a single bulk supply failure takes down a defined, non-trivial slice of I/O. Document which carrier sits on which branch and post it inside the cabinet door.

The second is testing failover with only one path removed at a time and never testing the other. A crossed primary/secondary pair passes the first test and fails the second, and the defect stays latent until a real switch failure.

The third is treating 22 AWG field wire as general-purpose panel wire. It belongs on 4-20 mA and dry-contact circuits and nowhere near coil or line power.

The fourth is replacing a controller for an I/O-wide outage. Before touching C1 or C2, take Check 2 and Check 3; a 12 VDC rail at zero volts explains the outage completely and a new controller will not.

Close the job by repeating Check 9 in both directions with the process running and confirming that neither controller logs a communication loss.

FAQ