Integrating OMRON V680S RFID with Siemens S7-1500 PROFINET

1. Overview

The OMRON V680S-series HF RFID Reader/Writer is an all-in-one short-range RFID head with native support for EtherNet/IP, Modbus TCP, Ethernet TCP/IP, and PROFINET. Integrating the V680S with a Siemens S7-1500 controller (for example, an S7-1511C-1 PN with an integrated PROFINET interface) is mechanically straightforward via a GSD-based device description, but the I/O data map and bit numbering are not byte-identical between the Siemens process-image convention and the OMRON tag-bit table published in the V680S Series Reader/Writer (EtherNet/IP) User's Manual. The result is a class of faults where the PLC establishes an apparently healthy PROFINET AR, the V680S RUN LED stays solid green, the LINK/ACT LED behaves normally, yet every command returns error code 0x1003 ("Command not supported by Reader/Writer").

This reference documents the correct slot/bit assignment, the command-execution sequence, the LED diagnostics, the meaning of error 0x1003, and a step-by-step commissioning procedure that takes the integrated S7-1500 + V680S pair from a freshly downloaded hardware configuration to a verified READ ID round trip on the bench.

2. Prerequisites

3. PROFINET Topology

The S7-1511C-1 PN provides two PROFINET ports on the CPU itself; the V680S is a single-port PROFINET IO Device. Connect port 1 of the CPU (X1 P1) to the RJ45 port of the V680S via a switch for commissioning flexibility, or back-to-back for a permanent bench link.

4. TIA Portal Hardware Configuration

1. Install the latest V680S GSDML file via Options → Manage General Station Description Files (GSD).
2. Drag the V680S device from the catalog into Devices & Networks and connect it to the PROFINET subnet of the S7-1500 CPU.
3. Assign a unique IP address (e.g. 192.168.0.20) and a PROFINET device name (e.g. v680s-rfid-1).
4. In the device slots, accept the default module assignment: Slot 0 = V680S PROFINET interface with input length 32 bytes and output length 32 bytes. Verify the start addresses in the I/O address overview: Inputs typically begin at IB 256, outputs at QB 256 on a project with no other IO.
5. Compile and download the hardware configuration to the S7-1500 CPU.
6. After download, open Online & Diagnostics on the V680S device. The status field must show No fault and the AR must be in state Established. If a red X appears, resolve the topology issue first; do not attempt I/O debugging until the AR is healthy.

5. I/O Memory Map - The Core Issue

This is the single most frequent source of integration trouble. The OMRON command/response model uses one-word-aligned control and status areas starting at the head's slot-base address. With the V680S default mapping in TIA Portal the base is IB 256 / QB 256. The byte/bit layout is as follows.

5.1 Input Area (Reader/Writer → PLC) - 32 bytes from IB 256

5.2 Output Area (PLC → Reader/Writer) - 32 bytes from QB 256

6. Command Set Reference

The Command Code is placed in Word 1 of the output area (QB 257 / QB 258) in big-endian order. For example, READ ID = 0x0090 means QB 257 = 0x90, QB 258 = 0x00.

7. LED Diagnostics

8. Error Code 0x1003 - Root Cause Analysis

Error code 0x1003 in the response area (IW 258 high / IW 259 low as big-endian uint16) translates to: "A command that is not supported by the Reader/Writer was received."

Three root causes are documented in the field for this exact symptom on a Siemens S7-1500 + V680S pair:

1. Wrong EXE bit address. Most common. Setting Q257.0 (which the engineer interpreted as EXE because the OMRON manual lists EXE as bit 0 of Word 1) instead of Q256.0. The reader sees an EXE on a reserved control bit and rejects the frame.
2. Command code byte-swap. Writing the command code as little-endian (QW 258 = 0x9000 instead of 0x0090) makes the high byte non-zero. The reader interprets the high byte as a command-class extension it does not support.
3. Command issued before READY. The PLC must verify I256.0 = 1 before raising EXE. Issuing EXE while BUSY (I256.1) is still set returns 0x1003 in some firmware revisions.

9. Commissioning Procedure - READ ID Round Trip

1. Verify AR is healthy. In TIA Portal, select the V680S device and open Online & Diagnostics → PROFINET diagnostics. Confirm: AR established, no alarms, I/O data is being exchanged.
2. Open a Watch Table on the S7-1500 with the following signals:
   • Inputs (decimal): IW 256, IW 258, IW 260 - IW 267
   • Outputs (decimal): QW 256, QW 258
   • Bool triggers: I256.0 (READY), I256.3 (ERR), Q256.0 (EXE), Q256.1 (CLR_ERR)
3. Confirm READY. IW 256 must equal 1 (only READY bit set). If ERR is set, click Q256.1 to raise CLR_ERR.
4. Load the command code. Set QW 258 = 16#0090 (READ ID). This writes 0x90 to QB 257 and 0x00 to QB 258.
5. Place an HF tag on the antenna face, within the rated read distance.
6. Trigger EXE. Briefly modify Q256.0 from 0 to 1 and back to 0 (rising edge). The NORM/ERR LED should flash green once.
7. Poll for completion. Within ~200 ms I256.1 (BUSY) should clear and I256.2 (COMPL) should rise. IW 260 - IW 267 now contains the 8-byte UID of the tag in big-endian order.
8. Reset for next command. Set Q256.0 = 0. COMPL and ERR clear on the next PROFINET cycle.

9.1 Sample Watch Table Sequence

// Step 1 - Confirm READY (expect IW256 = 1)
IW256  = 1              // decimal 1
I256.3  = 0              // no error pending

// Step 2 - Load READ ID command
QW258  = 16#0090         // Command Code = READ ID (big-endian)
QB257  = 16#90
QB258  = 16#00

// Step 3 - Execute (rising edge on EXE)
Q256.0 = 0               // ensure low first
Q256.0 = 1               // trigger
Q256.0 = 0               // release

// Step 4 - Verify completion
// I256.2 should rise within 200 ms
// IW260..IW267 contains UID

10. Verification Checklist

11. Troubleshooting Matrix

12. PROFINET Cycle-Time Considerations

The V680S supports the standard PROFINET update cycle range. For RFID command latency in the 10 - 50 ms total round trip, configure:

• Send clock: 1.0 ms (default for most V680S firmware loads)
• Reduction ratio: 16 (effective update interval ~16 ms)
• Watchdog time: 3 × update interval

If COMPL detection becomes intermittent in heavily loaded PROFINET networks, increase the update interval to 32 ms. Do not exceed the V680S-recommended maximum update time of 64 ms, as this delays the EXE-to-COMPL feedback loop and may push the I257.0 (RF_WAR) bit high under marginal RF conditions.

13. Firmware and Compatibility Notes

Always confirm the V680S unit's firmware revision against the GSD file version installed in TIA Portal. Mismatched firmware/GSD combinations can silently remap control bits. If a remap is suspected, update the GSDML to the latest revision from the V680S product family support page and re-import into TIA Portal. After a GSD update, recompile the hardware configuration and re-download to the CPU; do not only reload the program blocks.

14. Alternate Platform Notes

When migrating the same V680S to a third-party PROFINET controller (e.g. Allen-Bradley ControlLogix with PROFINET Scanner module, Beckhoff CX with EtherCAT/PROFINET gateway, or Schneider M580 with BMENOC0301), the slot-base addressing and the Siemens convention above do not apply. The bit semantics remain identical (READY = Word 0 bit 0, EXE = Word 0 bit 0, command code = Word 1), but the host-specific slot mapping must be derived from the scanner's I/O mapping configuration. The error-code table and the LED behaviour are unchanged.

15. FAQ