While developing a project involving the interaction of the FT View application with a PLC through an OPC UA server, I encountered a peculiar issue. A simple test can be replicated by placing two indicators on a display, each linked to OPC UA tags from separate devices. Everything functions correctly until one of the devices goes offline. At that point, all indicators on the display fail to work. I am seeking assistance in resolving this issue. Is this a common problem within my project or is there a known solution available? Your help is greatly appreciated.
One of the first steps I would recommend is to utilize an OPC test client to check for connectivity issues. Another helpful strategy would be to display the links on separate screens to test if there is any loss of communication.
Which OPC-UA server do you currently have in use?
Certainly, I have thoroughly tested it in various scenarios and all devices are operating as expected. Furthermore, I have uncovered additional evidence indicating that the issue lies on Rockwell's end. I have previously created a gateway using C# and the official OPC UA .NET Client for storing data from OPC UA to Oracle, which has proven to be successful in similar situations. The only issue I am experiencing is a 0x8000000 error for devices that are offline. Can someone replicate this scenario in their own environment for testing purposes? On a side note, I have discovered a temporary solution - by linking tags from problematic devices with local HMI tags, everything functions correctly. However, this workaround is not a permanent fix. I am eager to find a more sustainable solution to resolve this matter.
In my situation, I was able to resolve the issue by upgrading the "Service Platform" software version from 6.11 to 6.20. You can easily access the upgrade by visiting the Rockwell website for download.
It sounds like you're dealing with a common challenge when working with OPC UA and device connectivity. In cases like this, one possible issue could be how the FT View application handles the loss of connection with one of the devices. When one OPC UA tag goes offline, it might be causing the complete data refresh for all tags, resulting in that failure you’re seeing with the indicators. A potential workaround could be implementing error handling for the tags so that if one goes offline, it doesn’t affect the others. Another thing to check is whether you can configure the OPC UA client settings to allow for partial updates rather than requiring a full refresh. Hope this helps!
It sounds like you're running into a pretty common issue where the FT View application doesn't handle the loss of connection gracefully. One potential solution could be implementing some error handling or monitoring logic in your application to check the status of each device independently. This way, if one device goes offline, the other indicators could still function properly, or at least provide a relevant status message. Additionally, check if there are any timeouts or settings in the OPC UA configuration that might be affecting the communication upon disconnection. It could help to look into the specific error codes or logs in FT View as well—they might give you more insight into what's happening. Good luck!
It sounds like you're dealing with a typical issue related to how FT View handles device communications. When one device goes offline, it can cause the entire display to stop responding due to a communication timeout or error handling configuration. One potential solution is to modify the error handling settings for those indicators, allowing them to continue displaying the last known value or a default state when one device is offline. It might also be worth checking the OPC UA server settings to ensure it gracefully manages disconnected devices without impacting the overall operation. Hope this helps!
It sounds like you're running into a common issue with how the FT View application handles offline devices during OPC UA communications. When one device goes offline, it can cause the entire connection to falter, leading to issues across all linked indicators. One potential solution you could try is implementing error handling in your tags, such as using an expression to check the status of each device before allowing the indicators to display values. This way, even if one device is offline, the other should still function properly. Additionally, ensuring that your OPC UA server is configured to handle connection losses gracefully might help alleviate some of these problems. Hope this helps!
✅ 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. Q: Why are the indicators on my FT View display not responding when one of the connected devices goes offline in an OPC UA setup? The issue of FT View not responding to offline devices in an OPC UA setup can occur due to the loss of connection with the device, causing the tags to become invalid and the indicators to fail.
Answer: To address this issue, you may need to implement fault-tolerant mechanisms such as setting up alarms or handling communication failures in your FT View application to ensure proper functionality even when devices go offline.
Answer: Implementing strategies like using redundancy, configuring appropriate error handling, or designing failover mechanisms can help ensure that FT View remains responsive even when devices go offline in an OPC UA setup.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.