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: EPICS communication paradigm |
From: | renato sanhueza <[email protected]> |
To: | Mark Rivers <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Sat, 11 Nov 2017 19:28:10 -0300 |
Hi Renato,
What you said is basically correct. An EPICS control system typically consists of multiple channel access servers located on multiple computers. There are also multiple channel access clients located on multiple computers. The clients normally locate EPICS process variables (PVs) on the servers using a UDP broadcast with the PV name, and then connect to them with TCP. They can then subscribe to callbacks from the servers whenever the PV changes (publish/subscribe model), and can write new values to the PVs.
I'm not sure if this answers your question?
Mark
________________________________
From: [email protected] <[email protected]> on behalf of renato sanhueza <[email protected]. cl >
Sent: Saturday, November 11, 2017 1:05 PM
To: [email protected]
Subject: EPICS communication paradigm
Hi, I am learning about EPICS and I think I understand the basic concepts about it but I am still unable to determine in which communication paradigm is EPICS based on.
My best guess is that EPICS implements the Distributed Object Paradigm because Records are object distributed across different Channel Access Servers. Other technologies which implement this paradigm are CORBA and JavaRMI for example.
I would really appreciate if someone can point me in the right direction.
Thanks in advance
--
Renato Sanhueza Ulsen
Ing Civil Informática.