Re: [foxboro] Controller Issue after upgrade
- From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 6 Jun 2012 17:31:14 -0500
Hi David,
Is there a version change with this upgrade? If so, what was the version
when it was working on the CP30? There was a lot of PIDA block change
between 6.2.1 and 6.5.6.
Cheers,
Kevin
On Wed, Jun 6, 2012 at 4:36 PM, Dale Gillis <dale_gillis@xxxxxxxxxxx> wrote:
> Just a guess on my part but I remember LIMOPT behaving something similar
> to this between software upgrades. May be worth checking.
>
> Sent from my iPhone
>
> On 2012-06-06, at 5:20 PM, "Johnson, David" <
> David.Johnson@xxxxxxxxxxxxxxxxxx> wrote:
>
> > Hello all,
> > We are looking into some strange behavior after a recent upgrade from a
> CP30 to an FCP270. A PIDA block was set to be Proportional Derivative,
> MODOPT=3, PBAND = 125, INT=0.075 (INT is BTIME in PD mode). The BCALCI and
> FBK were both connected to the PIDA's own .OUT parameter. The Period is a
> 3, Phase is a 2. I think the BPC of the CP30 and FCP270 are both .5
> seconds.
> >
> > Behavior
> > In the FCP270, the output drives to the low output limit. It's as
> though the loop is in open loop control. Looking at trends indicate that
> this loop was controlling in the CP30. The configuration is identical to
> what it was in the CP30.
> >
> > Any advice on what to check.
> >
> > Thanks,
> > David
> >
> >
> > ________________________________
> > Confidentiality Notice:
> >
> > The information contained in this message is private and confidential.
> This information is intended only for the individual or entity named above.
> If the reader of this message is not the intended recipient, you are hereby
> notified that any use, review, dissemination, distribution, copying or
> action taken based on this message or its attachments, if any, is strictly
> prohibited. If you are not the intended recipient, please contact the
> sender by reply email and delete or destroy all copies of this message and
> any attachments. Thank you.
> >
> >
> >
> > _______________________________________________________________________
> > 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
>
>
_______________________________________________________________________
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:
