When communication between the Programmable Logic Controller (PLC) and the Factory Talk VIEW supervisory system is interrupted, the object in the supervisory system remains a neutral color instead of becoming transparent. This issue is not related to the watchdog function. Are there any internal tags in the supervisory system that indicate a loss of communication with Factory Talk VIEW?
For users seeking information on device tags, try checking the Diagnostics folder instead of the online folder. It is likely to contain tags indicating communication failures from Linx.
In the FactoryTalk Live Data connection, you can monitor predefined items such as @IsPresent and @mode that originate from the FactoryTalk Linx application's status. These items are thoroughly explained in the RSLinx Classic Help file. If you are looking to customize the wireframing behavior of a screen object when it loses connection to its data source, you may be describing a modification to its functionality.
Ken Roach mentioned that there are "Predefined Items" available for monitoring the connection between FactoryTalk Live Data and the controller. @IsPresent and @mode are commonly used, originating from the FactoryTalk Linx application status. These are well explained in the RSLinx Classic help file. However, perhaps you are looking to modify the "wireframing" behavior of a screen object when it fails to retrieve data from its source. Thank you. Indeed, I need a tag to animate an object on the FT screen when communication with the PLC is lost.
Ken Roach mentioned the use of "Pre Defined Items" for monitoring the FactoryTalk Live Data connection with the controller. Popular tags like @IsPresent and @mode are sourced from the FactoryTalk Linx application's status, as detailed in the RSLinx Classic Help file. If you're looking to customize a screen object's behavior in the absence of data from its source, consider making modifications to the "wireframing." Additionally, a tag on FT can indicate when the plc is offline.
Ken Roach explains the use of "Pre Defined Items" for monitoring the FactoryTalk Live Data connection to the controller. Popular options include @IsPresent and @mode, which are derived from FactoryTalk Linx application's status and well-documented in the RSLinx Classic Help file. Perhaps you are seeking to customize the behavior of a screen object when it loses communication with its data source, also known as "wireframing." In that case, you may require a tag for animating objects on the FactoryTalk screen during PLC communication disruptions.
While there might not be specific tags that indicate a loss of communication with Factory Talk VIEW, you might want to consider using system tags that are associated with the connection status of your supervisory system. You can assign a color change or some sort of indicator to these system tags for visual feedback. This way, if any disconnection occurs between PLC and Factory Talk VIEW, this modified indicator would show the disruption. Furthermore, you may also want to check the communication setup in Factory Talk VIEW to ensure its properly configured.
While I agree there could be an underlying system feature aimed at indicating a loss of communication, Factory Talk VIEW doesn't inherently track communication status with PLC via internal tags. However, a practical workaround might be to construct your own heartbeat or watchdog routine in the PLC, then link a Factory Talk VIEW object's visibility or color to that tag. If the comms fail, the watchdog timer will expire, changing the status of your tag, thus reflecting the issue in the supervisory system.
✅ 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: The issue could be unrelated to the watchdog function and may be due to other factors affecting the communication between the PLC and the supervisory system.
Answer: Answer: It is possible that there are internal tags within the supervisory system that are designed to indicate a loss of communication with the PLC, helping in troubleshooting and identifying the root cause of the issue.
Answer: Answer: In such cases, it may be necessary to investigate other potential causes of communication interruption, review network settings, check for software configurations, and consider any hardware issues that could be impacting the connection between the PLC and the supervisory system.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.