EPICS: VME Summary Interlock and Alarm Module

This page is the home of the EPICS device support for VME Summary Interlock and Alarm Module (SIAM). This site gives access to the software source code, information on other modules which are needed to install and run it, and documentation on how to include and use it in your EPICS applications. Please email any comments and bug reports to Stephanie Allison who is responsible for coordinating development and releases.

Hardware Supported

The software can drive the following types of hardware: For hardware assistance, please contact BiRa Systems (current contact name is Phil Biswell).

Where to Find it

You can download the software by anonymous ftp  from the links in the table below:
 
 
Module Version EPICS Release Filename Documentation Release Notes Known Bugs
R0
R3.13.2
 siam.tar.gz
See Below
None
None

Installation and Building

After obtaining a copy of the distribution, it must be installed and built for use at your site. These steps only need to be performed once for the site (unless versions of the module running under different releases of EPICS and/or the other required modules are needed).
  1. Start with an existing EPICS application area and cd to the src directory.
  2. Unpacking the distribution tar file produces a <siam> directory.
  3. The siam code in this release still has module_types.h dependencies. We plan to remove this dependency in a future release. Your EPICS manager must modify your system's base/src/include/module_types.h to include the SIAM definitions, and then rebuild iocCore. It may be necessary to remove base/src/db/O.*/iocInit.o to force a rebuild of that module. You may prefer to just rebuild all of base. The file siam/include/module_types.h.portion contains the section of module_types.h which must be changed (binary inputs). This may involve integrating the SIAM changes into any local changes to module_types.h. See siam/include/module_types.h for an example.
  4. Add siam to your src/Makefile and run gnumake. Check for any compilation errors.
  5. When using the siam in your application, you'll want to include devSIAM.dbd along with the normal base dbd files when building your application's database definition file (siam/src/SIAMInclude.dbd provides an example). You'll also want to include siamLib when building your application's library (ie, include it in your Makefile.Vx).
  6. See siam/html/SIAM_ioc_mods for vxWorks kernel modification to perform A24/D32 accesses.
  7. See siam/html/SIAM-HOW-TO for functional details and address switch information.
  8. Example databases and templates reside in siam/db.
  9. Example DM displays reside in siam/dl. Old gif images of some of these displays are SIAM 0, SIAM 1 (expert), SIAM 0 Diagnostics, SIAM 0 Diagnostics (expert), and SIAM 0 Diagnostics (noinhibit).
  10. Please email  Stephanie Allison  so she can keep track of which sites are using this software.

Documentation

The following documentation is available:

In Use

This software was originally developed by Susanna Jacobson (LBL). It is used at the following EPICS sites:
Stephanie Allison