Experimental Physics and
Industrial Control System

Ralph Lange <[email protected]> · Wed, 16 Dec 2015 10:41:36 +0100

Hi Carlos,

Thanks a lot for the pointers!

Some comments on your statements...

On 16/12/2015 09:32, Carlos Pascual wrote:

[...]
Finally, I must say that, as a complete alien to the EPICS world it took
me quite a lot of effort learning enough to set up such a minimal and
simple epics system (the "tutorial-style" docs I found were very lab-
specific and assumed a running system in place). This stresses the
convenience of a pre-packaged VM or docker image. I documented my own
"minimal-epics" installation in this short doc:

http://sf.net/p/tauruslib/wiki/howto-taurus-epics/

I know that the EPICS learning curve is not to be underestimated. And I

agree that VM/Docker is a good way to provide an easy start.

However, for the records:

EPICS Base contains fairly complete example applications in the form of

templates that you can instantiate and build.

The "Application Developer's Guide" (which is the central document for

EPICS) has a "Getting Started" chapter that walks you through the

examples on a few pages.

The examples are completely self-contained and free of lab-specifics.

They do require an installation of EPICS Base, which (on modern standard

systems) can be created by unpacking the distribution tar and running

"make".

One more remark  about

> $ taurusform epics://XXX:random epics://XXX:a epics://XXX:b

epics://XXX:sum

The EPICS V3 network protocol is called Channel Access. In URI-type

notation, applications should use "ca:" to denote the scheme.

The EPICS V4 (next generation) network protocol is called PV Access. Its

common URI scheme tag is "pva:".

Unless the "epics:" tag stands for something taurus-internal that is a

different scheme and not Channel Access, I would really prefer a

consistent naming.

Cheers,
~Ralph

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System