Re: [foxboro] PIDA-FBTUNE configuration

Thank you Neil for the reply, but I have tried THRESH from as small as =
1% to as high as 10% but the "settle" behaviour manifests itself each =
time (most of the time) the Meas crosses the Spt.  When this happens it =
searches for a new Peak_1 (although in rare cases it may already be in =
Peak_4).

How about the LIM parameter?

Budana Prijadi
(GMT +09:00)

-----Original Message-----
From: Neil Martin [mailto:neil_martin@xxxxxxxxxxxx]
Sent: Wednesday, June 18, 2003 5:28 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] PIDA-FBTUNE configuration



If I remember correctly, the FBTUNE in Selftune mode must see at least 3
significant peaks, possibly 4, in a row.  I believe the FBTUNE's THRESH
parameter is used to define what a significant peak is.  Note the value
entered for THRESH is % of the PIDA block range.

Neil Martin
Huntsman Polymers Corporation
2505 South Grandview
Odessa, TX.  79766
ph) 432-640-8436
pager)432-742-4289
email page)9157424289@xxxxxxxxxxxxxxxxxx


                                                                         =
                                                             =20
                      <Budana_Prijadi@f                                  =
                                                             =20
                      mi.com>                  To:       =
<foxboro@xxxxxxxxxxxxx>                                                  =
    =20
                      Sent by:                 cc:                       =
                                                             =20
                      foxboro-bounce@fr        Subject:  [foxboro] =
PIDA-FBTUNE configuration                                          =20
                      eelists.org                                        =
                                                             =20
                                                                         =
                                                             =20
                                                                         =
                                                             =20
                      06/17/03 09:10 AM                                  =
                                                             =20
                      Please respond to                                  =
                                                             =20
                      foxboro                                            =
                                                             =20
                                                                         =
                                                             =20
                                                                         =
                                                             =20




Dear I/A users,

I have been trying now for days to set up a PIDA-FBTUNE combo to
automatically tune (selftune) a real level control application in a =
mineral
processing rougher circuit (I am trying only for a first stage rougher =
bank
before copying to others).

The question I have is why if I get a confirmed Peak_1 or Peak_2 search =
and
then the measurement crosses the setpoint value, I always have a =
"SETTLE"
status?  This brings back to search for Peak_1.

In other words, I know there will be another Peak after crossing the
setpoint value, but the algorithm somehow starts again from Peak_1 =
rather
than continuing the next peak search.

Please have a look at the lower left quarter screen trend, where we know
that there is a pattern in measurement (cyan color) against the setpoint
(purple).  The output is given in white.

What FBTUNE parameters can I adjust to prevent "SETTLE" when measurement
crosses the setpoint value (line)?

Many thanks for any insights given.

Budana Prijadi
(GMT +09:00)

-- No attachments (even text) are allowed --
-- Type: application/x-zip-compressed
-- File: fbtune_settle.zip
-- Desc: fbtune_settle.zip




_______________________________________________________________________
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=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave






=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:             http://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:             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: