I wish there were a way to get a cross reference list for all the PLB = blocks linked to one FBM. The way I do it is to go to FBM/Ladder = assignment, get the list of PLB blocks, then get the cross reference = list for each block and make by hand a summary sheet. Is there a better = way? Andre -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Johnson, Alex (Foxboro) Sent: Thursday, May 12, 2005 12:16 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Reduce IFL's for FBM A few facts: * You may have multiple (8, I think) PLB blocks per FBM. * An FBM has a fixed number of rungs (100 or 150 I think) with a fixed number of symbols (500, I think). * The number of PLB blocks DOES NOT increase the number of IFLs, OFLs, rungs, and symbols. * The use of multiple PLBs per FBMs is a good way to go crazy - trust me on this. =20 Does this help? =20 Regards, =20 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 =20 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] = On Behalf Of Douglas G. Lloyd Sent: Thursday, May 12, 2005 1:13 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Reduce IFL's for FBM =20 Before you folks get too carried away, I don't think that you get more = IFLs or OFLs by splitting up the PLB into multiple blocks. These resources = are maintained in the FBM itself, with supporting logic in the PLB blocks. = In fact, when using multiple PLB blocks you need to be very careful about overlapping resources. If resources ARE overlapped, the last processed block "wins" and overwrites any previous logic. =20 Regards, =20 Doug Lloyd DGL Controls =20 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] = On Behalf Of Dirk Pauwels Sent: Thursday, May 12, 2005 11:28 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Reduce IFL's for FBM =20 That's interesting, I've never tried it either, the number of cout's is=20 still restricted to the FBM, but more ifl's offer more possible = interlocks. =20 Rgds, =20 Dirk =20 >From: brad.s.wilson@xxxxxxxxxxxxxx >Reply-To: foxboro@xxxxxxxxxxxxx >To: foxboro@xxxxxxxxxxxxx >Subject: Re: [foxboro] Reduce IFL's for FBM >Date: Thu, 12 May 2005 10:21:37 -0500 >=20 > >>> Martin Theobald wrote <<< >Reading the documentation (Volume 3 of B0193AX - Rev N) suggests that = each >FBM can support up to eight PLB blocks. This is not a feature I have = tried >or seen used. >=20 >Yes, we have a couple of FBMs with multiple PLBs, although I remember = that >there is a limit to the TOTAL number of lines in all PLBs running in an >FBM. I seem to recall that the number of lines allowed in an FBM is = the >constant, regardless of the number of PLBs. But this would certainly = allow >for more IFLs & OFLs. >=20 >Brad Wilson >ExxonMobil Chemical Co >Edison Synthetics Plant >732-321-6115 >732-321-6177 fax >Brad.S.Wilson@xxxxxxxxxxxxxx >=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: //www.freelists.org/list/foxboro >to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin >to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave >=20 =20 _________________________________________________________________ =20 =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: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 =20 =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: //www.freelists.org/list/foxboro to subscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: = mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =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: //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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave