What does XIC mean in ladder logic?

XIC stands for Examine If Closed. The instruction evaluates to TRUE (passes power) when the bit it references is a 1. It is the equivalent of a normally open contact in a hardwired relay schematic. If the bit is 0, the XIC instruction is FALSE and blocks the rung.

What does XIO mean in ladder logic?

XIO stands for Examine If Open. The instruction evaluates to TRUE when the bit it references is a 0. It behaves like a normally closed contact in relay logic. When the bit goes to 1, XIO becomes FALSE. It is commonly used for stop buttons, fault interlocks and inhibit conditions.

What is the difference between XIC and XIO in Allen-Bradley PLCs?

XIC passes power when its bit is 1; XIO passes power when its bit is 0. They are logical inverses of each other. Use XIC to check that something is ON or active, and XIO to check that something is OFF or inactive before allowing an output to energise.

Does XIO mean the physical contact is normally closed?

Not necessarily. XIO means 'the bit is currently 0.' The physical wiring of the field device matters separately. A physical NC contact wired to the PLC input drives the input bit HIGH when the contact is closed. Whether you then use XIC or XIO in logic depends on the safety and logic intent, not the contact type alone.

Can you use XIC and XIO on internal bits, not just physical inputs?

Yes, and this is very common. XIC and XIO work on any BOOL tag: physical input bits, output bits, internal memory bits (flags), timer done bits, counter done bits, and safety bits. The instruction only cares about the current value of the referenced bit, regardless of where it comes from.

Why does my XIO contact stay FALSE even though the physical device is open?

Check the input bit value in online monitoring first. If the wiring is correct but the bit is 1 when you expect 0, the field device may be sending current (NPN vs PNP mismatch, or a NC contact that is actually closed). See the post on sinking vs sourcing I/O for wiring details.

How do XIC and XIO appear in the Studio 5000 symbol?

In Studio 5000, XIC appears as two vertical bars with no decoration, identical to a normally open relay contact symbol. XIO appears as two vertical bars with a diagonal slash through them, matching the normally closed relay contact symbol. Both show the tag name above the symbol.

Is XIC the same as a normally open contact?

Functionally, yes. XIC mirrors the normally open relay contact: it is open (FALSE) at rest and closes (TRUE) when its coil or bit is energised. The key difference is that in ladder logic, 'energised' simply means the bit value is 1, not that current is physically flowing through a coil.

Can XIC and XIO be used in series on the same rung?

Yes. Series contacts in ladder logic perform a logical AND. The rung only passes power if ALL contacts in series evaluate to TRUE simultaneously. XIC requires its bit to be 1; XIO requires its bit to be 0. Mix them to build interlock conditions where several things must be true at once.

XIC vs XIO Ladder Logic: Contacts Explained

‌

Flat vector diagram comparing XIC and XIO ladder logic contact symbols with bit-state labels showing how each instruction evaluates its tag

XIC and XIO are the first two instructions you encounter in Allen-Bradley ladder logic, and they are also the source of more commissioning head-scratching than almost anything else. They look simple. Two vertical bars, or two vertical bars with a slash. But the mental model that connects the symbol to the bit value to the physical wiring trips up engineers at every level, from first-week students to experienced techs moving from a different vendor platform.

What Is the Difference Between XIC and XIO?

XIC (Examine If Closed) evaluates to TRUE and passes power when the bit it references is 1. XIO (Examine If Open) evaluates to TRUE and passes power when the bit it references is 0. They are logical inverses. XIC is the ladder equivalent of a normally open relay contact; XIO mirrors a normally closed contact. Both instructions read the current value of a single BOOL tag in the PLC's data table, and they do that read fresh on every scan.

Instruction	Full Name	Passes power when bit is...	Relay equivalent
XIC	Examine If Closed	1 (TRUE)	Normally Open (NO)
XIO	Examine If Open	0 (FALSE)	Normally Closed (NC)

XIC vs XIO at a glance in Logix5000 / Studio 5000

How the PLC Evaluates Each Instruction

During the input scan, the processor copies physical terminal states into the input image table. During the logic scan, XIC and XIO simply look at the stored bit. Neither instruction cares whether the bit came from a physical wire, an internal flag, a timer done bit, or a counter overflow bit. The only question is: is the bit a 1 or a 0 right now?

This is worth internalising. If you put an XIC on Conveyor_Run (an internal BOOL output), you are checking whether the conveyor output coil is currently energised. That is a perfectly valid interlock. Understanding PLC memory and addressing helps you see that all these bit addresses live in the same flat data table regardless of type.

XIC in Practice: When to Use It

Use XIC whenever you need to confirm that something is active or ON before taking an action. Classic examples:

Start pushbutton (momentary, wired NO): bit goes 1 when pressed, XIC fires once
Proximity sensor confirmation: part-in-position bit must be 1 before a fill valve opens
Seal-in latch: XIC on the output coil tag itself to hold the rung TRUE after the start button releases
Timer done bit: XIC(Fill_Timer.DN) to advance a step once timing is complete
Counter done bit: XIC(Part_Count.DN) to trigger an end-of-batch action

If you are reviewing ladder logic interview questions, XIC on a timer's .DN bit is almost guaranteed to come up. It is the most common contact type in any real program.

XIO in Practice: When to Use It

XIO is your interlock and inhibit instruction. Use it when an output must stay OFF while something else is active. Common applications:

Stop pushbutton (wired NC, bit normally 1): XIO evaluates FALSE when the stop is pressed, dropping the rung
Fault latch: XIO on a fault bit blocks a start command until the fault is cleared
Interlock: XIO on an arm-extended limit switch prevents a second cylinder from firing while the first is out
Mode inhibit: XIO on a 'Machine_Running' bit blocks a recipe-load command during production
Timer not-done: XIO on Purge_Timer.TT to hold a bypass open only while the timer is still timing

Stop-button wiring gotcha. A physical NC stop button wired to an input drives the bit HIGH (1) when the button is at rest. So you use XIO(Stop_PB) in the rung: the XIO is TRUE (rung passes) while the bit is 1 (button not pressed). When the operator presses stop, the NC contact opens, the bit drops to 0, and XIO becomes FALSE, cutting power to the output. If you wire a stop as NO and use XIO, you get the opposite behaviour. This is the single most common wiring-versus-logic mismatch on a first commissioning. Check the physical wiring, then decide which instruction makes the rung fail-safe.

The Bit Value Is Everything: Separating Wiring from Logic

This is the part that genuinely confuses people. The PLC does not know whether a physical device is normally open or normally closed. It only sees the bit. Whether that bit is a 1 or 0 depends on the wiring and the device type.

Take a 3-wire PNP proximity sensor. When a metal target is present, the PNP sensor sources current to the input, the input energises, and the bit goes to 1. A 3-wire NPN sensor does the same thing electrically but with the current path reversed. The sinking vs sourcing I/O wiring determines which of those two sensor types works with your module. But in both cases, once the bit is in the image table, XIC and XIO behave identically. The full picture for 3-wire sensors is in the PNP vs NPN wiring guide.

Safety-critical inputs add another layer. An E-stop button is always wired NC to the input, so the bit is 1 during normal operation. You use XIO on that bit so the rung drops power the instant the button is pressed. This is a fail-safe design: a broken wire also drives the bit to 0 and stops the machine. The emergency stop circuit wiring guide covers the hardware side, but your ladder logic must be consistent with it.

Series, Parallel and Mixed Contact Rungs

Contacts in series are AND logic: every contact must be TRUE for the rung to pass. Contacts in parallel branches are OR logic: any one TRUE branch is enough. You can freely mix XIC and XIO on the same rung.

A typical start circuit: [XIC(Start_PB) parallel with XIC(Motor_Run)] series XIO(Stop_PB) series XIO(Overload_Fault) -> OTE(Motor_Run). The seal-in uses XIC on the output tag itself. The stop and overload use XIO because both conditions hold the bit at 1 during normal run, and go to 0 to stop the machine. If you have worked through the PLC counter instructions or TON, TOF and TONR timer differences, you will have seen XIC and XIO in exactly those rung structures.

A Fresh Ladder Example: Conveyor Divert Gate with XIC and XIO

Here is a rung that is not the usual start/stop motor. A divert gate on a conveyor should extend only when three conditions are all met: the conveyor is running, the vision system has flagged a reject, and the gate is not already in a fault state. The gate must retract automatically once the reject timer times out.

Conveyor Divert Gate: Extend on Reject, Retract on Timer DoneLadder logic

Toggle inputs

Rung 0

Rung 1

Rung 2

Rung 3

Rung 4

Rung 5

Rung 6

energizedTip: click a contact in the diagram to flip its bit.

Rung 1: XIC on Conveyor_Running and Vision_RejectFlag (both must be 1), XIO on Gate_FaultLatch (must be 0, i.e. no fault active), latches Gate_Extend_Cmd ON. Rung 2: starts a 500 ms retract timer while the gate is commanded out. Rung 3: when the timer done bit fires, unlatch the gate command, reset the timer, and clear the reject flag. Rung 4: drives the physical solenoid output from the latched bit. Rungs 5-6: fault detection if the extend limit switch does not confirm within 2 seconds. Rung 7: operator ack clears the fault latch only when the gate is no longer commanded.

Notice how every safety interlock uses XIO: the fault latch and the fault ack both require their respective bits to be 0 (inactive) before allowing the controlled action. That is the pattern you will see repeated across every well-written Logix program. For a bigger version of this pattern in a real machine context, the PLC bottle filling machine project shows it applied across a full sequence.

XIC vs XIO in Other IEC 61131-3 Languages

XIC and XIO are Rockwell-specific names. Other vendors use the same concept under different labels. In Siemens TIA Portal, the ladder contacts are simply called Normally Open (NO) and Normally Closed (NC), with the same relay-symbol appearance. In CODESYS and IEC 61131-3 standard ladder, the symbols are identical but the contact types are described as 'contact' and 'negated contact.' The underlying logic is the same: one passes on bit = 1, the other passes on bit = 0.

If you are moving from Siemens to Rockwell, the mental shift is just learning the new names. The 5 types of PLC programming languages article covers where ladder sits among structured text, function block, and the rest. And if you want to see how Siemens handles the equivalent in a real project, the S7-1200 first program guide walks through the TIA Portal environment.

Troubleshooting XIC and XIO Contacts Online

Studio 5000 shows a live power flow highlight when you go online. A contact that is passing power is shown in green (or highlighted, depending on your colour theme). If an XIC contact is not highlighted when you expect it to be, the referenced bit is 0. If an XIO contact is not highlighted when you expect it to be, the referenced bit is 1.

The fastest debug path: hover over the tag name on the contact to see the live bit value in the tooltip, or open the tag browser and watch the value column update in real time. If the bit is wrong, trace it back, either to the physical input via PLC I/O fault diagnosis with a multimeter, or to the logic that drives it if it is an internal bit. The PLC troubleshooting with online monitoring guide goes deeper on this workflow.

From the field: I was commissioning a reject station on a biscuit line where the divert gate would not extend. Online monitoring showed the XIO on the fault latch was FALSE, meaning the fault bit was unexpectedly a 1. The fault had latched during a jog test the day before and nobody had cleared it via the HMI. Two seconds with online monitoring saved what could have been an hour of multimeter work on the field wiring. Always check the bit value before touching the panel.

Common Mistakes With XIC and XIO

Using XIC on a stop button wired NC. The bit is 1 at rest. XIC passes power, which is fine until you think through what happens on a wire break: the bit drops to 0, XIC goes FALSE, and the machine stops. That is actually safe behaviour. But if you intended the stop to only kill power when pressed, you need XIO.
Using XIO on a start button. Start buttons are typically wired NO. The bit is 0 at rest. XIO would pass power constantly and trigger the start immediately on powerup. This is almost never what you want.
Forgetting that output bits can be read by XIC/XIO. Placing XIC on an OTE output tag in the same program creates a seal-in or interlock based on the output state. This is intentional in motor starters but can create unintended latching if used carelessly.
Confusing the physical device type with the instruction type. A NC limit switch wired to a sourcing input drives the bit to 1 when the switch is closed (target present). Whether you use XIC or XIO in logic is a separate decision based on what you want the rung to do, not on whether the switch itself is NO or NC.
Scan-cycle timing on fast inputs. A very short pulse from a proximity sensor may only be 1 for one scan. If your XIC misses it, the rung never fires. The input pulse stretcher pattern in the PLC scan cycle problems guide addresses exactly this.

Keep Learning

Now that XIC and XIO are clear, the natural next step is understanding the output instructions they drive: OTE, OTL and OTU. Then move on to how timer done bits and counter done bits feed back into contacts, which is where TON, TOF and TONR timers and CTU, CTD and CTUD counters become essential reading. If you are preparing for an interview, the ladder logic interview questions post covers XIC, XIO and a lot more in a format that mirrors what hiring managers actually ask.