topic Re: .Error Tag Does Not Trigger w/o Quick Client in Kepware

.Error Tag Does Not Trigger w/o Quick Client

YS_11353887 — Wed, 10 Jul 2024 12:54:57 GMT

Hello,

I am reading Channel.Device.System*_Error tag via OPC DA Client of the SCADA. I am able to read tags of the device but can't read the _Error tag and quality is bad, whenever I restart the kepserver computer.

After started the quick client I can see the tag quality is good.

Why this is happen? Thank you in advance.

Re: .Error Tag Does Not Trigger w/o Quick Client

cmorehead — Fri, 12 Jul 2024 12:49:29 GMT

@YS_11353887

Are any of the other system tags other than the _Error tag showing as Bad Quality in your Scada application before opening the Quick Client?

Thanks,

*Chris

Re: .Error Tag Does Not Trigger w/o Quick Client

YS_11353887 — Tue, 16 Jul 2024 13:48:47 GMT

I am only using _Error tag but using _Error tags from several devices. Same problem occur from different devices.

Thanks.

Re: .Error Tag Does Not Trigger w/o Quick Client

cmorehead — Tue, 16 Jul 2024 16:21:20 GMT

@YS_11353887

There are no known issues with the use of the _Error tag. Since you are seeing similar behavior across multiple devices, there may be an issue with the way the system tag is being implemented in your particular set up. I recommend opening a support ticket with the Kepware team to analyze your specific architecture. My initial thought is that the system tags require a good connection before exhibiting good quality and becoming active. It seems as though the opening of the Quick Client creates the good connection allowing the system tags to become active. The Kepware team will be able to provide a deeper analysis of your specific set up. Here is a link to the login page where a ticket can be opened.

Thanks,

*Chris

Re: .Error Tag Does Not Trigger w/o Quick Client

YS_11353887 — Thu, 25 Jul 2024 05:32:14 GMT

Thank you Chris, I will submit a ticket and try my chance.