Re: [foxboro] CHARC block BCALCO generation
- From: "O'Brien, Con" <con.obrien@xxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 22 Mar 2006 05:52:29 +0800
Aargh, this annoying Outlook text formatting!! Original message repeated
below, hopefully without text artefacts...
I believe this is as-designed.=20
You can only configure a characterisation containing a 'peak' if you set
PRIBLK=3D0. If there's a peak in the curve (ie. it's not continuously
moving in one direction...what's the mathematical term for this?) then
it's not possible to generate a unique value for BCALCO for any value of
BCALCI. So I guess the designers included this as a genuine feature...to
allow you to put such curves in, BCALCO calculation has been disabled
when PRIBLK=3D0.=20
You can check this by trying to configure a curve containing a peak with
PRIBLK=3D1. The ICC will tell you where to go. If you turn PRIBLK off, =
it
goes in fine.=20
If you still need the BCALCO value in your control scheme, you can
configure a dummy BIAS block upstream of the CHARC, and use it to
terminate the initialisation chain.=20
Con O'Brien
Bulwer Island=20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Wednesday, 22 March 2006 2:32 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] CHARC block BCALCO generation
Hi list,
I noticed while troubleshooting some control logic the other day that
CHARC blocks will not continuously update the BCALCO parameter when
PRIBLK is not 1. Unfortunately in the scheme we're using I cannot set
PRIBLK to
1 as there is not always an upstream propagation path for it.
Is this as-designed behavior? I don't believe I've noticed this
phenomenon on other blocks, but I plan to experiment if I get time. I
took a quick look at the docs, but they don't explicitly mention this.
Thanks,
Corey Clingo
BASF Corp.
=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
Other related posts:
