Re: [foxboro] FBM232 and Allen Bradley PLC-5/40E with FDSI Ethernet/Ip
- From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 29 Apr 2010 19:42:59 +0900
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
> > 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:
