EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Record Alarm/ AsynPortDriver
From: reem ateia <[email protected]>
To: Mark Rivers <[email protected]>
Cc: [email protected]
Date: Wed, 29 Jun 2011 09:00:33 +0200
Thank you for your answer

Rime

On Tue, Jun 28, 2011 at 12:37 PM, Mark Rivers <[email protected]> wrote:
What is the SCAN state of the underlying records?  It is periodic, passive, or I/O Intr.  If it is not I/O Intr then your driver should implement the readInt32 method (for example) and simply return a bad status from that function when the driver detects an error.  If you use the base class implementation of readInt32 then it is not possible to return an error status.

If the record is I/O Intr scanned it is not currently possible to put the record into alarm directly from the driver, but we are working on a fix for that limitation.

Mark


________________________________

From: [email protected] on behalf of Rime Ateia
Sent: Tue 6/28/2011 1:58 AM
To: [email protected]
Subject: Record Alarm/ AsynPortDriver




Hello,



We are using the AsynPortDriver to implement a device support.

In some cases our requests at the lowest level to read values are either rejected or get a bad status. We would like to set these PVs to an invalid state.

Is there a way to modify the alarm status of a specific PV (ai) from this layer? Or how can we get the pointer to a specific PV in our code that uses the AsynPortDriver?




Thanks in advance

Rime




References:
Record Alarm/ AsynPortDriver Rime Ateia
RE: Record Alarm/ AsynPortDriver Mark Rivers

Navigate by Date:
Prev: Bug on alh (alarm handler) 1.2.26 alConfig.c file Juan.Guzman
Next: Re: Bug on alh (alarm handler) 1.2.26 alConfig.c file Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Record Alarm/ AsynPortDriver Mark Rivers
Next: Announcement : SiTCP for Accelerator Control Takashi OBINA
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·