Commissioning Quantum Inputs with the 140XSM00200 Simulator

The Schneider Electric 140XSM00200 provides 16 toggle switches that generate binary input signals for Modicon Quantum testing. It is useful for checking input mapping and sequence logic before reconnecting field devices.

The simulator does not prove that field wiring, sensors, or supply circuits are correct. Treat it as a controller-side test tool with a defined boundary.

Confirm the host module before fitting the simulator

Record the Quantum rack, slot, input-module catalog number, and application version. Do not assume every Quantum input module accepts the same simulator.

Compare the installed module against the 140XSM00200 product record and the applicable Schneider Electric documentation. Schneider describes the 140XSM00200 as a 16-toggle discrete simulator that can generate up to 16 binary input signals.

Save the current PLC application and I/O configuration. Record the raw input address used by each interlock. This prevents a successful test from hiding an addressing error.

Separate field energy from the logic test

Place the machine in the approved maintenance state. Isolate affected outputs and hazardous motion through the site procedure. A forced input can satisfy permissives that normally depend on real equipment.

Disconnect the field connector only under the host module procedure. Label it before removal. Keep field conductors clear of the simulator and adjacent terminals.

Disable automatic starts where the risk assessment requires it. Use a second person for tests that can change machine state.

Build a channel test matrix

Create one row for each simulator switch. Include the physical channel, PLC tag, expected raw bit, expected alarm, and expected interlock result.

Test item	Record
Switch	1–16
PLC address	Rack, slot, channel, and tag
Expected state	Raw input bit and interpreted condition
Interlock response	Permissive, alarm, trip, or no action
Observed result	Pass, fail, or discrepancy

Start with all switches in the documented inactive state. Capture the PLC input word before changing any channel.

Toggle one input at a time

Operate one switch and observe the raw input bit first. Then check the mapped tag, alarm logic, sequence state, and HMI indication.

Do not test only the positive transition. Return the switch and verify the input clears. Latching logic may require a separate reset path.

If two tags change together, stop the test. Check rack addressing, tag aliases, copied words, and reused intermediate bits before continuing.

Test interlocks without defeating the safety boundary

A simulator can check standard control logic. It cannot validate a complete safety function or the field device that initiates it.

Keep final outputs inhibited where practical. Verify that each simulated state reaches the intended permissive or fault routine. Record any timer, debounce, or sequence delay.

Test impossible combinations deliberately. Two switches may represent states that cannot coexist in the machine. The program should handle that discrepancy predictably.

Restore the field path and prove it separately

Return all switches to the documented state. Remove the simulator under the host module procedure, inspect the connector, and reconnect field wiring.

Repeat critical checks from the actual sensors or contacts. Confirm channel polarity, HMI text, alarms, interlocks, and reset behavior.

Store the completed matrix with the PLC backup. The record should show what the simulator proved and what remained a field test.

Source: Schneider Electric FAQ FA197451. Related controllers and I/O hardware are listed in the PLC and PAC systems collection.