Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution


Troubleshooting Bad Quality Data in RedundancyMaster


Last Update: 11/12/2018

Problem:
When reading data through RedundancyMaster using a connected client that is reporting a bad quality status in the OPC quality field, it may be difficult to know whether there is a problem with the end device/data source, the OPC servers, or RedundancyMaster.

Solution:
1. Check a system-level tag that is not associated with the end device or data source (if available in the OPC server). KEPServerEX has System Tags like _DateTimeLocal that users can reference from the client to verify that the server is functioning properly. As long as the server is running, a data change should be received on the tag every second and the quality should be Good.
2. Check the _Error and/or _NoError tags to see if the device is connected to the server. Binary values of "0" or "1" represent the state of the device.
3. If the OPC server and the device connections are healthy, check whether a shutdown message was sent to the client application. When RedundancyMaster is shut down normally, a message is sent to the client application. If RedundancyMaster was shut down abnormally, it is likely that the message was not sent.