Norberto,
You're right of course, I should have read that over more closely before
sending. That should have read:
setpars -- makes active change in CP
upload -- updates settable parameters in CP to station workfile
checkpoint -- builds new checkpoint file based on CP memory
saveall -- builds diskette based on station workfile
Regards,
Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
------------------------------------
Tel: +64 (9) 573 7690
Fax: +64 (9) 573 7691
"Marrassini, Norberto"
<Norberto.Marrassini@invensys To: Foxboro DCS Mail List
<[EMAIL PROTECTED]>
.com.ar> cc:
Sent by: Subject: RE: HLBL REF.
<[EMAIL PROTECTED]
oject.org>
07/14/01 03:01 AM
Please respond to "Foxboro
DCS Mail List"
Kevin,
The checkpoint -- builds new checkpoint file based on station
memory
and not station workfile, in that case we can guarantee always to have the
checkpoint file at memory status after a checkpoint, but not the workfile
since upload only updates settable parameters
Norberto Marrassini
Invensys Process Automation - Argentina
-----Mensaje original-----
De: FitzGerrell, Kevin
Enviado el: Monday, July 09, 2001 7:30 PM
Para: Foxboro DCS Mail List
Asunto: RE: HLBL REF.
Ken,
As others have stated, extreme caution should be taken when using setpars.
Anytime setpars is used for bulk changes it should be followed by an upload
and then a checkpoint (if you want the changes to be there in the event of
a reboot), because setpars makes active changes in the CP only, not in the
workfile or checkpoint file.
setpars -- makes active change in CP
upload -- updates settable parameters in CP to station workfile
checkpoint -- builds new checkpoint file based on station workfile
One of the big dangers in using setpars is that it can change non-settable
parameters. These changes can not be updated in the station workfile with
an upload, resulting in a mismatch between checkpoint file, station
workfile, and CP. Wildcards can be used in the filter specifications in
setpars which can lead to unforseen changes due to unexpected matches.
Making a small mistake when updating a setpars script can cause extensive
damage to control logic.
If you are making changes to settable parameters in an operating plant and
need to do them from a UNIX script, consider using omset or omsetimp.
Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
------------------------------------
Tel: +64 (9) 573 7690
Fax: +64 (9) 573 7691
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
