Re: [foxboro] Adding New FCP to existing system and downloading via IACC
- From: "Boulay, Russ" <Russ.Boulay@xxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 1 Apr 2014 19:55:20 -0400
Actually my last sentence previously is not absolute correct.
As long as coexistence has the hosting correct....and knows which host to go
to...then you are good on the IACC side.
On the CP host, the IACC-CP file will override the coexistence file.....so that
is why I make my changes there when needed to use IACC or ICC
_____________________________________________________________________________________
Russ Boulay | Schneider Electric | Invensys | United States | Support
Engineering Manager
Phone: +1 508 446 1769 | Mobile: +1 508 446 1769
Email: russ.boulay@xxxxxxxxxxxx | Site: www.invensys.com | Address: 2000 Crow
Canyon Place Suite 170, 94583 San Ramon, California, United States
*** Please consider the environment before printing this e-mail
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Boulay, Russ
Sent: Tuesday, April 01, 2014 4:47 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Adding New FCP to existing system and downloading via
IACC
I think Normand was trying to say two IACC-CP files in the same directory, but
just guessing.
In our lab...the only file I ever touch is /usr/fox/sp/files...as that is the
motherlode for this operation.
The coexistence location and then the subsequent safeguards.exe is just to
propagate the IACC-CP in coexistence to all AW's listed in the IACC-CP file.
So can just cut to the chase and go directly to /usr/fox/sp/files and edit the
IACC-CP file on each host...
Coexistence is only in the IACC directory of the IACC server which could be off
or on platform.
And using it as the master file.....safeguards then copies the file to the CP
host as listed in the file.
Coexistence could be blank.....as long as /usr/fox/sp/files/IACC-CP is
edited...you are good to go.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Tom VandeWater
Sent: Tuesday, April 01, 2014 4:32 PM
To: foxboro
Subject: [foxboro] Adding New FCP to existing system and downloading via IACC
To All,
Only Normand Bergeron told me about the duplicate files with the same name.
(I love you Norm;<) Did anyone else realize that there are actually two files
with the exact same name, (IACC-CP), but they are stored in two separate
locations?
/usr/fox/sp/files/IACC-CP
and
/opt/fox/IACC/CoExistence/IACC-CP
Or that you must edit both of them to make it work? Again, I don't
want to shoot the messengers that helped solve the problem. I really
appreciated everyone that spoke up.
The real problem stems from incomplete documentation coupled with a very poor
design solution reminiscent of the mid 80's when everything was done on a
command line. I know many wish it was still that way, but when I show young
engineers using newer systems/tools, they give me the "dinosaur" look and I
understand why;<) Not saying Foxboro's newer offerings are this way because I
don't know. I am one of the dinosaurs.
BTW, I used the instructions in:
B0400BP REV G
Configuration Component (IACC)
User’s Guide
September 28, 2007
That document is incomplete and misleading as you can see by reading an excerpt
below:
Thanks again to all.
Tom VandeWater
Control Conversions, Inc.
"Enabling IACC Downloads to a Control Station
While IACC was developed as a replacement for the Integrated Control
Configurator (ICC), the software supports co-existence with ICC and with
FoxCAE, which uses the facilities of IACC to perform control downloads. You can
use either IACC or ICC to maintain the control configuration in a specific
control station, but you cannot use both for the same station.
The IACC Safeguard program runs in the background on an IACC server to prevent
ICC downloads to IACC stations and IACC downloads to control stations that are
being maintained with ICC. The user-created IACC-CP file on the server
specifies which CPs are to be configured with IACC and lists the host
workstation for each CP. The IACC Safeguard program sends the IACCCP file to
the listed workstations. The workstations, in turn, check the file before
allowing a download from either IACC or ICC:
♦ If the target CP is listed in the IACC-CP file, the workstation allows
downloads from IACC, but not from ICC.
♦ If the CP is not designated in the file (or if there is no IACC-CP file on
the workstation), the workstation permits downloads from ICC, but not from IACC.
NOTE
When there are multiple IACC servers, the IACC-CP file should be created on one
server and the IACC Safeguard program should run on that server for all CPs and
host workstations on the network.
To designate control stations as IACC CPs:
1. Open ..\IACC\CoExistence\IACC-CP using Notepad or a similar text editor.
2. Follow the template in file to list the IACC control stations.
For each station, insert a line with the control station name, and the name and
IP address of its download host.
You must use a tab to separate the three elements in the list.
Make sure that you specify the ethernet address used by IACC:
♦ The second Ethernet port when IACC is installed off-platform or when IACC is
being used in an I/A Series environment that includes a 100 Mbps switched
control network and a legacy 10 Mbps Nodebus (see the configuration in Figure
1-3 on page 3).
♦ The main Ethernet port specified during system configuration of the download
host when IACC is being used to configure an I/A Series Version 8.x system, and
the IACC server and clients are implemented on I/A Series workstations and
communicate with the download hosts directly over The Mesh Control Network (see
the configuration in Figure 1-4 on page 3)."
_______________________________________________________________________
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
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys Limited, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please select the Legal Entities link at invensys.com.
Invensys Limited is owned by the Schneider-Electric Group.
You may contact Invensys Limited on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys Limited, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please select the Legal Entities link at invensys.com.
Invensys Limited is owned by the Schneider-Electric Group.
You may contact Invensys Limited on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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:
