EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: dynamic INP/OUT evaluation
From: Luedeke Andreas <[email protected]>
To: Andrew Johnson <[email protected]>
Cc: Luedeke Andreas <[email protected]>, tech-talk <[email protected]>
Date: Mon, 16 Aug 1999 09:56:17 +0200
Hi Andrew,
yes, that link support would be exactly what I would like to have.
It even would solve a few problems I had and didn't bother to ask.
I'm looking forward to this new release 8-) and meanwhile I will handle 
the dynamic INP/OUT evaluation by myself :-(

- Andreas

Andrew Johnson wrote:
> 
> Hi Andreas,
> 
> you hit one of my subject areas again...
> 
> Luedeke Andreas wrote:
> >
> > I'm writing a driver for a serial IP module (in-house) with
> > a VME_IO type of the INP and OUT field string:
> > #Cn Sm @parameter
> >
> > I want to allow dynamical changes of n, m and parameter.
> > Do I have to make a copy of n, m & parameter and compare it
> > to identify changes or is there a kind of flag that the field has changed?
> 
> With current versions of EPICS yes you have to keep track of the link
> fields yourself if you want to support dynamic changes.  Very few device
> support routines do this yet as the ability to change links at run-time
> was only introduced in EPICS R3.13
> 
> > I think it is possible to have a special processing in record support if
> > a field has changed. That would be the most elegant way to my opinion.
> > But my driver will support roughly a dozen types of records and I don't
> > want to rewrite them all.
> 
> I made a proposal at the last EPICS collaboration meeting to change the
> code that handles links to make them much more generic, and one of my
> changes will be to allow the device support to give a routine to be called
> when the link is changed.  This will be implemented (hopefully in the next
> major EPICS release), but I haven't had a chance to start looking at the
> code yet.  When this is released you'll have to make some minor changes to
> your code, but you'll also be able to define your own link formats.
> There's a document describing the proposal at
>         http://www.aps.anl.gov/asd/people/anj/lnkSup.html
> 
> - Andrew
> --
> I brake for tail-gaters

-- 
Andreas Luedeke, Controls Group, Swiss-Light-Source, PSI
mailto:[email protected], tel:+41-(0)56-310-4002, fax:-4413


References:
dynamic INP/OUT evaluation Luedeke Andreas
Re: dynamic INP/OUT evaluation Andrew Johnson

Navigate by Date:
Prev: Re: dynamic INP/OUT evaluation Andrew Johnson
Next: ADC boards Liam O Neill
Index: 1994  1995  1996  1997  1998  <19992000  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: Re: dynamic INP/OUT evaluation Andrew Johnson
Next: ADC boards Liam O Neill
Index: 1994  1995  1996  1997  1998  <19992000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·