Hi
I've made a test connecting BOY to the pvAccess protocol, it's fairly straightforward. BOY uses the org.csstudio.utility.pv.IPVFactory and org.csstudio.utility.pv.PV interfaces, there are plugins for simulated values already in CSS. Some minimal example code is here:
http://epics-pvdata.hg.sourceforge.net/hgweb/epics-pvdata/pvAccessCSSTests
You make a PVFactory which registers a prefix like ipc:// and returns a PV when called with createPV(name). The PV object has an IValue getValue() method, return an IDoubleValue wrapping a double and some metadata.
James
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Elliott Wolin
Sent: 30 September 2011 15:51
To: [email protected]; Kay-Uwe Kasemir
Cc: Hovanes Egiyan; David Lawrence; Vardan Gurjyan; carl Timmer
Subject: BOY widgets and protocols other than Channel Access
Hi,
I'm wondering how flexible BOY and its widgets are concerning
interprocess communication (IPC) protocols other than Channel Access.
We likely will use BOY for all our EPICS interfaces, and are considering
using it for our experiment control interfaces as well (i.e. for our
"ECS", following LHC nomenclature). Our experiment control and DAQ
systems use IPC protocols other than CA, including some home-grown ones
(e.g. the cMsg publish/subscribe package).
Can BOY accept IPC plugins? Is CA implemented as a plugin or something
analogous? Does BOY use a generic interface to connect to IPC packages
that we can implement ourselves using our other IPC packages? Or is CA
hard-wired in and difficult to disentangle from the core BOY code?
Any information and especially suggestions on how to proceed will be
appreciated.
Thanks,
--
Sincerely,
Elliott
================================================================================
Those raised in a morally relative or neutral environment will hold
no truths to be self-evident.
Elliott Wolin
Staff Physicist, Jefferson Lab
12000 Jefferson Ave
Suite 8 MS 12A1
Newport News, VA 23606
757-269-7365
================================================================================
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- Replies:
- Re: BOY widgets and protocols other than Channel Access Kasemir, Kay
- References:
- BOY widgets and protocols other than Channel Access Elliott Wolin
- Navigate by Date:
- Prev:
BOY widgets and protocols other than Channel Access Elliott Wolin
- Next:
Re: BOY widgets and protocols other than Channel Access Kasemir, Kay
- 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:
BOY widgets and protocols other than Channel Access Elliott Wolin
- Next:
Re: BOY widgets and protocols other than Channel Access Kasemir, Kay
- 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
|