Re: [foxboro] Global parameter changes
- From: brad.s.wilson@xxxxxxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 12 Sep 2006 12:23:00 -0400
Alex,
Thank you, that does help. I have rarely made any changes EXCEPT through
the ICC ... partly out of fear of mistyping something and having a shutdown
on my hands. I use getpars ALOT to read selected values. I know that if I
use ICCDriver (or whatever it's called), that's just like using the ICC.
Will either setpars or omset modify the configuration database? Or just
the work file? In other words, if I do a setpars or omset and then go into
the ICC, will I see the change? Or would I need to upload to see it?
Brad Wilson
Process Control Engineer
ExxonMobil Chemical Co
Edison Synthetics Plant
732-321-6115
732-321-6177 fax
Brad.S.Wilson@xxxxxxxxxxxxxx
"Johnson, Alex
P \(IPS\)"
<alex.johnson@ To
ips.invensys.c <foxboro@xxxxxxxxxxxxx>
om> cc
Sent by:
foxboro-bounce Subject
@freelists.org Re: [foxboro] Global parameter
changes
09/12/06 11:03
AM
Please respond
to
foxboro@freeli
sts.org
CP data is stored in the following locations:
* CP's RAM
* Checkpoint file
* Workfile
Currently, there are two techniques for changing parameters in a CP:
1) Changes that are made to the CP RAM and
2) Changes that are made to the CP RAM, the workfile, and the
checkpoint file as a set
The former approach uses tools like:
* /opt/fox/bin/tools/omsetimp
* /opt/fox/bin/tools/setpars
These tools do not automatically update the workfile or trigger a
checkpoint.
The latter approach uses the ICC Driver Task to make changes. It updates
all three locations automatically.
The mechanism used by omsetimp is a one-shot set. It moves one value to
the CP at a time and is slow. It can change any data type so long as the
parameter is "settable" and unsecured.
The mechanism used by setpars is the db_install task in the CP (getpars
uses db_query) and it can handle much more data in a communication
session. Generally, for lots of changes, I would expect setpars to be
faster. Its restrictions are documented in the man file in
/opt/fox/bin/tools.
The ICC Driver Task can change anything.
Does this help?
Regards,
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of brad.s.wilson@xxxxxxxxxxxxxx
Sent: Tuesday, September 12, 2006 9:14 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Global parameter changes
I've used getpars to view parameters globally and setpars to change them
individually, but I'd like to make some global changes and would like
some
input on the best way to accomplish this. For example, globally
changing
the BAG (bad alarm group) for all GDEVs. Would there be different
techniques for different types of parameters (boolean, integer, real,
string) ? I know that some parameters are not visible to setpars but
can
be touched by omsetimp or icconfig ... is that a factor ?
Brad Wilson
Process Control Engineer
ExxonMobil Chemical Co
Edison Synthetics Plant
732-321-6115
732-321-6177 fax
Brad.S.Wilson@xxxxxxxxxxxxxx
_______________________________________________________________________
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:
