Using _NAME_ instrument support in an application

Several files need minor modifications to use _NAME_ instrument support in an application.

  1. Add the full path to the _NAME_ support directory to the application configure/RELEASE file:
    _NAME_=xxxx/modules/instrument/_LOWERNAME_/<release>
    Where <release> is the release number of of the _NAME_ support.
  2. Add stream and asyn support to application database definition file
    The application database definition file must include the database definition files for the stream package and for any needed ASYN drivers. There are two ways that this can be done:
  3. Add the stream and asyn support libraries to the application
    You must link the stream support library and the ASYN support library with the application. Add the following lines:
    xxx_LIBS += stream
    xxx_LIBS += asyn
    before the
    xxx_LIBS += $(EPICS_BASE_IOC_LIBS)
    in the application Makefile.
  4. Load the _NAME_ support database records in the application startup script:
    cd $(_NAME_)      (cd _NAME_ if using the vxWorks shell)
    dbLoadRecords("db/dev_NAME_.db,"P=<P>,R=<R>,PORT=<PORT>,A=<A>")
    You'll have to provide appropriate values for the PV name prefixes (<P> and <R>), the port name (<PORT>) and the device address (<A>). The port name must match the value specified in an ASYN drvxxxxxConfigure command.

Installation and Building

After obtaining a copy of the distribution, it must be installed and built for use at your site.
  1. Create an installation directory for the module. The path name of this directory should end with modules/instrument/_LOWERNAME_.
  2. Place the distribution file into this directory.
  3. Execute the following commands:
    cd modules/instrument/_LOWERNAME_
    gunzip _LOWERNAME_<release>.tar.gz
    tar xvf _LOWERNAME_<release>.tar
    cd <release>
    Where <release> is the release number of of the _NAME_ support.
  4. Edit the configure/RELEASE file and set the paths to your installation of EPICS base, stream and ASYN support modules.
  5. Execute make in the top level directory.