• Replies 14 replies
  • Subscribers 585 subscribers
  • Views 482 views
  • Users 0 members are here
Options
Related

Citect Version V8.1 - NEW OPC device added and slow performance. - Now Resolved

Alan

i have Citect Version V8.1 which has been communicating with a Bailey INFI 90 DCS via serial comms since 1995 without issue.

we recently upgrade the serial comms on the DCS to ethernet with a Rovisys OPC90 interface. all is working well except 1 faceplate which has many variables.

this faceplate takes approx 6 seconds to populate all the variables. i have approached Rovisys support and they seem to think its a citect issue.

OPC90 server looks to be communicating well to the Bailey DCS.  citect as the OPC Client should read these variables in much faster than the serial link. the belwo is what Rovisys support has advised.

If Citect supports cached displays, verify the display is setup as a cached display. My suspicion is the 6 second delay isn’t related with getting values but rather with Citect setting up the OPC tags with OPC90 each time the display is called up. OPC90 is collecting the exception reported values for all the blocks in its database, regardless if those values are on display in Citect or not. If Citect supports definition of OPC tag group update time, verify the group update time for this display is not larger than 1000 ms.

are there any parameters i need to add to my .ini file to improve performance? 

i see in the I/O device for Rovisys.OPC90Server that there is a field for Cache and update time, do i need to add some parameters to this ?

Parents Reply Children
  • in reply to Alan

    If it's of interest, we're running PlantSCADA 2020 R2 talking through OFSOPC to a bunch of Unity PLCs and have seen
    issues where some pages are slow to load (~6s relative to others that are reasonably quick at ~1s).


    This was thought to be the fact that the slow pages contained tags that were not currently subscribed on the
    OFSOPC server. The above fix was attempted (i.e. setting [Page]WaitForValidData=0) however it was found to be a bit
    of a sledgehammer approach; as everything on the page was always initially presented as #COM/#BAD. A compromise was
    found by setting [Client]WaitForValidDataTimeout=500 (and removing the other parameter). This gives the page a couple
    of scans (@250ms each) to display any data currently subscribed on the server and just #COM the rest.
    Note that the default setting for [Client]WaitForValidDataTimeout is 5000ms; which is a rather long time.

  • in reply to Steve

    Hi Steve,

    Yes....it's definitely of interest.

    i did look at the OFSOPC and downloaded it and some documentation as an option i was looking at if all else failed. this may be something i will look at in time. i have 2 different OPC servers citect is accessing at present (Rovisys OPC90 Server and ABB Codesys OPC Server). Both these OPC servers also reside on my Citect Servers.

    Thanks for the reply.

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