Re: [foxboro] FoxCAE/IACC question

For the benefit of the list, please find a summary below of the solution
that I tested off-list with Tim to get the data and view required going from
IACC to FoxCAE.
Issue 1. When importing, the RIN block would not show up connected to the
ECB201 even if the loop had the ECB201, RIN and AIN blocks on the sheet.
Solution 1.  The database (like 99.99% of others I have both done and seen)
had the RIN blocks IOM_ID parameter addressing the ECB201 in the short
notation (ex.:B3722B).  For FoxCAE to detect and show this as a connection,
the full notation (ex.: CP1304_ECB:B3722B) must be used.  When this was
either changed in the IACC database before performing the export or manually
changed in FoxCAE before performing the backdocumentation, the loops showed
up with all connections.

Issue 2. When importing no FBM data in the form of an I/O connection is
shown on the loop sheets.
Solution 2. When performing the backdocumentation, no tag data is created.
It is from the taglist that FoxCAE extracts the pertinent FBM information to
show on the loop sheet.  No Tag in the loop, no I/O info.  It is possible to
export the Taglist from IACC prior to performing the backdocumentation in
DBF format.  The same DBF export may be imported in the FoxCAE taglist. The
tricky part is getting your dataforms and dataform propagations done upfront
in a way that you wont have to manually massage the data so it shows up the
way you want it once you have preformed the backdocumentation.
Bottom line, with 80% of planning, the transfer of data for Tim's purposes
can be done pretty efficiently and with little manual manipulation.  For the
novice, this will be the hard part, but with the help of someone familiar
with FoxCAE, this can be done with little pain.

If all this seems tedious, that's just because I tend to be verbose (today's
word of the day...verbose)...

Happy importing!

Howard C. Cossitt
National Training Coordinator, Lifetime Learning Center
Invensys Systems Canada
Phone: +1-514-421-8095
Fax: +1-514-421-8059
Email:  howard.cossitt@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Lowell, Tim:
Sent: Tuesday, June 13, 2006 11:00 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FoxCAE/IACC question

We've recently added several new FBM 214 HART FBMs to our system.  To
configure these and other FBMs we bought for the project, we purchased
an AW70XP and a copy of IACC.  Now that the project is completed, we
need to document the as-built loops.  We typically use AutoCAD for loop
drawings, and in the past, we've exported FoxCAE .dwg files to our
draftsmen, who clean them up a bit and incorporate them into an AutoCAD
drawing.  With these new IACC loops, though, we're stuck.  
 

I've been able to export a save-all from IACC into our FoxCAE database,
but FoxCAE doesn't seem to know how to handle the RIN blocks that are
necessary for HART transmitters.  FoxCAE doesn't consider either the RIN
blocks or the AIN blocks they are connected to as I/O tags, so it
doesn't draw a line to the FBM the way it does with a normal AIN or AOUT
block.

 

I have a two-part question, then.  Part 1) Does anyone know how to make
FoxCAE read a RIN block as an I/O tag so that it shows up in the Taglist
and connects to an FBM when you draw a Loop Sheet, and Part 2) Does
anyone know how to directly export an IACC loop to a format that AutoCAD
can read?  Either one of these would fix our problem.  Right now, we are
printing out a screen capture from IACC and handing that to the
draftsman to create an AutoCAD drawing, which is much more effort than
we think we should have to do, seeing as how IACC is a graphical
interface.  Any help would be appreciated.

 

Thanks,

 

Tim Lowell

Control Systems Engineer

ConocoPhillips Trainer Refinery

(610) 364-8362

tim.c.lowell@xxxxxxxxxxxxxxxxxx

 


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