Scope of this technical record
Use this record when SDCS-CON-4 is being considered for repair, replacement, donor sourcing or compatibility review in a DCS800 FieldAck, electronics-supply or measurement/interface case.
Do not remove or substitute SDCS-CON-4 until supply evidence, connector positions and parameter/firmware context have been preserved according to service procedures.
SDCS-CON-4 evidence route
Control-board replacement is not the first assumption.
SDCS-CON-4 is a decision point, not the first assumption
SDCS-CON-4 controls and interprets the DCS800 system, but an F521 message or dead control section does not prove this board is the failed part. Supply state, field architecture and interface-board evidence should be documented first.
A useful board request includes the installed board label, converter type code, frame, status display, supply relationship, X12/X13 interface context, field-exciter arrangement and any prior firmware or board replacement history.
Field record checklist
- SDCS-CON-4 label
- Status display
- Supply evidence
- X12 / X13 context
- Field architecture
- Parameters preserved
- Prior firmware/board work
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
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.
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.
Maps F521 FieldAck from the selected motor and field circuit through internal FEX or external DCF field exciter evidence, communication and control acknowledgement.
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