Experimental Physics and Industrial Control System
I'm trying to talk to a Agilent E2050B using GpibCore 1-1 under EPICS
3.14.2 running on RedHat Linux Enterprise. During startup, I get the
following sequence:
drvVxi11Config(0, "tsp-gpibdev.als.lbl.gov", 0, 0, "hpib", 0)
drvVxi11 (release 1.0) initialized successfully
E2050Reboot("tsp-gpibdev.als.lbl.gov")
drvVxi11 (release 1.0) initialized link 0
epicsThreadCreate vxiReconnect
Broken pipe
Followed by the IOC aborting to shell. The target GPIB interface does
seem to indicate with blinking lights that it got reset.
Anybody run into this before that can tell me what's I'm doing wrong?
Thanks!
--
Eric Williams
ALS Controls, LBL
- Replies:
- Re: GpibCore generates "broken pipe" Eric Williams
- Navigate by Date:
- Prev:
Re: ca_repeater bug (was Bugs in 3.14.5) Kate Feng
- Next:
Re: GpibCore generates "broken pipe" Eric Williams
- 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: ca_repeater bug (probably observable only on RTEMS) Till Straumann
- Next:
Re: GpibCore generates "broken pipe" Eric Williams
- 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