Re: GpibCore generates "broken pipe"

[Marty Kraimer <mrk@aps.anl.gov>]

Since asynDriver is the sucessor to gpibCore, gpibCore is no longer 
supported. See

http://www.aps.anl.gov/epics/modules/soft/asyn

Marty Kraimer

Eric Williams wrote:

> OK, figured it out.  The Reboot has to be called before the Config.  
> The documentation file has the calls in the wrong order, this should 
> be fixed.
> --
> eric
>
> Eric Williams wrote:
>
> > 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