EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: EtherNet/IP for AB SLC5/05 PLC.
From: Kay-Uwe Kasemir <[email protected]>
To: john sinclair <[email protected]>
Cc: Kiman Ha <[email protected]>, [email protected]
Date: Mon, 8 Mar 2004 10:30:38 -0700
On 2004.03.08 09:59, john sinclair wrote:
> Kay,
> 
> Is this also true for FlexLogix I/O?
Don't know FlexLogix I/O, but I'm afraid 
the EPICS driver for the ControlLogix 5000 PLC
is really specific to the ControlLogix 5000
and its CIP service codes 0x0A, 0x4C, 0x4D. 

The ControlNet/EtherNet/IP specifications include
an "Object Library".
In there you find an "Identity" object.
Any EtherNet/IP decide implements that.
The EPICS driver for the Logix 5000 uses queries it
to get the serial number of the Logix 5000 ENET module.

There is a "Message Router" object:
We use that to get from the ENET module to the Logix 5000
controller (where the ladder logix runs).
When I contact the MessageRouter on FlexLogix I/O
the same way I contact the MessageRouter onthe Logix 5000
ENET module, I'm pretty sure the response will be:
"Invalid Path", because the path from the Logix 5000 ENET module
to the controller in slot 0 of the Logix 5000 backplane
simply doesn't exist on FlexLogix. 

Then there are "Discrete Input Point", "Output Point",
"Analog Input Point" etc. objects:
Maybe you can use those to access I/O points
on any "EtherNet/IP" device.
But I was't getting anywhere with them for the
Logix 5000. And in order to read/write tags in
the Logix 5000 ladder logic, which is what I
ultimately wanted to do, I had to use the Logix-specific
service tags.

So talk about a device using "EtherNet/IP" and thus
being compatible is just like me handing you
the telephone number of my aunt in Germany:
Your telephone is certainly compatible with hers,
but I think the communication wouldn't go past a
> "Hello?"
< "Hallo?"
> "Do you speak English?"
< "Sprechen Sie Deutsch?"
> "Hello?"
< "Hallo?"
- click -
- Klick -


> 
> John Sinclair
> 
> On Monday 08 March 2004 11:13 am, Kay-Uwe Kasemir wrote:
> > On 2004.03.08 02:24, Kiman Ha wrote:
> > > Hello! Kay and Stephanie,
> > > Last Feb, I asked about AB SLC5/05 processor for Ethernet TCP/IP EPICS
> > > driver and support.
> > > The AB Comapny people said SLS5/05 PLC processor support EtherNet/IP.
> >
> > Yes, it might support the common portion of the EtherNet/IP
> > protocol, the part that's documented at www.odva.org.
> >
> > That will allow you to read the serial number of your SLC5/05's
> > ethernet interface.
> >
> > In addition, you need the CIP service codes that are specific
> > to your PLC, the ones that allow you to read/write tags
> > or files or whatever the data of interest is called on the
> > respective architecture.
> >
> > > I known your alread developed EtherNet/IP drivers and support for SNS
> > > project.
> >
> > That EtherNet/IP driver package uses the CIP codes for the
> > AB ControlLogix 5000 series as described in
> > AB Publication 1756-RM005A-EN-E.
> >
> > The latter publication also lists SCL commands,
> > but they are very different from the CIP service codes
> > for the ControlLogix series.
> > Control Logix uses CIP service codes
> > 0x4C : read data
> > 0x4D : write data
> > 0x0A : multi request
> > and all those adress string tags on the Logix5000.
> >
> > As far as I know, the SCL5 doesn't have string tags
> > but uses file/element/subelement addressing.
> >
> > So I'm afraid those AB people who talked to you can
> > recite "EtherIP" from some SLC5 brochure but don't
> > really understand the protocol.
> >
> > This means that the ether-ip driver for the ControlLogix 5000 won't
> > talk to the SLC5, and making it talk to the SLC5 would be a major deal,
> > close to starting from scratch.
> 
> -- 
> John Sinclair
> 
> 

References:
EtherNet/IP for AB SLC5/05 PLC. Kiman Ha
Re: EtherNet/IP for AB SLC5/05 PLC. Kay-Uwe Kasemir
Re: EtherNet/IP for AB SLC5/05 PLC. john sinclair

Navigate by Date:
Prev: RE: [Fwd: LabView/EPICS] Leng, Yongbin
Next: RE: [Fwd: LabView/EPICS] Liyu, Andrei
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: EtherNet/IP for AB SLC5/05 PLC. john sinclair
Next: VMIC 2510B driver and device support Kristi Luchini
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·