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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: looking for OSI version of epid record |
From: | Tim Mooney <[email protected]> |
To: | "LYNCH, Damien" <[email protected]> |
Cc: | [email protected] |
Date: | Fri, 18 Aug 2006 09:39:57 -0500 |
I am interested in the response to the following question as well (as I have just started using EPID this week myself).
Another question with regard to replacing pid by epid: Apart from teh above scaling issue, have I understood it correct that if the following scenario:
a pid record controlling an ao record, the latter in OMSL=closed_loop, output OIF=incremental mode, DOL referencing pid's DM
would be replaced by
epid record having OUTL point to ao record's VAL, ao record in OIF=full and OMSL=supervisory mode?
Yes. This allows the epid record to control any record, to have its output value transformed by a calc expression, etc.
I see the EPID record producing a value that should be added to the ao record's VAL field, implying the ao record should have OIF=Incremntal. But with the EPID record putting OVAL into what's pointed to by OUTL (ie the ao record) I'd expect to have OMSL=supervisory in the ao record.
The way I read the doco I thought EPID would calculate a value that would be put into the ao record (not added to what's already there).
-- Tim Mooney ([email protected]) (630)252-5417 Beamline Controls & Data Acquisition Group Advanced Photon Source, Argonne National Lab.