Re: [foxboro] Tricon ACM upgrade
- From: Richard Peck <lovetomix@xxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Sat, 14 Sep 2013 09:20:01 +1000
Hi,
Do we have details on how the new Triconex Comms Modules will interface
with IA?
From my understanding we are finally getting Triconex on the Mesh - but
there are no details yet on how it works.
Do the new comms modules (ACM II?) have a CP280 inside? Do we allocate
compounds and blocks within it?
It is very exciting :)
We currently use 2 CP270's each with a Redundant FBM233 connected to the
Tricon. One of the CP's has almost the limit of 2000 blocks reading from
the Tricon and the other one has in the order of 1000. From these two CP's
the data is sent over the mesh to displays and the other 12 CP's performing
control...
So - we are excited to see if we could replace this with the new ACM II?
Ta:)
On 14 September 2013 07:42, <Rguercio@xxxxxxx> wrote:
> Very sound advice.
>
> Rick Guercio, P.E.
> RG Consulting
> 918 E Desert Shrub Drive
> Washington, UT 84780
> 713-805-8742 cell
>
> In a message dated 9/13/2013 3:28:01 P.M. Eastern Daylight Time,
> Alex.Johnson@xxxxxxxxxxxx writes:
>
> One other consideration.
>
> I would not replace my AIN/AOUT/CIN/COUTs from FoxGuard Manager with
> RIN/ROUT/BIN/BOUTs.
>
> Rather, I would:
> 1) Add the RIN/ROUT/BIN/BOUT blocks
> 2) Put the existing I/O blocks in software input mode (IOMOPT=0 or 2) and
> connect those to the output of the new blocks.
>
> This step prevents you from having to change the names in "downstream"
> users, e.g., FoxView, Historian, and Peer-to-Peer connections.
>
> You won't run out of blocks. Since FoxGuard Manager only supported 600 and
> the CP270 supports 4000, you would have to combine quite a number of
> FoxGuard Managers to reach that limit.
>
> Regards,
>
> Alex Johnson
> Invensys Operations Management
> 10900 Equity Drive
> Houston, TX 77041
> +1 713 329 8472 (desk)
> +1 713 329 1600 (operator)
> +1 713 329 1700 (Central Fax)
> alex.johnson@xxxxxxxxxxxx
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Tadeo Armenta
> Sent: Friday, September 13, 2013 7:27 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Tricon ACM upgrade
>
> Hello,
> You can only pack coil registers with PAKIN/PAKOUT blocks. Analogs you
> will have them in RIN/ROUT blocks single.
>
> Its a little hostile but remember that you only need that the end block
> remains the same for display/control loop purposes. An excel file and some
> taglists (IACC), bulk configuration (Archestra) or the almighty iccdrv.tsk
> will do it in short time.
>
> Regards
>
>
>
>
> ________________________________
> De: "c.a.wolfschlag@xxxxxxxxxxxxxx" <c.a.wolfschlag@xxxxxxxxxxxxxx>
> Para: foxboro@xxxxxxxxxxxxx
> Enviado: Viernes, 13 de septiembre, 2013 7:07 A.M.
> Asunto: [foxboro] Tricon ACM upgrade
>
>
> I have several existing Triconex systems that are using the Tricon
> Advanced Communication Modules (ACMs) along with Foxgards to pass data to
> and
> from the Tricon and IA. The ACM is becoming obsolete and the replacement
> Tricon Communication module (TCM) will require a new IA interface via a
> FBM
> 232.
> In the Foxgard we used ECB's 90, 91 & 93's to read the Tricon alias and
> then created AI's, CIN's in IA to display, alarm and trend data. With
> these
> ECB's I can map 16 aliases on one block. I don't see anything like that
> with the FBM232, it appears to me that I will have to create a new block
> for
> each alias I want read/write?
> My question ... has any one replaced the ACM with a TCM? Is there an easy
> way to map multiple aliases with a FBM232? Any help or suggestions would
> be greatly appreciated.
>
>
>
>
> _______________________________________________________________________
> 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 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 plc, 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.
>
>
> You may contact Invensys plc 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 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
Other related posts:
