[foxboro] ^pRE: Block Equivalents List

Please use the sizing spreadsheets. The data that you want is all there.

Anything else is a very rough approximation.

Even the term 'block equivalents' has a different meaning in different
contexts. Generally, a BE is a certain amount of RAM (about an AIN's worth)
and/or 1/3 the time required to execute a PID loop:

1/8 ECB -> AIN -> PID -> AOUT -> 1/8 ECB == 1 loop

1/3 of a loop is one BE of processing power.

But this is really, really rough.

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
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Jack.Easley@xxxxxxx
Sent: Monday, March 27, 2006 5:18 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Block Equivalents List

Does anyone have a handy-dandy list of I/O Loading block equivalents for
the most common Foxboro blocks they are willing to share? I know Foxboro

has spreadsheets available for this, and that other factors affect CP/GW

loading, but I could use a better grasp of block equivalents to quickly

check loading problems.



A list of other CP/GW loading factors such as peer-2-peer, display,

historian, and PI connections and how one calculates (rsom, sipc, etc)

how significantly they affect CP/GW loading would be useful to most of

us also.



 



Appreciate it ...



Jack Easley



 



 





Confidentiality Notice: This email message, including any attachments, 

contains or may contain confidential information intended only for the 

addressee. If you are not an intended recipient of this message, be 

advised that any reading, dissemination, forwarding, printing, copying

or other use of this message or its attachments is strictly prohibited. If

you have received this message in error, please notify the sender 

immediately by reply message and delete this email message and any

attachments 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:             http://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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: