OK, you've gone and confused me now (don't get the big head; it's not that hard
to do ;-).
I am kind of new to I/A, and this whole checkpoint/workfile/CP's memory thing
has me asking a lot of questions, to say the least. I had thought that the
checkpoint at least was a direct copy of the CP's memory, but from what you say
below this is not the case. (Emotional state on discovering this deleted...)
So....is there anything else supplied by Foxvensys that can make changes to the
CP's memory that cannot be duplicated on-disk?
Corey Clingo
Sr. Engineer
BASF Corporation
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
-----------------------------------------------------------------------
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]
