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: Process aSub record on arrival of data |
From: | Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> |
To: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
Date: | Thu, 27 Jul 2023 22:51:12 +0200 |
Hi Matt,
On 7/27/23 1:33 PM, Matt Rippa via Tech-talk wrote:
The standard and most efficient way would be to have RX.INPA be a CA link to the TX.VALA field with the CPP link flag set, then every time TX updates its VALA field the CA monitor event will update the RX.A array and process that record immediately. If you want to make that processing conditional there are a couple of different ways to do that, but that's a different question for a different email.I have 2 aSub records: Tx on IOC A and Rx on IOC B.IOC A and B are on different machines on my network.
I want Tx to send an array to Rx over CA (or PVA). Once the data arrives is there a stock method to trigger Rx to process? IIUC, using the CPP attribute in Tx.OUTA will not cause the Rx to process since these records are on different IOC's. I'm using another OUT link in Tx to write to Rx.PROC.
Is that the most efficient way to do this?