Re: [foxboro] AB30 TO FBM231
- From: "Bill Walters" <bwalters@xxxxxxxxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 3 May 2007 12:30:27 -0600
Ricky - I am facing the same issue where we used the AB30 gateway and =
will be
using the FBM230.
I have had to use the FBM224 for MODBUS in applications where I had used =
the
MODBUS Integrator 30. Very similar to the FBM 230 issue. Except the =
FBM230
series needs drivers installed before it knows it is supposed to talk to =
DH+
device and not MODBUS or something else.
In answer to your question. Yes, you will have a lot of new =
configuration
ahead of you. PAKIN's, PAKOUT, IIN, IOUT etc. There will be some
configuration files instead of MDSCAN.
But there is some good news too. There appears to be better diagnostic
capability with the new foreign device interfaces. And they reside in =
the
I/O cabinet.... closer to the foreign device.=20
Bill Walters
Chief Engineer
Sinclair Wyoming Refining Company
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Ricky.Cash@xxxxxxxxx
Sent: Thursday, May 03, 2007 11:08 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] AB30 TO FBM231
I have several AB30 gateways communicating with PLC5 processors in my=20
system. I am making plans to upgrade to the mesh system which would=20
include FBM231 comm modules to replace these gateways. The FBM231 =
doesn't=20
support the MCIN and MCOUT blocks that I now use, it looks like I would=20
have to use PAKIN and PAKOUT blocks. Has anyone on the list been through =
this upgrade? I really don't want to do a complete rebuild of the =
gateway.
Thanks for any help you can provide,
Ricky Cash
Process Control Engineer
Greif Inc.
Amherst VA
CONFIDENTIALITY NOTICE: This message and its contents are confidential =
and
are intended solely for the use of the addressee.
If you are not the intended recipient, you are hereby notified that any =
use,
dissemination, distribution, or copying of this message and its contents =
is
strictly prohibited. In addition, please contact the sender by e-mail =
and
delete the original message immediately. Thank you for your =
cooperation.
=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
Other related posts:
