The confusing symptom is a manual note that appears to say two outputs cannot operate together. For the DVP-08SN 11 T, “Mutually Exclusive Output” describes a recommended control strategy: use an external interlock for loads that must never run simultaneously, then reinforce that protection in the PLC program. It does not identify a built-in pairing that automatically prevents two module outputs from turning on.
Where does each output command travel?
Follow the signal from the PLC program to the field device. The logic requests an output state, the transistor output channel switches, and current flows through the connected load circuit. The channels share a supply common in the referenced wiring arrangement, but each channel remains independently commanded.
| Path element | Reading or state to check | Meaning |
|---|---|---|
| PLC logic | Command state for each output point | Shows what the program is requesting |
| Output indication or status | ON or OFF for each channel | Shows whether the output subsystem accepted the request |
| Output terminal | Voltage relative to the specified common | Shows whether the transistor channel is switching the field circuit |
| Load | Coil voltage or input state | Shows whether the command reached the controlled device |
No network address or communication port participates in this path. The relevant references are the configured output point, its physical terminal, and the shared common. Exact terminal designations must come from the instruction sheet for the installed module. Output response timing also depends on the PLC scan, output update, field wiring, and load response; measure it at the terminals if the application has a timing requirement.
Can two output terminals switch at the same time?
Command both channels under controlled test conditions and read each channel at its terminal relative to the proper common. If both terminal states follow their commands, the outputs are operating independently. That is the expected interpretation of the wiring note.
| Logic commands | Terminal readings | Decision | Next check |
|---|---|---|---|
| Both ON | Both switch correctly | No built-in mutual exclusion is acting | Determine whether the loads require an interlock |
| Both ON | Only one switches | A wiring, load, supply, channel, or program condition is blocking the other path | Check the common and measure the blocked channel |
| One ON | The other load also operates | The field circuits may be cross-connected or sharing an unintended return path | Isolate the load wiring and perform continuity checks with power removed |
| Both OFF | A load remains energized | The load is being held elsewhere, such as by a seal-in circuit or mechanical condition | Trace the external control circuit |
When taking live readings, use the voltage reference shown in the module wiring sheet. A voltage measured to an unrelated ground can misrepresent the transistor state. Also compare the commanded state with the program’s final write to that output; duplicate logic can turn a point back off later in the scan.
Does a shared common make the outputs mutually exclusive?
No. A shared common provides a common electrical reference or current-return arrangement for a group of channels. It does not make their logic states mutually exclusive. Multiple channels can use that common simultaneously when the connected loads and total current remain within the module’s documented channel and common-group limits.
Read the installed module’s instruction sheet for the permitted output voltage, per-channel current, common-group current, wiring polarity, leakage behavior, and protective components. Those ratings are not interchangeable. A load may satisfy an individual channel limit while the sum of several simultaneous loads exceeds the common-group limit.
Layer one first. With power isolated, verify that the supply common reaches the specified terminal and that each load returns through the intended path. With power applied under an approved test method, measure supply voltage at the module and load voltage while one channel and then both channels are commanded. A supply collapse only during simultaneous operation points to supply capacity, excessive load current, or excessive wiring resistance—not mutual-exclusion logic.
Where should mutually exclusive operation be enforced?
First decide whether simultaneous operation can create a hazardous or damaging state. Typical examples include opposing contactors, incompatible valves, or actuators commanded in opposite directions. If concurrent operation is harmless, the manual note does not require arbitrarily pairing and blocking outputs.
If the loads must never operate together, use two layers:
| Layer | Function | What it protects against | What it cannot replace |
|---|---|---|---|
| PLC program | Prevents the logic from requesting incompatible states | Sequence errors and normal operating conflicts | Independent field-circuit protection |
| External electrical or mechanical interlock | Interrupts one device’s control path while the opposing device is active | Unexpected simultaneous PLC commands and specified single failures | Correct program sequencing and diagnostics |
The external interlock belongs in the controlled circuit, not between PLC output terminals. For two opposing contactors, a common electrical arrangement places a normally closed auxiliary contact from each contactor in series with the opposing contactor coil. A mechanical interlock may add direct physical blocking when the application requires it. Select the method from the machinery risk assessment and the controlled-device documentation.
An interlock is not the same as a seal-in circuit. A seal-in circuit uses an auxiliary contact to maintain a coil after a momentary start command. The manual wording does not require turning the PLC output off and holding the device with an auxiliary contact. Use seal-in behavior only when the control design calls for it and provides a defined stop path.
Which checks separate logic, wiring, and load faults?
- Read both command states. If the program never requests both outputs, inspect the software interlock. If it requests both, continue at the physical outputs.
- Read each terminal relative to the specified common. If the terminal states match the commands, continue toward the loads. If one does not match, disconnect or isolate the load as permitted and distinguish a channel problem from an overloaded or miswired field circuit.
- Read voltage at each load. Correct output-terminal voltage but incorrect load voltage identifies a cable, terminal, interposing-device, or return-path problem.
- Check auxiliary-contact states. An open interlock contact should block the opposing coil even when its PLC output is on. If it does not, correct the interlock wiring or contact selection.
- Check load current against documented limits. Compare each load and the simultaneous total with the instruction-sheet ratings. Account for coil inrush and the suppression device specified for the load.
- Review the final output logic. Search every write to each output point. A later instruction, forced state, fault routine, or operating mode can override the expected command.
How should the resolving interlock be tested?
- Remove forces and place the machine in a controlled test state.
- Command the first load alone and confirm its PLC state, output-terminal voltage, load voltage, and feedback state.
- While the first device is active, request the opposing output through an approved test sequence. Confirm that the software rejects the request or removes the first command before allowing the second.
- Test the external layer separately under the authorized validation method. Confirm that the active device’s auxiliary or mechanical interlock prevents the opposing device from energizing even if both control outputs are requested.
- Command both outputs off and confirm that both loads de-energize without depending on an unintended seal-in path.
Record the command, terminal, load, and feedback states for every branch. The resolving result is not merely two illuminated output indicators; it is independent channel operation during normal commands and positive blocking of the prohibited load combination.
FAQ
How do I know whether DVP-08SN 11 T outputs are internally paired?
Command two channels and measure each output relative to the specified common. If both follow their commands, the channels are independent; “Mutually Exclusive Output” refers to an application interlock, not an automatic module pairing.
How do I wire two outputs that must never operate together?
Drive each control device through the normally closed auxiliary contact of the opposing device, or use the mechanical interlock specified for that equipment. Add PLC logic that rejects simultaneous commands.
How do I distinguish a shared-common problem from an interlock?
Measure the module supply and each output relative to the specified common with one load active and then both active. Voltage collapse during the two-load test points to the supply, common, wiring resistance, or load current; a deliberate open auxiliary contact identifies the external interlock.
How do I verify the output interlock after wiring it?
Request the prohibited combination through an approved test sequence and record both output-terminal voltages, both coil voltages, and both device feedback states. Pass the test only when the allowed device operates and the opposing device remains de-energized under both software and external-interlock checks.