Along those same lines, you should check for sequence blocks in the CP. = Sequence blocks do not necessarily run periodically since they may wait = for a state change to run a few lines of code. But if you have a large = BPCSTM (max statements per BPC) then sequence code, once started will = run to logical completion and this could extend a BPC, too. If you are using any CP timing functions you must never have BPC = overruns on the STATION display. Terry -----Message d'origine----- De : foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] = De la part de Moore, Kenneth, Celanese/US Envoy=E9 : October 8, 2007 5:31 PM =C0 : foxboro@xxxxxxxxxxxxx Objet : Re: [foxboro] Timer Question I'm looking at an old block book, but the last entry is a Note that states: "In a serious system overload, TIM blocks are always processed, even if = it delays the next BPC". So if you seriously overloaded, every additional TIM block added to the = system extends the BPC. Ken Moore Celanese Enoree SC -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, Alex P (IPS) Sent: Monday, October 08, 2007 4:57 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Timer Question Two suggestions: 1) Check for overruns 2) If no overruns, delete the "bad" block and duplicate a "good" one and = see if that works. The most common problem cause is CP overruns. The TIMERS all work = assuming that the BPC never overruns. If you are seeing the timers = "double time" on your production system, it is almost certain that the = CP is over-running. Call up the Station (<cplbug>_STA:STATION) block's detail display, = active the monitoring, and watch your overruns. I bet you have a lot of = them If your "good" TIM is in the same CP as your "bad" TIM and there are no = overruns, and the configuration is identical, I'm stumped as to the = cause, but for the solution, I'd delete your "bad" one and use the ICC's = block copy to copy the good one and see if it still works. The ICC's block copy facility is invoked by typing the path name to the = "good" block in the TYPE field of a block you are building. NAME COPY_TIM TYPE OTHER_CMPD:ORIG_TIM Regards, Alex Johnson Invensys Systems, Inc. 10900 Equity Drive Houston, TX 77041 713.329.8472 (voice) 713.329.1700 (fax) 713.329.1600 (switchboard) alex.johnson@xxxxxxxxxxxxxxxx - =20 =20 _______________________________________________________________________ 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 =20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 _______________________________________________________________________ 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