Hello everyone, I have developed an application using the FT ME Edition along with the RSLogix 500 program, utilizing offline tags. My process began by importing an .EAS file, which successfully brought in all the necessary tags, including their symbols and addresses. This allowed me to create various screens and establish connections with the components, utilizing these tags for direct referencing. In the communication setup, I created a shortcut with a placeholder Ethernet address of 10.1.2.34. Once all the screens were completed, I moved on to test my application with a different PLC, currently operating at the address 10.2.3.45. To facilitate this, I set up a new communication path in the communication settings by selecting Ethernet and entering the IP address of the second PLC. However, as soon as I initiated the test application, I encountered some unusual messages in the diagnostics banner. One error indicated that the tag was incorrect, while another stated that it failed to connect to 10.1.2.34. I am uncertain about the steps I should take next. Could anyone provide guidance or suggestions on how to resolve this issue? Thank you!
I’m having trouble comprehending the issue at hand, so let’s go over some common factors that are often overlooked. If the tags are directly linked to the PLC within the HMI software, they should appear as follows: ::[PLC]B3:0/0. In this scenario, it’s crucial to ensure that the shortcut name you've assigned to the secondary PLC connection in the communication settings matches the shortcut name found in the tag addresses. This name is represented within the brackets—in my example, it’s "PLC." If the tags only contain a tag name, you will need to explore the tag database and check the tag information to identify the connection address. Again, confirm that the shortcut name associated with this address aligns with the shortcut name assigned to the PLC you wish to connect with. For instance, if you have an object on your HMI screen referencing ::[PLC1]B13:10/0, it's essential to verify that the PLC you are testing actually contains B13:10/0 in its program. If these addresses are absent on the PLC, your HMI program will inevitably return a communication error. Additionally, once you have configured your connections, don’t forget to click the "Copy to Runtime" option located in the top right corner of the communication setup screen. The application won't utilize the communication setup if this step is overlooked. If you’ve followed all the steps and still lack connection, it’s important to ping each device from your workstation to confirm they can communicate with one another. I noticed that your IP addresses have differing values in their third subnet—do you have a router in place to facilitate communication among these devices? Networking is often a challenging area for me, but typically, devices with varying values in the first three segments of their IP addresses do not communicate unless there is a router to manage the data exchange. If none of these suggestions resolve the issue, please provide more detail about your problem to assist me in understanding it better. As I mentioned, I’m finding it difficult to grasp the original post.
LoganB stated, "I'm not entirely clear on the issue at hand, so let me highlight a few key points that are often overlooked." First, when dealing with tags that are directly linked to the PLC within the HMI program, they typically follow the format: ::[PLC]B3:0/0. In this scenario, it's crucial to ensure that the shortcut name designated for the second PLC connection in your communication setup matches the shortcut name used in the tag addresses—this name appears between the brackets (e.g., "PLC" in my example). If the tags consist solely of tag names, you should explore the tag database and examine the tag information to determine the corresponding connection address. Again, it’s vital to confirm that the shortcut name in this address aligns with the shortcut name assigned to the specific PLC you aim to connect to. For instance, if an object on your HMI screen is linked to ::[PLC1]B13:10/0, confirm that the PLC you intend to test indeed includes a B13:10/0 in its program code. If these addresses are not present on the PLC, your HMI program will generate a communication error. Additionally, after configuring your connections, don't forget to click the "Copy to runtime" option located in the top right corner of the communication setup screen. The tested application will not utilize the communication setup unless this step is taken. If you’ve followed all these instructions and are still unable to establish a connection, check if you can ping all the devices from your workstation to confirm that they can communicate effectively. I noticed that your IP addresses differ in their third octet; is there a router present to facilitate their communication? While networking is not my area of expertise, I understand that devices with different values in the first three octets of an IP address typically require some form of routing to exchange messages. If none of this guidance proves useful, please provide additional details about your issue so that I can better assist you, as I'm struggling to fully grasp the original post. Thank you, Logan, for addressing nearly everything I needed clarification on.
LoganB commented: It seems there may be some confusion regarding the issue at hand. Let's go through some commonly overlooked aspects that may help clarify things. If your tags are specifically linked to the PLC within the HMI program, they will typically be formatted as follows: ::[PLC]B3:0/0. In this scenario, it's crucial to ensure that the shortcut name you assigned to the second PLC connection in the communication setup directly matches the name used in the tag addresses—this is the term found within the brackets, "PLC" in this instance. If the tags are merely using a tag name, you'll need to explore the tag database to access the tag information, which will reveal the associated connection address. Again, confirm that the shortcut name specified in this address aligns with the shortcut name you designated for the PLC you intend to connect with. For example, if there is an object on your HMI screen assigned to ::[PLC1]B13:10/0, make certain that your testing PLC contains a corresponding B13:10/0 in its program. Should these addresses not correspond with what exists on the PLC, your HMI program will likely display a communication error. Additionally, after configuring your connections, don't forget to select the "Copy to runtime" option located in the communication setup at the top-right corner of the screen. The application will not utilize the communication setup unless this step is taken. If you have completed all these steps and are still experiencing connectivity issues, it's vital to ensure that you can ping all devices from your station, confirming they can communicate effectively. I noticed that your IP addresses differ in their third subgroup. Is there a router in place ensuring these devices can interact? Networking is not my strongest suit, but I understand that devices with different values in the first three parts of their IP addresses typically do not communicate unless a router facilitates the connection. If this information does not resolve your issue, please provide more details to help me better understand the problem, as I'm finding it challenging to grasp the original post. On a related note, I have successfully created all the screens, and everything is functioning well—thank you, Logan. However, I encountered a runtime error on a few screens. Upon investigation, I found a common issue among them: the usage of inputs like I:3/31 or I:6/20. I'm puzzled as to why the application is not flagging errors for input bits 0 to 15, such as I:2/7, yet it is generating errors for bits 16 to 31. The runtime error displayed is framing the issue as "tag has an error at ::[shortcut]I:3/31."
The registers employed in the RS500 architecture are 16-bit in size.
Chopin has mentioned that the registers utilized in the RS500 system are 16-bit. Upon reviewing the PLC program, I noticed that I:3/31 is currently being employed. Should we consider assigning the value I:3.1/15?
✅ 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: 1. Open the FactoryTalk View Studio and navigate to the Communication Setup. 2. Select the existing shortcut and edit it. 3. Change the Ethernet address to the IP
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.