Re: [foxboro] FBM232 and Allen Bradley PLC-5/40E with FDSI Ethernet/Ip
- From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 30 Apr 2010 08:14:11 +0900
We were originally DH+ networked, but were experiencing bandwidth problems
and failures involving physical media. Moving to CNet allowed us to boost
the bandwidth and install redundant networks, as well as allowing us to keep
our MIS network connections for programming and monitoring without having to
re-engineer the corporate network for control level reliability.
It's likely that I'll replace the CNet in each plant area with AB's DLR at
some point in the future. At that point I'll be able to use a
firewalled router on each ring for the MIS/Corporate network connection, and
another access point(s) for FBM232(s).
Glad to hear your 224+ProSoft works well. I'm interested to see if the 232
works as well as I remember the 224 working.
Cheers,
Kevin
On Thu, Apr 29, 2010 at 9:25 PM, Brown, Stanley <
stan.brown@xxxxxxxxxxxxxxxxx> wrote:
> W< TOO ARE USING THE ProSoft and FMB224 solution. We have been able to get
> very high bandwidth, and move all sorts of data, including 32 bit floats
> this way.
>
> ControlNet, huh. What drove you guys to that, instead of Ethernet/CIP?
>
>
> > -----Original Message-----
> > From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of Kevin
> > Fitzgerrell
> > Sent: Thursday, April 29, 2010 8:18 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: Re: [foxboro] FBM232 and Allen Bradley PLC-5/40E with FDSI
> > Ethernet/Ip
> >
> > I've got PLC5s on a controlnet network. The single biggest feature I
> > could
> > use on the CSP driver would be to access those PLCs via a CL gateway
> > (baseplate with ethernet and cnet cards). The Foxboro driver lacks the
> > addressing capability to do this.
> > On the CIP driver, PLC5 addressing has not been implemented (last I
> > checked
> > anyway) so I can't access my PLC5s with this driver either. The next
> > biggest limitation is probably not being able to address tags in add-in
> > instructions.
> >
> > Most of my PLC5 cnet processors have an Ethernet sidecar, however we
> > connect
> > those via our MIS network for programming and monitoring - I don't want
> > control on that network. I don't have a 2nd Ethernet port that I can
> > use
> > for connecting to an FBM232.
> >
> > My best solutions at this point appear to be to use FBM232 with Modbus
> > TCP
> > and ProSoft InRax module and skip the Foxboro AB drivers completely.
> >
> > Regards,
> >
> > Kevin
> >
> >
> >
> >
> >
> >
> > On Thu, Apr 29, 2010 at 8:17 PM, Brown, Stanley <
> > stan.brown@xxxxxxxxxxxxxxxxx> wrote:
> >
> > > I am curious, what functionality do these drivers lack that you need?
> > >
> > >
> > > > -----Original Message-----
> > > > From: Stan Brown [mailto:stanb@xxxxxxxxx] On Behalf Of Kevin
> > > > Fitzgerrell
> > > > Sent: Thursday, April 29, 2010 6:43 AM
> > > > To: foxboro@xxxxxxxxxxxxx
> > > > Subject: Re: [foxboro] FBM232 and Allen Bradley PLC-5/40E with FDSI
> > > > Ethernet/Ip
> > > >
> > > > Which docs are those - Foxboro or AB - that say you can use
> > EthernetIP
> > > > to
> > > > PLC5? My understanding is that Foxboro had implemented a fairly
> > > > limited CIP
> > > > (EthernetIP) driver that works with ControlLogix but not PLC5.
> > They
> > > > have a
> > > > separate Ethernet driver for PLC5s, using CSP but it is also quite
> > > > limited.
> > > > Neither driver appears to be a good fit at my plant.
> > > > Cheers,
> > > >
> > > > Kevin FitzGerrell
> > > >
> > > > On Thu, Apr 29, 2010 at 7:16 PM, <jrmcleish63@xxxxxxxxxxxxxxx>
> > wrote:
> > > >
> > > > > Donato,
> > > > >
> > > > > I'm like Jack and no expert but the documentation does say that
> > you
> > > > can
> > > > > talk EthernetIP to PLC5E. Most of our PLC's are used to scan
> > > > devicenet
> > > > > rather than IO so we have been replacing these with FBM232 Anybus
> > > > > combination. This works well if you only have devicenet. We chose
> > not
> > > > to
> > > > > risk the ethernetIP since we only had a couple of PLC5E's and
> > went to
> > > > FBM230
> > > > > with serial which have proven to be reliable but need a lot of
> > work
> > > > to get
> > > > > your scanning in the right order. Basically once you have
> > arranged
> > > > your data
> > > > > into contiguous blocks by moving them to block transfer
> > reads/writes
> > > > then
> > > > > you can pull a lot of data across the link. If you get them wrong
> > > > comms can
> > > > > be very very slow...
> > > > >
> > > > > cheers, Rob.
> > > > >
> > > > >
> > > > >
> > > > > > Donato Azevedo <donatoaz@xxxxxxxxx> wrote:
> > > > > >
> > > > > > Bothering you gents once again:
> > > > > >
> > > > > > I have given up the idea of having one single FBM to
> > communicate
> > > > with
> > > > > > multiple devices (the idea of having more than one driver
> > image).
> > > > > >
> > > > > > I would like to know if I can interface the FBM232 to an A-B
> > PLC-
> > > > 5/40E
> > > > > > using the Ethernet/IP driver.
> > > > > >
> > > > > > The PSS says it can interface ControlLogix controllers, but it
> > does
> > > > > > not say whether it supports the PLC-5 Ethernet series or not.
> > > > > >
> > > > > > Regards,
> > > > > > --
> > > > > > Donato Azevedo
> > > > > >
> > > > > >
> > > > > >
> > > >
> > _______________________________________________________________________
> > > > > > 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<http://request@xxxxxxxxxxxxx/?subject=join>
> > > > > > to unsubscribe: mailto:foxboro-
> > > > request@xxxxxxxxxxxxx?subject=leave<http://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<http://request@xxxxxxxxxxxxx/?subject=join>
> > > > > to unsubscribe: mailto:foxboro-
> > > > request@xxxxxxxxxxxxx?subject=leave<http://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<http://request@xxxxxxxxxxxxx/?subject=join>
> > > > to unsubscribe: mailto:foxboro-
> > request@xxxxxxxxxxxxx?subject=leave<http://request@xxxxxxxxxxxxx/?subject=leave>
> > > >
> > >
> > >
> > > The information contained in this message and any attached files may
> > be
> > > privileged and/or confidential and protected from disclosure. If you
> > are not
> > > the intended recipient, any disclosure, copying, distribution or use
> > of any
> > > of the information contained in or attached to this transmission is
> > strictly
> > > prohibited. If you have received this transmission in error, please
> > so
> > > notify the sender immediately without reading it. Also, please
> > promptly
> > > destroy the original transmission and its attachments. Any views or
> > opinions
> > > presented in this message or attachments are those of the author and
> > do not
> > > necessarily represent those of KapStone Paper and Packaging
> > Corporation or
> > > its subsidiaries.
> > >
> > >
> > >
> > _______________________________________________________________________
> > > 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<http://request@xxxxxxxxxxxxx/?subject=join>
> > > to unsubscribe: mailto:foxboro-
> > request@xxxxxxxxxxxxx?subject=leave<http://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
> >
>
>
> The information contained in this message and any attached files may be
> privileged and/or confidential and protected from disclosure. If you are not
> the intended recipient, any disclosure, copying, distribution or use of any
> of the information contained in or attached to this transmission is strictly
> prohibited. If you have received this transmission in error, please so
> notify the sender immediately without reading it. Also, please promptly
> destroy the original transmission and its attachments. Any views or opinions
> presented in this message or attachments are those of the author and do not
> necessarily represent those of KapStone Paper and Packaging Corporation or
> its subsidiaries.
>
>
> _______________________________________________________________________
> 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:
