Hi Kay,
On Mon, 8 Jun 2026, Kasemir, Kay via Tech-talk wrote:
The hard part is of course that you can never get 2 people to agree on what such a ?PV?, the common denominator of all protocols, should look like.
Is there really much disagreement?
A "PV" usually consists of:
1. The data itself (with type descriptor - int/float/..., # of elements).
2. A timestamp.
3. A "status" of some kind (STAT+SEVR, quality, a bitmask of errors, ...).
Or are you talking about API? That is usually "read, write, monitor".
Even TANGO, with its messy DeviceAttribute (whose internals violate most
"good design practices") is compatible (and pairable) with EPICS.
With best regards,
Dmitry
- Replies:
- Re: CA Provider for PVXS André Favoto via Tech-talk
- References:
- CA Provider for PVXS Marks, Nicholas via Tech-talk
- Re: CA Provider for PVXS Kasemir, Kay via Tech-talk
- Navigate by Date:
- Prev:
RE: Strange problem linking a library on windows-x64 Freddie Akeroyd - STFC UKRI via Tech-talk
- Next:
Re: CA Provider for PVXS André Favoto via Tech-talk
- 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
<2026>
- Navigate by Thread:
- Prev:
Re: CA Provider for PVXS Kasemir, Kay via Tech-talk
- Next:
Re: CA Provider for PVXS André Favoto via Tech-talk
- 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
<2026>
|