Experimental Physics and Industrial Control System
|
Kay,
I set EIP_verbosity = 10 and it appears that the identity check
(EIP_check_interface) is failing only because Get_Attribute is returning
52 bytes where your code (ether_ip.c line 2212) requires less than 34
bytes for the Name attribute.
John
Kay-Uwe Kasemir wrote:
Hello:
On Apr 5, 2006, at 14:59 , John Dobbins wrote:
I have just used the EPICS Ethernet/IP device support to talk to an
Allen Bradley CompactLogix (i.e. not ControlLogix) module.
So far I have written a bit to a DINT and read a PLC boolean. The only
trouble encountered was an error/warning message on start-up:
drvEtherIP: launch scan task for PLC 'compactlogixtest'
EIP_startup: cannot determine target's identity
Well, unless there's some other error in the code that I don't see, this
means:
The driver tried several "GetAttributeSingle" calls on the "Identity
Object"
of the device, and that failed.
Specifically, it's trying to read the Vendor ID, Device Type, Revision,
Serial # and Product Name,
which are all "Attributes" of that "Identity" object.
That was about the first thing I tried when implementing the driver.
I don't really care about the result except for diagnostics purposes,
so the driver will march on even if that fails
- and that seems to work out OK for your test.
But the thing is:
The ControlNET specification that I used when implementing the driver
(Release 2.0 Errata 2) makes no mistake that ".. the Identity Object shall
be present in all devices". And while some of its attributes are optional,
the Vendor ID ... Product Name are "Required" (Part 10a, p.2 & 3 of the
specs).
This tells me that CompactLogix isn't fully spec compliant.
Might be OK, who cares about the serial number?
Might be problematic, because what else is different in the CompactLogix
interpretation of the specs?
Before I go any further with this test I wanted to ask if there is any
chance of EPICS community support for CompactLogix - OR - should I
send back this loaner, tell my colleagues that EPICS only supports
ControlLogix, and turn my attention to other tasks?
This test came about because a colleague was interested in
CompactLogix as it appeared to have lower capital costs. I gave them
the spiel about EPICS device support only being demonstrated to work
with ControlLogix but said if they could get a loaner I would give it
a try.
Well, the beauty of the community is that several other people might be
very interested in CompactLogix
and work with you on this.
As for me, I developed that driver because I originally needed it for my
SNS-related work.
I still maintain it as far as bug fixes and adaptation to new EPICS
releases are
concerned, and I would gladly attempt to incorporate any modifications that
allow its use with CompactLogix.
But since I'm not using CompactLogix, actually have not been using
ControlLogix
in any of the subsystems assigned to me for years, it is very unlikely
that I
can provide more active support for a CompactLogix adaptation.
-Kay
- Replies:
- Re: Ethernet/IP Device Support and CompactLogix Kay-Uwe Kasemir
- References:
- Ethernet/IP Device Support and CompactLogix John Dobbins
- Re: Ethernet/IP Device Support and CompactLogix Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
RE: EPICS record names: disallowed characters? Dalesio, Leo `Bob`
- Next:
Re: Ethernet/IP Device Support and CompactLogix Kay-Uwe Kasemir
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
<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 Device Support and CompactLogix Kay-Uwe Kasemir
- Next:
Re: Ethernet/IP Device Support and CompactLogix Kay-Uwe Kasemir
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|