Scope of this technical record
Use this record when a DCS800 D5-D7 has dead or unstable control electronics and SDCS-POW-4 may be the supply boundary before SDCS-CON-4 is judged.
Auxiliary supply and board-chain checks require qualified personnel and safe isolation. Do not probe or remove the board without verified safe state and connector documentation.
SDCS-POW-4 evidence route
Supply-rail evidence comes before CON board replacement.
SDCS-POW-4 starts the D5-D7 board-chain route
If the DCS800 control section is dead or resetting, the first board-chain question is whether SDCS-POW-4 is receiving the correct auxiliary input and whether its downstream load is credible. A failed or overloaded supply route can make SDCS-CON-4 appear to be the problem.
The service evidence should capture auxiliary input, board label, connector condition, visible stress and whether the downstream boards recover when the load path is separated by a qualified procedure.
Field record checklist
- SDCS-POW-4 label
- Auxiliary input
- Connector photos
- Visible stress
- Downstream loading
- Reset behavior
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
OEM basis for DCS800 safety, FieldAck / field-related fault context and DCS800 firmware diagnostic boundaries.
OEM basis for SDCS-CON-4, SDCS-POW-4, SDCS-PIN board-chain and D1-D7 converter hardware context.
OEM service context for SDCS-CON-4, board replacement and service procedures.
Public documentation context for DCSLink use with field exciters and communication-related service evidence.
Linked circuit records
Routes D5-D7 electronics evidence from auxiliary input through SDCS-POW-4, SDCS-CON-4, SDCS-PIN-51 and the measurement/firing interface before a control-board or measurement-board decision is made.
Shows how the DCS800 D5-D7 board chain should be documented before classifying a case as control-board, power-supply-board, measurement-interface or downstream firing evidence.
Turn this record into a qualified service request
A repair decision is much more reliable when the request includes the exact identity of the drive, the first fault evidence and the machine condition when the symptom appeared.
- Complete drive type code / MLFB or nameplate model
- Fault code, fault value and first event before reset
- When the event appears: power-up, enable, ramp, run, decel or stop
- Motor/cable connected or isolated during the symptom
- Visible board, option-card, module and connector identifiers
- Previous repair history, replacement parts and repeat-failure pattern