Re: [foxboro] CALC block

  • From: "Jim Mowrey" <jmowrey@xxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Thu, 8 Jan 2004 00:19:33 -0500

The value would not change because the block evaluates its inputs before
starting execution and will not examine them  again until the next BPC; I
believe this to be true of all blocks as well.

In a related matter, I once mistakenly set an output in the CALC block and
then set it again (to a different value with different logic) a few steps
later.  Since the outputs are stored in memory, but not written out to other
blocks , until the CALC block completes its logic, I never saw the first
value output from any downstream block responses.

jim

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of
IQUEIROLOO@xxxxxxxxxxxxx
Sent: Wednesday, January 07, 2004 8:47 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] CALC block


Hi list, I have a question about the CALC block. Suppose that we have a =
CALC block with this instruction in the first line:

Step 1          IN RI01

and the same instruction is repeated in the 40th line, as follows:

Step 40         IN RI01

If the value of RI01 has changed in the time between those two steps in =
the same BPC, the values that the block will read will be different?.

Suppose that the CALC block and the block where the value of the RI01 =
comes from are in the same compound.

Thanks,

Ignacio Queirolo Olivera
Repsol YPF
Tel: +54 221 429-8400 ext. 26481
Fax: +54 221 429-8400 ext. 26272
mailto:iqueiroloo@xxxxxxxxxxxxx



AVISO LEGAL:
Esta informaci=F3n es privada y confidencial y est=E1 dirigida =
=FAnicamente a su destinatario. Si usted no es el destinatario original =
de este mensaje y por este medio pudo acceder a dicha informaci=F3n por =
favor elimine el mensaje. La distribuci=F3n o copia de este mensaje =
est=E1 estrictamente prohibida. Esta comunicaci=F3n es s=F3lo para =
prop=F3sitos de informaci=F3n y no debe ser considerada como propuesta, =
aceptaci=F3n ni como una declaraci=F3n de voluntad oficial de REPSOL YPF =
S.A. y/o subsidiarias y/o afiliadas. La transmisi=F3n de e-mails no =
garantiza que el correo electr=F3nico sea seguro o libre de error. Por =
consiguiente, no manifestamos que esta informaci=F3n sea completa o =
precisa. Toda informaci=F3n est=E1 sujeta a alterarse sin previo aviso.=20

This information is private and confidential and intended for the =
recipient only. If you are not the intended recipient of this message =
you are hereby notified that any review, dissemination, distribution or =
copying of this message is strictly prohibited. This communication is =
for information purposes only and shall not be regarded neither as a =
proposal, acceptance nor as a statement of will or official statement =
from REPSOL YPF S.A. and/or subsidiaries and/or affiliates. Email =
transmission cannot be guaranteed to be secure or error-free. Therefore, =
we do not represent that this information is complete or accurate and it =
should not be relied upon as such. All information is subject to change =
without notice.


_______________________________________________________________________
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: