Experimental Physics and Industrial Control System
I'm not a computer scientist by any means. But I think it is fair to say that Channel Access operates at a fairly low level of abstraction. It deliberately hides the "object" nature of EPICS records. It only provides access to specific fields in those records. So there is no capability of introspection of the record structure, etc.
There is a new EPICS protocol called pvAccess, commonly known as EPICS V4. It provides a much higher level of abstraction, and is designed with middleware services as one of its target applications. It allows the transmission of arbitrary structured data with full introspection.
Mark
________________________________
From: renato sanhueza <[email protected]>
Sent: Saturday, November 11, 2017 4:28 PM
To: Mark Rivers
Cc: [email protected]
Subject: Re: EPICS communication paradigm
Hi Mark,
Thanks for your answer. You give a good summary of the whole communication process. I was asking about the communication paradigm as an attempt to determine in which level of abstraction EPICS works.
For example the Message Passing Paradigm is associated with the lowest level of abstraction in distributed inter-process communications. Message Systems Paradigm (aka Message Oriented Middleware) works in a higher level of abstraction than Message Passing, but lower than Distributed Object Paradigm.
EPICS use the Channel Access Protocol to communicate clients and servers, but I couldn't intuitively map this protocol to any of the "common" communication paradigms I know (besides the Distributed Objects Paradigm).
On Sat, Nov 11, 2017 at 6:59 PM, Mark Rivers <[email protected]<mailto:[email protected]>> wrote:
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]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of renato sanhueza <[email protected]<mailto:[email protected]>>
Sent: Saturday, November 11, 2017 1:05 PM
To: [email protected]<mailto:[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.
--
Renato Sanhueza Ulsen
Ing Civil Informática.
- Replies:
- Re: EPICS communication paradigm renato sanhueza
- References:
- EPICS communication paradigm renato sanhueza
- Re: EPICS communication paradigm Mark Rivers
- Re: EPICS communication paradigm renato sanhueza
- Navigate by Date:
- Prev:
Re: EPICS communication paradigm renato sanhueza
- Next:
Re: EPICS communication paradigm renato sanhueza
- 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
- Navigate by Thread:
- Prev:
Re: EPICS communication paradigm renato sanhueza
- Next:
Re: EPICS communication paradigm renato sanhueza
- 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