We are working to address an issue with subscription email notifications. In the meantime, be sure to check your favorite boards for new topics.
When I click on "Launch Quick Client Here" the quick client opens showing 640 tags. Most of which are unwanted. I have the timestamp for the opening time, quality Good and Update Count 1. All but two of the update count values remain at 1 and the time stamps for those value remain at the starting time. Two tags are updating every couple of seconds. Of the rest of the tags 7 are marked Bad. In the KepserverEx event log there are 12 tags marked "Unable to read tag" with a CIP Error = 0x5. Am I really getting data from the PLC? How can I tell if this is accurate? How do I make the other tags update like the two anomalies?
KepserverEx 6.14.263.0
Thanks for the help.
It sounds like you added the tags to the KEPServerEX Configuration through the Automatic Tag Generation
which pulls in all the tags that are Globally Scoped. You can go inti the configuration and delete all of the unwanted tags.
If the automatic tag generation was successful, then you are at least connected to the PLC.
Here is a link to the Kepware Knowledgebase Article that cover the CIP Error = 0x5:
My Kepware login credentials will be needed to access the article.
I recommend opening a support ticket with the Kepware team to provide a full analysis of your specific architecture. Here is a link the login page where a ticket submitted:
Thanks,
*Chris
Thank you, Chris, for replying.
I should have added that this is connected to an Omron PLC. I am not all that concerned with the CIP Ox5 error. My biggest concern, or primary question, is why do only two or three tags update? How do I make everything update? Each tag is set to 100ms, but the Group Update Rate Option is set to 1000ms . But watching for minutes only shows 3 being updated. I just checked and of the three updating tags one stopped at Update Count 7739, another at 7418, the third stopped at 10236. This was since Friday morning.
Thanks,
Ok, so the Omron error is typically an indication of the following:
Error message: CIP error = 0X5, Extended error = 0000 in PTC Kepware Products
Description
Additional Context
Cause
Resolution
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
100ms seems may be too fast for this type of device. What is your client scan rate set to? The recommendation of increasing the Request Timeout in the device properties should allow more time for the device to respond.
I definitely suggest opening a ticket so other diagnostic tools can be used to assist with troubleshooting.
Thanks,
*Chris