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

  • From: Terry Doucet <doucet427@xxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Fri, 13 Feb 2015 13:43:00 -0500

Alex,
 
Does the apicfg parameter  fastest_rsr take priority over the delta?   So if 
delta is 0.0, but fastest_rsr is 10 seconds you only send via OM every 10 
seconds as long as there is a change.
 
 
Terry
 
> From: alexander.johnson@xxxxxxxxxxxxxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Date: Fri, 13 Feb 2015 12:29:54 -0600
> Subject: Re: [foxboro] Station block parameters - OMSCAN  I/A 8.7-ZCP270
> 
> Dirk,
> Check the change deltas in use by PI. I've seen sites where they were set to 
> 0.0 which results in a report on every BPC and significant load.
> 
> The change deltas should be set to something "reasonable" for the value. For 
> example, AIN.MEAS should be monitored with a change delta slightly larger 
> than the typical noise on the signal to avoid useless reports. Relatively 
> static values, e.g., setpoints should have small non-zero values that are 
> slightly smaller than the normal adjustment. And so on...
> 
> Best,
> 
> Alex
> 
> _____________________________________________________________________________________
> 
> Alex Johnson | Schneider Electric | Invensys | United States | System 
> Architect, Next Generation Systems
> Phone: +1 713 329 8472 | Fax: +1 713 329 1700
> Email: alexander.johnson@xxxxxxxxxxxxxxxxxxxxxx | Site: 
> www.schneider-electric.com | Address: 10900 Equity Drive, 77041 Houston, TX, 
> United States
> 
> *** Please consider the environment before printing this e-mail
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
> Behalf Of Dirk Pauwels
> Sent: Friday, February 13, 2015 8:19 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Station block parameters - OMSCAN I/A 8.7-ZCP270
> 
> Hi Terry,
> 
> Ever since we went from CP60 to ZCP270 we haven't had any overruns anymore. 
> The om scan is showing no peaks, goes from 8 to 14%. BPC is at 0.5sec.
> I did check the foxray scripts like Scott suggested and there was a script 
> that resets the station block counters every time foxray checks these params. 
> I disabled the reset and I'll check if we have any overruns now.
> I might have expressed myself badly, we didn't change the osisoft scan, I 
> changed the foxapi.cfg. The scanrates in fxbais interfaces are still at 10sec 
> and onwards.
> I can slow down the foxapi scanrate further to see if it makes any 
> difference, but I have to stop PI interface and reboot the host every time 
> and production doesn't like that very much.....
> Thanks & Rgds,
> Dirk
> 
> 
> From: doucet427@xxxxxxxxxxx
> To: foxboro@xxxxxxxxxxxxx
> Subject: RE: [foxboro] Station block parameters - OMSCAN  I/A 8.7-ZCP270
> Date: Fri, 13 Feb 2015 08:42:48 -0500
> 
> Dirk,
> 
> The OM Scanner load on a CP is driven by the other stations in your system.  
> Unfortunately, there is not much you can do at the CP to change this loading. 
>   I presume you are running 1/2 second BPC but perhaps you are running faster?
> 
> I am very surprised to see zero OM overruns with such a high OM Scan.    
> Could another application be re-setting the value to zero?
> 
> Open the om Scannner overlay and watch the scan at the various phases to see 
> if it is evenly balanced at 10-12% for all phases or to get high peaks.  This 
> might help you find out what OM load is demanding peaks.
> 
> You say that you slowed down OSI software scan to 2 seconds.   In the olden 
> days a 2 second API scan could kill every CP on a network.  You are using 
> CP270 so  you get some grace here but I would try slowing it down even more.  
> At many sites, the normal API scan is 10 seconds.
> 
> 
> Terry
> 
> 
> _______________________________________________________________________
> 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
> 
> 
> ________________________________
> 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
>  
                                          
 
 
_______________________________________________________________________
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