| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: longout record reading? |
| From: | "Mark Rivers" <[email protected]> |
| To: | "Heinrich du Toit" <[email protected]>, "TechTalk EPICS" <[email protected]> |
| Date: | Fri, 5 Oct 2007 08:12:07 -0500 |
If an output value can change due to reasons other than the output record itself then I think you need to use an input record to provide a readback of the actual value. Mark ________________________________ From: [email protected] on behalf of Heinrich du Toit Sent: Fri 10/5/2007 7:06 AM To: TechTalk EPICS Subject: longout record reading? Hallo Ok I'm writing an asyn driver. There is a certain option that is connected to a PV via a asynInt32 interface. Both reading and writing of the option is allowed. Now I can have a longout record to write to this option which is fine. The problem is that sometimes the option changes because of something else. How can I force the longout record to read again? Or is the only solution to have another longin record that will read the value and then respond to I/O Intr from the driver? Or can I somehow just use longout? -Heinrich