Geoff Savage wrote:
>
> Here's what I found to resolve this problem.
>
> Somehow the INST_IO field in the device declaration had been changed to
> VME_IO for devAiVXStats and devAoVXStats in base.dbd.
>
Please note that this is documented in the release notes. The change occured
between 3.13.0beta11 and 3.13.0beta12. The notes state:
devVXStats
Major rewrite of this routine. It computes the cpu usage via a low priority task
rather than using spy. It reports file descriptor usage rather
than tcp connections (this is what is actually measures). The format of the INP
,and OUT fields has changed since the previous version. The
new device definitions are:
device(ai,INST_IO,devAiVXStats,"VX stats")
device(ao,INST_IO,devAoVXStats,"VX stats")
The INP fields now have the form
field(INP,"@memory")
field(INP,"@cpu")
field(INP,"@fd")
The OUT fields now have the form
field(OUT,"@memoryScanPeriod")
field(OUT,"@fdScanPeriod")
field(OUT,"@cpuScanPeriod")
The source file has comments showing a sample database.
Marty Kraimer
- References:
- vxworks statistics Geoff Savage
- SUMMARY: Re: vxworks statistics Geoff Savage
- Navigate by Date:
- Prev:
SUMMARY: Re: vxworks statistics Geoff Savage
- Next:
Re: eddCvrt1.16To2.2 Deb Kerstiens
- 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:
SUMMARY: Re: vxworks statistics Geoff Savage
- Next:
Re: imageRecord Leonard J. Reder
- 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
|