Man, you guys are scaring me. If upload is potentially unreliable, how does one
capture operator changes in the savealls? I want to be able to automatically
generate savealls at night. Do I have to do it once without uploads, and again
with uploads, then run that check_db_sync or whatever it's called to make sure
the databases are consistent, and if it fails, restore the one I did without
uploads (to save the work I did that day)? This issue is getting more
ridiculous by the moment.
I agree with Bo; the other system I have experience with (Honeywell TDC) allows
you to rebuild the configuration database from the controller's memory.
Actually, there is no separate configuration database. There is a "workfile"
(the IDF) and an ASCII representation of the configuration database (the
exception build file) but these are not essential to the configurator's
operation; they only exist as a temporary storage facility, a means to transfer
configuration between two systems, and as a bulk configuration mechanism. The
configurator also does not "lock" the entire controller, so you don't have the
issue of CP memory corruption when multiple users try to work in the same CP.
This is not rocket surgery, Invensys. Help us out a little, eh?
Corey Clingo
Sr. Engineer
BASF Corporation
Alan J Schaff <[EMAIL PROTECTED]> on 08/10/2001 12:31:51 PM
Please respond to Foxboro DCS Mail List <[EMAIL PROTECTED]>
To: Foxboro DCS Mail List <Foxboro
cc:
Subject: RE: Save All Script
We did the upload but to no avail, the work file is still corrupted. Our next
course of action is to load a backup tape on an off-line system get the work
file and load it onto the on-line system. Then we plan on taking the upload
function out of the saveall script since we believe this was the culprit.
Thanks,
Alan Schaff
-----------------------------------------------------------------------
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]
