modbus

Module Owner: Mark Rivers: University of Chicago

This page is the home of modbus. 

modbus supports EPICS communication with Programmable Logic Controllers (PLCs) via the Modbus protocol over TCP, serial RTU, and serial ASCII links.

The modbus software provides a layer between standard EPICS asyn device support, and the EPICS asyn TCP/IP or serial port driver.

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

Where to find it

The software can be downloaded from the links in the table below. The software can also be accessed through the github repository.

Module Version Release Date Filename Documentation Release Notes Known Problems
2-10-1 15-September-2017 R2-10-1 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-11 28-June-2018 R2-11 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-10 15-September-2017 R2-10 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-9 23-August-2016 R2-9 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-8 8-February-2016 R2-8 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-7 19-August-2014 R2-7 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-6 10-April-2014 R2-6 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-5 2-October-2013 R2-5 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-4 22-May-2012 R2-4 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-3 9-September-2011 R2-3 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-2 13-March-2011 R2-2 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-1 7-November-2010 R2-1 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
2-0 27-November-2009 R2-0 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
1-3 19-Septermber-2008 R1-3 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
1-2 6-September-2007 R1-2 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes
1-1 30-April-2007 R1-1 tar and zip files modbusDoc.html modbusReleaseNotes.html See release notes

Required Modules

Module version Requires module Release needed Required for
2-11 EPICS base 7.0.1 Base support
asyn 4-33 Driver support
2-10, 2-10-1 EPICS base 3.15.5 Base support
asyn 4-32 Driver support
2-9 EPICS base 3.14.12.5 Base support
asyn 4-30 Driver support
2-8 EPICS base 3.14.12.5 Base support
asyn 4-28 Driver support
2-7 EPICS base 3.14.12.4 Base support
asyn 4-23 Driver support
2-6 EPICS base 3.14.12.3 Base support
asyn 4-22 Driver support
2-5 EPICS base 3.14.12.3 Base support
asyn 4-21 Driver support
2-4 EPICS base 3.14.12.2 Base support
asyn 4-19 Driver support
2-3 EPICS base 3.14.12.1 Base support
asyn 4-17 Driver support
2-2 EPICS base 3.14.12 Base support
asyn 4-15 Driver support
2-1 EPICS base 3.14.11 Base support
asyn 4-14 Driver support
2-0 EPICS base 3.14.10 Base support
asyn 4-12 Driver support
1-3 EPICS base 3.14.8.2 Base support
asyn 4-10 Driver support
1-2 EPICS base 3.14.8.2 Base support
asyn 4-8 Driver support
1-1 EPICS base 3.14.8.2 Base support
asyn 4-8 Driver support

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) 
     tar xvzf modbusRX-Y.tgz
    where X-Y is the release.
  3. This creates a <top> application.
      .../support/modbusRX-Y
  4. Edit the configure/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, based on an earlier package by Rolf Keitel from Triumf.