Input addressing scheme in PLC Programming - Deep Dive

Overview - Input addressing scheme

What is it?

An input addressing scheme is a method used in programmable logic controllers (PLCs) to identify and access physical input devices like switches and sensors. It assigns unique addresses to each input point so the PLC can read their status during operation. This scheme helps the PLC know exactly where to look for signals from the real world.

Why it matters

Without a clear input addressing scheme, a PLC would not know which physical input corresponds to which internal signal. This would make automation unreliable or impossible, as the controller could not correctly respond to changes in the environment. Proper addressing ensures accurate control and monitoring, which is critical for safety and efficiency in industrial processes.

Where it fits

Before learning input addressing schemes, you should understand basic PLC concepts like inputs, outputs, and ladder logic. After mastering input addressing, you can learn output addressing schemes and advanced topics like memory mapping and communication protocols.

Mental Model

Core Idea

Input addressing schemes map physical input devices to unique identifiers so the PLC can read and respond to them correctly.

Think of it like...

It's like assigning a unique mailbox number to each house on a street so the mail carrier knows exactly where to deliver letters.

┌───────────────┐
│ Physical Inputs│
│ (Switches,    │
│ Sensors)      │
└──────┬────────┘
       │
       ▼
┌───────────────┐
│ Input Address │
│ Scheme       │
│ (Unique IDs) │
└──────┬────────┘
       │
       ▼
┌───────────────┐
│ PLC Reads     │
│ Input Status  │
└───────────────┘

Build-Up - 7 Steps

1

Foundation

What is an Input Address

Concept: Introduce the idea that each physical input device has a unique address in the PLC system.

In a PLC, each input device like a button or sensor is assigned a unique address. This address tells the PLC where to find the signal from that device. For example, input 0 might be a start button, and input 1 might be a stop button.

Result

You understand that inputs are not just random signals but have specific locations the PLC reads.

Understanding that inputs have unique addresses is the foundation for how PLCs interact with the physical world.

2

Foundation

Types of Input Addresses

Concept: Explain the common formats of input addresses used in PLCs.

Input addresses can be represented in different ways depending on the PLC brand. Common formats include: - Numeric (e.g., I0, I1) - Byte and bit (e.g., I0.0 for byte 0, bit 0) - Hexadecimal or decimal numbers These formats help organize inputs logically.

Result

You can recognize and interpret different input address formats.

Knowing address formats helps you read and write PLC programs correctly.

3

Intermediate

Mapping Physical Inputs to Addresses

Concept: Learn how physical input devices are connected and mapped to PLC input addresses.

Each physical input device is wired to a specific input terminal on the PLC hardware. The PLC documentation shows which terminal corresponds to which input address. For example, terminal 1 might be input I0.0, terminal 2 might be I0.1, and so on. This mapping ensures the PLC reads the correct device status.

Result

You can trace a physical input device to its PLC address.

Understanding wiring and mapping prevents errors in connecting devices and programming.

4

Intermediate

Reading Input Status in Programs

🤔Before reading on: do you think the PLC reads input addresses continuously or only once? Commit to your answer.

Concept: Explain how the PLC reads input addresses during its scan cycle.

The PLC continuously scans all input addresses in a loop called the scan cycle. It reads the status (on/off) of each input address and updates its internal memory. This allows the PLC program to react immediately to changes in inputs.

Result

You understand that input status is always current during PLC operation.

Knowing the scan cycle helps you design responsive and reliable control programs.

5

Intermediate

Input Addressing in Different PLC Brands

🤔Before reading on: do you think all PLCs use the same input addressing scheme? Commit to your answer.

Concept: Introduce variations in input addressing schemes across different PLC manufacturers.

Different PLC brands use different conventions for input addresses. For example: - Siemens uses I0.0, I0.1 for inputs - Allen-Bradley uses %I0:0/0 - Mitsubishi uses X0, X1 Knowing these differences is important when switching between PLCs or reading manuals.

Result

You can identify and adapt to different input addressing schemes.

Recognizing brand differences prevents confusion and errors in multi-vendor environments.

6

Advanced

Input Addressing with Expansion Modules

🤔Before reading on: do you think expansion modules change input addresses or keep them the same? Commit to your answer.

Concept: Explain how adding input expansion modules affects addressing schemes.

When you add expansion modules to a PLC, the input addresses extend to cover new physical inputs. For example, the base PLC might have inputs I0.0 to I0.7, and an expansion module adds I1.0 to I1.7. The addressing scheme must account for these to avoid overlap and confusion.

Result

You understand how to manage input addresses with hardware expansions.

Knowing how expansions affect addressing helps maintain scalable and organized PLC systems.

7

Expert

Addressing Conflicts and Best Practices

🤔Before reading on: do you think input addresses can overlap safely in a PLC system? Commit to your answer.

Concept: Discuss common pitfalls like address conflicts and how to avoid them in complex systems.

Address conflicts happen when two physical inputs are assigned the same address, causing unpredictable behavior. Best practices include: - Careful documentation - Using software tools to check addresses - Following manufacturer guidelines - Planning address ranges for expansions Avoiding conflicts ensures reliable and maintainable PLC programs.

Result

You can prevent and resolve input address conflicts in real projects.

Understanding conflicts and best practices is crucial for professional-grade PLC programming and system reliability.

Under the Hood

Internally, the PLC hardware has input modules with terminals connected to physical devices. Each terminal corresponds to a memory bit in the PLC's input image table. During the scan cycle, the PLC reads the voltage or signal level at each terminal and updates the corresponding bit in memory. The program then reads these bits to make decisions. This mapping from physical terminals to memory bits is the input addressing scheme.

Why designed this way?

This design separates hardware wiring from software logic, allowing flexible programming without changing physical connections. It also standardizes how inputs are read regardless of device type. Early PLCs used fixed addresses, but modern designs allow modular expansions and configurable addressing to support complex systems.

┌───────────────┐       ┌───────────────┐       ┌───────────────┐
│ Physical      │──────▶│ Input Module  │──────▶│ Input Image   │
│ Devices       │       │ (Terminals)   │       │ Table (Memory)│
└───────────────┘       └───────────────┘       └───────────────┘
                                   │
                                   ▼
                          ┌─────────────────┐
                          │ PLC Program     │
                          │ Reads Addresses │
                          └─────────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Do input addresses represent physical wiring only or also logical program variables? Commit to your answer.

Common Belief: Input addresses only represent physical wiring and have no relation to program variables.

Reality: Input addresses map physical wiring to logical memory bits that the program uses as variables.

Why it matters: Thinking addresses are only physical leads to confusion when programming and debugging, as the program works with logical bits, not wires.

Quick: Can two different physical inputs share the same input address safely? Commit to yes or no.

Common Belief: Yes, two physical inputs can share the same address without issues.

Reality: No, sharing addresses causes conflicts and unpredictable behavior in the PLC program.

Why it matters: Address conflicts can cause safety hazards and system failures in industrial automation.

Quick: Are input addresses the same across all PLC brands? Commit to yes or no.

Common Belief: All PLCs use the same input addressing scheme universally.

Reality: Different PLC brands use different addressing formats and conventions.

Why it matters: Assuming uniformity causes errors when switching brands or reading documentation.

Quick: Does adding expansion modules keep input addresses unchanged? Commit to yes or no.

Common Belief: Expansion modules do not affect input addresses; they remain the same.

Reality: Expansion modules add new address ranges, extending the input addressing scheme.

Why it matters: Ignoring this leads to address overlaps and programming errors in expanded systems.

Expert Zone

1

Some PLCs allow remapping input addresses in software, which can simplify complex wiring but requires careful management.

2

Input addressing schemes often align with hardware byte boundaries for efficient memory access, a detail important for performance tuning.

3

Advanced diagnostics use input addressing to monitor signal quality and detect wiring faults, not just on/off status.

When NOT to use

Input addressing schemes are not applicable for purely software-based simulations or virtual PLCs without physical I/O. In such cases, symbolic or variable-based addressing is used instead.

Production Patterns

In production, input addressing schemes are documented in I/O lists and wiring diagrams. Programmers use symbolic names linked to addresses for readability. Address ranges are reserved for different modules, and automated tools verify no overlaps exist before deployment.

Connections

Memory Mapping

Input addressing schemes build on memory mapping concepts by linking physical inputs to specific memory locations.

Understanding memory mapping clarifies how PLCs store and access input statuses internally.

Network Addressing

Both input addressing and network addressing assign unique identifiers to entities to enable communication and control.

Recognizing this similarity helps understand the importance of unique addresses in any system managing multiple devices.

Postal Addressing System

Input addressing is like postal addressing where each house has a unique address for mail delivery.

This cross-domain connection highlights the universal need for unique identifiers to organize and access distributed resources.

Common Pitfalls

#1 Assigning the same input address to multiple physical devices.

Wrong approach:

I0.0 = Start Button
I0.0 = Emergency Stop

Correct approach:

I0.0 = Start Button
I0.1 = Emergency Stop

Root cause:

Misunderstanding that each input address must be unique to avoid conflicts.

#2 Ignoring expansion module address ranges and overlapping addresses.

Wrong approach:

Base PLC inputs: I0.0 to I0.7
Expansion module inputs also assigned I0.0 to I0.7

Correct approach:

Base PLC inputs: I0.0 to I0.7
Expansion module inputs assigned I1.0 to I1.7

Root cause:

Not accounting for address extension when adding hardware modules.

#3 Using incorrect input address format for the PLC brand.

Wrong approach:

Using Siemens format I0.0 on Allen-Bradley PLC.

Correct approach:

Using Allen-Bradley format %I0:0/0 on Allen-Bradley PLC.

Root cause:

Assuming all PLCs share the same addressing syntax.

Key Takeaways

Input addressing schemes assign unique identifiers to physical input devices so the PLC can read their status accurately.

Different PLC brands use different input address formats, so always check the documentation before programming.

Expansion modules extend input addresses, requiring careful planning to avoid overlaps and conflicts.

The PLC continuously scans input addresses during operation, keeping the program updated with real-time input status.

Proper input addressing is essential for reliable, safe, and maintainable industrial automation systems.

Practice

1. What does the input addressing scheme I1.3 mean in a PLC program?

easy

A. Internal memory at byte 1, bit 3

B. Output at byte 1, bit 3

C. Input at byte 3, bit 1

D. Input at byte 1, bit 3

Solution

1. Step 1: Understand the input address format

   The format I<byte>.<bit> means input at specified byte and bit.

2. Step 2: Interpret I1.3

   This means input at byte 1, bit 3.

3. Final Answer:

   Input at byte 1, bit 3 -> Option D

4. Quick Check:

   Input address = I1.3 means byte 1, bit 3 [OK]

Hint: I means input, number before dot is byte, after dot is bit [OK]

Common Mistakes:

• Confusing input with output addresses
• Mixing up byte and bit positions
• Assuming bit number comes before byte

2. Which of the following is the correct syntax for addressing input bit 5 in byte 2?

easy

A. I2.5

B. I5.2

C. O2.5

D. I2-5

Solution

1. Step 1: Recall input address syntax

   The correct format is I<byte>.<bit>.

2. Step 2: Match byte 2 and bit 5

   So input bit 5 in byte 2 is I2.5.

3. Final Answer:

   I2.5 -> Option A

4. Quick Check:

   Correct input syntax = I2.5 [OK]

Hint: Use dot between byte and bit, start with I for input [OK]

Common Mistakes:

• Swapping byte and bit numbers
• Using O instead of I for input
• Using dash instead of dot

3. Given the PLC input address I0.7 is ON and all others OFF, what is the binary value of byte 0?

medium

A. 00000001

B. 10000000

C. 11111111

D. 00000000

Solution

1. Step 1: Understand bit numbering in a byte

   Bit 0 is the least significant bit (rightmost), bit 7 is the most significant (leftmost).

2. Step 2: Set bit 7 ON and others OFF

   Bit 7 ON means the leftmost bit is 1, others 0, so binary is 10000000.

3. Final Answer:

   10000000 -> Option B

4. Quick Check:

   I0.7 ON means bit 7 = 1, binary = 10000000 [OK]

Hint: Bit 7 is leftmost bit in byte, so 10000000 [OK]

Common Mistakes:

• Assuming bit 7 is rightmost bit
• Confusing bit numbering direction
• Setting wrong bit ON

4. A PLC program uses the input address I3.8. What is wrong with this address?

medium

A. Bit number 8 does not exist in a byte

B. Byte number 3 is invalid

C. Input addresses cannot have dots

D. I should be lowercase

Solution

1. Step 1: Recall bit numbering limits

   A byte has bits numbered 0 to 7 only, so bit 8 is invalid.

2. Step 2: Check address I3.8

   Bit 8 is outside valid range, so address is incorrect.

3. Final Answer:

   Bit number 8 does not exist in a byte -> Option A

4. Quick Check:

   Bits 0-7 valid, 8 invalid [OK]

Hint: Bits go 0 to 7 only, no bit 8 in a byte [OK]

Common Mistakes:

• Thinking bits go 1 to 8
• Ignoring dot separator
• Assuming case sensitivity matters

5. You want to read inputs from byte 4 bits 0 to 3 and combine them into a 4-bit number in your PLC program. Which input addresses should you use?

hard

A. I4.4, I4.5, I4.6, I4.7

B. I0.4, I1.4, I2.4, I3.4

C. I4.0, I4.1, I4.2, I4.3

D. I3.0, I3.1, I3.2, I3.3

Solution

1. Step 1: Identify byte and bit range

   You want bits 0 to 3 in byte 4, so bits 0,1,2,3 of byte 4.

2. Step 2: Write input addresses for these bits

   These are I4.0, I4.1, I4.2, I4.3.

3. Final Answer:

   I4.0, I4.1, I4.2, I4.3 -> Option C

4. Quick Check:

   Bits 0-3 in byte 4 = I4.0 to I4.3 [OK]

Hint: Bits 0-3 in byte 4 are I4.0 to I4.3 [OK]

Common Mistakes:

• Mixing bits from different bytes
• Using bits 4-7 instead of 0-3
• Confusing byte numbers