Experimental Physics and Industrial Control System

Hey hey!

I have a device on my Linux IOC, using Asyn GPIB.  The device works on the
IOC and, connected with EDM - is controllable.

When the device is turned off I get an error message:  asynError in write:
GPIB0 writeGpib failed ENOL 2: No listeners

The function in the proto file uses exception @replytimeout, but that
never executes,  which I would expect (I queried a device, it's not there,
I should have a timeout). This works on TCP/IP devices, just not GPIB.

Does anyone have any thoughts, or hacks, or updates on getting GPIB
exceptions to run the proto file exception commands?

Also when I try using the @writetimeout exception to more closely mimic
the error message, the IOC crashes on boot, not even an IOC command
prompt, which looks like a separate problem, any help on that would also
be appreciated.  Error message is:

A call to 'assert(dbLockIsInitialized)'
    by thread 'cbLow' failed in ../dbLock.c line 239.
EPICS Release EPICS R3.14.11 $R3-14-11$ $2009/08/28 18:47:36$.
Local time is 2017-10-06 08:13:40.495885987 PDT
Please E-mail this message to the author or to [email protected]
Calling epicsThreadSuspendSelf()
Thread cbLow (0x9a12518) suspended


Cheers
James Larsson

Replies:

Re: Asyn GPIB proto file exception @writetimeout Zimoch Dirk (PSI)

Navigate by Date:

Prev: Re: aD driver for Mako G G-032? Heinz Junkes

Next: Writing PVs from an amalgamated structure Iain Marcuson

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: EPICS 7 service use bob dalesio

Next: Re: Asyn GPIB proto file exception @writetimeout Zimoch Dirk (PSI)

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