Re: [foxboro] Automation of upload/checkpoint/save_all at sites with IACC

Kevin,

True, all the good tuning values, alarm settings, etc are right there in the 
checkpoint file.  All the stuff that takes 4-5 hours to extract from the CP270 
using the UPLOAD function is right there in this file.

So what we really need is for Invensys to make the UPLOAD tool operate on the 
checkpoint file instead of being a low priority task query into the CP itself. 
We do not want to increase the priority since the CP's main job is to control 
our plants. So take the UPLOAD function off-line. In the new super fast AW's 
this would likely take seconds to extract the data from the checkpoint file and 
poke it into the configuration database.

If they follow the Wonderware concept they can lease the tool on a yearly basis 
per CP. Invensys makes money and the users are happy because their CP's are not 
tied up for four hours per week.

Terry Doucet, Eng.


la part de Kevin Fitzgerrell
Envoyé : October 29, 2008 10:54 PM
À : foxboro@xxxxxxxxxxxxx
Objet : Re: [foxboro] Automation of upload/checkpoint/save_all at sites with 
IACC

One minor note - uploads do not affect the checkpoint file.
Checkpoints always have setpoint changes, alarm settings, tuning
parameters, etc. that are current as of the date/time of the
checkpoint.

Regards,

Kevin FitzGerrell

 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: