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

Subject: Re: multi-channel analog i/p
From: Stefen Paul <[email protected]>
To: "Hartman, Steven M." <[email protected]>
Cc: EPICS Tech Talk <[email protected]>
Date: Wed, 24 Jun 2015 13:02:15 +0530
Hi,

Is there a comprehensive document/website available telling about including 'driver support' in EPICS  ?

How can one call vxWorks device driver routines from EPICS records and make the data read by driver routine available to the EPICS records ?

Like in my case where I have a vxWorks driver for VME based 32-channel analog i/p board. I need to read the h/w through the driver only because of some FIFO design issues. But once the data is read by the driver, I would like to pass each channel's raw data to an individual ai record.

Thanks,
Stefen.

On Tue, Jun 23, 2015 at 6:19 PM, Hartman, Steven M. <[email protected]> wrote:

> On Jun 23, 2015, at 1:36 AM, Stephen Paul <[email protected]> wrote:
>
> Instead , I first want a record and its device support to read all the channels from the board in one go and then pass these values to individual 32 ai records for conversion.
>
> Can anyone suggest what type of record I can use before ai record to achieve this ?

Rather then a record for reading all of the hardware values, your device driver can have a worker thread responsible for reading from the hardware. This can be scheduled either periodically or based on some trigger. Your ai records would then read from the cached values from this worker thread rather then directly from the hardware. There are a number of drivers which take this approach, typically with more complicated hardware with a large number of registers to be read, or having a variety of different data types to support.

--
Steven Hartman
[email protected]




Replies:
Re: multi-channel analog i/p Peter Milne
RE: multi-channel analog i/p Mark Rivers
Re: multi-channel analog i/p Kasemir, Kay
References:
multi-channel analog i/p Stephen Paul
Re: multi-channel analog i/p Hartman, Steven M.

Navigate by Date:
Prev: Direction option for caByte in caQtDM Mezger Anton Christian (PSI)
Next: Re: multi-channel analog i/p Peter Milne
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: multi-channel analog i/p Hartman, Steven M.
Next: Re: multi-channel analog i/p Peter Milne
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·