View the snapshot of the EIP tag list to locate the designated digital input labeled as I31.1, which is connected via hard-wiring. It appears that reading specific bits of a tag may not be possible in this scenario. How should we address a channel from a remote IO like "RS2_AENTR"? The format for a local IO would typically be "Local:1:I.Ch01.Data." Alternatively, consider using "RS2_AENTR:1:I.Data" or "Local:1:I.Data[bit_number]" for bit addressing. Uncertainty remains regarding the addressing syntax for remote I/Os, such as I31.1. Our objective is to successfully display this particular bit.
If you are unsure, I am eager to learn the methods for locating this information in the future.
What is the designated name for the EIP device that will be integrated into the tag address? How does the device appear within the tag database?
Hey Ken, are you talking about the RS2_AENTR model?
Yes, he is discussing the RS2_AENTR. Is that the name listed in the device tree? Can you clarify where you are attempting to showcase it? If you are utilizing FactoryTalk View Studio, please note that the tag browser does not support direct addressing of bits. In the tag browser, make sure to choose the base tag, I31, and then manually add .1 to the end of it within the Selected Tag box at the bottom of the browser. This will allow you to accurately address the specific bits you need.
MikeyN mentioned the RS2_AENTR. Is this the corresponding name in the device tree? Where are you aiming to showcase it? If you are utilizing FactoryTalk View Studio, addressing bits directly in the tag browser is not allowed. Instead, select the base tag, I31, and manually append .1 to the end in the Selected Tag box at the bottom of the browser. Hey Mike, I am employed at a SaaS company that generates displays similar to SCADA, allowing customers to view machine activity without control capabilities. For instance, I am currently working on incorporating a whisker counter bit from a conveyor. While I have not attempted to include single bits like this before, our software team assures me it is feasible.
In this scenario, we are dealing with addressing a complex remote I/O, so the syntax will be a tad bit different. Typically, the RSLogix or Studio 5000 environment would be beneficial in sorting out the syntax. That said, your attempt with "RS2_AENTR:1:I.Data" might work, replacing I with the input module number, and Data with the bit you're looking to address. Let's say an example string could be "RS2_AENTR:4:I.Data[3]", where 4 is your input module and 3 is your desired bit. Just remember to keep the slot number (1) the same if that's where you've placed your remote adapter. Always keep in mind, your I/O configuration and your PLC program must match, or else it's not going to function as anticipated. I would recommend doing some more digging into the user manual specifically designated for your I/O model for more information.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: To address a channel from a remote I/O like "RS2_AENTR," you can use formats such as "RS2_AENTR:1:I.Data" or "Local:1:I.Data[bit_number]" for bit addressing.
Answer: Answer: It seems that reading specific bits of a tag like I31.1 may not be possible in this scenario.
Answer: Answer: The addressing syntax for remote I/Os like I31.1 could potentially be "RS2_AENTR:1:I.Data" or "Local:1:I.Data[bit_number]."
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.