EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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  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 
<== Date ==> <== Thread ==>
Subject: Re: issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP
From: "Steven M. Hartman" <[email protected]>
To: Jeff Hill <[email protected]>, "[email protected]" <[email protected]>
Date: Thu, 09 Sep 2010 13:28:18 -0400
Jeff Hill wrote: 
-> tt 0x1b22fd0
194e58 vxTaskEntry    +60 : 1c286f4 ()
1c28860 epicsTimeToStrftime+12a8: 1c28150 ()
1c2868c epicsTimeToStrftime+10d4: 1c244ec ()
1c24878 drvSerialGetFile+bac: scanOnce (1bdff10)
13eafc rngBufPut      +e0 : bcopy ()

Hello, Jeff--

We have a large number of VxWorks IOC running ether-ip 2.19 and we have not seen this problem.

From the limited information in the task trace, it looks like one of the check_xxx_callback functions in devEtherIP.c is calling scanOnce(rec). In dbScan.c, I'm guessing epicsRingPointerPush() is calling rngBufPut (or at least something nearby) which is calling bcopy which is apparently trying to use some memory which it shouldn't, throwing an exception.

As Kay pointed out, the argument to scanOnce() should be a pointer to a record. As long as this is a valid pointer to a valid record, I don't see how this exception could be caused by a bug in ether-ip. Can you poke around 0x1bdff10 and see what's there? If it is not really a record, try to get some more information as to what is happening (EIP_verbosity=7 or more, maybe recompile devEtherIP without static for the check_xxx_callback functions so the trace will tell us which one, set record TPRO=1, etc).

Also, can you run your IOC stripped down without the other device drivers? It could be that some other driver is clobbering some memory somewhere which ether-ip is stumbling over.

--
Steven Hartman
[email protected] || 865-466-6473
References:
issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP Jeff Hill
Navigate by Date:
Prev: controlling cross compiled build products Pelaia II, Tom
Next: ca client get waveform pv error wantianmin
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: issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP Kasemir, Kay
Next: controlling cross compiled build products Pelaia II, Tom
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, 09 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·