Skip to main content
Y
YS_113538873-Newcomer
3-Newcomer
July 10, 2024
Question

.Error Tag Does Not Trigger w/o Quick Client

  • July 10, 2024
  • 1 reply
  • 1147 views

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.

1 reply

C
cmorehead13-Aquamarine
13-Aquamarine
July 12, 2024

@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 

Y
YS_113538873-NewcomerAuthor
3-Newcomer
July 16, 2024

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

 

Thanks. 

 

C
cmorehead13-Aquamarine
13-Aquamarine
July 16, 2024

@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.

 

Log In | My Kepware

 

Thanks,

*Chris

Terms & ConditionsCookie settingsAccessibility statement