Connecting IFM RVP510 IO-Link Encoder to Siemens LOGO! 8

Overview: The LOGO! 8 vs IO-Link Compatibility Gap

The Siemens LOGO! 8 (order code prefix 6ED1-0BA8-) is a compact logic module positioned for small-machine and building-services automation, not as a full PLC in the SIMATIC S7 family. Its native I/O and communications capability covers digital/analog on-board points, expansion modules, and Ethernet-based protocols such as S7 communication and, on firmware 8.1 and newer, Modbus TCP. The module does not include any IO-Link master port, nor does it expose the SDCI (Single-Drop Digital Communication Interface) physical layer required by IEC 61131-9.

The IFM RVP510 incremental/absolute encoder family (depending on variant) is a single-port IO-Link device (COM2 / COM3, 38.4 / 230.4 kbit/s). Because it presents its process data exclusively through an IO-Link master, the encoder cannot be wired directly into a LOGO! 8 digital input or analog input and deliver meaningful position or velocity values.

The only practical way to bring RVP510 process data into a LOGO! 8 program is to interpose an IO-Link master that exposes its upstream data over a protocol the LOGO! can speak. On the Ethernet side, that means a master with a Modbus TCP server (and optionally EtherNet/IP or PROFINET). The IFM AL1340 is a four-port IO-Link master whose Linex-Device tool exposes every connected IO-Link device as a Modbus TCP register map.

Compatibility Matrix: LOGO! Firmware vs Protocols

Source: Siemens LOGO! system manual and Siemens Industry Online Support product pages for 6ED1052-xxx08-0BA8 variants.

Understanding the IFM RVP510 Encoder

The IFM RVP510 belongs to the IFM Electronic family of magnetic, single-turn/multi-turn rotary encoders packaged in a 36 mm (or 58 mm) stainless housing. Despite common mislabeling, the RVP510 is an IO-Link absolute encoder (single-turn in the base variant; multi-turn where designated RVP5xx M). Key electrical and protocol characteristics:

• Operating voltage: 24 V DC ± 20 % through IO-Link master port L+
• Process data update: cyclic at IO-Link cycle time (minimum 2.3 ms on COM3)
• Process data length: typically 2 bytes / 4 bytes input depending on variant (position + status)
• Vendor / Device ID: assigned by IFM (vendor 0x015D = 349 decimal); IODD required for full parameter decoding
• Connection: M12 A-coded 4-pin or 5-pin (L+, L-, C/Q, OUT2 on 5-pin variant)
• Resolution: device-specific (12-16 bit single-turn typical; check IODD)
• Port class: Class A (4-pin) or Class B (5-pin, isolated supply)

Because the device speaks only IO-Link on its M12 connector, the LOGO! 8 cannot read it without a master.

Architecture: IO-Link to Modbus TCP Bridge

The reference topology inserts an IO-Link master between the encoder and the LOGO!. The master acts as a gateway, terminating the SDCI layer and re-publishing the process data over Modbus TCP registers.

+------------------+        IO-Link (SDCI)        +--------------------+        Modbus TCP / S7        +------------------+
| IFM RVP510       |  <-------------------------->  | IFM AL1340         |  <--------------------------->  | Siemens LOGO! 8  |
| IO-Link encoder  |   M12 A-coded, 24 V, COM3   | IO-Link master (4P) |   10/100 Mbit, Cat5e         | 0BA8.FS04+       |
| Class A or B     |                              | 192.168.0.x         |                               | 192.168.0.y       |
+------------------+                              +--------------------+                                +------------------+
                                                          |
                                                          +--> Optional: additional IO-Link devices on ports 2-4
                                                          +--> Optional: EtherNet/IP or PROFINET to a higher-level controller

The IFM AL1340 (also sold as AL1341 / AL1342 variants) is a four-port IO-Link master with an M12 D-coded Ethernet uplink. Each IO-Link port exposes a cyclic process-data image and an acyclic parameter channel, both accessible over Modbus TCP. The master itself is a Modbus TCP server, so the LOGO! becomes the Modbus TCP client.

IFM AL1340 Master Configuration

Commissioning of the AL1340 is performed through the IFM Linex-Device (LRD) web interface or the moneo|configure software. The following parameters must be set before integrating with LOGO!.

1. Assign a static IPv4 address (DHCP is acceptable in test setups, but is non-deterministic and should not be used in production).
2. Set the Modbus TCP TCP port (default 502).
3. Enable Modbus TCP server, disable any password requirement for commissioning.
4. Connect RVP510 to Port 1 (or any port) using a shielded M12 A-coded cable. Verify the master shows the device in the topology view with a green status LED.
5. Import the IODD file for the RVP510; the master will then decode the process-data structure and assign Modbus register addresses automatically.
6. Record the base register address (typically 0x0000 for process input data, 0x0800 for parameter data). The exact mapping depends on the device; always read it from the AL1340's process-data table, not from external documentation.

References: IFM AL1340 operating instructions, available in the IFM online documentation portal.

LOGO! 8 Modbus TCP Client Configuration

The LOGO! 8 (firmware 8.1 / 0BA8.FS04 and newer) supports Modbus TCP as a client. It initiates connections, sends requests, and decodes responses in the user program. The corresponding blocks in LOGO!Soft Comfort are Network Input (NI) and Network Output (NQ) in the "Network" function group.

The LOGO! allows up to eight concurrent client connections on firmware 8.1+. Each NI/NQ pair occupies one connection slot. The AL1340 supports up to eight simultaneous Modbus TCP clients, so the LOGO! can subscribe to multiple IO-Link devices without exhausting the master.

Process Data Mapping Example (32-bit Position)

The exact Modbus mapping depends on the IODD of the connected device. The following is a representative example for an absolute position register:

Decoding in LOGO!Soft Comfort: combine NI word 1 (low) and NI word 2 (high) using the Analog Math or Math function block to reconstruct a 32-bit unsigned integer. Multiply the high word by 65536 and add the low word:

Position = (NetworkInput_HighWord x 65536) + NetworkInput_LowWord

LOGO!Soft Comfort Program Skeleton

The reference ladder structure to read position and convert it to an engineering unit (e.g., degrees) is:

1. NI block configured as Modbus TCP client targeting 192.168.0.50:502, FC 04, register 0x0000, length 2.
2. Math block: PositionRaw = NI_word_high * 65536 + NI_word_low.
3. Analog Gain/Offset block: PositionDeg = (PositionRaw / 65535) * 360 to scale the 16-bit value to 0-360 degrees. Adjust for the encoder's actual resolution.
4. Threshold Trigger: compare PositionDeg against setpoints for high/low limits.
5. Output Q1: drive a relay or solid-state output based on the threshold.

The same network can be extended with an NQ block to write parameters back to the RVP510 (e.g., preset position) using FC 06 (single register) or FC 16 (multiple registers).

Wiring and Topology Notes

Field wiring is straightforward but has pitfalls:

• Power: The AL1340 requires 24 V DC on its M12 L-coded power inlet. Provide 1 A per IO-Link port plus 200 mA for the master's own electronics.
• Ground: Bond the functional earth (FE) of the AL1340 to the cabinet PE bus with a short, low-impedance strap. Poor grounding produces IO-Link communication faults that mimic encoder failure.
• Cable length: Maximum IO-Link cable length is 20 m for non-shielded cables and 20 m for shielded (the limit is set by IEC 61131-9 capacitive loading, not by the master).
• Ethernet: Use Cat5e or higher between the AL1340 and the LOGO! 8's RJ45 port. The LOGO! 8 has only one Ethernet port; if the program also needs connection to LOGO!Soft Comfort for live editing, isolate the network or use a managed switch with VLAN segmentation.
• IP addressing: Keep LOGO! and AL1340 on the same /24 subnet; do not route Modbus TCP across layer-3 boundaries without QoS.

Verification and Commissioning Checklist

1. Power up the AL1340, confirm all four port LEDs show steady green (no IO-Link attached) or flashing green (IO-Link communication active).
2. Connect the RVP510 to port 1; verify the LED transitions from steady to flashing within 2-3 seconds.
3. Open the AL1340 web interface; verify the device name, vendor ID 0x015D, and process-data length match the IODD.
4. From a PC on the same network, use a Modbus TCP test client (e.g., modpoll, QModMaster) to read registers 0x0000-0x0003 and confirm non-zero, plausible data when the encoder shaft is rotated.
5. Configure the LOGO! NI block with the same target IP, port, function code, and register range as the test client.
6. Use the LOGO!Soft Comfort online monitor to verify the NI value updates at the configured poll rate.
7. Insert a temporary output or message-text block displaying the decoded position to confirm scaling.
8. Disconnect the encoder cable to validate the LOGO! error path: the NI block should hold the last good value or output zero, depending on the LOGO! version's NI failure mode.

Troubleshooting Matrix

Alternative Encoder Recommendations

If the LOGO! 8 is fixed in scope and adding an IO-Link master is not economically justified, consider encoders with protocols the LOGO! supports natively:

• Modbus TCP absolute encoders: IFM RM7xxx / RVP7xx variants, Sick AFM60 Ethernet, Kübler 8.5800 series. Connect directly to the LOGO! NI block without an intermediate master.
• Pulse-train encoders: standard HTL/TTL 24 V incremental encoders connected to the LOGO! 8 high-speed digital inputs (I3-I6 on the base module, I7-I8 on the AM2 expansion). Use the Frequency or Counter function blocks.
• EtherNet/IP encoders: not supported on LOGO! 8. Escalate to a SIMATIC S7-1200 if EtherNet/IP is required.

For systems where IO-Link is mandatory (sensor-actuator standardization across a factory), upgrading from a LOGO! 8 to an S7-1200 with an SM 1278 4-port IO-Link master removes the gateway and gives direct access to the IO-Link device via S7 function blocks. The S7-1200 also exposes the full acyclic parameter channel via the IODD interpreter, which the LOGO! cannot reach through Modbus TCP.

Performance and Timing Considerations

The end-to-end latency from the encoder shaft to a LOGO! coil is the sum of:

1. IO-Link cycle time (T_cyc): typically 2.3 ms on COM3 for short process data; up to 132 ms on COM2 with maximum cable length.
2. AL1340 internal processing and Modbus TCP response assembly: ~5-10 ms.
3. Ethernet round-trip: ~1 ms on a switched /24 network.
4. LOGO! scan cycle: 5-50 ms depending on program size; the Modbus NI block updates once per scan.

Expect 15-60 ms total latency. For closed-loop position control, this is too slow; treat the LOGO! as a supervisory controller for monitoring, threshold detection, and indication, not as a motion controller. If sub-millisecond response is required, move to a SIMATIC S7-1500 or a dedicated motion controller.

Cybersecurity and Network Hardening

IO-Link and Modbus TCP are clear-text protocols with no authentication in their standard forms. For any installation reachable beyond a closed cabinet network:

• Place the LOGO! 8 and AL1340 behind a managed switch with port isolation.
• Disable unused services on the AL1340 (web UI, FTP, MQTT, OPC UA) unless required.
• Enable the AL1340 Modbus TCP "write protection" if the application is read-only.
• Do not expose the LOGO! 8's Ethernet port to a corporate network without the LOGO! CMR firewall or a separate industrial firewall (e.g., Scalance S615).
• Lock the LOGO! 8 program with the project password to prevent unauthorized ladder edits.

References to Official Documentation

• Siemens Industry Online Support – LOGO! 8 system manual, entry ID 109744658.
• Siemens LOGO! product page – firmware revision history and order codes.
• IFM Electronic product documentation portal – RVP510 datasheet and IODD, AL1340 operating instructions.
• IO-Link Consortium – IEC 61131-9 SDCI specification and IODD finder.
• Modbus Organization – Modbus Application Protocol V1.1b3 specification.

FAQ