• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 1 reply
  • Subscribers 11 subscribers
  • Views 112 views
  • Users 0 members are here
Options
Related

Historian tag quality indicates an IOServer communication failure.

Inacio Tavares


I am using System Platform 2012 in a factory and migrating to 2020R2, rebuilding the application. However, I'm facing an issue with History: some tags, for reasons I haven't been able to identify, lose communication, as shown in the QualityDetail column in the image. What puzzles me is that this only happens in the new system; in the old one, these issues do not occur, and both systems are running in parallel.

Moreover, the issue occurs randomly with some tags within the areas. When I deploy the instance, communication is re-established, and the QualityDetail goes back to 192, as shown in the last row. I can't figure out what's causing this. Has anyone encountered this issue before or has any idea how to resolve it? There is nothing in the logs indicating any errors or warnings related to this.

Additional Information:

Version: SP2020R2
Setup: one node for each machine (History, GR, and four AOS, where the communication engines are located)
Using SMS."

  • +1

    The "QualityDetail" is set by Historian subsystems, either the integration with an AppEngine or by IDAS, or by the server itself. In contrast, the "OPCQuality" (not included in your screens) is set by the data source/interface.

    The pattern you've shown is more characteristic of a problem in network infrastructure than in the software.

    If the problem is with the physical network dropping (e.g. bad wiring, volatile cellular modem, etc.) or problems with network addresses and routing (e.g. competing DHCP servers, unreliable DNS, etc.), they should be consistent for all the tags from a given AppEngine or IDAS "topic".

    If none of this helps, I suggest reaching out to AVEVA Technical Support. 

© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.