Descargue nuestro Catálogo de productos 2025 para obtener planos detallados y parámetros técnicos de todos los componentes de los equipos de conmutación.
Obtener catálogo Descargue nuestro Catálogo de productos 2025 para obtener planos detallados y parámetros técnicos de todos los componentes de los equipos de conmutación.
Obtener catálogo
VCB auxiliary contact allocation for SCADA is not a matter of simply counting spare NO and NC contacts. In a vacuum circuit breaker, auxiliary contacts may be tied to the operating mechanism, the breaker shaft, the trip indication circuit, the mechanical close pushbutton, plug status, truck interlocking, close blocking, or other selected functions. The correct allocation depends on the approved breaker wiring diagram, the selected accessory package, and the separation needed between SCADA indication, protection relay logic, and interlocking circuits.
For VCB projects, the safest approach is to treat every auxiliary contact as a functional signal with a defined source, timing expectation, duty, and destination. ABB and Schneider documentation both show that breaker auxiliary contacts are product-configuration specific and function-specific, so an allocation schedule should be confirmed against the manufacturer’s drawings before factory acceptance testing, site wiring, or commissioning.
A VCB normally has several parties competing for auxiliary contacts: SCADA needs remote open and closed indication, protection relays may need breaker status for logic or disturbance records, interlocking circuits may need permissive or blocking feedback, and local control circuits may already consume contacts inside the breaker scheme.
If these needs are not allocated deliberately, a project can end up with duplicated signals, missing feedback, nuisance alarms, or unsafe modifications to the close and trip circuits. The risk is higher when the breaker is withdrawable, motor charged, electrically operated, or supplied with optional interlocks and plug-status contacts.
The phrase “breaker auxiliary contact” can also hide important differences. ABB’s VD4X documentation distinguishes mechanism auxiliary switches, switch-shaft auxiliary switches, tripped-indication contacts, mechanical-close-pushbutton auxiliary switches, and optional interlocking contacts. That distinction matters because each contact type represents a different physical or electrical condition. A shaft-driven open/closed contact is not the same as a trip indication contact, and neither should automatically be treated as an available spare for SCADA. The ABB VD4X instruction manual is the primary source for the product-specific requirement stated here. An abnormal close or trip result should be carried into the VCB close/trip fault checklist instead of being cleared as a generic defect.
The allocation process should begin with the manufacturer-approved circuit diagram, not with a generic terminal list. ABB’s SecoVac manual shows a 52 auxiliary switch used within the closing and interlocking circuit, and it identifies functions such as close-block and truck-interlock circuits. This illustrates a practical rule: some auxiliary contacts may already be part of the breaker’s own control and interlocking design.
Before assigning contacts to SCADA or protection relays, confirm:
This prevents a common design error: treating all contacts shown on the diagram as free contacts. A contact may appear in the circuit but still be reserved for close blocking, truck position logic, or manufacturer-designed interlocking.
SCADA and protection relays often ask for similar information, but they do not always need the same signal. SCADA usually needs reliable remote indication such as breaker open, breaker closed, trip alarm, spring charged, local/remote status, or truck position where available. Protection relays may need breaker status for breaker failure logic, reclosing supervision, disturbance recording, interlocking, or trip circuit monitoring interfaces.
Where contact quantity allows, avoid sharing a single dry contact between multiple systems unless the approved design specifically permits it through interposing relays, isolation modules, or a defined terminal scheme. Shared circuits can create troubleshooting problems, ground-fault exposure, or unintended interactions between SCADA input cards and relay binary inputs.
A practical allocation order is:
This order is not a universal specification; it is a design discipline. The final contact assignment must match the VCB model, accessory selection, secondary plug arrangement, and project wiring philosophy. Use the Gama de disyuntores de vacío XBRELE to screen available equipment against the project duty before requesting a final configuration.
A VCB contact allocation table should identify the source of each signal, not only the destination. For example, a breaker-position signal may be derived from a mechanism auxiliary switch or a switch-shaft auxiliary switch, depending on the breaker design. A trip indication contact may show that a trip event occurred, but it should not be assumed to be equivalent to the breaker open position unless the wiring diagram and operating description confirm that function.
Schneider’s EvoPacT documentation describes a standard secondary plug and an optional Contact Plus plug that can provide additional breaker auxiliary contacts and plug-status indication. It also notes that contact capacity is product-configuration specific. This is important for engineering and procurement: additional contacts may be possible, but they are not generic promises. They depend on the ordered configuration.
For each contact, the schedule should show:
This format reduces ambiguity during FAT and SAT because the test team can verify the contact by function, not just by continuity. Use the breaker FAT/SAT verification guide to keep factory and site evidence traceable through handover.
Auxiliary contact allocation must not interfere with the manufacturer’s closing circuit. Schneider cautions that the breaker’s own auxiliary contacts must not be wired in series with its closing release and close contact because doing so can defeat the mechanical anti-pump system. That warning should be treated as a design boundary.
Anti-pump protection is intended to prevent repeated closing attempts under certain sustained close-command conditions. If field wiring changes the relationship between the close command, closing release, and breaker auxiliary contacts, the original protection behavior may be compromised. Therefore, SCADA close permissives, relay close commands, and local close circuits should be implemented according to the approved control schematic rather than by adding improvised auxiliary-contact logic in series with the closing coil path.
This is especially relevant when a site wants to add remote-control supervision after the switchgear has already been supplied. The correct solution is not to “find a spare contact” and insert it into the close circuit. The correct solution is to review the manufacturer’s control diagram, confirm the allowed remote-close interface, and update the drawing through an approved engineering change.
Withdrawable VCBs can include truck-position, plug-status, close-block, and interlocking functions. These functions may look like useful SCADA signals, but they may also be part of safety and operating logic. ABB’s SecoVac documentation, for example, identifies close-block and truck-interlock functions, showing why these circuits must be handled as engineered interlocks rather than casual indication points.
If SCADA needs truck service/test position, secondary plug status, or close-block indication, confirm whether those signals are available as dedicated indication contacts or whether they are embedded in an interlocking circuit. Do not parallel monitoring circuits onto interlock contacts without checking contact rating, circuit voltage, isolation, and manufacturer guidance. For the rated-data check, compare these conditions with the guía de valores nominales de disyuntores de vacío.
The allocation should also distinguish between permissive status and alarm status. “Plug connected,” “truck in service position,” and “close not blocked” are not interchangeable. Each tells the operator or relay logic something different. Mislabeling these points can cause incorrect SCADA mimic displays or misleading remote-control permissives.
A contact allocation matrix is the central document for VCB auxiliary contact allocation. It should sit between the single-line diagram, control schematic, SCADA I/O list, and relay logic diagram. The matrix does not need to invent new specifications; it organizes the manufacturer’s available contacts and the project’s required functions.
A useful matrix includes these columns:
| Artículo | Contact source | Función | Normal state reference | Destination | Uso | Drawing reference |
|---|---|---|---|---|---|---|
| 1 | Breaker auxiliary switch | Breaker closed indication | Per manufacturer diagram | Protection relay | Logic/status | Approved schematic |
| 2 | Breaker auxiliary switch | Breaker open indication | Per manufacturer diagram | SCADA RTU | Remote indication | Approved schematic |
| 3 | Trip indication contact | Trip event indication | Per manufacturer diagram | Relay or SCADA | Alarm/event | Approved schematic |
| 4 | Plug-status contact, if supplied | Secondary plug indication | Per manufacturer diagram | SCADA | Maintenance/status | Approved schematic |
| 5 | Interlocking contact, if supplied | Close permissive or block status | Per manufacturer diagram | Control circuit or monitor | Interlock/status | Approved schematic |
The wording “if supplied” is essential. Schneider’s optional Contact Plus plug and ABB’s optional interlocking contacts show that auxiliary-contact availability depends on the ordered configuration. The matrix should therefore be checked against the actual breaker nameplate, wiring diagram, plug arrangement, and accessory list.
Factory acceptance testing and site acceptance testing should verify both contact operation and signal meaning. It is not enough to confirm that a binary input changes state. The test should confirm that the signal changes for the correct mechanical or electrical condition.
Recommended checks include:
Any discrepancy should be resolved by drawing revision and engineering approval, not by undocumented terminal changes.
VCB auxiliary contact allocation is the process of assigning each available breaker auxiliary contact to a defined purpose, such as SCADA indication, protection relay logic, trip indication, plug status, or interlocking. The allocation must be based on the manufacturer’s approved wiring diagram and the actual breaker configuration.
The best way is to first reserve contacts required by the breaker’s own control and interlocking circuits, then assign confirmed available contacts to SCADA points such as open, closed, trip indication, and plug status where supplied. SCADA should not consume contacts that are already part of closing, tripping, close-block, or truck-interlock logic.
Breaker status usually indicates the present open or closed position of the VCB. Trip indication is a separate event or condition showing that a trip operation occurred, if that contact is provided in the selected configuration. ABB’s VD4X documentation distinguishes tripped-indication contacts from other auxiliary switch types, so the two signals should not be assumed to mean the same thing.
The risk is that field wiring can interfere with the manufacturer’s closing and anti-pump design. Schneider specifically cautions that the breaker’s own auxiliary contacts must not be wired in series with its closing release and close contact because that can defeat the mechanical anti-pump system.
Optional auxiliary-contact plugs can expand the available signals or provide additional status indications, depending on the product configuration. Schneider’s EvoPacT documentation describes a standard secondary plug and an optional Contact Plus plug that can provide additional breaker auxiliary contacts and plug-status indication, while also making clear that contact capacity is configuration specific.
A reliable VCB auxiliary contact allocation for SCADA and protection relays is therefore a controlled engineering task. It starts with the breaker’s approved circuit diagram, respects manufacturer-defined functions, separates SCADA from protection needs where practical, avoids unauthorized changes to the closing circuit, and verifies every signal during FAT and SAT.
