Re: [foxboro] AW: setpars utility
- From: "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 11 Apr 2002 11:16:15 -0400
I sorry, but I'm not able to do that at this time. Up to my eyeballs in my
"real" job.
Regards,
Alex Johnson
System Products - Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx <mailto:ajohnson@xxxxxxxxxxx>
Come to the Invensys Showcase: http://www.invensysshowcase.com/
<http://www.invensysshowcase.com/>
-----Original Message-----
From: Weiss, Andreas [SMTP:Andreas.Weiss@xxxxxxxxx]
Sent: Thursday, April 11, 2002 5:59 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] AW: setpars utility
Hi Alex,
please send us the ultimative script which allows us to change all
LIMOPT-values.
Many users will get the problem with the next update.
Regards,
Andreas
-----Urspr=FCngliche Nachricht-----
Von: Johnson, Alex (Foxboro) [mailto:ajohnson@xxxxxxxxxxx]
Gesendet: Donnerstag, 11. April 2002 08:53
An: foxboro@xxxxxxxxxxxxx
Betreff: Re: [foxboro] setpars utility
Nothing changed with setpars is recorded the workfile.
Uploads will only update the workfile with those parameters that are
supposed to change.
Don't use setpars if you want the changes to be permanent. Use the
ICC
Driver Task.
Regards,
Alex Johnson
System Products - Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx <mailto:ajohnson@xxxxxxxxxxx>=20
Come to the Invensys Showcase: http://www.invensysshowcase.com/
<http://www.invensysshowcase.com/>=20
-----Original Message-----
From: Ajay_Tathgir@xxxxxxx [SMTP:Ajay_Tathgir@xxxxxxx]
Sent: Wednesday, April 10, 2002 11:20 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] setpars utility
Kevin
A small question. Are there any others parameters which
don't
get
updated on doing a upload when changed via setpars, or for
that
matter is it all non-settable parameters.
I once changed a description of AIN block via setpars, but
never could get it uploaded via upload.
Thanks & Regards
Ajay Tathgir
Reliance Industries Limited
Mumbai - India
Fitzgerrell Kevin <fitzgerrell@xxxxxxxxx>@freelists.org on
10-04-2002
10:52:42
Please respond to foxboro@xxxxxxxxxxxxx
Sent by: foxboro-bounce@xxxxxxxxxxxxx
To: foxboro@xxxxxxxxxxxxx
cc:
Subject: Re: [foxboro] setpars utility
James,
Take a look at the MODOPT setting in the PIDA blocks that
stayed
at
LIMOPT=3D3. I think you'll find that they don't have an
integral
term,
ie P or PD. In the P only blocks (MODOPT=3D1) the
controller will
show
LIMOPT=3D3 regardless of it's state in the ICC (I didn't
check the
PD
option), ie. in a PIDA block with MODOPT=3D1 and LIMOPT=3D1
showing
in
ICC,
SELECT will show LIMOPT=3D3. If you change MODOPT to 5, and
make
no
change to LIMOPT, SELECT will show MODOPT=3D5 and
LIMOPT=3D1.
You may want to reconsider your use of setpars to make these
changes.
Because LIMOPT is not a settable parameter, changes made by
setpars
to
it will not be updated to the station workfiles with an
upload.
This
results in a permanent mismatch between station and
workfile.
Savealls
are generated based on the station workfiles, so if you ever
load
from
a saveall diskette these changes would be lost.
Additionally,
setpars
doesn't checkpoint, so until the stations are checkpointed
after
the
changes are made, a CP reboot would cause these changes to
be
lost.
Finally, consider the scenario where a P only block is
changed
to a
PI.
If LIMOPT had originally been set to 2 in the ICC (or via
iccdrvr.tsk), when the later change to PI mode is made,
LIMOPT
will
still be 2 (and will now show 2 instead of 3 in SELECT). If
LIMOPT
was
set with setpars, a subsequent change in MODOPT would cause
LIMOPT
to
revert to the value in the station workfile, probably 1.
The iccdrvr.tsk is fairly easy to use for bulk editing,
makes
changes
in both CP and station workfile and does checkpoints.
Additionally,
small typos are significantly less likely to cause major
damage
to
the
control database (-c vs -C for instance).
Regards,
Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
+64 9 573 7690
kevin.fitzgerrell@xxxxxxxxxxxx
fitzgerrell@xxxxxxxxx
--- "Hyde, James" <James.Hyde@xxxxxxxxxxxxxx> wrote: >
> Hi,
>
>
> With the recommendation from Foxboro in the :
> Customer Advisory
> PIDA Block Behavior with V6.3 CS Release
> April 1, 2002
>
> We use a lot of PIDA's and, we did have most of the
LIMOPT's
set
to
> 1. I
> used the setpars utility to change the LIMOPTS to 2.
>
> /opt/fox/bin/tools/setpars -Ucp**** -tpida -mlimopt=3D2
-gIknowwhatido
>
> This only change the parameters that were set as 1 to a 2.
It
did
> not
> change the parameters that were set as 3 to a 2.
> Does anyone know why?
>
>
> James W. Hyde III
> Controls Technician
> Wellman Inc.
> Office: 228-533-4528
> Pager: 888-634-1690
>
>
> If the reader of this e-mail is not an intended recipient,
you
have
> received
> this e-mail in error and any review, dissemination,
distribution
or
> copying
> is strictly prohibited. If you have received this e-mail
in
error,
> please
> notify the sender immediately by return e-mail and
permanently
delete
> the
> copy you received.
>
>
>
>
http://www.sold.com.au - SOLD.com.au Auctions
- 1,000s of Bargains!
=09
_______________________________________________________________________
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=3Djoin
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
=20
=09
_______________________________________________________________________
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
=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
_______________________________________________________________________
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:
