Update your settings

RFID RF685R Attribute Handling in TIA Portal Basic

Hello,

You've encountered a common issue when working with RFID RF685R readers and TIA Portal Basic. Yes, there are limitations when switching between different attribute IDs within the same project and block instances.

Here's why you're seeing errors:

• Attribute Locking: The RFID reader often 'locks' onto the initially used attribute set (16#86/87 for presence detection) within a specific inventory block instance. Subsequent attempts to read different attributes (16#80/81 for data) using the same block instance often fail.
• Reset Reader Limitations: While the "Reset Reader" block is helpful, it doesn't always fully clear the previous attribute lock, especially within the TIA Portal Basic environment.

Recommended Solution:

1. Separate Inventory Blocks: The most reliable method is to create separate Inventory blocks in your TIA Portal project – one specifically for presence detection (16#86/87) and another dedicated to reading data (16#80/81). Each block should have its own instance.
2. Instance DBs: Ensure each Inventory block instance has its own dedicated Data Block (DB) for storing its results.
3. Sequential Operation: If you need to read data immediately after detecting presence, structure your code to first complete the presence detection inventory block cycle, then trigger the data reading inventory block.

For more detailed information and examples, please refer to the following resources in SiePortal:

• RFID - How to read the user memory of an RFID tag with SIMATIC RF685R
• TIA Portal: Using the Inventory block for RFID - How to find the correct settings

If you continue to experience issues, please provide your TIA Portal project version and a more detailed description of your code for further assistance.