| 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: generalTime/epicsTimeGetCurrent and casr questions |
| From: | "Kasemir, Kay via Tech-talk" <[email protected]> |
| To: | "Brands Helge (PSI)" <[email protected]>, Mark Rivers <[email protected]>, techtalk <[email protected]> |
| Date: | Wed, 13 Mar 2019 13:06:22 +0000 |
|
> Can anyone answer how edm, CSS, and PyDM handle this? edm and CS-Studio connect once and then keep that connection.
This is useful for two reasons.
One is the performance gain respectively reduced load on network and IOCs as you already mentioned.
The other is that we're in a distributed environment.
Your display that has a text entry field or a slider might not be the only tools that's writing to those PVs.
In fact the IOC might just change the PV on its own.
Or you write "105", but the IOC clamps the value at "100".
This means that you always need to monitor a PV that you write.
You move the slider or enter a new value into a text entry field
-> Your tool writes to the PV.
Meanwhile, the PV can be changed by somebody else
-> Your tool needs to show that value in the text entry field, or move the slider to the received value.
Thanks,
Kay
|