Re: [foxboro] Grouping for compounds

And even a Modbus gateway does not require grouping of the block types
in separate compounds.
I have AOUT, MCIN and MAIN blocks mixed in a compound with some CALC,
BLNALM, TIM and IND mixed in for good measure and all on a Modbus
gateway.

Cheers,
Frits Schouten.
NZSteel.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Neil Martin
Sent: Thursday, 25 September 2008 4:43 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Grouping for compounds

I highly suggest that where applicable, that control blocks associated 
with the controls for a piece of equipment (like a distillation column,
a 
batch kettle, etc.) be grouped within the same COMPOUND.  Where
practical, 
blocks that are part of the same control strategy should be in the same 
COMPOUND.  Doing so will effect the block processing order, the ease of 
configuring the block and monitoring the block in FoxSelect, and
numerous 
other reasons.  I believe Modbus gateways will require that Booleans be 
grouped in a COMPOUND separate from reals, but unless there are 
requirements to do so, don't separate Compounds by block type.

Neil Martin
Huntsman Performance Chemicals
Conroe & Dayton , TX. 
Conroe ph) 936-760-6205
Dayton ph)  936-257-4212
pager) 936-522-0052



Jeff Hurt <thehurtman@xxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
09/24/2008 10:46 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
[foxboro] Grouping for compounds






We are in the design phase for a new Foxboro I/A project.  For our 
compounds, we were considering having one compound for each type of
block 
(AIN, COUT, etc).  It seems that this is a break from the norm, grouping

by system.  Any thoughts as to why grouping by block type would be a bad

idea?
 
Thanks,
Jeff
 
 
_______________________________________________________________________
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
 




NOTICE - This message and any attached files may contain information that is 
confidential, legally privileged or proprietary.  It is intended only for use 
by the intended recipient. If you are not the intended recipient or the person 
responsible for delivering the message to the intended recipient, be advised 
that you have received this message in error. Any dissemination, copying, use 
or re-transmission of this message or attachment, or the disclosure of any 
information therein, is strictly forbidden. BlueScope Steel Limited does not 
represent or guarantee that this message or attachment is free of errors, virus 
or interference. 
   
If you have received this message in error please notify the sender immediately 
and delete the message.  Any views expressed in this email are not necessarily 
the views of BlueScope Steel Limited.
 
 
_______________________________________________________________________
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: