Hello Jeff:
At the SNS we're using drvEtherIP V2.19 without known problems.
> -> tt 0x1b22fd0
> 194e58 vxTaskEntry +60 : 1c286f4 ()
> 1c28860 epicsTimeToStrftime+12a8: 1c28150 ()
> 1c2868c epicsTimeToStrftime+10d4: 1c244ec ()
> 1c24878 drvSerialGetFile+bac: scanOnce (1bdff10)
> 13eafc rngBufPut +e0 : bcopy ()
Do you always get this type of stack trace with
unknown, unknown, unknown, scanOnce, bcopy?
I don't see how bcopy() fits in, but if the PLC driver really called
scanOnce it might be helpful to see which method in devEtherIP.c invoked
scanOnce.
The arg to scanOnce should be the record that's to be scanned. Peeking into
that memory might give the record name, and then you can narrow down which
type causes this problem.
Or try to run the same PLC database in a Linux soft IOC under valgrind to
see if that shows memory access problems.
Thanks,
Kay
- References:
- issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP Jeff Hill
- Navigate by Date:
- Prev:
RE: issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP Allison, Stephanie
- 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
- Navigate by Thread:
- Prev:
RE: issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP Allison, Stephanie
- Next:
Re: issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP Steven M. Hartman
- 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
|