Tom, I am currently away from my system so I can't verify the filenames. The first time I setup a CP with IACC I used the document B0400BT_C - Learning to Use IACC It's a step by step guide which when I followed it, everything worked ok. Hope this helps, Maks Wilde On Tue, Apr 1, 2014 at 1:25 PM, Pulas, Philip <Philip.G.Pulas@xxxxxxxxxxx>wrote: > Tom, > > I don't have IACC, but did you pass the Commit through more than just the > host AW for the new FCP? I thought IACC had one AW that kept a master > database, something equivalent to CSA Server, but for IACC. > > Thanks, > Philip Pulas > Lead Engineer, Process Systems > Tesoro Golden Eagle Refinery > Ph: (925) 372-3043 > Email: philip.g.pulas@xxxxxxxxxxx > > -----Original Message----- > From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] > On Behalf Of Tom VandeWater > Sent: Tuesday, April 01, 2014 10:00 AM > To: foxboro > Subject: [foxboro] Adding New FCP to System and downloading via IACC. > > To All, > I added a new FCP, (F270FT named CP0013), to System Definition, > created commit disk, and successfully installed the new CP on the host AW. > The new FCP booted up successfully and I can see it in SMDH/Sysmon. I can > ping CP0013 so I know the host file in C:/Windows/System32 is correct and > being accessed. The FTMAC Address in System Def and IP Address match what > I see in SMDH, EQUIP INFO and I can Image Update, Reboot, and Checkpoint > from SYSMON. FoxSelect shows the CP and the Station and ECB compounds. > All sounds good to this point. > > The problem is this. I MUST use IACC for configuration. I tried > everything I could read about but still cannot successfully download the > new FCP from IACC. Here were my steps: > > 1. I have never accessed the CP via ICC, (although I really want to;<) > > 2. I edited the file D:/opt/fox/IACC/CoExistence/IACC-CP and added the new > CP0013 and IP address. The CP's previously on the system show up in there > already and can be accessed and downloaded from IACC. > > 3. Reviewed D:/opt/fox/IACC/CoExistence/IACCSGsettings.dat to verify > values for [INTERVAL] and [LOGMESSAGES] were both set to 1. As I > understand it "1" for INTERVAL means that once per minute the > IACCSafeguards.exe will enforce that the stations defined in > D:/opt/fox/IACC/CoExistence/IACC-CP > can only be accessed via IACC. > > 4. I executed D:/opt/fox/IACC/bin/IACCSafeguards.exe > > 5. I entered IACC and tried to add the new CP to the existing IACC > database. I could set the IP address to match what SysDef had defined but > the FTMAC address IACC assigned was not the same as what SYSDEF and the > live system show. I can't change it to be correct. > > 6. I generated an export disk from SysDef and tried to import it into the > plants existing IACC database but IACC says it needs a clean/initial > database to import the SysDef export. Not sure how you can add a new > station to an existing IACC database with the correct FTMAC. Any guidance > is appreciated. > > 7. I created a new database by creating a new folder in > D:/opt/fox/IACC/Database named "My_New_DB" and then copied the files from > D:/opt/fox/IACC/Database/EmptyDb into "My_New_DB" folder. I could then > import the updated SysDef into "My_New_DB" database and the the old and new > CP's all have correct IP address and FTMAC address. > > 8. I open up IACC and select "My_New_DB" project but when I try to > download to CP0013 I get this error: > > "Control Station Download Agent Error. Download Failed. Reason: OPEN > CP0013!:ICC OPEN error: icOpenSession: OPEN ACCESS by IACC not allowed. > > When I look in D:/usr/fox/sp/locks I see a file named fCP0013 which I > know means it is locked. If I remove that lock file from > D:/usr/fox/sp/locks and try again the lock file reappears at the time I try > to download from IACC. It looks like ICC has taken ownership and won't let > IACC access the new CP. > > Is there another hidden file I need to edit to make ICC give it up? > > Thanks for any help. I assume there is an easy answer to this but > haven't been able to find any other solution. Surely using IACC can't be > this difficult to achieve. > > Regards, > > Tom VandeWater > > Control Conversions, Inc. > > > > > _______________________________________________________________________ > 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 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 > > -- > Confidentiality Warning: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential, and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, retransmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return e-mail, and delete this message and any attachments > from your system. > _______________________________________________________________________ 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