If you already have a server running and all you need to do is connect to it,
here is how you can create an EPICS client under Linux. It's relatively quick
Pick a root directory for ALL of EPICS (source and everything). It will
be referenced here as $EPICS (some people call this "<TOP>")
[I choose to place EPICS under /opt/epics to conform to the
Linux Filesystem Hierarchy standard]
At the very least, you need
(where, for example, a.b.c = 3.14.2) and, if you are going to use any
extensions, you need
Make sure you get the Config[ure] file for your
version of EPICS. If you look at the directory structure
("extensions/config" vs. "extensions/configure"), you can run both 3.13
and 3.14 simultaneously. N.B. Some extensions still
require the "config" directories. In this case, you will need to
install BOTH extensions/configure and extensions/config.
You should get
EzcaScan from the same directory for a simple channel access
(ezca may be slower than straight Channel Access---but EzcaScan
(which provides the client programs "caget" and "caput") depends on
The source for any extensions should go under
Do a tar tvf <extension>.tar to determine where to untar it.
Now compile EPICS base. (These abbreviated
instructions are for 3.14.8)
Set the environment variable EPICS_HOST_ARCH to "linux-x86"
make (then grab a cup of coffee)
If compilation is successful, you will have a bin, dbd, include, lib,
javalib, man, startup, and templates directories.
Binaries are found in $EPICS/base/bin/linux-x86
Compile the extensions
Correct EPICS_BASE in $EPICS/extensions/config[ure]/RELEASE,
then type "make" in that directory
(you may also need to set COMPAT_TOOLS_313=YES in
Binaries are found in $EPICS/extensions/bin/linux-x86
Congratulations! You should have a working EPICS client (be sure you compile
up "caput" and "caget"---you'll want those for command-line access to PVs).
How will you know? Well... you'll know when you get the server running...
(The Bird's Eye View) <-BACK |
NEXT-> (Configuring a VME/vxWorks EPICS Server)