Although I realize that this is not Chip's first priority for fixing the
problem, I would still be interested to know the nature of the CAMAC error that
causes the CAMAC driver (and/or scan task) to eat up the CPU at CEBAF & Triumf.
If you run
camacIoReport 2
or
camac_io_report 2
(depending on which version of the driver you have) on the offending IOC, what
does it say?
Eric Bjorklund
LANSCE
- Navigate by Date:
- Prev:
Re: flaky IOC problems at Jefferson Lab watson
- Next:
Re: flaky IOC problems at Jefferson Lab Jeff Hill
- 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:
Foundation FieldBus Russell J. Page, Sr.
- Next:
PC/WIN32 Display Options 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
|