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  <20092010  2011  2012  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  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Alarm if no status update received for a given time
From: Ralph Lange <[email protected]>
To: "Dalesio, Leo" <[email protected]>
Cc: [email protected]
Date: Wed, 06 May 2009 18:10:09 +0200
Another option - as it is in your own device support and epicsTimers are not too expensive:

Create an epicsTimerQueue for the device support and an epicsTimer for every record instance. Whenever the record processes, it cancels the active timer and sets up a new one after <timeout> seconds (<timeout> probably taken from the INP link info @....). The handler function (that gets called with a record* when the timer expires) sets the record state to INVALID/TIMEOUT (or READ ERROR, as Bob prefers).

Good luck!
Ralph


On 06.05.2009 17:16 Dalesio, Leo wrote:
The standard way to handle hardware errors is to have the device support set the alarm severity to INVALID and the alarm state to READ ERROR. The device support defines what conditions are needed to do this - how many reads before it fails. If you want to configure this, you can extend the device support to decide pseudo channels to the driver by using the INF extension. Create ao device support for setting these parameters. The device support for CAN and extend the OUT field with an @TIMEOUT. Make the record passive - and whenever you write to the VAL - this replaces the timeout counter. You can do this per link or per device - whatever you decide.



-----Original Message-----
From: [email protected] on behalf of Martin Konrad
Sent: Wed 5/6/2009 5:57 AM
To: [email protected]
Subject: Alarm if no status update received for a given time
Hi all, I'm using some devices via a simple CAN device support for SocketCAN without support for acknowledged writes etc. The IOC instead periodically asks the devices for an update and they reply with a CAN packet containing the device status.

Now my question is very simple: What is the EPICS way of implementing a timeout which raises an alarm if a device did not answer for a given time? Is it possible to configure this alarm condition in the database?

Thanks a lot in advance.

Martin



References:
Alarm if no status update received for a given time Martin Konrad
RE: Alarm if no status update received for a given time Dalesio, Leo

Navigate by Date:
Prev: RE: Alarm if no status update received for a given time Dalesio, Leo
Next: Motor Control - anyone have drivers and opinions for: SpiiPlus, Delta Tau, Parker ACR9000 Dalesio, Leo
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Alarm if no status update received for a given time Dalesio, Leo
Next: Failed to create single DLLs on Windows Wang Xiaoqiang
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·