Experimental Physics and
Industrial Control System

> In the dev system, everything seems to boot and operate normally.  In the prod
> system, I get a large burst of "error interrupts" when the GPIB board is
> initialized or serviced.  Seems simple enough.  But there's more.
> 

Perhaps you have some sort of interrupt vector collision. Here is how 
to check:

1) load iocCore 
2) run "veclist()" from the vxWorks shell
3) run "iocInit" from the vxWorks shell
4) run "veclist()" again from the vxWorks shell and look for collision


Perhaps there is a high network load and this is resulting in poor VME
interrupt throughput to the GPIB board. Perhaps "ifShow", "ipstatShow",
and "icmpstatShow" from the vxWorks shell will be useful. Also take a 
look at the LAN LED on the 167's front panel for a rough indication
of the network load.

Try the following test to see if the network is involved:
1) load all objects and databases from the NFS server
2) disconnect the network cable
3) run "iocInit" from the vxWorks shell comparing the GPIB
driver init to past behavior.

Jeff



______________________________________________________________________
Jeffrey O. Hill			Internet	[email protected]
LANL MS H820			Voice		505 665 1831
Los Alamos, NM USA 87545	FAX		505 665 5107

Navigate by Date:

Prev: "The problem admits of no explanation...." Bill Brown

Next: VxWorks development machine Tony Carter, MIT Bates Linac

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: "The problem admits of no explanation...." Bill Brown

Next: VxWorks development machine Tony Carter, MIT Bates Linac

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