How to Connect RFID Readers to PLCs: Protocols, Wiring & Real-World Examples

How to Connect RFID Readers to PLCs: Protocols, Wiring & Real-World Examples

In modern factories, the Programmable Logic Controller (PLC) is the undisputed brain of automation — controlling conveyors, robots, and packaging machines. But a PLC is blind without sensors. While photoelectric sensors detect presence and barcode scanners need a clean line of sight, RFID (Radio Frequency Identification) gives the PLC the ability to uniquely identify parts, Tools, and products, even in dirty or harsh environments.

This article focuses on the practical side: how to physically and logically connect an RFID reader to a PLC, what protocols to use, and three real industrial cases you can learn from.

Part 1: The Big Picture — What Does an RFID System Look Like to a PLC?

From the PLC‘s perspective, an RFID reader is simply another I/O device — but one that delivers structured data (a tag ID and possibly user memory) rather than a single bit.

A typical industrial RFID system consists of:

1. Tag (transponder) – mounted on a pallet, tool, or product.

2. Read/Write Head (antenna + electronics) – fixed on a machine or conveyor.

3. Interface / Processor – converts the raw RF signal into a protocol the PLC understands. Many modern heads integrate this internally.

4. PLC – reads the data and makes a decision (e.g., accept/reject, route to next station, change machine parameters).

The key difference from a simple sensor: the PLC must execute a “read” or “write” command and wait for a response, not just monitor a binary signal.

Part 2: Four Main Ways to Connect an RFID Reader to a PLC

There is no single “RFID cable”. The choice depends on your PLC brand, distance, data volume, and speed requirements.

Option 1: Discrete I/O (Digital Signals) — Simple but Limited

• How it works: The RFID reader outputs 24V DC signals on dedicated pins: “Tag present”, “Read complete”, “Error”.

• PLC side: Connect these to standard digital input modules.

• Data transferred: None — only status flags. The tag ID is not transmitted.

• Best for: Applications where you only need to know that a tag is present (e.g., presence check before a press operation).

• Limitation: You cannot read the actual ID or write data.

Option 2: Serial Communication (RS232 / RS485) — Legacy but Universal

• How it works: The reader sends ASCII strings or binary frames via serial lines.

• Common protocols: Simple command-response (e.g., “READ” -> returns tag ID), or modbus RTU.

• PLC side: Requires a serial module (or converter). The PLC must parse strings — which is cumbersome in older PLCs.

• Best for: Simple point-to-point connections with low data rates, often retrofit projects.

• Drawback: Slower, and serial ports are disappearing on new PLCs.

Option 3: Industrial Ethernet (Profinet, EtherNet/IP, Modbus TCP) — The Modern Standard

This is the recommended approach for new installations.

How it works in practice:

• The RFID reader appears as a device on the Ethernet network.

• The PLC uses cyclic data exchange (e.g., every 10–100 ms) or acyclic services (on-demand) to send commands and receive tag data.

• Most RFID vendors provide prewritten function blocks (FBs) for each protocol, so you don’t need to build the low-level messaging yourself.

Example: A Balluff BIS V read/write head with Profinet interface — you import the GSDML File into TIA Portal, drag the FB into your ladder logic, and the tag ID appears in a data block.

Option 4: IO-Link — The Smart Sensor Connection

• How it works: IO-Link is a point-to-point serial protocol that runs over standard unshielded M12 cables (up to 20m). The RFID head connects to an IO‑Link master module, which then talks to the PLC via Profinet, EtherNet/IP, or EtherCAT.

• Advantage: Very simple wiring; the master automatically transfers process data (tag ID) and service data (configuration, diagnostics) to the PLC.

• Best for: Distributed architectures where you have many simple sensors and occasional RFID points.

Part 3: Step-by-Step — What the PLC Program Actually Does

Regardless of the protocol, your PLC code must follow a state machine. Below is a simplified pseudocode sequence that applies to almost all systems:

text

1.  Wait for part to arrive (e.g., photoelectric sensor = ON)
2.  Send command: "READ tag ID" to RFID reader
3.  Wait for response (typical delay: 20–200 ms)
4.  If response = OK:
        Store tag ID in PLC memory
        Compare ID to expected value(s)
        Set output: "Good" or "Reject"
    Else:
        Set alarm or retry
5.  After action, move part forward and repeat

In practice, the READ command is sent by setting certain bits in the PLC’s output data area, and the tag ID is read from the input data area. Vendor function blocks hide this complexity.

Part 4: Three Real-World Applications

Application 1: Engine Assembly Line (Automotive)

Challenge: 12 different engine types run on one mixed-model assembly line. Each requires a different set of bolts, torque values, and testing routines.

RFID solution:

• A high-frequency (13.56 MHz) RFID tag is attached to each engine carrier.

• The tag stores the engine type, target torque, and optional test results.

• At each station, a fixed read/write head reads the tag within 30 ms.

• The PLC instantly calls the correct program.

Result: 100% traceability + zero mixing errors. The line runs mixed models without manual changeovers.

Application 2: Automated warehouse (Pallet Tracking)

Challenge: A distribution center with 50 inbound/outbound gates needs to automatically identify incoming pallets and verify they belong to that gate.

RFID solution:

• UHF (860–960 MHz) tags are applied to wooden pallets (read range up to 3m).

• Overhead readers connected via EtherNet/IP to a ControlLogix PLC.

• The PLC reads the tag, compares it to the expected shipment list, and automatically directs the pallet to the correct storage zone or loading dock.

Result: Pallet read rates >99.5%; operator scanning eliminated.

Application 3: CNC Tool Presetter (Metalworking)

Challenge: A CNC machining center uses 200 different tools. If the wrong tool is loaded, the machine crashes — costing hours of downtime and expensive repairs.

RFID solution:

• Each tool holder has a high-temperature RFID tag (resists coolant and chips).

• The tool presetter writes tool geometry (length, diameter, offset) into the tag.

• On the machine, a ruggedized LF read head (immune to metal interference) reads the tag.

• The PLC verifies the tool matches the next operation’s requirement and automatically loads the correct offset data.

Result: Tool crash incidents reduced to zero. Changeover time cut by 40%.

Part 5: Choosing the Right Frequency for Your PLC Application

Practical tip: For most assembly line applications with close reading distances (5–20 cm) and occasional metal nearby, HF (13.56 MHz) is the best compromise. For exclusively metallic environments, LF is safer. For long-range logistics, UHF is the default.

Part 6: Common Pitfalls and How to Avoid Them

• Pitfall 1: Wiring the wrong protocol.
  Solution: Before buying, confirm that both the RFID reader and your PLC module speak the same protocol (e.g., don’t buy Profinet if you have an EtherNet/IP system).

• Pitfall 2: Ignoring tag placement.
  Solution: Always test the read range with the actual part material. Metal between tag and antenna kills read range.

• Pitfall 3: Writing too much data.
  Solution: On most industrial HF tags, writing 64 bytes can take 100–200 ms. For fast-moving lines, pre‑load the tag earlier or write only a small status byte.

• Pitfall 4: Forgetting about tag orientation.
  Solution: With linear antennas, the tag must be parallel to the magnetic field lines. Circular antennas are more forgiving but have shorter range.

• Pitfall 5: No retry strategy.
  Solution: Implement a retry (e.g., 1–3 attempts) and a timeout. Manufacturing environments have occasional no‑reads.

Part 7: Summary — Which Path Should You Take?

Conclusion

Integrating RFID with a PLC is not magic — it is a well‑understood Engineering task. The key decisions are:

1. Select the right frequency for your environment (LF/HF/UHF).

2. Choose a communication protocol that matches your PLC (Profinet for Siemens, EtherNet/IP for Rockwell, or Modbus TCP for everything else).

3. Use vendor function blocks to handle messaging, rather than writing raw socket code.

4. Design the mechanical and timing aspects carefully — RFID is reliable, but it is not instantaneous like a proximity switch.

PREVIOUS：Never Miss a Calibration: RFID Tool Carts for Precision Measuring Instruments NEXT：How RFID Enhances Industrial PCs for Smart Manufacturing | IPC Guide 2026