Re: [foxboro] Timer Question
- From: "Kevin Fitzgerrell" <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 9 Oct 2007 11:30:04 +0900
Ken,
Sorry, I missed your point before.
Does this mean that TIM blocks are processed in an extended BPC while
other blocks in the same overloaded CP may be processed in an overrun?
My understanding was that in a control station, all blocks were
processed without exception, the BPC overrunning to allow that. Seems
a bit odd if the TIM blocks are treated differently, as that could
change the normal compound/block processing order.
Which manual was that quote from?
Regards,
Kevin FitzGerrell
On 10/9/07, Kevin_Fitzgerrell@xxxxxxx <Kevin_Fitzgerrell@xxxxxxx> wrote:
> Ken,
>
> While the TIM blocks are always processed, the next cycle is delayed if
> overloaded. The timing on the TIM blocks depends on each block
> executing in it's scheduled slot. So, although the TIM blocks are
> always executed, the extra overrun slots in between the normal block
> execution slots affects the timing. This also affects ACCUM blocks and
> I believe CALC block timing (DON, DOFF, etc).
>
> Kevin
>
> -----Original Message-----
> =46rom: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Moore, Kenneth, Celanese/US
> Sent: Tuesday, October 09, 2007 6:31 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: 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
>
_______________________________________________________________________
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:
