Re: [foxboro] FoxCAE Backdocumentation
- From: "Burbach, Norbert" <nburbach@xxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 29 Mar 2005 14:27:30 -0500
You can't force a reload of a loop. You need to delete the loop in the 'Loop
Database' in order to regenerate it with new/added blocks or you have to
manually move the blocks to the new loops.
Norbert
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Meredith, Travis ASE
Sent: Tuesday, March 29, 2005 12:41 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxCAE Backdocumentation
Thanks. I gave this a try but it didn't work as this seems to be a =
little more of a specific case:
I reloaded the CP's on top of the existing FoxCAE database. The only =
changes made were to LOOPID's. The intention is that I'm trying to move =
some blocks to different loops within FoxCAE by manipulating the LOOPID =
of those blocks. When I reload, the modified LOOPID's are updated in the =
block parameters in FoxCAE. However, I'm not given the option to =
re-backdocument these blocks and therefore I cannot have them relocate =
to their intended loops.
Is there a way to force a reload of the loops with the new block =
LOOPID's?
Travis
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Burbach, Norbert
Sent: March 29, 2005 8:57 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] FoxCAE Backdocumentation
Travis,
Don't delete the current blocks in FoxCAE. Just load the uploaded blocks
back on top of the FoxCAE database. All changed parameters get replaced. =
New
block you have to back document or to add to existing loops.
Norbert
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Meredith, Travis ASE
Sent: Tuesday, March 29, 2005 10:44 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FoxCAE Backdocumentation
Hello list. I am trying to run a backdocumentation of our system using
FoxCAE. I would like to use the method using LOOPID's to create loops =
based
on the current system configuration. To do this I took the following =
steps:
1. first uploaded all CP's
2. Selected "Undoc" blocks
3. Selected all compounds
4. Use the backdocumentation command (checked "Use the LOOPID parameter" =
&
checked "Update Existing Loop information")
This created loops exactly as I want. I am then able to enter info into =
the
loop sheets such as titles, refs etc.
Now, I would like to update these loops with a fresh system =
configuration.
To do this I took the following steps:
1. Deleted all current blocks, compounds, & CP's in FoxCAE (while =
leaving
the loops remaining with title block info etc).
2. Re-upload all CP's
3. Selected "Undoc" blocks
4. Use the backdocumentation command (checked "Use the LOOPID parameter" =
&
checked "Update Existing Loop information")
Basically this is the same procedure as before. Only now, the blocks do =
not
get updated into their original loops (named after the LOOPID). Now the
blocks are exported to new loops with the following naming convention:
'COMPOUND''LOOPID'.
My question is: How do I update existing loops with new CP uploads while
keeping the original loops (with my manually entered title block info) =
that
were created from the first backdocumentation?
Thanks,
Travis
Travis Meredith
DCS Programmer
Albian Sands Energy Inc
P.O. Box 5670, Fort McMurray, Alberta, T9H 4W1, Canada
Tel: +1 780 713 4767
Email: travis.meredith@xxxxxxxxxxxxxx
Internet: http://www.albiansands.ca
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
--=20
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 3/27/05
=20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 3/27/05
_______________________________________________________________________
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: