BASEstar[TM] Classic DAS
for Modicon®
Programmable_Controllers____________________________
Installation and User's Guide
Order Number: AA-R216A-TE
November 1996
This manual describes how to install and use the DAS
for Modicon Programmable Controllers for BASEstar
Classic on OpenVMS.
Revision/Update Information: This is a revised
document.
Operating System and Version: OpenVMS/Alpha Version
6.1
Operating System and Version: OpenVMS/VAX Version
5.5-2
Interface Software and Version:ASEstar Classic
Version 3.4
Software Version: BASEstar Classic
DAS for Modicon
Programmable
Controllers, Version
3.4
Digital Equipment Corporation
Maynard, Massachusetts
________________________________________________________________
November 1996
Possession, use, or copying of the software described in
this publication is authorized only pursuant to a valid
written license from Digital or an authorized sublicensor.
Digital Equipment Corporation makes no representations
that the use of its products in the manner described in
this publication will not infringe on existing or future
patent rights, nor do the descriptions contained in this
publication imply the granting of licenses to make, use,
or sell equipment or software in accordance with the
description.
© Digital Equipment Corporation 1992, 1996. All Rights
Reserved.
The following are trademarks of Digital Equipment
Corporation:
Alpha, BASEstar, Digital, LAT, OpenVMS, TK, VAX, and the
Digital logo.
Modicon and Modbus are registered trademarks of AEG
Schneider Automation.
Micro 84, 184, 384, 484, 584, 884, 984, SQ85, and SA85 are
trademarks of AEG Schneider Automation.
All other trademarks and registered trademarks are the
property of their respective holders.
This document is available on CDROM.
This document was prepared using DEC DOCUMENT Version 3.0.
_________________________________________________________________
Contents
Preface................................................... v
1 Overview
1.1 Description................................... 1-1
1.2 Device Communications......................... 1-1
1.3 Supported Functions and Devices............... 1-2
2 Installing the DAS for Modicon Programmable Controllers
2.1 Installation Requirements..................... 2-1
2.1.1 Hardware.................................. 2-1
2.1.1.1 Additional Hardware Requirements........ 2-2
2.1.2 Software.................................. 2-2
2.1.3 Additional Software....................... 2-3
2.1.4 Disk Space................................ 2-3
2.2 Installing the DAS for Modicon Programmable
Controllers................................... 2-3
2.2.1 Files Created During Installation......... 2-6
2.2.2 Installation Messages..................... 2-7
2.3 Postinstallation Tasks........................ 2-8
2.3.1 Editing the Configuration File............ 2-9
2.3.1.1 Editing Type Records.................... 2-9
2.3.1.2 Editing Path Records.................... 2-11
2.3.1.3 Editing Device Records.................. 2-12
2.3.1.4 DAS for Modicon Programmable Controllers
Configuration File...................... 2-14
2.3.2 DAS SPT Block Usage....................... 2-17
2.3.3 Configuring Ports......................... 2-18
2.3.4 Addressing a Modbus Plus Node............. 2-19
2.3.5 Addressing a Modbus Plus Host Node........ 2-19
2.3.6 Setting Modbus Plus Parameters............ 2-20
2.3.7 Setting Up Plant-Floor Equipment.......... 2-21
iii
2.4 Tracing Device Communications................. 2-21
2.5 Failures During Product Use................... 2-22
3 Using the DAS for Modicon Programmable Controllers
3.1 Accessing the DAS for Modicon Programmable
Controllers Functions......................... 3-1
3.2 Structured Data............................... 3-2
3.3 Supported Functions........................... 3-2
3.3.1 Start and Stop............................ 3-3
3.3.2 Upload and Download....................... 3-3
3.3.3 Read and Write Data Functions............. 3-4
3.3.3.1 Modicon 184 and Modicon 384............. 3-6
3.3.3.2 Modicon 484............................. 3-7
3.3.3.3 Modicon 584 and Modicon 984............. 3-7
3.3.3.4 Modicon 884............................. 3-8
3.3.3.5 Micro 84................................ 3-9
3.3.4 Read Status............................... 3-10
3.4 Automatic Data Collection..................... 3-11
3.4.1 Polled Data Collection.................... 3-11
3.4.2 Unsolicited Data Collection............... 3-11
3.4.2.1 Unsolicited ID.......................... 3-12
A Equipment Configuration
Index
Examples
3-1 Read Data Screen.......................... 3-4
3-2 Read Data Screen with Structured Data..... 3-5
3-3 Write Data Screen......................... 3-5
3-4 Write Data Screen with Structured Data.... 3-5
3-5 Read Status Screen........................ 3-10
iv
Figures
1-1 DAS for Modicon Programmable Controllers
Communications............................ 1-2
A-1 Processor-to-Modem Connection............. A-1
A-2 Modbus Block Diagram...................... A-2
A-3 Modbus Plus Block Diagram................. A-3
Tables
1-1 Modicon Programmable Controllers.......... 1-3
2-1 Disk Space Requirements................... 2-3
2-2 BASEstar Classic Device Connection
Management Files.......................... 2-6
2-3 Files Used by Simple Compare.............. 2-7
2-4 CREATE TYPE............................... 2-10
2-5 CREATE MODBUS_PATH........................ 2-11
2-6 Line Parameters........................... 2-12
2-7 CREATE MPLUS_PATH......................... 2-12
2-8 CREATE DEVICE............................. 2-14
2-9 Modbus Plus Parameters.................... 2-20
3-1 Modicon Devices and Functions............. 3-2
v
_________________________________________________________________
Preface
This document describes how to install and use the BASEstar
Classic DAS for Modicon programmable controllers.
Intended Audience
This document is intended for system managers who must set
up and maintain the following:
o BASEstar Classic for OpenVMS software
o BASEstar Classic DAS for Modicon programmable
controllers
This document is also intended for application programmers
who develop plant-floor management software layered on
BASEstar Classic software.
Readers of this document should have a solid understanding
of OpenVMS operations and administration, as well as
OpenVMS application software. In addition, knowledge
of Modicon programmable controllers and the specific
requirements of the installation site is essential.
Document Structure
This document is organized as follows:
o Chapter 1 provides an overview of the DAS for Modicon
programmable controllers.
o Chapter 2 provides information you need to install the
DAS for Modicon programmable controllers.
o Chapter 3 provides information about the supported
functions for Modicon programmable controllers, and
how to access those functions.
v
Associated Documents
Further information on BASEstar Classic can be found in the
following documents:
o BASEstar Classic Installation Guide
o BASEstar Classic Configuration and Tuning Guide
o BASEstar Classic Menu Interface User's Guide
o BASEstar Classic Command Line Interface User's Guide
o BASEstar Classic Introduction to Callable Services
o BASEstar Classic Guide to Writing Device Access Software
o BASEstar Classic Application Programming Interface
Reference Guide
Further information on Modicon communications can be found
in the following documents:
o Modbus Protocol Reference Guide
o Modbus System Planning Guide
o J478 Stand-Alone Modem Guide
o Modicon DEC Host Based Devices User's Guide
Conventions
This document uses the following conventions:
Boldface Highlights user input within textual
descriptions.
<Return> Press the key labeled Return. Unless otherwise
specified, press <Return> after entering a
command or responding to a prompt.
Enter Type the words or symbols described and press
<Return>.
vi
1
_________________________________________________________________
Overview
This chapter provides an overview of the BASEstar Classic
DAS for Modicon programmable controllers. It also briefly
describes Modicon programmable controllers and the
supported functions for the DAS.
1.1 Description
The DAS for Modicon programmable controllers allows you to
access Modicon programmable controllers through BASEstar
Classic device connection management capabilities. Device
connection management is the device connection/control
component of BASEstar Classic for OpenVMS. BASEstar
Classic for OpenVMS is software designed to facilitate the
integration of manufacturing equipment and applications,
accelerate the development of integrated manufacturing
systems, and provide an architecture for consistent
development of manufacturing applications.
Using the DAS for Modicon programmable controllers,
users or applications can perform a variety of device
access functions which include: reading and writing data,
uploading and downloading, and reading the status of a
device.
1.2 Device Communications
The DAS for Modicon programmable controllers consists of a
protocol emulator (PE) and two network interfaces (NI). The
PE and the NI work together to provide device-specific
communications for BASEstar Classic device connection
management's generic callable services.
The PE translates BASEstar Classic device connection
management's generic services into a device-understandable
format. The PE also converts device-specific protocol into
a BASEstar Classic device connection management format.
Overview 1-1
Overview
1.2 Device Communications
The NI works directly with a OpenVMS driver to send data
to and receive data from plant-floor devices. The NI
communicates the requests and data translated by the PE.
Figure 1-1 shows how the DAS facilitates communications
between BASEstar Classic device connection management and
the devices.
Figure 1-1 DAS for Modicon Programmable Controllers
Communications
1.3 Supported Functions and Devices
You can perform only the BASEstar Classic device connection
management functions that are supported by a device's PE.
These functions can be accessed through BASEstar Classic
device connection management's menu system, commands, and
callable services.
The DAS for Modicon programmable controllers supports the
following BASEstar Classic device connection management
functions:
o Start and stop operations on a device
o Upload the contents of a device's memory to an OpenVMS
file
o Download an OpenVMS file to a device's memory
o Read data from a specific address in a device's memory
o Write data to a specific address in a device's memory
o Read status of a device
The DAS for Modicon programmable controllers supports
a variety of programmable controllers, as shown in
Table 1-1.
1-2 Overview
Overview
1.3 Supported Functions and Devices
Table_1-1_Modicon_Programmable_Controllers_______________________
Read Write Read
Device____Upload__DownloadStart___Stop____Data____Data____Status_
984A X X X X X X X
984B X X X X X X X
984X X X X X X X X
884 X X X X X X X
584L X X X X X X X
584M X X X X X X X
484 X X X X X X X
384 X X X X X X
184 X X X X X X
Micro_84__X_______X_______________X_______X_______X_______X______
For more information about the supported functions, refer
to Chapter 3 of this document.
Overview 1-3
2
_________________________________________________________________
Installing the DAS for Modicon Programmable Controllers
This chapter provides the information you need to
install the BASEstar Classic DAS for Modicon programmable
controllers and to configure your system.
2.1 Installation Requirements
Review the following hardware and software requirements
to ensure that your system is prepared for the DAS
installation.
________________________ Note ________________________
Back up the disks on your system before installing
this software. This will provide a method to restore
your system in the event of an installation problem.
The procedure for backing up disks is described in the
OpenVMS System Management Utilities Reference Manual.
______________________________________________________
2.1.1 Hardware
The DAS for Modicon programmable controllers requires
the same hardware as BASEstar Classic device connection
management software. For specific information on device
connect management hardware requirements, refer to the
BASEstar Classic Installation Guide. Additional hardware
needed for the DAS for Modicon programmable controllers
includes:
o J374 Modicon Modbus communication adapter for Modicon
384 programmable controllers, which works in tandem with
the J478 modem
o J474 Modicon Modbus communication adapter for Modicon
484 programmable controllers
o J478 modem
Installing the DAS for Modicon Programmable Controllers 2-1
Installing the DAS for Modicon Programmable Controllers
2.1 Installation Requirements
o J375 Modicon Modbus adapter for Micro 84 programmable
controllers, which works in tandem with the J378 modem
o J378 modem for Micro 84 programmable controllers, which
works in tandem with the J375 Modbus adapter
o Cables from the host port or LAT port (see the cable
wiring diagram in Appendix A)
2.1.1.1 Additional Hardware Requirements
If you intend to use the Modbus Plus communication protocol
you must also have:
o SQ85 Network Card (OpenVMS/VAX systems)
o SA85 Network Card (OpenVMS/Alpha systems)
o Modicon 984 series programmable controllers that end in
the number 5 (for example 984/385)
2.1.2 Software
Before installing the DAS for Modicon programmable
controllers, the following software must already be
installed:
o OpenVMS Version 5.5-2 or higher (VAX)
o OpenVMS Version 6.1 or higher (Alpha)
o BASEstar Classic for OpenVMS, Version 3.4
For information on installing the above software, refer to
the BASEstar Classic Installation Guide.
________________________ Note ________________________
Before using this product on a system, you must first
register a License Product Authorization Key (License
PAK) using the License Management Facility (LMF). For
more information about the License Management Utility,
refer to the License Management Utility Manual for
OpenVMS.
______________________________________________________
2-2 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.1 Installation Requirements
2.1.3 Additional Software
In addition to the above software, if Modbus-Plus is being
used the following software must also be installed:
o Modbus-Plus driver for OpenVMS/VAX (SQ85 Network Card)
o Modbus-Plus driver for OpenVMS/Alpha (SA85 Network Card)
2.1.4 Disk Space
Table 2-1 lists the disk space required to install the
DAS for Modicon programmable controllers. The space
requirements are approximations; actual sizes may vary
depending on your system environment and configuration.
Table_2-1_Disk_Space_Requirements__________________________
Approximate Space Requirements
Peak/Net_Usage____________(Blocks)_________________________
Peak usage (during 600 (VAX)
installation)
850 (Alpha)
Net usage (after 500 (VAX)
installation)
______________________________700_(Alpha)__________________
2.2 Installing the DAS for Modicon Programmable Controllers
When your system meets all hardware and software
requirements, you can install the BASEstar Classic DAS
for Modicon programmable controllers. The installation
takes from 1 to 5 minutes, depending on the system load and
configuration.
Install the DAS for Modicon programmable controllers by
using the following steps:
1. Log in to a privileged system manager's account.
2. Invoke VMSINSTAL:
$ @SYS$UPDATE:VMSINSTAL DCM_MODVV034 ddcu:
Installing the DAS for Modicon Programmable Controllers 2-3
Installing the DAS for Modicon Programmable Controllers
2.2 Installing the DAS for Modicon Programmable Controllers
The DCM_MODVV034 argument is the kit name. The 034
portion of the name is the version number. The ddcu
argument represents the name of the device on which the
installation media is mounted, where:
o dd is the device code
o c is the controller designation
o u is the unit number
VMSINSTAL prompts you for information during the
installation. Note that DECnet software does not need
to be running to perform the installation procedure.
The following is an example of the output from the
installation:
VAX/VMS Software Product Installation Procedure V5.5-2
It is 16-OCT-1996 at 11:28.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]?
The following products will be processed:
DCM_MODVV V3.4
Beginning installation of DCM_MODVV V3.4 at 11:34
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
Copyright (C) Digital Equipment Corporation 1992, 1996. All rights reserved.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government
is subject to restrictions as set forth in subparagraph (c)(1)(ii) of
DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III,
as applicable.
This software is proprietary to and embodies the confidential technology
of Digital Equipment Corporation. Possession, usr, or copying of this
software and media is authorized only pusuant to a valid written license
from Digital or an authorized sublicensor.
BASEstar Classic DAS for Modicon Programmable Controllers
installation procedure.
2-4 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.2 Installing the DAS for Modicon Programmable Controllers
Checking for a valid license...
Product: DAS-MOD-CL
Producer: DEC
Version: 3.4
Release Date: 13-DEC-1996
* Does this product have an authorization key registered and loaded? y
Now checking OpenVMS version...
Now checking that BASEstar Classic is installed...
* Do you want to purge files replaced by this installation [YES]?
* Do you want to run the IVP after the installation [YES]?
Please respond to the following questions concerning what configuration
you require on your system.
* Does your site have Modbus communications [YES]?
* Does your site have Modbus Plus communications [YES]?
* Does your site have Modicon 184/384 Programmable Controllers [YES]?
* Does your site have Modicon 484 Programmable Controllers [YES]?
* Does your site have Modicon 584 Programmable Controllers [YES]?
* Does your site have Modicon 884 Programmable Controllers [YES]?
%DCM_MODVV-I-MOD984, Including support for Modicon 984 programmable controllers
* Does your site have Modicon Micro 84 Programmable Controllers [YES]?
The configuration template file for Modicon support, DCM_MOD_CONFIG.TEMPLATE,
is used to define the Modicon paths, types, and devices. Edit this
file, as necessary, to reflect your specific site configuration.
During installation it will be placed in the directory BCC$SYSDATA.
The installation procedure has no further questions to ask and will
complete in 1 to 5 minutes depending on the system and system load.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
Copyright (C) Digital Equipment Corporation 1992, 1996. All rights reserved.
Executing the Installation Verification Procedure.
BASEstar Classic DAS for Modicon Programmable Controllors
installation procedure has succeeded.
Installation of DCM_MODVV V3.4 completed at 11:38
Installing the DAS for Modicon Programmable Controllers 2-5
Installing the DAS for Modicon Programmable Controllers
2.2 Installing the DAS for Modicon Programmable Controllers
VMSINSTAL procedure done at 11:38
2.2.1 Files Created During Installation
Table 2-2 lists the files that the DAS for Modicon
programmable controllers installation procedure creates
and the directories in which they are placed.
Table 2-2 BASEstar Classic Device Connection Management
__________Files____________________________________________
Directory_____________Filename_____________________________
BCC$SYSDATA: DCM_MOD_CONFIG.TEMPLATE
DCM_MOD$MSG.DAT
SYS$LIBRARY: ILAN_MOD384.EXE
ILAN_MOD484.EXE
ILAN_MOD584.EXE
ILAN_MOD884.EXE
ILAN_MOD984.EXE
ILAN_MODM84.EXE
ILAN_MODHOST.EXE
ILAN_MODBUS.EXE
ILAN_MPLUS.EXE
SYS$HELP: DCM_MODVV034.RELEASE_NOTES (VAX)
DCM_MODVA034.RELEASE_NOTES (Alpha)
SYS$TEST:_____________DCM_MOD$IVP.COM______________________
If the BASEstar Classic library system has been installed,
the files in Table 2-3 will also be created.
NOTE: The library system is not available on OpenVMS/Alpha
systems.
2-6 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.2 Installing the DAS for Modicon Programmable Controllers
Table_2-3_Files_Used_by_Simple_Compare_____________________
Directory_____________Filename_____________________________
SYS$LIBRARY: ILAN_MOD384_SCMP.EXE
ILAN_MOD484_SCMP.EXE
ILAN_MOD584_SCMP.EXE
ILAN_MOD984_SCMP.EXE
______________________ILAN_MODM84_SCMP.EXE_________________
2.2.2 Installation Messages
You may see VMSINSTAL messages during the installation
procedure. The following messages are specific to the DAS
for Modicon programmable controllers installation:
BADBCC, BASEstar Classic software must be installed before DAS
for Modicon Programmable Controllers.
Explanation: Error. Incorrect version of or missing BASEstar
Classic software.
User Action: Install BASEstar Classic for OpenVMS, Release
3.4 or higher software.
BADDCM, BASEstar Classic Device Connect must be installed
before the DAS for Modicon Programmable Controllers.
Explanation: Error. Incorrect version of or missing BASEstar
Classic DCM software.
User Action: Install BASEstar Classic DCM for OpenVMS,
Release 3.4 or higher software.
BADVMS (VAX), The DAS for Modicon Programmable Controllers must
be installed under OpenVMS V5.5-2 or greater.
Explanation: Error. Incorrect version of OpenVMS.
User Action: Install OpenVMS V5.5-2 or higher.
BADVMS (Alpha), The DAS for Modicon Programmable Controllers
must be installed under OpenVMS V6.1 or greater.
Explanation: Error. Incorrect version of OpenVMS.
User Action: Install OpenVMS V6.1 or higher.
Installing the DAS for Modicon Programmable Controllers 2-7
Installing the DAS for Modicon Programmable Controllers
2.2 Installing the DAS for Modicon Programmable Controllers
NETBLOCKS (VAX), The DAS for Modicon Programmable Controllers
requires 500 blocks after installation.
Explanation: Error. Not enough disk space to complete
installation.
User Action: Delete any unnecessary files, then reinstall.
NETBLOCKS (Alpha), The DAS for Modicon Programmable Controllers
requires 700 blocks after installation.
Explanation: Error. Not enough disk space to complete
installation.
User Action: Delete any unnecessary files, then reinstall.
NOLICENSE, No license found for this product - IVP will not be
run.,
Explanation: Informational. A valid license was not found.
The installation will continue, but the IVP will not be run.
User Action: Register and load a valid license for this
product before attempting to use the DAS.
NOLOAD, License for this product not loaded - IVP will not be
run.,
Explanation: Informational. The license for this product
has not been loaded by the License Management Utility. The
installation willl proceed, but the IVP will not be run.
User Action: Load the license using the License Management
Utility before attempting to use the DAS.
2.3 Postinstallation Tasks
This section describes the tasks to perform after
installing the DAS for Modicon programmable controllers,
including editing the configuration file, setting the
BASEstar Classic DCM support block parameter, configuring
ports, addressing a Modbus Plus node, setting Modbus Plus
parameters and setting up plant-floor equipment.
2-8 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
2.3.1 Editing the Configuration File
A configuration file template, BCC$SYSDATA:DCM_MOD_
CONFIG.TEMPLATE, is supplied with the DAS kit. The
configuration file contains definitions for types, paths,
and devices. A type record represents a protocol emulator
(PE). A path record represents a network interface (NI).
Copy the template file, edit the file to include site-
specific information about types and paths, and execute the
file.
The following sections give examples of the type, path,
device records. Refer to the BASEstar Classic Command Line
Interface User's Guide for more information about creating
type, path, and device definitions.
2.3.1.1 Editing Type Records
The following example shows the type records created by the
configuration file:
create type MOD_M84_TYPE/manufacturer="Modicon"/model=Micro-84 -
/protocol=MODM84/description="Modicon Micro 84"/LOG
create type MOD_384_TYPE/manufacturer="Modicon"/model=384 -
/protocol=MOD384/description="Modicon 384"/LOG
create type MOD_484_TYPE/manufacturer="Modicon"/model=484 -
/protocol=MOD484/description="Modicon 484"/LOG
create type MOD_584_TYPE/manufacturer="Modicon"/model=584 -
/protocol=MOD584/description="Modicon 584"/LOG
create type MOD_884_TYPE/manufacturer="Modicon"/model=884 -
/protocol=MOD884/description="Modicon 884"/LOG
create type MOD_984_TYPE/manufacturer="Modicon"/model=984 -
/protocol=MOD984/description="Modicon 984"/LOG
create type MOD_HOST_TYPE/manufacturer="Modicon"/model=984 -
/protocol=MODHOST/description="Modicon 984"/LOG
Table 2-4 lists the types and parameters of the CREATE
TYPE command, and indicates the parameters of the previous
example that you can change.
Installing the DAS for Modicon Programmable Controllers 2-9
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
Table_2-4_CREATE_TYPE______________________________________
Type____________Parameter___Modifiable?____________________
MOD_M84_TYPE Manufacturer No
Model No
Protocol No
Description Yes
MOD_384_TYPE Manufacturer No
Model No
Protocol No
Description Yes
MOD_484_TYPE Manufacturer No
Model No
Protocol No
Description Yes
MOD_584_TYPE Manufacturer No
Model No
Protocol No
Description Yes
MOD_884_TYPE Manufacturer No
Model No
Protocol No
Description Yes
MOD_984_TYPE Manufacturer No
Model No
Protocol No
Description Yes
MOD_HOST_TYPE Manufacturer No
Model No
Protocol No
(continued on next page)
2-10 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
Table_2-4_(Cont.)_CREATE_TYPE______________________________
Type____________Parameter___Modifiable?____________________
________________Description____Yes_________________________
2.3.1.2 Editing Path Records
The following example shows the path records created by the
configuration file:
create path MODBUS_PATH /vaxport=LTAXXX:/netname=MODBUS -
/multidrop/io_size=512/retries=2 -
/line=(mode=rtu,type_ahead,speed=9600,data=8,stop=1,parity=even,full,hangup)-
/LOG
create path MPLUS_PATH /vaxport=MPA1:/netname=MPLUS -
/multidrop/LOG
Table 2-5 and Table 2-7 list the path and parameters of
the CREATE PATH command, and indicate the parameters of
the previous example that you can change. Verify that the
VAXport and the line parameters match your plant-floor
configuration.
Table_2-5_CREATE_MODBUS_PATH_______________________________
Parameter___Modifiable?_Value(s)___________________________
VAXport Yes
Netname No MODBUS
Multidrop No MULTIDROP
I/O size Yes 256-512
Retries________Yes______1-5________________________________
Table 2-6 lists valid line parameter values.
Installing the DAS for Modicon Programmable Controllers 2-11
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
Table_2-6_Line_Parameters__________________________________
Parameter___Modifiable?_Value(s)___________________________
Stop Bits No 1
Data Bits Yes 7-8
Parity Yes Even, Odd, None
Speed Yes 110-19200
Duplex Yes
Echo No NoEcho
Host Synch Yes
TT Synch Yes
Typeahead No Typeahead
Hangup No Hangup
Modem Yes
Dialup Yes
Disconnect_____Yes_________________________________________
Devices using Modbus communications should use the MODBUS
path. Devices using Modbus-Plus communications should use
the MPLUS path.
Table_2-7_CREATE_MPLUS_PATH________________________________
Parameter___Modifiable?_Value(s)___________________________
VAXport Yes
Netname No MPLUS
Multidrop______No_______MULTIDROP__________________________
2.3.1.3 Editing Device Records
The following example shows the device records created by
the configuration file:
create device MOD_384 /type=MOD_384_TYPE -
/descrip="Modicon 384"/netaddress=YY -
/path=MODBUS_PATH/manuf="Modicon"/timeout=300/LOG
create device MOD_584 /type=MOD_584_TYPE -
/descrip="Modicon 584"/netaddress=YY -
/path=MODBUS_PATH/manuf="Modicon"/timeout=300/LOG
2-12 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
create device MOD_984 /type=MOD_984_TYPE -
/descrip="Modicon 984"/netaddress=YY -
/path=MODBUS_PATH/manuf="Modicon"/timeout=400/LOG
create device MPLUS_984 /type=MOD_984_TYPE -
/descrip="Modicon 984"/netaddress="YY-YY-YY-YY-YY" -
/path=MPLUS_PATH/manuf="Modicon"/timeout=400/LOG
create device MHOST_984 /type=MOD_HOST_TYPE -
/descrip="Modicon 984"/netaddress="YY" -
/path=MPLUS_PATH/manuf="Modicon"/timeout=400/LOG
Table 2-8 lists the devices and parameters of the CREATE
DEVICE command, and indicates the parameters of the
previous example that you can change.
Installing the DAS for Modicon Programmable Controllers 2-13
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
Table_2-8_CREATE_DEVICE____________________________________
Device______Parameter___Modifiable?________________________
MOD_384 Path No
Type No
Description Yes
Netaddr Yes
Manuf No
MOD_584 Path No
Type No
Description Yes
Netaddr Yes
Manuf No
MOD_984 Path No
Type No
Description Yes
Netaddr Yes
Manuf No
MPLUS_984 Path No
Type No
Description Yes
Netaddr Yes
Manuf No
MHOST_984 Path No
Type No
Description Yes
Netaddr Yes
____________Manuf__________No______________________________
2.3.1.4 DAS for Modicon Programmable Controllers Configuration
File
The following is an example of the DAS for Modicon
programmable controllers configuration file:
2-14 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
$!
$! DAS for Modicon Programmable Controllers configuration template
$!
$!********************************************************************!
$! !
$! This is a template for the Modicon site specific configuration !
$! command file. Rename and edit this command procedure template !
$! to reflect your site specific Modicon configuration. You must !
$! manually execute this command procedure to configure your !
$! devices. !
$! !
$! Add comments to the site specific changes here. !
$! !
$!********************************************************************!
$!
$ bstar/dcm
!*********************************************************************!
! !
! Create types for the models supported by the Modicon PE. In !
! general, the type definitions are DAS specific, and should !
! not be modified. !
! !
!*********************************************************************!
create type MOD_M84_TYPE/manufacturer="Modicon"/model=Micro-84 -
/protocol=MODM84/description="Modicon Micro 84"/LOG
create type MOD_384_TYPE/manufacturer="Modicon"/model=384 -
/protocol=MOD384/description="Modicon 384"/LOG
create type MOD_484_TYPE/manufacturer="Modicon"/model=484 -
/protocol=MOD484/description="Modicon 484"/LOG
create type MOD_584_TYPE/manufacturer="Modicon"/model=584 -
/protocol=MOD584/description="Modicon 584"/LOG
create type MOD_884_TYPE/manufacturer="Modicon"/model=884 -
/protocol=MOD884/description="Modicon 884"/LOG
create type MOD_984_TYPE/manufacturer="Modicon"/model=984 -
/protocol=MOD984/description="Modicon 984"/LOG
create type MOD_HOST_TYPE/manufacturer="Modicon"/model=984 -
/protocol=MODHOST/description="Modicon 984"/LOG
Installing the DAS for Modicon Programmable Controllers 2-15
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
!*********************************************************************!
! !
! Modify these path and device definitions for your specific !
! configuration. !
! !
!*********************************************************************!
!*********************************************************************!
! !
! Create a Modbus path. !
! !
!*********************************************************************!
!create path MODBUS_PATH /vaxport=LTAXXX:/netname=MODBUS -
! /multidrop/io_size=512/retries=2 -
! /line=(mode=rtu,type_ahead,speed=9600,data=8,stop=1,parity=even,full,hangup)-
! /LOG
!*********************************************************************!
! !
! Create a Modbus Plus path. !
! !
!*********************************************************************!
!create path MPLUS_PATH /vaxport=MPA1:/netname=MPLUS -
! /multidrop/LOG
!********************************************************************!
! !
! Create a Modicon 384 device !
! !
!********************************************************************!
!create device MOD_384 /type=MOD_384_TYPE -
! /descrip="Modicon 384"/netaddress=YY -
! /path=MODBUS_PATH/manuf="Modicon"/timeout=300/LOG
!********************************************************************!
! !
! Create a Modicon 584 device !
! !
!********************************************************************!
!create device MOD_584 /type=MOD_584_TYPE -
! /descrip="Modicon 584"/netaddress=YY -
! /path=MODBUS_PATH/manuf="Modicon"/timeout=300/LOG
2-16 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
!********************************************************************!
! !
! Create a Modicon 984 device !
! !
!********************************************************************!
!create device MOD_984 /type=MOD_984_TYPE -
! /descrip="Modicon 984"/netaddress=YY -
! /path=MODBUS_PATH/manuf="Modicon"/timeout=400/LOG
!********************************************************************!
! !
! Create a Modicon 984 device using MODBUS PLUS !
! !
!********************************************************************!
!create device MPLUS_984 /type=MOD_984_TYPE -
! /descrip="Modicon 984"/netaddress="YY-YY-YY-YY-YY" -
! /path=MPLUS_PATH/manuf="Modicon"/timeout=400/LOG
!
!create device MHOST_984 /type=MOD_HOST_TYPE -
! /descrip="Modicon 984"/netaddress="YY" -
! /path=MPLUS_PATH/manuf="Modicon"/timeout=400/LOG
$ exit
For more information about maintaining type, path, and
device definitions, refer to the BASEstar Classic Command
Line Interface User's Guide.
2.3.2 DAS SPT Block Usage
The ILAN$MAX_SPT_REQUESTS parameter specifies the maximum
number of blocks allocated in the SPT (support) global
section. To set this parameter, perform the following
steps:
1. If using the MODBUS NI, approximate the SPT blocks for
this DAS by using the following formula:
SPT = 1 + num_paths + (6 * num_devices)
If using the MODBUS PLUS NI, approximate the SPT blocks
for this DAS by using the following formula:
SPT = 1 + num_paths + (8 * num_devices) + (2 * ILAN$MOD984_UNSOL_QUEUE_SIZE)
Installing the DAS for Modicon Programmable Controllers 2-17
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
The num_paths argument is the number of paths defined in
the configuration file. The num_devices argument is the
number of Modicon devices defined. The SPT argument is
the approximate number of blocks for the DAS for Modicon
programmable controllers.
2. Use SPT to calculate the total block requirements
for the ILAN$MAX_SPT_REQUESTS parameter. Refer to
the BASEstar Classic Configuration and Tuning Guide
for instructions on calculating the total block
requirements.
2.3.3 Configuring Ports
A device can be physically connected to a local area
transport (LAT) port. To use a LAT port with the DAS,
you must define the LAT port on the host system by using
the LAT control program. The following DCL example shows
how to define port_2 on the LAT node srvr4 as LTA992. It
is very important when defining the LAT port to use the
/NOQUEUE option. If the port is owned by another process
device connection management reports an error during the
establishment of a connection to the device. When you
define a path and a device to BASEstar Classic device
connection management LTA992 is supplied as the VAXport.
$ MCR LATCP
LCP> CREATE PORT LTA992
LCP> SET PORT LTA992 /NODE=srvr4/PORT=port_2/NOQUEUE
For the DAS to send and receive data correctly, you must
set and define LAT port characteristics to match the line
parameters of the path definition for devices and terminals
connected to the LAT. An example of the characteristics set
at the LAT prompt follows:
Local> DEF PORT n SPEED 9600
Local> DEF PORT n AUTOBAUD DISABLED
Local> DEF PORT n AUTOCONNECT DISABLED
Local> DEF PORT n FLOW DISABLED
Local> DEF PORT n PREFERRED NONE
Local> DEF PORT n ACCESS REMOTE
Local> DEF PORT n CHAR 8
Local> DEF PORT n PARITY EVEN
2-18 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
You must also set the following SYSGEN parameters to access
Modicon programmable controllers to reduce the potential
for data overruns. Use the SYSGEN utility to display the
current values and AUTOGEN to reset the values accordingly.
For information on using SYSGEN and AUTOGEN, refer to the
OpenVMS System Management Utilities Reference Manual for
details.
___________________________________________________________
Parameter________Value_____________________________________
TTY_ALTALARM 0
TTY_ALTYPAHD_____1024______________________________________
To enable use of the alternate typeahead buffer, type the
following command from DCL:
$ SET TERM LTA992:/ALTYPEAHD/PERMANENT
2.3.4 Addressing a Modbus Plus Node
Modbus Plus requires 5 bytes of routing information to
address a particular node on the network. This method
allows remote nodes to be addressed up to four networks
away from the VAX. The range of node addresses on a single
network is 1 ... 64. The format for the network address
field within DCM is as follows:
xx-xx-xx-xx-xx
Where xx is the routing address byte. All five bytes of
routing information must be included in the network address
field. A zero as a routing byte indicates that no further
routing will occur. Once a zero is encountered as a routing
address byte all of the remaining routing bytes must be
zero.
2.3.5 Addressing a Modbus Plus Host Node
When addressing the host node only one routing address
byte is required. Specify the Modbus-Plus address of the
host SQ-85/SA-85 card. Only one host device is allowed per
Modbus-Plus card.
Installing the DAS for Modicon Programmable Controllers 2-19
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
2.3.6 Setting Modbus Plus Parameters
The installation procedure for the DAS for Modicon
programmable controllers creates BASEstar Classic
parameters to allow you to tune the Modbus Plus environment
for collecting unsolicited data. These parameters are
discussed in Table 2-9.
Table_2-9_Modbus_Plus_Parameters___________________________
Parameter_____________Default_____Description______________
ILAN$MOD984_MAX_REG_ 1000 This value specifies
ADDRESS the maximum holding
register offset value
that can be specified
as the destination in
a Modbus MSTR write
function block.
ILAN$MOD984_UNSOL_ 7 This value specifies
QUEUE_SIZE the size of the queue
to receive unsolicited
write messages from the
Modbus-Plus network. A
larger value allows more
data to be handled in a
burst of messages from
the Modbus-Plus network
at the expense of more
memory consumption.
ILAN$MODHOST_MAX_ 1000 This value specifies
REG_ADDRESS the maximum holding
register offset value
that can be specified
as the destination in a
Modbus MSTR read function
block.
(continued on next page)
2-20 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.3 Postinstallation Tasks
Table_2-9_(Cont.)_Modbus_Plus_Parameters___________________
Parameter_____________Default_____Description______________
ILAN$MODHOST_UNSOL_ 7 This value specifies
QUEUE_SIZE the size of the queue
to receive unsolicited
read messages from the
Modbus-Plus network. A
larger value allows more
data to be handled in a
burst of messages from
the Modbus-Plus network
at the expense of more
__________________________________memory_consumption.______
2.3.7 Setting Up Plant-Floor Equipment
For information on configuring your Modicon equipment,
see Appendix A. For information on your specific device,
refer to the Modbus System Planning Guide and the J478
Stand-Alone Modem Guide for Modbus communications or to the
Modicon DEC Host Based Devices User's Guide for Modbus-Plus
communications.
2.4 Tracing Device Communications
The DAS for Modicon programmable controllers has built
into it the capability to trace programmable controller
communications and to send this output to either a file
or a user terminal. The purpose of this tracing is to
allow the troubleshooting of programmable controller
communications.
To enable tracing do the following:
o Set one of the following logicals to 1:
DCM_MOD$MODBUS_TRACE Trace the MODBUS NI (Network
Interface)
DCM_MOD$MPLUS_TRACE Trace the MODBUS-PLUS NI
(Network Interface)
The logical name must be defined in a scope that will be
seen by the device server process (ILAN$DEVSRV).
Installing the DAS for Modicon Programmable Controllers 2-21
Installing the DAS for Modicon Programmable Controllers
2.4 Tracing Device Communications
o Set the trace output logical to a file or other output
device:
DCM_MOD$MODBUS_TRACE_ Trace the MODBUS NI (Network
OUTPUT Interface)
DCM_MOD$MPLUS_TRACE_ Trace the MODBUS-PLUS NI
OUTPUT (Network Interface)
The logical name must be defined in a scope that will be
seen by the device server process (ILAN$DEVSRV).
o Start the tracing.
To start tracing for the NI, disable all devices on the
line for which tracing is desired and reenable them. The
trace logical is read when the first device on the line
is enabled.
The trace output is flushed to the file after every 100
lines that are traced, so trace output may lag actual
device I/O.
To turn tracing off, reverse the steps used to turn tracing
on.
2.5 Failures During Product Use
If an error occurs while this product is in use and you
believe the error is caused by a problem with the product,
take one of the following actions:
o If you have a Software Product Services Support
Agreement, contact your Customer Support Center (CSC)
by telephone or by using the electronic means provided
with your support agreement (such as DSNlink). The CSC
provides telephone support for high-level advisory and
remedial assistance. When you initially contact the CSC,
indicate the following:
- The name and version number of the operating system
you are using
- The version number of the product you are using
- The version number of BASEstar Classic you are using
- The hardware system you are using (such as a model
number)
2-22 Installing the DAS for Modicon Programmable Controllers
Installing the DAS for Modicon Programmable Controllers
2.5 Failures During Product Use
- The Modicon programmable controllers you are
communicating with
- A brief description of the problem (one sentence if
possible)
- How critical the problem is
o If you have a Self-Maintenance Software Agreement, you
can submit a Software Performance Report (SPR).
o If you do not have any type of software services support
agreement and you purchased this product within the past
year, you can submit an SPR if you think the problem is
caused by a software error.
When you submit an SPR, take the following steps:
1. Describe as accurately as possible the circumstances and
state of the system when the problem occurred. Include
the description and version number of the product being
used. Demonstrate the problem with specific examples.
2. Reduce the problem to as small a size as possible.
3. Remember to include listings of any command files,
INCLUDE files, or relevant data files, and so forth.
4. Report only one problem per SPR. This will facilitate a
faster response.
5. Mail the SPR package to Digital.
Installing the DAS for Modicon Programmable Controllers 2-23
3
_________________________________________________________________
Using the DAS for Modicon Programmable Controllers
This chapter provides information about the supported
functions for Modicon devices, and how to access these
functions.
3.1 Accessing the DAS for Modicon Programmable Controllers
Functions
DAS for Modicon programmable controllers functions are
accessed through the BASEstar Classic software, through the
following means:
o Commands
o Menu system
o Callable services
To use the BASEstar Classic device connection management
commands, enter the following command at the DCL prompt
($):
$ BSTAR DCM
To use the BASEstar Classic device connection management
menu system, enter the following command:
$ BSTAR/MENU
For information about the BASEstar Classic device
connection management commands and the menu system, refer
to the BASEstar Classic Menu Interface User's Guide.
For information about the BASEstar Classic device
connection management callable services, refer to the
BASEstar Classic Introduction to Callable Services.
Using the DAS for Modicon Programmable Controllers 3-1
Using the DAS for Modicon Programmable Controllers
3.2 Structured Data
3.2 Structured Data
Structured data is a block of data, typically represented
by a buffer, that can be broken down into meaningful
elements of data. Structured data allows you to impose a
structure on the data formats for any given read or write
operation. A structure tells the device how to interpret
the data that it is reading or writing.
Structured data can represent synchronized data elements
from a single source, such as a plant-floor device.
Structured data can also represent composite views of
different data elements from different sources, such as
the total part counts from several different plant-floor
devices.
For the DAS for Modicon programmable controllers, mixed
data types are not allowed within a given address range.
3.3 Supported Functions
This section describes the functions that are supported
by the DAS for Modicon programmable controllers devices
Table 3-1 displays the Modicon devices and the functions
they support.
Table_3-1_Modicon_Devices_and_Functions__________________________
Read Write Read
Device____Upload__DownloadStart___Stop____Data____Data____Status_
984A X X X X X X X
984B X X X X X X X
984X X X X X X X X
884 X X X X X X X
584L X X X X X X X
584M X X X X X X X
484 X X X X X X X
384 X X X X X X
184 X X X X X X
Micro_84__X_______X_______________X_______X_______X_______X______
3-2 Using the DAS for Modicon Programmable Controllers
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
3.3.1 Start and Stop
The start and stop functions change the operating mode of
a device. The start function enables outputs and the stop
function disables outputs.
_______________________ Warning _______________________
Devices can control complex and perhaps dangerous
industrial processes. Do not use the start and
stop functions until you take the required safety
precautions and put required operating restrictions
into effect. Refer to the manufacturer's documentation
for specific safety precautions.
______________________________________________________
The start function is not implemented for the Modicon 384
and Micro 84 programmable controllers.
3.3.2 Upload and Download
The upload function transfers the contents of a device's
memory to an OpenVMS file. The download function transfers
the contents of an OpenVMS file to a device's memory.
The upload functions for the Modicon 884 and Micro 84
devices must issue a login command to the programmable
controller. The login command will fail if there is another
device logged in to the controller.
To perform the download function, the memory protect
keyswitch must be in the OFF position for all device
models. For the Modicon 584, 884, 984, and Micro 84
devices, all other devices must be detached.
________________________ Note ________________________
You perform a download function on a Modicon device
without first stopping the device.
______________________________________________________
Using the DAS for Modicon Programmable Controllers 3-3
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
3.3.3 Read and Write Data Functions
Use the BASEstar Classic device connection management
read data and write data functions to read data from and
write data to a specific address in device storage. Address
syntax is specific to each device or device family, and is
similar to the syntax used with the Modicon terminals. The
supported data types depend on the device.
Example 3-1 shows an example of the information displayed
when you enter the READ DATA command.
Example 3-1 Read Data Screen
DCM> read data mod_584/addr=00001/form=bit
Device : MOD_584
Data starting at address 00001 for BIT element.
Data:
0: 1
DCM> read data mod_584/addr=00001/form=array[64]:bit
Device : MOD_584
Data starting at address 00001 for ARRAY[64]:BIT element.
Data:
0: 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
16: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
32: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
48: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Example 3-2 provides an example of the information
displayed when you enter the READ DATA command using
structured data.
3-4 Using the DAS for Modicon Programmable Controllers
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
Example 3-2 Read Data Screen with Structured Data
DCM> cre phyp p1/dev=mod_584_1/addr=00001/form="struct" -
DCM> (word,word,array[10]:word)"/write
DCM> read phyp p1/dev=mod_584_1
Point : P1
Device : MOD_584_1
Address : 40100
Format : STRUCTURE(S_WORD,S_WORD,ARRAY[10]:S_WORD)
Data:
0 : 26
1.0 : 29 29 29 29 29 29
1.7 : 29 29 29
Example 3-3 shows an example of the information displayed
when you enter the WRITE DATA command.
Example 3-3 Write Data Screen
DCM> write data mod_584/addr=40200/format=word
Device : MOD_584
Data starting at address 40200 for S_WORD element
Data value 0 : 100
Example 3-4 shows an example of the information displayed
when you enter the WRITE DATA command using structured
data.
Example 3-4 Write Data Screen with Structured Data
DCM> write phyp p2/dev=mod_584_1
Point : P2
Device : MOD_584_1
Address : 00001
Format : STRUCTURE(BIT,BIT,ARRAY[8]:BIT)
(continued on next page)
Using the DAS for Modicon Programmable Controllers 3-5
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
Example 3-4 (Cont.) Write Data Screen with Structured Data
Data value 0 : 1
Data value 1 : 0
Data value 2.0 : 1
Data value 2.1 : 1
Data value 2.2 : 1
Data value 2.3 : 0
Data value 2.4 : 0
Data value 2.5 : 0
Data value 2.6 : 0
Data value 2.7 : 1
The following sections describe the use of the read data
and write data functions by specific Modicon devices,
including addressing and data type formats. The supported
data type formats are bit, word, unsigned word, and
longword.
3.3.3.1 Modicon 184 and Modicon 384
Addressing and data type formats are necessary for
performing the read data and write data functions for the
Modicon 184 and Modicon 384 device.
Addressing
The valid addressing types for the Modicon 184 and Modicon
384 are:
0001 - 0xxx Lines
1001 - 1xxx Discrete inputs
3001 - 3xxx Input registers
4001 - 4xxx Holding registers
________________________ Note ________________________
You cannot write to discrete inputs or input
registers.
______________________________________________________
3-6 Using the DAS for Modicon Programmable Controllers
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
Data Type Formats
The valid data type formats for the Modicon 184 and Modicon
384 are:
0001 - 0xxx Bit
1001 - 1xxx Bit
3001 - 3xxx Word or U_word
4001 - 4xxx Word or U_word
3.3.3.2 Modicon 484
Addressing and data type formats are necessary for
performing the read data and write data functions for the
Modicon 484 device.
Addressing
The valid addressing types for the Modicon 484 are:
0001 - 0xxx Outputs
1001 - 1xxx Discrete inputs
3001 - 3xxx Input registers
4001 - 4xxx Holding registers
Data Type Formats
The valid data type formats for the Modicon 484 are:
0001 - 0xxx Bit
1001 - 1xxx Bit
3001 - 3xxx Word or U_word
4001 - 4xxx Word or U_word
3.3.3.3 Modicon 584 and Modicon 984
Addressing and data type formats are necessary for
performing the read data and write data functions for the
Modicon 584 and 984 devices.
Addressing
The valid addressing types for the Modicon 584 and 984 are:
00001 - 0xxxx Coils
10001 - 1xxxx Discrete inputs
30001 - 3xxxx Input registers
40001 - 4xxxx Holding registers
________________________ Note ________________________
For the Modicon 984, the maximum holding and input
register is 65535. For the Modicon 584, the maximum
Using the DAS for Modicon Programmable Controllers 3-7
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
holding and input register is 9999.
______________________________________________________
For controllers that have the extended file capability, the
format is as follows:
60000:1 - 6xxxx:y xxxx is the highest register number within a file
y is the file number
________________________ Note ________________________
You cannot write to discrete inputs or input
registers.
______________________________________________________
Data Type Formats
The valid data type formats for the Modicon 584 and 984
are:
00001 - 0xxxxx Bit
10001 - 1xxxxx Bit
30001 - 3xxxxx Word or U_word
40001 - 4xxxxx Word or U_word
60001:1 - 6xxxxx:y Word or U_word
3.3.3.4 Modicon 884
Addressing and data type formats are necessary for
performing the read data and write data functions for the
Modicon 884 device.
Addressing
The valid addressing types for the Modicon 884 are:
00001 - 00768 Coils
10001 - 10256 Discrete inputs
20001 - 23200 Sequencer registers
30001 - 30128 Input registers
40001 - 40864 Holding registers
50001 - 50032 Double precision registers
90001 - 90256 Latches
________________________ Note ________________________
You cannot write to discrete inputs, input registers,
double precision registers, and latches.
______________________________________________________
3-8 Using the DAS for Modicon Programmable Controllers
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
Data Type Formats
The valid data type formats for the Modicon 884 are:
00001 - 00768 Bit
10001 - 10256 Bit
20100 - 23200 Word
30001 - 30128 Word or U_word
40001 - 40864 Word or U_word
50001 - 50016 Longword
90001 - 90256 Word or U_word
3.3.3.5 Micro 84
Addressing and data type formats are necessary for
performing the read data and write data functions for the
Micro 84 device.
Addressing
The valid addressing types for the Micro 84 are:
0001 - 0064 Coils
1001 - 1064 Discrete inputs
3001 - 3004 Input registers
4001 - 4032 Holding registers
________________________ Note ________________________
You cannot write to discrete inputs or input
registers.
______________________________________________________
Data Type Formats
The valid data type formats for the Micro 84 are:
0001 - 0064 Bit
1001 - 1064 Bit
3001 - 3004 Word or U_word
4001 - 4032 Word or U_word
Using the DAS for Modicon Programmable Controllers 3-9
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
3.3.4 Read Status
The read status function issues a diagnostic status
request to the programmable controller, interprets the
device response, and returns the interpretation as a
character buffer. An error message is displayed if a
device definition does not match the device in the device
response. If this occurs, you must correct the device
definition before you can perform an upload function or
download function for the device.
The BASEstar Classic Command Line Interface User's Guide
gives detailed information about the READ STATUS command.
To display the returned values for device status, enter
the following at the BASEstar Classic device connection
management prompt:
DCM> READ STATUS device-name/FULL
Example 3-5 shows an example of the values returned in the
status buffer when you enter the command for reading device
status.
Example 3-5 Read Status Screen
DCM> read status mod_384/full
Status of device mod_384 at dd-mmm-yyyy 09:50:50.55
Processor Type : Modicon 384
Executive I.D : 101071
Memory Protection: OFF
Processor State : RUNNING
DCM> read status mod_884/full
Status of device mod_884 at dd-mmm-yyyy 09:50:54.72
Processor Type : Modicon 884
Application Memory : 9 K bytes
Processor State : RUNNING
For the host pseudo-device used to process unsolicited
read requests from a Modbus-Plus device the read status
command displays the number of read requests and the number
3-10 Using the DAS for Modicon Programmable Controllers
Using the DAS for Modicon Programmable Controllers
3.3 Supported Functions
of "trigger" notification sent. "Triggers" and unsolicited
read requests are discussed in Section 3.4.2.
3.4 Automatic Data Collection
BASEstar Classic device connection management supports
automatic data collection using both polled and unsolicited
data collection. Polled data collection is supported for
both Modbus and Modbus-Plus communications. Unsolicited
data collection is supported for Modbus-Plus data
collection only.
3.4.1 Polled Data Collection
BASEstar Classic device connection management physical
points may be grouped together into pollsets to optimize
data collection. Pollsets created for the Modicon devices
have the following limitations:
o Physical points of differing data types cannot be part
of the same pollset. For example, a physical point of
type WORD and a physical point of type BIT cannot be
members of the same pollset. Physical points of the same
data type with varying element counts can reside in the
same pollset.
o The size of any pollset cannot exceed 200 contiguous
bytes, regardless of the number of physical points in
the pollset. Therefore, the first byte of the physical
point with the lowest address cannot be more than 200
bytes away from the last byte of the physical point with
the highest address.
For more information on physical points, refer to the
BASEstar Classic Command Line Interface User's Guide.
3.4.2 Unsolicited Data Collection
The DAS for Modicon programmable controllers supports
unsolicited data collection using Modbus-Plus only.
Unsolicited data collection for the Modicon devices have
the following limitations:
o The only supported functions are reads and writes to the
host. Get statistics, etc. are not supported.
Using the DAS for Modicon Programmable Controllers 3-11
Using the DAS for Modicon Programmable Controllers
3.4 Automatic Data Collection
o Only holding registers can be read from or written to
the host. This limitation is imposed by the Modbus-Plus
protocol.
o Reads or writes must be done to slave path numbers 1 or
2. Other slave paths are not supported.
o For writes, the first 5 words written must contain
routing information for the node performing the write.
The DAS for Modicon programmable controllers uses the
first five words of the message to determine which
programmable controller sent the message and therefore
which device to associate with this message.
o For reads, a special "host" device must be used to
receive the unsolicited read request.
o The size of the data being written must match the size
the definition of the corresponding physical point. If
the sizes are different then an error is generated for
the physical point being written.
3.4.2.1 Unsolicited ID
The DAS for Modicon programmable controllers supports both
unsolicited read and write requests from the programmable
controller. The following sections describe the unsolicited
ID syntax for reads and writes.
Unsolicited IDs for Write
For writes, the unsolicited ID specified in the physical
point definition defines the first holding register address
being written. (This address starts after the routing
information contained in the first 5 words of the message.)
The valid unsolicited ID type for the Modbus-Plus writes
is:
400001 - 4xxxxx Word or U_word
The maximum holding register is specified by the parameter
ILAN$MOD984_MAX_REG_ADDRESS.
3-12 Using the DAS for Modicon Programmable Controllers
Using the DAS for Modicon Programmable Controllers
3.4 Automatic Data Collection
Unsolicited IDs for Read
For reads, the unsolicited ID specified in the physical
point definition defines the first holding register address
being read. It also defines the name of the logical point
from which to get the data to be returned to the device.
The valid unsolicited ID types for the Modbus-Plus reads
are:
400001:POINT_NAME - 4xxxxx:POINT_NAME Word or U_word
400001:TRIGGER - 4xxxxx:TRIGGER Bit
The maximum holding register is specified by the parameter
ILAN$MODHOST_MAX_REG_ADDRESS. The POINT_NAME is the name of
a BASEstar Classic logical point from which to retrieve the
data to be sent to the device.
A trigger unsolicited ID can also be specified. The
trigger point can be used to notify an application when the
programmable controller has read the associated unsolicited
read point. A trigger is specified by creating a physical
point with an unsolicited ID with the same holding register
number of the associated physical point and a "POINT_NAME"
of "TRIGGER". The "TRIGGER" keyword is reserved and cannot
be used as a logical point name.
Using the DAS for Modicon Programmable Controllers 3-13
A
_________________________________________________________________
Equipment Configuration
Figure A-1 shows the cable wiring and pin assignments from
the processor to the J478 modem.
Figure A-1 Processor-to-Modem Connection
Equipment Configuration A-1
Equipment Configuration
Modbus Configuration
Modbus is an industrial communication network that can link
one master to as many as 247 slaves. Specific masters may
have restrictions that limit the number of slaves.
The host port modem is wired as the master on the Modbus.
The master modem is connected by twisted-pair wire to
all of the slave modems, such as a J478 or a J474, that
interface to the individual programmable controllers.
Figure A-2 represents a Modbus configuration.
Figure A-2 Modbus Block Diagram
A-2 Equipment Configuration
Equipment Configuration
Figure A-3 represents a Modbus-Plus configuration.
Figure A-3 Modbus Plus Block Diagram
Equipment Configuration A-3
_________________________________________________________________
Index
A Data type formats (cont'd)
_______________________________ Modicon 884, 3-9
Accessing DAS functions, 3-1 Modicon 984, 3-8
Addressing structured data, 3-4
Micro 84, 3-9 Device access software
Modicon 184, 3-6 accessing functions, 3-1
Modicon 384, 3-6 description of, 1-1
Modicon 484, 3-7 installation of, 2-1
Modicon 584, 3-7 installation requirements,
Modicon 884, 3-8 2-1
Modicon 984, 3-7 overview, 1-1
Automatic data collection, supported devices, 1-2
3-11 supported functions, 1-2,
pollsets, 3-11 3-2
unsolicited, 3-11 using, 3-1
Device communications
C______________________________ tracing, 2-21
Configuration file Device records, 2-12
device records, 2-12 Devices, 1-1
editing, 2-9 communications, 1-1
example, 2-14 Modicon, 1-2
path records Disk space requirements, 2-3
line parameters, 2-11 Download function, 3-3
type records, 2-9
Configuring ports, 2-18 F______________________________
Files
D______________________________ created during installation,
Data type formats 2-6
Micro 84, 3-9 Functions
Modicon 184, 3-7 read data, 3-4
Modicon 384, 3-7 write data, 3-4
Modicon 484, 3-7
Modicon 584, 3-8
Index-1
Modicon 584
H______________________________ addressing, 3-7
Hardware data type formats, 3-8
required, 2-1 read data, 3-7
write data, 3-7
I Modicon 884
_______________________________ addressing, 3-8
Installation, 2-1 data type formats, 3-9
files created, 2-6 read data, 3-8
messages, 2-7 write data, 3-8
postinstallation tasks, 2-8 Modicon 984
procedure, 2-3 addressing, 3-7
requirements, 2-1 data type formats, 3-8
read data, 3-7
L______________________________ write data, 3-7
Line parameters, 2-11
P______________________________
M______________________________ Path records, 2-11
Messages Plant-floor equipment
installation, 2-7 setting up, 2-21
Micro 84 Postinstallation tasks, 2-8
addressing, 3-9 Problem reporting, 2-22
data type formats, 3-9 Product failure, 2-22
read data, 3-9
write data, 3-9 R______________________________
Modbus Plus Read data function
addressing node, 2-19 Micro 84, 3-9
setting parameters, 2-20 Modicon 184, 3-6
Modicon 184 Modicon 384, 3-6
addressing, 3-6 Modicon 484, 3-7
data type formats, 3-7 Modicon 584, 3-7
read data, 3-6 Modicon 884, 3-8
write data, 3-6 Modicon 984, 3-7
Modicon 384 structured data, 3-2
addressing, 3-6 Read data functions, 3-4
data type formats, 3-7 Read status function, 3-10
read data, 3-6
write data, 3-6 S______________________________
Modicon 484 Software
addressing, 3-7 additional required, 2-3
data type formats, 3-7 required, 2-2
read data, 3-7 SPT block usage, 2-17
write data, 3-7
Index-2
Start function, 3-3 Unsolicted ID
Stop function, 3-3 syntax, 3-12
Structured data, 3-2 Upload function, 3-3
mixed data types, 3-2
W______________________________
T______________________________ Write data function
Trace Micro 84, 3-9
using, 2-21 Modicon 184, 3-6
Type records, 2-9 Modicon 384, 3-6
Modicon 484, 3-7
U______________________________ Modicon 584, 3-7
Unsolicited ID Modicon 884, 3-8
read, 3-13 Modicon 984, 3-7
write, 3-12 structured data, 3-2
Write data functions, 3-4
Index-3