Re: [foxboro] Station block parameters - OMSCAN I/A 8.7-ZCP270

  • From: "Landry, Scott" <Scott.Landry@xxxxxxxxxxxxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 13 Feb 2015 06:45:53 -0500


   On   #1   below,   Do you have FoxRay ?   I have noticed that FoxRay likes 
to deactivate this !


    Scott

________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of 
Dirk Pauwels [dirk.pauwels@xxxxxxxxxx]
Sent: Friday, February 13, 2015 4:01 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Station block parameters - OMSCAN  I/A 8.7-ZCP270

Hi list,
2 questions:


1.       We're monitoring the station block parameters for one of our ZCP270's, 
because the total memory is low (1100000) and the OMSCAN is high (12%). (see 2.)
Doing this I noticed that both in DCS and (off course) in PI these station 
block values were stale for longer periods. If I check the foxselect station 
block display and click the inactive button to active, the values start 
updating. Yet if you check the display again later the updating is back to 
inactive. Why doesn't it remain active, and do we get a correct trend this way? 
It looks like the trends are not reliable because of this active/inactive 
behavior?


2.        We're experiencing problems with MAXMEM dropping below the CSIZE so 
we cannot compile certain sequences anymore. (CP reboot solves this very 
temporarily, but we're restricted to plant maintenance shutdowns to do this.)  
Also sometimes sequences fail (handled by exception handlers) on external 
links. I know the use of external links is discouraged, but in the other CP's 
it works fine and it's not easy to correct this on +- 1000IND's. The sequence 
then generates a sys error > 3000. Normally we're supposed to exit the sequence 
in that case, but because it happens regularly we're adjusting the exception 
handlers to allow some retries, also in case of this type of error.



We've had this problem for the last 2 years, all this time we were told it was 
due to CSPACE/CSIZE problems and we needed to correct the CSPACE settings. 
Preventive maintenance twice a year never reveiled anything out of the 
ordinary. Although OMSCAN was high, it was never mentioned this could be a 
problem.  It's clear now that CSPACE/CSIZE is not the cause.

What's been done so far:

                Adjust all of the CPACE sizes, checked by Invensys and approved.

                Installed latest CP images. 90035

                Rebooted CP's (both simultaneously, primary and shadow)

                Slowed down scan rate for OSISOFT PI to 2 seconds and cdtlay 
from 50 to 200.

                Stopped foxray and other 3rd party services  to see if it made 
any difference .

                Removed restore_index.dat, and rebooted the boothost.



None of these actions showed any difference in OMSCAN load.



During our last maintenance shutdown I monitored the OMSCAN and although there 
was no production and none of the sequences were active the OMSCAN was still 
high, the only difference was that in normal operation the OMSCAN varies a lot, 
and during shutdown it was more or less stable.



According to Invensys OMSCAN is the cause of our problems and we need to find 
the reason why OMSCAN is too high. Anyone have any idea's?


Thanks & Rgds,
Dirk


________________________________
Lawter Notice: The information (including any attachments) contained in this 
communication is confidential, private and proprietary, may be privileged or 
otherwise protected by applicable law or legal rule, and is intended only for 
the use of the addressee(s). Unauthorized use, disclosure, distribution or 
copying is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify the sender immediately by reply e-mail, 
or by calling the sender, and then delete it completely from your system.



_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html

foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________

*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys Limited, which is a company registered in England and 
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 
7AW (Registered number 166023). For a list of European legal entities within 
the Invensys Group, please select the Legal Entities link at invensys.com. 
Invensys Limited is owned by the Schneider-Electric Group.

You may contact Invensys Limited on +44 (0)20 3155 1200 or e-mail 
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject 
to the terms of any agreements between Invensys (and/or its subsidiaries and 
affiliates) and the recipient (and/or its subsidiaries and affiliates).
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts:

  1. Home
  2. foxboro
  3. Archive
  4. 02-2015