synApps: ip330

Module Owner: Mark Rivers: University of Chicago

This page is the home of ip330. 

ip330 supports Industry Pack analog to digital converters.

Devices supported in ip330 include:

From Acromag

The ip330 provides driver support for other synApps modules that I've written, use as a waveform digitizer using the MCA record (included in mca), and for fast feedback using the EPID record (included in std)

Please email any comments and bug reports to Mark Rivers who is responsible for coordinating development and releases.

Where to find it

The software is in the epics-modules/ip330 repository on Github It can be downloaded from the links below.

Module Version Release Date Filename Documentation Release Notes Known Problems
2-9 16-September-2017 R2-9 ip330Doc Release notes See release notes
2-8 5-December-2014 R2-8 ip330Doc Release notes See release notes
2-7 9-September-2011 R2-7 ip330Doc Release notes See release notes
2-6 20-Mar-2010 R2-6 ip330Doc Release notes See release notes
2-5 18-Oct-2007 R2-5. ip330Doc Release notes See release notes
2-3 23-Mar-2005 R2-3 ip330Doc Release notes See release notes
2-2 4-Mar-2004 R2-2 ip330Doc Release notes See release notes
2-1 3-Nov-2003 R2-1 ip330Doc Release notes See release notes
1-7 25-Apr-2003 R1-7 ip330Doc Release notes see release notes
1-6 31-Mar-2003 R1-6 ip330Doc Release notes see release notes
1-5 31-Jul-2002 R1-5 ip330Doc Release notes see release notes

Required Modules

Module Version Requires module Release needed Required for
2-9 EPICS base 3.15.5 Base support
asyn 4-32 Driver support
ipac 2-14 Industry pack support
2-8 EPICS base 3.14.12.4 Base support
asyn 4-24 Driver support
ipac 2-12 Industry pack support
2-7 EPICS base 3.14.12.1 Base support
asyn 4-17 Driver support
ipac 2-11 Industry pack support
2-6 EPICS base 3.14.11 Base support
asyn 4-13 Driver support
ipac 2-10 Industry pack support
2-5 EPICS base 3.14.8.2 Base support
asyn 4-9 Driver support
ipac 2-8 Industry pack support
2-3 EPICS base 3.14.7 Base support
asyn 4-2 Driver support
ipac 2-8 Industry pack support
2-2 EPICS base 3.14.5 Base support
mpf 2-4-2 Message passing
ipac 2-7a Industry pack support
mca 6-2 MCA record support (optional)
dac128V 2-2 EPID record support (optional)
std 2-3 EPID record support (optional)
2-1 EPICS base 3.14.4 Base support
mpf 2-4 Message passing
ipac 2-5 Industry pack support
mca 6-1 MCA record support (optional)
dac128V 2-1 EPID record support (optional)
std 2-2 EPID record support (optional)
1-7 EPICS base 3.13.7 Base support
mpf 1-10 Message passing and Industry Pack support
mca 5-4 MCA record support (optional)
dac128V 1-4 EPID record support (optional)
std 1-3 EPID record support (optional)
1-6 EPICS base 3.13.3 Base support
mpf 1-8 Message passing and Industry Pack support
mca 5-3 MCA record support (optional)
dac128V 1-3 EPID record support (optional)
std 1-2? EPID record support (optional)
1-5 EPICS base 3.13.3 Base support
mpf 1-? Message passing and Industry Pack support
mca 5-? MCA record support (optional)
dac128V 1-? EPID record support (optional)
std 1-? EPID record support (optional)

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. Create an installation directory for the module, usually this will end with

    .../support/
  2. Place the distribution file in this directory. Then issue the commands (Unix style) 
    gunzip ip330RX-Y.tar.gz
tar xvf ip330RX-Y.tar
    where X-Y is the release.
  3. This creates a <top> application.
    .../support/ip330RX-Y
  4. Edit the config[ure]/RELEASE file and set the paths to your installation of EPICS base and to your versions of other required modules.
  5. Run gnumake in the top level directory and check for any compilation errors.
  6. Please email  Mark Rivers  so that a record can be kept of which sites are using this software.

In Use

This software was originally developed by Mark Rivers and Tim Mooney.