EPICS: Mizar 8310 Timimg module
-
Module Owner: Marty Kraimer
NOTICE: I really don't want responsibility for this module
This page is the home of the mizar VME timing module. This consists of
the following components :
pulseCounterRecord.c
pulseCounterRecord.dbd
pulseDelayRecord.c
pulseDelayRecord.dbd
pulseTrainRecord.c
pulseTrainRecord.dbd
timerRecord.c
timerRecord.dbd
devMz8310.c
devTimerMz8310.c
drvMz8310.c
drvMz8310.h
drvStc.c
drvStc.h
mz8310.dbd
/pre>
These components previously resided in epics/base. The first unbundled
release is arbitrarily being called R1-1.
Please email any comments and bug reports to _Marty
Kraimer_ who is responsible for coordinating development and releases.
Discussion
Since the Mizar 8310 is an old device it should not be used for new applications.
This support is meant for existing applications.
The original support was developed for GTACS, the precurser to EPICS.
This support consisted of timerRecord, drvStc and devTimerMz8310. Later
the pulse support, which uses many more features of the mz8310 , was added.
The Mizar has two AMD STC timer chips. It is these chips that
provide most of the functionality. It is also a rather complicated chip.
Many of the fields in the pulse and timer records are used to program the
AMD chips. For this reason none of these record are general purpose and
should only be used for the Mizar module. The pulse records do have many
nice features but if they are needed for other devices they should be reimplemented
to be more general purpose.
Hardware Supported
The Mizar 8310.
Documentation
The pulseCounterRecord, pulseDelayRecord, pulseTrainRecord, and
timerRecord are documented in the Record Referance Manual located a
t Los Alamos. Go to the following site and look for the Reference Manual.
The mizar documentaion was taken from the old APS EPICS documentaion page. It now appears here.
mizar (PS)
Where to Find it
You can download the software by anonymous ftp from the links in
the table below:
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).
-
Create an installation directory for the module, usually this will end
with
/support/mizar
-
Unpacking the distribution tar file produces a directory
named after the release number.
-
Edit the configure/RELEASE file and set the paths to your installation
of
EPICS base and to your version of ipac.
-
Run make in the top level directory and check for any compilation
errors.
Marty Kraimer