Re: [foxboro] IACC
- From: "Badura, Tom" <tbadura@xxxxxxxxxx>
- To: "Prinsloo, Anton" <Anton.Prinsloo@xxxxxxxxxxx>
- Date: Thu, 17 Apr 2008 09:32:49 -0500
Thank you Anton,
This is all very good advice. We are at IACC vers. 2.3 plus a few quickfixes.
Things must not have changed much, though, because I have already discovered
and learned to avoid most of the issues you have pointed out. I have recently
run into a situation with one of our ZCP270s that sounds like the CP/database
mismatch you described. When I try to download individual items (blocks, CSDs,
Compunds) I get a message that "CP must be downloaded because Compounds have
been deleted". Even after downloading the entire CP I continue to get the same
message. I have run the Synch To CP utility and corrected any mismatches.
Fortunately, at this point I am still able to perform downloads at the CP
level. I will throw this line out to the community at large also and see if I
get any more bites, but I will also take your advice and contact TAC before I
do end up dead in the water.
Best Regards,
Tom Badura
Plastics Engineering Company
From: Prinsloo, Anton [mailto:Anton.Prinsloo@xxxxxxxxxxx]
Sent: Wednesday, April 16, 2008 7:20 PM
To: Badura, Tom
Subject: IACC
Tom,
Good day to you...
The version of IACC you have may have been vastly improved on the version I
worked on about 3 years ago.
I have subsequently moved to a site which does not have IACC.
I will give you a few pointers to watch out for, though.
***REMEMBER my experience is 3 years old - my issues may have been corrected in
new versions.***
If you work with blocks directly, any links you create in the "background" as
with typing CBP links directly into parameters and downloading them - i.e. not
using the graphical interface, will NOT show upas a line in the drawing you
created before. So your drawing will not match the database.
If you use the mouse to drag from a block SINK to a block SOURCE, (remember
that we connect from s SOURCE TO a SINK in real life) the drawing WILL show the
line and a "link" will be made but when you download it, the IPC connection
will show up as unserviced. Watch the direction of the arrow closely, a bad
link will have the arrow going from SINK to SOURCE.
The drawing interface, as you mention is very VERY clumsy, and whenever you lay
the whole thing out neatly, and make a change, all the bloody lines re-arrange
themselves on top of each other again.
You can't download a block - as in the past in ICC - to trigger an
initialisation; it will not download UNLESS you have made a validated change.
The only way I got past that was to change an innocuous parameter such a as a
bit of text, perhaps add a full stop in an alarm message or something and that
will constitute a change.
Look after your databases very very well - if a difference develops between
what's in the CP versus what's in the IACC database, you're in serious trouble
- it will not download anything - perhaps explore this with a service centre
and develop your procedures accordingly.
My biggest issue was that with their attempt at version control you can only
have one engineer busy in your database at any one time. They have advised
building a number of databases - one for each plant area - this would allow you
to have a number of engineers working of different CP's. All good and well,
but then the plant areas are invisible to each other from within each of the
databases.
I hope that I stand corrected on some of these issues, but rather be aware of
the potential of this happening to you.
Kind regards
Anton
__________________________________
Anton Prinsloo
Superintendent Control Systems
( Phone: +61 7 4769 5762 4 Fax: +61 7 4769 5764 È Mobile: 0423 608 734
* Email: anton.prinsloo@xxxxxxxxxxx
ZINIFEX CENTURY MINE
ABN 59 006 670 300
Lawn Hill via Mt Isa, QLD 4825, AUSTRALIA
P. O. Box 8016, Garbutt, QLD 4814, AUSTRALIA
_______________________________________________________________________
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: