Resolving Siemens RF615R OPC UA Error 17 DEVICE_NOT_READY

Problem Overview

The SIMATIC RF615R UHF RFID reader exposes an embedded OPC UA server that allows SCADA, MES, and PLC clients to read tag data, subscribe to read events, and trigger read operations on configured read points. On firmware V4.2, an OPC UA client can establish a session (anonymous or certificate-based), browse the address space, read tag records produced by the last successful scan, and subscribe to event notifications without issue. Calls to the Scan or ScanStart method on a read point, however, return OPC UA status Bad_DeviceNotReady with the symbolic name DEVICE_NOT_READY, the internal numeric code 17, and the description "The specified read point is not active because no antenna was assigned to it." The reader's status LED changes from green to a blinking red pattern, the WBM Logbook writes an OPC UA error 17 entry tied to the offending read point, and the Service Logbook adds a corresponding ReadPointMethodError line. The same read point continues to operate correctly when the operator initiates a scan from the WBM Diagnostics page, which makes the failure look inconsistent.

This article consolidates the root cause, the diagnostic workflow, the corrective procedure, and the verification steps for OPC UA scan-method failures on the SIMATIC RF615R and the related RF600 family readers. The guidance applies to OPC UA clients built with the official SIMATIC RF615R OPC UA test application, custom Python clients using the opcua library, Kepware, Ignition, the Siemens OPC UA Scout, and the SIMATIC Ident Configuration Tools.

Affected Hardware and Firmware

Symptom Summary

The following symptoms, all observed simultaneously, form the diagnostic fingerprint of the issue:

• OPC UA session establishment succeeds (anonymous or with x509 certificate + user token).
• Browsing the address space succeeds; the ObjectsFolder > DeviceSet > RF615R > ReadPointCollection > ReadPoint_1 node is visible.
• Reading tag data (e.g., LastEPC, LastRSSI, LastAntenna) returns the most recent cached scan result.
• Event subscriptions (e.g., TagSeenEventType) deliver prior events but stop firing once the failure begins.
• Calling Scan or ScanStart on ReadPoint_1 returns Bad_DeviceNotReady / numeric 17 / DEVICE_NOT_READY.
• The WBM Diagnostics > Read Point "Start" button continues to scan successfully and populates the tag list.
• The reader status LED transitions from solid green to a repeating red blink pattern, even though physical RF transmission is still active.
• WBM Logbook contains: OPC UA error 17 ReadPointMethodError.
• WBM Service Logbook contains: Read point not active: no antenna assigned to read point 1.

Two facts are essential: (1) the OPC UA path is healthy enough to read cached data, which rules out transport, certificate, and authentication problems; (2) the WBM-initiated scan works, which rules out RF hardware failures, antenna cabling, and tag compatibility. The defect is therefore a configuration-state mismatch on the read point, not a transport or hardware fault.

Root Cause Analysis

Two independent configuration conditions on the SIMATIC RF615R prevent an OPC UA client from calling Scan or ScanStart on a read point. Either condition can produce the same observable status 17 in the logbook. A third, rarer condition produces the literal error message wording. All three must be inspected during diagnosis.

Cause 1 — Read Point in "Parallel" (Continuous) Scan Mode

The RF615R supports two scan-timing models for each read point: triggered and parallel / continuous. In triggered mode, the read point is idle until a trigger fires (WBM button, OPC UA method, or external digital input). The OPC UA methods Scan, ScanStart, and ScanStop are valid and behave as documented.

In parallel mode, the read point begins scanning as soon as the configuration is activated and continues indefinitely in a round-robin over the assigned antennas. A read point in parallel mode is internally flagged as "always scanning." The OPC UA server rejects Scan and ScanStart on a read point that is already scanning, because the call would be a no-op or could corrupt the internal scan state machine. The reader's internal status returns 17 (DEVICE_NOT_READY) with the misleading description referencing the antenna assignment, which is a known behavior on firmware V4.2.

The "parallel" name in the WBM is counter-intuitive: it does not mean "operate OPC UA and WBM in parallel." It means "operate the read point in continuous, non-triggered mode." Disabling the parallel option returns the read point to triggered mode, where OPC UA scan methods are accepted.

Cause 2 — A Trigger Is Bound to the Read Point

When a digital input, a logical condition, or an internal cyclic trigger is bound to a read point, the read point is also treated by the firmware as "permanently active" even if the parallel option is disabled. The trigger fires the scan automatically and re-arms, so the firmware again rejects Scan and ScanStart as redundant. The status code returned is identical to the parallel-mode case.

Triggers are configured under WBM > Configuration > Read Points > select the read point > Triggers. Common entries on a fresh project include:

• Trigger_1 bound to digital input DI0 of the reader's M12 port.
• Trigger_2 bound to a cyclic 250 ms timer.
• Trigger_3 bound to a PLC tag over the PROFINET or EtherNet/IP interface.

Removing the trigger binding and reloading the configuration to the reader clears the second cause.

Cause 3 — No Antenna Assigned to the Read Point

The literal interpretation of the error description ("no antenna was assigned to it") is a third, rarer cause: the read point configuration has zero antennas bound. This is the case when the WBM Configuration > Read Points > Antennas list is empty. The OPC UA method call short-circuits with the same status 17. Always verify this condition first because it is the cheapest to check and the most common commissioning mistake.

Diagnostic Procedure

Run the following checks in order. Each step is independent of OPC UA; they can all be performed from the WBM, which removes the client from the equation.

1. Log in to WBM at https://<reader-IP> using an administrator credential. The default user is admin with the password configured during first commissioning.
2. Open the Logbook. Navigate to Diagnostics > Logbook. Filter for entries containing OPC UA and 17. Confirm that the timestamp of the error matches the timestamp of the client call.
3. Open the Service Logbook. Navigate to Diagnostics > Service Logbook. Look for ReadPointMethodError and the descriptive message. Capture the exact text into the support ticket.
4. Inspect the Read Point configuration. Navigate to Configuration > Read Points. Select the read point named in the OPC UA call. Under Antennas, verify that at least one physical antenna port (Ant1, Ant2, Ant3, Ant4) is listed and enabled.
5. Inspect the Read Point scan mode. On the same Read Point page, locate the Parallel mode or Continuous mode checkbox. Note its state.
6. Inspect the Triggers tab. On the Read Point page, open the Triggers sub-page. Note any configured triggers and their sources.
7. Trigger a scan from the WBM. Navigate to Diagnostics > Read Point, select the read point, and click Start scan. If this works, the RF chain, antennas, and tag inventory are healthy. The failure is isolated to OPC UA method handling.
8. Test ScanStop first. From the OPC UA client, call ScanStop on the read point. This forces the read point out of any active scan state, regardless of mode. Then re-attempt Scan or ScanStart. If the retry succeeds, the read point was in continuous mode and the ScanStop call broke the lock.
9. Export the configuration. Click the floppy disk icon in the WBM toolbar to download the current configuration file (.rfc or .xml). Attach it to the support ticket so a Siemens specialist can verify the read point mode and trigger bindings offline.

Resolution

Three corrective paths are available. Apply them in the order listed, then verify.

Resolution Path A — Clear the Parallel / Continuous Mode

1. In the WBM, navigate to Configuration > Read Points and select the affected read point.
2. Locate the Parallel mode option (also labeled Continuous scanning or Cyclic scanning depending on firmware minor revision) and disable it.
3. Click Apply or Save.
4. Click the Load to device (or Transfer to reader) button to commit the change to the reader's non-volatile memory. The reader will restart the read point service, not the full reader.
5. Wait for the read point to enter the Idle state in the WBM Diagnostics view.

Resolution Path B — Remove the Trigger Binding

1. In the same Read Point page, open the Triggers sub-page.
2. For each trigger listed, click the Delete (trash can) icon or uncheck the Active checkbox.
3. If a trigger is referenced from a higher-level object (such as a PROFINET slot), remove the reference there as well. Open Configuration > Interfaces > PROFINET and inspect the input assignment for the trigger word.
4. Click Apply, then Load to device.

Resolution Path C — Restore an Antenna to the Read Point

1. Open Configuration > Read Points and select the read point.
2. Open the Antennas sub-page.
3. Check the box next to each antenna port that is physically connected (Ant1 through Ant4).
4. Set the radiated power (in dBm) and the antenna gain (in dBi) to match the physical antenna datasheet.
5. Click Apply, then Load to device.

Verification

After the corrective steps, run the following verification sequence.

1. WBM scan test. From Diagnostics > Read Point, start a manual scan. Confirm that the tag list populates within the configured scan timeout (default 5000 ms).
2. OPC UA Scan method. From the OPC UA client, call Scan on the read point with a short timeout (for example, 2000 ms). The call must return Good. The response contains the number of tags read.
3. OPC UA ScanStart and ScanStop methods. Call ScanStart to start a continuous scan from the client. Confirm that the read point's status changes to Scanning in the WBM. Call ScanStop after 5 seconds. Confirm that the status returns to Idle.
4. Logbook regression check. Open the WBM Logbook and filter for the last hour. Confirm that no new OPC UA error 17 or ReadPointMethodError entries are present.
5. Event subscription check. From the OPC UA client, subscribe to TagSeenEventType. Place a known tag in front of the antenna. Confirm that the event fires with the correct EPC, RSSI, and antenna ID.
6. Configuration persistence. Power-cycle the reader (disconnect and reapply the 24 V supply). Re-run steps 1 to 3. The changes must persist, confirming that the configuration was committed to non-volatile memory.

OPC UA Method and Read Point Reference

The RF615R OPC UA address space follows the OPC UA Companion Specification for RFID. The methods under the ReadPointType are summarized below.

The GetLastScan method is the reason a malfunctioning client still "appears" to work: it returns the last cached scan result without engaging the scan state machine. This explains the original report that "I can see the result of the last scans, but scan or scan-start actions don't work."

Read Point Configuration Parameters

The read point is the logical grouping of antennas and triggers that the OPC UA server exposes. A correct read point configuration is the foundation of OPC UA scan reliability. The following table summarizes the settings and their impact on OPC UA method behavior.

Network, Security, and Client Integration

Endpoint and Discovery

The RF615R OPC UA server listens on TCP port 4840 by default. The endpoint URL is:

The server publishes an OPC UA discovery endpoint on the same port. The discovery URL follows the same pattern. With the default WBM configuration, the server exposes two security policies:

• None with anonymous authentication (development use only).
• Basic256Sha256 with x509 certificate authentication and optional user-token policy (Username / Password or Certificate).

For production deployments, disable the None policy under WBM > Security > OPC UA > Endpoint Configuration, generate a server certificate with at least a 2048-bit RSA key, and push the certificate to the OPC UA clients in their trust store.

Client Code Example (Python, opcua Library)

The following Python snippet demonstrates a robust client wrapper that performs the recommended ScanStop pre-flight check, calls Scan, and parses the result. Adapt the endpoint URL and NodeId to match the project configuration.

from opcua import Client, ua

client = Client("opc.tcp://192.168.0.50:4840")
client.set_security_string("Basic256Sha256,Sign,certificate.der,private_key.pem")
client.connect()

read_point = client.get_node("ns=4;s=ReadPoint_1")

# Defensive pre-flight: force idle
try:
    read_point.call_method("4:ScanStop")
except ua.UaStatusCodeError as e:
    if e.code != ua.StatusCodes.Bad_Busy and e.code != ua.StatusCodes.Bad_DeviceNotReady:
        raise

# Execute a one-shot scan
status, out = read_point.call_method("4:Scan")
print("Scan status:", status, "tags:", out)

client.disconnect()

Client Code Example (Python, Plain Asynchronous Scan Loop)

import time
from opcua import Client, ua

client = Client("opc.tcp://192.168.0.50:4840")
client.connect()
rp = client.get_node("ns=4;s=ReadPoint_1")

rp.call_method("4:ScanStart")
try:
    for _ in range(5):
        time.sleep(1)
        ev = client.get_node("ns=4;s=ReadPoint_1_LastEPC").get_value()
        if ev:
            print("Tag seen:", ev)
finally:
    rp.call_method("4:ScanStop")
    client.disconnect()

Integration with TIA Portal and SIMATIC Ident

When the RF615R is connected to a SIMATIC S7-1200 or S7-1500 controller over PROFINET, the SIMATIC Ident function blocks (FB 119 "IDENT_CONTROL", FB 126 "IDENT_DEMO") communicate with the reader through the Ident profile. OPC UA on the RF615R can run alongside PROFINET, but the read point used for the PLC should be a different read point than the one used for OPC UA control. Sharing a single read point between the PLC and an OPC UA SCADA causes the same status 17 because the PLC's cyclic trigger keeps the read point in the "always scanning" state from the OPC UA server's perspective.

Error Code Reference

The RF615R returns a numeric status code in the WBM Service Logbook that maps to an OPC UA status code and a symbolic name. The mapping for firmware V4.2 is summarized below.

Best Practices and Preventive Configuration

Apply the following configuration discipline on new deployments to prevent the issue from recurring.

1. One mode per read point. Decide between triggered-by-client (no parallel, no triggers) and triggered-by-hardware (triggers from PLC or DI) at design time. Mixing them on a single read point will produce intermittent status 17 errors.
2. Always call ScanStop before Scan. Even on a read point that is believed to be idle, a defensive ScanStop call clears any stale scanning flag. Treat it as a one-line pre-flight check in every client wrapper.
3. Use a separate read point for OPC UA control. On a project that also drives the read point from a PROFINET PLC, create two physical read points: one for the PLC trigger path, one for the OPC UA control path. This isolates the two control domains and prevents accidental contention.
4. Apply the configuration, then power-cycle. WBM changes are not durable until Load to device is clicked. After loading, perform a controlled 24 V power cycle to validate that the change persisted.
5. Tag the configuration file. Save the exported .rfc configuration into version control with a commit hash and the reader's serial number. This makes a future rollback a single file restore.
6. Lock the WBM admin role. Disable anonymous WBM access. Require a strong, rotated password. An attacker on the OT network can otherwise re-enable parallel mode remotely and disrupt production.
7. Monitor the OPC UA diagnostics page. Periodically poll Server_ServerStatus_State and Server_ServerStatus_StartTime to detect silent restarts of the OPC UA server, which often coincide with WBM configuration reloads.
8. Disable unused security policies. The WBM allows simultaneous exposure of the None and Basic256Sha256 policies. In production, leave only Basic256Sha256 enabled to prevent credential downgrade attacks.

Frequently Asked Questions