Re: [foxboro] IACC Product and Integration with existing I/A tool s

Re: RTFM

Always a good idea. :)


Re: I guess I ought to RTFM, but how does the IACC server talk to the host
AW to actually do the CP downloads, particularly if that AW is a 51?

IACC transfers a file to the AW that contains ICC driver task information
and then runs the IACC driver task. (plus or minus a few details)

Regards,
 
Alex Johnson
Invensys Process Systems
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Corey R Clingo
Sent: Thursday, February 03, 2005 11:16 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC Product and Integration with existing I/A tool s

This is good, though it doesn't help me because we only have one 
AW70...and I try to stay off it if I can (Windows boxen tend to lock up 
less frequently that way :).  I would still have to do the VNC thing for 
my 51s.

I guess I ought to RTFM, but how does the IACC server talk to the host AW 
to actually do the CP downloads, particularly if that AW is a 51?


Corey







"Boulay, Russ" <russ.boulay@xxxxxxxxxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
02/03/2005 08:55 AM
Please respond to foxboro

              To:  "'foxboro@xxxxxxxxxxxxx'" 
              cc: 
         Subject:       Re: [foxboro] IACC Product and Integration with
existing I/A tool        s






One of the issues of note is Corey's last statement where he would load 
VNC
to be able to configure control database from different locations.

This is one of the areas that have been missed in these discussions.

With IACC you can have an "off platform" IACC server and then have your
AW70's/WP70's be IACC clients to that server.
The server can also be one of your AW70's.
So using the server/client functions of IACC, config work can be performed
from different locations.

There are the IACC rules of accessing the database one user at a time, but
this would be similar to ICC and have configuration tools from any
workstation that you designated as a IACC client.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
On
Behalf Of tom.vandewater@xxxxxxxxxxxxxx
Sent: Thursday, February 03, 2005 9:35 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC Product and Integration with existing I/A tool 
s

Corey,
You said:
"I like to use iccprt to get configuration data out of the system.  I have
several scripts that parse this data for various purposes.  Even if I did
decide to use IACC for all my configuration, I'd still like to have this
capability.  I suppose if the "ownership" of a CP is determined merely by 
a
text file somewhere, as Doug suggests, it's easy enough to get around,
though even doing what he describes for a quick iccprt dump is more effort
than I'd like."

You may have missed it in all of these postings on this issue but
Iccdrvr.tsk is still supported if you are using IACC even without 
switching
back to ICC so your iccprt scripts should still work.  We, too, are 
heavily
utilizing Iccdrvr.tsk functionality.

Read the last line of the anonymous posting below:

> Did you previously use ICC or FOXCAE?
Yes, ICC, FoxCae and IACC hold no secrets for me, it's my job for over 6
years. ICC is great for changing/building a single block but otherwise
useless in my work. FoxCae is great for generating large databases, it has 
a
very fast and reliable database, but it's a complex, unintuitive program.
IACC is different and has its issues, but has some definitive advantages 
as
well. "Iccdrvr.tsk is also still my good friend."

Tom



 
 
_______________________________________________________________________
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
 

 
 
_______________________________________________________________________
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: