Tele PACE User And Reference Manual
TelePACE%20User%20and%20Reference%20Manual
User Manual:
Open the PDF directly: View PDF 
.
Page Count: 1184
| Download | |
| Open PDF In Browser | View PDF |
TelePACE Ladder Logic
Overview
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE,
TeleSAFE Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus,
SCADAPack 32, SCADAPack 32P, SCADAPack 350, SCADAPack LP,
SCADAPack 100, SCADASense 4202 DS, SCADASense 4202 DR,
SCADASense 4203 DS, SCADASense 4203 DR, SCADASense 4102,
SCADASense 4012, SCADASense 4032 and TeleBUS are registered
trademarks of Control Microsystems.
All other product names are copyright and registered trademarks or trade names
of their respective owners.
Material used in the User and Reference manual section titled SCADAServer
OLE Automation Reference is distributed under license from the OPC
Foundation.
TelePACE Ladder Logic Overview
May 8, 2007
1
Table of Contents
1
TELEPACE LADDER LOGIC OVERVIEW.................................................... 4
1.1
System Requirements .............................................................................. 4
1.2
Installation on a Hard Disk ........................................................................ 4
1.3
Running TelePACE Ladder Logic Editor................................................... 4
2
LADDER EDITOR ENVIRONMENT .............................................................. 5
2.1
Introduction ............................................................................................... 5
2.2
2.2.1
2.2.2
Ladder Editor Display ............................................................................... 5
Title Bar ............................................................................................... 5
Menu Bar............................................................................................. 5
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
Tool Bar .................................................................................................... 5
Network Title ....................................................................................... 7
Comment Editor .................................................................................. 7
Splitter Bar........................................................................................... 7
Status Bar............................................................................................ 7
Network Display .................................................................................. 7
Register List ........................................................................................ 7
Cursor.................................................................................................. 8
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
TelePACE Major Components.................................................................. 9
Networks ............................................................................................. 9
Network Elements ............................................................................... 9
Subroutines ......................................................................................... 9
Program Execution Order.................................................................. 10
Ladder Logic Memory Usage ............................................................ 10
2.5
2.5.1
2.5.1.1
TelePACE I/O Database Registers......................................................... 11
16-bit Controller I/O Database........................................................... 11
I/O Database register types ......................................................... 12
2.5.1.1.1
2.5.1.1.2
2.5.1.1.3
2.5.1.1.4
2.5.2
2.5.2.1
2.5.2.1.1
2.5.2.1.2
2.5.2.1.3
2.5.2.1.4
Coil Registers ................................................................................... 12
Status Registers ............................................................................... 13
Input Registers ................................................................................. 13
Holding Registers ............................................................................. 13
32-bit Controller I/O Database........................................................... 13
I/O Database register types ......................................................... 14
Coil Registers ................................................................................... 14
Status Registers ............................................................................... 14
Input Registers ................................................................................. 15
Holding Registers ............................................................................. 15
TelePACE Ladder Logic Overview
May 8, 2007
2
2.5.3
2.5.3.1
2.5.3.1.1
2.5.3.1.2
2.5.3.1.3
2.5.3.1.4
SCADAPack 100: 256K I/O Database............................................... 15
I/O Database register types ......................................................... 16
Coil Registers ................................................................................... 16
Status Registers ............................................................................... 16
Input Registers ................................................................................. 16
Holding Registers ............................................................................. 16
TelePACE Ladder Logic Overview
May 8, 2007
3
1
TelePACE Ladder Logic Overview
TelePACE ladder logic is ideal for electricians, engineers, and programmers who program
sequencing and process control. The ladder logic editor is a powerful tool for writing, debugging
and documenting ladder logic programs. The SCADAPack and TeleSAFE family of controllers
executes ladder logic and C application programs simultaneously, providing you with maximum
flexibility in implementing your control strategy.
This manual provides full documentation on the TelePACE program including the Ladder Network
Editor and the ladder logic programming language. We strongly encourage you to read it, and to
notify us if you identify any items that you feel should be clarified, or included in future
documentation releases.
We sincerely hope that the reliability and flexibility afforded by this fully programmable controller
enable you and your company to solve your automation problems in a cost effective and efficient
manner.
To use TelePACE, you need to install the program on your system. The automated installation takes
only a few minutes.
Some virus checking software may interfere with Setup. If you experience problems with Setup,
disable your virus checker and run Setup again.
1.1
System Requirements
The TelePACE ladder editor requires the following minimum system configuration.
•
Microsoft Windows NT, Windows 2000 or Windows XP operating systems. Note that
Windows 95, 98 and ME operating systems are no longer supported.
• Mouse or compatible pointing device; and
• Hard disk with approximately 2.5 Mbytes of free disk space.
1.2
Installation on a Hard Disk
To install the TelePACE Ladder Logic Editor:
1. Click Start, then select Run.
2. From the Run dialog box, select Browse and select the setup.exe file in the TelePACE
Demo folder on the CD.
3. Follow the setup directions on the screen.
1.3
Running TelePACE Ladder Logic Editor
To run the ladder logic editor:
•
Click Start, then select the TelePACE icon grouping, and select TelePACE Ladder
Editor.
TelePACE Ladder Logic Overview
May 8, 2007
4
2
2.1
Ladder Editor Environment
Introduction
The TelePACE Ladder Network Editor is a powerful programming and monitoring tool that enables
the user to create, edit, document, save, and read or write Ladder Logic programs for the controller.
This section of the manual outlines the features of the Ladder Logic Editor. A full description of the
Editor is described in the TelePACE Program Reference section of this manual. The user is
encouraged to read the following sections to gain an understanding of the many programming and
monitoring features available.
2.2
Ladder Editor Display
The following figure illustrates the TelePACE Ladder Editor:
Title Bar
Menu Bar
Tool Bar
Network Title
Comment Editor
Splitter Bar
Network Display
Status Bar
Command Description Cursor Location
Mode
Memory Used
Figure 1: TelePACE Ladder Editor Display
2.2.1
Title Bar
The title bar displays the TelePACE program title and the name of the ladder logic file. The file
name area is blank if there is no file in use or the file is new and has not been saved.
2.2.2
Menu Bar
The menu bar displays the programming, editing, monitoring and utility functions available within
the Editor. Menu commands can be displayed by clicking the mouse on the menu item or by
pressing the alt key and the underlined letter of the menu item.
2.3
Tool Bar
The Tool Bar contains buttons for commonly used commands.
TelePACE Ladder Logic Overview
May 8, 2007
5
Icon
Command
Open File
Save File
Print
Previous Network
Next Network
Read From Controller
Write To Controller
C Program Loader
Connect to Controller
Disconnect from Controller
Edit Off Line
Edit On Line
Monitor On Line
Help
TelePACE Ladder Logic Overview
May 8, 2007
Description
Opens an existing ladder program file. This is the same as
the Open command in the File menu.
Saves the currently open ladder program file. This is the
same as the Save command on the File menu.
Prints the currently open ladder program file. This is the
same as the Print command on the File menu. The Print
dialog box appears. This option is disabled when the editor
is in Monitor On Line mode.
Displays the previous network in the currently open ladder
program. This is the same as selecting Previous from the
Go To Network command in the Search menu.
Displays the next network in the currently open ladder
program. This is the same as selecting Next from the Go
To Network command in the Search menu.
The ladder logic program, register assignment and serial
port settings in the controller are read into TelePACE
memory. This is the same as the Read From Controller
command on the Communication menu.
The ladder logic program, register assignment and serial
port settings in the TelePACE program are written to the
controller. This is the same as the Write To Controller
command on the Communication menu.
The C Program Loader dialog box appears. This is the
same as the C Program Loader command on the
Controller menu.
Establishes a connection to a remote unit using a dial up
modem. This button is disabled if the current controller is
not a dial up connection. This is the same as the Connect
To Controller command on the Communication menu.
Ends a connection to a remote unit using a dial up modem.
This button is disabled if the current controller is not a dial
up connection. This is the same as the Disconnect From
Controller command on the Communication menu.
Places the editor in Off Line editing mode. This mode is
used for creation and editing of a ladder program file. This
is the same as the Edit Off Line command on the Activity
menu.
Places the editor in On Line editing mode. In this mode,
any change to the ladder program is immediately written to
the controller. This is the same as the Edit On Line
command on the Activity menu.
Places the TelePACE program in Monitor On Line mode.
This mode is used to monitor ladder program execution in
real time. Color is used to indicate power flow within the
displayed network. The contents of a user-defined list of
registers (see Monitor List) are updated in real time. This
is the same as the Monitor On Line command on the
Activity menu.
Displays the TelePACE program on-line help file. This is
the same as selecting Contents from the Help menu.
6
2.3.1
Network Title
The network title has three sections. The left section displays the number of the network being
edited and the total number of networks (current/total). Clicking the left mouse button here opens
the Go To Network dialog.
The center section displays Main if the current network is in the main program and Sub x if it’s in a
subroutine.
The right section of the Network Title shows the network title. Clicking here opens the Edit
Network Title pop up dialog box.
2.3.2
Comment Editor
Each network in the ladder program can have approximately three pages of text documentation. The
text in the comment editor can be cut or copied to the Windows clipboard or pasted from the
clipboard.
The comment editor is selected for editing by positioning the mouse pointer anywhere in the
comment editor pane and left clicking the mouse button. A vertical bar indicates the cursor position
within the comment editor pane. The scroll bar to the right of the comment editor pane scrolls the
editor text within the pane.
2.3.3
Splitter Bar
The splitter bar divides the Comment Editor and the Ladder Editor Panes. Positioning the mouse
pointer over the bar and dragging the bar to a new location changes the position of the splitter bar.
2.3.4
Status Bar
The status bar displays command and programming status of the Network Editor. The Status Bar is
divided into five panels.
The leftmost panel describes the Toolbar or Menu command pointed to by the mouse.
The second and third panels show the column and row position of the cursor in the Ladder Editor
pane.
The fourth panel displays the execution mode of the attached controller, or OFFLINE if the Network
Editor is not communicating with a controller.
The last panel displays the percentage of ladder logic memory used in the target controller.
2.3.5
Network Display
The Ladder Editor Pane displays the current network of the open program. This area is used for
creation and editing of the ladder logic. When in Monitor On Line mode, this area also contains the
Monitor list.
2.3.6
Register List
The register list is a display window containing a list of selected I/O database registers and their real
time contents. The I/O database registers to be included in monitor list display window are defined
by selecting Registers from the Edit Menu.
TelePACE Ladder Logic Overview
May 8, 2007
7
2.3.7
Cursor
To position the cursor in the Ladder editor pane move the mouse pointer to any position in the
displayed Ladder network and click the left mouse button. The cursor highlights the element or
function where it is positioned. The cursor can be moved about the network using the arrow keys on
the keyboard.
TelePACE Ladder Logic Overview
May 8, 2007
8
2.4
TelePACE Major Components
The major components of a ladder program are ladder networks, function elements, subroutines, and
comments. Understanding how these components work and how a program is executed is important
to writing an effective program.
NOTE:
2.4.1
Program execution order (described below) must be considered when organizing the
ladder logic program.
Networks
A network is a diagrammatic representation of control logic similar to a wiring schematic, showing
interconnection of relays, timers, contacts and other control elements.
Power Rail
START
MOTOR
Neutral Rail
STOP
Ladder
Function
Element
MOTOR
Ladder Rung
Element Tag
Name
Figure 2: A Ladder Network
Networks in the TelePACE Ladder Editor contain up to eight rungs. Each rung can contain a
maximum of 10 logic elements. The highlighted cursor in the Ladder Editor pane occupies one logic
element position.
The number of networks in a program is only limited by the memory available.
2.4.2
Network Elements
Network elements are contacts, coils, and function blocks. Shunts are used to interconnect elements.
Coils are always found connected to the neutral rail and represent either physical outputs in the
controller or internal (memory only) outputs in the I/O database. Contacts represent physical status
inputs from the controller or internal (memory only) status inputs in the I/O database. Function
blocks are used to perform specific functions, such as moving data, manipulating data or
communicating data.
2.4.3
Subroutines
Subroutines permit conditional execution of parts of a Ladder Logic program. Subroutines can be
used to reduce the scan time of a program by only scanning code when it is absolutely needed.
Reduced scan time will increase the frequency of program execution.
Subroutines can also reduce the size of the program by placing frequently used or repeated code into
subroutines that are called from various locations in the main program.
The Ladder Logic program consists of the main program followed by a number of subroutines.
TelePACE Ladder Logic Overview
May 8, 2007
9
The main program is defined as all the logic networks up to the start of the first subroutine, or until
the end of the program if no subroutines exist.
A subroutine is defined as all the logic networks from a subroutine element until the next subroutine
element, or the end of the program if there are no more subroutines.
The program is executed from the start of the main program to the end of the main program. If a
subroutine call function block is encountered, execution transfers to the start of the subroutine and
continues until the end of the subroutine. Execution then returns to the element after the subroutine
call element.
Subroutine execution can be nested. This allows subroutines to call other subroutines.
Subroutine execution cannot be recursive. This prevents potential infinite loops in the ladder logic
program.
Two elements control the definition and execution of subroutines. The SUBR element defines the
start of a subroutine. The CALL element executes a subroutine.
2.4.4
Program Execution Order
The controller evaluates each element, or function block, in the network in a sequence that starts at
the top left hand corner; or ROW 1, COLUMN 1.
The ladder evaluation moves down column 1 until it reaches row 8. The evaluation then continues at
the top of column 2 and moves down to row 8 again.
This process continues until the entire network has been evaluated. If there is more than one
network, evaluation continues to the next sequential network in the program until the entire program
has been evaluated.
Col Col Col Col Col Col Col Col Col Col
9 10
6
5
8
7
4
3
2
1
Row1
Row2
Row3
Row4
Row5
Row6
Row7
Row8
Figure 3: TelePACE Ladder Editor Network Execution
2.4.5
Ladder Logic Memory Usage
Memory usage in a Ladder Logic application program is based on the number of networks and
number of elements used by a program.
Networks
Columns
Each network in an application requires one word of memory, whether the
network is used or not.
Each column that is occupied in a network requires one word of memory.
TelePACE Ladder Logic Overview
May 8, 2007
10
Single Elements
Double Elements
Triple Elements
Each single element requires one word of memory.
Each double element requires two words of memory.
Each triple element requires three words of memory.
Two words of
memory are
required for each
double element.
Three words of
memory are
required for each
triple element.
One word of
memory is
required for each
single element.
One word of memory is
required for each network.
One word of
memory is
required for each
column.
Figure 4: Ladder Logic Memory Usage
2.5
TelePACE I/O Database Registers
The I/O Database is different on the 16 and 32-bt controllers.
The 16-bit controllers comprise of SCADAPack (Light and Plus), SCADAPack 100, SCADAPack
LP, SCADASense 4202 DR and SCADASense 4202 DS. The SCADAPack 100: 1024K controller
differs from the SCADAPack 100: 256 K controller in that it has the same I/O database as other
SCADAPack controllers. The SCADAPack 100: 1024K controller has firmware version 1.80 or
newer and a controller ID that is greater than or equal to A182922.
The 32-bit controllers comprise SCADAPack 350, SCADAPack 32, SCADASense 4203 DR and
SCADASense 4203 DS.
Note:
2.5.1
In this manual, the SCADASense 4202 DR and DS controllers are collectively referred to as
the SCADASense 4202 Series controller. The SCADASense 4203 DR and DS are
collectively referred to as the SCADASense 4203 Series controllers. The 4202 and 4203
controllers are collectively referred to as the SCADASense controllers.
16-bit Controller I/O Database
The 16-bit controllers which comprise of SCADAPack (Light and Plus), SCADAPack 100:1024K,
SCADAPack LP, and SCADASense 4202 Series controllers all have the same IO database. The IO
database in the SCADAPack 100: 256K is different as indicated in section 2.5.3-SCADAPack 100:
256K I/O Database.
The I/O database allows data to be shared between C programs, Ladder Logic programs and
communication protocols. A simplified diagram of the I/O Database is shown in Figure 5:
TelePACE Ladder Logic Overview
May 8, 2007
11
SCADAPack, SCADAPack 100: 1024K, SCADAPack LP, SCADASense 4202 Series I/O
Database Block Diagram.
The I/O database contains general purpose and user-assigned registers. Ladder Logic and C
application programs to store processed information and to receive information from a remote device
may use general-purpose registers. Initially all registers in the I/O Database are general-purpose
registers.
User-assigned registers are mapped directly from the I/O database to physical I/O hardware, or to
controller system configuration and diagnostic parameters. The Register Assignment performs the
mapping of registers from the I/O database to physical I/O hardware and system parameters.
Ladder
Logic
Programs
C Tools
Programs
TeleBUS
Protocols
Controller I/O
Database
Coil Registers
00001 to 04096
Status Registers
10001 to 14096
Input Registers
30001 to 31024
Holding Registers
40001 to 49999
Controller
Register
Assignment Table
5000 Series
I/O Modules
System
Parameters
Figure 5: SCADAPack, SCADAPack 100: 1024K, SCADAPack LP, SCADASense 4202 Series
I/O Database Block Diagram
User-assigned registers are initialized to the default hardware state or system parameter when the
controller is reset. Assigned output registers do not maintain their values during power failures.
Assigned output registers do retain their values during application program loading.
General-purpose registers retain their values during power failures and application program loading.
The values change only when written by an application program or a communication protocol.
The TeleBUS communication protocols provide a standard communication interface to the
controller. The TeleBUS protocols are compatible with the widely used Modbus RTU and ASCII
protocols. They provide full access to the I/O database in the controller.
2.5.1.1
I/O Database register types
The I/O database is divided into four types of I/O registers. Each of these types is initially
configured as general purpose registers by the controller.
2.5.1.1.1
Coil Registers
Coil registers are single bit registers located in the digital output section of the I/O database. Coil, or
digital output, database registers may be assigned to 5000 Series digital output modules or
SCADAPack I/O modules through the Register Assignment. Coil registers may also be assigned to
controller on board digital outputs and to system configuration modules.
There are 4096 coil registers numbered 00001 to 04096. Ladder logic programs, C language
programs, and the TeleBUS protocols can read from and write to these registers.
TelePACE Ladder Logic Overview
May 8, 2007
12
2.5.1.1.2
Status Registers
Status registers are single bit registers located in the digital input section of the I/O database. Status,
or digital input, database registers may be assigned to 5000 Series digital input modules or
SCADAPack I/O modules through the Register Assignment. Status registers may also be assigned to
controller on board digital inputs and to system diagnostic modules.
There are 4096 status registers numbered 10001 to 14096. Ladder logic programs and the TeleBUS
protocols can only read from these registers. C language programs can read data from and write data
to these registers.
2.5.1.1.3
Input Registers
Input registers are 16 bit registers located in the analog input section of the I/O database. Input
database registers may be assigned to 5000 Series analog input modules or SCADAPack I/O
modules through the Register Assignment. Input registers may also be assigned to controller internal
analog inputs and to system diagnostic modules.
There are 1024 input registers numbered 30001 to 31024. Ladder logic programs and the TeleBUS
protocols can only read from these registers. C language programs can read data from and write data
to these registers.
2.5.1.1.4
Holding Registers
Holding registers are 16 bit registers located in the analog output section of the I/O database.
Holding, or analog output, database registers may be assigned to 5000 Series analog output modules
or SCADAPack analog output modules through the Register Assignment. Holding registers may
also be assigned to system diagnostic and configuration modules.
There are 9999 holding registers numbered 40001 to 49999. Ladder logic programs, C language
programs, and the TeleBUS protocols can read from and write to these registers.
2.5.2
32-bit Controller I/O Database
The 32-bit controllers, which comprise of SCADAPack32, SCADAPack 350, SCADASense 4203
Series (SCADASense 4203 DR and SCADASense 4203 DS) , all have the same IO database.
The I/O database allows data to be shared between C programs, Ladder Logic programs and
communication protocols. A simplified diagram of the I/O Database is shown in Figure 6:
SCADASense 4203 Series, SCADAPack 350 and SCADAPack 32 I/O Database Block Diagram.
The I/O database contains general purpose and user-assigned registers. Ladder Logic and C
application programs to store processed information and to receive information from a remote device
may use general-purpose registers. Initially all registers in the I/O Database are general-purpose
registers.
User-assigned registers are mapped directly from the I/O database to physical I/O hardware, or to
controller system configuration and diagnostic parameters. The Register Assignment performs the
mapping of registers from the I/O database to physical I/O hardware and system parameters.
TelePACE Ladder Logic Overview
May 8, 2007
13
Ladder
Logic
Programs
C Tools
Programs
TeleBUS
Protocols
Controller I/O
Database
Coil Registers
00001 to 04096
Status Registers
10001 to 14096
Input Registers
30001 to 39999
Holding Registers
40001 to 49999
Controller
Register
Assignment Table
5000 Series
I/O Modules
System
Parameters
Figure 6: SCADASense 4203 Series, SCADAPack 350 and SCADAPack 32 I/O Database Block
Diagram
User-assigned registers are initialized to the default hardware state or system parameter when the
controller is reset. Assigned output registers do not maintain their values during power failures.
Assigned output registers do retain their values during application program loading.
General-purpose registers retain their values during power failures and application program loading.
The values change only when written by an application program or a communication protocol.
The TeleBUS communication protocols provide a standard communication interface to the
controller. The TeleBUS protocols are compatible with the widely used Modbus RTU and ASCII
protocols. They provide full access to the I/O database in the controller.
2.5.2.1
I/O Database register types
The I/O database is divided into four types of I/O registers. Each of these types is initially
configured as general purpose registers by the controller.
2.5.2.1.1
Coil Registers
Coil registers are single bit registers located in the digital output section of the I/O database. Coil, or
digital output, database registers may be assigned to 5000 Series digital output modules or
SCADAPack I/O modules through the Register Assignment. Coil registers may also be assigned to
controller on board digital outputs and to system configuration modules.
There are 4096 coil registers numbered 00001 to 04096. Ladder logic programs, C language
programs, and the TeleBUS protocols can read from and write to these registers.
2.5.2.1.2
Status Registers
Status registers are single bit registers located in the digital input section of the I/O database. Status,
or digital input, database registers may be assigned to 5000 Series digital input modules or
SCADAPack I/O modules through the Register Assignment. Status registers may also be assigned to
controller on board digital inputs and to system diagnostic modules.
There are 4096 status registers numbered 10001 to 14096. Ladder logic programs and the TeleBUS
protocols can only read from these registers. C language programs can read data from and write data
to these registers.
TelePACE Ladder Logic Overview
May 8, 2007
14
2.5.2.1.3
Input Registers
Input registers are 16 bit registers located in the analog input section of the I/O database. Input
database registers may be assigned to 5000 Series analog input modules or SCADAPack I/O
modules through the Register Assignment. Input registers may also be assigned to controller internal
analog inputs and to system diagnostic modules.
There are 9999 input registers numbered 30001 to 39999. Ladder logic programs and the TeleBUS
protocols can only read from these registers. C language programs can read data from and write data
to these registers.
2.5.2.1.4
Holding Registers
Holding registers are 16 bit registers located in the analog output section of the I/O database.
Holding, or analog output, database registers may be assigned to 5000 Series analog output modules
or SCADAPack analog output modules through the Register Assignment. Holding registers may
also be assigned to system diagnostic and configuration modules.
There are 9999 holding registers numbered 40001 to 49999. Ladder logic programs, C language
programs, and the TeleBUS protocols can read from and write to these registers.
2.5.3
SCADAPack 100: 256K I/O Database
The SCADAPack 100: 256K controller differs from the SCADAPack 100: 1024K controller in that
it has a limited I/O database. The SCADAPack 100: 256K controller has firmware version older
than 1.80 and a controller ID that is less or equal to A182921.
The SCADAPack 100: 256K I/O database allows data to be shared between C programs, Ladder
Logic programs and communication protocols. A simplified diagram of the I/O Database is shown
in Figure 7: SCADAPack 100 – 256K I/O Database Block Diagram.
The I/O database contains general purpose and user-assigned registers. Ladder Logic and C
application programs to store processed information and to receive information from a remote device
may use general-purpose registers. Initially all registers in the I/O Database are general-purpose
registers.
User-assigned registers are mapped directly from the I/O database to physical I/O hardware, or to
controller system configuration and diagnostic parameters. The Register Assignment performs the
mapping of registers from the I/O database to physical I/O hardware and system parameters.
Ladder
Logic
Programs
C Tools
Programs
TeleBUS
Protocols
Controller I/O
Database
Coil Registers
00001 to 04096
Status Registers
10001 to 14096
Input Registers
30001 to 30512
Holding Registers
40001 to 44000
Controller
Register
Assignment Table
5000 Series
I/O Modules
System
Parameters
Figure 7: SCADAPack 100 – 256K I/O Database Block Diagram
TelePACE Ladder Logic Overview
May 8, 2007
15
User-assigned registers are initialized to the default hardware state or system parameter when the
controller is reset. Assigned output registers do not maintain their values during power failures.
Assigned output registers do retain their values during application program loading.
General-purpose registers retain their values during power failures and application program loading.
The values change only when written by an application program or a communication protocol.
The TeleBUS communication protocols provide a standard communication interface to the
controller. The TeleBUS protocols are compatible with the widely used Modbus RTU and ASCII
protocols. They provide full access to the I/O database in the controller.
2.5.3.1
I/O Database register types
The I/O database is divided into four types of I/O registers. Each of these types is initially
configured as general purpose registers by the controller.
2.5.3.1.1
Coil Registers
Coil registers are single bit registers located in the digital output section of the I/O database. Coil, or
digital output, database registers may be assigned to 5000 Series digital output modules or
SCADAPack I/O modules through the Register Assignment. Coil registers may also be assigned to
controller on board digital outputs and to system configuration modules.
There are 4096 coil registers numbered 00001 to 04096. Ladder logic programs, C language
programs, and the TeleBUS protocols can read from and write to these registers.
2.5.3.1.2
Status Registers
Status registers are single bit registers located in the digital input section of the I/O database. Status,
or digital input, database registers may be assigned to 5000 Series digital input modules or
SCADAPack I/O modules through the Register Assignment. Status registers may also be assigned to
controller on board digital inputs and to system diagnostic modules.
There are 4096 status registers numbered 10001 to 14096. Ladder logic programs and the TeleBUS
protocols can only read from these registers. C language programs can read data from and write data
to these registers.
2.5.3.1.3
Input Registers
Input registers are 16 bit registers located in the analog input section of the I/O database. Input
database registers may be assigned to 5000 Series analog input modules or SCADAPack I/O
modules through the Register Assignment. Input registers may also be assigned to controller internal
analog inputs and to system diagnostic modules.
The I/O database for the SCADAPack 100: 256K controller has 512 input registers numbered 30001
to 30512. Ladder logic programs and the TeleBUS protocols can only read from these registers. C
language programs can read data from and write data to these registers.
2.5.3.1.4
Holding Registers
Holding registers are 16 bit registers located in the analog output section of the I/O database.
Holding, or analog output, database registers may be assigned to 5000 Series analog output modules
or SCADAPack analog output modules through the Register Assignment. Holding registers may
also be assigned to system diagnostic and configuration modules.
The I/O database for the SCADAPack 100: 1924K controller has 4000 holding registers numbered
40001 to 44000. Ladder logic programs, C language programs, and the TeleBUS protocols can read
from and write to these registers.
TelePACE Ladder Logic Overview
May 8, 2007
16
TelePACE Ladder Logic
Program Development
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE,
TeleSAFE Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus,
SCADAPack 32, SCADAPack 32P, SCADAPack 350, SCADAPack LP,
SCADAPack 100, SCADASense 4202 DS, SCADASense 4202 DR,
SCADASense 4203 DS, SCADASense 4203 DR, SCADASense 4102,
SCADASense 4012, SCADASense 4032 and TeleBUS are registered
trademarks of Control Microsystems.
All other product names are copyright and registered trademarks or trade names
of their respective owners.
Material used in the User and Reference manual section titled SCADAServer
OLE Automation Reference is distributed under license from the OPC
Foundation.
TelePACE Ladder Logic Program Development
May 8, 2007
1
Table of Contents
1
TELEPACE PROGRAM DEVELOPMENT .................................................... 3
1.1
Introduction .................................................................................................... 3
1.2
Configuration of the TelePACE Program ....................................................... 3
1.2.1
PC Communication Settings ..................................................................... 3
1.2.2
Options ..................................................................................................... 3
1.3
Initializing the Controller ................................................................................. 4
1.4
Define Register Assignment........................................................................... 4
1.5
Create Ladder Logic Program ........................................................................ 4
1.5.1
Inserting Elements .................................................................................... 4
1.5.2
Inserting Networks .................................................................................... 5
1.5.3
Editing Elements....................................................................................... 5
1.5.4
Deleting Elements..................................................................................... 5
1.5.5
Selecting Elements ................................................................................... 5
1.6
Setting Outputs On Stop ................................................................................ 5
1.7
Controller Serial Port Settings ........................................................................ 6
1.8
Write program to controller............................................................................. 6
1.9
Monitor Program On Line............................................................................... 6
1.9.1
Contact Monitoring.................................................................................... 6
1.10
Edit Program On Line..................................................................................... 7
1.11
Force Registers.............................................................................................. 7
1.12
Preventing Unauthorized Changes ................................................................ 7
TelePACE Ladder Logic Program Development
May 8, 2007
2
1
TelePACE Program Development
1.1
Introduction
A Ladder Logic program may be developed in any sequence. Best results, particularly for new users,
will be obtained using the following sequence:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Configure TelePACE.
Create the ladder program.
Create the Register Assignment.
Select Outputs-On-Stop settings.
Define serial port settings.
Create Ladder Logic Program.
Initialize controller.
Write program to the controller.
Run and test program.
These steps are described in more detail in the sections that follow.
1.2
Configuration of the TelePACE Program
The configuration of the TelePACE program involves setting the serial port parameters for the target
controller and selecting options to customize the Ladder Editor environment.
1.2.1
PC Communication Settings
Configure TelePACE communications to satisfy the requirements of the communication media
between the TelePACE program and the target controller. Refer to the PC Communication
Settings in the TelePACE Program Reference.
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers, com3 is supported only
when the SCADAPack 5601 or 5604 I/O module is installed. Com4 is supported only when the
SCADAPack 5602 I/O module is installed. To optimize performance, minimize the length of
messages on com3 and com4. Examples of recommended uses for com3 and com4 are for local
operator terminals, and for programming and diagnostics using the TelePACE program.
1.2.2
Options
Set the Ladder Editor environment options to suit the display resolution and color capability of your
computer. From the Options menu select Screen Font to change the Editor screen font and Colors
to change the Ladder Logic display color.
The format of floating point numbers may be changed using the Floating-Point Settings option.
The Tool Bar, Title Bar and the Status Bar may be removed from the Editor Display by selecting
or de-selecting the option in the Option menu.
Select tag names display options to meet your personal preference. The selections are Single Tag
Names, Double Tag Names, Tag and Address and Numeric Address.
In most cases it is recommended that the Allow Multiple Coils and Warning Messages be selected.
TelePACE Ladder Logic Program Development
May 8, 2007
3
1.3
Initializing the Controller
The controller should be initialized before a new program is loaded into the controller. The
Initialize Controller dialog appears when Initialize is selected in the Controller menu. Ladder
Logic programs C programs and the Register Assignment may be erased from this dialog.
WARNING:
•
•
•
•
•
•
•
•
•
•
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller. Element Configuration
may be used for the following functions:
DIAL – Control Dial-Up Modem;
INIM – Initialize Dial-Up Modem;
MSTR – Master Message;
SLP – Put Controller into Sleep Mode;
HART – Protocol Driver;
DLOG – Data Logger;
FLOW – Flow Accumulation;
TOTL – Flow Totalizer;
PIDA – PID controller for analog output; and
PIDD – PID controller for digital output.
Refer to the Ladder Logic Function Reference for a description of these functions.
1.4
Define Register Assignment
All I/O hardware that is used by the controller must be assigned to I/O database registers in order for
the I/O points to be used by the ladder program. Ladder logic programs may read data from, or write
data to, the I/O hardware through user-assigned registers in the I/O database.
The Register Assignment assigns I/O database registers to user-assigned registers using I/O modules.
An I/O Module can refer to an actual I/O hardware module (e.g. 5401 Digital Input Module) or it
may refer to a set of controller parameters, such as serial port settings.
The Register Assignment Reference section describes the purpose of each module and the register
assignment requirements for the module.
Register assignments are stored in the user configured Register Assignment and are downloaded with
the ladder logic application program.
1.5
1.5.1
Create Ladder Logic Program
Inserting Elements
To insert an element in the Ladder network, position the cursor at the network position where the
element is to be inserted. Double click the left mouse button. The Insert/Edit Network Element
dialog box pops up and an element or function can be selected to insert.
The Insert/Edit Network Element dialog box only displays the elements and functions that will fit
from the cursor position.
Elements can be inserted using the right mouse button and selecting Edit Element from the drop
down menu.
Elements can be inserted from the keyboard by positioning the cursor at the desired network position
and pressing the Insert key.
TelePACE Ladder Logic Program Development
May 8, 2007
4
1.5.2
Inserting Networks
To insert another network, select Insert from the Edit menu. The Insert dialog pops up. Selections
are made in this dialog by moving the mouse pointer to the required radio button and clicking the left
mouse button. Networks may be inserted before or after the current network.
1.5.3
Editing Elements
To edit an element in the Ladder network, position the cursor on the element to be edited. Double
click the left mouse button. The Insert/Edit Network Element dialog box pops up and the element
can be edited.
Elements can be edited using the right mouse button and selecting Edit Element from the drop down
menu.
Elements can be edited from the keyboard by positioning the cursor at the desired element the
pressing the Insert key.
1.5.4
Deleting Elements
To remove an element from a network, press the Delete key, or select Delete from the Edit menu.
The element at the cursor position or selected elements, columns, rows or networks can be selected
for deleting.
Selected elements can be deleted using the right mouse button and selecting Delete from the drop
down menu.
1.5.5
Selecting Elements
To select multiple elements position the cursor on the first element or function of the selection and
press the left mouse button. Hold the button down and drag the pointer to the last element or
function. The elements selected will be highlighted in the same way as the cursor. Releasing the
mouse button does not change the highlighting.
Individual disconnected elements may also be selected and copied to the clipboard. To select
disconnected elements position the cursor on the first element. Hold the keyboard shift key down.
Using the left mouse button, click on elements to be copied to the clipboard.
To select elements or functions with the keyboard move the cursor to the first element or function.
Hold the shift key down while using the directional arrow keys to move the cursor to the last element
or function. The selected elements are highlighted.
1.6
Setting Outputs On Stop
Select Outputs on Stop from the Controller menu and the Output Conditions on Program Stop
dialog appears. This dialog controls the state of the controller analog and digital outputs when the
ladder logic program is stopped.
The state of the digital outputs may be set to hold their last value or to turn off when the ladder
program is stopped.
The state of the analog outputs may be set to hold their last value or to go to Zero when the ladder
program is stopped.
TelePACE Ladder Logic Program Development
May 8, 2007
5
1.7
Controller Serial Port Settings
Select the Serial Ports command from the Controller menu to configure the controller serial ports.
The Controller Serial Ports Settings dialog box pops up when the Serial Ports command is
selected.
For SCADAPack, SCADAPack Light, and SCADAPack Plus controllers, Com3 is supported only
when the SCADAPack 5601 or 5604 I/O module is installed. Com4 is supported only when the
SCADAPack 5602 I/O module is installed. To optimize performance, minimize the length of
messages on com3 and com4. Examples of recommended uses for com3 and com4 are for local
operator terminals, and for programming and diagnostics using the TelePACE program.
1.8
Write program to controller
The Write to Controller command in the Communications menu writes the Ladder Logic program
to the controller. The program replaces the program in the controller.
If the program in the controller is executing a dialog box will request whether to stop execution of
the new program when the write is complete or to continue execution of the new program after the
write is complete.
WARNING:
1.9
Exercise caution when selecting the Continue option. The program will execute
with the changes you make, even if the changes are not complete. This may cause
undesired operation. Select Stop if you are making multiple changes.
Monitor Program On Line
The Monitor On Line selection in the Activity menu enables the real time monitoring of a program
executing in a controller. The editor shows the power flow through the network on the screen. No
changes can be made to the program in monitor mode. The Register Editor window is displayed
when Monitor On Line is selected.
1.9.1
Contact Monitoring
It is often necessary, while in Monitor On line mode, to determine whether a contact would pass
power if power were supplied to it. This feature is extremely useful when testing the operation of
ladder logic programs.
In Monitor On line mode, TelePACE shows the power flow through the network. It also colors
contacts that are not powered to show how power would flow if they were.
TelePACE Ladder Logic Program Development
May 8, 2007
6
The following diagram illustrates how power flow information is displayed in Monitor On line
mode:
10001 10002
00003
In the above example, normally open contact 10001 and normally closed contact 10002, are not
energized. The shaded background, in contact 10002, indicates power would flow through the
contact if the input side were powered.
•
The background of a normally open contact is colored when it is energized and its input
is not powered.
•
The background of a normally closed contact is colored when it is not energized and its
input is not powered.
The background is only displayed on contacts if the input side of the contact is not powered.
The color used for contact monitoring can be changed using the Colors command.
1.10
Edit Program On Line
The Edit On Line selection in the Activity menu is used to edit a ladder logic program that is
executing in the controller. All editing commands affect the program in the controller and the
program in the TelePACE Ladder Network Editor.
1.11
Force Registers
The Register Editor dialog allows the user to modify registers in the memory of the controller. This
dialog is only available in the on-line mode. Data modified by the dialog is stored only in the
memory of the controller. It does not form part of the ladder logic program. Refer to the Program
Reference section for detailed information on the Register Editor.
1.12
Preventing Unauthorized Changes
A TeleSAFE Micro16 or SCADAPack controller can be locked to prevent unauthorized changes. A
password is required to unlock the controller to make changes.
The controller will reject commands sent to the unit when it is locked. A controller that is unlocked
operates without restriction. Three levels of locks are provided.
•
Locking the programming commands prevents modifying or viewing the program in the
controller. Communication protocols can read and write the I/O database.
•
Locking programming and database write a command prevent modifying or viewing the
program; and prevents writing to the I/O database. Communication protocols can read
data from the I/O database, but cannot modify any data.
•
Locking programming and database commands prevents modifying or viewing the
program and prevents reading and writing the I/O database. Communication protocols
cannot read or write the I/O database.
Refer to the sections Lock Controller, Unlock Controller, Override Controller Lock and Show Lock
Status for details on using this feature.
TelePACE Ladder Logic Program Development
May 8, 2007
7
TelePACE Ladder Logic
Program Reference
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE,
TeleSAFE Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus,
SCADAPack 32, SCADAPack 32P, SCADAPack 350, SCADAPack LP,
SCADAPack 100, SCADASense 4202 DS, SCADASense 4202 DR,
SCADASense 4203 DS, SCADASense 4203 DR, SCADASense 4102,
SCADASense 4012, SCADASense 4032 and TeleBUS are registered
trademarks of Control Microsystems.
All other product names are copyright and registered trademarks or trade names
of their respective owners.
Material used in the User and Reference manual section titled SCADAServer
OLE Automation Reference is distributed under license from the OPC
Foundation.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
1
Table of Contents
1
INTRODUCTION.......................................................................................... 11
2
FILE MENU.................................................................................................. 12
2.1
New.............................................................................................................. 12
2.2
Open ............................................................................................................ 12
2.3
Save............................................................................................................. 12
2.4
Save As........................................................................................................ 12
2.5
Page Setup .................................................................................................. 12
2.6
Print.............................................................................................................. 13
2.7
Select Print Items ......................................................................................... 13
2.8
Quick File List............................................................................................... 14
2.9
Exit ............................................................................................................... 14
3
EDIT MENU ................................................................................................. 15
3.1
Undo ............................................................................................................ 15
3.2
Cut Selected................................................................................................. 15
3.3
Copy Selected.............................................................................................. 15
3.4
Copy Networks............................................................................................. 15
3.5
Cut Networks................................................................................................ 15
3.6
Paste............................................................................................................ 15
3.7
Insert ............................................................................................................ 16
3.7.1
Insert Vertical Shunt ............................................................................... 16
3.7.2
Insert Element......................................................................................... 16
3.7.3
Address Types........................................................................................ 18
3.7.4
Empty Column ........................................................................................ 18
3.7.5
Empty Row ............................................................................................. 18
3.7.6
Network Before ....................................................................................... 18
3.7.7
Network After .......................................................................................... 18
3.8
Delete........................................................................................................... 18
3.8.1
Vertical Shunt ......................................................................................... 19
3.8.2
Element .................................................................................................. 19
3.8.3
Selected Elements.................................................................................. 19
3.8.4
Empty Column ........................................................................................ 19
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
2
3.8.5
3.8.6
3.8.7
Empty Row ............................................................................................. 19
Network .................................................................................................. 19
Delete All Networks ................................................................................ 19
3.9
Toggle Vertical Shunt................................................................................... 20
3.10
Tag Names .................................................................................................. 20
3.11
Erase All Tags.............................................................................................. 21
3.12
Export Tag Names ....................................................................................... 21
3.13
Import Tag Names ....................................................................................... 21
3.14
Network Title ................................................................................................ 22
3.15
Element Configuration.................................................................................. 22
3.16 Registers ...................................................................................................... 22
3.16.1
Register Editor ........................................................................................ 23
3.16.1.1........................................................................................................................ Groups
3.16.1.2............................................................................................................... Update Rate
3.16.1.3............................................................................................................... Register List
3.16.2
Add Registers Dialog .............................................................................. 25
3.16.2.1........................................................................................................ Registers In Use
3.16.2.2..........................................................................................................................Range
3.16.2.3.............................................................................................................................Tags
3.16.3
Edit Register Dialog ................................................................................ 28
3.16.4
Register Data File ................................................................................... 30
3.16.4.1........................................................................................Register Data File Format
3.16.5
Editing the Register Data File ................................................................. 31
4
SEARCH MENU .......................................................................................... 33
4.1
Next Network................................................................................................ 33
4.2
Previous Network ......................................................................................... 33
4.3
Go To Network ............................................................................................. 33
4.4
Find Address ................................................................................................ 33
4.5
Find Device .................................................................................................. 34
4.6
Find Tag Name ............................................................................................ 34
4.7
Repeat Last Find.......................................................................................... 35
4.8
Replace Address.......................................................................................... 35
4.9
Multiple Coils................................................................................................ 36
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
3
23
24
24
27
27
27
30
5
CONTROLLER MENU................................................................................. 37
5.1
Type ............................................................................................................. 37
5.2
Serial Ports .................................................................................................. 37
5.3
IP Configuration ........................................................................................... 49
5.3.1
LAN Port ................................................................................................. 50
5.3.2
com1 Port ............................................................................................... 51
5.3.3
com2 Port ............................................................................................... 53
5.3.4
com3 Port ............................................................................................... 53
5.3.5
com4 Port ............................................................................................... 53
5.3.6
PPP Login............................................................................................... 53
5.3.6.1 ........................................................................................ Add PPP Username dialog
5.3.6.2 ........................................................................................ Edit PPP Username dialog
5.3.7
Modbus Common ................................................................................... 55
5.3.8
Modbus/TCP........................................................................................... 57
5.3.9
Modbus RTU in UDP .............................................................................. 58
5.3.10
Modbus ASCII in UDP ............................................................................ 58
5.3.11
DNP in TCP ............................................................................................ 59
5.3.12
DNP in UDP............................................................................................ 61
5.3.13
Friendly IP List ........................................................................................ 61
5.3.13.1................................................................. Add Friendly IP Address Range Dialog
54
55
63
5.4
Register Assignment .................................................................................... 63
5.4.1
Edit Register Assignment Dialog ............................................................ 66
5.5
Outputs On Stop .......................................................................................... 67
5.6
Store and Forward ....................................................................................... 68
5.6.1
Add/Edit Store and Forward Dialog ........................................................ 70
5.7
DNP ............................................................................................................. 71
5.8
DNP Status .................................................................................................. 71
5.9
DNP Master Status ...................................................................................... 71
5.10 Initialize ........................................................................................................ 71
5.10.1
SCADAPack and SCADAPack 32 Controllers ........................................ 72
5.10.2
SCADAPack 350 and SCADASense 4203 Series of Controllers............ 73
5.10.2.1..................................................Actions Performed when Controller is Initialized
5.11
Real Time Clock........................................................................................... 75
5.12
Monitor Element ........................................................................................... 76
5.13
List Force Registers ..................................................................................... 77
5.14
Remove All Forces....................................................................................... 78
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
4
74
5.15
Lock Controller ............................................................................................. 78
5.16
Unlock Controller.......................................................................................... 79
5.17
Override Controller Lock .............................................................................. 79
5.18
Show Lock Status ........................................................................................ 80
5.19 C/C++ Program Loader................................................................................ 80
5.19.1
SCADAPack and SCADAPack 32 Controllers ........................................ 80
5.19.1.1.....................................................................................Add C/C++ Program Dialog
5.19.2
SCADAPack 350 and SCADASense 4203 Series Controllers................ 82
81
5.20 Flash Loader ................................................................................................ 83
5.20.1
Writing Programs to Flash ...................................................................... 84
5.21 Program Status ............................................................................................ 85
5.21.1
SCADAPack and SCADAPack 32 Controllers ........................................ 86
5.21.2
SCADAPack 350 and SCADASense 4203 Series of Controllers............ 87
6
COMMUNICATIONS MENU ........................................................................ 89
6.1
Read from Controller.................................................................................... 89
6.2
Write to Controller ........................................................................................ 89
6.3
PC Communications Settings....................................................................... 89
6.3.1
ClearSCADA........................................................................................... 90
6.3.1.1 ................................................................................................... General Parameters
6.3.1.2 ................................................................................................ Advanced Parameters
6.3.1.3 ................................................................................................................... Information
6.3.1.3.1 ................................................................................................................... Information
6.3.2
DNP ........................................................................................................ 93
6.3.2.1 ................................................................................................... General Parameters
6.3.2.2 ........................................................................................... Flow Control Parameters
6.3.2.2.1 ................................................................................................ RTS/CTS Flow Control
6.3.2.3 .....................................................................................................Dial Up Parameters
6.3.2.4 ................................................................................................ Advanced Parameters
6.3.2.5 ................................................................................................................... Information
6.3.3
DNP/TCP .............................................................................................. 100
6.3.3.1 ...............................................................................................................General Page
6.3.3.1.1 ....................................................................................................... IP Address / Name
6.3.3.2 ........................................................................................................... Advanced Page
6.3.3.3 ......................................................................................................... Information Page
6.3.4
DNP/UDP.............................................................................................. 104
6.3.4.1 ...............................................................................................................General Page
6.3.4.1.1 ....................................................................................................... IP Address / Name
6.3.4.2 ........................................................................................................... Advanced Page
6.3.4.3 ......................................................................................................... Information Page
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
5
90
91
92
93
93
95
96
97
98
99
101
102
102
103
105
106
106
107
6.3.5
Modbus ASCII....................................................................................... 108
6.3.5.1 ................................................................................................... General Parameters
6.3.5.2 ...........................................................Modbus ASCII Configuration (Flow Control)
6.3.5.3 .................................................................... Modbus ASCII Configuration (Dial Up)
6.3.5.4 ................................................................................................ Advanced Parameters
6.3.5.5 ................................................................................................................... Information
6.3.6
Modbus ASCII in TCP........................................................................... 115
6.3.6.1 ................................................................................................... General Parameters
6.3.6.2 ................................................................................................ Advanced Parameters
6.3.6.3 ................................................................................................................... Information
6.3.7
Modbus ASCII in UDP .......................................................................... 119
6.3.7.1 ................................................................................................... General Parameters
6.3.7.2 ................................................................................................ Advanced Parameters
6.3.7.3 ................................................................................................................... Information
6.3.8
Modbus RTU......................................................................................... 123
6.3.8.1 ...................................................................................................................Introduction
6.3.8.2 ................................................................................................... General Parameters
6.3.8.3 .............................................................Modbus RTU Configuration (Flow Control)
6.3.8.4 ...................................................................... Modbus RTU Configuration (Dial Up)
6.3.8.5 ................................................................................................ Advanced Parameters
6.3.8.6 ................................................................................................................... Information
6.3.9
Modbus RTU in TCP............................................................................. 130
6.3.9.1 ................................................................................................... General Parameters
6.3.9.2 ................................................................................................ Advanced Parameters
6.3.9.3 ................................................................................................................... Information
6.3.10
Modbus RTU in UDP ............................................................................ 134
6.3.10.1................................................................................................. General Parameters
6.3.10.2.............................................................................................. Advanced Parameters
6.3.10.3................................................................................................................. Information
6.3.11
Modbus/TCP......................................................................................... 138
6.3.11.1................................................................................................. General Parameters
6.3.11.2.............................................................................................. Advanced Parameters
6.3.11.3................................................................................................................. Information
6.3.12
Modbus/UDP ........................................................................................ 142
6.3.12.1................................................................................................. General Parameters
6.3.12.2.............................................................................................. Advanced Parameters
6.3.12.3................................................................................................................. Information
6.3.13
Modbus/USB......................................................................................... 145
6.3.13.1.............................................................................................................General Page
6.3.13.2....................................................................................................... Information Page
6.3.14
SCADAServer....................................................................................... 148
6.3.14.1................................................................................................. General Parameters
6.3.14.2.............................................................................................. Advanced Parameters
6.3.14.3................................................................................................................. Information
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
6
108
110
112
113
114
116
118
119
120
121
122
123
123
125
127
129
130
131
133
134
135
136
137
139
140
141
142
143
145
146
147
149
150
151
7
ACTIVITY MENU ....................................................................................... 152
7.1
Edit Off Line ............................................................................................... 152
7.2
Edit On Line ............................................................................................... 152
7.3
Monitor On Line.......................................................................................... 152
8
OPERATION MENU .................................................................................. 153
8.1
Stop............................................................................................................ 153
8.2
Debug ........................................................................................................ 153
8.3
Run ............................................................................................................ 153
9
OPTIONS MENU ....................................................................................... 154
9.1
Screen Font ............................................................................................... 154
9.2
Colors......................................................................................................... 154
9.3
Floating-Point Settings ............................................................................... 154
9.4
Tool Bar ..................................................................................................... 154
9.5
Title Bar...................................................................................................... 155
9.6
Status Bar .................................................................................................. 155
9.7
Single Tag Names...................................................................................... 155
9.8
Double Tag Names .................................................................................... 155
9.9
Tag and Address........................................................................................ 155
9.10
Numeric Address........................................................................................ 155
9.11
Allow Multiple Coils .................................................................................... 155
9.12
Warning Messages .................................................................................... 156
10
HELP MENU .............................................................................................. 157
10.1
Contents..................................................................................................... 157
10.2
About Program ........................................................................................... 157
Index of Figures
Figure 1:
Figure 2:
Figure 3:
Figure 4:
Figure 5:
Figure 6:
Select Print Items Dialog Box ..............................................................................13
Insert Dialog Box .................................................................................................16
Insert / Edit Network Element Dialog Box............................................................17
Delete Dialog Box ................................................................................................19
Edit Tag Names Dialog Box.................................................................................20
Erase All Tags Dialog Box ...................................................................................21
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
7
Figure 7: Register Editor Dialog Box...................................................................................23
Figure 8: New Group Dialog Box ........................................................................................24
Figure 9: Rename Group Dialog Box..................................................................................24
Figure 10: Add Registers – List Dialog Box ........................................................................26
Figure 11: Edit Register Dialog Box....................................................................................28
Figure 12: Edit Register Dialog Box- Value Off...................................................................29
Figure 13: Go To Network Dialog Box ................................................................................33
Figure 14: Find Network Address Dialog Box .....................................................................33
Figure 15: Find Network Element Dialog Box .....................................................................34
Figure 16: Find Tag Name Dialog Box................................................................................35
Figure 17: Replace Address Dialog Box .............................................................................35
Figure 18: Controller Serial Ports Settings Dialog Box .......................................................38
Figure 19: Controller IP Configuration – LAN Port Dialog Box ...........................................51
Figure 20: Controller IP Configuration – com1 Port Dialog Box..........................................52
Figure 21: Controller IP Configuration – PPP Login Dialog Box .........................................54
Figure 22: Add PPP User Name Dialog Box.......................................................................54
Figure 23: Edit PPP User Name Dialog Box.......................................................................55
Figure 24: Controller IP Configuration - Modbus Common Dialog Box ..............................56
Figure 25: Controller IP Configuration - Modbus/TCP Dialog Box......................................57
Figure 26: Controller IP Configuration Modbus RTU in UDP Dialog Box ...........................58
Figure 27: Controller IP Configuration – Modbus ASCII in UDP Dialog Box ......................59
Figure 28: Controller IP Configuration – DNP in TCP Dialog Box ......................................60
Figure 29: Controller IP Configuration – DNP in UDP Dialog Box ......................................61
Figure 30: Controller IP Configuration – Friendly IP List Dialog Box ..................................62
Figure 31: Add Friendly IP Address Range Dialog Box ......................................................63
Figure 32: Register Assignment Dialog Box .......................................................................63
Figure 33: Cancel Register Assignment Dialog Box ...........................................................64
Figure 34: Select Register Assignment Option Dialog Box.................................................65
Figure 35: Register Assignment Dialog Box .......................................................................66
Figure 36: Edit Register Assignment Dialog Box ................................................................66
Figure 37: Output Conditions on Program Stop Dialog Box ...............................................68
Figure 38: Store and Forward Command Reference..........................................................68
Figure 39: Store and Forward Dialog Box...........................................................................69
Figure 40: Add/Edit Store and Forward Dialog Box ............................................................70
Figure 41: Initialize Controller Dialog Box SCADAPack and SCADAPack 32 Controllers..72
Figure 42: Initialize Controller Dialog Box...........................................................................73
Figure 43: Initialize Dialog for SCADAPack 350 and SCADASense 4203 Series Controllers
......................................................................................................................................73
Figure 44: Real Time Clock Setting Dialog Box..................................................................75
Figure 45: Monitor Element Dialog Box ..............................................................................76
Figure 46: New Group Dialog Box ......................................................................................76
Figure 47: Forced Registers Dialog Box .............................................................................77
Figure 48: Remove All Forces Dialog Box ..........................................................................77
Figure 49: Remove All Forces Dialog Box ..........................................................................78
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
8
Figure 50: Lock Controller Dialog Box ................................................................................78
Figure 51: Unlock Controller Dialog Box.............................................................................79
Figure 52: Override Controller Lock....................................................................................80
Figure 53: C/C++ Program Loader dialog for SCADAPack Series .....................................81
Figure 54: Write C/C++ Program dialog..............................................................................81
Figure 55: C/C++ Program Loader dialog...........................................................................82
Figure 56: Flash Loader Dialog Box ...................................................................................83
Figure 57: Flash Loader Dialog Box ...................................................................................84
Figure 58: Flash Loader Dialog Box ...................................................................................84
Figure 59: Flash Loader Dialog Box ...................................................................................85
Figure 60: Program Status Dialog Box SCADAPack and SCADAPack 32 Controllers ......86
Figure 61: Program Status Dialog for SCADAPack 350 and SCADASense 4203 Series
Controllers .....................................................................................................................87
Figure 62: Communication Protocols Configuration dialog..................................................90
Figure 63: ClearSCADA Configuration (General) Dialog Box.............................................91
Figure 64: ClearSCADA Configuration (Advanced) Dialog Box..........................................92
Figure 65: ClearSCADA Configuration (Information) Dialog Box........................................93
Figure 66: DNP Configuration (General) Dialog Box ..........................................................94
Figure 67: DNP Configuration (Flow Control) Dialog Box...................................................96
Figure 68: DNP Configuration (Dial Up) Dialog Box ...........................................................97
Figure 69: DNP Configuration (Advanced) Dialog Box .......................................................99
Figure 70: DNP Configuration (Information) Dialog Box ...................................................100
Figure 71: DNP in TCP Configuration (General) Dialog Box ............................................101
Figure 72: DNP n TCP Configuration (Advanced) Dialog Box..........................................103
Figure 73: DNP in TCP Configuration (Information) Dialog Box .......................................104
Figure 74: DNP in UDP Configuration (General) Dialog Box............................................105
Figure 75: DNP in UDP Configuration (Advanced) Dialog Box.........................................106
Figure 76: DNP in UDP Configuration (Information) Dialog Box.......................................107
Figure 77: Modbus ASCII Configuration (General) Dialog Box.........................................109
Figure 78: Modbus ASCII Configuration (Flow Control)....................................................111
Figure 79: Modbus ASCII Configuration (Dial Up) ............................................................112
Figure 80: Modbus ASCII Configuration (Advanced) Dialog Box .....................................114
Figure 81: Modbus ASCII Configuration (Information) Dialog Box ...................................115
Figure 82: Modbus ASCII in TCP Configuration (General) Dialog Box.............................116
Figure 83: Modbus ASCII in TCP Configuration (Advanced) Dialog Box .........................118
Figure 84: Modbus ASCII in TCP Configuration (Information) Dialog Box .......................119
Figure 85: Modbus ASCII in UDP Configuration (General) Dialog Box ............................120
Figure 86: Modbus ASCII in UDP Configuration (Advanced) Dialog Box .........................121
Figure 87: Modbus ASCII in UDP Configuration (Information) Dialog Box .......................122
Figure 88: Modbus RTU Configuration (General) Dialog Box...........................................124
Figure 89: Modbus RTU Configuration (Flow Control)......................................................126
Figure 90: Modbus RTU Configuration (Dial Up) ..............................................................127
Figure 91: Modbus RTU Configuration (Advanced) Dialog Box .......................................129
Figure 92: Modbus RTU Configuration (Information) Dialog Box .....................................130
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
9
Figure 93: Modbus RTU in TCP Configuration (General) Dialog Box...............................131
Figure 94: Modbus RTU in TCP Configuration (Advanced) Dialog Box ...........................133
Figure 95: Modbus RTU in TCP Configuration (Information) Dialog Box .........................134
Figure 96: Modbus RTU in UDP Configuration (General) Dialog Box ..............................135
Figure 97: Modbus RTU in UDP Configuration (Advanced) Dialog Box ...........................136
Figure 98: Modbus RTU in UDP Configuration (Information) Dialog Box .........................137
Figure 99: Modbus/TCP Configuration (General) Dialog Box...........................................139
Figure 100: Modbus/TCP Configuration (Advanced) Dialog Box......................................140
Figure 101: Modbus/TCP Configuration (Information) Dialog Box....................................141
Figure 102: Modbus/UDP Configuration (General) Dialog Box ........................................142
Figure 103: Modbus/UDP Configuration (Advanced) Dialog Box .....................................144
Figure 104: Modbus/UDP Configuration (Information) Dialog Box ...................................145
Figure 105: Modbus/USB Configuration (General) Dialog Box.........................................146
Figure 106: Multiple Controller USB Error Dialog .............................................................147
Figure 107: Selecting a USB controller from list ...............................................................147
Figure 108: Modbus/USB Configuration (Information) Dialog Box ...................................148
Figure 109: SCADAServer Configuration (General) Dialog Box.......................................149
Figure 110: SCADAServer Configuration (Advanced) Dialog Box....................................150
Figure 111: SCADAServer Configuration (Information) Dialog Box..................................151
Index of Tables
Table 1: Address Types ......................................................................................................18
Table 2: Register Formats ..................................................................................................25
Table 3: Register Display Properties ..................................................................................26
Table 4: Register Formats ..................................................................................................29
Table 5: Insert Table Caption Here......................................................................................31
Table 6: Controller Port Settings.........................................................................................39
Table 7: Valid Protocols ......................................................................................................40
Table 8: Valid Addressing Modes .......................................................................................40
Table 9: Valid Addresses ....................................................................................................40
Table 10: Duplex Settings...................................................................................................41
Table 11: Baud Rates .........................................................................................................42
Table 12: Parity Settings.....................................................................................................43
Table 13: RX Flow Settings ................................................................................................45
Table 14: TX Flow Settings.................................................................................................46
Table 15: Com Port Type Settings I....................................................................................48
Table 16: Com Port Type Settings II..................................... Error! Bookmark not defined.
Table 17: Com Port Type Settings III.................................... Error! Bookmark not defined.
Table 18: Com Port Type Settings IV ................................... Error! Bookmark not defined.
Table 19: Enron Modbus Settings.......................................................................................49
Table 20: Enron Modbus Station Settings ..........................................................................49
Table 21: Program Status Settings .....................................................................................87
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
10
1
Introduction
The TelePACE program is a powerful programming and monitoring tool that enables the user to
create, edit, document and save Ladder Logic programs for the controller. TelePACE also loads and
runs C programs in the controller. Ladder Logic programs can be written to a controller or read from
a controller using the TelePACE Ladder Logic Editor. The on-line monitoring and editing features
enable efficient debugging of program and control problems.
The TelePACE program can be used locally – connected directly to the controller – or remotely –
connected to the controller through a communication network or dial up modem. TelePACE supports
connections to remote controllers using SCADAServer and Modbus\IP. All features of TelePACE
are available locally and remotely.
This section of the manual describes each of the TelePACE program commands available from the
TelePACE menu bar. The user is encouraged to read through the following sections to gain an
understanding of the many programming and monitoring features available.
The menu bar selections and the functions available for each selection are described in the following
sections.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
11
2
File Menu
The File menu contains commands to create, open and save Ladder Logic files; utility commands to
import and export tag names; and commands to configure printer options and print Ladder Logic
programs.
2.1
New
The New command starts a new TelePACE Ladder Logic program. The comment editor window and
the ladder editor window are cleared and the network display shows network one of one. The
TelePACE Ladder Network Editor retains all information from the previous editor settings with the
exception that the I/O Assignments are defaulted to inputs for all channels.
If the current file has not been saved, the editor warns you to save the current file. You may save the
changes, discard the changes or cancel the New command.
2.2
Open
The Open command loads a ladder logic program from disk into the editor. The file replaces the
existing file in the editor. If the current file has not been saved, the editor warns you to save the
current file. You may save the changes, discard the changes or cancel the Open command.
The Open command will cause the Open File dialog box to appear. This dialog box is used to select
the file to Open. Ladder logic files normally end with the file extension LAD. The dialog box
displays these files by default. Press Ctrl-O to execute the Open command.
2.3
Save
The Save command stores the current file on disk. If the current file has not yet been named, the
Save As File dialog box will appear. The file name and working directory can be selected from this
dialog box. The title bar at the top of the editor window shows the current file name. Press Ctrl-S to
execute the Save command.
2.4
Save As
The Save As command stores a file with a different name, or location, than the current file. The Save
As File dialog box is used to specify the file name and directory in which to save the file. Ladder
logic file names normally end with the extension LAD. The editor uses the extension LAD
automatically, if you do not type it. Press Ctrl-A to execute Save As command.
2.5
Page Setup
The Page Setup dialog controls the appearance of printed documentation. The items to be
documented are selected with the Select Print Items command.
The Margins section defines the printing margins for the page. Use the margins to adjust the look of
the printed output. The Measurement Units box selects the units of measurement for the margins.
The Page Headings section selects headers for each page of printed documentation.
•
Check the Page Header box to print headings on all pages. The heading includes the file name,
a page description, and the items described below.
•
Check the Date and Time box to print the time and date on each page.
•
Check the Page Numbers box to print page numbers on each page. Page numbers normally
begin with page 1. You can specify the starting page.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
12
2.6
Print
The Print command is used to print documentation on your printer. The Print dialog box is used to
select the printer and printer options such as page size and orientation for the print job.
The items to be documented are selected with the Select Print Items command. The page layout and
margins are selected with the Page Setup command.
2.7
Select Print Items
The Select Print Items command is used to select the program documentation and print topics to be
printed. Through the selections in the Select Print Items dialog box, shown below, a customized
program print-out can be created.
Figure 1: Select Print Items Dialog Box
The Network Listings section contains selections for defining the networks and comments to be
printed.
The Print Networks selection defines the networks to print. All networks in the ladder program or a
range of networks may be selected for printing.
The Print Embedded Comments selection enables network comments to be printed with the
networks.
The Configuration selection enables the printing of the element configuration parameters for
elements that use the element configuration dialog.
Select Multiple Networks on Page to allow multiple unbroken, networks and embedded comments
to be printed on each page.
Select Network Font to modify the font used in printing the embedded comments and network
functions, addresses, tag names and network titles.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
13
The Supplemental Listings section contains selections for detailed program information that can be
printed. Each item selected in the supplemental listings section is printed as a separate section with
page header, if selected in page setup.
The List of Tag Names selection adds a complete list of all tag names used to the print out. Tag
names can be sorted by their name or address.
A list of all network titles and network numbers used in the program are printed when the List of
Network Titles is selected.
Selecting the DNP Configuration prints the complete configuration for the DNP protocol if it is
used in the application.
Selecting the Serial Port Settings selection prints complete serial port settings for each serial port.
The Outputs On Stop Settings for the analog and digital outputs are printed when this item is
selected.
Register Assignment selection enables the complete register assignment used in the application to
be printed.
A list of destination coils and tag names in use is added to the print-out when List of Coils Used is
selected.
An index of all print topics selected is added to the print-out by selecting Index.
The font used for printing the supplemental listings is can be modified by selecting Listing Font.
Selecting Addresses in the Location References section adds a complete cross-reference of all
addresses used in the ladder logic program. The addresses are cross-referenced to Network / Row /
Column locations for all occurrences of each address.
•
Click OK to accept the selected print items and close the dialog box.
•
Click Cancel to discard changes.
2.8
Quick File List
The quick file list area displays the names of the four most recently used Ladder Logic files. Select a
file from this list by clicking the left mouse button on the file name or by pressing the number of the
file.
2.9
Exit
The Exit command terminates the TelePACE program. The editor warns you to save the current file,
if it changed since the last save. You may save the changes, throw away the changes or cancel the
Exit command. Press Ctrl-Q to execute the Exit command.
Selecting Close from the system menu also terminates the program. The editor prompts you to save
changes to your program.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
14
3
Edit Menu
The Edit menu commands are used to insert, delete and modify the logic elements, function blocks,
comments and networks used in the Ladder Logic program. Clicking the left mouse button on the
desired command, or, from the keyboard by pressing the underlined letter accesses all Edit menu
commands.
3.1
Undo
The Undo command reverses the last change made in the Ladder editor or Comment editor. This is a
single level command and only the last change made before selecting Undo is reversible. Selecting
Undo again reverses the action of the last Undo.
•
Press Ctrl-Z to execute the Undo command from the keyboard.
•
Right click your mouse and select Undo from the command list.
3.2
Cut Selected
The Cut Selected command removes the selected elements in the Ladder Editor or the Comment
editor and puts them on the Clipboard. Items on the clipboard remain there until they are replaced by
other selected elements.
•
Press Ctrl-X to execute the Cut Selected command from the keyboard.
•
Right click your mouse and select Cut Selected from the command list.
3.3
Copy Selected
The Copy Selected command copies the selected elements in the Ladder editor to the clipboard.
Items on the clipboard remain there until they are replaced by other selected elements.
•
Press Ctrl-C to execute the Copy Selected command from the keyboard.
•
Right click your mouse and select Copy Selected from the command list.
3.4
Copy Networks
The Copy Networks command copies a network or block of networks to the clipboard. Comments
for the network are also copied to the clipboard.
Networks to copy are selected from the Copy Networks dialog box. Continuous networks from the
First Network selection to the Last Network selection may be copied to the clipboard.
3.5
Cut Networks
The Cut Networks command cuts a network or block of networks to the clipboard. Comments for the
network are also cut to the clipboard.
Networks to cut are selected from the Cut Networks dialog box. Continuous networks from the First
Network selection to the Last Network selection may be cut to the clipboard.
3.6
Paste
The Paste command is used to paste items on the clipboard to the current cursor position. The paste
command in the Edit menu box is grayed out when there are no items on the clipboard or the cursor
is in the wrong pane for the clipboard items. For example text cannot be pasted into the Ladder
Editor pane and network elements cannot be pasted into the Comment Editor pane.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
15
Text cannot be pasted into the Comment Editor if the clipboard text will cause the Comment Editor
to exceed 16 Kbytes of text for the network. In the Ladder Editor pane if there is not enough room
between the cursor and the edge of the network to paste the selected items an error message is
displayed.
When a network or block of networks are pasted from the clipboard the Paste Block of Networks
dialog box appears. This dialog box is used to determine if the block of networks is to be pasted
before or after the current network and whether network titles and comments are pasted with the
block of networks.
•
Press Ctrl-V to execute the Paste command from the keyboard.
•
Right click your mouse and select Paste from the command list.
3.7
Insert
The Insert command is used to insert changes to the current ladder logic network. When the Insert
command is selected the Insert dialog box pops up. Items that can be inserted into the ladder logic
program are displayed in the dialog box. Items in the dialog are inaccessible (grayed) if they cannot
be used from the current cursor position. Items to be inserted are selected by selecting the radio
button associated with each selection.
Figure 2: Insert Dialog Box
3.7.1
Insert Vertical Shunt
The insert Vertical Shunt selection inserts a vertical shunt on the right side of the element
highlighted by the cursor. Where a multiple cell element is selected, the vertical shunt is inserted in
the cursor position shown on the status bar. This command is not available in the Comment Editor
pane.
•
Press F5 to insert a vertical shunt.
•
Right click your mouse and select Insert Vertical Shunt from the command list.
3.7.2
Insert Element
The insert Element selection inserts or edits an element at the current cursor position. A dialog box
appears displaying the Ladder Editor function block list. This command is not available in the
Comment Editor pane.
•
Press Insert to execute this function from the keyboard.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
16
•
Right click your mouse and select Insert/Edit Element from the command list.
Function List
Input Value
Input Tag List
Input Type
Selection
Function
Input Description
Figure 3: Insert / Edit Network Element Dialog Box
The function block list shows the function blocks that fit in the current position. If the cursor is over
an existing function block, the list shows only function blocks of the same size. If the cursor is over a
blank space, the list shows all function blocks that fit. Function blocks occupy one, two, or three
cells in a network. The left side of the status bar at the bottom of the dialog shows the selected
function block name.
Selecting a function activates the input boxes at the bottom of the dialog. There are one, two, or three
inputs depending on the function. A description of the input is shown on the status bar, when an
input is selected for editing.
Some function blocks allow either addresses or constants as inputs. The radio buttons on the left of
the input box indicate if the value in the input box is an address or a constant. Click the left radio
button to input a constant. Click the right radio button to input an address of the type displayed. The
radio button defaults to the address type selection.
There are two ways to edit an input:
When an address type is selected the register address can be typed into the input edit box. By default
the first register address, of the type required, is displayed in the edit box. Some functions require a
range of registers to define an input. In these cases the first and last register of the range are
displayed. Edit the displayed address to the meet the requirements of your application. The upper
range limit is recalculated automatically as soon as any valid start register is entered.
When a constant type is selected the constant value can be typed into the input edit box. By default
the number of the first register address, of the type required, is displayed in the edit box. Edit the
displayed constant to the meet the requirements of your application.
A tag name can be selected from the tag selection list. Click the tag list and choose the tag for the
address or constant desired. The tag selection list will show only tags that are allowed on the selected
input.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
17
3.7.3
Address Types
The text beside the address button indicates the register types that are valid for the current function.
Type
0reg
0blk
1reg
1blk
3reg
4reg
Description
Discrete output register address
Discrete output register block address
Discrete input register address
Discrete input register block address
Analog input register address
Analog output register address
Registers
Single bit register
16 single bit registers
Single bit register
16 single bit registers
Sixteen bit register
Sixteen bit register
Table 1: Address Types
Note: Discrete input and output register blocks (blk types) must begin at the start of a 16-bit word
within the controller memory. Suitable addresses are 00001, 00017, 10001, 10033, etc.
3.7.4
Empty Column
The Empty Column selection inserts an empty column to the left of the current cursor position. This
selection is greyed if an empty column already exists to the left of the cursor or if there is no room
for an empty column in the network. This command is not available in the Comment Editor pane.
3.7.5
Empty Row
The Empty Row selection inserts an empty row above the current cursor position. This selection is
greyed if an empty row already exists to the left of the cursor or if there is no room for an empty row
in the network. This command is not available in the Comment Editor pane.
3.7.6
Network Before
The Network Before selection inserts an empty network before the current network. The cursor
moves to column 1 Row 1 of the new network. This command is available in the Comment Editor
pane.
3.7.7
Network After
The Network After selection inserts an empty network after the current network. The cursor moves
to column 1 Row 1 of the new network. This command is available in the Comment Editor pane.
3.8
Delete
The Delete command removes items from the current Ladder Editor network. Press Delete to execute
this function. A dialog box showing items that can be deleted appears. Items in the dialog box may
be inaccessible (grayed) if they do not apply to the selected elements. The delete command is grayed
out in the Edit menu when the cursor is in the Comment Editor pane. Items to delete are selected by
clicking on the radio button associated with each selection.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
18
Figure 4: Delete Dialog Box
3.8.1
Vertical Shunt
The Vertical Shunt selection deletes the vertical shunt on the element highlighted by the cursor. This
command is greyed if there is no vertical shunt on the element.
3.8.2
Element
The Element selection deletes the element at the current cursor position. This will delete a single
element only, even if multiple elements are selected.
3.8.3
Selected Elements
The Selected Element selection deletes the elements highlighted in the network. Elements are
highlighted by dragging the network cursor to highlight more than a single element.
3.8.4
Empty Column
The Empty Column selection deletes a column that contains no elements, and moves the elements in
the columns to the right of it one column to the left.
3.8.5
Empty Row
The Empty Row selection deletes a row that contains no elements, and moves the elements in the
rows below it up one row.
3.8.6
Network
The delete Network command deletes the current network and all the elements in it. Deleting a
network does not remove the Tag names from the program.
3.8.7
Delete All Networks
The delete All Networks command deletes all ladder logic networks in the current file. You are
asked to confirm that you wish to delete the networks. Deleting all networks does not change tag
names, I/O assignments or the file name.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
19
3.9
Toggle Vertical Shunt
The Toggle Vertical Shunt command toggles (inserts or deletes) a vertical shunt on the right side of
the element highlighted by the cursor. The F5 key also performs this command.
3.10
Tag Names
The Tag Names selection is used to edit names that can be used in place of addresses and constants.
Tag names may be used once only for a constant or an address. Numbers can occur once for a
constant and once for an address.
•
Tag names must conform to the .CSV file format naming convention.
•
Tag names may be up to 16 characters long and up to 2500 tag names can be created.
•
The Edit Tag Names dialog box appears allowing the editing of Tag names.
Figure 5: Edit Tag Names Dialog Box
The Edit Tag Names edit box is used to enter tag names. The drop down menu to the right of the
box displays tag names already created.
The Number edit box is used to enter the number associated with the tag.
The Tag Type radio buttons select the type of tag. A Tag Type can be an address or a constant.
The Tag Display edit box displays the Tag Name entered in the Tag Name edit box. Tag names are a
maximum of sixteen characters with eight characters on each line. The tag display box shows the tag
name as it will be displayed in the Ladder Editor.
The Next Free Number button will cause the value in the Number edit box to be replaced by the
next unused address or number of the Tag Type that is not in use.
The Add Tag Name button adds the tag to the list of tag names. An error dialog will appear if the
tag name exists with a different type or number, or if a number exists with the same type and a
different name.
The Remove Tag Name button removes the selected tag from the list of tag names. An error dialog
will appear if the name is in the list but the other data does not match the type button or number box.
The Close button closes the Edit Tag Names dialog.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
20
3.11
Erase All Tags
The Erase All Tags command is used to erase all tag names in a TelePACE Ladder Logic application
program. This command can be used before importing tags from another program or a CSV file to
eliminate errors when there are conflicts between existing tag names and imported tag names.
The command opens the following message box:
Figure 6: Erase All Tags Dialog Box
•
Click on Yes to erase all tags.
•
Click on No to abort the command.
Note: Erasing all tags cannot be undone. If you are unsure you should save your file before
executing this command.
3.12
Export Tag Names
The Export Tag Names command is used to write the program tag names into a CSV (comma
separated value) file. A CSV file can be opened, and edited in most spreadsheet programs. Note that
the modified tag names must conform to the .CSV format.
The Export Tag Names to File dialog box is used to specify the file name and directory of the export
file. Tag name files normally end with the extension CSV. The editor uses the extension CSV
automatically, if you do not type it.
The CSV file contains a title line followed by multiple data lines containing the type_specifier,
address and tag_name fields. Commas separate these fields. The type_specifier is A for an address
tag, and C for a constant tag. The tag name can be enclosed in quotes. If the tag name contains a
comma, it must be enclosed in quotes.
Note that if a type and register value is specified, a corresponding tag name must be entered
otherwise an error will result.
Title line:
Data line:
Note:
3.13
Type, Value, Tag
type_specifier, address, tag_name
A blank tag name is not allowed. If a type and register value is specified, a corresponding
tag name must be entered otherwise an error will result.
Import Tag Names
The Import Tag Names command is used to read tag names into the editor. Tag names may be read
from another ladder logic program, or from a CSV file. New tags are added to the existing tag list.
The Import Tag Names From File dialog box is used to select the file containing the tag names. Files
with the extensions LAD and CSV are displayed by default.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
21
As the tags are imported, they are checked for errors. If a tag is imported that that already exists in
the program an error will occur. If an error occurs, you may continue to process the input file to look
for more errors, or you may abort the import. If an error occurs, no tags are imported.
A CSV file consists of a title line followed by multiple data lines containing the type_specifier,
address and tag_name fields. Commas separate these fields. The type_specifier is A for an address
tag, and C for a constant tag. The tag name can be enclosed in quotes. If the tag name contains a
comma, it must be enclosed in quotes.
Title line:
Data line:
3.14
Type, Value, Tag
type_specifier, address, tag_name
Network Title
The edit Network Title selection is used to edit the title of the current network. When selected the
Edit Network Title dialog box appears and the title can be edited. The title may be a maximum of 28
characters long.
3.15
Element Configuration
The element configuration command edits initial values for 40000 series registers used by the
MSTR, DIAL, INIM, HART, FLOW, SCAL, TOTL, PIDD, PIDA and SLP elements. The register
values are written to the controller with the program. The register values may be modified later by
other elements of the program.
Right click your mouse and select Element Configuration from the command list.
WARNING
If the controller is initialized, using the Initialize command in the Controller menu, all I/O database
registers used for Element Configuration are set to zero. The application program must be re-loaded
to the controller.
Any change made to an element configuration in the Edit On Line mode will be downloaded to the
controller immediately.
3.16
Registers
The Registers command replaces, and enhances, the Monitor List command from previous versions
of TelePACE. The Registers command allows the online monitoring and control and the offline
editing of registers used in a TelePACE application. These registers may be saved in a single group,
or in multiple groups for monitoring. Individual registers may be selected for on-line and off-line
editing of their data.
When the Registers command is selected the Register Editor is opened. The Register Editor is used
to add registers to the Register list; edit registers in the list and to display register data.
All registers in the Register list are automatically added to the Register data file see the Register
Data File section for complete details on this file. Through using the Register Editor and the
associated Register Data File users are able to easily:
Save a list, or lists, of registers for monitoring and control that is specific for each TelePACE
application program.
Preload registers used in a TelePACE application with data.
Save a ‘snap shot’ of data in registers used in a TelePACE application.
Create meaningful groups of registers for monitoring and control.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
22
3.16.1
Register Editor
The Register Editor displays registers and allows the editing of register content. The dialog is
divided into three main areas. The Groups section allows the user to create and manage groups of
registers. The Register List section displays the registers, and register attributes, for each register in
a group. The Update Rate section allows the user to control the refresh frequency for the registers
in a displayed group.
The Register Editor may be opened in the off-line and on-line editing modes. When opened the
Register Editor is displayed on top of the Ladder Editor. Ladder Logic cannot be modified while the
Register Editor is open. The Register Editor dialog is opened automatically in the Monitor on-line
mode.
Figure 7: Register Editor Dialog Box
3.16.1.1
Groups
Register groups allows users to manage how registers are viewed in the Register Editor. Registers
that are used in various parts of an application can be grouped together to provide an easy to view,
and edit, list of registers. When in the on-line mode, only the registers in the current group are
updated. This improves response time as large groups of registers can take a long time to update.
Registers may be assigned to more than one group.
The Groups list box displays the register groups that have been created. When a group is selected
the registers in the group are displayed in the Registers window. The group that was last selected the
previous time the Register Editor was opened is displayed. Only one group can be selected at a time.
The New button creates a new group. It opens the New Group dialog.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
23
Figure 8: New Group Dialog Box
The Group edit box specifies the name of the new group. The group name may contain letters,
numbers, and spaces. The group name is 1 to 16 characters long. Group names are case insensitive.
The OK button creates the new group and closes the dialog. If the group name already exists an error
message is displayed and the dialog remains open.
The Cancel button closes the dialog.
The Remove button deletes a group from the group list. All the registers in the group are deleted.
The button is disabled (greyed) if no group is selected.
The Rename button renames a group. It opens the Rename Group dialog.
Figure 9: Rename Group Dialog Box
The Group Name field shows the current name of the group.
The New Name edit box specifies the new name of the group. The group name may contain letters,
numbers, and spaces. The group name is 1 to 16 characters long. Group names are case insensitive.
The OK button renames the group and closes the dialog. If the group name already exists an error
message is displayed and the dialog remains open.
The Cancel button closes the dialog.
3.16.1.2
Update Rate
The Update Rate edit box determines how often the register editor updates values when on-line.
Valid values are 0.1 to 1000 seconds. The default value is 1 second. This value is used for all files
opened by TelePACE and is saved when TelePACE is closed.
The Change button sets the current update rate. The modification in the Update Rate edit box will
not take effect until the Change button is pressed. This button is disabled when the Register Editor is
offline.
3.16.1.3
Register List
The Register list is displayed in the center of the Register Editor dialog. The Register List displays
the registers for the selected group. Each register in the list has seven fields, or columns associated
with it. The columns can be resized by dragging the edge of the column heading. The columns may
be sorted by clicking the heading of each column.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
24
The Register column displays the register number.
The Tag column displays the tag name associated with the register.
The Value column displays the value of the register in the selected format. Coil and status registers
are shown as OFF or ON.
The Format column displays the register format. The register format is one of the following:
Register Format
Unsigned
Signed
Unsigned Double
Signed Double
Floating Point
Hexadecimal
Binary
ASCII
Boolean
Description
Displays a single register as an unsigned integer
Displays a single register as a signed integer
Displays two consecutive registers as an unsigned double integer
Displays two consecutive registers as a signed double integer
Displays two consecutive registers as a floating point number
Displays a single register as a hexadecimal number
Displays a single register as a binary number
Displays a single register as two ASCII characters
Displays coil and status registers which have no format
Table 2: Register Formats
The Forced column indicates if the register value is forced. Valid selections are No and Forced.
The Available column indicates if the register value is available always or only when TelePACE is
on-line with the controller.
The Configuration column indicates if the register is part of an element configuration. It is
recommended that registers that are part of an element configuration not be modified in the register
editor. Use the element configuration feature instead.
The Add button adds registers to the selected group. It opens the Add Registers Dialog. This button
is disabled if no group is selected.
The Delete button deletes the selected registers from the group. This button is disabled if no register
is selected. This button is disabled if no group is selected.
The Edit button opens the Edit Register Dialog to edit the selected register value, format, force
status, and register availability. This button is disabled if no register is selected or more than one
register is selected. This button is disabled if no group is selected.
The Close button closes the dialog. This button is disabled in the monitor on-line mode.
The dialog is resizable. Click on the lower right corner and drag to change the size of the dialog.
3.16.2
Add Registers Dialog
The Add Registers dialog adds registers to the current group in the Register Editor dialog. The group
name is displayed in the window title.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
25
Figure 10: Add Registers – List Dialog Box
The Format drop-down list box specifies how the registers will be displayed. Select the format
before adding registers.
Display
Unsigned
Signed
Unsigned Double
Signed Double
Floating Point
Hexadecimal
Binary
ASCII
Boolean
Description
Displays a single register as an unsigned integer
Displays a single register as a signed integer
Displays two consecutive registers as an unsigned double integer
Displays two consecutive registers as a signed double integer
Displays two consecutive registers as a floating point number
Displays a single register as a hexadecimal number
Displays a single register as a binary number
Displays a single register as two ASCII characters
Displays coil and status registers which have no format
Table 3: Register Display Properties
If a register or tag is used by element configuration its format cannot be changed. The register cannot
be merged with adjacent registers or split if the format of an adjacent register is changed.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
26
If a register or tag is already in the any register editor group but has a different format, the format of
the register is changed in all groups.
The Unsigned Double, Signed Double, and Floating Point formats add two registers to the register
editor group. The pair of registers is displayed as a single number.
If a single register is added that is part of an existing pair, the existing pair will become invalid and
only new single register is displayed.
If a pair of registers is added that overlaps an existing single register, the single register and the
following register will be made part of the register pair. If the following register is a part of the
existing pair, that existing pair will become invalid.
If a pair of registers is added that overlaps one register of an existing pair, or two registers of two
existing pairs, the new pair will be added and the existing overlapped pair will become invalid.
The Available list box specifies when register values can be viewed and edited. Valid values are
Always and Online. The Always selection makes the register values available in both online and
offline editing modes. The Online selection makes the register values available only in the online
editing modes. The default is Online.
3.16.2.1
Registers In Use
The Registers in Use list box displays all registers that are used in the Ladder Logic program. One
or more registers may be selected.
•
To select a register, click on it.
•
To select more than one register, hold the Ctrl key and click on each register to be added.
•
To select a range of registers, click on the first register and hold down the Shift key while
clicking on the last register. A second method is to hold the Shift key and use the Down Arrow
key or Up Arrow key to select the registers.
The Add Registers button adds the selected registers to the register editor group. The registers are
added in the format selected.
3.16.2.2
Range
The Start and End edit boxes specify a range of registers to add.
•
To select a range, enter the Start and End registers.
•
To select a single register, enter it in the Start edit box and enter 0 in the End edit box.
The Add Range button adds the selected registers to the register editor group. The registers are
added in the format selected.
3.16.2.3
Tags
The Tags list box displays all tags and the corresponding register number that are defined in the
Ladder Logic program. One or more tags may be selected.
•
To select a tag, click on it.
•
To select more than one tag, hold the Ctrl key and click on tags.
•
To select a range of tags, click on the first tag and hold down the Shift key while clicking on the
last tag or use Down Arrow key or Up Arrow key.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
27
•
To select a range of tags, click on the first tag and hold down the Shift key while clicking on the
last tag. A second method is to hold the Shift key and use the Down Arrow key or Up Arrow key
to select the tags.
The Add Tags button adds the selected tags to the register editor group. The tags are added in the
format selected.
The Close button closes the dialog.
3.16.3
Edit Register Dialog
The Edit Register dialog modifies values for a register. There are two forms of the dialog. The
following dialog is used for editing input registers (3xxxx type) and holding registers (4xxxx type).
Figure 11: Edit Register Dialog Box
The following dialog is used for editing coil registers (0xxxx type) and status registers (0xxxx type).
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
28
Figure 12: Edit Register Dialog Box- Value Off
The Register field displays the register number. This field cannot be edited.
The Tag field displays the tag for the register. This field cannot be edited.
The Value edit box displays and allows the editing of register values.
For input and holding registers the Value edit box displays the current value of the register. Valid
values depend on the format of the register. The edit box is disabled if the register is not available
Always and the editor is in the off-line mode.
For coil and status registers the Value drop-down list box shows the value of the register. Valid
values are ON and OFF. The list box is disabled if the register is not available Always and the editor
is in the off-line mode.
The Format list box selects the format of the register. The list box is disabled and shows none for
coil and status registers. The list box is disabled if the register is used for Element Configuration the format of these registers cannot be changed. The following formats are available.
Format
Unsigned
Signed
Unsigned Double
Signed Double
Floating Point
Hexadecimal
Binary
ASCII
Boolean
Description
Displays a single register as an unsigned integer
Displays a single register as a signed integer
Displays two consecutive registers as an unsigned double integer
Displays two consecutive registers as a signed double integer
Displays two consecutive registers as a floating point number
Displays a single register as a hexadecimal number
Displays a single register as a binary number
Displays a single register as two ASCII characters
Displays coil and status registers which have no format
Table 4: Register Formats
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
29
The Force drop-down list box indicates if the value is forced. Valid values are No and Forced. The
list box is disabled if the register is not available Always and the editor is in the off-line mode.
The Available drop-down list box indicates when register values can be viewed and edited. Valid
values are Always and Online. The Always selection makes the register values available in both
online and offline editing modes. The Online selection makes the register values available only in the
online editing modes. The default is Always if the editor is off-line and Online if the editor is online.
The Warning is displayed if the register is used by element configuration. It is recommended
Element Configuration be used to change the register value. The Element Configuration function
performs additional error checking specific to the Ladder Logic element.
The OK button saves changes and closes the dialog. If the Editor is on-line, changes are written to
the controller.
The Cancel button closes the dialog.
The Apply button writes the changes to the controller, when the editor is on-line. The Apply button
is disabled if the editor is off-line.
3.16.4
Register Data File
The register data file is created, saved and opened with the Ladder Logic file. The register data file
contains the information for any registers that have been added to the Register Editor and any
registers used in an element configuration. The Register Data file will contain only the header record
(see Register Data File Format) if there are no Register Editor entries or element configuration.
Users can easily edit the register data file providing a rapid way to add or remove registers or modify
their values or format.
3.16.4.1
Register Data File Format
The register data file is saved as a CSV (comma separated value) format file. The file is saved in the
format: filename - Registers.csv. Where filename is the TelePACE Ladder Logic file name.
Each line in the CSV file is one record. The following is an example of a Register Data file.
Register,Value,Format,Forced,Available,Groups
01057,0,BO,No,Always,Sensors
30002,9440,S,No,Online,Sensors
30004,312,S,No,Online,Sensors
40238,1826,U,No,Always,all
45021,606,U,No,Online,Heating;Cooling
45035,+23.6250,F,No,Always,Cooling
45041,32,B,No,Always,Cooling
48016,1074,U,No,Always,*Element
The first line in the file is a header record and it contains the names of each of the fields. The
following table describes each of the fields in the file.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
30
Field
Register
Value
Format
Force
Available
Groups
Description
The address of the register or first register of a register pair. Register pairs
are used for unsigned double, signed double and floating point registers.
Valid register addresses are:
00001 to 09999 Digital Output registers.
10001 to 19999 Digital Input registers.
30001 to 39999 Analog Input registers.
40001 to 49999 Analog Output registers.
Value of the register or registers.
Boolean:
0 to 1
Unsigned:
0 to 65535
Signed:
-32768 to 32767
Unsigned double: 0 to 232-1
Signed double: -231 to 231-1
Hexadecimal: same as unsigned
Binary:
same as unsigned
ASCII:
same as unsigned
Display format for the register or registers.
BO
Boolean
U
Unsigned
S
Signed
UD
Unsigned double
SD
Signed double
F
Floating point
H
Hexadecimal
B
Binary
A
ASCII
Indicates if register value is forced.
No
Indicates register is not forced
Forced Indicates register is forced
Indicates if register is available always or online only.
Always Indicates that the register may be edited in either the Online or Off
line mode.
Online Indicates that the register may be edited in the Online mode only.
List of groups that include this register. If the register is included in more than
one group each group is listed with semicolons separating the group names.
The special value *Element is reserved for registers used by element
configuration.
Table 5: Insert Table Caption Here
3.16.5
Editing the Register Data File
The CSV file may be edited using a text editor, such as Notepad or a spreadsheet program such as
Excel. The following operations can be done easily with a text editor or spreadsheet: adding,
inserting, replacing, removing or editing many registers, searching for registers, and sorting.
Care must be exercised when editing the CSV file. Improper changes may result in loss of element
configuration or register data. The following list gives some suggestions when editing a CSV file.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
31
•
Make a backup copy of the file before changing it. The file can be restored if you make invalid
changes.
•
A register can occur only once in the CSV file. Check that a register is listed only once after
copying lines.
•
Do not change the header record.
•
Do not change the order of the columns.
•
Do not use empty fields.
•
Avoid including the header record when sorting column.
•
Avoid sorting only some of the columns.
•
Avoid overlapped registers with different register formats.
•
Group names may contain spaces, letters, and numbers only. Don’t use other characters.
•
Separate group names with semicolons.
•
Group names are case insensitive the case does not matter.
•
If registers containing part of an element configuration are deleted, the value for that register will
be missing. This may cause unexpected operation of your ladder logic program.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
32
4
Search Menu
Search Menu commands are used to locate networks, devices, addresses and tag names in the current
Ladder Editor program. Addresses may be located, or located and replaced from the Search menu.
4.1
Next Network
Selecting the Next Network command from the Search Menu moves the Ladder Editor to the next
Network in the program. The next network command is grayed out if the current network is the last
network. Press F8 to move the Ladder Editor to the next network.
4.2
Previous Network
Selecting the Previous Network command from the Search Menu moves the Ladder Editor to the
previous Network in the program. The Previous Network command is grayed out if the current
network is the first network. Press F7 on the keyboard to move the Ladder Editor to the previous
network.
4.3
Go To Network
The Go To Network command is used to move the Ladder Editor to a desired network. When the Go
To Network command is selected the Go To Network dialog box pops up. The network titles or
number to go to is entered in this dialog box. The Title box selects the title of the network. A drop
down list shows multiple network titles in use. Networks that have no title are displayed showing the
network number only. The Network box selects the number of the network. The Previous button
moves backward through the list of networks. The Next button moves forwards through the list of
networks.
Figure 13: Go To Network Dialog Box
4.4
Find Address
The Find Address command searches the program for an address, or range of addresses, and moves
to the first element containing any address in the range. The search proceeds down the rows from the
present column, to column ten, row eight in the current network, then moves to the next network.
Figure 14: Find Network Address Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
33
The Find Network Address dialog box is used to enter the address, or range of addresses to find. The
From box specifies the first address to locate. The initial value comes from the element at the current
cursor position. The To box specifies the last address in a range. A value of 0 indicates that only the
address in the From field is to be located. Checking the Start at Top of Logic box starts the search at
the beginning of the program. The search starts at the current cursor position when this box is
unchecked.
4.5
Find Device
The Find Device command is used to search the program for a device, and move to the first element
containing that device. The search proceeds down rows from the present column to column ten row
eight in the current network, then moves to the next network.
Figure 15: Find Network Element Dialog Box
The Find Network Element dialog box pops up when the Find Device command is selected. The
Function list specifies the device to locate. The initial value comes from the element at the current
cursor position. Checking the Start at Top of Logic box starts the search at the beginning of the
program. Leaving this box unchecked starts the search at the current cursor position.
4.6
Find Tag Name
The Find Tag Name command is used to search the program for a tag name, and move to the first
element containing the tag name. The search proceeds down rows from the present column to
column ten, row eight in the current network, then moves to the next network.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
34
Figure 16: Find Tag Name Dialog Box
The Find Tag Name dialog box, displaying all the tag names used in the program, pops up when the
Find Tag Name command is selected. Select a tag name in the Tag list by left clicking the mouse on
the desired tag name. Checking the Start at Top of Logic box starts the search for the selected tag
name at the beginning of the program. If left unchecked, the search starts at the current cursor
position.
4.7
Repeat Last Find
The Repeat Last Find command repeats the last search performed. Press F3 to repeat the last find.
4.8
Replace Address
The Replace Address command is used to search the program for an address and then replace the
address with another address. The search proceeds down rows from the present column to column
ten, row eight in the current network, then moves to the next network.
Figure 17: Replace Address Dialog Box
When the Replace Address command is selected the Replace Address dialog box pops up. The
address to find and the replacement address are selected from this dialog box.
The Find Address box specifies the address to be replaced. The Replace With box specifies the
replacement address.
Checking the Start at Top of Logic box starts the search at the beginning of the program. If left
unchecked, the search starts at the current cursor position. Checking the Return to Current Location
box returns the cursor to the current network after the command is executed. If left unchecked, the
cursor is in the last program network after the command is executed.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
35
The Find First button, when selected, will cause the Change Address dialog box to appear each time
the search finds the address to be replaced. The With box allows changing of the replacement
address. Selecting the Replace button replaces the address. The Find Next button continues the
search to the next occurrence of the address to find.
4.9
Multiple Coils
Selecting the Multiple Coils command causes the Multiple Coils dialog box to pop up. This dialog
box displays all coils that are used more than once in the current program.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
36
5
Controller Menu
The Controller menu commands are used to configure the Micro16 and SCADAPack controllers.
Controller selection, serial port configuration, I/O assignments, register assignment, and outputs on
stop are defined in this menu selection. Controller initialization, I/O forcing and the C Program
Loader are also selected from this menu.
5.1
Type
The TelePACE program is used to program and configure the Micro16, SCADAPack and
SCADASense controllers. The selected controller determines controller specific options for other
menus and communication functions.
TelePACE verifies the controller type when writing to the target controller and when entering the
on-line modes. If the controller type selected in the application is different than the target controller,
the following message appears:
"Cannot write to a different type or model of controller. Do you want to switch the controller
type to xxxx?"
Where xxxx is the detected controller type.
The various controller types available in TelePACE are:
•
SCADASense 4202 DR
•
SCADASense 4202 DS
•
SCADASense 4203 DR
•
SCADASense 4203 DS
•
Micro16
•
SCADAPack
•
SCADAPack 100: 1024K: This controller type can only be used when the controller firmware is
version 1.80 or newer and the controller ID is greater than or equal to A182922.
•
SCADAPack 100: 256K: This controller type can only be used when the controller firmware is
version older than 1.80 and the controller ID is less than or equal to A182921.
•
SCADAPack 32
•
SCADAPack 32P
•
SCADAPack LIGHT
•
SCADAPack LP
•
SCADAPack PLUS
•
SCADAPack 350
Select the appropriate target controller this application is intended for.
5.2
Serial Ports
The Serial Ports selection is used to configure the serial port settings on the controller. There is a set
of port settings for each serial port on the controller. Each serial port is independently configured for
all serial and protocol parameters.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
37
The Controller Serial Ports Settings dialog box pops up when the Serial Ports command is selected.
Changes to serial port parameters are made within this dialog box.
To optimize communication performance on SCADAPack, SCADAPack Light and SCADAPack
Plus controllers, minimize the length of messages on com3 and com4. Examples of recommended
uses for com3 and com4 are for local operator display terminals, and for programming and
diagnostics using the TelePACE program.
Each item in the dialog is explained in the following paragraphs.
Figure 18: Controller Serial Ports Settings Dialog Box
The Port drop down menu selects the controller serial port to configure. The settings for the port are
displayed in the Port Settings controls section of the dialog. The valid serial ports depend on the
controller type. The default serial port is com1.
Controller Type
Micro16
SCADAPack
SCADAPack Plus
SCADAPack Light
SCADAPack LP
SCADAPack 100
SCADAPack 32
SCADAPack 32P
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
com1
X
X
X
X
X
X
X
X
com2
X
X
X
X
X
X
X
X
com3
X
X
com4
X
X
X
X
X
X
38
Controller Type
SCADAPack 350
SCADASense 4202 DR
SCADASense 4202 DS
SCADASense 4203 DR
SCADASense 4203 DS
com1
X
X
X
X
X
com2
X
X
X
X
X
com3
X
X
X
X
X
com4
Table 6: Controller Port Settings
The Protocol drop down menu selects the communication protocol type. Valid protocols depend on
the controller type as shown in the following table.
Controller Type
Micro16
SCADAPack
SCADAPack Plus
SCADAPack Light
SCADAPack LP
SCADAPack 100
SCADAPack 32
SCADAPack 32P
SCADASense family of
programmable controllers
(4202 DR, 4202 DS, 4203
DR and 4203 DS)
SCADAPack 350
Valid Protocols
None
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
* Note that SCADAPack 100
controllers with firmware older
than version 1.80 do not
support DF1 protocols.
None
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
PPP
Com 1 fixed as Sensor.
Com 2 and Com 3:
None
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
None
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
Default Protocol
Modbus RTU
Modbus RTU
Com 1 fixed as Sensor.
Com 2 and Com 3 default
is Modbus RTU.
Modbus RTU
39
Controller Type
Valid Protocols
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
Default Protocol
Table 7: Valid Protocols
The Addressing drop down menu selects the addressing mode for the selected protocol. The control
is disabled if the protocol does not support it. Valid addressing modes depend on the selected
protocol as shown in the following table.
Protocol
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
PPP
None
Valid Mode
Standard
Extended
Control is disabled
Default Mode
Standard
N/A
Control is disabled
Control is disabled
Control is disabled
N/A
N/A
N/A
Table 8: Valid Addressing Modes
The Station entry sets the station address for the selected controller serial port. Valid addresses
depend on the protocol and addressing mode selected, as shown in the table below.
Protocol
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
PPP
None
Valid Addresses
Standard addressing:
1 to 255
Extended addressing:
1 to 65534
0 to 254
Default Address
1
N/A
Control is disabled
Control is disabled
Control is disabled
N/A
N/A
N/A
Table 9: Valid Addresses
The Duplex drop down menu selects full or half-duplex operation for the selected Port. Valid and
default duplex settings depend on the serial port and controller type, as shown in the table below.
Note that the duplex is forced to Half if a SCADASense transmitter is configured on the port.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
40
Controller Type
Micro16
SCADAPack
SCADAPack Plus
SCADAPack Light
SCADAPack LP
SCADAPack 100
SCADAPack 32
SCADAPack 32P
SCADASense 4202 DR
SCADASense 4202 DS
SCADASense 4203 DR
SCADASense 4203 DS
SCADAPack 350
com1
com2
Valid
Full
Half
Full
Half
Full
Half
Full
Half
Half
Def.
Full
Full
Half
Full
Half
Full
Half
Full
Full
Half
Half
Half
Half
Full
Full
Full
Half
Full
Full
Full
com3
com4
Valid
Full
Half
Full
Half
Full
Half
Full
Half
Full
Half
Full
Half
Full
Half
Full
Half
Half
Def.
Full
Valid
Def.
Full
Half
Half
Full
Half
Half
Half
Half
Half
Full
Half
Full
Half
Half
Full
Half
Half
Full
Full
Full
Full
Half
Half
Half
Half
Valid
Def.
Half
Half
Half
Half
Full
Half
Full
Half
Full
Full
Full
Full
Half
Full
Full
Table 10: Duplex Settings
The Baud Rate drop down menu selects the communication speed for the selected serial port. Valid
baud rates depend on the serial port and controller type, as shown in the table below. The default
value is always 9600 baud.
300
600
1200
2400
4800
9600
19200
38400
57600
115200
Baud Rate
X
X
X
X
X
X
X
X
SCADAPack
Com 1, Com 2
Com 3
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
SCADAPack Plus
Com 1, Com 2
Com 3, Com 4
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Controller
Micro 16
Com 1, Com 2
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
X
41
1200
2400
4800
9600
19200
38400
57600
115200
Baud Rate
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
300
600
Controller
SCADAPack Light
Com 1, Com 2
Com 4
X
X
SCADAPack LP
Com 1, Com 2
Com 3
X
SCADAPack 100: 1024K
Com 1, Com 2
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
SCADAPack32P
Com 1, Com 2, Com 4
X
X
X
X
X
X
X
X
X
X
SCADAPack 350
Com 1, Com2, Com3
X
X
X
X
X
X
X
X
X
X
SCADASense Series of Programmable Controllers
Com1
X
Com2
X
X
X
X
X
X
Com3
X
X
X
X
X
X
X
X
X
X
SCADAPack32
Com 1, Com 2, Com 4
Com 3
Table 11: Baud Rates
The Data Bits drop down menu selects the number of data bits. Valid selections are 7 and 8 bits.
This parameter is forced to 8 bits when the protocol type is Modbus RTU, PPP or any DF1 protocol.
The default selection is 8 bits.
The Parity drop down menu selects the parity for the selected port. Valid selections depend on the
serial port, controller type and data bits, as shown in the table below. The default selection is always
none.
Controller Type
Micro16
SCADAPack
com1
None
even
odd
None
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
com2
none
even
odd
none
com3
7 bits
N/A
com4
8 bits
7 bits
N/A
none
N/A
8 bits
42
Controller Type
com1
com2
even
odd
SCADAPack Plus
SCADAPack Light
SCADAPack LP
SCADAPack 100
SCADAPack 32
SCADAPack 32P
even
odd
None
even
odd
none
even
odd
none
even
odd
none
even
odd
none
even
odd
none
even
odd
none
even
odd
none
even
odd
none
even
odd
none
even
odd
none
even
odd
none
none
even
odd
none
even
odd
SCADASense 4203 DR
SCADASense 4203 DS
none
SCADAPack 350
none
even
odd
none
even
odd
none
even
odd
SCADASense 4202 DR
SCADASense 4202 DS
com3
7 bits
even
odd
space
mark
even
odd
space
mark
N/A
even
odd
space
mark
even
odd
space
mark
N/A
none
even
odd
mark
none
even
odd
None
even
odd
com4
8 bits
even
odd
mark
none
even
odd
mark
none
even
odd
7 bits
even
odd
space
mark
even
odd
space
mark
N/A
8 bits
none
even
odd
mark
none
even
odd
mark
mark
none
even
odd
none
even
odd
mark
none
even
odd
N/A
N/A
N/A
Table 12: Parity Settings
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
43
The Stop Bits drop down menu selects the number of stop bits for the selected serial port. Besides
the SCADAPack 350 with a preset stop bit of 1, valid selections are 1 and 2 for all other controllers.
Valid selection for com3 is 1 stop bit. The default selection is 1.
Note: The SCADAPack 350 has only 1 stop bit. This cannot be changed.
The Rx Flow drop down menu selects the receiver flow control for the selected port. Valid selections
depend on the protocol, controller type, and serial port, as shown in the table below. If there is only
one valid value the control is disabled. If there is more than one possible value, the default selection
is none.
Protocol
DF1 Full BCC
DF1 Full CRC
DF1 Half BCC
DF1 Half CRC
DNP
Modbus RTU
Controller
Micro16
SP
SP Plus
SP Light
SP LP
SP 100
SP 32
SP 32P
SCADASense 4202 DR
SCADASense 4202 DS
SCADASense 4203 DR
SCADASense 4203 DS
SCADAPack 350
Micro16
SP
com1
None
None
None
None
None
None
None
None
N/A
com2
None
None
None
None
None
None
None
None
None
N/A
None
None
None
None
None
None
None
SP Plus
None
None
SP Light
None
None
SP LP
None
None
SP 100
SP 32
None
Modbus
RTU
Modbus
RTU
None
None
Modbus
RTU
Modbus
RTU
None
None
Modbus
RTU
Modbus
RTU
N/A
Modbus
RTU
None
Xon/Xoff
None
Xon/Xoff
Modbus
RTU
none
Xon/Xoff
none
Xon/Xoff
Modbus
RTU
N/A
SP 32P
SCADASense 4202 DR
SCADASense 4202 DS
SCADASense 4203 DR
SCADASense 4203 DS
SCADAPack 350
None
Modbus ASCII
Micro16
SP
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
com3
N/A
None
None
N/A
None
N/A
None
N/A
None
Ignore CTS
None
com4
N/A
N/A
None
none
N/A
N/A
None
None
N/A
None
N/A
Modbus
RTU
Modbus
RTU
N/A
N/A
N/A
Modbus
RTU
N/A
Modbus
RTU
N/A
Modbus
RTU
Modbus
RTU
N/A
Modbus
RTU
Modbus
RTU
Modbus
RTU
N/A
None
N/A
44
Protocol
Controller
SP Plus
SP Light
SP LP
SP 100
SP 32
SP 32P
SCADASense 4202 DR
SCADASense 4202 DS
PPP
SCADASense 4203 DR
SCADASense 4203 DS
SCADAPack 350
SP 32
SP 32P
com1
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
None
None
com2
none
Xon/Xoff
none
Xon/Xoff
none
Xon/Xoff
none
Xon/Xoff
None
None
None
com3
None
com4
None
N/A
None
None
N/A
None
None
None
None
N/A
None
None
N/A
None
Modbus
RTU
None
None
None
Queued
Queued
None
Queued
Queued
None
Queued
Queued
N/A
Queued
Queued
N/A
Table 13: RX Flow Settings
The Tx Flow drop down menu selects the transmitter flow control for the selected port. Valid
selections depend on the protocol, controller type, and serial port, as shown in the table below. The
default selection is none.
Protocol
Modbus RTU
DF1 Full BCC
DF1 Full CRC
DF1 Half BCC
DF1 Half CRC
DNP
Controller
Micro16
SP
com1
None
None
com2
None
None
SP Plus
None
None
SP Light
None
None
SP LP
None
None
SP 100
SP 32
None
None
Ignore CTS
SP 32P
None
Ignore CTS
SCADASense 4202 DR
SCADASense 4202 DS
SCADASense 4203 DR
SCADASense 4203 DS
SCADAPack 350
None
None
None
Ignore
CTS
None
Ignore
CTS
None
None
None
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
com3
N/A
None
Ignore CTS
None
Ignore CTS
N/A
None
Ignore CTS
N/A
None
Ignore CTS
com4
N/A
N/A
None
Ignore CTS
None
Ignore CTS
N/A
N/A
None
Ignore CTS
N/A
None
Ignore CTS
N/A
None
None
Ignore CTS
None
N/A
None
None
N/A
45
Protocol
None
Modbus ASCII
Controller
Micro16
com1
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Ignore CTS
SP 32P
None
Ignore CTS
SCADASense 4202 DR
SCADASense 4202 DS
SCADASense 4203 DR
SCADASense 4203 DS
SCADAPack 350
N/A
com2
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Xon/Xoff
None
Ignore
CTS
None
Ignore
CTS
None
N/A
None
None
Ignore CTS
None
None
None
None
SP
SP Plus
SP Light
SP LP
SP 100
SP 32
com3
N/A
com4
N/A
None
Ignore CTS
None
Ignore CTS
N/A
N/A
None
Ignore CTS
None
Ignore CTS
N/A
None
Ignore CTS
N/A
N/A
None
Ignore CTS
None
Ignore CTS
N/A
None
Ignore CTS
N/A
N/A
N/A
Table 14: TX Flow Settings
The Port Type drop down menu selects the type of serial port. Valid selections depend on the serial
port and controller type as shown in the table below. The default selection is RS-232. The options
are as follows:
•
RS-232 for a regular RS-232 connection.
•
RS-232 Dial-up modem: If an external dial-up modem is used on the RS-232 connection.
This setting is required if the RTU is initiating a dialup connection through an external modem
connected to the corresponding serial port. For SCADASense controllers, the digital input point can
be used to provide a DCD signal, as required by the external modem.
•
RS-232 Collision Avoidance: RS-232 connection with collision avoidance based on the CD
signal is available only when the DNP protocol type is selected on the serial port, and the
serial port supports handshaking.
When this flow control is enabled, the protocol uses the Carrier Detect (CD) signal provided by the
serial port to detect if the communication medium is in use. If it is, it waits until the medium is free
before transmitting.
Prior to transmitting each Data Link (DL) frame, the controller will test the CD line. If it is active, a
countdown equal to the DL timeout will be set and CD will be monitored every 100 ms throughout
this countdown period. If the Data Link timeout is set to the minimum of 100 ms, the CD line will
be tested once.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
46
If the CD line reports inactive (line not in use), a frame will be transmitted immediately, and a new
DL timeout is started as normal. On the other hand, if CD remains active during the DL timeout, the
transmission attempt will fail. If a non-zero retry is configured in the Data Link layer, the test will
be repeated until the number of retries has been exhausted.
Note:
•
RS-232 Collision Avoidance is supported only on serial ports which support
handshaking and whose protocol type is set for DNP.
RS-485: for a regular RS-485 connection.
Controller Type
com1
com2, com4
com3
Micro16
SCADAPack
SCADAPack Plus
SCADAPack Light
RS-232
RS-232 dial-up modem
RS-232 Collision Avoidance
RS-485
RS-232
RS-232 dial-up modem
RS-232 Collision Avoidance
S-232
RS-232 dial-up modem
SCADAPack 32
SCADAPack 32P
RS-232
RS-232 dial-up modem
RS-232 Collision Avoidance
Note: com4 is available on
the SCADAPack Light and
Plus only.
RS-232
RS-232 dial-up modem
RS-232 Collision Avoidance
S-232
RS-232 dial-up modem
NOTE:
Port type RS-232 applies for
RS-232 or RS-485 operation
on COM1. Jumper J9 on the
controller board must be
installed to configure COM1
for RS-485 operation.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
47
Controller Type
SCADASense Programmable
Controllers
(4202 DR, 4202 DS, 4203 DR
and 4203 DS).
com1
N/A (RS-232)
com2, com3
RS-232
RS-232 Dialup Up Modem
(com 2 only)
NOTE:
RS-232 Port Type applies
for RS-232 or RS-485
operation.
SCADAPack 100
RS-232
RS-232 Collision Avoidance
NOTE:
Port type RS-232 applies for
RS-232 or RS-485 operation
on Com 1.
SCADAPack LP
RS-485
SCADAPack 350
RS-485
RS-232
RS-232 dial-up modem
RS-232 Collision
Avoidance
Com 3: not available
RS-232
RS-232 dial-up modem
RS-232 Collision
Avoidance
RS-232
RS-232 dial-up modem
RS-232 Collision
Avoidance
NOTE:
Port type RS-232 applies
for RS-232 or RS-485
operation on COM2.
Jumper J13 on the
controller board must be
installed to configure
COM2 for RS-485
operation.
Table 15: Serial Port Type
The Store and Forward drop down menu selects whether store and forward messaging is enabled
for the port. Valid selections are enabled and disabled. If this option is enabled, messages will be
forwarded according to the settings in the store and forward routing table. The default selection is
disabled. This control is disabled when PPP protocol is selected for a serial port, or if any of the DF1
protocols are selected and for Com2 and Com3 on the SCADASense series of controllers.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
48
The Store and Forward menu selection changes to Routing menu selection when DNP protocol is
selected for a serial port. Valid selections are enabled and disabled. Routing must be enabled on a
serial port to enable routing of DNP messages.
The Enron Modbus drop down menu selects whether Enron Modbus is enabled for the port. If this
option is enabled, the controller, in addition to regular Modbus messages, will handle Enron Modbus
messages. Valid selections depend on the protocol as shown in the table below. This control is
disabled when PPP protocol is selected for a serial port and for com 1 on the SCADASense series of
controllers.
Protocol
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
None
Valid Selections
Enabled
Disabled
Control is disabled
Default Selection
Disabled
N/A
Control is disabled
Control is disabled
N/A
N/A
Table 16: Enron Modbus Settings
The Enron Station entry selects the Enron Modbus station address for the serial port. Valid entries
depend on the protocol. The Enron station must be different from the Modbus station set in the
Station control. This ensures Enron Modbus and Modbus communication can occur on the same
port. This entry is greyed out if Enron Modbus is not enabled.
Protocol
Modbus RTU
Modbus ASCII
DF1 Full Duplex BCC
DF1 Full Duplex CRC
DF1 Half Duplex BCC
DF1 Half Duplex CRC
DNP
None
Valid Values
Standard addressing:
1 to 255
Extended addressing:
1 to 65534
Control is disabled
Default Value
2
N/A
Control is disabled
Control is disabled
N/A
N/A
Table 17: Enron Modbus Station Settings
•
The OK button saves the settings for all serial ports and closes the dialog.
•
The Cancel button closes the dialog without saving.
•
The Default button sets the parameters for the port to their default values.
5.3
IP Configuration
When the IP Configuration menu item is clicked under the Controller menu the IP Configuration
dialog is opened. This dialog is available only when the controller type is set to SCADAPack 350,
SCADAPack 32 or SCADAPack 32P.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
49
The IP Configuration dialog has a tree control on the left side of the window. The SCADAPack 32
and SCADAPack 32P support Point-To-Point Protocol (PPP) on the serial ports. The tree control
displays headings for com 1 Port through com 4 Port and PPP Login are displayed for configuring
the serial ports for PPP. The SCADAPack 350 does not support PPP on the serial ports and the
headings for com 1 Port through com 4 Port and PPP Login are not displayed.
Each of the tree control selections is explained in the following sections of this user manual.
This tree control for the SCADAPack 32 and SCADAPack 32P contains headings for:
•
•
•
•
•
•
•
•
•
•
•
•
•
LAN Port
com 1 Port
com 2 Port
com 3 Port
com 4 Port
PPP Login
Modbus Common
Modbus/TCP
Modbus RTU in UDP
Modbus ASCII in UDP
DNP in TCP
DNP in UDP
Friendly IP List
This tree control for the SCADAPack 350 contains headings for:
•
•
•
•
•
•
•
•
LAN Port
Modbus Common
Modbus/TCP
Modbus RTU in UDP
Modbus ASCII in UDP
DNP in TCP
DNP in UDP
Friendly IP List
When a tree control is selected by clicking the mouse on a heading, a property page is opened for the
header selected. From the property page the IP configuration parameters for the selected header is
displayed.
The Default button selects the default values for the current property page.
The OK button saves the configuration and closes the Controller IP Configuration dialog.
The Cancel button closes the Controller IP Configuration dialog without saving any changes.
5.3.1
LAN Port
The LAN Port property page is selected for editing by clicking LAN Port in the tree control section
of the Controller IP Configuration dialog. When selected the LAN Port property page is active.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
50
Figure 19: Controller IP Configuration – LAN Port Dialog Box
The IP Address is the address of the controller LAN port. The IP address is statically assigned.
Contact your network administrator to obtain an IP address for the controller. The default value is
0.0.0.0.
The Subnet Mask is determines the subnet on which the controller LAN port is located. The subnet
mask is statically assigned. Contact your network administrator to obtain the subnet mask for the
controller. The default value is 255.255.255.0.
The Gateway determines how your controller communicates with devices outside its subnet. The
LAN radio button selects the gateway specified in the LAN edit box. Enter the IP address of the
gateway. The gateway is located on the LAN port subnet. The gateway is statically assigned. Contact
your network administrator to obtain the gateway IP address. The default value is 0.0.0.0.
The PPP radio button selects the serial port where the gateway is located. The PPP drop down menu
displays only those serial ports currently configured for the PPP protocol. Select a serial port from
this menu to select its remote IP address as the gateway. The gateway is automatically assigned to
the remote IP address of the selected serial port.
5.3.2
com1 Port
The com1 Port property page is selected for editing by clicking com1 Port in the tree control section
of the Controller IP Configuration dialog. When selected the com1 Port property page is active. This
page configures the IP settings for com1 when the PPP protocol is selected for this serial port.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
51
Figure 20: Controller IP Configuration – com1 Port Dialog Box
The Enable Auto Answer (PPP Server) checkbox enables the PPP Server on this serial port. Check
this box if you want to allow a remote PPP client to connect to this port. This checkbox enables the
remaining settings in the page.
The IP Address is the address of this serial port. The IP address is statically assigned. Contact your
network administrator to obtain an IP address for this serial port.
The Subnet Mask determines the subnet on which this serial port is located. The subnet mask is
statically assigned. Contact your network administrator to obtain the subnet mask for this serial port.
In a standard PPP configuration, a subnet mask of 255.255.255.255 is used to restrict routing on this
serial port to a single host (i.e. the Remote IP Address).
If another subnet mask is used, all packets on that subnet will be forwarded to this serial port. Any
address on that subnet in addition to the Remote IP Address can be used for the remote host in this
case.
The Remote IP Address is the address that will be assigned to the remote PPP client connected to
this serial port. The Automatic radio button automatically selects the address to be the serial port’s
IP address + 1. The second radio button selects the address specified in the edit box. Enter the IP
address to assign to the remote client.
The Allow remote to specify its own IP address checkbox allows the remote PPP client to assign
its own IP address. Check this box if you want to allow this option. Note that the client may or may
not request its own IP address. If the client does not make this request, the PPP Server will assign the
IP address selected.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
52
The Authentication determines the login protocol used at the start of every PPP connection. The
None radio button removes the login step. The PAP radio button selects the Password
Authentication Protocol (PAP). The CHAP radio button selects the Challenge-Handshake
Authentication Protocol (CHAP). PAP and CHAP usernames and passwords are configured on the
PPP Login page.
The Inactivity Timeout is the inactivity timeout for this serial port. If there has been no activity on
an existing PPP connection for the selected number of minutes, then the connection is automatically
closed. If there is a modem connected it is hung up. Setting this value to zero disables the timeout.
5.3.3
com2 Port
The com2 Port property page is selected for editing by clicking com2 Port in the tree control section
of the IP Configuration dialog. When selected the com2 Port property page is active. This page
configures the IP settings for com2 when the PPP protocol is selected for this serial port.
The com2 Port property page provides the same options as the com1 Port page. See the com1 Port
page for a description of these options.
5.3.4
com3 Port
The com3 Port property page is selected for editing by clicking com3 Port in the tree control section
of the IP Configuration dialog. When selected the com3 Port property page is active. This page
configures the IP settings for com3 when the PPP protocol is selected for this serial port.
The com3 Port property page provides the same options as the com1 Port page. See the com1 Port
page for a description of these options.
5.3.5
com4 Port
The com4 Port property page is selected for editing by clicking com4 Port in the tree control section
of the IP Configuration dialog. When selected the com4 Port property page is active. This page
configures the IP settings for com4 when the PPP protocol is selected for this serial port.
The com4 Port property page provides the same options as the com1 Port page. See the com1 Port
page for a description of these options.
5.3.6
PPP Login
The PPP Login property page is selected for editing by clicking PPP Login in the tree control section
of the IP Configuration dialog. When selected the PPP Login property page is active.
This page configures the username and password list for PPP login authentication. The list is used
only by those serial ports configured for the PPP protocol using PAP or CHAP authentication.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
53
Figure 21: Controller IP Configuration – PPP Login Dialog Box
•
Click Add to enter a new username to the list. Selecting the Add button opens the Add PPP
Username dialog.
•
Click Edit to edit the username highlighted in the list. Selecting the Edit button opens the Edit
PPP Username dialog. This button is disabled if there are no entries in the list.
•
Click Delete to remove the selected usernames from the list. This button is disabled if there are
no entries in the list.
5.3.6.1
Add PPP Username dialog
This dialog selects a new PPP username and password.
Figure 22: Add PPP User Name Dialog Box
The Username edit box selects the username. A username is any alphanumeric string 1 to 16
characters in length, and is case sensitive.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
54
The Password edit box selects the password. A password is any alphanumeric string 1 to 16
characters in length, and is case sensitive.
The Verify Password edit box selects the verify password. Enter the same string entered for the
password.
The Cancel button discards any changes made to this dialog and exits the dialog.
The OK button to accepts all changes made to this dialog and exits the dialog.
5.3.6.2
Edit PPP Username dialog
This dialog edits a PPP username and password selected from the list.
Figure 23: Edit PPP User Name Dialog Box
The Username edit box selects the username. A username is any alphanumeric string 1 to 16
characters in length, and is case sensitive.
The Password edit box selects the password. A password is any alphanumeric string 1 to 16
characters in length, and is case sensitive.
The Verify Password edit box selects the verify password. Enter the same string entered for the
password.
The Cancel button discards any changes made to this dialog and exits the dialog.
The OK button to accepts all changes made to this dialog and exits the dialog.
5.3.7
Modbus Common
The Modbus Common property page is selected for editing by clicking Modbus Common in the tree
control section of the IP Configuration dialog. When selected the Modbus Common property page is
active.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
55
Figure 24: Controller IP Configuration - Modbus Common Dialog Box
The Addressing menu selects standard or extended Modbus addressing. Standard addressing allows
255 stations and is compatible with standard Modbus devices. Extended addressing allows 65534
stations, with stations 1 to 254 compatible with standard Modbus devices. The default value is
standard.
The Station menu sets the station number of the controller. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default value is 1.
The Store and Forward selection controls forwarding of messages using IP based protocols. If this
option is enabled, messages will be forwarded according to the settings in the store and forward
routing table. The default value is disabled.
The Enron Modbus box selects whether Enron Modbus is enabled for the port. If this option is
enabled, the controller, in addition to regular Modbus messages, will handle Enron Modbus
messages.
The Enron Station box selects the Enron Modbus station address. The valid range for Enron Station
is 1 to 255 if the Addressing control is set to Standard. The valid range for Enron Station is 1 to
65534 if the Addressing control is set to Extended. The Enron station must be different from the
Modbus station set in the Station edit box. This ensures Enron Modbus and Modbus communication
can occur on the same port.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
56
5.3.8
Modbus/TCP
The Modbus/TCP property page is selected for editing by clicking Modbus/TCP in the tree control
section of the IP Configuration dialog. When selected the Modbus/TCP property page is active.
Figure 25: Controller IP Configuration - Modbus/TCP Dialog Box
The Server selection selects whether the server is enabled. If this option is enabled the controller
supports incoming slave messages. Disabling this option prevents the controller from processing
slave messages. Master messaging is always enabled.
The Master Idle Timeout determines when connections to a slave controller are closed. Setting this
value to zero disables the timeout; the connection will be closed only when your program closes it.
Any other value sets the timeout in seconds. The connection will be closed if no messages are sent in
that time. This allows the slave device to free unused connections. Valid timeout range is 0 to
4294967295 seconds. The default value is 10 seconds.
The Server Idle Timeout determines when connections from a remote device are closed. Setting this
value to zero disables the timeout; the connection will be closed only when the remote device closes
it. Any other value sets the timeout in seconds. The connection will be closed if no messages are
received in that time. This allows the controller to free unused connections. Valid timeout range is 0
to 4294967295 seconds. The default value is 250 seconds.
The TCP Port sets the port used by the Modbus/TCP protocol. In almost all cases this should be set
to 502. This is the well-known port number for Modbus/TCP. Modbus/TCP devices use 502 by
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
57
default, and on many devices the value cannot be changed. It is suggested that you change this value
only if this port is used by another service on your network. Valid port number range is 1 to 65534.
Consult your network administrator to obtain a port if you are not using the default.
5.3.9
Modbus RTU in UDP
The Modbus RTU in UDP property page is selected for editing by clicking Modbus RTU in UDP in
the tree control section of the IP Configuration dialog. When selected the Modbus RTU in UDP
property page is active.
Figure 26: Controller IP Configuration Modbus RTU in UDP Dialog Box
The Server selection selects whether the server is enabled. If this option is enabled the controller
supports incoming slave messages. Disabling this option prevents the controller from processing
slave messages. Master messaging is always enabled.
The UDP Port sets the port used by the protocol. Valid port number range is 1 to 65534. The default
value is 49152. This is a recommendation only. Consult your network administrator to obtain a port
if you are not using the default.
5.3.10
Modbus ASCII in UDP
The Modbus ASCII in UDP property page is selected for editing by clicking Modbus ASCII in UDP
in the tree control section of the IP Configuration dialog. When selected the Modbus ASCII in UDP
property page is active.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
58
Figure 27: Controller IP Configuration – Modbus ASCII in UDP Dialog Box
The Server selection selects whether the server is enabled. If this option is enabled the controller
supports incoming slave messages. Disabling this option prevents the controller from processing
slave messages. Master messaging is always enabled.
The UDP Port sets the port used by the protocol. Valid port number range is 1 to 65534. The default
value is 49153. This is a recommendation only. Consult your network administrator to obtain a port
if you are not using the default.
5.3.11
DNP in TCP
The DNP in TCP property page is selected for editing by DNP in TCP in the tree control section of
the IP Configuration dialog. When selected the DNP in TCP property page is active.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
59
Figure 28: Controller IP Configuration – DNP in TCP Dialog Box
The Protocol selection selects whether the DNP in TCP protocol is enabled. If this option is enabled
the controller supports DNP in TCP protocol. Disabling this option prevents the controller from
processing DNP in TCP protocol messages. Master messaging is always enabled. The default
selection is disabled.
The Server Idle Timeout determines when connections from a remote device are closed. Setting this
value to zero disables the timeout; the connection will be closed only when the remote device closes
it. Any other value sets the timeout in seconds. The connection will be closed if no messages are
received in that time. This allows the controller to free unused connections. Valid timeout range is 0
to 4294967295 seconds. The default value is 250 seconds.
The Master Idle Timeout determines when connections to a slave controller are closed. Setting this
value to zero disables the timeout; the connection will be closed only when your program closes it.
Any other value sets the timeout in seconds. The connection will be closed if no messages are sent in
that time. This allows the slave device to free unused connections. Valid timeout range is 0 to
4294967295 seconds. The default value is 10 seconds.
The TCP Port sets the port used by the DNP in TCP protocol. Valid port number range is 1 to
65534. The default value is 20000. Consult your network administrator to obtain a port if you are not
using the default.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
60
5.3.12
DNP in UDP
The DNP in UDP property page is selected for editing by DNP in UDP in the tree control section of
the IP Configuration dialog. When selected the DNP in UDP property page is active.
Figure 29: Controller IP Configuration – DNP in UDP Dialog Box
The Protocol selection selects whether the DNP in UDP protocol is enabled. If this option is enabled
the controller supports DNP in UDP protocol. Disabling this option prevents the controller from
processing DNP in UDP protocol messages and sending DNP in UDP master messages. The default
selection is disabled.
The UDP Port sets the port used by the DNP in UDP protocol. Valid port number range is 1 to
65534. The default value is 20000. Consult your network administrator to obtain a port if you are not
using the default.
5.3.13
Friendly IP List
The Friendly IP property page is selected for editing by Friendly IP in the tree control section of the
IP Configuration dialog.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
61
Figure 30: Controller IP Configuration – Friendly IP List Dialog Box
The Enable Friendly IP List checkbox enables or disables the friendly IP list. Check this box to
accept messages from only the IP addresses in the list. Uncheck this to accept message from all IP
addresses.
Click Add to enter a new row in the Friendly IP list. Selecting the Add button opens the Add
Friendly IP address dialog. The button is disabled if the Enable Friendly IP List control is not
checked. The button is disabled if the table is full. Up to 32 entries can be added to the table.
Click Edit to edit range in the Friendly IP list. Selecting the Edit button opens the Edit Friendly IP
address dialog. The button is disabled if the Enable Friendly IP List control is not checked.
The Delete button removes the selected rows from the list. This button is disabled if there are no
entries in the list. The button is disabled if the Enable Friendly IP List control is not checked.
Click on the column headings to sort the list by that column. Click a second time to reverse the sort
order. The order is indicated by the triangle next to the text.
The settings are verified when the OK button is pressed or another settings page is selected.
An error message is displayed if the friendly IP list is enabled and the list is empty.
A warning message is displayed if the IP address of the PC is not in the friendly IP table.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
62
5.3.13.1
Add Friendly IP Address Range Dialog
The Add Friendly IP Address Range dialog specifies an IP address range to add to the Friendly IP
list.
Figure 31: Add Friendly IP Address Range Dialog Box
Start Address specifies the starting IP address in the range. Enter any valid IP address.
End Address specifies the ending IP address in the range. Enter a valid IP address that is
numerically greater than or equal to the IP Start Address. This field can be left blank if only a single
IP address is required.
The OK button adds the IP address range to the list and closes the dialog. An error is displayed if the
address range is invalid.
The Cancel button closes the dialog without making any changes.
5.4
Register Assignment
The Register Assignment dialog displays the current register assignment list. The user may edit the
list or the entries in the list.
Figure 32: Register Assignment Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
63
The main portion of the dialog is a list showing the modules in the register assignment list. The
module list displays the Module, Module Address, Start Register, End Register and the number of
Registers for the module.
The Module field displays the type and name of I/O modules that have been added to the Register
Assignment. For modules that support more than one type of I/O, there are multiple lines in the row
of the table, one for each input or output I/O type.
The Address field displays the unique module address of the physical hardware, such as a 5000
Series 5401 Digital I/O module. Some module types have no address that can be set by the user. The
address is blank for these modules.
The Start Register field displays the first register address in the I/O database where the module data
is stored. A start register is required for each type of input or output on the module.
The End Register field displays the last address in the I/O database used by the module. An end
register is required for each type of input or output on the module.
The Registers field displays the number of registers used by the module. A size is required for each
type of input or output on the module.
The I/O Module Error Indication check box determines if the controller displays I/O module
communication errors. If enabled, the controller will blink the Status LED if there is an I/O error.
See the DIAG Controller Status Code diagnostic module for information on the controller status
code. If disabled, the controller will not display the module communication status. The module
communication status is always checked. This option controls only the indication on the Status LED.
The Sort by: window selects how the Register Assignment List is sorted. The selections
are: Module, Start Register, or Address.
Click OK to update the register assignment list and close the dialog.
If the register assignment is changed it is written to the controller as follows.
If TelePACE is Off Line the changes are not written.
If TelePACE is On Line, the changes are downloaded automatically.
Selecting Cancel exits the dialog without saving changes. If changes were made, the user is
prompted for confirmation before exiting. This protects against accidentally discarding a large
number of changes. Press ESC to Cancel.
If changes were made the following dialog appears.
Figure 33: Cancel Register Assignment Dialog Box
Click Yes to close the Register Assignment dialog and the register assignment list is not changed.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
64
Click No to return to the Register Assignment dialog. No is the default selection. Press Enter or
ESC to select No.
Click Add to open the Edit Register Assignment dialog. The Add function adds a new module to the
register assignment.
Click Add Copy to open the Edit Register Assignment dialog. The Address field is set to the first
unused address for the currently selected module type. All other fields are set to the values from the
currently selected I/O module. The Add Copy button is grayed if:
•
the table is empty,
•
all I/O modules of the given type are in use (i.e. modules are already defined for all possible
addresses for the selected module type),
Selecting Edit opens the Edit Register Assignment dialog. All fields are set to the values from the
currently selected I/O module. The Edit button is grayed if:
•
the table is empty,
•
no module is selected in the table.
The Delete function removes the selected module from the register assignment. The Delete button is
grayed if:
•
the table is empty,
•
no module is selected in the table.
Selecting the Undo button undoes the last change to the register assignment list. A single level of
undo is provided. Selecting the Undo function a second time, restores the list to its state before the
first Undo.
The Default function replaces the current Register Assignment with the Default Register Assignment
for the controller type selected.
If the controller is a SCADAPack or SCADAPack 32 the following prompt is displayed.
Figure 34: Select Register Assignment Option Dialog Box
Select the I/O module, 5601, 5604 or 5606 that you are using in your controller and click OK.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
65
If the controller type is a SCADASense 4202 DR, the following dialog appears.
Figure 35: Register Assignment Dialog Box
5.4.1
Edit Register Assignment Dialog
The Edit Register Assignment dialog modifies an entry in the register assignment. The following
example shows the dialog editing a module with more than one I/O type.
Figure 36: Edit Register Assignment Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
66
The Module drop-down list box shows the current module type. The drop-down list displays all
available modules. If the maximum number of modules of a particular I/O module type is already
configured, no modules of this class are shown in the drop-down list.
The Address drop-down list box shows the current module address. The drop-down list displays all
addresses valid for the current module type that are not already used. If all addresses are in use, the
list will be empty.
There are up to four Type description fields. The text displays the type of the input or output
register. The type descriptions are 0xxxx, 1xxxx, 3xxxx and 4xxxx.
•
Digital output data is read from coil (0xxxx) registers. The digital outputs are updated
continuously with data read from the coil registers.
•
Digital input data is stored in status (1xxxx) registers. The status registers are updated
continuously with data read from the digital inputs.
•
Analog input data is stored in input (3xxxx) registers. The input registers are updated
continuously with data read from the analog inputs.
•
Analog output data is stored in holding (4xxxx) registers. The analog output registers are
updated continuously with data read from the holding registers.
The Start edit box holds the starting register in the I/O database for the I/O type. The edit box allows
any number to be entered.
The End field shows the last register used by the module for the I/O type. TelePACE automatically
fills this field.
The Registers field shows the number of registers in the I/O module. TelePACE automatically fills
this field
The Description field displays the I/O type for multiple I/O modules. TelePACE automatically fills
this field
The Extended Parameters window will contain I/O module extended parameters if they are used.
Extended parameters may include such items as analog input type for example. Refer to the Register
Assignment Reference for information on all I/O modules.
Selecting OK checks the data entered. If the data is correct the dialog is closed and the Register
Assignment dialog returns with the changes made. If any data is incorrect, a beep will sound and the
cursor will select the field containing the first error found. Press ENTER to select OK.
Click Cancel to exit the dialog without saving changes. Press ESC to select Cancel.
5.5
Outputs On Stop
Select Outputs on Stop command and the Output Conditions on Program Stop dialog appears. This
dialog controls the state of the controller analog and digital outputs when the ladder logic program is
stopped.
The state of the digital outputs may be set to Hold their last value or to turn Off when the ladder
program is stopped.
The state of the analog outputs may be set to Hold their last value or to go to Zero when the ladder
program is stopped.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
67
Figure 37: Output Conditions on Program Stop Dialog Box
The Digital Output drop-down list box specifies the state of the digital outputs. It has two options:
Hold and Off.
The Analog Output drop-down list box specifies the state of the analog outputs. It has two options:
Hold and Zero.
5.6
Store and Forward
The Store and Forward command is used to configure store and forward messaging. A controller
configured for store and forward operation receives messages destined for a remote Slave Station on
the Slave Interface. The controller forwards the message on the Forward Interface to the Forward
Station.
Note: This command is available only when the controller type is set to SCADAPack 350,
SCADAPack 32 or SCADAPack 32P.
Refer to the following diagram as a reference for the terminology used in the following Store and
Forward command reference.
Slave Interface
The Ethernet port is set for Modbus
address 2. The local SCADAPack
32 will respond to all messages
received for address 2.
Messages that require forwarding
must not be addressed for station
2.
SCADAPack 32
Controller
Communication
Interfaces
LAN
Message to be Forwarded
The message, from a remote master station,
that is to be forwarded by the SCADAPack 32
controller.
The station address of the message must be in
the Store and Forward table. In this example the
station address must not be 2.
COM1
COM2
COM4
Forward Interface
COM port 4 is set for Modbus
address 2. The local SCADAPack
32 will respond to all messages
received for station 2. Messages
that are forwarded must not be
addressed for station 2.
Forwarded Message
The forwarded message, to the remote slave
station, that is forwarded by the SCADAPack
32 controller.
The station address of the message must be in
the Store and Forward table. In this example
the station address must not be 2.
Figure 38: Store and Forward Command Reference
When the Store and Forward command is selected the Store and Forward dialog appears. This dialog
displays the Store and Forward table for the controller.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
68
Figure 39: Store and Forward Dialog Box
The Store and Forward table displays each Store and Forward translation as a row, with column
headings, in the table. The table may have up to 128 entries. A vertical scroll bar is used if the list
exceeds the window size.
The Slave Interface heading displays the receiving slave interface the message is received from for
each translation.
The Slave Station heading displays the Modbus station address of the slave message.
The Forward Interface heading displays the interface the message is forwarded from. When
forwarding to a Modbus TCP or UDP network, the protocol type is selected for the Forward
Interface. The IP Stack automatically determines the exact interface (e.g. LAN/PPP) to use when it
searches the network for the Forward IP Address. If a serial port is selected for the Forward
Interface, and the serial port is configured for PPP protocol, the message will not be forwarded.
The Forward Station heading displays the Modbus station address of the forwarded message.
The Forward IP Address heading displays the IP address of the Forward Station. This field is blank
unless a TCP or UDP network is selected for Forward Interface.
The Time Out heading displays the maximum time (in tenths of seconds) the forwarding task waits
for a valid response from the Forward Station. The time out should be equal to or less than the time
out set for the master message received on the Slave Interface.
The OK button saves the table data. No error checking is done on the table data.
The Cancel button closes the dialog without saving changes.
Click Add to enter a new row in the store and forward table. Selecting the Add button opens the
Add/Edit Store and Forward dialog.
Click Edit to modify the selected row in the store and forward table. Selecting the Edit button opens
the Add/Edit Store and Forward dialog containing the data from the selected row. This button is
disabled if more than one row is selected. This button is disabled if there are no entries in the table.
The Delete button removes the selected rows from the table. This button is disabled if there are no
entries in the table.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
69
The Undo button undoes the action performed by the last button selection since the dialog was
opened. This applies to the buttons Add, Edit, Delete and Undo. This button is disabled when the
dialog is opened, and is enabled as soon as any of the applicable buttons are selected.
The Sorted by menu box lists each of the five column headings. The rows are sorted according to
the selected heading. Headings in the table are, by default, sorted by the Slave Interface heading.
5.6.1
Add/Edit Store and Forward Dialog
This dialog is used to edit an entry or add a new entry in the store and forward table.
Figure 40: Add/Edit Store and Forward Dialog Box
The Slave Interface is the receiving slave interface the message received from. The drop down list
allows the following selection:
•
com1
•
com2
•
com3
•
com4
•
LAN/PPP
The Slave Station is the Modbus station address of the slave message. This address must be different
from the Modbus address assigned to the Slave Interface. Valid range for Slave Station is:
1 to 255 when standard addressing is selected for the interface.
1 to 65534 when extended addressing is selected for the interface.
The Forward Interface is the interface the message is forwarded from. The drop down list allows
the following selection:
•
com1
•
com2
•
com3
•
com4
•
Modbus/TCP
•
Modbus RTU in UDP
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
70
•
Modbus ASCII in UDP
The Forward Station is the Modbus station address of the forwarded message. This address must be
different from the Modbus address assigned to the Forward Interface. Valid range for Forward
Station is:
1 to 255 when standard addressing is selected for the interface.
1 to 65534 when extended addressing is selected for the interface.
The Forward IP Address edit box is disabled and the address is forced to “0.0.0.0“ whenever the
Forward Interface is set to com1, com2, com3 or com4. The Forward IP Address edit box is enabled
only when the Forward Interface is set to a TCP or UDP network. Valid entries are 0 to 255 for each
byte in the IP address.
The Time Out is the maximum time the forwarding task waits for a valid response from the
Forward Station, in tenths of second. Valid entries are 0 to 65535. The time out should be equal to or
less than the time out set for the master message received on the Slave Interface.
The OK button checks the data for this table entry. If the data is valid the dialog is closed. If the
table data entered is invalid, an error message is displayed and the dialog remains open. The table
entry is invalid if any of the fields is out of range. The data is also invalid if it conflicts with another
entry in the table.
The Cancel button closes the dialog without saving changes.
5.7
DNP
The DNP command is used to configure the DNP protocol settings for the controller. When selected
the DNP Settings window is opened, as shown below.
For complete information on DNP configuration refer to the DNP 3 User and Reference Manual.
5.8
DNP Status
The DNP Status command opens the DNP Status dialog. This dialog shows the run-time DNP
diagnostics and current data values for the local DNP points.
For complete information on the DNP Status command refer to the DNP 3 User and Reference
Manual.
5.9
DNP Master Status
The DNP Status command opens the DNP Master Status dialog. This dialog shows the runtime DNP diagnostics and status of the DNP outstations defined in the Master Poll table and
current data values for the DNP points in these outstations.
For complete information on the DNP Status command refer to the DNP 3 User and Reference
Manual.
5.10
Initialize
The initialize command is used to restore a controller to default settings. This is typically done when
starting a new project with a controller. The Initialize controller dialog is displayed when this
command is selected. The Initialize Controller dialog presented depends on the type of controller
selected. The dialog is different between the SCADAPack 32 or SCADAPack series controllers
(Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus, SCADAPack 100, SCADAPack
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
71
350, and the SCADASense Series of programmable controllers (4202 DR, 4202 DS, 4203 DR and
4203 DS). The different dialogs are described in the following sections.
5.10.1
SCADAPack and SCADAPack 32 Controllers
The Initialize Controller dialog shown below appears when the command is selected and the
Controller Type is SCADAPack or SCADAPack 32 (not SCADAPack 350).
Figure 41: Initialize Controller Dialog Box SCADAPack and SCADAPack 32 Controllers
Check the Erase Ladder Logic Program selection to erase the ladder logic program in the
controller RAM memory.
Check the Erase C Program selection to erase the C application program in the controller RAM
memory.
Check the Initialize Controller selection to reset all values in the I/O database to default settings.
The Initialize controller command will do the following:
•
The default communication parameters are set for all serial ports. If you are communicating
using settings other than the default, the PC Communication Settings will have to be changed
once the command is complete. Note that the Ethernet port on SCADAPack 32 controllers is not
changed by the initialize controller command.
•
The registers in the I/O database are initialized to their default values.
•
All forcing is removed.
•
The controller is unlocked.
Check the Erase Register Assignment selection to erase the controller register assignments. The
Register Assignment is cleared and must be reconfigured.
Check the Erase Ladder Logic Flash selection to erase the Ladder Logic program in Flash. This
control is greyed if the controller firmware does not support programs in Flash or if the Flash is used
by the operating system.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
72
Check the Erase C Program Flash selection to erase the C program in Flash. This control is greyed
if the controller firmware does not support programs in Flash or if the Flash is used by the operating
system.
•
Click OK to perform the requested initializations.
•
Click Cancel to exit without performing any action.
Erasing Programs in Flash
Erasing the Flash memory requires the Ladder Logic and C programs be stopped. The following
message is displayed if the OK button is selected.
Figure 42: Initialize Controller Dialog Box
•
Click OK to stop the execution and erase the flash memory. The following actions occur.
The Ladder Logic and C programs in the controller are stopped.
If it was selected, the Ladder Logic program is erased.
If it was selected, the C program is erased.
Programs that were stopped to allow Flash to be erased are not re-started. These programs must be
re-started.
5.10.2
SCADAPack 350 and SCADASense 4203 Series of Controllers
For SCADAPack 350 and SCADASense 4203 Series of controllers (4203 DR and 4203 DS), the
Initialize dialog shown below appears when the command is selected.
Figure 43: Initialize Dialog for SCADAPack 350 and SCADASense 4203 Series Controllers
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
73
Select the Initialize All to Factory Settings radio button to erase all programs in the controller
memory and initialize the controller to factory settings. Please see Actions Performed when
Controller is Initialized below for details. Erasing all programs includes all C/C++ programs, the
Ladder Logic program in RAM, and the Ladder Logic program in ROM, if applicable.
Select the Initialize radio button to initialize only the selected items. The items that may be selected
are as follows:
•
Check the Erase Ladder Logic Program and Register Assignment selection to erase the
ladder logic program and register assignment in the controller RAM memory.
•
Check the Erase All C/C++ Programs selection to erase all C/C++ programs in the
controller.
•
Check the Erase Ladder Logic Flash selection to erase the Ladder Logic program in Flash
(ROM).
•
Check the Initialize Controller selection to initialize the controller to default settings.
Please see Actions Performed when Controller is Initialized below for details. The default
settings used depends on the radio button selected below this selection:
•
Click on the OK button to perform the requested initializations.
•
Click on the Cancel button to exit without performing any action.
5.10.2.1 Actions Performed when Controller is Initialized
The following actions are performed when the controller is initialized:
•
The controller settings below are set to default values. If you are communicating using settings
other than the default, the PC Communication Settings will have to be changed once the
command is complete. Note that the Ethernet port is not changed by the initialize controller
command.
•
Serial port communication parameters
•
Modbus/IP and DNP/IP protocol settings
•
Outputs on Stop settings
•
HART modem configurations
•
LED power control
•
All forcing is cleared.
•
All Modbus registers are set to zero.
•
If there is a register assignment, the assigned registers are initialized to their default values. For
example, if a configuration module for a group of controller settings is in the register
assignment, the assigned registers are initialized to the default values for those controller
settings.
•
All digital outputs and analog outputs are cleared.
•
Data logged by all DLOG functions is erased.
•
Alarm clock is cleared.
•
Serial port event counters are cleared.
•
Store and forward table is cleared.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
74
•
Friendly IP List is cleared.
•
The power mode changes to full power.
5.11
Real Time Clock
The Real Time Clock command is used to set the controller Real Time Clock. The user may set the
clock to the PC time, to a user specified time or adjust the clock forward or back by a number of
seconds. The Real Time Clock Setting dialog shown below appears when the command is selected.
Figure 44: Real Time Clock Setting Dialog Box
The following controls are available from the Real Time Clock Setting dialog.
Controller time shows the current time and date in the controller. It is updated continuously while
the dialog is open. The time and date are displayed in the short time format as defined in the
Windows Control Panel.
The Set to PC Time radio button selects setting the controller time to match the PC time. The
current PC time and date are shown to the right of the button. The time and date are displayed in the
short format as defined in the Windows Control Panel.
The Set to User Entered Time radio button selects setting the time and date to the values specified
by the user in the Year, Month, Day, Hour, Minute and Second controls. The valid values for entry
are shown in the dialog. If the Set to User Entered Time radio button is not selected these controls
are grayed.
The Adjust Forward or Backward radio button selects adjusting the time by the number of seconds
specified in the Adjust Clock by Seconds edit box. The value can be negative or positive. The edit
box is grayed if the Adjust by radio button is not selected.
•
The Close button closes the dialog.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
75
•
The Write button writes the selected time to the controller.
5.12
Monitor Element
The Monitor Element command is used to add registers used by selected elements to the Register
Editor. All registers used by the currently selected element, or elements, are added to the Register
Editor. This command is available only if an element, or multiple elements, is selected.
This command may be selected by right click your mouse button on a highlighted element, or group
of elements, and selecting Monitor Element from the list of commands.
To add registers to the Register Editor using the Monitor Registers command first highlight an
element by clicking the left mouse button on an element or dragging the cursor over a group of
elements. Then select the Monitor Element command from the Controller menu or from the mouse
right click menu.
When the Monitor Element command is selected the Monitor Element dialog is displayed.
Figure 45: Monitor Element Dialog Box
The Add to Group list box selects which group the registers are added to. A drop down selection
displays all created groups. If no groups have been created use the New Group button to add a
Register Editor group.
The OK button adds the registers and closes the dialog. The registers are added to the Register
Editor in the format used by the selected element or elements.
The Available status is set to Online for all registers except registers contained in elements that use
Element Configuration.
The Available status is set to Always for all registers contained in elements that use Element
Configuration.
The Cancel button closes the dialog without adding the registers to the Register Editor.
The New Group button opens New group dialog. This dialog is used to create a new group in the
Register Editor.
Figure 46: New Group Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
76
The Group edit box is used to enter the name of the new group. The group name may contain letters,
numbers, and spaces. The group name may be 1 to 16 characters long and the name is not case
sensitive.
The OK button creates the new group and closes the dialog. If the group name already exists an error
message is displayed and the dialog remains open.
The Cancel button closes the dialog.
5.13
List Force Registers
The List Forced Registers command displays the Forced Registers dialog. This dialog displays a list
of registers that are forced. The user may view and edit the registers, add registers to the list, remove
registers from the list and clear all forces. The dialog appears as shown below.
Figure 47: Forced Registers Dialog Box
The Register list box shows all registers in the controller that are currently forced.
Click Close to close the dialog box. Press ESC to select Close.
Selecting the Remove All button clears the force status for all registers. All registers are removed
from the register list box. When selected the user is prompted for confirmation.
Figure 48: Remove All Forces Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
77
Selecting Yes removes all forcing. Selecting No aborts the command. The No button is the default
selection. Press ENTER or ESC to select No. This button is grayed when there are no registers in
the register list box.
The Remove Force button clears the force status for the selected register. The register is removed
from the register list box. This button is grayed when there are no registers in the register list box.
5.14
Remove All Forces
Selecting the Remove All Forces command clears the force status for all forced registers. This
command is only available in the on-line mode.
Selecting Remove All Forces prompts the user for confirmation:
Figure 49: Remove All Forces Dialog Box
•
Selecting Yes removes all forcing.
•
Selecting No aborts the command. The No button is the default selection. Press ENTER or ESC
to select No.
5.15
Lock Controller
Locking a controller prevents unauthorized access. Commands sent to the controller when it is
locked will be rejected. A controller that is unlocked operates without restriction.
The Lock Controller dialog specifies a password to be used to lock the controller and the commands
that are locked.
Figure 50: Lock Controller Dialog Box
Enter a password in the Password edit box. Re-enter the password in the Verify Password edit box.
Any character string up to eight characters in length may be entered. Typing in these edit boxes is
masked. An asterisk is shown for each character typed.
The Prevent radio buttons select the commands that are locked.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
78
Locking the programming commands prevents modifying or viewing the program in the controller.
Communication protocols can read and write the I/O database.
Locking programming and database write commands prevents modifying or viewing the program
and prevents writing to the I/O database. Communication protocols can read data from the I/O
database, but cannot modify any data.
Locking programming and database commands prevents modifying or viewing the program and
prevents reading and writing the I/O database. Communication protocols cannot read or write the I/O
database.
The OK button verifies the passwords are the same and sends the lock controller command to the
controller. The dialog is closed. If the passwords are not the same an error message is displayed.
Control returns to the dialog.
The Cancel button closes the dialog without any action.
If the controller is already locked, a message indicating this is shown instead of the dialog.
5.16
Unlock Controller
The Unlock Controller dialog prompts the user for a password to be used to unlock the controller. If
the controller is locked, the following dialog is displayed.
Figure 51: Unlock Controller Dialog Box
Enter the password that was used to lock the controller in the Password edit box. Typing in this edit
box is masked. An asterisk is shown for each character typed.
The Cancel button closes the dialog without any action.
The OK button sends the Unlock Controller command to the controller. If the password is correct
the controller will be unlocked. If the password is not correct, the controller will remain locked.
If you forget the controller password, the Override Controller Lock command can be used to unlock
the controller. It will erase all programs in the controller.
5.17
Override Controller Lock
The Override Controller Lock dialog allows the user to unlock a controller without knowing the
password. This can be used in the event that that the password is forgotten.
To prevent unauthorized access to the information in the controller, the C and Ladder Logic
programs are erased. Use this command with caution, as you will lose the programs in the controller.
Selecting the Override Controller Lock command displays the following dialog.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
79
Figure 52: Override Controller Lock
•
The Yes button unlocks the controller and erases all programs.
•
The No button closes the dialog without any action.
5.18
Show Lock Status
The Show Lock Status command displays the controller lock state. It opens a dialog showing one of
the following states:
•
unlocked
•
locked against programming commands
•
locked against programming commands and database write
•
locked against programming commands and database read/write
•
The OK button closes the dialog.
5.19
C/C++ Program Loader
The C/C++ Program Loader command opens the C/C++ Program Loader dialog. This dialog allows
the user to load, run, stop and delete C/C++ programs.
The C/C++ Program Loader dialog presented is the same for all controller types. For all controllers
except the SCADAPack 350, this dialog may be used to load, run, stop or delete just one C/C++
program.
5.19.1
SCADAPack and SCADAPack 32 Controllers
The dialog shown below appears when the C/C++ Program Loader command is selected from the
controller menu and the Controller Type is either a SCADAPack32 or any one of the SCADAPack
series of controllers (Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus, SCADAPack
100 and SCADASense 4202 DR and DS) but not a SCADAPack 350.
For all controllers except the SCADAPack 350, the C/C++ Program Loader dialog may be used to
load just one C/C++ program.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
80
Figure 53: C/C++ Program Loader dialog for SCADAPack Series
The dialog displays the status of the C/C++ Program if one has been loaded in the controller. The
status of the program is indicated as Running or Stopped. The list is empty if there is no C/C++
Program loaded in the controller.
The Close button closes the dialog.
The Add button writes a C/C++ program to the controller. Selecting the Write button opens the Add
C/C++ Program dialog.
The Run button stops and restarts the C/C++ program in the controller.
The Stop button stops the selected C/C++ program in the controller.
The Delete button stops and erases the selected C/C++ program in the controller.
The Run, Stop and Delete buttons are disabled if there is no C/C++ program loaded in the
controller.
The Reset button resets the controller. A reset restarts the controller processor, the C/C++ program
and the Ladder Logic program.
The Refresh button refreshes the status of the loaded C/C++ program.
5.19.1.1 Add C/C++ Program Dialog
The Add C/C++ Program dialog writes a C/C++ Program to the controller.
Figure 54: Write C/C++ Program dialog
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
81
File Name specifies the C/C++ Program to write to controller. The file name may be selected in a
number of ways.
•
Click on the Browse button to open a standard file open dialog.
•
Use the drop-down menu to select the file from a list of previously written files.
•
Type the path and file name directly into the edit box.
The Write button writes the selected file to the controller. The communication progress dialog box
displays information about the write in progress, and allows you to cancel the write. If a C/C++
program is already loaded, it is stopped and erased before the selected file is written to the controller.
The Cancel button exits the dialog without writing to the controller.
5.19.2
SCADAPack 350 and SCADASense 4203 Series Controllers
If the controller type is a SCADAPack 350 or a SCADASense 4203 Series controller, the C/C++
Program Loader dialog displayed is shown below. In contrast to all other SCADAPack controllers,
this dialog allows multiple C/C++ programs to be loaded, monitored, and controlled. The number
of C/C++ programs that can be loaded into a SCADAPack 350 or a SCADASense 4203 Series
controller depends on the memory capacity of RAM of Flash.
Figure 55: C/C++ Program Loader dialog
The dialog displays the C/C++ Programs that have been loaded in the controller. The status of each
program is indicated as Running or Stopped.
The Close button closes the dialog.
The Add button writes a new C/C++ program to the controller. Selecting the Add button opens the
Add C/C++ Program dialog. Refer to 5.19.1.1-Add C/C++ Program Dialog for a description of
the Add C/C++ program dialog.
The Run, Stop and Delete buttons apply to the C/C++ program selected from the list of loaded
C/C++ programs. These buttons are disabled when there are no C/C++ programs loaded.
The Run button stops and restarts the selected C/C++ program in the controller.
The Stop button stops the selected C/C++ program in the controller.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
82
The Delete button stops and erases the selected C/C++ program in the controller.
The Reset button resets the controller. A reset restarts the controller processor, all C/C++ programs
and the Ladder Logic program.
The Refresh button refreshes the list of loaded programs and their status.
Click on the column headings to sort the list by that column. Click a second time to reverse the sort
order.
5.20
Flash Loader
The Flash Loader command opens the Flash Loader dialog. This dialog is used to write Ladder Logic
and C/C++ programs into Flash memory. This memory is permanently programmed and does not
require power or a backup battery. The programs in Flash can be written through all supported
communication media.
When this command is selected TelePACE checks if the controller supports Flash memory and, if a
Flash memory chip is installed.
If the controller does not support Flash memory, the message “Controller does not support Flash
memory” is displayed.
If the controller supports flash memory but there is no Flash memory installed in the application
ROM socket, the message “Flash memory is not installed in the application socket (U14)” is
displayed. Flash memory will have to be installed in the controller.
If there is Flash memory installed in the application program socket U14, the Flash Loader dialog is
displayed as shown below.
Figure 56: Flash Loader Dialog Box
The Write Ladder check-box controls writing of the Ladder Logic program and configuration data.
Configuration data includes serial port settings, register assignment, outputs on stop settings and,
element configuration. The file currently open Ladder Logic program in TelePACE will be written.
This control is disabled if the controller has operating system code in the Ladder Logic section of
Flash.
The Write C Program check-box controls writing of the C/C++ programs. This area is greyed out if
the controller type is one of the following:
•
SCADAPack 350
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
83
•
SCADAPack 32 or SCADAPack 32P
•
SCADAPack
•
SCADASense 4202 DR and DS with firmware 1.65 or newer
•
SCADASense 4203 DR and DS
The following controls select which file will be written. These controls are disabled if the controller
has operating system code in the C Program section of Flash.
The File name edit-box contains the full path name of the file to be written.
The Browse button opens standard file open dialog. It displays files of type *.abs. Selecting a file
fills in the File name edit-box.
The Message Length edit-box selects the maximum message length to be used while writing the
programs to the controller. Control over message length is needed when writing large amounts of
data over certain communication networks. The C program is written more quickly with a longer
message length. The allowable range is 26 to 255 bytes. The default value is 255.
•
The Close button closes the dialog.
•
The Write to Flash button writes the selected programs to Flash memory in the controller.
5.20.1
Writing Programs to Flash
Programming the Flash memory requires the Ladder Logic and C programs be stopped. The
following message is displayed when the Write to Flash button is selected.
Figure 57: Flash Loader Dialog Box
•
Click OK to stop the program execution and proceed with writing the program to Flash.
•
Click Cancel to stop the write to Flash operation.
Ladder Logic and C application programs can both be programmed into RAM and into Flash.
If there is a Ladder Logic program in RAM, the following message is displayed.
Figure 58: Flash Loader Dialog Box
•
Click Yes to erase the RAM program and continue with the write to Flash.
•
Click No to leave the RAM program in its place and continue with the write to Flash.
•
Click Cancel to stop the entire operation.
If there is a C program in RAM, the following message is displayed.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
84
Figure 59: Flash Loader Dialog Box
•
Click Yes to erase the RAM program and continue with the write to Flash.
•
Click No to leave the RAM program in its place and continue with the write to Flash.
•
Click Cancel to stop the entire operation
During the write to Flash operation a communication progress dialog is opened displaying the status
of the write operation. Click on the Cancel button to abort the write to Flash at any time. The
following actions occur during the write to Flash.
•
The programs in the controller are stopped.
•
The programs in RAM are erased if required.
•
The Flash is erased if required.
•
If it was selected, the Ladder Logic program is written to the controller.
•
If it was selected, the C program is written to the controller.
If a Ladder Logic program is loaded in RAM or Flash in the controller, a prompt is displayed asking
if the program should be started. If there is a Ladder Logic program in RAM the prompt asks if the
Ladder Logic program in RAM should be started. If there is a Ladder Logic program in Flash the
prompt asks it the Ladder Logic program in Flash should be started.
•
Click Yes to run the Ladder Logic program. This will happen immediately.
•
Click No to leave the program stopped.
If a C program is loaded in RAM or Flash in the controller, a prompt is displayed asking if the
program should be started. If there is a C program in RAM the prompt asks if the C program in RAM
should be started. If there is a C program in Flash the prompt asks it the C program in Flash should
be started.
•
Click Yes to run the C Program. This will happen immediately.
•
Click No to leave the C Program stopped.
5.21
Program Status
The Program Status dialog displays information about programs loaded in the controller memory.
The Program Status dialog is displayed when this command is selected. The Program Status dialog
displayed is different for SCADAPack 32 controllers and SCADAPack series controllers (Micro16,
SCADAPack, SCADAPack Light, SCADAPack Plus, SCADAPack 100, SCADAPack 350, and
SCADASense Series of programmable controllers. The Program Status is described for each
controller type in the following sections.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
85
5.21.1
SCADAPack and SCADAPack 32 Controllers
Programs in RAM memory always take precedence over programs in Flash or EPROM memory.
When a command to run a program is received, the controller first checks for a program in RAM,
then for one in Flash or EPROM.
Figure 60: Program Status Dialog Box SCADAPack and SCADAPack 32 Controllers
The Ladder Logic Programs section shows information about the Ladder Logic programs.
The RAM Memory section shows if a program is loaded and the execution state of the program.
The Flash Memory section shows if a program is loaded and the execution state of the program. The
program in Flash will be running only if there is no program in RAM. This section is greyed if the
controller does not have Flash memory installed.
If the controller has operating system code in the Ladder Logic section of Flash then the Flash
Memory or EPROM Memory section displays “Operating System”.
The EPROM Memory section shows if a program is loaded and the execution state of the program.
This section is greyed if the controller has Flash memory installed.
The C Programs section shows information about the C programs.
The RAM Memory section shows if a program is loaded and the execution state of the program.
The Flash Memory section shows if a program is loaded. This section is greyed if the controller
does not have Flash memory installed. If the controller type is SCADAPack 32 or SCADAPack 32P
the section displays “Operating System Loaded”.
If the controller has operating system code in the C Program section of Flash then the Flash Memory
or EPROM Memory section displays “Operating System”.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
86
The EPROM Memory section shows if a program is loaded. This section is greyed if the controller
has Flash memory installed.
The Close button closes the dialog.
The table below shows the messages that are displayed for the various conditions.
Condition
A program was found in the memory
No program was found in the memory
Ladder Logic mode is running
Ladder Logic mode is debug
Ladder Logic mode is stopped
Message
Program loaded
No program
Program RUNNING
Program RUNNING in DEBUG
Program STOPPED
Table 18: Program Status Settings
5.21.2
SCADAPack 350 and SCADASense 4203 Series of Controllers
When the controller type is SCADAPack 350 or a member of the SCADASense 4203 series of
controllers, the Program Status dialog displays the current status of the Ladder Logic program and all
C\C++ programs loaded in controller as shown in the diagram below.
Figure 61: Program Status Dialog for SCADAPack 350 and SCADASense 4203 Series Controllers
The status may be one of the following:
•
Stopped indicates the program has been downloaded and is currently stopped.
•
Running indicates the program has been downloaded and is currently running.
•
Debug indicates the program has been downloaded and is currently running in debug mode
(Ladder Logic program only).
•
No Program indicates that there is no program in the controller.
The memory used by each program is displayed in addition to the program status.
•
The ROM (KB) column describes the amount of memory used in ROM by each program.
•
The RAM (KB) column describes the amount of memory used in RAM by each program.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
87
•
The NVRAM (KB) column describes the amount of memory used in non-volatile RAM by each
program.
•
The Memory Remaining row describes the unused memory of each type available to all
programs.
The Ladder Logic program in RAM memory always takes precedence over a Ladder Logic program
in ROM. When a command to run a program is received, the controller first checks for a program in
RAM, then for one in ROM. A Ladder Logic program in ROM may only be run if there is no Ladder
Logic program in RAM.
The Close button closes the dialog.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
88
6
Communications Menu
Communication menu commands are used to transfer programs between the Host PC and the
controller. PC Communication settings for the host PC are configured in this menu selection.
6.1
Read from Controller
The Read from controller command is used to read the ladder logic program, register assignment and
serial port settings from a controller into the TelePACE program. The program replaces the current
program in the ladder editor. The communication progress dialog box displays information about the
read in progress, and allows you to Start or Cancel the read. Click Cancel to abort a read in progress.
6.2
Write to Controller
The Write to controller command writes the ladder logic program, register assignment and serial port
settings in the TelePACE program to the controller. The program replaces the current program in the
controller. The communication progress dialog box displays information about the write progress,
and allows you to Start or Cancel the write. Click Cancel to stop a write in progress.
If the program in the controller is executing, a dialog box appears to request the next action. Press
Stop to stop execution of the ladder logic program when the write is complete. Press Continue to
continue execution of the new program after the write is complete. Press Cancel to abort the write.
TelePACE stops the program in the controller before writing the new program to the controller.
Programs that are executing in the target controller are paused momentarily when commands are
written. The length of the pause depends on the command written.
6.3
PC Communications Settings
The PC Communication Settings command defines the communication protocol and communication
link used for communication between the personal computer (PC) and SCADAPack or 4202 series
controllers.
When the command is select the Communication Protocols Configuration dialog is displayed as
shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
89
Figure 62: Communication Protocols Configuration dialog.
6.3.1
ClearSCADA
The ClearSCADA protocol driver is used for communicating with a local or remote ClearSCADA
server. The ClearSCADA server will then, in turn, communicate with devices as per its
configuration. The ClearSCADA protocol driver communicates with the ClearSCADA server using
a TCP connection.
•
To configure a ClearSCADA protocol connection, highlight ClearSCADA in the
Communication Protocols window and click the Configure button. The ClearSCADA
Configuration window is displayed.
•
To select a configured ClearSCADA protocol connection, highlight ClearSCADA in the
Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.1.1
General Parameters
When ClearSCADA protocol is selected for configuration the ClearSCADA Configuration dialog is
opened with the General tab selected as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
90
Figure 63: ClearSCADA Configuration (General) Dialog Box
The General tab component information section contains the name of Communication Component
and the author, Control Microsystems.
The Communications Settings grouping contains all the essential details necessary to establish
communication to a device through a local or remote ClearSCADA installation.
The Modbus Station entry specifies the station address of the target device. Valid values are 1 to
65534.
The Outstation Set entry specifies the ClearSCADA outstation set to which the target device is
attached. The valid range is 0 to 65535. The default value is 0.
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The TCP Port Number entry specifies the TCP port on the ClearSCADA server. The valid range is
0 to 65535. The default value is 49155
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The contents of this field will remain unchanged.
6.3.1.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
91
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 64: ClearSCADA Configuration (Advanced) Dialog Box
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value will indicate
to the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 264. The default value is 264.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.1.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
92
Figure 65: ClearSCADA Configuration (Information) Dialog Box
6.3.1.3.1 Information
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.2
DNP
The DNP protocol driver is used to communicate over a serial DNP network to SCADAPack
controllers configured for DNP communication.
•
To configure a DNP protocol connection, highlight DNP in the Communication Protocols
window and click the Configure button. The DNP Configuration window is displayed.
•
To select a configured DNP protocol connection, highlight DNP in the Communication
Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.2.1
General Parameters
When DNP is selected for configuration the DNP Configuration dialog is opened with the General
tab selected as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
93
Figure 66: DNP Configuration (General) Dialog Box
The General tab component information section contains the name of Communication Component
and the author, Control Microsystems.
The DNP Communication Settings logical grouping contains DNP specific communication settings
including the DNP Station address, the timeout interval as well as the number of attempts.
The RTU Station parameter sets the target DNP station number. Valid entries are 0 to 65519. The
default address is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
This Serial Port Settings grouping contains details directly related to the PC’s
communication port including the port number, the baud rate, parity and stop bit settings.
The Port parameter specifies the PC serial port to use. The DNP driver determines what serial ports
are available on the PC and presents these in the drop-down menu list. The available serial ports list
will include any USB to serial converters used on the PC. The default value is the first existing port
found by the driver.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
94
The Baud parameter specifies the baud rate to use for communication. The menu list displays
selections for 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, and 57600. The default value is
9600.
The Parity parameter specifies the type of parity to use for communication. The menu list displays
selections for none, odd and even parity. The default value is None.
The Stop Bits parameter specifies the number of stop bits to use for communication. The menu list
displays selections for 1 and 2 stop bits. The default value is 1 bit.
The Connection Type parameter specifies the serial connection type. The DNP driver supports
direct serial connection with no flow control, Request-to-send (RTS) and clear-to-send (CTS) flow
control and PSTN dial-up connections. The menu list displays selections for Direct Connection,
RTS/CTS Flow Control and Dial Up Connection. The default selection is Direct Connection.
•
Select Direct Connection for RS-232 for RS-485 connections that do not require the hardware
control lines on the serial ports.
•
Select RTS/CTS Flow Control to communicate over radio or leased-line networks using
modems that require RTS/CTS handshaking. Selecting RTS/CTS Flow Control adds a new tab,
Flow Control, to the DNP Configuration dialog. Refer to the Flow Control Parameters section
below for configuration details.
•
Select Dial Up Connection to communication over dial up modems. Selecting Dial Up
Connection adds a new tab, Dial Up, to the DNP Configuration dialog. Refer to the Dial Up
Parameters section below for configuration details.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.2.2
Flow Control Parameters
Flow Control parameters are used to configure how RTS and CTS control is used. When RTS/CTS
Flow Control is selected for Connection Type the Flow Control tab is added to the DNP
Configuration dialog. When the Flow Control tab heading is clicked the Flow Control dialog is
opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
95
Figure 67: DNP Configuration (Flow Control) Dialog Box
6.3.2.2.1
RTS/CTS Flow Control
The RTS/CTS Flow Control grouping contains two mutually exclusive options, Use Hardware
Control Lines and Use CTS Delay Time. These options enable the driver to communicate over radio
or leased-line networks using modems that require RTS/CTS handshaking.
The Use Hardware Control Lines option specifies a half-duplex connection requiring the use of the
Request to Send (RTS) and Clear to Send (CTS) hardware control lines to control the flow of data.
This selection is used with radios and dedicated telephone line modems. The driver turns on the RTS
signal when it wants to transmit data. The modem or other device then turns on CTS when it is ready
to transmit. The driver transmits the data, and then turns off the RTS signal. This selection is
mutually exclusive of the Use CTS Delay Time selection described below. This is the default
selection.
The Use CTS Delay Time option is selected if the device cannot generate a CTS signal. The driver
will assert RTS then wait the specified Delay Time, in milliseconds, before proceeding. This option
is mutually exclusive with the Use Hardware Control Lines selection described above.
The Delay Time parameter sets the time in milliseconds that the driver will wait after asserting RTS
before proceeding. The value of this field must be smaller than the Time Out value set in the General
parameters dialog. For example, if the Timeout value is set to 3 seconds, the CTS Delay Time can be
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
96
set to 2999 milliseconds or less. The minimum value for this field is 0 milliseconds. The value is
initially set to 0 by default.
The Hold Time parameter specifies the time, in milliseconds, that the driver will hold RTS after the
last character is transmitted. This is useful for devices that immediately end transmission when RTS
is turned off. The value of this field must be smaller than the Time Out value set in the General
parameters dialog. For example, if the Timeout value is set to 3 seconds, the CTS Delay Time can be
set to 2999 milliseconds or less. The minimum value for this field is 0 milliseconds. The value is
initially set to 0 by default.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.2.3
Dial Up Parameters
Dial Up parameters are used to configure a dial up connection. When Dial Up is selected for
Connection Type the Dial Up tab is added to the DNP Configuration dialog. When the Dial Up tab
heading is clicked the Dial Up dialog is opened as shown below.
Figure 68: DNP Configuration (Dial Up) Dialog Box
The Dialing Prefix parameter specifies the commands sent to the modem before dialing. A
maximum of 32 characters can be entered. All characters are valid. The default value is “&F0 &K0
S0=1 &W0 &Y0”.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
97
The Phone Number parameter specifies the telephone number of the remote controller. A maximum
of 32 characters can be entered. All characters are valid. This field’s default value is blank.
The Dial Type parameter specifies the dialing type. Valid values are Pulse and Tone. The default
value is Tone.
The Dial Attempts parameter specifies how many dialing attempts will be made. Valid values are 1
to 10. The default value is 1.
The Connect Time parameter specifies the amount of time in seconds the modem will wait for a
connection. Valid values are 6 to 300. The default value is 60.
The Pause Time parameter specifies the time in seconds between dialing attempts. Valid values are
6 to 600. The default value is 30.
Check the Inactivity Timeout check box to automatically terminate the dialup connection after a
period of inactivity. The Inactivity Time edit box is enabled only if this option is checked. The
default state is checked.
Enter the inactivity period, in minutes, in the Inactivity Timeout box. The dialup connection will be
terminated automatically after the specified number of minutes of inactivity has lapsed. This option
is only active if the Inactivity Timeout box is checked. Valid values are from 1 to 30 minutes. The
default value is 1.
•
Click Restore Defaults to restore default values to all fields on this page, except for the Phone
Number field. The content of this field will remain unchanged.
6.3.2.4
Advanced Parameters
DNP Configuration Advanced parameters set the DNP master station address and message size
control. When the Advanced tab heading is clicked the Advanced dialog is opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
98
Figure 69: DNP Configuration (Advanced) Dialog Box
The Master Station parameter is the DNP station address assumed by this communication
component. When this driver sends out commands, responses form the controller will be directed to
this address. The default value is 100.
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible. Valid
values are 2 to 231. The default value is 231.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.2.5
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
99
Figure 70: DNP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.3
DNP/TCP
The DNP/TCP protocol driver is used to communicate over an Ethernet DNP network to
SCADAPack controllers configured for DNP/TCP communication.
•
To configure a DNP/TCP protocol connection, highlight DNP/TCP in the Communication
Protocols window and click the Configure button. The DNP/TCP Configuration window is
displayed.
•
To select a configured DNP/TCP protocol connection, highlight DNP/TCP in the
Communication Protocols window and click the OK button.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
100
•
To close the dialog, without making a selection click the Cancel button.
6.3.3.1
General Page
When DNP/TCP protocol is selected for configuration the DNP/TCP Configuration dialog is opened
with the General tab selected as shown below.
Figure 71: DNP in TCP Configuration (General) Dialog Box
The DNP Communication Settings grouping contains DNP specific communication settings
including the DNP Station address, the timeout interval as well as the number of attempts.
The RTU Station parameter specifies the DNP station number of the target device. The valid range
is 0 to 65519. The default is station 1.
The Timeout parameter specifies the length of time, in seconds, to wait for a response from the
controller before retrying (see Attempts) or ultimately failing. Valid values are 1 to 255. The default
value is 3 seconds.
The Attempts parameter specifies the number of times to send a command to the controller before
giving up and reporting this failure to the host application. Valid values are 1 to 20. The default
value is 3 attempts.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
101
The Host Network Details grouping contains information about the IP network including the
target’s IP address or name, and the TCP port number on which it is listening. More details on these
below.
6.3.3.1.1
IP Address / Name
The IP Address / Name parameter specifies the Ethernet IP address of the target RTU, or a DNS
name that can be resolved to an IP address. The default value is blank. The following IP addresses
are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The TCP Port No. field specifies the TCP port of the remote device. Valid values are 0 to 65535.
The default value is 20000.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
6.3.3.2
Advanced Page
Advanced parameters are used to set the Master Station address and control the message size for the
protocol. Control over message length is needed when writing large amounts of data over certain
communication networks. A larger value can improve communication speed but can increase the
number of failed transmissions. A smaller value can reduce the number of failed transmissions but
may reduce throughput. When the Advanced tab heading is clicked the Advanced dialog is opened as
shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
102
Figure 72: DNP n TCP Configuration (Advanced) Dialog Box
The Master Station parameter specifies the DNP station address of the RealFLO application. When
RealFLO sends out commands, responses from the target controller will be directed to this address.
The valid range is 0 to 65519, except that this value cannot be the same as the target RTU Station
number. The default value is 100.
The Maximum selection indicates that you want the host application to package messages using the
maximum size allowable by the protocol.
The Custom value selection specifies a custom value for message size. This value indicates to the
host application to package messages to be no larger than what is specified if possible. The valid
range for the Custom value field is from 2 to 231. Maximum is selected by default.
•
Click Restore Defaults to restore default values to all fields on this page
6.3.3.3
Information Page
The Information page displays detailed driver information. When the Information tab is clicked the
Information dialog is opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
103
Figure 73: DNP in TCP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.4
DNP/UDP
The DNP/UDP protocol driver is used to communicate over an Ethernet DNP network to
SCADAPack controllers configured for DNP/UDP communication.
•
To configure a DNP/UDP protocol connection, highlight DNP/UDP in the Communication
Protocols window and click the Configure button. The DNP/UDP Configuration window is
displayed.
•
To select a configured DNP/UDP protocol connection, highlight DNP/UDP in the
Communication Protocols window and click the OK button.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
104
•
To close the dialog, without making a selection click the Cancel button.
6.3.4.1
General Page
When DNP/UDP protocol is selected for configuration the DNP/UDP Configuration dialog is
opened with the General tab selected as shown below.
Figure 74: DNP in UDP Configuration (General) Dialog Box
The DNP Communication Settings grouping contains DNP specific communication settings
including the DNP Station address, the timeout interval as well as the number of attempts.
The RTU Station parameter specifies the DNP station number of the target device. The valid range
is 0 to 65519. The default is station 1.
The Timeout parameter specifies the length of time, in seconds, to wait for a response from the
controller before retrying (see Attempts) or ultimately failing. Valid values are 1 to 255. The default
value is 3 seconds.
The Attempts parameter specifies the number of times to send a command to the controller before
giving up and reporting this failure to the host application. Valid values are 1 to 20. The default
value is 3 attempts.
The Host Network Details grouping contains information about the IP network including the
target’s IP address or name, and the UDP port number on which it is listening. More details on these
below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
105
6.3.4.1.1
IP Address / Name
The IP Address / Name parameter specifies the Ethernet IP address of the target RTU, or a DNS
name that can be resolved to an IP address. The default value is blank. The following IP addresses
are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The UDP Port No. field specifies the UDP port of the remote device. Valid values are 0 to 65534.
The default value is 20000.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
6.3.4.2
Advanced Page
Advanced parameters are used to set the Master Station address and control the message size for the
protocol. Control over message length is needed when writing large amounts of data over certain
communication networks. A larger value can improve communication speed but can increase the
number of failed transmissions. A smaller value can reduce the number of failed transmissions but
may reduce throughput. When the Advanced tab heading is clicked the Advanced dialog is opened as
shown below.
Figure 75: DNP in UDP Configuration (Advanced) Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
106
The Master Station parameter specifies the DNP station address of the RealFLO application. When
RealFLO sends out commands, responses from the target controller will be directed to this address.
The valid range is 0 to 65519, except that this value cannot be the same as the target RTU Station
number. The default value is 100.
The Maximum selection indicates that you want the host application to package messages using the
maximum size allowable by the protocol.
The Custom value selection specifies a custom value for message size. This value indicates to the
host application to package messages to be no larger than what is specified if possible. The valid
range for the Custom value field is from 2 to 231. Maximum is selected by default.
•
Click Restore Defaults to restore default values to all fields on this page
6.3.4.3
Information Page
The Information page displays detailed driver information. When the Information tab is clicked the
Information dialog is opened as shown below.
Figure 76: DNP in UDP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
107
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.5
Modbus ASCII
The Modbus ASCII protocol driver is used to communicate over a serial network, using Modbus
ASCII framing, to SCADAPack controllers configured for Modbus ASCII protocol.
•
To configure a Modbus ASCII protocol connection, highlight Modbus ASCII in the
Communication Protocols window and click the Configure button. The Modbus ASCII
Configuration window is displayed.
•
To select a configured Modbus ASCII protocol connection, highlight Modbus ASCII in the
Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.5.1
General Parameters
When Modbus ASCII is selected for configuration the Modbus ASCII Configuration dialog is
opened with the General tab selected as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
108
Figure 77: Modbus ASCII Configuration (General) Dialog Box
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
This Serial Port Settings grouping contains details directly related to the PC’s
communication port including the port number, the baud rate, parity and stop bit settings.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
109
The Port parameter specifies the PC serial port to use. The DNP driver determines what serial ports
are available on the PC and presents these in the drop-down menu list. The available serial ports list
will include any USB to serial converters used on the PC. The default value is the first existing port
found by the driver.
The Baud parameter specifies the baud rate to use for communication. The menu list displays
selections for 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, and 57600. The default value is
9600.
The Parity parameter specifies the type of parity to use for communication. The menu list displays
selections for none, odd and even parity. The default value is None.
The Data Bits parameter specifies the number of data bits contained in the character frame. Valid
values are for this field is 7 and 8 bits. The default value is 8 bits.
The Stop Bits parameter specifies the number of stop bits to use for communication. The menu list
displays selections for 1 and 2 stop bits. The default value is 1 bit.
The Connection Type parameter specifies the serial connection type. The Modbus ASCII driver
supports direct serial connection with no flow control, Request-to-send (RTS) and clear-to-send
(CTS) flow control and PSTN dial-up connections. The menu list displays selections for Direct
Connection, RTS/CTS Flow Control and Dial Up Connection. The default selection is Direct
Connection.
•
Select Direct Connection for RS-232 for RS-485 connections that do not require the hardware
control lines on the serial ports.
•
Select RTS/CTS Flow Control to communicate over radio or leased-line networks using
modems that require RTS/CTS handshaking. Selecting RTS/CTS Flow Control adds a new tab,
Flow Control, to the Modbus ASCII Configuration dialog. Refer to the Flow Control Parameters
section below for configuration details.
•
Select Dial Up Connection to communication over dial up modems. Selecting Dial Up
Connection adds a new tab, Dial Up, to the Modbus ASCII Configuration dialog. Refer to the
Dial Up Parameters section below for configuration details.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.5.2
Modbus ASCII Configuration (Flow Control)
Flow Control parameters are used to configure how RTS and CTS control is used. When RTS/CTS
Flow Control is selected for Connection Type the Flow Control tab is added to the Modbus ASCII
Configuration dialog. When the Flow Control tab heading is clicked the Flow Control dialog is
opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
110
Figure 78: Modbus ASCII Configuration (Flow Control)
The RTS/CTS Flow Control grouping contains two mutually exclusive options, Use Hardware
Control Lines and Use CTS Delay Time. These options enable the driver to communicate over radio
or leased-line networks using modems that require RTS/CTS handshaking.
The Use Hardware Control Lines option specifies a half-duplex connection requiring the use of the
Request to Send (RTS) and Clear to Send (CTS) hardware control lines to control the flow of data.
This selection is used with radios and dedicated telephone line modems. The driver turns on the RTS
signal when it wants to transmit data. The modem or other device then turns on CTS when it is ready
to transmit. The driver transmits the data, and then turns off the RTS signal. This selection is
mutually exclusive of the Use CTS Delay Time selection described below. This is the default
selection.
The Use CTS Delay Time option is selected if the device cannot generate a CTS signal. The driver
will assert RTS then wait the specified Delay Time, in milliseconds, before proceeding. This option
is mutually exclusive with the Use Hardware Control Lines selection described above.
The Delay Time parameter sets the time in milliseconds that the driver will wait after asserting RTS
before proceeding. The value of this field must be smaller than the Time Out value set in the General
parameters dialog. For example, if the Timeout value is set to 3 seconds, the CTS Delay Time can be
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
111
set to 2999 milliseconds or less. The minimum value for this field is 0 milliseconds. The value is
initially set to 0 by default.
The Hold Time parameter specifies the time, in milliseconds, that the driver will hold RTS after the
last character is transmitted. This is useful for devices that immediately end transmission when RTS
is turned off. The value of this field must be smaller than the Time Out value set in the General
parameters dialog. For example, if the Timeout value is set to 3 seconds, the CTS Delay Time can be
set to 2999 milliseconds or less. The minimum value for this field is 0 milliseconds. The value is
initially set to 0 by default.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.5.3
Modbus ASCII Configuration (Dial Up)
Dial Up parameters are used to configure a dial up connection. When Dial Up is selected for
Connection Type the Dial Up tab is added to the Modbus ASCII Configuration dialog. When the
Dial Up tab heading is clicked the Dial Up dialog is opened as shown below.
Figure 79: Modbus ASCII Configuration (Dial Up)
The Dialing Prefix parameter specifies the commands sent to the modem before dialing. A
maximum of 32 characters can be entered. All characters are valid. The default value is “&F0 &K0
S0=1 &W0 &Y0”.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
112
The Phone Number parameter specifies the telephone number of the remote controller. A maximum
of 32 characters can be entered. All characters are valid. This field’s default value is blank.
The Dial Type parameter specifies the dialing type. Valid values are Pulse and Tone. The default
value is Tone.
The Dial Attempts parameter specifies how many dialing attempts will be made. Valid values are 1
to 10. The default value is 1.
The Connect Time parameter specifies the amount of time in seconds the modem will wait for a
connection. Valid values are 6 to 300. The default value is 60.
The Pause Time parameter specifies the time in seconds between dialing attempts. Valid values are
6 to 600. The default value is 30.
Check the Inactivity Timeout check box to automatically terminate the dialup connection after a
period of inactivity. The Inactivity Time edit box is enabled only if this option is checked. The
default state is checked.
Enter the inactivity period, in minutes, in the Inactivity Timeout box. The dialup connection will be
terminated automatically after the specified number of minutes of inactivity has lapsed. This option
is only active if the Inactivity Timeout box is checked. Valid values are from 1 to 30 minutes. The
default value is 1.
•
Click Restore Defaults to restore default values to all fields on this page, except for the Phone
Number field. The content of this field will remain unchanged.
6.3.5.4
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
113
Figure 80: Modbus ASCII Configuration (Advanced) Dialog Box
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 250 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 252. When
Addressing is set to Standard valid values are 2 to 252.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.5.5
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
114
Figure 81: Modbus ASCII Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.6
Modbus ASCII in TCP
Modbus ASCII in TCP message format is exactly same as that of the Modbus ASCII protocol. The
main difference is that Modbus ASCII in TCP protocol communicates with a SCADAPack controller
through the Internet and Modbus ASCII through the serial port. The Modbus ASCII in TCP protocol
does not include a six-byte header prefix, as with the Modbus\TCP, but does include the Modbus
‘CRC-16’ or ‘LRC’ check fields.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
115
•
To configure a Modbus ASCII in TCP protocol connection, highlight Modbus ASCII in TCP in
the Communication Protocols window and click the Configure button. The Modbus ASCII in
TCP Configuration window is displayed.
•
To select a configured Modbus ASCII in TCP protocol connection, highlight Modbus ASCII in
TCP in the Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.6.1
General Parameters
When Modbus ASCII in TCP is selected for configuration the Modbus ASCII in TCP Configuration
dialog is opened with the General tab selected as shown below.
Figure 82: Modbus ASCII in TCP Configuration (General) Dialog Box
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
116
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
The Host Network Details grouping contains entries for the host’s IP address or name and
the TCP port on which it is listening.
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The TCP Port No. field specifies the TCP port of the remote device. Valid values are 0 to
65535. The default value is 49153.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
117
6.3.6.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 83: Modbus ASCII in TCP Configuration (Advanced) Dialog Box
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 250 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 252. When
Addressing is set to Standard valid values are 2 to 252.
•
Click Restore Defaults to restore default values to all fields on this page.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
118
6.3.6.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 84: Modbus ASCII in TCP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.7
Modbus ASCII in UDP
Modbus ASCII in UDP protocol is similar to Modbus ASCII in TCP protocol. It has the same
message format as the Modbus ASCII in TCP. The only difference between them is one uses TCP
protocol and another uses UDP protocol.
•
To configure a Modbus ASCII in TCP protocol connection, highlight Modbus ASCII in UDP in
the Communication Protocols window and click the Configure button. The Modbus ASCII in
UDP Configuration window is displayed.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
119
•
To select a configured Modbus ASCII in TCP protocol connection, highlight Modbus ASCII in
UDP in the Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.7.1
General Parameters
When Modbus ASCII in UDP is selected for configuration the Modbus ASCII in UDP Configuration
dialog is opened with the General tab selected as shown below.
Figure 85: Modbus ASCII in UDP Configuration (General) Dialog Box
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
120
The Host Network Details grouping contains entries for the host’s IP address or name and
the TCP port on which it is listening.
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The UDP Port No. field specifies the UDP port of the remote device. Valid values are 0 to
65535. The default value is 49153.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
6.3.7.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 86: Modbus ASCII in UDP Configuration (Advanced) Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
121
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 250 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 252. When
Addressing is set to Standard valid values are 2 to 252.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.7.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 87: Modbus ASCII in UDP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
122
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.8
Modbus RTU
6.3.8.1
Introduction
The Modbus RTU protocol driver is used to communicate over a serial network, using Modbus RTU
framing, to SCADAPack controllers configured for Modbus RTU protocol.
•
To configure a Modbus RTU protocol connection, highlight Modbus RTU in the
Communication Protocols window and click the Configure button. The Modbus RTU
Configuration window is displayed.
•
To select a configured Modbus RTU protocol connection, highlight Modbus RTU in the
Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.8.2
General Parameters
When Modbus RTU is selected for configuration the Modbus RTU Configuration dialog is opened
with the General tab selected as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
123
Figure 88: Modbus RTU Configuration (General) Dialog Box
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
This Serial Port Settings grouping contains details directly related to the PC’s
communication port including the port number, the baud rate, parity and stop bit settings.
The Port parameter specifies the PC serial port to use. The DNP driver determines what serial ports
are available on the PC and presents these in the drop-down menu list. The available serial ports list
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
124
will include any USB to serial converters used on the PC. The default value is the first existing port
found by the driver.
The Baud parameter specifies the baud rate to use for communication. The menu list displays
selections for 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, and 57600. The default value is
9600.
The Parity parameter specifies the type of parity to use for communication. The menu list displays
selections for none, odd and even parity. The default value is None.
The Stop Bits parameter specifies the number of stop bits to use for communication. The menu list
displays selections for 1 and 2 stop bits. The default value is 1 bit.
The Connection Type parameter specifies the serial connection type. The Modbus RTU driver
supports direct serial connection with no flow control, Request-to-send (RTS) and clear-to-send
(CTS) flow control and PSTN dial-up connections. The menu list displays selections for Direct
Connection, RTS/CTS Flow Control and Dial Up Connection. The default selection is Direct
Connection.
•
Select Direct Connection for RS-232 for RS-485 connections that do not require the hardware
control lines on the serial ports.
•
Select RTS/CTS Flow Control to communicate over radio or leased-line networks using
modems that require RTS/CTS handshaking. Selecting RTS/CTS Flow Control adds a new tab,
Flow Control, to the Modbus RTU Configuration dialog. Refer to the Flow Control Parameters
section below for configuration details.
•
Select Dial Up Connection to communication over dial up modems. Selecting Dial Up
Connection adds a new tab, Dial Up, to the Modbus RTU Configuration dialog. Refer to the Dial
Up Parameters section below for configuration details.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.8.3
Modbus RTU Configuration (Flow Control)
Flow Control parameters are used to configure how RTS and CTS control is used. When RTS/CTS
Flow Control is selected for Connection Type the Flow Control tab is added to the Modbus RTU
Configuration dialog. When the Flow Control tab heading is clicked the Flow Control dialog is
opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
125
Figure 89: Modbus RTU Configuration (Flow Control)
The RTS/CTS Flow Control grouping contains two mutually exclusive options, Use Hardware
Control Lines and Use CTS Delay Time. These options enable the driver to communicate over radio
or leased-line networks using modems that require RTS/CTS handshaking.
The Use Hardware Control Lines option specifies a half-duplex connection requiring the use of the
Request to Send (RTS) and Clear to Send (CTS) hardware control lines to control the flow of data.
This selection is used with radios and dedicated telephone line modems. The driver turns on the RTS
signal when it wants to transmit data. The modem or other device then turns on CTS when it is ready
to transmit. The driver transmits the data, and then turns off the RTS signal. This selection is
mutually exclusive of the Use CTS Delay Time selection described below. This is the default
selection.
The Use CTS Delay Time option is selected if the device cannot generate a CTS signal. The driver
will assert RTS then wait the specified Delay Time, in milliseconds, before proceeding. This option
is mutually exclusive with the Use Hardware Control Lines selection described above.
The Delay Time parameter sets the time in milliseconds that the driver will wait after asserting RTS
before proceeding. The value of this field must be smaller than the Time Out value set in the General
parameters dialog. For example, if the Timeout value is set to 3 seconds, the CTS Delay Time can be
set to 2999 milliseconds or less. The minimum value for this field is 0 milliseconds. The value is
initially set to 0 by default.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
126
The Hold Time parameter specifies the time, in milliseconds, that the driver will hold RTS after the
last character is transmitted. This is useful for devices that immediately end transmission when RTS
is turned off. The value of this field must be smaller than the Time Out value set in the General
parameters dialog. For example, if the Timeout value is set to 3 seconds, the CTS Delay Time can be
set to 2999 milliseconds or less. The minimum value for this field is 0 milliseconds. The value is
initially set to 0 by default.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.8.4
Modbus RTU Configuration (Dial Up)
Dial Up parameters are used to configure a dial up connection. When Dial Up is selected for
Connection Type the Dial Up tab is added to the Modbus RTU Configuration dialog. When the Dial
Up tab heading is clicked the Dial Up dialog is opened as shown below.
Figure 90: Modbus RTU Configuration (Dial Up)
The Dialing Prefix parameter specifies the commands sent to the modem before dialing. A
maximum of 32 characters can be entered. All characters are valid. The default value is “&F0 &K0
S0=1 &W0 &Y0”.
The Phone Number parameter specifies the telephone number of the remote controller. A maximum
of 32 characters can be entered. All characters are valid. This field’s default value is blank.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
127
The Dial Type parameter specifies the dialing type. Valid values are Pulse and Tone. The default
value is Tone.
The Dial Attempts parameter specifies how many dialing attempts will be made. Valid values are 1
to 10. The default value is 1.
The Connect Time parameter specifies the amount of time in seconds the modem will wait for a
connection. Valid values are 6 to 300. The default value is 60.
The Pause Time parameter specifies the time in seconds between dialing attempts. Valid values are
6 to 600. The default value is 30.
Check the Inactivity Timeout check box to automatically terminate the dialup connection after a
period of inactivity. The Inactivity Time edit box is enabled only if this option is checked. The
default state is checked.
Enter the inactivity period, in minutes, in the Inactivity Timeout box. The dialup connection will be
terminated automatically after the specified number of minutes of inactivity has lapsed. This option
is only active if the Inactivity Timeout box is checked. Valid values are from 1 to 30 minutes. The
default value is 1.
•
Click Restore Defaults to restore default values to all fields on this page, except for the Phone
Number field. The content of this field will remain unchanged.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
128
6.3.8.5
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 91: Modbus RTU Configuration (Advanced) Dialog Box
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 250 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 252. When
Addressing is set to Standard valid values are 2 to 252.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
129
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.8.6
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 92: Modbus RTU Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.9
Modbus RTU in TCP
Modbus RTU in TCP message format is exactly same as that of the Modbus RTU protocol. The main
difference is that Modbus RTU in TCP protocol communicates with a controller through the Internet
and Modbus RTU protocol through the serial port. The Modbus RTU in TCP protocol does not
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
130
include a six-byte header prefix, as with the Modbus\TCP, but does include the Modbus ‘CRC-16’ or
‘LRC’ check fields. The Modbus RTU in TCP message format supports Modbus RTU message
format.
•
To configure a Modbus RTU in TCP protocol connection, highlight Modbus RTU in TCP in
the Communication Protocols window and click the Configure button. The Modbus RTU in
TCP Configuration window is displayed.
•
To select a configured Modbus RTU in TCP protocol connection, highlight Modbus RTU in
TCP in the Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.9.1
General Parameters
When Modbus RTU in TCP is selected for configuration the Modbus RTU in TCP Configuration
dialog is opened with the General tab selected as shown below.
Figure 93: Modbus RTU in TCP Configuration (General) Dialog Box
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
131
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
The Host Network Details grouping contains entries for the host’s IP address or name and
the TCP port on which it is listening.
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The TCP Port No. field specifies the TCP port of the remote device. Valid values are 0 to
65535. The default value is 49152.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
132
6.3.9.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 94: Modbus RTU in TCP Configuration (Advanced) Dialog Box
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 250 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 252. When
Addressing is set to Standard valid values are 2 to 252.
•
Click Restore Defaults to restore default values to all fields on this page.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
133
6.3.9.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 95: Modbus RTU in TCP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.10
Modbus RTU in UDP
Modbus RTU in UDP protocol is similar to Modbus RTU in TCP protocol. It has the same
message format as the RTU in TCP message. The only difference between them is one uses
TCP protocol and another uses UDP protocol.
•
To configure a Modbus RTU in UDP protocol connection, highlight Modbus RTU in UDP in
the Communication Protocols window and click the Configure button. The Modbus RTU in
UDP Configuration window is displayed.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
134
•
To select a configured Modbus RTU in UDP protocol connection, highlight Modbus RTU in
UDP in the Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.10.1
General Parameters
When Modbus RTU in UDP is selected for configuration the Modbus RTU in UDP Configuration
dialog is opened with the General tab selected as shown below.
Figure 96: Modbus RTU in UDP Configuration (General) Dialog Box
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
135
The Host Network Details grouping contains entries for the host’s IP address or name and
the TCP port on which it is listening.
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The UDP Port No. field specifies the UDP port of the remote device. Valid values are 0 to
65535. The default value is 49152.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
6.3.10.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 97: Modbus RTU in UDP Configuration (Advanced) Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
136
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 250 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 252. When
Addressing is set to Standard valid values are 2 to 252.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.10.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 98: Modbus RTU in UDP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
137
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.11
Modbus/TCP
Modbus/TCP is an extension of serial Modbus, which defines how Modbus messages are encoded
within and transported over TCP/IP-based networks. The Modbus/TCP protocol uses a custom
Modbus protocol layer on top of the TCP protocol. Its request and response messages are prefixed by
six bytes. These six bytes consist of three fields: transaction ID field, protocol ID field and length
field. The encapsulated Modbus message has exactly the same layout and meaning, from the
function code to the end of the data portion, as other Modbus messages. The Modbus ‘CRC-16’ or
‘LRC’ check fields are not used in Modbus/TCP. The TCP/IP and link layer (e.g. Ethernet)
checksum mechanisms instead are used to verify accurate delivery of the packet.
•
To configure a Modbus/TCP protocol connection, highlight Modbus/TCP in the
Communication Protocols window and click the Configure button. The Modbus/TCP
Configuration window is displayed.
•
To select a configured Modbus/TCP protocol connection, highlight Modbus/TCP in the
Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
138
6.3.11.1
General Parameters
When Modbus/TCP is selected for configuration the Modbus/TCP Configuration dialog is opened
with the General tab selected as shown below.
Figure 99: Modbus/TCP Configuration (General) Dialog Box
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
The Host Network Details grouping contains entries for the host’s IP address or name and
the TCP port on which it is listening.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
139
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The TCP Port No. field specifies the UDP port of the remote device. Valid values are 0 to
65535. The default value is 502.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
6.3.11.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 100: Modbus/TCP Configuration (Advanced) Dialog Box
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
140
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 246 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 248. When
Addressing is set to Standard valid values are 2 to 248.
•
Click Restore Defaults to restore default values to all fields on this page.
6.3.11.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 101: Modbus/TCP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
141
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.12
Modbus/UDP
Modbus/UDP communication mode is similar to Modbus/TCP communication mode. It has
the same message format with the Modbus/TCP. The only difference between them is one
uses TCP protocol and another uses UDP protocol.
•
To configure a Modbus/UDP protocol connection, highlight Modbus/UDP in the
Communication Protocols window and click the Configure button. The Modbus/ UDP
Configuration window is displayed.
•
To select a configured Modbus/UDP protocol connection, highlight Modbus/ UDP in the
Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
6.3.12.1
General Parameters
When Modbus/UDP is selected for configuration the Modbus/ UDP Configuration dialog is opened
with the General tab selected as shown below.
Figure 102: Modbus/UDP Configuration (General) Dialog Box
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
142
The Modbus Communication Settings grouping contains Modbus specific communication settings
including the addressing mode, the station address, the timeout interval as well as the number of
attempts.
The Addressing parameter selects standard or extended Modbus addressing. Standard addressing
allows 255 stations and is compatible with standard Modbus devices. Extended addressing allows
65534 stations, with stations 1 to 254 compatible with standard Modbus devices. The default is
Standard.
The Station parameter sets the target station number. The valid range is 1 to 255 if standard
addressing is used, and 1 to 65534 if extended addressing is used. The default is 1.
The Timeout parameter sets the length of time, in seconds, to wait for a response from the controller
before retrying (see Attempts), or ultimately failing. Valid entries are 1 to 255. The default is 3.
The Attempts parameter sets number of times to send a command to the controller before giving up
and reporting this failure to the host application. Valid entries are 1 to 20. The default is 3.
The Host Network Details grouping contains entries for the host’s IP address or name and
the TCP port on which it is listening.
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
The UDP Port No. field specifies the UDP port of the remote device. Valid values are 0 to
65535. The default value is 502.
•
Click Restore Defaults to restore default values to all fields on this page, except for the IP
Address / Name field. The content of this field will remain unchanged.
6.3.12.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
143
Figure 103: Modbus/UDP Configuration (Advanced) Dialog Box
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 246 when Addressing is set to Extended and Station is 255 or higher. When
Addressing is set to Extended and Station is less than 255 valid values are 2 to 248. When
Addressing is set to Standard valid values are 2 to 248.
•
Click Restore Defaults to restore default values to all fields on this page.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
144
6.3.12.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 104: Modbus/UDP Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.13
Modbus/USB
This driver provides the means to communicate with SCADAPack controllers equipped with a
Universal Serial Bus (USB) peripheral port using Modbus/USB messaging. The driver does not
require configuration making it possible to connect and communicate with a SCADAPack controller
almost instantaneously.
•
To configure a Modbus/USB protocol connection, highlight Modbus/USB in the
Communication Protocols window and click the Configure button. The Modbus/ USB
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
145
Configuration window is displayed. The pages in this configuration window are described in the
sections below.
•
To select a configured Modbus/USB protocol connection, highlight Modbus/ USB in the
Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
The following sections describe the information presented and user input required to configure the
Modbus/USB driver.
6.3.13.1
General Page
The general page identifies the type of driver and its author. This page also allows a user to specify
how the application searches and connects to a USB equipped SCADAPack controller. User input
depends on the number of USB equipped controllers connected on the bus.
Figure 105: Modbus/USB Configuration (General) Dialog Box
The Connection Settings grouping presents two connection options:
•
Select Automatic Connection when a single controller is present on the bus.
A typical scenario involves a single controller connected directly to a USB port on the host PC.
The driver will reject connection requests by the application if this mode is selected with multiple
controllers detected on the bus. In this case, the following error message is displayed:
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
146
Figure 106: Multiple Controller USB Error Dialog
Note that this option is selected by default.
•
Select Connect to controller with this ‘Controller ID when multiple controllers are present on
the bus.
A typical scenario involves more than one USB equipped SCADAPack controller connected via a
USB hub to the host PC.
If multiple controllers exist on the bus, the controller ID drop down box will display a list of all
identifiable devices. The user connects to the controller in question by selecting its Controller ID
from the list. The Controller ID takes on the format ‘A123456’ and can be found printed on the
controller casing or the circuit board.
Figure 107: Selecting a USB controller from list
Note that this option can also be used when there is a single controller present on the bus. However,
the Controller ID must be known and entered in the Controller ID dialog.
The chosen controller does need to be present on the bus at configuration time.
•
Click on the Restore Defaults button to reset the page contents to its default state.
In the default state, the Automatic Connection option is selected and the Controller ID text box is
disabled. Any text in the Controller ID text box remains but is displayed in grey.
6.3.13.2
Information Page
The Information page identifies the driver type and author. This page further provides detailed
driver information which can be useful in identification and troubleshooting scenarios.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
147
Figure 108: Modbus/USB Configuration (Information) Dialog Box
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
6.3.14
SCADAServer
The SCADAServer protocol specifies a SCADAServer Host connection. Applications will act as an
OPC client and route all programming commands through the SCADAServer Host to the
SCADAPack controller. The type of connection to the field device: no flow control, hardware flow
control or dial-up modem is configured in the SCADAServer Host itself.
•
To configure a SCADAServer protocol connection, highlight SCADAServer in the
Communication Protocols window and click the Configure button. The SCADAServer
Configuration window is displayed.
•
To select a configured SCADAServer protocol connection, highlight SCADAServer in the
Communication Protocols window and click the OK button.
•
To close the dialog, without making a selection click the Cancel button.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
148
6.3.14.1
General Parameters
When SCADAServer is selected for configuration the SCADAServer Configuration dialog is opened
with the General tab selected as shown below.
Figure 109: SCADAServer Configuration (General) Dialog Box
The Communication Settings grouping contains all essential details necessary to establish
communication to a device through a local or remote SCADAServer installation.
The Modbus Station parameter specifies the station address of the target device. The valid range is
1 to 65534. The default is station 1.
The Access Path parameter specifies the access path to a SCADAServer connection. This parameter
is entered as a string with a maximum size of 16 characters. This access path was named when a
connection was defined within the SCADAServer installation. If the access path is left blank, the
default SCADAServer connection will be used, as defined within the SCADAServer installation.
The default for this entry is blank.
The Use a remote server check box defines whether the SCADAServer connection uses a
SCADAServer installation installed on the same physical PC as the client application or on a remote
PC. If the SCADAServer installation is located on a separate machine, check this option and enter
the host name or IP address of the remote PC into the “IP Address / Name” edit box. If the
SCADAServer installation is located on the same PC as the client application leave this box
unchecked. The default state for this check box is unchecked.
The IP Address / Name entry specifies the Ethernet IP address in dotted quad notation, or a DNS
host name that can be resolved to an IP address, of the PC where the ClearSCADA server is
installed. The following IP addresses are not supported and will be rejected:
•
0.0.0.0 through 0.255.255.255
•
127.0.0.0 through 127.255.255.255 (except 127.0.0.1)
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
149
•
•
224.0.0.0 through 224.255.255.255
•
255.0.0.0 through 255.255.255.255.
Click Restore Defaults to restore default values to all fields on this page.
6.3.14.2
Advanced Parameters
Advanced parameters are used to control the message size for the protocol. Control over message
length is needed when writing large amounts of data over certain communication networks. A larger
value can improve communication speed but can increase the number of failed transmissions. A
smaller value can reduce the number of failed transmissions but may reduce throughput. When the
Advanced tab heading is clicked the Advanced dialog is opened as shown below.
Figure 110: SCADAServer Configuration (Advanced) Dialog Box
The Message Size grouping parameters are used to control the message size for the protocol. Control
over message length is needed when writing large amounts of data over certain communication
networks. A larger value can improve communication speed but can increase the number of failed
transmissions. A smaller value can reduce the number of failed transmissions but may reduce
throughput.
The Maximum selection indicates that the host application is to package messages using the
maximum size allowable by the protocol.
The Custom Value selection specifies a custom value for the message size. This value indicates to
the host application to package messages to be no larger than what is specified, if it is possible.
Valid values are 2 to 246.
•
Click Restore Defaults to restore default values to all fields on this page.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
150
6.3.14.3
Information
Information displays detailed driver information. When the Information tab heading is clicked the
Information dialog is opened as shown below.
Figure 111: SCADAServer Configuration (Information) Dialog Box
The Information grouping presents informative details concerning the executing protocol driver.
Module is the physical name of the driver.
File Version is the version number of the driver.
In GAC indicates whether the module (assembly) was loaded from the Global Assembly Cache
(GAC).
Runtime is the version of the Common Language Runtime (CLR) the driver was built against.
Copyright indicates the copyright information of the protocol driver.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
151
7
Activity Menu
The Activity commands select the mode of operation for the TelePACE program. The TelePACE
program can operate in three different programming modes, Edit Off Line, Edit On Line and Monitor
On Line. A check mark on the Activity drop down menu selection indicates the current mode.
7.1
Edit Off Line
The Edit Off Line selection enables editing of a ladder logic program without a connection to a
controller. The editing commands affect only the program file in use in the TelePACE Network
Ladder Editor. Forcing commands cannot be used in this mode. All other TelePACE commands can
be used in this mode.
7.2
Edit On Line
The Edit On Line selection is used to edit a ladder logic program loaded into a controller. All editing
commands affect the program in the controller and the file in the TelePACE Ladder Network Editor.
The multiple element selection and the cut, copy and paste functions of the Editor are not available
in this mode. Forcing commands can be used in this mode.
7.3
Monitor On Line
The Monitor On Line selection enables the monitoring of a program executing in a controller. The
editor shows the power flow through the ladder network on the screen. The Monitor List window is
displayed. No changes can be made to the program in monitor mode. Editing commands are disabled
on the menus. Forcing commands can be used in this mode. The C program loader is disabled in this
mode.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
152
8
Operation Menu
The Operation menu commands control the execution of the ladder logic program in the controller.
(Control of execution of a C Program in the controller is controlled from the C Program Loader
dialog.) The status of ladder logic program execution in the controller is displayed on the Status Bar.
8.1
Stop
The Stop command stops execution of the ladder logic program in the controller.
8.2
Debug
The Debug command start's the execution of the ladder logic program in debug mode. In debug
mode the monitor on line feature of the editor can be used to monitor the operation of the program.
The program runs slower in debug mode than in run mode.
8.3
Run
The Run command starts execution of the ladder logic program in run mode. The monitor on line
feature of the editor cannot be used to monitor execution in this mode.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
153
9
Options Menu
The Options menu commands are used to modify the Ladder Network Editor display, the use of
multiple coils and warning message options. The Option drop-down menu allows selection of the
option to modify.
9.1
Screen Font
The Screen Font selection selects the font used to display text on the Ladder Editor pane. This
selection does not affect the font in the Comment Editor pane, this pane uses the system font. A
dialog box appears that allows selection of the Font, Font Style and the Size of the font to be used in
the Ladder Editor pane.
9.2
Colors
The Colors dialog sets the colors used to display networks on the ladder editor and monitor on line
screens. The sample text and elements show how the colors look for the Edit Modes, Monitor Mode,
Forced Elements and the Contact Monitor.
The Item drop-down list box selects which item to modify. The follow items can be changed:
•
Element
•
Power Flow
•
Cursor
•
Forced (Foreground)
•
Forced (Background)
•
Contact Power Flow
•
The Color drop-down list box selects the color for the item.
•
Click Default to return the color selections to default values.
•
Click OK to accept the changes or Cancel to cancel the changes.
9.3
Floating-Point Settings
The Floating Point dialog controls the display precision and format of floating point numbers used in
TelePACE.
The Display Precision selection sets the number of digits after the decimal place that will be
displayed. Valid entries are 1 through 7. The default value is 2.
The Format drop down box selects the format of floating point numbers. The valid selections are:
•
Fixed displays numbers in the format ####.##.
•
Scientific displays numbers in the format #.### E###.
Click OK to close the dialog and save the settings.
Click Cancel to close the dialog and discards the changes.
9.4
Tool Bar
Selecting the Tool Bar option enables the Tool Bar to be displayed in the Network Editor. A check
mark to the left of the selection indicates the Tool Bar is active.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
154
9.5
Title Bar
Selecting the Title Bar option enables the Title Bar to be displayed in the Network Editor. A check
mark to the left of the selection indicates the Title Bar is active.
9.6
Status Bar
Selecting the Status Bar option enables the Status Bar to be displayed in the Network Editor. A
check mark to the left of the selection indicates the Status Bar is active.
9.7
Single Tag Names
The Single Tag Names selection enables the Editor to use one line to display tag names and
addresses on the Editor screen and printed network listings. The first 8 characters of the tag name are
displayed. A numeric value will be displayed if no tag name is defined for the address or constant. A
check beside the selection on the pull down menu indicates the mode selected.
9.8
Double Tag Names
The Double Tag Names selection enables the Editor to use two lines to display tag names and
addresses on the Editor screen and printed network listings. The first 16 characters of the tag name
will be displayed. A numeric value will be displayed if no tag name is defined for the address or
constant, or if the tag name is 8 characters or less in length. A check beside the selection on the pull
down menu indicates the mode selected.
9.9
Tag and Address
The Tag and Address selection enables the Editor to use three lines to display tag names and
addresses on the Editor screen and printed network listings. The first 16 characters of the tag name
are displayed, followed by the numeric address. A numeric value alone will be displayed if no tag
name is defined for the address or constant. A check beside this selection on the pull down menu
indicates the mode selected. A check beside the selection on the pull down menu indicates the mode
selected.
9.10
Numeric Address
The Numeric Address selection enables the Editor to use one line for numeric addresses on the editor
screen and printed network listings. No tag name is displayed, even if one is defined. A check beside
the selection on the pull down menu indicates the mode selected.
9.11
Allow Multiple Coils
The Allow Multiple Coils selection enables the use of multiple coils. Multiple coils are coils with the
same address.
When the Allow Multiple Coils is not selected the Editor will not allow the insertion of a coil that
has an address already in use in the program. An error message is displayed when the insertion is
attempted.
When the Allow Multiple Coils is enabled a Dialog box is displayed asking for confirmation when a
coil is inserted that has an address already in use in the program. A check beside this selection in the
pull down menu indicates multiple coils are allowed.
A check mark is displayed beside this command when it is enabled.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
155
9.12
Warning Messages
The Warning Messages option enables additional warning messages. A check mark is displayed
beside this command when it is enabled.
When this option is enabled warning messages are displayed on all errors.
When this option is disabled, some warning messages are replaced by a beep. This speeds up editing
for experienced users as they do not have to clear a message box when they occasionally make a
mistake.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
156
10
Help Menu
The Help selection allows access to the TelePACE program extensive on line help. A drop down
menu displays the selections for Contents, How to Use Help and About Program.
10.1
Contents
The Contents selection displays the TelePACE Program Help Window. Help is available on the
following topics.
The TelePACE Program Reference describes how each TelePACE command works.
The Ladder Logic Function Reference describes the logic function blocks.
The Controller Register Assignment describes the I/O modules used in the Register Assignment.
10.2
About Program
The About Program selection displays program version information and technical support phone and
fax numbers.
TelePACE Ladder Logic User and Reference Manual
May 9, 2007
157
TelePACE Ladder Logic
Function Reference
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
TelePACE Ladder Logic Function Reference
©2006 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TeleSAFE, TelePACE, SmartWIRE, SCADAPack, TeleSAFE Micro16 and
TeleBUS are registered trademarks of Control Microsystems Inc.
All other product names are copyright and registered trademarks or trade names
of their respective owners.
Material used in the User and Reference manual section titled SCADAServer
OLE Automation Reference is distributed under license from the OPC
Foundation.
TelePACE Ladder Logic Function Reference
February 19, 2007
1
Table of Contents
1
REGISTER TYPES ........................................................................................ 5
2
LADDER LOGIC FUNCTIONS ...................................................................... 6
2.1
ABS – Absolute Value.................................................................................... 7
2.2
ABSF - Floating-Point Absolute Value ........................................................... 8
2.3
ADD – Add Signed Values ........................................................................... 10
2.4
ADDF - Add Floating-Point Values............................................................... 12
2.5
ADDU – Add Unsigned Values..................................................................... 14
2.6
AND – And Block ......................................................................................... 16
2.7
CALL - Execute Subroutine.......................................................................... 18
2.8
Coil............................................................................................................... 20
2.9
CMPB – Compare Bit................................................................................... 21
2.10
CMP – Compare Signed Values .................................................................. 23
2.11
CMPU – Compare Unsigned Values............................................................ 25
2.12
DCTR – Down Counter ................................................................................ 27
2.13
DEVT – Generate DNP Event ...................................................................... 29
2.14
DIAL – Control Dial-Up Modem.................................................................... 30
2.15
DIV – Divide Signed Values ......................................................................... 34
2.16
DIVF - Divide Floating-Point Values............................................................. 36
2.17
DIVU – Divide Unsigned Values................................................................... 38
2.18
DLOG - Data Logger .................................................................................... 40
2.19
DPOL – Trigger a DNP class poll................................................................. 45
2.20
DSYC – Trigger a DNP clock synchronization ............................................. 47
2.21
DUNS – Trigger a DNP unsolicited response message ............................... 48
2.22
FIN – FIFO Queue Insert ............................................................................. 50
2.23
FOUT – FIFO Queue Remove ..................................................................... 52
2.24
FLOW – Flow Accumulator .......................................................................... 55
2.25
FTOS - Floating-Point to Signed Integer ...................................................... 59
2.26
FTOU - Floating-Point to Unsigned Integer.................................................. 61
2.27
GETB – Get Bit from Block .......................................................................... 63
2.28
GETL - Data Logger Extract......................................................................... 65
TelePACE Ladder Logic Function Reference
February 19, 2007
2
2.29
GTEF – Floating-Point Greater Than or Equal ............................................. 67
2.30
HART – Send HART Command................................................................... 69
2.31
INIM – Initialize Dial-Up Modem................................................................... 75
2.32
L–>L – List to List Transfer........................................................................... 78
2.33
L–>R – List to Register Transfer .................................................................. 80
2.34
LTEF - Floating-Point Less Than or Equal ................................................... 82
2.35
MOD – Modulus of Signed Values ............................................................... 84
2.36
MODU – Modulus of Unsigned Values......................................................... 86
2.37
MOVE – Move Block .................................................................................... 88
2.38
MSTR – Master Message ............................................................................ 90
2.39
MSIP – Master IP Message ......................................................................... 96
2.40
MUL – Multiply Signed Values ................................................................... 102
2.41
MULF - Multiply Floating-Point Values ....................................................... 104
2.42
MULU – Multiply Unsigned Values............................................................. 106
2.43
Normally Closed Contact ........................................................................... 108
2.44
Normally Open Contact.............................................................................. 109
2.45
NOT – Not Block ........................................................................................ 110
2.46
One Shot Coil............................................................................................. 112
2.47
OR – Or Block ............................................................................................ 113
2.48
OVER – Override Block of Registers ......................................................... 115
2.49
PID – PID Controller................................................................................... 118
2.50
PIDA – Analog Output PID......................................................................... 119
2.51
PIDD – Digital Output PID.......................................................................... 123
2.52
POWR – Floating-Point Raised to Power................................................... 127
2.53
PULM - Pulse Minutes ............................................................................... 129
2.54
PULS - Pulse Seconds............................................................................... 130
2.55
PUTB – Put Bit into Block .......................................................................... 131
2.56
PUT – Put Signed Value into Registers ..................................................... 133
2.57
PUTF - Put Floating-Point Value ................................................................ 135
2.58
PUTU – Put Unsigned Value into Registers ............................................... 137
2.59
R–>L – Register to List Transfer ................................................................ 139
2.60
ROTB – Rotate Bits in Block ...................................................................... 141
2.61
SCAL – Scale Analog Value....................................................................... 143
TelePACE Ladder Logic Function Reference
February 19, 2007
3
2.62
Shunts........................................................................................................ 146
2.63
SLP – Put Controller into Sleep Mode........................................................ 147
2.64
SQRF - Square Root of Floating-Point Value............................................. 150
2.65
STOF - Signed Integer to Floating-Point .................................................... 152
2.66
SUB – Subtract Signed Values .................................................................. 154
2.67
SUBF – Subtract Floating-Point Values ..................................................... 156
2.68
SUBR - Start of Subroutine ........................................................................ 158
2.69
SUBU –Subtract Unsigned Values............................................................. 159
2.70
Timers ........................................................................................................ 161
2.71
TOTL – Analog Totalizer ............................................................................ 163
2.72
UCTR – Up Counter................................................................................... 167
2.73
UTOF - Unsigned Integer to Floating-Point................................................ 169
2.74
XOR – Exclusive Or Block ......................................................................... 171
TelePACE Ladder Logic Function Reference
February 19, 2007
4
1
Register Types
TelePACE function elements support a number of different register formats. The type of register
format used will depend on the type function. The following table defines the register formats used.
Unsigned Integer
Signed Integer
Unsigned Double
Signed Double
Floating Point
Unsigned integer data are in the range 0 to 65535. This data requires
a single 16-bit register, 3xxxx or 4xxxx.
Signed integer data are in the range –32768 to 32767. This data
requires a single 16-bit register, 3xxxx or 4xxxx.
Unsigned long integer data are in the range 0 to 4,294,967,295. This
data requires two 16 bit registers, 3xxxx or 4xxxx. The lower numbered
register contains the lower order word.
Signed long integer data are in the range -2,147,483,648 to
2,147,483,647. This data requires two 16 bit registers, 3xxxx or 4xxxx.
The lower numbered register contains the lower order word.
Floating-point data are in the IEEE single precision floating-point
format. This data requires two 16 bit registers, 3xxxx or 4xxxx. The
lower numbered register contains the upper 16 bits of the number. The
higher numbered register contains the lower 16 bits of the number.
TelePACE Ladder Logic Function Reference
February 19, 2007
5
2
Ladder Logic Functions
The function blocks are described in detail in the pages that follow.
TelePACE Ladder Logic Function Reference
February 19, 2007
6
2.1
ABS – Absolute Value
Description
The ABS function stores the absolute value of a signed constant or register into a holding register.
When the enable ABS is ON the absolute value of the source register or constant is stored in the
destination holding register.
ON = enable ABS
source
copies status of input1
ABS
destination
Function Variables
Variable
Source
Destination
Valid Types
Constant
(-32768...32767)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
a signed value or register
destination = abs(source)
Related Functions
ABSF - Floating-Point Absolute Value
Example
network 1:
44001
ABS
45211
In this example the absolute value of the source, holding register 44001, is stored in the
destination, holding register 45211. Assuming holding register 44001 has a value of -4455, the
value stored in holding register 45211 would be +4455.
TelePACE Ladder Logic Function Reference
February 19, 2007
7
2.2
ABSF - Floating-Point Absolute Value
Description
The ABSF element stores the absolute value of a floating-point register or constant in a floatingpoint holding register.
When the enable input is ON the absolute value of the source is stored in the result floating-point
holding register. The element output is ON when the input is.
ON = enable
source
copies status of input
ABSF
result
Function Variables
The element has two parameters.
Variable
Source
Result
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
2 holding registers (4xxxx)
Description
a floating-point register or constant
value
floating-point absolute value of
source register
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower
16 bits of the number.
Floating point numbers can represent positive and negative values in the range –3.402 × 1038 to
3.402 × 1038.
Related Functions
ABS – Absolute Value
Example
network 1:
40001
ABSF
45555
TelePACE Ladder Logic Function Reference
February 19, 2007
8
In this example the absolute value of the source, holding register 40001, is stored in the result,
floating point register 45555. Assuming floating point register 40001 contains a floating-point value
of – 77988.99, the value stored in floating point register 45555 would be +77988.99.
TelePACE Ladder Logic Function Reference
February 19, 2007
9
2.3
ADD – Add Signed Values
Description
The ADD function block adds two registers or constants and stores the result in a holding register.
Signed addition is used. If the result is out of range, the sum rolls over and the out of range output is
enabled.
When the enable ADD input is ON the sum of value 1 and value 2 is stored in sum holding register.
If the sum is out of range (–32768...32767) the result out of range output is ON.
ON = enable ADD
value1
copies status of input1
value2
ON = result out of range
ADD
sum
Function Variables
Variable
Value 1
Value 2
Sum
Valid Types
Constant
(-32768...32767)
input register (3xxxx)
holding register (4xxxx)
constant
(-32768...32767)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
first signed value to add
second signed value to add
sum = value 1 + value 2
Related Functions
ADDF - Add Floating-Point Values
ADDU – Add Unsigned Values
Example
network 1:
42399
43567
( )
00017
ADD
44981
TelePACE Ladder Logic Function Reference
February 19, 2007
10
The ADD function in network 1 adds holding register 42399 to holding register 43567 and stores the
result is holding register 44981. When the addition is out of range – less than –32768 or greater than
32767-output coil 00017 is energized. The table below shows some examples.
value 1
Holding Register
42399
23411
–2047
12767
TelePACE Ladder Logic Function Reference
February 19, 2007
Value 2
Holding Register
43567
1098
819
23000
sum
Holding Register
44981
24509
–1228
–29769
out of range
Output Coil
00017
OFF
OFF
ON
11
2.4
ADDF - Add Floating-Point Values
Description
The ADDF element adds two floating-point registers or constants and stores the result in a floatingpoint holding register.
When the enable input is ON the sum value 1 + value 2 is stored in the sum floating point register.
The element output is ON when the input is.
ON = enable
value1
copies status of input
value2
ADDF
sum
Function Variables
The element has three parameters.
Variable
Value1
Value2
Sum
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
2 holding registers (4xxxx)
Description
first floating-point register or constant value to
add
second floating-point register or constant value
to add
floating-point sum = value1+value2
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower
16 bits of the number.
Floating point numbers can represent positive and negative values in the range –3.402 × 1038 to
3.402 × 1038.
Related Functions
ADD – Add Signed Values
ADDU – Add Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
12
Example
network 1:
+101.3
40098
ADDF
40100
The ADDF function in network 1 adds floating-point constant +101.3 to floating-point register
40098 (registers 40098 and 40099). Assuming floating point register 40098 contains a value of
+1000.00 then the result is +1101.30. This value is stored in floating-point register 40100 (registers
40100 and 40101).
TelePACE Ladder Logic Function Reference
February 19, 2007
13
2.5
ADDU – Add Unsigned Values
Description
The ADDU function block adds two registers or constants and stores the result in a holding register.
Unsigned addition is used. If the result is out of range, the sum rolls over and the out of range output
is enabled.
When the enable ADDU input is ON the sum of value 1 and value 2 is stored in sum holding
register. If the sum is out of range (> 65535) the result out of range output is ON.
ON = enable ADDU
value1
copies status of input1
value2
ON = result out of range
ADDU
sum
Function Variables
Variable
Value 1
Value 2
Sum
Valid Types
constant (0...65535)
input register (3xxxx)
holding register (4xxxx)
constant (0...65535)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
first unsigned value to add
Second unsigned value to add
Sum = value 1 + value 2
Related Functions
ADD – Add Signed Values
ADDF - Add Floating-Point Values
Example
network 1:
46549
44723
( )
00021
ADDU
44483
The ADDU function in network 1 adds holding register 46549 to holding register 44723 and stores
the result is holding register 44483. When the addition is out of range, greater than 65535, output
coil 00021 is energized. The table below shows some examples.
TelePACE Ladder Logic Function Reference
February 19, 2007
14
value 1
Holding Register
46549
2048
23000
35000
Value 2
Holding Register
44723
819
42530
35000
TelePACE Ladder Logic Function Reference
February 19, 2007
Sum
Holding Register
44483
2867
65530
4464
out of range
Output Coil
00021
OFF
OFF
ON
15
2.6
AND – And Block
Description
The AND function block logically ANDs the source block of registers with the destination block of
registers and stores the result in the destination block of registers. The number of registers in the
source and destination blocks is determined by the size.
ON = enable AND
source
copies status of input1
destination
AND
size
Function Variables
Variable
Source
Destination
Size
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
coil block (0xxxx)
holding register (4xxxx)
constant (1...100)
Description
The first register in the first source block.
The address for a coil or status register block is
the first register in a group of 16 registers that
will be ANDed.
The first register in the second source block and
destination block.
The address for a coil register block is the first
register in a group of 16 registers that will be
ANDed.
The number of 16 bit words in the block.
Notes
AND accesses 16 bit words. Coil and status register blocks are groups of 16 registers that start with
the register specified as the block address. A block size of 2 corresponds to 32 coils, or two holding
registers.
Coil and status register blocks must begin at the start of a 16 bit word within the controller memory.
Suitable addresses are 00001, 00017, 10001, 10033, etc.
Related Functions
OR – Or Block
XOR – Exclusive Or Block
NOT – Not Block
TelePACE Ladder Logic Function Reference
February 19, 2007
16
Example
network 1:
11000
01026
AND
1
In this example the source register has a value of 1521310 (0011101101101101). The destination
register has a value of 2237910 (0101011101101011) before the AND function and a value of
496910 (0001001101101001) after the AND function.
source register
0 0 1 1 1 0 1 1 0 1 1 0 1 1 0 1
destination register
before AND
0 1 0 1 0 1 1 1 0 1 1 0 1 0 1 1
destination register
after AND
0 0 0 1 0 0 1 1 0 1 1 0 1 0 0 1
TelePACE Ladder Logic Function Reference
February 19, 2007
17
2.7
CALL - Execute Subroutine
Description
The CALL element transfers execution from the main program to a subroutine. Execution of the
main program is suspended until the subroutine returns.
Subroutine calls can be used to execute parts of a program only when needed. The subroutine is
called only if the input to the CALL element is ON.
The function variable number indicates which subroutine to call. The subroutine number must
correspond to the number of a SUBR element.
ON = call subroutine
CALL
number
copy of input
Function Variables
The CALL element has one parameter:
Variable
Number
Valid Types
Constant
Description
the number of the subroutine. Any number in the range 1 to
500 is valid.
Notes
A subroutine can call other subroutines. This is called nesting. The maximum level of nesting is 20
calls.
Subroutine calls cannot be recursive. For example, subroutine 1 cannot call itself or call another
subroutine that calls subroutine 1. This prevents potential infinite loops in the ladder logic program.
The normal order of network evaluation is followed when executing each network. Execution
proceeds down the columns, then across the rows. When the CALL function is executed, the
execution of the current network is suspended at the point of the CALL until the subroutine returns.
A subroutine can be called by one or more CALL elements.
Related Functions
SUBR - Start of Subroutine
Example
This example calls subroutine 1 when input 10001 is on. Subroutine 1, in turn, calls Subroutine 2.
The sequence of execution is as follows.
The networks in the start of the main program are executed.
If input 10001 is on, Subroutine 1 is called.
At the beginning of Subroutine 1, Subroutine 2 is called.
The body of Subroutine 2 is executed.
The rest of Subroutine 1 is executed.
TelePACE Ladder Logic Function Reference
February 19, 2007
18
The networks in the rest of the main program are executed.
When execution reaches the start of Subroutine 1, the main program is complete. Execution starts
over at the start of the main program.
start of main program
10001
CALL
1
rest of main program
SUBR
1
CALL
2
rest of subroutine 1
SUBR
2
body of subroutine 2
TelePACE Ladder Logic Function Reference
February 19, 2007
19
2.8
Coil
Description
The COIL function block enables an output coil when its input power is ON.
input power
always connects to right rail
output
Function Variables
Variable
Output
Valid Types
coil register (0xxxx)
Description
output register address
Related Functions
One Shot Coil
Example
network 1:
( )
00009
01025
01025
00010
( )
When discrete input contact 00009 is closed power is applied to the input power input of coil
01025. This will enable the coil and the associated contact of 01025 is energized. The NO contacts
01025 are closed and this causes power to be applied to output coil 00010.
TelePACE Ladder Logic Function Reference
February 19, 2007
20
2.9
CMPB – Compare Bit
Description
The CMPB function block compares two blocks of registers, bit by bit and identifies the first bit that
does not match. The bit index will be set to the bit offset of the first mismatched bit.
ON = enable CMPB
ON = Start Compare at bit 0
OFF = Start Compare at last
mismatch
source 1
copies status of input 1
index and
source 2
ON = difference found
CMPB
size
ON = status of bit at index in
source 1 block.
Function Variables
Variable
Source 1
Index and
source 2
Size
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
constant (1..100)
Description
The first register in the first source block.
The address for a coil or status register block
is the first register in a group of 16 registers
that will be compared.
The bit index register and the second block of
source registers. The bit index is in register
[4xxxx]. A bit index of 0 is the most significant
bit of the first register of the source blocks.
The second source register block is at register
[4xxxx+1] to register [4xxxx+ size].
The number of 16 bit words in the blocks.
Notes
Compare accesses 16 bit words. Coil and status register blocks are groups of 16 registers that start
with the register specified as the block address. A block size of 2 corresponds to 32 coils, or two
holding registers.
Coil and status register blocks must begin at the start of a 16 bit word within the controller memory.
Suitable addresses are 00001, 00017, 10001, 10033, etc.
Related Functions
CMP – Compare Signed Values
CMPU – Compare Unsigned Values
GTEF – Floating-Point Greater Than or Equal
LTEF - Floating-Point Less Than or Equal
TelePACE Ladder Logic Function Reference
February 19, 2007
21
Example
network 1:
( )
01401
10001
01026
42100
( )
01366
01025
CMPB
1
The CMPB function in network 1 is used to check the status inputs 10001 to 10016. If Holding
Register 42100 is set to zero, with a PUTU function, any status inputs in the range 10001 to 10016
that are on will be detected by the CMPB function.
Using the information in the chart below, status input registers 10004,10013 and 10014 are on.
Closing contacts 01366 will start the index at bit 0 and the index will be set to the bit offset of the
first mismatched bit, bit 2. Discrete output coil 01026 will be on and discrete output coil 01025 will
be on.
If contacts 01366 are left closed the index will start at bit 0 and be set to the bit offset of the first
mismatched bit, bit 2, on each scan of network 1. Discrete output coil 01026 will be on and discrete
output coil 01025 will be on.
Opening contacts 01366 will allow the index to start at bit 2 on the next scan of network 1. The
index will be set to the bit offset of the next mismatched bit, bit 3. Discrete output coil 01026 will be
on and coil register 01025 will be on.
On the next scan of network 1 the index will start at bit 3. The index will be set to the bit offset of
the next mismatched bit, bit 12. Coil 01026 will be on and coil register 01025 will be on.
The next scan of network 1 will have the index starting at bit 12. The remaining bits are compared
and no further mismatches occur. The index will be set to bit 15 and wait for the contacts 01366 to
close to start the compare at bit index 0.
Bit Index:
Discrete Input State:
Discrete Input Address:
(read top to bottom)
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
0 0 1 1 0 0 0 0 0 0 0 0 1 0 0 0
1
0
0
1
6
1
0
0
1
5
1
0
0
1
4
1
0
0
1
3
1
0
0
1
2
TelePACE Ladder Logic Function Reference
February 19, 2007
1
0
0
1
1
1
0
0
1
0
1
0
0
0
9
1
0
0
0
8
1
0
0
0
7
1
0
0
0
6
1
0
0
0
5
1
0
0
0
4
1
0
0
0
3
1
0
0
0
2
1
0
0
0
1
22
2.10
CMP – Compare Signed Values
Description
The CMP function compares two signed registers or constants and stores the difference in a holding
register. When the enable CMP input is energized value 1 is compared to value 2.
If value 1 is greater than value 2 the value 1 > value 2 output is energized and the difference of
value 1 minus value 2 is stored in difference register.
If value 1 is less than value 2 the value 1 < value 2 output is energized and the difference of value 2
minus value 1 is stored in the difference register.
If value 1 equals value 2 the value 1 = value 2 output is energized and zero is stored in the
difference register.
ON = enable CMP
value 1
value 1 > value 2
value 2
value 1 = value2
CMP
difference
value 1 < value 2
Function Variables
Variable
value 1
Value 2
Difference
Valid Types
Constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
Constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
first signed value to compare
Second signed value to compare
if value 1 > value 2 then
difference = value 1 - value 2
if value 2 > value 1 then
difference = value 2 - value 1
Related Functions
CMPU – Compare Unsigned Values
CMPB – Compare Bit
GTEF – Floating-Point Greater Than or Equal
LTEF - Floating-Point Less Than or Equal
TelePACE Ladder Logic Function Reference
February 19, 2007
23
Example
n e tw o rk 1 :
30001
1638
+5
01257
(
)
00017
T .1
41050
CMP
+10
(
)
01257
41040
T .1
00017
41051
The CMP function in network 1 above compares the signed value of Analog Input Register 30001
with the value 1638. The output coil 00017 could be tied to a light to indicate when the Input
Register value is over 1638.
The value 1 > value 2 and value 1 = value 2 outputs are tied together. When value of register 30001
is greater than or equal to 1638 these outputs are energized. This will enable the flasher circuit of
Timers 41050 and 41051 to energize and output coil 00017 will cycle at a rate of 1 second on and
0.5 seconds off.
TelePACE Ladder Logic Function Reference
February 19, 2007
24
2.11
CMPU – Compare Unsigned Values
Description
The CMPU function compares two unsigned registers or constants and stores the difference in a
holding register. When enable CMPU input is energized value 1 is compared to value 2.
If value 1 is greater than value 2 the value 1 > value 2 output is energized and the difference of
value 1 minus value 2 is stored in difference register.
If value 1 is less than value 2 the value 1 < value 2 output is energized and the difference of value 2
minus value 1 is stored in the difference register.
If value 1 equals value 2 the value 1 = value 2 output is energized.
ON = enable CMPU
value 1
value 1 > value 2
value 2
value 1 = value2
CMPU
difference
value 1 < value 2
Function Variables
Variable
value 1
Value 2
Difference
Valid Types
Constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
Constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
first unsigned value to compare
Second unsigned value to compare
If value 1 > value 2 then
Difference = value 1 - value 2.
If value 2 > value 1 then
difference = value 2 - value 1.
Related Functions
CMPB – Compare Bit
CMP – Compare Signed Values
GTEF – Floating-Point Greater Than or Equal
LTEF - Floating-Point Less Than or Equal
TelePACE Ladder Logic Function Reference
February 19, 2007
25
Example
n e tw o rk 1 :
40001
(
)
00017
+3276
CMP
41040
(
)
01257
The CMPU function in network 1 above compares the unsigned value of holding register 40001 with
the value 3276. Coil 00017 is energized when holding register 40001 is greater than or equal to the
constant 3276.
The value 1 > value 2 and value 1 = value 2 outputs are tied together.
TelePACE Ladder Logic Function Reference
February 19, 2007
26
2.12
DCTR – Down Counter
Description
The DCTR function block decrements (subtracts 1 from) the value in the preset register or constant
and stores it in the counter holding register when the decrement count input changes from OFF to
ON. The counter stops counting when it reaches 0.
When the counting enabled input is ON and the decrement count goes from OFF to ON the
counter decrements by one. When the counting enabled input is OFF the counter value is reset to
preset.
When the counting enabled input is ON and the counter has decremented to zero then the counter =
0 output is ON.
When the counting enabled input is ON and the counter is greater than the preset then the counter >
0 output is ON.
OFF to ON = decrement count
preset
ON = counter = 0
ON = counting enabled
OFF = reset counter to preset
DCTR
counter
ON = counter > 0
Function Variables
Variable
Preset
Counter
Valid Types
constant (1..65535)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
Preset value for counter
Current counter value
Related Functions
UCTR – Up Counter
TelePACE Ladder Logic Function Reference
February 19, 2007
27
Example
n e tw o rk 1 :
+1
01057
(
)
01057
T .1
46770
01057
01058
100
(
)
01058
DCTR
45776
The DCTR function in network 1 decrements each time the timer output is enabled. The timer limit
is 0.1 seconds and it will take 10 seconds for the DCTR to decrement 100 times.
When the DCTR decrements to 0, output coil 01058 is energized. NC contacts 01058 will open and
the DCTR will reset counter to preset. This will happen every 10 seconds.
TelePACE Ladder Logic Function Reference
February 19, 2007
28
2.13
DEVT – Generate DNP Event
Description
This function generates a DNP change event for the specified DNP point.
A change event is generated for the Point Address specified when the enable input changes from
OFF to ON. The status register is set to 0 and the success output is energized if the function is
successful and a change event was generated.
The status register is set to 1 and the failure output is energized if the function failed and a change
event was not generated. The failure output indicates that the specified DNP point is invalid, or the
DNP configuration has not been created.
enable
Point type
Point
address
success
failure
DEVT
status
Function Variables
Variable
Point
Type
Point
Address
Status
Valid
Types
Constant or
holding
register
(4xxxx)
Constant or
holding
register
(4xxxx)
Holding
register
(4xxxx)
Description
DNP Point Type. Valid values are:
0 = Binary Input,
1 = 16-bit Analog Input,
2 = 32-bit Analog Input,
3 = Float Analog Input,
5 = 16-bit Counter Input,
6 = 32-bit Counter Input.
DNP Point Address
Status of the operation
0 = success
1 = failure
Related Functions
DUNS – Trigger a DNP unsolicited response message
DPOL – Trigger a DNP class poll
Error! Not a valid link.
TelePACE Ladder Logic Function Reference
February 19, 2007
29
2.14
DIAL – Control Dial-Up Modem
Description
The DIAL function connects an internal modem or an external modem to a remote modem. Only one
DIAL block may be active on each serial communication port at any one time. The DIAL function
handles all port sharing and multiple dialing attempts.
Note: The SCADAPack 100 does not support dial up connections on com port 1. SCADASense
Series controllers do not support dialup connections.
When the enable DIAL input is ON the DIAL element sends the modem initialization string to the
modem. The modem will attempt to connect to the remote modem. If a connection is made the ON
when connection complete output is turned ON. If a connection is not made in the specified number
of attempts the ON when all connect attempts have failed output is turned ON.
The enable DIAL input must be energized for the entire DIAL time, including multiple dial
attempts.
Note: A pause is required between hanging up the phone line after a DIAL and initiating a new
DIAL attempt. This is required for the external modem to hang-up.
ON = enable DIAL
config
ON when connection is
complete
DIAL
status
ON when all connect
attempts have failed
Function Variables
Variable
Config
Valid Types
Holding register (4xxxx)
TelePACE Ladder Logic Function Reference
February 19, 2007
Description
Address of the first register in the
configuration block. There are 39
registers in the block at addresses
config+0 to config+38.
+0 = Communication port
+1 = Dialing attempts
+2 = Connect time
+3 = Pause time
+4 = Dialing type
+5 = Length of modem string
+6 = Modem initialization string
+22 = Length of phone number
+23 = Phone number
NOTE:
Registers should be programmed
using the Element Configuration
command.
30
Variable
Config
Valid Types
Holding register (4xxxx)
Status
Holding register (4xxxx)
Description
Address of the first register in the
configuration block. There are 39
registers in the block at addresses
config+0 to config+38.
+0 = Communication port
+1 = Dialing attempts
+2 = Connect time
+3 = Pause time
+4 = Dialing type
+5 = Length of modem string
+6 = Modem initialization string
+22 = Length of phone number
+23 = Phone number
NOTE:
Registers should be programmed
using the Element Configuration
command.
address of the first register in the
status block. There are 2 registers
in the block at addresses
status+0 and status+1.
+0 = error code
+1 = reservation identifier
Element Configuration
This element is configured using the DIAL Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
TelePACE Ladder Logic Function Reference
February 19, 2007
31
The modem initialization string and the phone number are packed. Two ASCII characters are stored
in each register.
The error codes are:
Error Code
0
1
2
3
4
5
6
7
8
9
Description
No Error
Bad configuration error occurs when an incorrect initialization string is sent
to the modem. This usually means the modem does not understand a
specific command in the initialization string.
No modem connected to the controller serial port, or the controller serial
port is not set to RS232 Modem.
Initialization error occurs when the modem does not respond to the
initialization string and may be turned off.
No dial tone error indicates modem is not connected to a telephone line or
the S6 setting in the modem is too short.
Busy line indicates another device is using the phone line.
Call aborted by the program. This will occur if the enable DIAL input goes
OFF before a modem connection occurs.
Failed to connect error occurs when there are no other errors but the
modem failed to make a connection with the remote modem.
Carrier lost error occurs when carrier is lost for a time exceeding the S10
setting in the modem. Phone lines with call waiting are very susceptible to
this condition.
“Serial port is not available” error occurs when the DIAL function attempts
to use the serial port when another ladder communication element, C
program or an incoming call has control of the port.
TelePACE Ladder Logic Function Reference
February 19, 2007
32
Notes
The reservation identifier is required for the operation of the dialer but can be ignored by the ladder
program.
The DIAL function outputs are powered only when the enable DIAL input is powered ON.
The dial-up connection handler prevents outgoing calls from using the serial port when an incoming
call is in progress and communication is active. If communication stops for more than five minutes,
then outgoing call requests are allowed to end the incoming call. This prevents problems with the
modem or the calling application from permanently disabling outgoing calls.
Note: The SCADAPack 100 does not support dial up connections on com port 1.
SCADASense Series controllers do not support dial up connections.
To optimize performance, minimize the length of messages on com3 and com4. Examples of
recommended uses for com3 and com4 are for local operator display terminals, and for programming
and diagnostics using the TelePACE program.
Related Functions
INIM – Initialize Dial-Up Modem
Example
An example of dialing using the DIAL block is the file DIAL.LAD. This file is automatically
installed on the computer when the TelePACE program is installed. It is located in the
TELEPACE\EXAMPLES directory.
TelePACE Ladder Logic Function Reference
February 19, 2007
33
2.15
DIV – Divide Signed Values
Description
The DIV function block divides two registers or a constant, value 1, by a register or constant, value
2, and stores the quotient in a Holding Register, result. Signed division is used. The values and
result are signed numbers.
The result out of range output is enabled if the result is greater than 32767 or less than –32768. The
divide by zero output is enabled if value 2 equals 0.
ON = enable DIV
value 1
copies status of input 1
value 2
ON = result out of range
DIV
result
ON = divide by zero
Function Variables
Variable
value 1
Value 2
Result
Valid Types
constant
(-32768..32767)
2 Input registers (3xxxx)
2 holding registers (4xxxx)
constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
holding registers (4xxxx)
Description
Signed value to divide
The low order word is stored in the
first register if registers are used.
Signed value to divide by
Result = value 1 / value 2
Related Functions
DIVF - Divide Floating-Point Values
DIVU – Divide Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
34
Example
network 1:
-32100
41012
+1
-200
( )
01025
MUL
DIV
41012
41204
( )
01026
The MUL function is used to create the double precision values required for value 1. A constant is
multiplied by 1 with the result stored in Holding Register 41012. The low order word, 41012, and
the high order word, 41013, are returned from the MUL function.
The following table illustrates various value 1 and value 2 values and the result of the division.
Example
1
Example
2
Example
3
Example
4
high order low order
Register
Register
41013
41012
value 1
-1
-32070
Constant
Value
value 2
-200
Register
41204
result
160
0
32070
-200
-160
-1
-2048
16
-128
0
3276
30
109
TelePACE Ladder Logic Function Reference
February 19, 2007
35
2.16
DIVF - Divide Floating-Point Values
Description
The DIVF element divides one floating-point register or constant by another and stores the result in a
floating-point holding register.
When the enable input is ON the result value 1 ÷ value 2 is stored in the result floating-point
register. The top output is ON when the input is. The middle output is ON if value2 equals 0 and the
input is ON.
ON = enable
value1
copies status of input
value2
ON = divide by zero
DIVF
result
Function Variables
The element has three parameters.
Variable
value1
Value2
Result
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
2 holding registers (4xxxx)
Description
Floating-point register or constant
value to divide
Floating-point register or constant
value to divide by
Floating-point result = value1 ÷
value2
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number.
Floating point numbers can represent positive and negative values in the range –3.402 × 1038 to
3.402 × 1038.
Related Functions
DIV – Divide Signed Values
DIVU – Divide Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
36
Example
network 1:
+917.15
40100
DIVF
40102
The DIVF function in network 1 divides floating-point constant +917.15 by the contents of floatingpoint register 40100 (registers 40100 and 40101). Assuming floating-point register 40100 has a
value of 5.00 then the result is +183.43. This value is stored in floating-point register 40102
(registers 40102 and 40103).
TelePACE Ladder Logic Function Reference
February 19, 2007
37
2.17
DIVU – Divide Unsigned Values
Description
The DIVU function block divides two registers or a constant, value 1, by a register or constant,
value 2. The quotient is stored in a Holding Register, result. Unsigned division is used. The values
and result are unsigned numbers.
The result out of range output is enabled if the result is greater than 65535 or less than 0. The
divide by zero output is enabled if value 2 equals 0.
ON = enable DIVU
value 1
copies status of input 1
value 2
ON = result out of range
DIVU
result
ON = divide by zero
Function Variables
Variabl
e
value 1
Value 2
Result
Valid Types
constant (0..65535)
2 Input registers
(3xxxx)
2 holding registers
(4xxxx)
constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
holding registers (4xxxx)
Unsigned value to divide
The low order word is stored in the
first register if registers are used.
Unsigned value to divide by
Result = value 1 / value 2
Related Functions
DIV – Divide Signed Values
DIVF - Divide Floating-Point Values
TelePACE Ladder Logic Function Reference
February 19, 2007
38
Examples
n e tw o rk 1 :
43186
47722
+1
622
(
)
02561
M ULU
D IV U
47722
47742
(
)
02562
The MULU function is used to create the double precision values required for value 1. A constant is
multiplied by 1 with the result stored in Holding Register 47722. The low order word, 47722, and
the high order word, 47723, are returned from the MULU function. The MULU function ensures a
value of 0 in the high order word.
The following table illustrates various value 1 and value 2 values and the result of the DIVU
function.
Example 1
Example 2
Example 3
Example 4
high
low
order
order
Register Register Constant Registe
47723
47722
Value
r 47742
value 1
value 2
result
0
53186
622
85
0
7000
70
100
0
8192
819
10
0
42998
226
190
TelePACE Ladder Logic Function Reference
February 19, 2007
39
2.18
DLOG - Data Logger
Description
The DLOG function records entries in a data log. When a low to high transition occurs on the
enable DLOG input, the data log identified by LogID is created and initialized. If the data log
exists and has a different configuration then an error will be generated. If an error is generated (see
status codes below) then a different LogID must be used or the log must be deleted using the delete
log input.
While the enable DLOG is ON and a low to high transition occurs on the grab data input, an entry
is recorded in the data log identified by LogID.
When the delete log input is low, all records in the data log are deleted.
The top output is a copy of the top input. The error output is ON if there was a creation,
configuration or data logging error. The outputs are powered only when the enable input is powered.
NOTE: In order for the changes to an existing DLOG configuration to take effect, the following
steps must be followed:
•
Read the data from the log, if desired.
•
Disable the DLOG
•
Delete the log
•
Write the new configuration
•
Enable the log
ON = enable DLOG
config
copies state of input 1
OFF to ON = grab data
status
ON = error
OFF = delete log
DLOG
LogID
TelePACE Ladder Logic Function Reference
February 19, 2007
40
Function Variables
Variable
Config
Valid Types
18 holding registers
(4xxxx)
Status
Holding register (4xxxx)
Log ID
Constant (1 to 16)
Description
Address of the first register of the log configuration
block. There are 18 registers in the block at
config+0 to config+17.
+0 = Maximum number of records in the log.
+1 = number of data fields.
+2 = Field #1 register address
+3 = Field #1 data type (see data types below)
+4 = Field #2 register address
+5 = Field #2 data type
+6 = Field #3 register address
+7 = Field #3 data type
+8 = Field #4 register address
+9 = Field #4 data type
+10 = Field #5 register address
+11 = Field #5 data type
+12 = Field #6 register address
+13 = Field #6 data type
+14 = Field #7 register address
+15 = Field #7 data type
+16 = Field #8 register address
+17 = Field #8 data type
Address of the status register.
+0 = status code (see status codes below)
Identifies the internal log.
Configuration Register
A Field Register Address is the address of a Modbus register, or the address of the first Modbus
register of a small block of consecutive registers. Valid values are any register in the range 00001 to
49999.
The configuration data types are:
Data Type
0
1
2
3
4
5
Description
16 bit unsigned integer
16 bit signed integer
32 bit unsigned integer
32 bit signed integer
32 bit floating point
Days and hundredths of seconds in two 32 bit unsigned integers.
The first two registers are an Unsigned Double containing the number of
complete days since 01/01/97
The last two registers are an Unsigned Double containing the number of
hundredths of a second since the start of the current day.
TelePACE Ladder Logic Function Reference
February 19, 2007
41
Status Register
The status register stores the result of a log attempt. It can have the following values. If the status
register is not equal to 10 then the error output is turned on.
The status codes are:
Status Code
10
11
12
13
14
15
16
17
Description
The configuration is valid and data can be logged.
A different configuration already exists for the log.
The log ID is invalid.
The configuration was not valid and was rejected.
There is not enough memory available to create a log of the request size.
The number of data fields was invalid.
The log was successfully deleted. No log configuration exists.
Undefined status. This should never occur.
DLOG Element Configuration
This element is configured using the DLOG Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
WARNING:
If the controller is initialized, using the Initialize command in the Controller
menu, all I/O database registers used for Element Configuration are set to
zero. The application program must be re-loaded to the controller.
DLOG Element Configuration Dialog
Selecting Element Configuration from the Edit menu while the cursor is over a DLOG element can
access this dialog.
The addresses are determined from the ladder element. They cannot be modified in this dialog.
The Number of Records selects the number of records in the log. Each record contains the data for
all the fields in the log. The number of records available will depend on the type of controller used.
For SCADAPack 100: 256K controllers the maximum number of records is 190 records of 8
unsigned integer fields.
For SCADAPack LP and SCADAPack 100: 1024K controllers the maximum number of records is
approximately 22970 records of 8 unsigned integer fields.
For SCADAPack and Micro16 controller the number of records depends on the available memory in
socket U10 in the controller. For example a 128K RAM in U10 will allow approximately 190
TelePACE Ladder Logic Function Reference
February 19, 2007
42
records of 8 unsigned integer fields and a 512K RAM in U10 will allow approximately 22970
records of 8 unsigned integer fields.
For SCADAPack 32 controllers the maximum number of records is 58,352 records of 8 unsigned
integer fields for a total of 466816 words. The maximum number of records will be reduced if DNP
protocol, RealFLO or custom C++ applications are used in the controller.
For SCADAPack 350 controllers the maximum number of records is 56,743 records of 8 unsigned
integer fields for a total of 453947 words. The maximum number of records will be reduced if DNP
protocol, RealFLO or custom C++ applications are used in the controller.
The Field entries contain information about each item in the log. The fields are numbered,1 through
8, as they are added to the record. The Registers column contains the Modbus registers used in for
the field. The Type column contains the Modbus register type and the Tag column contains the tag
name for the Modbus Register.
Press the Add key to add an item to the end of the list. When selected the Add/Edit DLOG Field
dialog is displayed, see description of this dialog below. The key is grayed if the list is full.
Press the Edit key to modify the currently selected item in the list. When selected the Add/Edit
DLOG Field dialog is displayed. The key is grayed if the list is empty.
Press the Delete key to delete the currently selected item from the list. The key is grayed if the list is
empty.
Press the Move Up key to move the currently selected item up one position in the list. The key is
grayed if the list is empty or the selected item is at the top of the list.
Press the Move Down key to move the currently selected item down one position in the list. The key
is grayed if the list is empty or the selected item is at the bottom top of the list.
Press OK to accept the current list.
Press Cancel to discard the changes made to the list.
Data Log Field Dialog
This dialog can be accessed by pressing Add or Edit from the DLOG Element Configuration dialog.
The Address entry will contain the Modbus register address for the record if the Edit button was
selected. This entry will be zero if the Add button was selected. Valid values are any register in the
range 00001 to 49999.
The Tag entry contains the tagname for the selected register address if one exists. The drop down list
will display all tag names for valid address. Selecting a tag name from the list will cause the
associated register address to be displayed in the Address entry.
The Data Type selection allows the selection of one of the following data types:
TelePACE Ladder Logic Function Reference
February 19, 2007
43
16 bit unsigned integer
16 bit signed integer
32 bit unsigned integer
32 bit signed integer
32 bit floating point
Days and hundredths of seconds in two 32 bit unsigned integers
Press OK to validate the data and close the dialog.
Press Cancel to discard the changes made in the dialog.
The output bits are powered only when the enable input is powered.
Related Functions:
GETL - Data Logger Extract
TelePACE Ladder Logic Function Reference
February 19, 2007
44
2.19
DPOL – Trigger a DNP class poll
Description
This function sends a DNP Class Poll message to request the specified data classes from a DNP
slave. The DNP class poll is requested when the enable input changes from OFF to ON.
The status register is set to 0 and the success output is energized if the function was successful.
The 'success' output is energized immediately if the poll was triggered successfully. It does not
provide any information about the success or otherwise of the actual message transaction.
The status register is set to 1 and the failure output is energized if the function failed. Failure
indicates the specified slave address has not been configured in the DNP Routing Table, or the DNP
configuration has not been created.
enable
slave
address
classes
success
failure
DPOL
status
Function Variables
Variable
Slave Address
Valid Types
Constant or holding register
(4xxxx)
Description
DNP slave station address
Classes
Constant or holding register
(4xxxx)
Status
Holding register (4xxxx)
This is a bit-mapped register containing
the classes of data to be included in the
class poll message. If multiple classes
are required the following values should
be added together.
1 = class 0 data
2 = class 1 data
4 = class 2 data
8 = class 3 data
Status of the operation
0 = success
1 = failure
Notes
This function is available on the SCADAPack 350 SCADAPack 32 controllers only.
The function sets internal flags to trigger a DNP poll message, and returns immediately. The DNP
message will be sent some time after the function call.
TelePACE Ladder Logic Function Reference
February 19, 2007
45
Related Functions
DEVT – Generate DNP Event
DUNS – Trigger a DNP unsolicited response message
TelePACE Ladder Logic Function Reference
February 19, 2007
46
2.20
DSYC – Trigger a DNP clock synchronization
Description
This function sends a Clock Synchronization message to a DNP slave.
The Clock Synchronization message is sent to the slave address when the enable input changes
from OFF to ON. The status register is set to 0 and the success output is energized if the function
was successful.
The status register is set to 1 and the failure output is energized if the Time Synchronization
message failed. The failure output indicates the specified slave address has not been configured in
the DNP Routing Table, or the DNP configuration has not been created.
enable
slave
address
success
DSYC
status
failure
Function Variables
Variable
Slave Address
Valid Types
Constant or holding register
(4xxxx)
Description
DNP slave station address
Status
Holding register (4xxxx)
Status of the operation
0 = success
1 = failure
Notes
This function is available on the SCADAPack 32 only.
The function sets internal flags to trigger a DNP message and returns immediately. The DNP
message will be sent some time after the function call.
Related Functions
DEVT – Generate DNP Event
DPOL – Trigger a DNP class poll
DUNS – Trigger a DNP unsolicited response message
TelePACE Ladder Logic Function Reference
February 19, 2007
47
2.21
DUNS – Trigger a DNP unsolicited response message
Description
The DUNS function triggers a DNP unsolicited response message of the specified class or classes.
The unsolicited response for the specified classes is triggered when the enable input changes from
OFF to ON. The status register is set to 0 and the success output is energized if the message was
triggered successfully.
The status register is set to 1 and the failure output is energized if the unsolicited response message
failed. The failure output indicates master addresses have not been configured in the DNP Routing
Table, or the DNP configuration has not been created.
classes
enable
DUNS
status
success
failure
Function Variables
Variable
Classes
Valid Types
Constant or
holding
register
(4xxxx)
Status
Holding
register
(4xxxx)
Description
This is a bit-mapped register containing the classes of data to
be included in the unsolicited message. If multiple classes are
required the following values should be added together.
1 = class 0 data
2 = class 1 data
4 = class 2 data
8 = class 3 data
Status of the operation
0 = success
1 = failure
Notes
The function sets internal flags to trigger a DNP unsolicited message, and returns immediately. The
DNP message will be sent some time after the function call.
DNP unsolicited messages do not have to be enabled in the Application Layer configuration for
events to be sent with this function. Unsolicited messages at Start Up must be enabled, or the master
must enable unsolicited messages before the first message can be sent.
If no events are pending an empty unsolicited message will be sent.
The message will be sent to the configured DNP master station or stations.
The return status indicates whether the flags were set. The status will be FALSE if the DNP engine is
not running.
Related Functions
DPOL – Trigger a DNP class poll
TelePACE Ladder Logic Function Reference
February 19, 2007
48
DUNS – Trigger a DNP unsolicited response message
TelePACE Ladder Logic Function Reference
February 19, 2007
49
2.22
FIN – FIFO Queue Insert
Description
The FIN function inserts the contents of the source register into the First-In-First-Out (FIFO) queue.
Values in the FIFO queue are pushed down until the queue is full.
When the enable insert input is ON and the FIFO full is not ON, the source register is inserted into
the queue.
The index is incremented by one after each insert until the index value equals the size. When the
index equals the size and enable insert is ON then FIFO full turns ON and no further insertions can
take place.
The FIFO Queue Insert function is used with the FIFO Queue Remove function to enable full control
of the FIFO Queue.
ON = enable insert
source
copies status of input 1
queue
ON = FIFO full
FIN
size
Function Variables
Variable
Source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Queue
holding register (4xxxx)
Size
constant (1..9999)
Description
The address of the source register.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
inserted.
The address of the index register
and the queue registers. The index
is stored in register [4xxxx]. The
FIFO queue is located in register
[4xxxx+1] to
register [4xxxx + size].
The number of registers in the
queue.
Notes
FIN accesses 16 bit words. Coil and status register blocks are groups of 16 registers that start with
the register specified as the block address. Coil and status register blocks must begin at the start of a
16 bit word within the controller memory. Suitable addresses are 00001, 00017, 10001, 10033, etc.
Related Functions
FOUT – FIFO Queue Remove
TelePACE Ladder Logic Function Reference
February 19, 2007
50
Example
See the example for the FOUT function.
TelePACE Ladder Logic Function Reference
February 19, 2007
51
2.23
FOUT – FIFO Queue Remove
Description
The FOUT function removes a value from the first-in-first-out (FIFO) queue and transfers it into the
destination register. Values in the queue are moved up, until the queue is empty.
When the enable remove input is ON and the FIFO empty is not ON, the first queue register is
transferred into the destination register.
The index is decremented by one after each transfer until the index value equals zero. When the
index equals zero and the enable remove input is ON the FIFO empty turns ON and no further
removals can take place.
The FIFO Queue Remove function is used with the FIFO Queue Insert function to enable full control
of the FIFO Queue. See FIFO Queue example.
ON = enable remove
queue
copies status of input 1
destination
FOUT
size
ON = FIFO empty
Function Variables
Variable
Queue
Valid Types
Holding register (4xxxx)
Destination
coil block (0xxxx)
holding register (4xxxx)
Size
Constant (1..9999)
Description
The address of the index register
and the queue registers. The index
is stored in register [4xxxx]. The
FIFO queue in located in register
[4xxxx+1] to
Register [4xxxx + size].
The address of the destination
register.
The address for a coil register block
is the first register in a group of 16
registers.
The number of 16 bit registers in
the queue.
Notes
FOUT accesses 16 bit words. Coil blocks are groups of 16 registers that start with the register
specified as the block address. Coil blocks must begin at the start of a 16 bit word within the
controller memory. Suitable addresses are 00001, 00017, 00033, etc.
Related Functions
FIN – FIFO Queue Insert
TelePACE Ladder Logic Function Reference
February 19, 2007
52
Example
01057
42012
(
42599
)
00017
F IN
+4
01058
42599
42016
FOUT
+4
(
)
00018
The following discussion describes the operation of a FIN function. The queue starts out empty with
the FIFO index register having a value of zero.
Source
Register
42012
FIFO
Queue
Regist
ers
Source
Register
Data
Xxxx
FIFO Index-->
FIFO register 0-->
FIFO register 1-->
FIFO register 2-->
FIFO register 3-->
42599
42600
42601
42602
42603
When FIFO queue index register 42599 has a value of 0 and the FIN function is enabled, by closing
contact 1057, the contents of source register 42012 is inserted into FIFO Queue register 42600 and
the index is incremented to 1.
When FIFO queue index register 42599 has a value of 1 and the FIN function is enabled, by closing
contact 1057, the contents of queue register 42600 is transferred to queue register 42601. The
contents of source register 42012 are inserted into FIFO queue register 42600, and the index is
incremented to 2.
When FIFO queue index register 42599 has a value of 2 and the FIN function is enabled, by closing
contact 1057, the contents of queue register 42601 is transferred to queue register 42602. The
contents of queue register 42600 is transferred to queue register 42601, the contents of source
register 42012 is inserted into FIFO queue register 42600 and the index is incremented to 3.
When FIFO queue index register 42599 has a value of 3 and the FIN function is enabled, by closing
contact 1057, the contents of queue register 42602 is transferred to queue register 42603. The
contents of queue register 42601 is transferred to queue register 42602, the contents of queue register
42600 is transferred to queue register 42601, the contents of source register 42012 is inserted into
FIFO queue register 42600 and the index is incremented to 4.
The queue is now full and no further insertions are allowed. Coil 00017 will turn ON. The FOUT
Queue Remove function must be used to remove values from the queue.
The following discussion describes the operation of a FOUT function. The queue starts out full with
the FIFO index register having a value of three.
TelePACE Ladder Logic Function Reference
February 19, 2007
53
FIFO
Queue
Registers
FIFO Index-->
FIFO register 0->
FIFO register 1->
FIFO register 2->
FIFO register 3->
FIFO
Queue
Register
Data
Destination
Register
xxxx
42016
42599
42600
42601
42602
42603
When FIFO queue index register 42599 has a value of 4 and the FOUT function is enabled, by
closing contact 1058, the contents of queue register 42603, pointed to by the index is transferred to
the FIFO destination register 42016 and the index is decremented by one.
When FIFO queue index register 42599 has a value of 3 and the FOUT function is enabled, by
closing contact 1058, the contents of queue register 42602 is transferred to the FIFO destination
register 42016 and the index is decremented by one.
When FIFO queue index register 42599 has a value of 2 and the FOUT function is enabled the
contents of queue register 42601 is transferred to the FIFO destination register 42016 and the index
register is decremented by one.
When FIFO queue index register 42599 has a value of 1 and the FOUT function is enabled, by
closing contact 1058, the contents of queue register 42600 is transferred to the FIFO destination
register 42016 and the index is decremented to 0.
The queue is now empty and no further removals are allowed. Coil 00018 will be now be energized.
The FIN Queue Insert function must be used to insert values into the queue.
TelePACE Ladder Logic Function Reference
February 19, 2007
54
2.24
FLOW – Flow Accumulator
Description
The FLOW function accumulates flow from pulse type devices such as turbine flow meters.
When the accumulate input is ON the function accumulates volume and calculates the flow rate.
When the Log Data input goes from OFF to ON, the accumulated volume, flow time and the time at
the end of the period is saved in the history registers. Older history is pushed down and the oldest
record is discarded. The Log Data input must be triggered at least once every 119 hours (at the
maximum pulse rate). Otherwise the volume accumulator will overflow, and the accumulated
volume will not be accurate.
When the accumulator enabled input is ON, accumulation and rate calculations are enabled. When
the input is OFF, all accumulators and the rate outputs are set to zero.
The function reads and accumulates the number of pulses, and divides by the K factor to calculate
the total volume. This is done on each scan of the controller logic. The function calculates the flow
rate in engineering units based on the K-factor provided. The rate updates once per second if there is
sufficient flow. If the flow is insufficient, the update slows to as little as once every ten seconds to
maintain resolution of the calculated rate.
ON = accumulate flow
config
OFF to ON = log data
outputs
ON = enable accumulation
OFF = clear outputs
FLOW
records
copies state of input 1
ON = error
Function Variables
Variable
Config
Valid Types
holding register (4xxxx)
TelePACE Ladder Logic Function Reference
February 19, 2007
Description
Address of the first register of the
configuration block. There are five
registers in the block at config+0 to
config+4.
+0, 1 = K factor (floating-point)
+2 = input register (3xxxx or 4xxxx)
+3 = input type (see table below)
+4 = rate period (see table below)
55
Variable
Outputs
Valid Types
holding register (4xxxx)
Records
Constant
Description
Address of the first register of the
output block. There are 18 to 222
registers in the block at outputs+0
to outputs+221. The number of
registers used depends on the
records variable.
+0 = status (see table below)
+1,2 = flow rate (floating-point)
+3,4 = internal: rate accumulator
+5,6 = internal: time of last rate
+7,8 = internal: input at last sample
+9,10 = internal: pulse accumulator
+11 = number of records to follow
+12,13 = volume for period 1 (float)
+14,15 = time at end of period 1
+16,17 = flow time for period 1
+18,19= volume for period 2 (float)
+20,21 = time at end of period 2
+22,23 = flow time for period 2
+24,25= volume for period 3 (float)
+26,27 = time at end of period 3
+28,29 = flow time for period 3
…
+216,217 = volume for period 35
(float)
+218,219 = time at end of period 35
+220,221 = flow time for period 35
The number of measurement
records stored in the output array.
The valid values are 1 to 35. This
value determines the number of
output registers used by the
function.
Element Configuration
This element is configured using the FLOW Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
TelePACE Ladder Logic Function Reference
February 19, 2007
56
The K Factor is a floating-point value. It may be any non-zero, positive value.
The Input Register is the address of the register that holds the input pulse count. Valid values are
any input or holding register in the range 30001 to 49999.
The Input Type may be one of the following.
16 bit counter A free running 16-bit counter.
Holding register (4xxxx) = 0
32 bit counter A free running 32-bit counter with low word in the first register.
Holding register (4xxxx) = 1
16 bit difference
The 16-bit difference between any two counters.
Holding Register (4xxxx) = 2
The Rate Period determines the units of time used to display the flow rate. It may be one of the
following. Note that this value does not affect when the rate calculation is performed.
per second
Holding register (4xxxx) = 0
per minute
Holding register (4xxxx) = 1
per hour
Holding register (4xxxx) = 2
per day
Holding Resister (4xxxx) = 3
Output Registers
The output registers store the results of the flow accumulation and act as internal workspace for the
accumulation.
The status register indicates the status of the flow accumulation. It can have the following values. If
the status register is non-zero, the error output is turned ON.
Status Register Value
0
1
2
3
4
5
Description
no error
invalid K factor configuration
invalid Input Register configuration
invalid Input Type configuration
invalid Rate Period configuration
pulse rate is too low for accurate flow rate calculation
The flow rate register contains the flow rate in engineering units based on the K-factor and rate
period provided.
TelePACE Ladder Logic Function Reference
February 19, 2007
57
The eight internal registers are used for the accumulation of the flow and calculation of the flow
rate.
The Number of Records register indicates how many sets of flow and time registers follow. This
value is equal to the Records variable. There are four registers in each record.
The Volume for Period n is stored as a floating-point number in two consecutive registers.
The End Time for Period n is stored as a 32-bit integer in two consecutive registers. The registers
hold the number of seconds since January 1, 1970. This is an unsigned number.
The Flow Time for Period n is stored as a 32-bit integer in two consecutive registers. The register
holds the number of seconds flow was accumulated in the period. This measures the time the
Accumulate input is ON, including times when the flow was zero.
Notes
The maximum pulse rate is 10 kHz.
The accumulated flow is calculated by measuring the accumulated pulses and dividing by the K
factor. The K factor cannot be changed while an accumulation is in progress. Only change the K
factor while accumulation is stopped.
Example
n e tw o rk 1 :
40001
40100
10009
FLO W
+31
The FLOW function in network 1 has the accumulate flow and enable accumulation inputs
connected to the left power rail. When these inputs are continuously powered the FLOW function
accumulates volume and calculates flow rate.
Each time contact 10009 is closed, powering the log data input, the accumulated volume, flow time
and the time at the end of the period is saved in the history registers.
The records value is set to 31. This means that 31 sets of history registers, volume, flow time and
end of period time, will be logged. In this example the accumulation input is never turned off
meaning that once 31 sets of history registers are saved the next time contact 10009 is closed the 31st
record is removed and the newest record is added to the history.
TelePACE Ladder Logic Function Reference
February 19, 2007
58
2.25
FTOS - Floating-Point to Signed Integer
Description
The FTOS element converts a floating-point register or constant into a signed integer and stores the
result in a holding register.
When the enable input is ON, value is converted into a signed number and stored in the result
register. The value is rounded to the nearest integer. If the value is less than –32768, then –32768 is
stored. If the value is greater than 32767, then 32767 is stored.
The top output is ON when the input is. The bottom output is ON if the floating-point value is less
than –32768 or greater than 32767.
ON = enable
value
copies status of input
FTOS
result
ON = result out of range
Function Variables
The element has two parameters.
Variable
value
Result
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
holding register (4xxxx)
Description
a floating-point register or constant
Converted signed value
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number.
Floating point numbers can represent positive or negative values in the range –3.402 × 1038 to 3.402
× 1038.
Related Functions
UTOF - Unsigned Integer to Floating-Point
STOF - Signed Integer to Floating-Point
FTOU - Floating-Point to Unsigned Integer
TelePACE Ladder Logic Function Reference
February 19, 2007
59
Example
network 1:
-223.51
FTOS
42102
The FTOS function in network 1 converts floating-point constant –223.51 to a signed integer value
and puts the value into register 42102. In this example the content of register 42102 is the signed
integer –224.
TelePACE Ladder Logic Function Reference
February 19, 2007
60
2.26
FTOU - Floating-Point to Unsigned Integer
Description
The FTOU element converts a floating-point register or constant into an unsigned integer and stores
the result in a holding register.
When the enable input is ON, value is converted into an unsigned number and stored in the result
register. The value is rounded to the nearest integer. If the value is less than zero, then zero is stored.
If the value is greater than 65535, then 65535 is stored.
The top output is ON when the input is. The bottom output is ON if the floating-point value is less
than 0 or greater than 65535.
ON = enable
value
copies status of input
FTOU
result
ON = result out of range
Function Variables
The element has two parameters.
Variable
value
Result
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
holding register (4xxxx)
Description
a floating-point register or constant
Converted unsigned value
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number.
Floating point numbers can represent positive or negative values in the range –3.402 × 1038 to 3.402
× 1038.
Related Functions
UTOF - Unsigned Integer to Floating-Point
STOF - Signed Integer to Floating-Point
FTOS - Floating-Point to Signed Integer
TelePACE Ladder Logic Function Reference
February 19, 2007
61
Example
network 1:
+437.501
FTOU
42101
The FTOU function in network 1 converts floating-point constant +437.501 to an unsigned integer
value and puts the value into register 42101. In this example the content of register 42101 is the
unsigned integer +438.
TelePACE Ladder Logic Function Reference
February 19, 2007
62
2.27
GETB – Get Bit from Block
Description
The GETB function block reads the status of a bit, at the bit index, from the source block of
registers.
When the bit index is defined as a holding register the enable GETB input must be ON to increment
bit index or reset bit index to zero.
The increment bit index input increments the bit index once, each scan, when enabled.
The reset bit index to 0 input resets the bit index to 0 when enabled.
When the bit index is defined as a constant, the GETB function checks the status of the bit at the bit
index when enable GETB is ON. The increment bit index and reset bit index to 0 inputs have no
effect on the function block in this condition.
When the enable GETB is ON, the state of bit selected output is ON if the source bit is 1 and OFF
if the source bit is 0.
The index>size output is enabled when the bit index is equal to size + 1 and the enable GETB input
is ON. The reset bit index to 0 input must be set to continue function operation.
ON = enable GETB
bit index
copies state of input 1
ON = increment bit index
source
state of the bit selected
ON = reset bit index to 0
GETB
size
ON if index > size
Function Variables
Variable
bit index
Valid Types
Constant (0..65535)
holding register (4xxxx)
Source
coil block (0xxxx)
holding register (4xxxx)
Size
Constant (1..100)
Description
The index of the bit within the source block. A
bit index of 0 is the most significant bit of the
first register of the source block.
The address of the source register.
The address for a coil register block is the first
register in a group of 16 registers.
number of 16 bit words in the block.
Notes
The Get bit from block function accesses 16 bit words. Coil blocks are groups of 16 registers that
start with the register specified as the block address. Coil blocks must begin at the start of a 16 bit
word within the controller memory. Suitable addresses are 00001, 00017, 00033, etc.
Related Functions
PUTB – Put Bit into Block
TelePACE Ladder Logic Function Reference
February 19, 2007
63
ROTB – Rotate Bits in Block
CMPB – Compare Bit
Example
10010
+2
40223
(
)
00017
GETB
+1
In this example the GETB function is used to test bit 13 of the PID block 0 Status register to check if
the Control Block is in manual mode.
The twenty-five holding registers used for PID block 0 are assigned to the CNFG PID Control
Block I/O Module in the Register Assignment. In this case holding registers 40220 through 40245
are assigned to the I/O module.
The Control Block status register, 40223 is tested to see if bit 13 is ON. The GETB function uses bit
index of 0 for the most significant bit. This means that a bit index of 2 will test for bit 13 of the
Control Block register.
Closing contacts 10010 sets the enable GETB input on. If PID block 0 is in manual mode output
00017 will turn ON.
TelePACE Ladder Logic Function Reference
February 19, 2007
64
2.28
GETL - Data Logger Extract
Description
The GETL function extracts one record from a data log and writes it into holding registers.
When a low to high transition occurs on the enable GETL input, the error code and sequence
number status registers are updated and the data length is cleared.
When the enable GETL input is ON and a low to high transition occurs on the read data input, the
status registers are updated and the data for the requested sequence number is copied to the data from
log holding registers.
The error output is ON if the log is not configured or if there was a data reading error, see table
below. The outputs are powered only when the enable input is powered.
ON = enable GETL
request
OFF to ON = read data
status
copies state of input 1
ON = error
GETL
LogID
Function Variables
Variable
Request
Valid Types
2 holding registers
(4xxxx)
Status
Up to 36 holding registers
(4xxxx)
LogID
Constant (1 to 16)
Description
Unsigned long sequence number requested
from the log.
+0 = least significant word
+1 = most significant word
Status and data registers
+0 = error code
+1,2 = sequence number
+3 = length of data
+4 to+35 = data from log
Identifies the internal log.
Status Register
The status register stores the result of an enable log attempt and a log data attempt. It can have the
following values. If the status register is does not contain the code 20 then the error output is turned
on. The status error codes are:
Error Code
20
21
22
23
Description
The configuration is valid and data can be retrieved.
The log ID is invalid.
The log is not configured.
The requested sequence number was not in the valid range.
TelePACE Ladder Logic Function Reference
February 19, 2007
65
Notes:
To get the oldest sequence number in the log toggle the enable GETL input, the error code and
sequence number status registers are updated and the data length is cleared. To clear the error 23 the
enable GETL input must be turned off.
Related Functions:
DLOG - Data Logger
TelePACE Ladder Logic Function Reference
February 19, 2007
66
2.29
GTEF – Floating-Point Greater Than or Equal
Description
The GTEF element tests if a floating-point register or constant is greater than or equal to another
floating-point register or constant.
When the enable input is ON, value1 and value2 are compared. If value1 is greater than value2, the
top output is ON. If value1 is equal to value2 the bottom output is ON.
ON = enable
value1
ON if value1 > value2
GTEF
value2
ON if value1 = value2
Function Variables
The element has two parameters.
Variable
Value1
Value2
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
Description
a floating-point register or constant
a floating-point register or constant
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number. Floating point numbers can represent positive and negative values in the range –
3.402 × 1038 to 3.402 × 1038.
Related Functions
CMP – Compare Signed Values
CMPU – Compare Unsigned Values
Example
network 1:
+22.601
GTEF
40001
TelePACE Ladder Logic Function Reference
February 19, 2007
67
The GTEF function in network 1 compares the floating-point constant +22.601 to the contents of
floating-point register 40001. The top output of the GTEF function is ON if the value of register
40001 is less than +22.601. The bottom output of the GTEF is ON if the value of register 40001 is
equal to +22.601.
TelePACE Ladder Logic Function Reference
February 19, 2007
68
2.30
HART – Send HART Command
Description
The HART element sends a HART protocol command and processes the response. The SCADAPack
100 or SCADASense Series controllers do not support this command.
The HART element is a two-cell element, with one input and two outputs. When the enable HART
input changes from OFF to ON, the element sends the HART command to the HART device. When
the enable HART input changes from ON to OFF, the current command is aborted and no response
is processed.
When a response is received, the data in the response is stored in the I/O database and the command
complete output turns ON. If there is an error in the command, or if the HART device fails to
respond to any of the attempts, the command error output turns ON.
The enable HART input must remain ON until the response has been received or an error has
occurred. All outputs turn OFF when the input is OFF.
ON = enable HART
command
HART
ON = command complete
ON = command error
status
Function Variables
The HART element has two parameters:
Variable
command
Valid Types
Holding register
(4xxxx)
status
Holding register
(4xxxx)
Description
Address of the first register in the HART
command block. There are 5 registers in the
block at addresses command+0 to
command+4.
+0 = 5904 HART interface module number
+1 = HART device address
+2 = command number
+3 = command data register address
+4 = response register address
Address of the first register of the status
block. There are two registers in the block at
addresses status+0 and status+1.
+0 = command status
+1 = additional information code
The 5904 HART interface module number must be set to 0, 1, 2 or 3. This must correspond with
the module number of a CNFG 5904 HART Interface module in the Register Assignment.
The HART device address must be in the range 0 to 15.
Valid values for command number are shown below.
TelePACE Ladder Logic Function Reference
February 19, 2007
69
The command data register address specifies an I/O database register where the data for the
command is stored. The program must set the values in these registers. The tables below show how
this address is used.
The response register address specifies an I/O database register where the data in the response is
stored. The tables below show how this address is used. Registers marked as (float) contain floatingpoint values.
Command
Purpose
Command Data
Registers
Response
Registers
Notes
0
Read the device identifier
Not used
+0 = manufacturer ID
+1 = manufacturer Device Type
+2 = preambles Requested
+3 = command Revision
+4 = transmitter Revision
+5 = software Revision
+6 = hardware Revision
+7 = flags
+8,9 = device ID (double)
This command is also the link initialization command. The
HART element performs link initialization automatically.
The user does not have to send this command unless the
device identifier is needed.
Command
Purpose
Command Data
Registers
Response
Registers
1
Read primary variable (PV)
Not used
Command
Purpose
Command Data
Registers
Response
Registers
2
Read primary variable current and percent of span
Not used
+0,1 = PV (float)
+2 = PV units code
+0,1 = PV current (float)
+2 = PV current units code
+3,4 = PV percent (float)
+5 = PV percent units code
TelePACE Ladder Logic Function Reference
February 19, 2007
70
Command
Purpose
Command Data
Registers
Response
Registers
Notes
Command
Purpose
Command Data
Registers
Response
Registers
3
Read dynamic variables and primary variable current
Not used
+0,1 = primary variable current (float)
+2 = primary variable current units code
+3,4 = primary variable value (float)
+5 = primary variable units code
+6,7 = secondary variable value (float)
+8 = secondary variable units code
+9,10 = tertiary variable value (float)
+11 = tertiary variable units code
+12,13 = fourth variable value (float)
+14 = fourth variable units code
Not all devices return primary, secondary, tertiary and
fourth variables. If the device does not support them, zero
is written into the value and units code for that variable.
33
Read specified transmitter variables
+0 = variable code 0
+1 = variable code 1
+2 = variable code 2
+3 = variable code 3
+0,1 = variable 0 value (float)
+2 = variable 0 units code
+3,4 = variable 1 value (float)
+5 = variable 1 units code
+6,7 = variable 2 value (float)
+8 = variable 2 units code
+9,10 = variable 3 value (float)
+11 = variable 3 units code
The status registers contains the current command status and additional code returned from the
HART interface. The table below shows the values.
status
0
1
2
3
Description
HART interface
module is not
communicating
Command ready to
send to device
Command sent to
device
Response received
TelePACE Ladder Logic Function Reference
February 19, 2007
Code
not used
not used
current attempt number
response code from HART device (see
Notes)
71
status
4
Description
No valid response
received after all
attempts made
5
HART interface is not
ready to transmit
Code
0=no response from HART device.
Other = error response code from HART
device (see Notes)
not used
Element Configuration
This element is configured using the HART Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
WARNING:
If the controller is initialized (using the TelePACE Initialize command), all I/O
database registers used for element configuration are set to zero. The Ladder Logic
program must be re-loaded to the controller to restore the element configuration.
Addresses shows the register addresses that will be used by the element.
Module number selects the HART interface module to which the command will be sent. The valid
range is 0 to 3.
Device Address selects the address of the HART device. The valid range is 0 to 15.
Command selects the HART command to be sent to the device. The valid values are:
Read Device Identifier = 0
Read PV = 1
Read PV Current and % = 2
Read Dynamic Variables = 3
Read Specified Variables = 33
Data Register Address selects the resisters where data for the command is stored. This field is
grayed for the Read Device Identifier, Read PV, Read PV Current and %, and Read Dynamic
Variables commands. These commands do not have any data.
Response Register Address selects the registers where the data in the response from the command
will be stored.
TelePACE Ladder Logic Function Reference
February 19, 2007
72
Notes
The HART element performs link initialization automatically. The user does not have to send the
link initialization command. If the command fails after all attempts, the link is automatically
reinitialized by the HART element, at the time of the next command.
Some variables read from HART devices are 32-bit floating-point values. Each floating-point value
is stored in two consecutive database registers. The most significant 16 bits of the value is stored in
the lower numbered register. The least significant 16 bit of the value is stored in the higher numbered
register.
The variable codes specify which variables are read from the HART device. See the documentation
for your HART device for valid values for the variable codes.
The unit codes are standardized for all HART devices. See the HART specification or the
documentation for your HART device for valid values.
The response code from the HART device contains communication error and status information. The
information varies by device, but there are some common values.
If bit 7 of the high byte is set, the high byte contains a communication error summary. This field is
bit-mapped. The following table shows the meaning of each bit as defined by the HART protocol
specifications. Consult the documentation for the HART device for more information.
Bit
6
5
4
3
2
1
0
Description
vertical parity error
overrun error
framing error
longitudinal parity error
reserved – always 0
buffer overflow
Undefined
If bit 7 of the high byte is cleared, the high byte contains a command response summary. The
following table shows common values. Other values may be defined for specific commands. Consult
the documentation for the HART device.
Code
32
64
Description
Busy – the device is performing a function that
cannot be interrupted by this command
Command not Implemented – the command is not
defined for this device.
The low byte contains the field device status. This field is bit-mapped. The following table shows the
meaning of each bit as defined by the HART protocol specifications. Consult the documentation for
the HART device for more information.
Bit
7
6
5
Description
field device malfunction
Configuration changed
cold start
TelePACE Ladder Logic Function Reference
February 19, 2007
73
Bit
4
3
2
1
0
Description
more status available (use command 48 to
read)
primary variable analog output fixed
primary variable analog output saturated
non-primary variable out of limits
primary variable out of limits
Example
An example of polling using the HART block is in the file HART.LAD. This file is automatically
installed on the computer when the TelePACE program is installed. It is located in the
TELEPACE\EXAMPLES directory.
See Also
MSTR - Master Message
TelePACE Ladder Logic Function Reference
February 19, 2007
74
2.31
INIM – Initialize Dial-Up Modem
Description
The INIM function initializes an internal modem or an external modem, typically to set it to receive
calls. Only one INIM block may be active on each serial communication port at any one time.
When enable INIM input is ON, the INIM element sends the modem initialization string to the
modem. When the initialization is complete the ON when initialization is complete output is turned
ON. If an error occurs, the ON when initialization failed output is turned ON.
The enable INIM input must be energized for the entire INIM time, including multiple initialization
attempts.
Note: The SCADAPack 100 does not support dial up connections on com port 1.
SCADASense Series controllers do not support dial connections on any serial port.
ON = enable INIM
config
ON when initialization is
complete
INIM
status
ON when initialization failed
Function Variables
Variable
Config
Status
Valid Types
holding register
(4xxxx)
Holding register
(4xxxx)
Description
Address of the first register in the
configuration block. There are 18
registers in the block at addresses
configuration+0 to configuration+17.
+0 = Communication port
+1 = Length of modem string
+2 = Modem initialization string
Registers should be programmed using
the Element Configuration command.
Address of the first register in the status
block. There are 2 registers in the block at
addresses status+0 to status+1.
+0 = error code
+1 = reservation identifier
Notes
The modem initialization string is packed. Two ASCII characters are stored in each register.
The reservation identifier is required for the operation of the dialer but can be ignored by the ladder
program.
TelePACE Ladder Logic Function Reference
February 19, 2007
75
Element Configuration
This element is configured using the INIM Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
Error Code
0
1
2
3
6
9
Description
No Error
Bad configuration error occurs when an incorrect initialization string is sent
to the modem. This usually means the modem does not understand a
specific command in the initialization string.
No modem is connected to the controller serial port, or the controller serial
port is not set to RS232 Modem.
Initialization error occurs when the modem does not respond to the
initialization string and may be turned off.
Call aborted by the program. This will occur if the enable INIM input goes
OFF before a modem connection occurs.
“Serial port is not available” error occurs when the INIM function attempts
to use the serial port when another ladder communication element, C
program or an incoming call has control of the port.
To optimize performance, minimize the length of messages on com3 and com4. Examples of
recommended uses for com3 and com4 are for local operator display terminals, and for programming
and diagnostics using the TelePACE program.
Related Functions
DIAL – Control Dial-Up Modem
Example
The following network configures a generic Hayes compatible modem to answer on the second ring.
The modem is initialized when the controller is powered up.
TelePACE Ladder Logic Function Reference
February 19, 2007
76
Network 1: Initialize Modem on Power Up
Power-Up
01025
Init_MOD
01028
Config
44000
Complete
01026
INIM
Status
44018
Power-Up
01025
Failed
01027
Complete
01026
Failed
01027
Init_MOD
01028
Init_MOD
01028
TelePACE Ladder Logic Function Reference
February 19, 2007
77
2.32
L–>L – List to List Transfer
Description
The L–>L function transfers the contents of one register from the source list of registers into one
register from the destination list of registers, at the position of the index. The index register points to
the same position in both the source and the destination list of registers.
When the enable transfer input is ON, and the index equals size output is not ON, the source list
register is transferred to the destination list register at the position of the index in both lists.
The freeze/increment index input allows control of the index. If this input is ON the index is not
incremented. If the input is OFF the index is incremented by one after each transfer.
When the reset index input is ON the index is reset to zero.
The index is incremented by one on each transfer until the index equals size. When the index equals
size output is ON no further increments in index value occur until the index is reset.
ON = enable transfer
ON = freeze index
OFF = increment index
ON = reset index to 0
source
index and
destination
copies state of
enable transfer input
ON if index equals size
and enable transfer = ON
L->L
size
Function Variables
Variable
source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Index and
destination
holding register (4xxxx)
Size
constant (1..9999)
Description
The address of the source register
list.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
copied.
The address of the index register
and the destination register list. The
index is stored in register [4xxxx].
The data is stored in register
[4xxxx+1] to register [4xxxx+size]
The number of registers in the
source and destination lists.
Related Functions
L–>R – List to Register Transfer
R–>L – Register to List Transfer
MOVE – Move Block
TelePACE Ladder Logic Function Reference
February 19, 2007
78
Example
E n ab le
T ran s fer
04082
30001
42011
L -> L
R es et
+3
T ran s fer
04081
The List to List function transfers the contents of one register in the source list of registers into one
register of the destination list of registers, at the position of the index. The index register points to
the same position in the source and destination lists.
Sourc
e List
list register 0->
list register 1->
list register 2->
list register 3->
Destinati
on List
30001
List Index---->
list register 0-->
42011
42012
30002
list register 1-->
42013
30003
list register 2-->
42014
30004
list register 3-->
42015
In this example the source register list starts at input register 30001. The index is holding register
42011 and the destination register list starts at holding register 42012. The source register list
contains the first four analog input registers. The index is a general purpose analog output register
that will have a value of 0, 1, 2 or 3. The destination register list starts at the next sequential register
after the index register. The destination list contains four general purpose analog output registers and
has a size of four.
When list index register 42011 has a value of 0 and the L->L function is enabled the contents of
source list register 30001 is transferred to destination list register 40012.
When list index register 42011 has a value of 1 and the L->L function is enabled the contents of
source list register 30002 is transferred to destination list register 42013.
When list index register 42011 has a value of 2 and the L->L function is enabled the contents of
source list register 30003 is transferred to destination list register 42014.
When list index register 42011 has a value of 3 and the L->L function is enabled the contents of
source list register 30004 is transferred to destination register 42015.
TelePACE Ladder Logic Function Reference
February 19, 2007
79
2.33
L–>R – List to Register Transfer
Description
The L->R function transfers the contents of a register indicated by the index from the source list of
registers into the destination register.
When the enable transfer input is ON, and the index equals size output is OFF, the source list
register pointed to by the index is transferred to the destination register.
The freeze/increment index input allows control of the index. If this input is ON the index is not
incremented. If the input is OFF the index is incremented by one after each transfer.
When the reset index input is ON the index is reset to zero.
The index is incremented by one on each transfer until the index equals size. When the index equals
size output is ON no further increments in the index value occur until the index is reset.
ON = enable transfer
source
ON = freeze index
OFF = increment index
index and
destination
ON = reset index to 0
L->R
size
copies state of input 1
ON if index equals size
and enable transfer = ON
Function Variables
Variable
Source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Index and
destination
holding register (4xxxx)
Size
constant (1..9999)
Description
The address of the source register
list.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
read.
The address of the index register
and the destination register. The
index to the source list is stored in
holding register [4xxxx]. The
destination register is holding
register [4xxxx+1].
The number of registers in the
source list.
Related Functions
R–>L – Register to List Transfer
L–>L – List to List Transfer
MOVE – Move Block
TelePACE Ladder Logic Function Reference
February 19, 2007
80
Example
03202
30001
42009
L -> R
03201
+3
The List to Register function transfers the contents of a register indicated by the index from the
source list of registers into the destination register.
Source
Register
List
list register 0-->
list register 1-->
30001
30002
list register 2-->
30003
list register 3-->
30004
List Index---->
Destination
Register->
4200
9
4201
0
An example of the registers used in a List to Register ( L->R) transfer is shown in the above
diagram. The source register list contains the first four analog input registers and has a size of four.
The index is a general purpose analog output register that will have a value of 0, 1, 2 or 3. The
destination register is a general purpose analog output register that is the next sequential register after
the index register.
When list index register 42009 has a value of 0 and the L->R function is enabled, the contents of
source register 30001 is transferred to destination register 42010.
When list index register 42009 has a value of 1 and the L->R function is enabled, the contents of
source register 30002 is transferred to destination register 42010.
When list index register 42009 has a value of 2 and the L->R function is enabled, the contents of
source register 30003 is transferred to destination register 42010.
When list index register 42009 has a value of 3 and the L->R function is enabled, the contents of
source register 30004 is transferred to destination register 42010.
TelePACE Ladder Logic Function Reference
February 19, 2007
81
2.34
LTEF - Floating-Point Less Than or Equal
Description
The LTEF element tests if a floating-point register or constant is less than or equal to another
floating-point register or constant.
When the enable input is ON, value1 and value2 are compared. If value1 is less than value2, the top
output is ON. If value1 is equal to value2 the bottom output is ON.
ON = enable
value1
ON if value1 < value2
LTEF
value2
ON if value1 = value2
Function Variables
The element has two parameters.
Variable
value1
Value2
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
Description
a floating-point register or constant
a floating-point register or constant
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number. Floating point numbers can represent positive and negative values in the range –
3.402 × 1038 to 3.402 × 1038.
Related Functions
CMP – Compare Signed Values
CMPU – Compare Unsigned Values
Example
network 1:
+19.21
LTEF
40101
TelePACE Ladder Logic Function Reference
February 19, 2007
82
The LTEF function in network 1 compares the floating-point constant +19.21 to the contents of
floating-point register 40101. The top output of the LTEF function is ON if the value of register
40101 is greater than +19.21. The bottom output of the LTEF is ON if the value of register 40001 is
equal to +19.21.
TelePACE Ladder Logic Function Reference
February 19, 2007
83
2.35
MOD – Modulus of Signed Values
Description
The MOD function divides two registers or a constant, value 1, by a register or constant, value 2,
and stores the modulus (remainder) in a holding register, result. Signed division is used. The value
1, value 2 and result are signed numbers.
The out of range output is enabled if the result is greater than 32767 or less than -32768. The divide
by zero output is enabled if value 2 equals 0.
ON = enable MOD
value 1
copies status of input 1
value 2
ON = result out of range
MOD
result
ON = divide by zero
Function Variables
Variable
Value 1
Value 2
Result
Valid Types
constant
(-32768..32767)
2 Input registers (3xxxx)
2 holding registers (4xxxx)
constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
Signed value to divide.
The low order word is stored in the
first register if registers are used.
Signed value to divide by
Result = value 1 modulo value 2
Related Functions
MODU – Modulus of Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
84
Example
n e tw o rk 1 :
45556
45553
MOD
45554
The MOD function in network 1 divides value 1, double word registers 45556 and 45557 by value
2, register 45553. The modulus of this division is stored in register 45554. The table below shows
some examples of different values for the registers in the MOD function.
example 1
example 2
example 3
Example 4
Value of Register
45556
5689
-32600
-22765
19823
TelePACE Ladder Logic Function Reference
February 19, 2007
Value of Register
45553
77
-234
7659
-7692
Modulus Register
45554
68
-74
-7447
4439
85
2.36
MODU – Modulus of Unsigned Values
Description
The MODU function divides two registers or a constant, value 1, by a register or constant, value 2,
and stores the modulus (remainder) in a holding register, result. Unsigned division is used. The
value 1, value 2 and result are unsigned numbers.
The out of range output is enabled if the result is greater than 65535 or less than 0. The divide by
zero output is enabled if value 2 equals 0.
ON = enable MODU
value 1
copies status of input 1
value 2
ON = result out of range
MODU
result
ON = divide by zero
Function Variables
Variable
Value 1
Value 2
Result
Valid Types
constant (0..65535)
2 Input registers (3xxxx)
2 holding registers (4xxxx)
constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
Unsigned value to divide.
The low order word is stored in the
first register if registers are used.
unsigned value to divide by
result = value 1 modulo value 2
Related Functions
MOD – Modulus of Signed Values
TelePACE Ladder Logic Function Reference
February 19, 2007
86
Example
n e tw o rk 1 :
41300
46444
MODU
41306
The MODU function in network 1 divides value 1, double word registers 41300 and 41301 by value
2, register 46444. The modulus of this division is stored in register 41306. The table below shows
some examples of different values for the registers in the MOD function.
Example 1
Example 2
Example 3
Example 4
Value of Register
45556
26744
56398
37697
33005
TelePACE Ladder Logic Function Reference
February 19, 2007
Value of Register
45553
320
34022
2366
1100
Modulus Register
45554
184
20878
2207
5
87
2.37
MOVE – Move Block
Description
The MOVE function block copies the source block of registers into the destination block of coil, or
holding, registers.
ON = move block
source
copies status of input 1
destination
MOVE
size
Function Variables
Variable
Source
Destination
Size
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
coil block (0xxxx)
holding register (4xxxx)
constant (1..100)
Description
The first register in the source block.
The address for a coil or status register
block is the first register in a group of 16
registers that will be copied.
The first register in the destination block.
The address for a coil register block is the
first register in a group of 16 registers into
which data will be copied.
The number of 16 bit words in the block.
Block move copies 16 bit words. Coil and status register blocks are groups of 16 registers that start
with the register specified as the block address. A block size of 2 corresponds to 32 coils, or two
holding registers.
Coil and status register blocks must begin at the start of a 16 bit word within the controller memory.
Suitable addresses are 00001, 00017, 10001, 10033, etc.
Related Functions
Error! Not a valid link.
L–>L – List to List Transfer
L–>R – List to Register Transfer
TelePACE Ladder Logic Function Reference
February 19, 2007
88
Example
n etw ork 1 :
30001
40001
MOVE
+4
In the above figure the source register entered is 30001 (3reg) and the destination register entered is
40001 (4reg) and the block size entered is 4.
When this MOVE block is enabled:
the contents of register 30001 are copied to register 40001
the contents of register 30002 are copied to register 40002
the contents of register 30003 are copied to register 40003
the contents of register 30004 are copied to register 40004
TelePACE Ladder Logic Function Reference
February 19, 2007
89
2.38
MSTR – Master Message
Description
The MSTR function exchanges data with another controller using either the Modbus or the DF1
communication protocols.
Note
Only one MSTR block may be active on each serial communication port at any one time.
When the enable MSTR goes from OFF to ON the MSTR function will send one master message to
the slave address. The enable MSTR must go from OFF to ON to send another MSTR message. The
message complete output will be energized if the MSTR receives a valid response from the slave
station. The message format or communication error is energized if an error occurs. See the status
code table below for a list of possible errors.
message
ON = enable MSTR
MSTR
timer
message complete
ON = message format or
communication error
Function Variables
Variable
Message
Valid Types
holding register (4xxxx)
Timer
holding register (4xxxx)
Description
Address of the first register in the
message control block. There are 7
registers in the block at addresses
message+0 to message+6.
+0 = port
+1 = function code
+2 = slave controller address
+3 = slave register address
+4 = master register address
+5 = length
+6 = time-out in 0.1s increments
timer accumulator register
Notes
To optimize performance, minimize the length of messages on com3 and com4. Examples of
recommended uses for com3 and com4 are for local operator display terminals, and for programming
and diagnostics using the TelePACE program.
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
TelePACE Ladder Logic Function Reference
February 19, 2007
90
Using MSTR with Modbus Protocol
This element is configured using the MSTR Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
Valid Function Codes are shown below. Functions 05, 06, 15, and 16 support broadcast messages.
Functions 129, 130, 132, 133, 135, 136, 138, and 139 may be broadcast, but some Enron Modbus
slave devices may not support broadcast messages. See the TeleBUS Protocols Modbus Compatible
Protocols User Manual for details on each function code.
Function
01
Description
Read Coil Status
02
Read Input Status
03
Read Holding Register
04
Read Input Register
05
Write Single Coil
06
Write Single Register
15
Write Multiple Coils
16
Write Multiple Registers
128
Read Enron Boolean
129
Write Enron Single
Boolean
TelePACE Ladder Logic Function Reference
February 19, 2007
Purpose
Read digital output
registers.
Read digital input
registers.
Read analog output
registers.
Read analog input
registers.
Write digital output
register.
Write analog output
registers.
Write digital output
registers.
Write analog output
registers.
Read Enron Boolean
registers
Write Enron Boolean
register
Maximum Registers
2000
2000
125
125
1
1
880
60
2000
1
91
Function
130
137
Description
Write Enron Multiple
Booleans
Read Enron Short
Integers
Write Enron Single Short
Integer
Write Enron Multiple
Short Integers
Read Enron Long
Integers
Write Enron Single Long
Integer
Write Enron Multiple
Long Integers
Read Enron Floats
138
Write Enron Single Float
139
Write Enron Multiple
Floats
131
132
133
134
135
136
Purpose
Write Enron Boolean
registers
Read Enron short
integer register
Write Enron short integer
register
Write Enron short integer
registers
Read Enron long integer
register
Write Enron long integer
register
Write Enron long integer
registers
Read Enron floatingpoint register
Write Enron floatingpoint register
Write Enron floatingpoint registers
Maximum Registers
880
125
1
60
62
1
30
62
1
30
The port must be set to 1, 2, 3 or 4 corresponding to the com1, com2, com3 and com4 serial ports.
The slave controller address edit-box sets the station number of the controller. For the Modbus
ASCII and Modbus RTU protocols, the valid range is 0 to 255 if standard addressing is used, and 0
to 65534 if extended addressing is used. Address 0 is reserved for broadcast messages.
The slave register address specifies the first register where data will be read from or written to in
the slave controller. The following table shows the valid slave register addresses for each command.
Function Code
Slave Register
Length
Read Coil Status
Read Input Status
Read Holding Register
Read Input Register
Write Single Coil
Write Single Register
Write Multiple Coils
Write Multiple Registers
Read Enron Boolean
Write Enron Boolean
Write Enron Multiple Boolean
Read Enron Short Integer
Write Enron Short Integer
Write Enron Multiple Short Integer
Read Enron Long Integer
Write Enron Long Integer
Write Enron Multiple Long Integer
Address
00001 to 09999
10001 to 19999
40001 to 49999
30001 to 39999
00001 to 09999
40001 to 49999
00001 to 09999
40001 to 49999
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
2000
2000
125
125
1
1
880
60
2000
1
880
125
1
60
62
1
30
TelePACE Ladder Logic Function Reference
February 19, 2007
92
Function Code
Slave Register
Length
Read Enron Floating Point
Write Enron Floating Point
Write Enron Multiple Floating Point
Address
0 to 65535
0 to 65535
0 to 65535
62
1
30
The master register address specifies the first register where data will be written to or read from in
this controller. The register type does not have to match the type of the slave register address. It is
possible to store input registers from a slave into output registers on the master and vice-versa.
The length parameter specifies how many registers are to be transferred. The maximum length for
each function code is shown in the above table. Functions 05 and 06 always transfer 1 register,
regardless of the value of length.
The time-out is in 0.1s increments. The error output is energized if the time-out period ends without
a valid response to the message.
When an error occurs, an error status code is stored in the master command status register in the
analog input database. There is one status register for each port.
The module DIAG Serial port protocol status must be added to the register assignment to monitor
the master command status register for the desired serial port. The status codes are shown in the
following table.
Status Code
0
1
3
4
5
6
7
12
24
25
26
27
28
29
30
Description
Message sent - waiting for response
Response received (no error occurred)
bad value in function code register
bad value in slave controller address register
bad value in slave register address register
bad value in length register
serial port or protocol is invalid
response timeout
exception response: invalid function code
exception response: invalid address
exception response: invalid value
protocol is invalid or serial port queue is full
slave and master stations are equal; they must be different
exception response: slave device failure
exception response: slave device busy
Example
An example of polling using the MSTR block is in the file MSTR.LAD. This file is automatically
installed on the computer when the TelePACE program is installed. It is located in the
TELEPACE\EXAMPLES directory.
TelePACE Ladder Logic Function Reference
February 19, 2007
93
Using MSTR with DF1 Protocol
This element is configured using the MSTR Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
DF1
DF1 Address
DF1 Address
The Port must be set to 1, 2, 3 or 4 corresponding to the com1, com2, com3 and com4 serial ports.
Valid Function Codes are:
Function
00
Description
Protected Write
01
Unprotected Read
02
Protected Bit Write
05
Unprotected Bit Write
08
Unprotected Write
Purpose
Writes words of data to
limited areas of the
database.
Reads words of data from
any area of the database.
Sets or resets individual
bits within limited areas of
the database.
Sets or resets individual
bits in any area of the
database.
Writes words of data to any
area of the database.
Maximum Registers
121
122
1
1
121
The Slave RTU Address must be in the range 0 to 254.
The Slave Register Address specifies the first DF1 physical 16-bit address where data will be read
from or written to in the slave controller.
The Master Register Address specifies the first physical 16-bit address where data will be written
to or read from in this controller. The register type does not have to match the type of the slave
register address. It is possible to store input registers from a slave into output registers on the master
and vice-versa.
TelePACE Ladder Logic Function Reference
February 19, 2007
94
The Length parameter specifies how many 16-bit registers are to be transferred for functions 00, 01
and 08. For function codes 02 and 05, this field is labeled Bit Mask. Bit Mask selects the 16-bit
bitmask specifying which bits in the Master Register to send. If a bit is set in Bit Mask, the
corresponding bit in the register will be sent.
The Time Out is in 0.1s increments. The error output is energized if the time-out period ends
without a valid response to the message. If the MSTR function is used to send a broadcast message,
the Slave RTU Address must be 255 and the Time Out can be set to 0 since there is no response to
wait for.
The module DIAG Serial port protocol status must be added to the register assignment to monitor
the master command status register for the desired serial port. The status codes are shown in the
following table.
Status Code
0
1
3
4
5
6
7
8
9
16
80
Other
Description
Message sent - waiting for response
Response received (no error occurred)
bad value in function code register
bad value in slave controller address register
bad value in slave register address register
bad value in length register
slave has no more responses to send.
Response received didn’t match command sent.
Specified protocol is not supported by this controller.
slave error - illegal command or format.
slave error - addressing problem or memory protect rungs.
error codes from other DF1 compatible controllers - Consult the
documentation for specific controller.
Notes
Details about the DF1 driver implementation on the SCADAPack controllers can be found in the
TeleBUS DF1 Protocol Booklet in this manual.
An example of polling using the MSTR block is in the file ab_mstr.lad. This file is automatically
installed on the computer when the TelePACE program is installed. It is located in the
TELEPACE\EXAMPLES directory.
TelePACE Ladder Logic Function Reference
February 19, 2007
95
2.39
MSIP – Master IP Message
Description
The MSIP function exchanges data with another controller using the Modbus IP communication
protocol. This function sends a master message to a remote IP address.
Note Unlike the MSTR function, multiple MSIP blocks may be active on the same
communication interface at the same time. The number of active MSIP blocks is limited only by the
number of available connections (typical capacity is 20 connections).
When the open input goes from OFF to ON the MSIP function opens an IP connection. Set the open
input to OFF to close the connection.
When the send message input goes from OFF to ON, and the open input is ON, the MSIP function
will send one Modbus IP master message to the slave address. The send message input must go from
OFF to ON to send another MTCP message. Each master message is complete when either output is
energized: The message complete output will be energized if the MSIP block receives a valid
response from the slave station. The message format or communication error is energized if an
error occurs. See the status code table below for a list of possible errors.
ON = send message
message
ON = open
MSIP
timer
message complete
ON = message format or
communication error
Function Variables
Variable
message
Valid Types
holding register (4xxxx)
Description
Address of the first register in the message
control block. There are 11 registers in the block
at addresses message+0 to message+11.
+0 = byte1 of slave IP address MSB, using format
byte1.byte2.byte3.byte4
+1 = byte2 of slave IP address
+2 = byte3 of slave IP address
+3 = byte4 of slave IP address LSB
+4 = protocol type
+5 = function code
+6 = slave controller address
+7 = slave register address
+8 = master register address
+9 = length
+10 = time-out in 0.1s increments
TelePACE Ladder Logic Function Reference
February 19, 2007
96
Variable
timer
Valid Types
holding register (4xxxx)
Description
Address of the first register in the timer control
block. There are 5 registers in the block at
addresses timer+0 and timer+4.
+0 = timer accumulator register
+1 = command status register
+2 = internal: connection ID
+3 = internal: closing state
+4 = internal: initialized
Sending a Message
Set the open input to ON to open an IP connection. This input may be set to ON at the same time as
the send message input in the next step.
If the maximum number of opened connections has been reached, an error occurs: The error output
is energized and the value of the command status register indicates the maximum number of
connections has been reached. Close the connection used by another MSIP function to correct the
error and repeat step 1.
Send one command message by toggling the send message input from OFF to ON.
The value of the command status register is 0 indicating that the message was sent.
Sending is complete when either the message complete output or error output is energized. The
message complete output is energized if the response is received successfully. The error output is
energized if there was a command error, timeout, or connection failure. The value of the command
status register is 1 for success or another value for error conditions.
Repeat steps 2 to 4 to send additional command messages.
Notes
The time-out register determines how long to wait for a response before closing the connection and
reporting an error. The connection is re-connected automatically when the next message is sent. The
open input does not need to be toggled to do this.
Leave the open input ON to keep the connection open for this MTCP function.
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
Element Configuration
This element is configured using the MSIP Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
TelePACE Ladder Logic Function Reference
February 19, 2007
97
The slave IP address has the format 255.255.255.255 where one register is used for each byte:
byte1.byte2.byte3.byte4
The protocol type must be one of the values shown below:
Protocol Type
1
2
3
Description
Modbus/TCP
Modbus RTU over UDP
Modbus ASCII over UDP
Valid Function Codes are shown below. Functions 05, 06, 15, and 16 support broadcast messages.
Functions 129, 130, 132, 133, 135, 136, 138, and 139 may be broadcast, but some Enron Modbus
slave devices may not support broadcast messages. See the TeleBUS Protocols Modbus Compatible
Protocols User Manual for details on each function code.
Function
01
Description
Read Coil Status
02
Read Input Status
03
Read Holding Register
04
Read Input Register
05
Write Single Coil
06
Write Single Register
15
Write Multiple Coils
16
Write Multiple Registers
TelePACE Ladder Logic Function Reference
February 19, 2007
Purpose
Read digital output
registers.
Read digital input
registers.
Read analog output
registers.
Read analog input
registers.
Write digital output
register.
Write analog output
registers.
Write digital output
registers.
Write analog output
registers.
Maximum Registers
2000
2000
125 note 1
125 note 1
1
1
880
60
98
Function
128
Description
Read Enron Booleans
129
137
Write Enron Single
Boolean
Write Enron Multiple
Booleans
Read Enron Short
Integers
Write Enron Single Short
Integer
Write Enron Multiple
Short Integers
Read Enron Long
Integers
Write Enron Single Long
Integer
Write Enron Multiple
Long Integers
Read Enron Floats
138
Write Enron Single Float
139
Write Enron Multiple
Floats
130
131
132
133
134
135
136
Purpose
Read Enron Boolean
registers
Write Enron Boolean
register
Write Enron Boolean
registers
Read Enron short
integer register
Write Enron short integer
register
Write Enron short integer
registers
Read Enron long integer
register
Write Enron long integer
register
Write Enron long integer
registers
Read Enron floatingpoint register
Write Enron floatingpoint register
Write Enron floatingpoint registers
Maximum Registers
2000
1
880
125 note 1
1
60
62 note 2
1
30
62
1
30
Notes
For SCADASense Series controllers, the MSIP function can read a maximum of 123 registers with a
single MSIP function. Note that SCADASense Series controllers do not support Enron Modbus
commands.
The slave controller address edit-box sets the station number of the controller. The valid range is 0 to
255 if standard addressing is used, and 0 to 65534 if extended addressing is used. Address 0 is
reserved for broadcast messages, which are directed to the IP address specified in the slave IP
address field only.
The slave register address specifies the first register where data will be read from or written to in the
slave controller. The following table shows the valid slave register addresses for each command.
Function Code
Slave Register
Length
Read Coil Status
Read Input Status
Read Holding Register
Read Input Register
Write Single Coil
Write Single Register
Write Multiple Coils
Write Multiple Registers
Read Enron Boolean
Address
00001 to 09999
10001 to 19999
40001 to 49999
30001 to 39999
00001 to 09999
40001 to 49999
00001 to 09999
40001 to 49999
0 to 65535
2000
2000
125
125
1
1
880
60
2000
TelePACE Ladder Logic Function Reference
February 19, 2007
99
Function Code
Slave Register
Length
Write Enron Boolean
Write Enron Multiple Boolean
Read Enron Short Integer
Write Enron Short Integer
Write Enron Multiple Short Integer
Read Enron Long Integer
Write Enron Long Integer
Write Enron Multiple Long Integer
Read Enron Floating Point
Write Enron Floating Point
Write Enron Multiple Floating Point
Address
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
0 to 65535
1
880
125
1
60
62
1
30
62
1
30
The master register address specifies the first register where data will be written to or read from in
this controller. The register type does not have to match the type of the slave register address. It is
possible to store input registers from a slave into output registers on the master and vice-versa.
The length parameter specifies how many registers are to be transferred. The maximum length for
each function code is shown in the above table. Functions 05 and 06 always transfer 1 register,
regardless of the value of length.
The time-out is in 0.1s increments. The error output is energized if the time-out period ends without
a valid response to the message.
When an error occurs, an error status code is stored in the command status register in the timer
control block. The status codes are shown in the following table.
Status Code
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Description
valid command has been sent
response was received
no message was sent
invalid function code
invalid slave station address
invalid database address
invalid message length
serial port or protocol is invalid
connecting to slave IP address
connected to slave IP address
timeout while connecting to slave IP address
TCP/IP error has occurred while sending message
timeout has occurred waiting for response
slave has closed connection; incorrect response; or, incorrect response
length
disconnecting from slave IP address is in progress
connection to slave IP address is disconnected
invalid connection ID
invalid protocol type
invalid slave IP address
TelePACE Ladder Logic Function Reference
February 19, 2007
100
Status Code
19
20
21
22
24
25
26
27
28
29
30
Description
last message is still being processed
master connection has been released
error while connecting to slave IP address
no more connections are available
exception response: invalid function code
exception response: invalid address
exception response: invalid value
protocol is invalid or serial port queue is full
slave and master stations are equal; they must be different
exception response: slave device failure
exception response: slave device busy
Example
An example of polling using the MSIP block is in the file MTCP.LAD. This file is automatically
installed on the computer when the TelePACE program is installed. It is located in the
TELEPACE\EXAMPLES directory.
TelePACE Ladder Logic Function Reference
February 19, 2007
101
2.40
MUL – Multiply Signed Values
Description
The MUL function block multiplies a signed register or constant, value 1, by a signed register or
constant, value 2 and stores the result in two consecutive holding registers, product. Signed
multiplication is used.
ON = enable MUL
value 1
copies input 1
value 2
MUL
product
Function Variables
Variable
Value 1
Value 2
Product
Valid Types
Constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
Constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
2 holding registers (4xxxx)
Description
first signed value to multiply
Second signed value to multiply
product = value 1 x value 2
The result is stored in two consecutive holding
registers. The low order word is stored in the
first register.
Related Functions
MULF - Multiply Floating-Point Values
MULU – Multiply Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
102
Example
n e tw o rk 1 :
47286
48661
MUL
44216
In network 1 a MUL function is used to multiply the contents of Holding Register 47286, value 1,
with the contents of Holding Register 48661, value 2. The product is stored in Holding Registers
44216, low order word and Holding Register 44217, high order word.
The examples in the table below show the product of the multiplication for various values in
registers 47286 and 48661. The product is displayed as registers 44216, low order word and register
44217, high order word.
example 1
example 2
example 3
example 4
Register
47286
Value 1
-3057
-15
1654
164
TelePACE Ladder Logic Function Reference
February 19, 2007
Register
48661
value 2
-10
100
17
-55
high order
Register
44217
Product
0
-1
0
-1
low order
Register
44216
product
30570
-1500
28118
-9020
103
2.41
MULF - Multiply Floating-Point Values
Description
The MULF element multiplies two floating-point registers or constants and stores the result in a
floating-point holding register.
When the enable input is ON the product value 1 × value 2 is stored in the product floating-point
register. The element output is ON when the input is.
ON = enable
value1
copies status of input
value2
MULF
product
Function Variables
The element has three parameters.
Variable
Value1
Value2
Product
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
2 holding registers (4xxxx)
Description
first floating-point register or
constant to multiply
second floating-point register or
constant to multiply
floating-point product = value1 ×
value2
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number. Floating point numbers can represent positive or negative values in the range –
3.402 × 1038 to 3.402 × 1038.
Related Functions
MULU – Multiply Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
104
Example
network 1:
+44.10
40100
MULF
40102
The MULF function in network 1 multiplies floating-point constant +44.10 by the contents of
floating-point register 40100 (registers 40100 and 40101). Assuming floating-point register 40100
contains a value of +3.5 then the result is +154.35. This value is stored in floating-point register
40102 (registers 40102 and 40103).
TelePACE Ladder Logic Function Reference
February 19, 2007
105
2.42
MULU – Multiply Unsigned Values
Description
The MULU function block multiplies an unsigned register or constant, value 1, and an unsigned
register or constant , value 2. The result is stored in two consecutive Holding Registers, product.
Unsigned multiplication is used.
ON = enable MULU
value 1
copies input 1
value 2
MULU
product
Function Variables
Variable
value 1
value 2
Product
Valid Types
Constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
Constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
2 holding registers (4xxxx)
Description
first unsigned value to multiply
Second unsigned value to multiply
Product = value 1 x value 2
The result is stored in two
consecutive holding registers. The
low order word is stored in the first
register.
Related Functions
MULF - Multiply Floating-Point Values
TelePACE Ladder Logic Function Reference
February 19, 2007
106
Example
n e tw o rk 1 :
47286
48661
M ULU
44216
In network 1 a MULU function is used to multiply the contents of Holding Register 47286, value 1,
with the contents of Holding Register 48661, value 2. The product is stored in Holding Registers
44216, low order word and Holding Register 44217, high order word.
The examples in the table below show the product of the multiplication for various values in
registers 47286 and 48661. The product is displayed as registers 44216, low order word and register
44217, high order word.
Example 1
Example 2
Example 3
Example 4
Register
47286
Value 1
2048
251
77
650
TelePACE Ladder Logic Function Reference
February 19, 2007
Register
48661
value 2
30
251
77
735
high order
Register
44217
Product
0
0
0
7
low order
Register
44216
product
61440
63001
5929
18998
107
2.43
Normally Closed Contact
Description
The NC contact function block conducts power when the coil or status register is OFF.
input
output
contact
Function Variables
Variable
contact
Valid Types
coil register (0xxxx)
status register (1xxxx)
Description
Output is ON if contact is OFF and
input is ON
Related Functions
Normally Open Contact
Example
n e tw o rk 1 :
(
)
10003
01041
01041
00010
(
)
Network 1 shows NO contact 10003 and NC contact 01041. Power conducts through NC contact
01041 keeping coil 00010 ON. When NO contact 10003 is closed coil 01041 turns ON and NC
contact 01041 will open, turning OFF coil 00010.
TelePACE Ladder Logic Function Reference
February 19, 2007
108
2.44
Normally Open Contact
Description
The NO contact function block conducts power when the coil or status register is ON.
input
output
contact
Function Variables
Variable
contact
Valid Types
coil register (0xxxx)
status register (1xxxx)
Description
output is ON if contact is ON and
input is ON
Related Functions
Normally Closed Contact
Example
n e tw o rk 1 :
(
)
10033
00006
00006
04081
(
)
Network 1 shows NC contact 10033 and NO contact 00006. Power conducts through NC contact
10033 keeping coil 00006 ON. With coil 00006 ON, NO contact 00006 is closed and coil 04081 is
ON.
TelePACE Ladder Logic Function Reference
February 19, 2007
109
2.45
NOT – Not Block
Description
The NOT function block inverts the source block of registers and stores the result in the destination
block of coil or Holding registers. NOT changes bits that are ON to OFF, and changes bits that are
OFF to ON.
ON = enable NOT
source
copies status of input1
destination
NOT
size
Function Variables
Variable
Source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Destination
coil block (0xxxx)
holding register (4xxxx)
Size
Constant (1..100)
Description
The first register in the source
block.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
complemented.
The first register in the destination
block. The address for a coil
register block is the first register in
a group of 16 registers where the
result will be stored.
The number of 16 bit words in the
block.
Notes
NOT accesses 16 bit words. Coil and status register blocks are groups of 16 registers that start with
the register specified as the block address. A block size of 2 corresponds to 32 coils, or two holding
registers.
Coil and status register blocks must begin at the start of a 16 bit word within the controller memory.
Suitable addresses are 00001, 00017, 10001, 10033, etc.
Related Functions
AND – And Block
OR – Or Block
XOR – Exclusive Or Block
TelePACE Ladder Logic Function Reference
February 19, 2007
110
Example
n e tw o rk 1 :
10001
48000
NOT
+1
In this example the status of discrete inputs 10001 through 10016 are used as the source for the NOT
function. These inputs are inverted and stored in the destination register 48000.
status registers:
read top to bottom
1
0
0
1
6
1
0
0
1
5
1
0
0
1
4
1
0
0
1
3
1
0
0
1
2
1
0
0
1
1
1
0
0
1
0
1
0
0
0
9
1
0
0
0
8
1
0
0
0
7
1
0
0
0
6
1
0
0
0
5
1
0
0
0
4
1
0
0
0
3
1
0
0
0
2
1
0
0
0
1
source register:
0 0 0 1 1 0 1 1 0 1 1 0 1 1 0 1
destination register
after storing result
1 1 1 0 0 1 0 0 1 0 0 1 0 0 1 0
TelePACE Ladder Logic Function Reference
February 19, 2007
111
2.46
One Shot Coil
Description
The One Shot Coil function block enables an output coil for one scan when the input power changes
from OFF to ON.
input power
always connects to right rail
output
Function Variables
Variable
Output
Valid Types
coil register (0xxxx)
Description
output register
address
Related Functions
Coil
Example
n e tw o rk 1 :
(
)
00004
One shot coil 00004 is energized for one scan on power up of the ladder logic program.
Refer to the I/O Database Registers section of this manual for more information on coil outputs.
TelePACE Ladder Logic Function Reference
February 19, 2007
112
2.47
OR – Or Block
Description
The OR function block logically ORs the source block of registers with the destination block of
registers and stores the result in the destination block of registers.
ON = enable OR
source
copies status of input1
destination
OR
size
Function Variables
Variable
Source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Destination
coil block (0xxxx)
holding register (4xxxx)
Size
Constant (1..100)
Description
The first register in the source
block.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
ORed.
The first register in the destination
block.
The address for a coil register block
is the first register in a group of 16
registers that will be ORed.
The number of 16 bit words in the
block.
Notes
OR accesses 16 bit words. Coil and status register blocks are groups of 16 registers that start with the
register specified as the block address. A block size of 2 corresponds to 32 coils, or two holding
registers.
Coil and status register blocks must begin at the start of a 16 bit word within the controller memory.
Suitable addresses are 00001, 00017, 10001, 10033, etc.
Related Functions
AND – And Block
NOT – Not Block
XOR – Exclusive Or Block
TelePACE Ladder Logic Function Reference
February 19, 2007
113
Example
45420
46110
OR
+1
In this example the contents of source register, 45420, are ORed with the destination register, 46110.
The result is stored in the destination register. The content of register 45420 is 1521310
(11101101101101). The content of the destination register before the OR function is 2237910
(101011101101011). The content of the destination register after the OR function is 3262310
(111111101101111).
source register
0 0 1 1 1 0 1 1 0 1 1 0 1 1 0 1
destination register
before OR
0 1 0 1 0 1 1 1 0 1 1 0 1 0 1 1
destination register
after OR
0 1 1 1 1 1 1 1 0 1 1 0 1 1 1 1
TelePACE Ladder Logic Function Reference
February 19, 2007
114
2.48
OVER – Override Block of Registers
Description
The OVER function copies, in one scan, the source block of registers into the destination block of
registers and forces all registers in the destination block. When the override block input transitions
from OFF to ON the destination registers are forced. The destination register values are overwritten
with the source register values while the override block input is ON. Destination registers are
unforced when the override block input transitions from ON to OFF. The function block output
copies the input state.
The FORCE led on the controller is turned on when the OVER function is enabled. This function is
useful for simulating inputs while debugging a control program.
ON = override block
source
copies status of input 1
destination
OVER
size
Function Variables
Variable
Source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Destination
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Size
constant (1 to 100)
Description
The first register in the source
block.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
copied.
The first register in the destination
block.
The address for a coil or status
register block is the first register in
a group of 16 registers.
The number of 16 bit words in the
block.
Notes
The OVER function copies 16-bit words. Coil and status register blocks are groups of 16 registers
that start with the register specified as the block address. A block size of 2 corresponds to 32 coils, or
two holding registers.
Coil and status register blocks must begin at the start of a 16-bit word within the controller memory.
Suitable addresses are 00001, 00017, 10001, 10033, etc.
TelePACE Ladder Logic Function Reference
February 19, 2007
115
An ON to OFF transition of the input must occur to remove the forcing on the registers. If you place
an OVER function in a subroutine, be sure to execute the subroutine at least once with the input OFF
to clear forcing (see the example below).
If forcing is cleared with a TelePACE command while the OVER function is enabled, the forcing
will not be set again by the OVER function. You must disable and re-enable the function to force the
registers. The function will continue to attempt to write to destination registers even though they are
not forced.
Related Functions
MOVE – Move Block
Example
This example shows how simulated values can be written over input values in the I/O database. For
this example, assume there is a register assignment that connects input hardware to registers 30001 to
30011, and to registers 10001 to 10016.
The simulate contact (10050) enables and disables the simulation. When the contact is ON simulated
values are used. To simulate the values of the inputs, the program overrides the values in registers
30001 to 30011, and registers 10001 to 10016.
The first network calls the subroutine when the simulate contact is ON, and one additional time when
the contact goes from ON to OFF.
simulate
10050
end
00001
CALL
simulate
10050
+1
end
00001
The second network is a subroutine that overrides the destination registers while the simulate contact
is closed. A subroutine is used so that the logic is not scanned when the simulated values are not
needed. In most programs this is the normal operating state, so scanning the functions would add
unnecessarily to the execution time of the program.
TelePACE Ladder Logic Function Reference
February 19, 2007
116
SUBR
+1
simulate
10050
source1
40100
source2
00017
dest1
30001
dest2
10001
OVER
10
OVER
1
TelePACE Ladder Logic Function Reference
February 19, 2007
117
2.49
PID – PID Controller
Description
The PID function controls the execution of a PID controller. PID controllers execute independently
of the ladder logic scan. A PID controller is configured by writing data into the PID controller
registers defined in the register assignment.
The PID block starts execution of the PID controller number on the rising edge of the execute PID
input. Execution of the PID controller is stopped when the execute PID is OFF.
The execute PID input must be toggled from OFF to ON under program control to start PID
execution. The execute PID input cannot be directly connected to the power rail or PID execution
will not restart when the program restarts.
The error output is enabled if the PID number is not found in the Register Assignment. The error
output is also enabled if an error code is present in the PID Status Register (SR).
For a detailed description of the operation of the PID function refer to the TelePACE PID
Controllers User Manual.
ON = execute PID
OFF = stop PID
number
PID
period
copies status of input 1
ON = error
Function Variables
Variable
number
period
Valid Types
Constant (0..31)
Constant (0..65535)
Description
PID controller number
PID controller execution period
(tenths of seconds )
The I/O module, CNFG PID control block, must be configured in the Register Assignment when
PID functions are used. The I/O module CNFG PID control block provides control over the
configuration of a PID control block and provides access to the control block parameters. Control
block parameters are assigned to 25 consecutive holding registers. The I/O module address refers to
the PID control block number.
Notes
The SCADAPack 32 controller does not support the PID function. See the function PIDA – Analog
Output PID and the function PIDD – Digital Output PID.
TelePACE Ladder Logic Function Reference
February 19, 2007
118
2.50
PIDA – Analog Output PID
Description
The PIDA function performs a PID algorithm and calculates an analog output.
When the enable PIDA input is ON, the function executes the PID algorithm. Execution of the PID
algorithm is stopped when the enable PIDA is OFF.
When the auto/manual mode input is ON, the PID is placed in automatic mode. In automatic mode
the output is calculated using the PID algorithm. A new calculation is done at the rate specified by
cycle time.
When the auto/manual mode input is OFF, the PID is placed in manual mode. In manual mode the
output is set to the value specified by manual mode output. The output is limited to the range set
by full and zero.
ON = enable PIDA
settings
ON = auto mode
OFF = manual mode
copies status of input1
PIDA
output
Function Variables
Variable
Settings
Output
Valid Types
holding register (4xxxx)
holding register (4xxxx)
Description
Address of the first register in the settings
control block. There are 20 registers in the block
at addresses settings+0 to settings+19.
+0,1 = process value (float)
+2,3 = setpoint (float)
+4,5 = gain (float)
+6,7 = reset time in seconds (float)
+8,9 = rate time in seconds (float)
+10,11 = deadband (float)
+12,13 = full (float)
+14,15 = zero (float)
+16,17 = cycle time in seconds (float)
+18,19 = manual mode output (float)
+0,1 = PID output (float)
+2,3 = internal: process value N-1st (float)
+4,5 = internal: process value N-2nd (float)
+6,7 = internal: error N-1st (float)
+8,9 = internal: time of last scan (UINT32)
The process value is a value that represents the actual state of the process being controlled. This
value is typically input to the controller as an analog input signal or as a signal from a MVT. The
process value is a floating-point number. If the process value is an analog input signal to the
controller it must be converted to a floating-point number using the STOF function. If the analog
TelePACE Ladder Logic Function Reference
February 19, 2007
119
input requires scaling use the SCAL function to scale the input and provide a floating-point number
for the process value.
Element Configuration
This element is configured using the PIDA Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
PID Velocity Algorithm
The PIDD function uses the velocity form of the PID algorithm. The velocity form calculates the
change in the output and adds it to the previous output.
en = s n − p n
⎤
⎡
T
R
mn = mn −1 + K ⎢en − en −1 + en + ( p n − 2 p n −1 + p n − 2 )⎥
Ti
T
⎦
⎣
Where: e = error
s = setpoint
p = process value
K = gain
T = execution period
Ti = integral or reset time
R = rate gain
m = output
The Element Configuration dialog is used to input each parameter into the calculation. These
parameters are described below.
TelePACE Ladder Logic Function Reference
February 19, 2007
120
Setpoint
The setpoint is a floating-point value representing the desired value of the process value. The error
value is the difference between the process value and the setpoint.
error = process value – setpoint (+/- deadband).
Process Value
The process value is a value that represents the actual state of the process being controlled. See the
Function Variables section above for the registers to use for the process value input to the PIDD.
Gain
The proportional (P) part of the PID algorithm is the gain. A positive value of gain configures a
forward-acting PID controller and a negative value of gain configures a reverse acting controller.
Reset Time
The integral (I) part of the PID algorithm is the reset time. This value, in seconds, controls the reset
gain (or magnitude of integral action) in a PI or PID controller. This is typically referred to as
Seconds Per Repeat. From the equation above it is seen that the integral action of the PI or PID
controller is a function of the reset time and the execution period (cycle time). A smaller reset time
provides more integral action and a larger reset time provides less integral action. Valid range is any
value greater than 0. A value of 0 disables the reset action.
Rate Gain
The derivative (D) part of the PID algorithm is the rate time. This value, in seconds, controls the
rate gain (or magnitude of derivative action) in a PD or PID controller. From the equation above it is
seen that the derivative action of the PD or PID controller is a function of the rate gain and the
execution period (cycle time). A larger rate gain provides more derivative action and a smaller rate
gain provides less derivative action. Valid range is any value greater than 0. A value of 0 disables the
rate action.
Deadband
The deadband parameter is used by the PID algorithm to determine if the process requires the
control outputs to be changed. If the absolute value of the error is less than the deadband, then the
function block skips execution of the control algorithm. This prevents changes to the output when
the process value is near the setpoint and can reduce wear on the control elements. Valid range is any
value greater than 0.The setpoint is a floating-point value representing the desired value of the
process value.
Full
The full setting is used in limiting the maximum output value of the PIDA function. If the PID
algorithm calculates an output quantity that is greater than the value stored in full, the output
quantity is set equal to the value stored in full. The full setting should always be greater than the
zero setting.
TelePACE Ladder Logic Function Reference
February 19, 2007
121
Zero
The zero setting is used in limiting the minimum output value of the PIDA function. If the PID
algorithm calculates an output quantity that is less than the value stored in zero, the output quantity
is set equal to the value stored in zero. The zero setting should always be less than the full setting.
Cycle Time
The cycle time is the floating-point value of the PID algorithm execution period measured in
seconds. Any value greater than or equal to 0.001 seconds (1 ms) may be specified. If the cycle time
specified is less than the scan time of the TelePACE program, the program scan time becomes the
PID cycle time.
Manual Mode
The manual mode output is the value that the output is set to when the PIDA function is in manual
mode.
Related Functions
PIDD – Digital Output PID
TelePACE Ladder Logic Function Reference
February 19, 2007
122
2.51
PIDD – Digital Output PID
Description
The PIDD function performs a PID velocity algorithm (see description below) and operates two
discrete outputs to maintain PID control.
The output of the PIDD is the output percent value output%. The output% is a duty cycle of the
cycle time as defined by the zero% and full% parameters.
The increase output is cycled when the output% is greater than zero. The decrease output is cycled
when the output% is less than zero.
When the enable PIDD input is ON, the function executes the PID algorithm. Execution of the PID
algorithm is stopped when the enable PIDD is OFF.
When the auto/manual mode input is ON, the PID is placed in automatic mode. In automatic mode
the output is calculated using the PID algorithm. A new calculation is done at the rate specified by
cycle time.
When the auto/manual mode input is OFF, the PID is placed in manual mode. In manual mode the
output% is set to the value specified by manual output%. The output is limited to the range set by
full% and zero%.
ON = enable PIDD
settings
ON = increase; output% > 0
ON = auto mode
OFF = manual mode
PIDD
output%
ON = decrease; output% < 0
Function Variables
Variable
Valid Types
Description
settings
holding register (4xxxx)
Address of the first register in the settings
control block. There are 21 registers in the
block at addresses settings+0 to settings+20.
output%
holding register (4xxxx)
TelePACE Ladder Logic Function Reference
February 19, 2007
+0,1 = process value (float)
+2,3 = setpoint (float)
+4,5 = gain (float)
+6,7 = reset time in seconds (float)
+8,9 = rate time in seconds (float)
+10,11 = deadband (float)
+12,13 = full% (float)
+14,15 = zero% (float)
+16,17 = cycle time in seconds (float)
+18,19 = manual mode output% (float)
+20 = motor output enabled
+0,1 = PID output % (float)
+2,3 = internal: process value N-1st (float)
123
Variable
Valid Types
Description
+4,5 = internal: process value N-2nd (float)
+6,7 = internal: error N-1st (float)
+8,9 = internal: time of last scan (UINT32)
+10,11 = internal: on time for controller
(UINT32)
The process value is a value that represents the actual state of the process being controlled. This
value is typically input to the controller as an analog input signal or as a signal from a MVT. The
process value is a floating-point number. If the process value is an analog input signal to the
controller it must be converted to a floating-point number using the STOF function. If the analog
input requires scaling use the SCAL function to scale the input and provide a floating-point number
for the process value.
The remaining settings and output% registers are described in the Element Configuration section
below.
Element Configuration
This element is configured using the PIDD Element Configuration dialog. Highlight the
element by moving the cursor over the element and then use the Element Configuration
command on the Edit menu to modify the configuration block.
PID Velocity Algorithm
The PIDD function uses the velocity form of the PID algorithm. The velocity form calculates the
change in the output and adds it to the previous output.
en = s n − p n
TelePACE Ladder Logic Function Reference
February 19, 2007
124
⎤
⎡
R
T
mn = mn −1 + K ⎢en − en −1 + en + ( p n − 2 p n −1 + p n − 2 )⎥
T
Ti
⎦
⎣
Where: e = error
s = setpoint
p = process value
K = gain
T = execution period
Ti = integral or reset time
R = rate gain
m = output
The Element Configuration dialog is used to input each parameter into the calculation. These
parameters are described below.
Setpoint
The setpoint is a floating-point value representing the desired value of the process value. The error
value is the difference between the process value and the setpoint.
error = process value – setpoint (+/- deadband).
Process Value
The process value is a value that represents the actual state of the process being controlled. See the
Function Variables section above for the registers to use for the process value input to the PIDD.
Gain
The proportional (P) part of the PID algorithm is the gain. A positive value of gain configures a
forward-acting PID controller and a negative value of gain configures a reverse acting controller.
Reset Time
The integral (I) part of the PID algorithm is the reset time. This value, in seconds, controls the reset
gain (or magnitude of integral action) in a PI or PID controller. This is typically referred to as
Seconds Per Repeat. From the equation above it is seen that the integral action of the PI or PID
controller is a function of the reset time and the execution period (cycle time). A smaller reset time
provides more integral action and a larger reset time provides less integral action. Valid range is any
value greater than 0. A value of 0 disables the reset action.
Rate Gain
The derivative (D) part of the PID algorithm is the rate time. This value, in seconds, controls the
rate gain (or magnitude of derivative action) in a PD or PID controller. From the equation above it is
seen that the derivative action of the PD or PID controller is a function of the rate gain and the
execution period (cycle time). A larger rate gain provides more derivative action and a smaller rate
gain provides less derivative action. Valid range is any value greater than 0. A value of 0 disables the
rate action.
TelePACE Ladder Logic Function Reference
February 19, 2007
125
Deadband
The deadband parameter is used by the PID algorithm to determine if the process requires the
control outputs to be changed. If the absolute value of the error is less than the deadband, then the
function block skips execution of the control algorithm. This prevents changes to the output when
the process value is near the setpoint and can reduce wear on the control elements. Valid range is any
value greater than 0.
Full Scale Output
The full% setting is the full-scale output limit in percent of cycle time. For example if the cycle time
is 10 seconds and the full% value is 100 then the maximum duty cycle of the output% is 100 percent
or 10 seconds.
When the zero% value is 0 or greater then the increase output is turned on for the duty cycle of the
output%. When the zero% value is less than zero the decrease output is turned on for the duty cycle
of the output% when the output% is negative.
Zero Scale Output
The zero% setting is the zero scale output limit in percent of cycle time. When the zero% value is 0
or greater then the increase output is turned on for the duty cycle of the output%. When the zero%
value is less than zero the decrease output is turned on for the duty cycle of the output% when the
output% is negative.
Cycle Time
The cycle time is the floating-point value of the PID algorithm execution period measured in
seconds. Any value greater than or equal to 0.001 seconds (1 ms) may be specified. If the cycle time
specified is less than the scan time of the TelePACE program, the program scan time becomes the
PID cycle time.
Manual Mode Output
The manual mode output% is the value that the output% is set to when the PIDD function is in
manual mode.
Motor Output
When the motor output is set to enabled the increase and decrease outputs are de-energized when
error is within the deadband. When the motor output is set to disabled the increase and decrease
outputs operate continuously based on the output%.
Related Functions
PIDA – Analog Output PID
TelePACE Ladder Logic Function Reference
February 19, 2007
126
2.52
POWR – Floating-Point Raised to Power
Description
The POWR function calculates the result of a value raised to an exponent and stores the result in a
floating-point holding register.
When the enable input is ON, value is raised to the exponent and stored in the result floating-point
register.
The top output is ON when the input is.
The out-of-range output is ON if the value is zero and exponent is less than zero; and if value is
negative. The result is not calculated in these cases.
ON = enable
value
exponent
copies status of input 1
ON = out of range
POWR
result
Function Variables
Variable
Value
Exponent
Result
Valid Types
Floating Point Constant
2 input registers (3xxxx)
2 holding register (4xxxx)
Floating Point Constant
2 input registers (3xxxx)
2 holding register (4xxxx)
2 holding register (4xxxx)
Description
Floating Point value to be raised.
The high order word is stored in the
first register.
Floating Point value to raise value
to.
The high order word is stored in the
first register.
result = valueexponent
The high order word is stored in the
first register.
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number.
The calculation is performed using a single-precision floating-point number.
Floating point numbers can represent positive or negative values in the range –3.402 × 1038 to 3.402
× 1038.
Related Functions
ABSF - Floating-Point Absolute Value
TelePACE Ladder Logic Function Reference
February 19, 2007
127
ADDF - Add Floating-Point Values
DIVF - Divide Floating-Point Values
MULF - Multiply Floating-Point Values
SQRF - Square Root of Floating-Point Value
SUBF – Subtract Floating-Point Values
TelePACE Ladder Logic Function Reference
February 19, 2007
128
2.53
PULM - Pulse Minutes
Description
The PULM function controls a square wave digital signal.
While the enable is ON, the output signal will be active ON or OFF based on the period. The output
is powered only when the enable input is ON.
For example when the enable input is on and a period of 10 minutes is used the result will be an
output square wave that is ON for 5 minutes and then OFF for 5 minutes.
ON = enable
period
Output signal
PULM
counter
Function Variables
Variable
Period
Counter
Valid Types
Constant (1..65535)
input register (3xxxx)
holding register (4xxxx)
2 holding registers (4xxxx)
Description
The period of the waveform, in
minutes.
Contains the accumulated time of
the period in seconds.
Notes
The Period is from 1 to 65535 minutes.
Related Functions
PULS - Pulse Seconds
Example
n e tw o rk 1 :
+10
(
)
01057
P U LM
46770
In this example the PULM function has a period value of 10 minutes. Coil 01057 will be on for 5
minutes and then off for 5 minutes. When the program is first run coil 01057 will start in on state for
5 minutes then go off for 5 minutes, repeating this cycle as long as the enable input is true. Registers
46770 and 46771 contain the accumulated time for the period in seconds.
TelePACE Ladder Logic Function Reference
February 19, 2007
129
2.54
PULS - Pulse Seconds
Description
The PULS function controls a square wave digital signal.
While the enable is ON, the output signal will be active ON or OFF based on the period. The output
is powered only when the enable input is ON.
For example when the enable input is on and a period of 10 seconds is used the result will be an
output square wave that is ON for 5 seconds and then OFF for 5 seconds.
ON = enable
period
Output signal
PULS
counter
Function Variables
Variable
Period
Counter
Valid Types
Constant (1..65535)
input register (3xxxx)
holding register (4xxxx)
2 holding registers (4xxxx)
Description
The period of the waveform, in
seconds.
Contains the accumulated time of
the period in tenths of seconds.
Notes
The Period is from 1 to 65535 seconds. The smallest actual period will depend on the ladder scan
time. Smaller ladder programs will be able to handle smaller periods.
Related Functions
Timers
Example
n e tw o rk 1 :
+10
(
)
01057
P U LS
45660
In this example the PULM function has a period value of 10 seconds. Coil 01057 will be on for 5
seconds and then off for 5 seconds. When the program is first run coil 01057 will start in on state for
5 seconds then go off for 5 minutes, repeating this cycle as long as the enable input is true. Registers
46770 and 46771 contain the accumulated time for the period in seconds.
TelePACE Ladder Logic Function Reference
February 19, 2007
130
2.55
PUTB – Put Bit into Block
Description
The PUTB function block writes the status of a bit, at the bit index, into the destination block of
registers.
The enable PUTB input must be energized for a PUTB function to execute.
The bit to put into block input is the bit value that will be written into the destination register at the
location of the bit index when enable PUTB is energized.
The increment bit index input increments the index, once each scan, when enable PUTB is
energized.
ON = enable PUTB
bit index
copies state of input 1
bit to put into block
destination
copies state of input 2
ON = increment bit index
PUTB
size
ON if index > size
Function Variables
Variable
bit index
Valid Types
Constant (0..65535)
Holding register (4xxxx)
Destination
coil block (0xxxx)
holding register (4xxxx)
Size
Constant (1..100)
Description
The index of the bit within the
destination block. A bit index of 0 is
the most significant bit of the first
register of the destination block.
The address of the destination
register block.
The address for a coil register block
is the first register in a group of 16
registers.
number of 16 bit words in the block.
Notes
Put bit into block accesses 16 bit words. Coil blocks are groups of 16 registers that start with the
register specified as the block address. Coil blocks must begin at the start of a 16 bit word within the
controller memory. Suitable addresses are 00001, 00017, 00033, etc.
Related Functions
GETB – Get Bit from Block
ROTB – Rotate Bits in Block
CMPB – Compare Bit
TelePACE Ladder Logic Function Reference
February 19, 2007
131
Example
01056
+2
40234
(
)
03841
01057
PUTB
+1
In network 1 the PUTB function is being used to set the manual control bit in the PID Block 0
Control Register, bit 13 of register 40234. The bit index of the manual control bit is 2, with 0 being
the most significant bit.
Closing contacts 01056 allows power to be supplied to the enable PUTB input of the PUTB function
block. With the function block enabled, closing contacts 01057 allows power to the put bit into
block input of the function block. The bit at the index is then set in the destination register, the PID
Block 0 Control Register. Output coil 03841 is energized.
TelePACE Ladder Logic Function Reference
February 19, 2007
132
2.56
PUT – Put Signed Value into Registers
Description
The PUT function transfers, in one scan, the source holding register or signed constant into the
destination holding registers. The number of destination registers is determined by size. The same
value is stored in each destination register.
The source register, or signed constant, is transferred to the destination holding register when enable
transfer is ON.
If the source is a register, this function is identical to the PUTU function.
ON = enable transfer
source
copies state of input1
destination
PUT
size
Function Variables
Variable
source
destination
Size
Valid Types
Constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
Holding register (4xxxx)
Constant
(1..9999)
Description
The signed value or address of the
register containing the value to be
stored.
The address of the first destination
register.
The number of destination
registers.
Related Functions
PUTU – Put Unsigned Value into Registers
PUTF - Put Floating-Point Value
TelePACE Ladder Logic Function Reference
February 19, 2007
133
Example
n e tw o rk 1 :
(
)
01025
1
01025
2
3
-1 8
42526
0
44513
49483
44260
PUT
PUT
PUT
+1
+3
+8
In this example there are three PUT functions in network 1. On power up One Shot coil 01025 is
energized for one scan. This will cause NO contacts 01025 to close, applying power to the enable
transfer input on PUT functions 1,2 and 3.
In PUT 1 the constant value -18 is transferred to holding register 44513.
In PUT 2 the value of holding register 42526 (1000) is transferred to holding registers 49483 through
49485.
In PUT 3 the constant value 0 is transferred to holding registers 44260 through 44267.
TelePACE Ladder Logic Function Reference
February 19, 2007
134
2.57
PUTF - Put Floating-Point Value
Description
The PUTF element transfers, in one scan, the source floating-point holding register or constant into
the destination floating-point holding registers. The number of floating-point destination registers is
determined by size. The same value is stored in each floating-point register pair.
When the enable input is ON, the source register or constant is transferred to the destination
registers. The element output is ON when the input is.
ON = enable
source
copies status of input
destination
PUTF
size
Function Variables
The element has three parameters.
Variable
source
Destination
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
Holding register (4xxxx)
Size
Constant (1…4999)
Description
Floating-point register or
constant to be stored
Address of the first pair of
destination registers
the number of floating-point
destination registers pairs to
store
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number. Floating point numbers can represent positive and negative values in the range –
3.402 × 1038 to 3.402 × 1038.
The size parameter determines the number of floating-point register pairs affected. The number of
registers affected is twice the value of size, since each floating-point value uses two registers.
Related Functions
PUT – Put Signed Value into Registers
PUTU – Put Unsigned Value into Registers
TelePACE Ladder Logic Function Reference
February 19, 2007
135
Example
network 1:
+44.10
40100
PUTF
+1
The PUTF function in network 1 puts the floating-point constant +44.10 value into floating-point
register 40100 (registers 40100 and 40101).
TelePACE Ladder Logic Function Reference
February 19, 2007
136
2.58
PUTU – Put Unsigned Value into Registers
Description
The PUTU function transfers, in one scan, the source holding register or unsigned constant into the
destination holding registers. The number of destination registers is determined by size. The same
value is stored in each destination register.
The source register, or unsigned constant, is transferred to the destination holding register when
enable transfer is ON.
If the source is a register, this function is identical to the PUT function.
source
ON = enable transfer
copies state of input1
destination
PUTU
size
Function Variables
Variable
source
Destination
Valid Types
Constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
Holding register (4xxxx)
Size
Constant (1..9999)
Description
The unsigned value or address of
the register containing the value to
be stored.
The address of the first destination
register.
The number of destination registers.
Related Functions
PUT – Put Signed Value into Registers
PUTF - Put Floating-Point Value
TelePACE Ladder Logic Function Reference
February 19, 2007
137
Example
network 1:
( )
01057
01057
14
30
0
40210
40211
40212
PUTU
PUTU
PUTU
+1
+1
+1
This example uses two PUTU functions to write the correct time to the Real Time Clock. The time
for this example is 14:30:00.
The holding registers used to in this example must be assigned to the CNFG Real Time Clock and
Alarm I/O Module in the Register Assignment. Holding registers 40210 through 40220 are assigned
to this I/O module.
On power up One Shot coil 01057 is energized for one scan. This will cause NO contacts 01057 to
close, applying power to the enable transfer inputs on the two PUTU functions.
The real time clock continues to run with the new time setting immediately after these PUTU
functions are enabled. Note that all seven clock registers must be set to valid values for the clock to
operate correctly.
Another method for setting the clock, is to use the Edit/Force Register dialog to write the current
time to the appropriate module registers. Leave the force box in the dialog unchecked so that the data
is only written, not forced.
TelePACE Ladder Logic Function Reference
February 19, 2007
138
2.59
R–>L – Register to List Transfer
Description
The R->L function transfers the contents of the source register into a register in the destination list of
registers indicated by the index.
When the enable transfer input is ON and the index equals size output is OFF, the source register is
transferred to the destination list register at the position of the index.
The freeze/increment index input allows control of the index. If this input is ON the index is not
incremented. If the input is OFF the index is incremented by one after each transfer.
When the reset index input is ON the index is reset to zero.
The index is incremented by one on each transfer until the index equals size. When the index equals
size output is ON no further increments of the index value occur until the index is reset.
ON = enable transfer
source
ON = freeze index
OFF = increment index
list
ON = reset index to 0
copies state of input 1
ON if index = size
and enable transfer = ON
R->L
size
Function Variables
Variable
source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
index and
destination
Holding register (4xxxx)
Size
Constant (1..9999)
Description
The address of the source register.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
read.
The address of the index register
and the data registers. The index is
stored in register [4xxxx]. The data
is stored in register [4xxxx+1] to
register [4xxxx+size]
The number of registers in the list.
Related Functions
L–>L – List to List Transfer
L–>R – List to Register Transfer
MOVE – Move Block
TelePACE Ladder Logic Function Reference
February 19, 2007
139
Example
01386
42010
42011
R -> L
+4
The Register to List function transfers the contents of the source register 42010 into a register in the
destination list of registers, 42012 to 42015, indicated by the index register 42011.
Destination Register List
Source Register->
42010
List Index-->
list register 0-->
42011
42012
list register 1-->
list register 2-->
list register 3-->
42013
42014
42015
An example of the registers used in a Register to List (R->L) transfer is shown in the above diagram.
The source register is a general purpose analog output register. The index is a general purpose analog
output register that will have a value of 0, 1, 2 or 3. The destination register list starts at the next
sequential register after the index register. The destination list contains four general purpose analog
output registers and has a size of 4.
When list index register 42011 has a value of 0 and the R->L function is enabled the contents of
source register 42010 is transferred to destination list register 40012.
When list index register 42011 has a value of 1 and the R->L function is enabled the contents of
source register 42010 is transferred to destination list register 42013.
When list index register 42011 has a value of 2 and the R->L function is enabled the contents of
source register 42010 is transferred to destination list register 42014.
When list index register 42011 has a value of 3 and the R->L function is enabled the contents of
source register 42010 is transferred to destination register 42015.
TelePACE Ladder Logic Function Reference
February 19, 2007
140
2.60
ROTB – Rotate Bits in Block
Description
The ROTB function block rotates the bits in the source block by one bit and stores the result in the
destination block. The block can be rotated towards either the most significant bit (MSB) or
towards the least significant bit (LSB).
source
ON = rotate bits
ON = rotate toward MSB
OFF = rotate towards LSB
destination
ON = rotate last bit into start
copies status of input 1
state of the last bit shifted
out
ROTB
size
Function Variables
Variable
Source
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
Destination
coil block (0xxxx)
holding register (4xxxx)
Size
Constant (1..100)
Description
The address of the first source
register.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
rotated.
The address of the first destination
register.
The address for a coil or status
register block is the first register in
a group of 16 registers that will be
rotated.
The number of 16 bit words in the
block.
Related Functions
PUTB – Put Bit into Block
GETB – Get Bit from Block
CMPB – Compare Bit
TelePACE Ladder Logic Function Reference
February 19, 2007
141
Example
n e tw o rk 1 :
10010
40221
(
42222
10011
)
00017
10009
ROTB
+1
The ROTB function in network 1 is configured to demonstrate the operation of the function block.
Register 40221, the source register, has a value of 6985. Register 40222 is the destination register.
The first example is a rotate towards LSB. Closing the rotate bits input, contacts 10010, will cause
the bits in the source register to rotate right by one bit and the result to be stored in the destination
register.
source register
0 0 0 1 1 0 1 1 0 1 0 0 1 0 0 1
Rotate towards LSB
destination register
0 0 0 0 1 1 0 1 1 0 1 0 0 1 0 0
The next example is a rotate towards MSB. Closing the rotate towards MSB input, contacts 10009
and then closing the rotate bits input, contacts 10010, will cause the bits in the source register to
rotate once to the left. The result is stored in the destination register.
source register
0 0 0 1 1 0 1 1 0 1 0 0 1 0 0 1
Rotate towards MSB
destination register
0 0 1 1 0 1 1 0 1 0 0 1 0 0 1 0
In the last example the rotate bits input is enabled by closing contact 10010. Closing contacts 10011
will enable the rotate last bit to start input. The LSB of the source register is rotated to the MSB
and the remaining bits are rotated right.
source register
0 0 0 1 1 0 1 1 0 1 0 0 1 0 0 1
Rotate last bit into start
destination register
1 0 0 0 1 1 0 1 1 0 1 0 0 1 0 0
TelePACE Ladder Logic Function Reference
February 19, 2007
142
2.61
SCAL – Scale Analog Value
Description
The SCAL function scales an integer into a floating-point value and detects changes in the floatingpoint value.
When the Enable input is ON the SCAL function calculates the scaled value.
When the Enable input is ON the scaled value is compared to the previous scaled value. If the
difference is greater than the deadband the scaled value changed output is turned ON and the scaled
value is copied to the previous scaled value. The previous scaled value does not change if scaled
value is within the deadband.
When the Enable input changes from OFF to ON, the scaled value is copied to previous scaled
value.
ON = enable
config
SCAL
scaled value
copies status of input
ON = scaled value changed
Function Variables
Variable
config
Valid Types
holding register (4xxxx)
scaled
value
4 holding registers (4xxxx)
Description
Address of the first register in the configuration
block. There are 9 registers in the block at
addresses message+0 to message+8.
+0 = input register
+1 = zero scale raw input
+2 = full scale raw input
+3-4 = zero scale output (floating point)
+5-6 = full scale output (floating point)
+7-8 = deadband (floating point)
Address of the first register in the output block.
There are 4 registers in the block at addresses
output+0 to output+3
+0-1: scaled value (floating point)
+2-3: previous scaled value (floating point)
Element Configuration
This element is configured using the SCAL Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
TelePACE Ladder Logic Function Reference
February 19, 2007
143
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
The Input Register specifies the register from which the input is read. Valid values are any input
(3xxxx) or holding (4xxxx) register. The range depends upon the registers supported in the selected
controller type.
The Zero Scale Raw Input specifies the minimum raw input value. Valid values are -32768 to
32767. This value must be less than the full-scale raw input.
The Full Scale Raw Input specifies the maximum raw input value. Valid values are -32768 to
32767. This value must be greater than the zero scale raw input.
The Zero Scale Output is the floating-point value calculated when the input is equal to the zero
scale raw input. This value must be less than the full-scale output. Valid values are any floating-point
number.
The Full Scale Output is the floating-point value calculated when the input is equal to the full-scale
raw input. This value must be greater than the zero scale output. Valid values are any floating-point
number.
The Output Deadband is the amount by which the output must change for the scaled value
changed output to be energized. Valid values are any floating-point number greater than or equal to
0.0.
Notes
The input is scaled using this formula.
scaled =
input − zero _ raw
× ( full _ output − zero _ output ) + zero _ output
full _ raw − zero _ raw
The previous scaled value changes only when difference between the current and previous values is
greater than the deadband. The scaled value changed output is energized when this occurs.
The input register may contain values less than the zero scale raw input or greater than the full-scale
raw input. The scaling calculation is still performed.
TelePACE Ladder Logic Function Reference
February 19, 2007
144
Example
In this example a SCAL block is used to convert an analog input into engineering units and close a
contact each time a change of 10 units occurs.
40020
SCAL
40030
00012
The element configuration for the SCAL block is as follows
Parameter
Input Register
Value
30001
Zero Scale Raw Input
Full Scale Raw Input
Zero Scale Output
Full Scale Output
0
32767
0
1000
Output Deadband
10
TelePACE Ladder Logic Function Reference
February 19, 2007
Notes
assign to analog input module in register
assignment
minimum value for unipolar analog input
maximum value for analog input
corresponds to the minimum value of analog input
corresponds to the maximum value of analog
input
change in output to turn on change output
145
2.62
Shunts
Horizontal
The horizontal shunt conducts power from left to right.
input
output = input
Vertical
The vertical shunt conducts power between rows. If any of the rows connected by vertical shunts are
powered, all output rows will be powered, as shown in the example below.
input = ON
output = ON
input = OFF
output = ON
TelePACE Ladder Logic Function Reference
February 19, 2007
146
2.63
SLP – Put Controller into Sleep Mode
Description
The SLP function places the controller into sleep mode. Sleep mode reduces power consumption to a
minimum by halting the microprocessor clock and shutting down the power supply. All programs
halt until the controller resumes execution. All output points turn off while the controller is in sleep
mode.
This function is not supported in the SCADAPack 32, SCADAPack 100 or SCADASense Series
controllers.
ON = enter sleep mode
clock alarm
settings
copy of input 1
SLP
wake src
Function Variables
Variable
clock alarm
settings
Valid Types
holding register (4xxxx)
wake src
holding register (4xxxx)
Description
Address of the first register in the clock alarm
settings block. There are 4 registers in the
block at addresses settings+0 to settings + 3
+0 = type
+1 = hour
+2 = minute
+3 = second
Valid values for type are
0 = no alarm
1 = absolute time alarm
2 = elapsed time alarm
address of the wake up source register. This
register indicates the reason the controller left
sleep mode. Valid values are:
1 = real time clock alarm
2 = interrupt input
4 = led power switch
8 = counter 0 overflow
16 = counter 1 overflow
32 = counter 2 overflow
256 = Assertion of:
- digital input 0 for SCADAPack 350
- Any digital input on SCADAPack LP
- INT/Cntr digital Input on SCADAPack
with 5203/5204 controller board
TelePACE Ladder Logic Function Reference
February 19, 2007
147
Notes
The SCADAPack 32 and SCADAPack 100 controllers do not support the SLP function
Note that this function block triggers the same interrupt as the CNFG Real Time Clock and Alarm
register assignment. Using both alarm settings, therefore, in the same program is not recommended.
Element Configuration
This element is configured using the SLP Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
Valid values for the time parameters are listed in the table below.
Alarm Type
Absolute
Elapsed
Parameter
Hours
Minutes
Seconds
Hours
Minutes
Seconds
Range
0 to 23
0 to 59
0 to 59
0 to 23
0 to 1439
0 to 65535
Total of all time must be less than 23 hours, 59 minutes, 59
seconds
The controller will wake up under the following conditions.
Condition
Hardware Reset
External Interrupt
Real Time Clock
Alarm
LED Power Button
Wake Up Effects
Application programs execute from
start of program.
Program execution continues from
point sleep function was executed.
Program execution continues from
point sleep function was executed.
Program execution continues from
point sleep function was executed.
TelePACE Ladder Logic Function Reference
February 19, 2007
148
Condition
Hardware Counter
Rollover
Wake Up Effects
Software portion of counter is
incremented.
Program execution continues from
point sleep function was executed.
Example
The following network will put the controller into sleep mode. The clock alarm is set to wake the
controller in 60 seconds. Other conditions may wake up the controller before the 60 seconds expires.
network 1:
10001
+2
0
0
60
42001
42001
42002
42003
42004
SLP
42100
PUTU
+1
PUTU
+1
PUTU
+1
PUTU
+1
The Element Configuration dialog may be used to edit the configuration of the SLP block, instead
of PUTU functions. This reduces the memory used by the program. However, the alarm settings are
written to the controller only when the program is loaded. The network using the PUTU elements
configures the alarm settings on every execution of the SLP element.
network 1:
10001
42001
SLP
42100
TelePACE Ladder Logic Function Reference
February 19, 2007
149
2.64
SQRF - Square Root of Floating-Point Value
Description
The SQRF element stores the square root of a floating-point register or constant in a floating-point
holding register.
When the enable input is ON the square root of the source is stored in the result floating-point
holding register. The top output is ON when the input is. The bottom output is ON if the source is
negative, and the input is ON.
ON = enable
source
copies status of input
SQRF
result
ON if source < 0
Function Variables
The element has two parameters.
Variable
source
result
Valid Types
FP constant
2 input registers
(3xxxx)
2 holding registers (4xxxx)
2 holding registers (4xxxx)
Description
a floating-point register or constant
Floating-point square root of source
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number. Floating point numbers can represent positive or negative values in the range –
3.402 × 1038 to 3.402 × 1038.
The square root of a negative number cannot be calculated. The source must be positive or zero to
calculate a result..
Related Functions
DIV – Divide Signed Values
DIVU – Divide Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
150
Example
network 1:
+155.230
SQRF
40001
The SQRF function in network 1 takes the square root of the floating-point constant +155.23 and
puts the result in floating-point register 40001 (registers 40001 and 40002). The value in 40001 is
=12.459.
TelePACE Ladder Logic Function Reference
February 19, 2007
151
2.65
STOF - Signed Integer to Floating-Point
Description
The STOF element converts a signed register or constant into a floating-point number and stores the
result in a floating-point holding register.
When the enable input is ON, value is converted into a floating-point number and stored in the
result floating-point register. The element output is ON when the input is.
ON = enable
value
copies status of input
STOF
result
Function Variables
The element has two parameters.
Variable
Value
Result
Valid Types
Constant
(–32768…32767)
input register (3xxxx)
holding register (4xxxx)
2 holding registers (4xxxx)
Description
Signed value to convert
Converted floating-point value
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number.
Floating point numbers can represent positive or negative values in the range –3.402 × 1038 to 3.402
× 1038.
Related Functions
UTOF - Unsigned Integer to Floating-Point
FTOS - Floating-Point to Signed Integer
FTOU - Floating-Point to Unsigned Integer
TelePACE Ladder Logic Function Reference
February 19, 2007
152
Example
network 1:
-2445
STOF
40001
The STOF function in network 1 converts signed integer constant -2445 to a floating-point value and
puts the value into floating point-register 40001 (registers 40001 and 40002). In this example the
content of floating-point register 40001 is the floating-point value –2445.00.
TelePACE Ladder Logic Function Reference
February 19, 2007
153
2.66
SUB – Subtract Signed Values
Description
The SUB function block subtracts a signed register or constant, value 2, from a signed register or
constant, value 1, and stores the result in a holding register, result. Signed subtraction is used. The
result out of range output is enabled if the result is greater than 32767 or less than -32768.
ON = enable SUB
value 1
copies status of input1
value 2
ON = result out of range
SUB
difference
Function Variables
Variable
value 1
value 2
Difference
Valid Types
Constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
Constant
(-32768..32767)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
Signed value to subtract from
Signed value to subtract
Difference = value 1 - value 2
Related Functions
SUBF – Subtract Floating-Point Values
SUBU –Subtract Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
154
Example
network 1:
41822
( )
41824
02561
SUB
41886
The SUB function in network 1 subtracts the contents of register 41824, value 2, from the contents
of register 41822, value 1. The difference is stored in register 41886. Some examples of different
values for registers 41822 and 41824 are shown in the table below.
Example 1
Example 2
Example 3
Register
41822
value 1
-27765
3276
-30000
TelePACE Ladder Logic Function Reference
February 19, 2007
Register
41824
value 2
-18755
-12269
27881
Register
41886
difference
-9010
15545
7655
Coil
02561
out of range
OFF
OFF
ON
155
2.67
SUBF – Subtract Floating-Point Values
Description
The SUBF element subtracts one floating-point register or constant from another and stores the result
in a floating-point holding register.
When the enable input is ON the difference value 1 – value 2 is stored in the difference holding
register. The element output is ON when the input is.
ON = enable
value1
copies status of input
value2
SUBF
difference
Function Variables
The element has three parameters.
Variable
value1
Value2
Difference
Valid Types
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
FP constant
2 input registers (3xxxx)
2 holding registers (4xxxx)
2 holding registers (4xxxx)
Description
Floating-point register or constant to subtract
from
floating-point register or constant to subtract
floating-point difference = value1 – value2
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number.
Floating point numbers can represent positive or negative values in the range –3.402 × 1038 to 3.402
× 1038.
Related Functions
SUB – Subtract Signed Values
SUBU –Subtract Unsigned Values
TelePACE Ladder Logic Function Reference
February 19, 2007
156
Example
network 1:
40001
+101.3
SUBF
40100
The SUBF function in network 1 subtracts floating-point constant +101.3 from floating-point
register 40001 (registers 40001 and 40002). Assuming floating-point register 40001 contains a value
of 1000.00 the result is +898.7. The result is stored in floating-point register 40100 (registers 40100
and 40101).
TelePACE Ladder Logic Function Reference
February 19, 2007
157
2.68
SUBR - Start of Subroutine
Description
The SUBR element defines the start of a subroutine.
A subroutine is a group of logic networks that can be executed conditionally. The subroutine begins
with the network containing the SUBR element. A subroutine ends when another subroutine element
is encountered, or when the end of the ladder logic program is reached.
The element is a single cell element. Visually it covers the entire width of the first row of the
network.
SUBR
number
Function Variables
The SUBR element has one parameter:
Variable
number
Valid Types
Constant
Description
The number of the subroutine. Any number in the range 1 to
500 is valid.
Notes
The SUBR element must be located in row 1, column 1 of a network.
No other element can be located to the right of the SUBR element.
Outputs of a subroutine remain in their last state when a subroutine is not called. For example, a coil
that is turned on by a subroutine remains on when the subroutine is not called. The output will only
turn off when the subroutine is called and it turns the output off.
The subroutine number is a constant. Constant tag names are used with this value.
The subroutine number must be unique. No other subroutine can use the same number.
Subroutines do not have to be programmed in any particular numerical order. For example,
subroutine 1 can follow subroutine 2, subroutine 200 can follow subroutine 400.
Related Functions
CALL - Execute Subroutine
Example
See the example for the CALL function.
TelePACE Ladder Logic Function Reference
February 19, 2007
158
2.69
SUBU –Subtract Unsigned Values
Description
The SUBU function block subtracts an unsigned register or constant, value 2, from an unsigned
register or constant, value 1, and stores the result in a holding register, difference. Unsigned
subtraction is used. The result out of range output is enabled if the result is greater than 65535 or
less than 0.
ON = enable SUBU
value 1
copies status of input1
value 2
ON = result out of range
SUBU
difference
Variable
value 1
Value 2
Difference
Valid Types
Constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
Constant (0..65535)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
Unsigned value to subtract from
Unsigned value to subtract
Difference = value 1 - value 2
Related Functions
SUB – Subtract Signed Values
SUBF – Subtract Floating-Point Values
Example
n e tw o rk 1 :
49920
(
42992
)
02011
SUBU
44996
TelePACE Ladder Logic Function Reference
February 19, 2007
159
The SUBU function in network 1 subtracts the contents of register 42992, value 2, from the contents
of register 49920, value 1. The difference is stored in register 44996. Some examples of different
values for registers 49920 and 42992 are shown in the table below.
Example 1
Example 2
Example 3
Register
49920
value 1
22675
61223
3877
TelePACE Ladder Logic Function Reference
February 19, 2007
Register
42992
value 2
1988
2399
54440
Register
44996
Difference
20687
58824
14973
Coil
02011
out of range
OFF
OFF
ON
160
2.70
Timers
Description
The three timer functions measure elapsed time and save it in a holding register, accumulator. The
T1 timer measures time in 1.0 second intervals. The T.1 timer measures time in 0.1 second intervals.
The T.01 timer measures time in 0.01 second intervals.
When the enable timer input is ON and the accumulate time is ON the accumulator increments by
the Timer interval to the value of the limit. When the enable timer is off the accumulator is reset to
zero.
When the enable timer is ON and the accumulator equals the limit then the accumulator = limit
output is On.
When the enable timer is ON and the accumulator is less than the limit then the accumulator <
limit output is On.
ON = accumulate time
limit
ON = accumulator = limit
ON = enable timer
OFF = reset timer to 0
T1
accumulator
ON = accumulator < limit
Variable
Limit
Valid Types
Constant (1..65535)
input register (3xxxx)
holding register (4xxxx)
Description
Upper limit for accumulator
Accumulator
Holding register (4xxxx)
Register holds time during which
accumulate time input has been ON
Example
n e tw o rk 1 :
+5
10009
01257
(
)
00017
T .1
41050
+10
(
)
01257
T .1
00017
41051
In network 1 two Timer functions are configured such that output coil 00017 is ON for 1.0 second
(10 * 0.1) and OFF for 0.5 second (5 * 0.1).
When power is applied to the circuit by closing contacts 10009, output coil 00017 is OFF and Timer
41050 starts to accumulate time. When the accumulator reaches the limit of 5, output coil 00017
turns ON. Timer 41051 is enabled by the NO contacts of output coil 00017 and starts to accumulate
TelePACE Ladder Logic Function Reference
February 19, 2007
161
time. When the accumulator reaches the limit of 10, output coil 01257 turns ON and resets Timer
41050 by the NC contacts of 01257. Output coil 00017 turns OFF. The process is then repeated until
contacts 10009 are opened.
TelePACE Ladder Logic Function Reference
February 19, 2007
162
2.71
TOTL – Analog Totalizer
Description
The TOTL function reads a rate input and accumulates (integrates) a total. It is used to measure a
flow rate and accumulate a volume, or a similar calculation.
When the Accumulate input is ON and it has been longer than the sample interval since the last
accumulation, the function reads the value of the input, scales it by time difference from the previous
accumulation, and adds it into the total.
When the Log Data input goes from OFF to ON, the accumulated total, accumulation time, and the
time at the end of the period is saved in the history registers. Older history is pushed down and the
oldest record is discarded.
When the Enable Accumulation input is ON, accumulation is enabled. When the input is OFF, all
accumulators and outputs are set to zero.
The Error output is ON if there is an error in the configuration registers.
ON = accumulate
config
copies state of input 1
OFF to ON = log data
outputs
ON = error
ON = enable accumulation
OFF = clear outputs
TOTL
records
Function Variables
Variable
Config
Valid Types
holding register (4xxxx)
TelePACE Ladder Logic Function Reference
February 19, 2007
Description
Address of the first register in the configuration
block. There are 3 registers in the block at
addresses message+0 to message+2.
+0 = rate input register
+1 = input rate (see table below)
+2 = sample interval (tenths of seconds)
163
Variable
Outputs
Records
Valid Types
holding register (4xxxx)
Constant
Description
Address of the first register of the output block.
There are 10 to 214 registers in the block at
outputs+0 to outputs+213. The number of registers
used depends on the records variable.
+0 = number of records to follow
+1 = status
+2,3 = internal: time at last sample
+4,5 = period 1: total (float)
+6,7 = period 1: end time
+8,9 = period 1: accumulation time
+10,11= period 2: total (float)
+12,13 = period 2: end time
+14,15 = period 2: accumulation time
+16,17= period 3: total (float)
+18,19 = period 3: end time
+20,21 = period 3: accumulation time
…
+208,209 = period 35: total (float)
+210,211 = period 35: end time
+212,213 = period 35: accumulation time
The number of measurement records stored in the
output array. The valid values are 1 to 35. This
value determines the number of output registers
used by the function.
Element Configuration
This element is configured using the TOTL Element Configuration dialog. Highlight the element by
moving the cursor over the element and then use the Element Configuration command on the Edit
menu to modify the configuration block.
WARNING:
If the controller is initialized, using the Initialize command in the Controller menu,
all I/O database registers used for Element Configuration are set to zero. The
application program must be re-loaded to the controller.
The Input Register specifies the register address from which the rate input is read. Valid value for
this register is any floating point register. The function will use the specified register, and the next
TelePACE Ladder Logic Function Reference
February 19, 2007
164
sequential register, as a floating point rate value. The address range depends upon the registers
supported in the selected controller type.
The Rate Units specifies the units of time for the rate input. It may be one of the following.
per second (holding register = 0)
per minute (holding register = 1)
per hour (holding register = 2)
per day (holding register = 3)
The Sample Interval specifies the interval at which the rate input will be sampled. A sample is taken
and a calculation performed if the time since the last sample is greater than or equal to the sample
interval. The exact time depends on the scan time of the logic program. The valid values are 0.1 to
6553.5 seconds (1 to 65535 tenths of a second). The dialog shows the value in seconds; the register
contains an integer value in tenths of seconds.
Output Registers
The output registers store the results of the accumulation and act as internal workspace for the
accumulation.
The Number of Records register indicates how many sets of total and time registers follow. This
value is equal to the Records variable. There are six registers in each record.
The status register indicates the status of the accumulation. It can have the following values. If the
status register is non-zero, the error output is turned ON.
Status
0
1
2
Description
no error
invalid rate units configuration
invalid sample interval
The function block uses the two internal registers. The registers are not intended for use in a ladder
logic program.
The Period n: Total is stored as a floating-point number in two consecutive registers.
The Period n: End Time is stored as a 32-bit integer in two consecutive registers. The registers hold
the number of seconds since January 1, 1970. This is an unsigned number.
The Period n: Accumulation is stored as a 32-bit integer in two consecutive registers. The register
holds the number of seconds accumulation occurred in the period. This measures the time the
Accumulate input is ON, including times when the rate was zero.
Notes
The accumulated value is a floating-point number. All floating-point numbers are approximations. If
the accumulated value grows large, then low rate inputs will have little or no effect on the
accumulated value and the accumulated value will not be accurate. Use the Log Data input to save
the accumulated value and start a new accumulation when the accumulated value grows large.
The Log Data input must be triggered at a suitable rate or the accumulator will overflow, and the
accumulated value will not be accurate.
TelePACE Ladder Logic Function Reference
February 19, 2007
165
Related Functions
FLOW – Flow Accumulator
Example
In this example a TOTL function is used to read a flow rate from an analog input and accumulate 14
days of data. The analog input measures a flow rate in gallons per minute.
network 1
40001
40100
10009
TOTL
14
The TOTL function in network 1 has the Accumulate and Enable Accumulation inputs connected
to the left power rail. When these inputs are continuously powered the TOTL function accumulates
totals.
The Records variable is set to 14. This means 14 sets of history registers (total, flow time and end of
period time) will be logged. In this example the accumulation input is never turned off meaning that
once 14 sets of history registers are saved the next time contact 10009 is closed the 14th record is
removed and the newest record is added to the history.
Each time contact 10009 is closed it powers the log data input. The accumulated total, accumulation
time and the time at the end of the period is saved in the history registers. The contact should be
closed by another network once per day for this example.
The element configuration for the TOTL block is as follows
Parameter
Input Register
Value
42000
Rate Units
per
minute
10
Sample Interval
TelePACE Ladder Logic Function Reference
February 19, 2007
Notes
The register that contains the rate input. This is a floating
point value contained in register 42000 and 42001.
The value in floating point register 42000 represents the
flow rate in units/minute
sample, calculate, and accumulate approximately every
10.0 seconds
166
2.72
UCTR – Up Counter
Description
The UCTR function block increments (adds one to) the value in the counter register when the
increment count input changes from OFF to ON. The counter stops counting when the limit register
or constant is reached.
When the counting enabled input is ON and the increment count changes from OFF to ON the
counter value increments by one. When the counting enabled input is OFF the counter is reset to
zero.
When the counting enabled input is ON and the counter equals the limit then the counter = limit
output is ON.
When the counting enabled input is ON and the counter is less than the limit then the counter <
limit output is ON.
OFF to ON = increment count
ON = counting enabled
OFF = reset counter to 0
Variable
Limit
Counter
limit
ON = counter = limit
UCTR
counter
ON = counter < limit
Valid Types
constant (1..65535)
input register (3xxxx)
holding register (4xxxx)
holding register (4xxxx)
Description
Upper limit for counter
Register holds current counter value
Related Functions
DCTR – Down Counter
TelePACE Ladder Logic Function Reference
February 19, 2007
167
Example
n e tw o rk 1 :
+1
01057
(
)
01057
T .1
46770
01057
01058
100
(
)
01058
UCTR
45776
The UCTR function in network 1 increments each time the timer output is enabled. The timer limit is
0.1 seconds and it will take 10 seconds for the UCTR to increment 100 times.
When the timer limit is reached after 0.1 seconds the output coil 01057 is energized. NC contact
01057 will open resetting the timer and NO contact 01057 will close incrementing the UCTR.
When the UCTR increments to 100 output coil 01058 is energized. NC contacts 01058 will open and
the UCTR will reset counter to zero. This will happen every 10 seconds.
TelePACE Ladder Logic Function Reference
February 19, 2007
168
2.73
UTOF - Unsigned Integer to Floating-Point
Description
The UTOF element converts an unsigned register or constant into a floating-point number and stores
the result in a floating-point holding register.
When the enable input is ON, value is converted into a floating-point number and stored in the
result floating-point register. The element output is ON when the input is.
ON = enable
value
copies status of input
UTOF
result
Function Variables
The element has two parameters.
Variable
value
result
Valid Types
Constant (0…65535)
input register (3xxxx)
holding register (4xxxx)
2 holding registers (4xxxx)
Description
Unsigned value to convert
Converted floating-point value
Notes
Floating-point values are stored in two consecutive I/O database registers. The lower numbered
register contains the upper 16 bits of the number. The higher numbered register contains the lower 16
bits of the number.
Floating point numbers can represent positive or negative values in the range –3.402 × 1038 to 3.402
× 1038.
Related Functions
STOF - Signed Integer to Floating-Point
FTOS - Floating-Point to Signed Integer
FTOU - Floating-Point to Unsigned Integer
TelePACE Ladder Logic Function Reference
February 19, 2007
169
Example
network 1:
+2233
UTOF
40100
The UTOF function in network 1 converts unsigned constant +2233 to a floating-point number and
puts the value into register 40100. In this example the content of floating point-register 40100
(registers 40100 and 40101) is 2233.00.
TelePACE Ladder Logic Function Reference
February 19, 2007
170
2.74
XOR – Exclusive Or Block
Description
The XOR function block logically EXCLUSIVE-ORs the source block of registers with the
destination block of registers and stores the result in the destination block of registers.
ON = enable XOR
source
copies status of input1
destination
XOR
size
Variable
Source
Destination
Size
Valid Types
coil block (0xxxx)
status block (1xxxx)
input register (3xxxx)
holding register (4xxxx)
coil block (0xxxx)
holding register (4xxxx)
constant (1..100)
Description
The first register in the first source block.
The address for a coil or status register block is
the first register in a group of 16 registers that
will be EXCLUSIVE-ORed.
The first register in the second source block and
destination block.
The address for a coil register block is the first
register in a group of 16 registers that will be
EXCLUSIVE-ORed.
The number of 16 bit words in the block.
Notes
Exclusive-or accesses 16 bit words. Coil and status register blocks are groups of 16 registers that
start with the register specified as the block address. A block size of 2 corresponds to 32 coils, or two
holding registers.
Coil and status register blocks must begin at the start of a 16 bit word within the controller memory.
Suitable addresses are 00001, 00017, 10001, 10033, etc.
Related Functions
AND – And Block
NOT – Not Block
OR – Or Block
TelePACE Ladder Logic Function Reference
February 19, 2007
171
Example
network 1:
11000
01026
XOR
1
In this example the source block has a value of 1521310 (11101101101101). The destination register
has a value of 2237910 (101011101101011) before the XOR function and a value of 2765410 after the
XOR function.
source register
0 0 1 1 1 0 1 1 0 1 1 0 1 1 0 1
destination register
before XOR
0 1 0 1 0 1 1 1 0 1 1 0 1 0 1 1
destination register
afterXOR
0 1 1 0 1 1 0 0 0 0 0 0 0 1 1 0
TelePACE Ladder Logic Function Reference
February 19, 2007
172
TelePACE Ladder Logic
Register Assignment Reference
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE,
TeleSAFE Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus,
SCADAPack 32, SCADAPack 32P, SCADAPack 350, SCADAPack LP,
SCADAPack 100, SCADASense 4202 DS, SCADASense 4202 DR,
SCADASense 4203 DS, SCADASense 4203 DR, SCADASense 4102,
SCADASense 4012, SCADASense 4032 and TeleBUS are registered
trademarks of Control Microsystems.
All other product names are copyright and registered trademarks or trade names
of their respective owners.
Material used in the User and Reference manual section titled SCADAServer
OLE Automation Reference is distributed under license from the OPC
Foundation.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
1
Table of Contents
1
REGISTER ASSIGNMENT REFERENCE ..................................................... 5
1.1
Register Assignment Specification................................................................. 7
1.2
Register Assignment Example ....................................................................... 8
1.3
Analog Input I/O Modules............................................................................. 10
1.3.1
AIN Controller RAM Battery V................................................................. 11
1.3.2
AIN Controller temperature ..................................................................... 12
1.3.3
AIN 5501 Module .................................................................................... 13
1.3.4
AIN 5502 Module .................................................................................... 14
1.3.5
AIN 5503 Module .................................................................................... 15
1.3.6
AIN 5504 Module .................................................................................... 16
1.3.7
AIN 5505 Module .................................................................................... 17
1.3.8
AIN 5506 Module .................................................................................... 21
1.3.9
AIN 5521 Module .................................................................................... 25
1.3.10
AIN Generic 8 Point Module ................................................................... 26
1.4
Analog Output I/O Modules.......................................................................... 27
1.4.1
AOUT 5301 Module ................................................................................ 28
1.4.2
AOUT 5302 Module ................................................................................ 29
1.4.3
AOUT 5304 Module ................................................................................ 30
1.4.4
AOUT Generic 2 Point Module ............................................................... 31
1.4.5
AOUT Generic 4 Point Module ............................................................... 32
1.5
Configuration I/O Modules ........................................................................... 33
1.5.1
CNFG Clear Protocol Counters .............................................................. 34
1.5.2
CNFG Clear Serial Port Counters........................................................... 35
1.5.3
CNFG DTR Off ....................................................................................... 36
1.5.4
CNFG 5904 HART Interface Module ...................................................... 37
1.5.5
CNFG IP Settings ................................................................................... 39
1.5.6
CNFG LED Power Settings..................................................................... 41
1.5.7
CNFG Modbus IP Interface .................................................................... 43
1.5.8
CNFG Modbus IP Protocols.................................................................... 45
1.5.9
CNFG Modbus/TCP Settings.................................................................. 47
1.5.10
CNFG PID Control Block ........................................................................ 49
1.5.11
CNFG Power Mode ................................................................................ 51
1.5.12
CNFG Protocol Settings Method 1.......................................................... 52
1.5.13
CNFG Protocol Settings Method 2.......................................................... 54
1.5.14
CNFG Protocol Settings Method 3.......................................................... 56
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
2
1.5.15
1.5.16
1.5.17
1.5.18
CNFG Real Time Clock and Alarm ......................................................... 59
CNFG Save Settings to EEPROM .......................................................... 61
CNFG Serial Port Settings ...................................................................... 62
CNFG Store and Forward ....................................................................... 64
1.6
Counter I/O Modules .................................................................................... 66
1.6.1
CNTR Controller Counter Inputs............................................................. 67
1.6.2
CNTR Controller Interrupt Input .............................................................. 68
1.6.3
CNTR 5410 input module ....................................................................... 69
1.7
Diagnostic I/O Modules ................................................................................ 70
1.7.1
DIAG Controller Status Code.................................................................. 71
1.7.2
DIAG DNP Connection Status ................................................................ 73
1.7.3
DIAG DNP Event Status Module ............................................................ 74
1.7.4
DIAG DNP Port Status Module ............................................................... 76
1.7.5
DIAG DNP Station Status ....................................................................... 78
1.7.6
DIAG Force............................................................................................. 80
1.7.7
DIAG IP Connections.............................................................................. 81
1.7.8
DIAG Logic Status .................................................................................. 82
1.7.9
DIAG Modbus Protocol Status ................................................................ 83
1.7.10
DIAG Serial Port Comm. Status.............................................................. 85
1.7.11
DIAG Serial Port Protocol Status ............................................................ 87
1.8
Digital Input I/O Modules.............................................................................. 89
1.8.1
DIN Controller Digital Inputs ................................................................... 90
1.8.2
DIN Controller Interrupt Input.................................................................. 91
1.8.3
DIN Controller Option Switches .............................................................. 92
1.8.4
DIN SCADAPack 32 Option Switches .................................................... 93
1.8.5
DIN 5401 Module.................................................................................... 94
1.8.6
DIN 5402 Module.................................................................................... 95
1.8.7
DIN 5403 Module.................................................................................... 97
1.8.8
DIN 5404 Module.................................................................................... 98
1.8.9
DIN 5405 Module.................................................................................... 99
1.8.10
DIN 5421 Module.................................................................................. 101
1.8.11
DIN Generic 16 Point Module ............................................................... 102
1.8.12
DIN Generic 8 Point Module ................................................................. 104
1.9
Digital Output I/O Modules ......................................................................... 105
1.9.1
DOUT 5401 Module.............................................................................. 106
1.9.2
DOUT 5402 Module.............................................................................. 107
1.9.3
DOUT 5406 Module.............................................................................. 108
1.9.4
DOUT 5407 Module.............................................................................. 109
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
3
1.9.5
1.9.6
1.9.7
1.9.8
1.9.9
DOUT 5408 Module.............................................................................. 110
DOUT 5409 Module.............................................................................. 111
DOUT 5411 Module.............................................................................. 112
DOUT Generic 16 Point Module ........................................................... 114
DOUT Generic 8 Point Module ............................................................. 116
1.10 SCADAPack and SCADASense Series I/O Modules ................................. 117
1.10.1
4202 DR Extended/4203 DR IO............................................................ 118
1.10.2
4202 DR I/O.......................................................................................... 120
1.10.3
4202/4203 DS I/O ................................................................................. 122
1.10.4
SCADAPack AOUT Module.................................................................. 124
1.10.5
SCADAPack 5601 I/O Module .............................................................. 126
1.10.6
SCADAPack 5602 I/O Module .............................................................. 129
1.10.7
SCADAPack 5604 I/O Module .............................................................. 132
1.10.8
SCADAPack 5606 I/O Module .............................................................. 138
1.10.9
SCADAPack LP I/O .............................................................................. 143
1.10.10 SCADAPack 100 I/O............................................................................. 147
1.10.11 SCADAPack 350 I/O............................................................................. 149
1.11 Controller Default Register Assignments ................................................... 153
1.11.1
4202 DR Extended/4203 DR I/O Register Assignment......................... 154
1.11.2
SCADASense 4202/4203 DS I/O Default Register Assignment ........... 155
1.11.3
Micro16 Default Register Assignment (Backwards Compatible Modules)156
1.11.4
Micro16 Default Register Assignment (Controller I/O Only).................. 161
1.11.5
SCADAPack (5601 I/O Module) Default Register Assignment ............. 162
1.11.6
SCADAPack (5604 I/O Module) Default Register Assignment ............. 163
1.11.7
SCADAPack LIGHT Default Register Assignment................................ 164
1.11.8
SCADAPack PLUS (5601 I/O Module) Default Register Assignment ... 165
1.11.9
SCADAPack Plus (5604 I/O Module) Default Register Assignment ..... 166
1.11.10 SCADAPack LP Default Register Assignment...................................... 167
1.11.11 SCADAPack 350 Default Register Assignment .................................... 168
1.11.12 SCADAPack 32 (5601 I/O Module) Default Register Assignment ........ 169
1.11.13 SCADAPack 32 (5604 I/O Module) Default Register Assignment ........ 170
1.11.14 SCADAPack 32P Default Register Assignment.................................... 171
1.11.15 SCADAPack 100 Default Register Assignment .................................... 172
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
4
1
Register Assignment Reference
A complete description of each I/O Module in the Register Assignment is presented in this reference.
The I/O modules are divided into classes that group similar modules together for ease of reference.
All I/O hardware that is used by the controller must be assigned to I/O database registers in order for
the I/O data to be used by the ladder program. Ladder logic programs may read data from, or write
data to the I/O hardware through user-assigned registers in the I/O database.
Register assignments are stored in the user configured Register Assignment and are downloaded with
the ladder logic application program.
The Register Assignment assigns I/O database registers to user-assigned registers using I/O Modules.
An I/O Module can refer to an actual I/O hardware module (e.g. 5401 Digital Input Module) or it
may refer to a set of controller parameters, such as serial port settings.
Analog Input (AIN)
These modules are used to assign data from physical analog inputs to input registers in the I/O
Database. The physical analog inputs are specific 5000 Series I/O modules, generic I/O modules, and
internal controller data such as RAM battery voltage and board temperature.
Note: To properly view analog input/output registers, the register type should be set to type signed.
Setting the register type to anything else may result in inaccurate readings being
displayed/written to these registers.
Analog Output (AOUT)
These modules are used to assign data from the I/O Database to physical analog outputs. The
physical analog outputs are specific 5000 Series I/O modules or generic I/O modules.
Note: To properly view analog input/output registers, the register type should be set to type signed.
Setting the register type to anything else may result in inaccurate readings being
displayed/written to these registers.
Digital Input (DIN)
These modules are used to assign data from physical digital inputs to input registers in the I/O
Database. The physical digital inputs are specific 5000 Series I/O modules, generic I/O modules, and
controller digital inputs.
Digital Output (DOUT)
These modules are used to assign data from the I/O Database to physical digital outputs. The
physical digital outputs are specific 5000 Series I/O modules or generic I/O modules.
Counter Input (CNTR)
These modules are used to assign data from physical counter inputs to input registers in the I/O
Database. The physical counter inputs are specific 5000 Series I/O modules and controller counter
inputs.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
5
SCADAPack (SCADAPack 5601, SCADAPack 5602, SCADAPack 5604, and
SCADAPack AOUT)
These modules are used to assign data to registers in the I/O Database, from physical SCADAPack
digital and analog I/O. The physical inputs and outputs are specific SCADAPack I/O modules.
Controller Diagnostic (DIAG)
These modules are used to assign diagnostic data from the controller to input or status registers in the
I/O Database. The diagnostic data is used to monitor internal controller data such as controller status
code, the force LED, serial port communication status and serial port protocol status.
Controller Configuration (CNFG)
These modules are used to assign data from I/O Database coil and holding registers to controller
configuration registers. The configuration data is used to configure controller settings such as
clearing protocol and serial counters, real time clock settings, HART protocol interface and PID
control blocks.
Default Register Assignment
This provides a default assignment of registers for the selected controller type.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
6
1.1
Register Assignment Specification
The Register Assignment I/O modules described in this manual are formatted as follows.
Header
The module header displays the I/O module name.
Module Description
The module description section describes the function, data origin and data destination of the I/O
module.
Register Assignment
The register assignment description is used to describe the information required in the Add Register
Assignment dialog. The information required for each section of the Add Register Assignment
dialog is explained in the table shown below.
The column at the left of the table indicates the information that is required for the I/O module in the
Add Register Assignment dialog. The requirements vary depending on the I/O module.
Module
Module Name
Address
End
Physical I/O modules are assigned a unique
module address between 0 and 15. No
other similar type modules may use this
module address.
Diagnostic and configuration modules and
SCADAPack 5601, 5602 and 5604 I/O
modules do not require a physical address.
Register type of 0xxxx, 1xxxx, 3xxxx or
4xxxx.
First register of any unused
3xxxx
block of consecutive registers.
Last register of block
3xxxx + 7
Registers
Number of registers for module.
Description
Description of module.
Extended Parameters
Additional parameters, if applicable.
Type
Start
Register Data
The register data table describes what data each assigned register will contain.
Notes Section
The notes section is used to provide any additional information that may be useful when using the
module.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
7
1.2
Register Assignment Example
In this example, the application program requires a 5501 Analog Input module. The analog input
data from the 5000 Series 5501 module must be assigned to the I/O Database before the Ladder
Logic application program can access it. The register assignment is used to assign the input data to
the I/O database.
Run the TelePACE program.
Select File from the menu bar. From the drop down File menu, select New.
Select Controller from the menu bar. From the drop down Controller menu, select Register
Assignment.
The Register Assignment is displayed. The table is initially empty when a new file is started.
Selecting the Add button opens the Add Register Assignment dialog.
The first I/O module in the I/O module list is displayed and highlighted in the Module window.
Click the left mouse button on the down arrow at the left side of the Module window.
The entire I/O module list is displayed in the drop down window. Use the up and down arrows at the
right side of the list to scroll through the list of I/O modules.
Select the AIN 5501 module by clicking the left mouse button on the AIN 5501 module text. When
selected the AIN 5501 module is highlighted and the module list is closed.
The AIN 5501 module is described in the Register Assignment section of this manual.
The module reference for the AIN module is described in detail below. Each section of the module
reference provides information that is required to configure the register assignment. All modules in
the Register Assignment follow a similar format.
Header
The module header displays the I/O module name. For example, AIN 5501 Module is displayed.
Module Description
The module description section describes the function, data origin and data destination of the I/O
module. The description for the AIN 5501 module indicates that data is received from the 5501
Analog Input module. This data is then assigned to eight consecutive input (3xxxx) registers in the
I/O database. The I/O database registers used by the AIN 5501 module are continuously updated
with data from the 5000 Series 5501 analog input module.
Register Assignment Description
The register assignment description is used to describe the information required in the Add Register
Assignment dialog. The information required for each section of the Add Register Assignment
dialog is explained in the table. A sample is shown below.
Module
Address
Type
AIN 5501 Module
This module is assigned a unique module
address between 0 and 15. No other AINtype module may use this module address.
Input Register
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
8
Start
End
Registers
Description
Extended Parameters
First register of any unused
block of 8 consecutive input
registers.
Last register of block
8 input registers.
None
None
3xxxx
3xxxx + 7
The column at the left of the table indicates the information that is required for the I/O module in the
Add Register Assignment dialog. The requirements vary depending on the I/O module.
Module The I/O module highlighted in the Module window.
Address The physical address of the 5000 Series 5501 analog input module. This
address is set equal to the address of 5501 analog input module. See the
5501 Analog Input Module User Manual.
Type
The I/O database register type that the I/O module will assign data to. The
I/O database register types are:
Coil Register
0xxxx
Status Register
1xxxx
Input Register
3xxxx
Holding Register 4xxxx
The AIN 5501 module will assign data to input registers (3xxxx).
Start
The I/O database register address where the AIN 5501 module begins the
register assignment. For the AIN 5501 module, this is the first of eight
consecutive input registers.
End
The I/O database register where the AIN 5501 module ends the register
assignment. This value is automatically set to Start + 8 by the AIN 5501
module.
Registers Number of I/O database registers that the AIN 5501 module assigns. This
is automatically set to 8 for the AIN 5501 module.
Description The register type description for I/O modules that assign multiple
types of registers. The AIN 5501 module does not have an entry for this
field.
Extended Parameters
None.
Register Data
The register data table describes what data each assigned register will contain. In the case of the AIN
5501 Module, the data will be the physical analog input channels from the 5000 Series 5501 module.
Notes Section
The notes section is used to provide any additional information that may be useful when using this
module.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
9
1.3
Analog Input I/O Modules
Analog input modules are used to assign data from physical analog inputs to input registers in the
I/O Database. The physical analog inputs are specific 5000 Series I/O modules, generic I/O modules,
and internal controller data such as RAM battery voltage and board temperature.
Analog input I/O modules may assign data to any input registers in the I/O database that are not
being used by another Analog Input or Counter I/O module. There are 1024 I/O database input
registers available. These input registers are numbered 30001 - 31024. Input registers are referred to
as 3xxxx registers throughout this manual.
All I/O database input registers that are not assigned to any other I/O modules may be used as
general purpose input registers in a ladder program. The I/O modules available are described in the
following pages.
Note: To properly view analog input/output registers, the register type should be set to type signed.
Setting the register type to anything else may result in inaccurate readings being
displayed/written to these registers.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
10
1.3.1
AIN Controller RAM Battery V
Description
The module, AIN Controller RAM battery V, reads the RAM backup battery voltage of the
SCADAPack controllers. This module reads the input voltage for the SCADASense programmable
controllers.( SCADASense 4202 DR, 4202 DS, 4203 DR, and 4203 DS) The voltage value is
assigned to one input register. The input register is updated continuously with voltage data read from
the RAM battery.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN Controller RAM battery V
No physical address is required.
Input Register
Any unused input register.
3xxxx
Same as start register.
1 input register
None
None
Register Data
Register Assignment
1 input register
Assignment to Module Hardware
RAM battery voltage (0-5000 millivolts for SCADAPack
controllers).
Input power voltage (0-32767 millivolts for SCADASense
Programmable Controllers.
Notes
One input register is always assigned to the I/O Database when this module is used.
The 3.6V lithium battery will return a typical value of 3600 or 3700. A reading less than 3000 (3.0V)
indicates that the lithium battery requires replacement. The RAM battery voltage resolution is 100
millivolts.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
11
1.3.2
AIN Controller temperature
Description
The module, AIN Controller temperature, reads the circuit board temperature of the 5203 or 5204
controller. The temperature data is assigned to two consecutive input registers. The input registers
are updated continuously with data read from the controller.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN Controller temperature
No physical address is required.
Input Register
First register of any unused
3xxxx
block of 2 consecutive input
registers.
Last register of block
3xxxx + 1
2 input registers.
None
None
Register Data
Register Assignment
Start Register
Start Register + 1
Assignment to Module Hardware
Board temperature (degrees C)
Board temperature (degrees F)
Notes
Two input registers are always assigned to the I/O Database when this module is used.
The temperature sensor returns a value in the range -40°C to 75°C or -40°F to 167°F. Temperatures
outside this range cannot be measured.
Refer to the System Manual for further information on the circuit board temperature.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
12
1.3.3
AIN 5501 Module
Description
The AIN 5501 module provides eight analog inputs, from the 5501 analog input module, for each
module address. Data from each module is assigned to eight consecutive input registers. The input
registers are updated continuously with data read from the analog inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN 5501 module
This module is assigned a unique module
address between 0 and 15. No other AINtype module may use this module address.
Input Register
First register of any unused
3xxxx
block of 8 consecutive input
registers.
Last register of block
3xxxx + 7
8 input registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Notes
Eight input registers are always assigned to the I/O Database when this module is used.
Refer to the 5501 Analog Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
13
1.3.4
AIN 5502 Module
Description
The AIN 5502 module provides eight analog inputs, from the 5502 analog input module, for each
module address. Data from each module is assigned to eight consecutive input registers. The input
registers are updated continuously with data read from the analog inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN 5502 module
This module is assigned a unique module
address between 0 and 15. No other AINtype module may use this module address.
Input Register
First register of any unused
3xxxx
block of 8 consecutive input
registers.
Last register of block
3xxxx + 7
8 input registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Notes
Eight input registers are always assigned to the I/O Database when this module is used.
Refer to the 5502 Analog Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
14
1.3.5
AIN 5503 Module
Description
The AIN 5503 module provides four analog inputs, from the 5503 RTD analog input module, for
each module address. Data is assigned to four consecutive input registers. The input registers are
updated continuously with data read from the analog inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN 5503 module
This module is assigned a unique module
address between 0 and 15. No other AINtype module may use this module address.
Input Register
First register of any unused
3xxxx
block of 4 consecutive input
registers.
Last register of block
3xxxx + 3
4 input registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Notes
Four input registers are always assigned to the I/O Database when this module is used.
Refer to the 5503 RTD Analog Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
15
1.3.6
AIN 5504 Module
Description
The AIN 5504 module provides eight analog inputs, from the Thermocouple analog input module,
for each module address. Data is assigned to eight consecutive input registers. The input registers are
updated continuously with data read from the analog inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN 5504 module
This module is assigned a unique module
address between 0 and 15. No other AINtype module may use this module address.
Input Register
First register of any unused
3xxxx
block of 8 consecutive input
registers.
Last register of block
3xxxx + 7
8 input registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Notes
Eight input registers are always assigned to the I/O Database when this module is used.
Refer to the 5504 Thermocouple Analog Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
16
1.3.7
AIN 5505 Module
Description
The AIN 5505 module provides four RTD analog input points from a 5505 RTD module. A
maximum of sixteen 5505 RTD modules may be installed on the I/O bus. The 5505 RTD module can
operate in Native mode or in 5503 Emulation Mode. The operating mode is determined via a DIP
switch on the 5505 RTD module. Refer to the Control Microsystems Hardware Manual for details
on the DIP switch settings for the module.
When using the 5505 RTD module in 5503 Emulation mode the AIN 5503 module is used in the
register assignment. See the AIN 5503 Module section if the module is to be used in 5503 Emulation
mode.
The 5505 RTD module native mode provides enhanced capability over the 5503 emulation mode.
The module operates in native mode if the 5503 Emulation DIP switch is open. This mode is
recommended for all new installations.
•
Each input is individually configurable for resistance measurement or RTD temperature
measurement
•
Each RTD input is configurable to return the measured temperature in degrees Celsius,
Kelvin, or Fahrenheit.
•
All inputs have a common configurable filter rate that can be used to dampen process
variations or noise.
•
The module returns diagnostic and status information for each input, such as RTD type
(3 or 4 wire), open RTD annunciation, and RTD out of range annunciation.
•
Data is returned as an IEEE 32 bit, single precision floating point number that requires no
additional scaling.
RTD data is assigned to eight consecutive input (3xxxx) registers, two for each floating point RTD
value. The input registers are updated continuously with data read from the analog inputs.
The 5505 RTD module provides 16 internal digital input (1xxxx) registers that return status and
diagnostic information about the RTDs. The digital input registers are updated continuously with
data read from the digital inputs.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
17
Register Assignment
The register assignment for the AIN 5505 module is used to configure the registers used for the
module data and the Extended Parameters available for the module. To open the register assignment
dialog for the AIN 5505 module:
•
Select Register Assignment from the Controller menu in TelePACE.
•
In the Register Assignment window select the Add button.
•
In the Add Register Assignment dialog select the AIN 5505 module from the list presented in
the Module window.
The register assignment dialog for the AIN 5505 module is shown below.
The Module selection displays the name of the 5505 RTD module used for the register assignment.
The Address selection displays the module address of the physical 5505 RTD module. The address
on the module is selected via dip switches on the module. A maximum of sixteen AIN type modules
may be added to a system.
The register type 1xxxx defines the register range for the digital input status data. Sixteen sequential
registers are needed for the AIN 5505 module status data. Any unused block of sixteen registers may
be used. See the Status Register Data section below for an explanation of the digital input status
data.
The register type 3xxxx defines the register range for the analog input data. Eight sequential registers
are needed for the AIN 5505 module analog data. Any unused block of eight registers may be used.
See the Input Register Data section below for an explanation of the analog input.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
18
The Extended Parameters grouping defines the type of data returned from the 5505 RTD module,
for each RTD input, and the filtering used by all RTD inputs.
The Type selection for each input (AIN 0, 1, 2 and 3) defines the measurement type. The data in the
input registers assigned to the input is set to the type selected.
•
The deg C selection sets the input point measurement type to degrees Celsius.
•
The deg F selection sets the input point data measurement to degrees Fahrenheit.
•
The deg K selection sets the input point data measurement to degrees Kelvin.
•
The ohms selection sets the input point data measurement as resistance measurement in ohms.
The AIN Filter selection set the input filter rate for all RTD inputs. The filter rate is used to dampen
process variations or noise.
•
The 0.5s selection sets the filter rate to 0.5 seconds.
•
The 1s selection sets the filter rate to 1 second.
•
The 2s selection sets the filter rate to 2 seconds.
•
The 4s selection sets the filter rate to 4 seconds.
Status Register Data
Status register data is assigned to sixteen consecutive status (1xxxx) registers. The following
table begins at the Start address defined in the Register Assignment and continues for
sixteen registers.
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Assignment to Module Hardware
OFF = channel 0 RTD is good
ON = channel 0 RTD is open or PWR input is off
OFF = channel 0 data in range
ON = channel 0 data is out of range
OFF = channel 0 RTD is using 3-wire measurement
ON = channel 0 RTD is using 4-wire measurement
Reserved for future use
OFF = channel 1 RTD is good
ON = channel 1 RTD is open or PWR input is off
OFF = channel 1 data in range
ON = channel 1 data is out of range
OFF = channel 1 RTD is using 3-wire measurement
ON = channel 1 RTD is using 4-wire measurement
Reserved for future use
OFF = channel 2 RTD is good
ON = channel 2 RTD is open or PWR input is off
OFF = channel 2 data in range
ON = channel 2 data is out of range
OFF = channel 2 RTD is using 3-wire measurement
ON = channel 2 RTD is using 4-wire measurement
Reserved for future use
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
19
Registers
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
OFF = channel 3 RTD is good
ON = channel 3 RTD is open or PWR input is off
OFF = channel 3 data in range
ON = channel 3 data is out of range
OFF = channel 3 RTD is using 3-wire measurement
ON = channel 3 RTD is using 4-wire measurement
Reserved for future use
Input Register Data
Input register data is assigned to eight consecutive input (3xxxx) registers. The following
table begins at the Start address defined in the Register Assignment and continues for eight
registers. Note that each input point uses two input registers formatted in IEEE 754 floating
point format.
Registers
Start Register and Start Register + 1
(in IEEE 754 floating point format)
Start Register + 2 and Start Register + 3
(in IEEE 754 floating point format)
Start Register + 4 and Start Register + 5
(in IEEE 754 floating point format)
Start Register + 6 and Start Register + 7
(in IEEE 754 floating point format)
Assignment to Module
Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Notes
Refer to the 5505 RTD Analog Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
20
1.3.8
AIN 5506 Module
Description
The AIN 5506 module provides eight analog inputs from a 5506 Analog Input module. A maximum
of sixteen 5506 analog input modules may be installed on the I/O bus. The 5506 Analog Input
module can operate in Native mode or in 5501 Emulation Mode. The operating mode is determined
via a DIP switch on the 5506 Analog Input. Refer to the Control Microsystems Hardware Manual
for details on the DIP switch settings for the module.
When using the 5506 Analog Input module in 5501 Emulation mode the AIN 5501 module is used in
the register assignment. See the AIN 5501 Module section if the module is to be used in 5501
Emulation mode.
5506 native mode provides enhanced capability over the 5501 emulation mode. The module
operates in native mode if the 5501 Emulation DIP switch is open.
•
Each input is individually configurable for 0-5V, 1-5V, 0-20mA, or 4-20mA operation.
•
Converted analog input data is returned as a signed 15-bit value, providing 8 times more
resolution than in 5501 mode. Negative values are possible, for example if a 4-20mA is
open loop.
•
The module returns status information for each analog input indicating if the analog
input is in or out of range for the defined signal type.
•
All inputs have a configurable filter rate.
•
The input-scanning rate is software configurable to 50 or 60 hertz.
Analog input data is assigned to eight consecutive input (3xxxx) registers. The input registers are
updated continuously with data read from the analog inputs.
The 5506 Analog Input module provides 8 internal digital input (1xxxx) registers that return status
information about the analog inputs. The digital input registers are updated continuously with data
read from the digital inputs.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
21
Register Assignment
The register assignment for the AIN 5506 module is used to configure the registers used for the
module data and the Extended Parameters available for the module. To open the register assignment
dialog for the AIN 5505 module:
•
Select Register Assignment from the Controller menu in TelePACE.
•
In the Register Assignment window select the Add button.
•
In the Add Register Assignment dialog select the AIN 5506 module from the list presented in
the Module window.
The register assignment dialog for the AIN 5506 module is shown below.
The Module selection displays the name of the 5506 Analog Input module used for the register
assignment.
The Address selection displays the module address of the physical 5506 Analog Input module. The
address on the module is selected via dip switches on the module. A maximum of sixteen AIN type
modules may be added to a system.
The register type 1xxxx defines the register range for the digital input status data. Eight sequential
registers are needed for the AIN 5506 module status data. Any unused block of eight registers may
be used. See the Status Register Data section below for an explanation of the digital input status
data.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
22
The register type 3xxxx defines the register range for the analog input data. Eight sequential registers
are needed for the AIN 5506 module analog data. Any unused block of eight registers may be used.
See the Input Register Data section below for an explanation of the analog input.
The Extended Parameters grouping defines the type of data returned from the 5506 AIN module,
filtering used by all inputs and the scan frequency.
The Type selection for each input (AIN 0, 1, 2, 3, 4, 5, 6, and 7) defines the input measurement type
for the analog input.
•
The 0-5V selection sets the input type to measure 0 to 5V input signals.
•
The 1-5V selection sets the input type to measure 1 to 5V input signals.
•
The 0-20 mA selection sets the input type to measure 0 to 20mA input signals.
•
The 4-20 mA selection sets the input type to measure 4 to 20mA input signals.
The AIN Filter selection set the input filter for all analog inputs. Filtering is used to dampen process
variations or noise.
•
The 3 Hz filter selection sets the response time to 155ms at 60Hz and 185ms at 50Hz.
•
The 6 Hz filter selection sets response time to 85ms at 60Hz and 85ms at 50Hz.
•
The 11 Hz filter selection sets response time to 45ms at 60Hz and 55ms at 50Hz.
•
The 30 Hz filter selection sets response time to 30ms at 60Hz and 30ms at 50Hz.
The Scan Frequency selection set the input scan rate for all analog inputs. The scan rate selection is
not critical but AC noise rejection is improved at the correct frequency. If the module is used in a DC
environment, the 60 Hz setting will yield slightly faster response time.
•
The 60 Hz selection synchronies the input scanning to 60Hz.
•
The 50 Hz selection synchronies the input scanning to 50Hz.
Status Register Data
Status register data is assigned to sixteen consecutive status (1xxxx) registers. The following
table begins at the Start address defined in the Register Assignment and continues for
sixteen registers.
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Assignment to Module Hardware
OFF = channel 0 is OK
ON = channel 0 is over or under range
OFF = channel 1 is OK
ON = channel 1 is over or under range
OFF = channel 2 is OK
ON = channel 2 is over or under range
OFF = channel 3 is OK
ON = channel 3 is over or under range
OFF = channel 4 is OK
ON = channel 4 is over or under range
OFF = channel 5 is OK
ON = channel 5 is over or under range
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
23
Registers
Start Register + 6
Start Register + 7
Assignment to Module Hardware
OFF = channel 6 is OK
ON = channel 6 is over or under range
OFF = channel 7 is OK
ON = channel 7 is over or under range
Input Register Data
Input register data is assigned to eight consecutive input (3xxxx) registers. The following
table begins at the Start address defined in the Register Assignment and continues for eight
registers.
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Notes
Refer to the 5506 Analog Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
24
1.3.9
AIN 5521 Module
Description
The AIN 5521 module provides eight analog inputs, from the 5521 Potentiometer analog input
module, for each module used. Data is assigned to eight consecutive input registers. The input
registers are updated continuously with data read from the analog inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN 5521 module
This module is assigned a unique module
address between 0 and 7. No other AINtype module may use this module address.
Input Register
First register of any unused
3xxxx
block of 8 consecutive input
registers.
Last register of block
3xxxx + 7
8 input registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Notes
Eight input registers are always assigned to the I/O Database when this module is used.
Refer to the 5521 Potentiometer Analog Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
25
1.3.10
AIN Generic 8 Point Module
Description
The AIN Generic 8 point module provides eight analog inputs. Data is assigned to eight
consecutive input registers. The input registers are updated continuously with data read from the
analog inputs. The AIN Generic 8 point module may be used in place of any other 8 point AINtype module.
The AIN Generic 8 point module type is a useful selection early on in the system design stage
before the final selection of the specific AIN module type is known.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AIN Generic 8 Point Module
This module is assigned a unique module
address between 0 and 15. No other AINtype module may use this module address.
Input Register
First register of any unused
3xxxx
block of 8 consecutive input
registers.
Last register of block
3xxxx + 7
8 input registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Notes
Eight input registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
26
1.4
Analog Output I/O Modules
Analog output modules are used to assign data from the I/O Database to physical analog outputs. The
physical analog outputs are specific 5000 Series I/O modules or generic I/O modules.
Analog output I/O modules may assign data to any holding registers in the I/O database that are not
being used by another Analog output I/O module. There are 9999 holding registers available. These
holding registers are numbered 40001 - 49999. Holding registers are referred to as 4xxxx registers
throughout this manual.
All holding registers that are not assigned to any other I/O modules may be used as general purpose
holding registers in a ladder program. The I/O modules available are described in the following
pages.
Note: To properly view analog input/output registers, the register type should be set to type signed.
Setting the register type to anything else may result in inaccurate readings being
displayed/written to these registers.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
27
1.4.1
AOUT 5301 Module
Description
The AOUT 5301 module provides two analog outputs, to the 5000 Series 5301 Analog output
module, for each module used. Data is assigned from two consecutive holding registers. The analog
outputs are updated continuously with data read from the holding registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AOUT 5301 module
This module is assigned a unique module
address between 0 and 15. No other AOUTtype module may use this module address.
Holding Register
First register of any unused
4xxxx
block of 2 consecutive holding
registers.
Last register of block
4xxxx + 1
2 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Analog output 0
Analog output 1
Notes
Two holding registers are always assigned to the I/O Database when this module is used.
Refer to the 5301 Analog Output Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
28
1.4.2
AOUT 5302 Module
Description
The AOUT 5302 module provides four analog outputs, to the 5000 Series 5302 Analog output
module, for each module used. Data is assigned from four consecutive holding registers. The analog
outputs are updated continuously with data read from the holding registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AOUT 5302 module
This module is assigned a unique module
address between 0 and 15. No other AOUTtype module may use this module address.
Holding Register
First register of any unused
4xxxx
block of 4 consecutive holding
registers.
Last register of block
4xxxx + 3
4 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Analog output 0
Analog output 1
Analog output 2
Analog output 3
Notes
Four holding registers are always assigned to the I/O Database when this module is used.
Refer to the 5302 Analog Output Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
29
1.4.3
AOUT 5304 Module
Description
The AOUT 5304 module provides four analog outputs, to the 5000 Series 5304 Analog output
module, for each module used. Data is assigned from four consecutive holding registers. The analog
outputs are updated continuously with data read from the holding registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AOUT 5304 module
This module is assigned a unique module
address between 0 and 15. No other AOUTtype module may use this module address.
Holding Register
First register of any unused
4xxxx
block of 4 consecutive holding
registers.
Last register of block
4xxxx + 3
4 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Analog output 0
Analog output 1
Analog output 2
Analog output 3
Notes
Four holding registers are always assigned to the I/O Database when this module is used.
Refer to the 5304 Analog Output Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
30
1.4.4
AOUT Generic 2 Point Module
Description
The AOUT Generic 2 point module provides two analog outputs. Data is assigned from two
consecutive holding registers. The analog outputs are updated continuously with data read from the
holding registers. The AOUT Generic 2 point module may be used in place of any other 2 point
AOUT-type module.
The AOUT Generic 2 point module type is a useful selection early on in the system design stage
before the final selection of the specific AOUT module type is known.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AOUT Generic 2 point module
This module is assigned a unique module
address between 0 and 15. No other AOUTtype module may use this module address.
Holding Register
First register of any unused
4xxxx
block of 2 consecutive holding
registers.
Last register of block
4xxxx + 1
2 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Analog output 0
Analog output 1
Notes
Two holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
31
1.4.5
AOUT Generic 4 Point Module
Description
The AOUT Generic 4 point module provides four analog outputs. Data is assigned from four
consecutive holding registers. The analog outputs are updated continuously with data read from the
holding registers. The AOUT Generic 4 point module may be used in place of any other 4 point
AOUT-type module.
The AOUT Generic 4 point module type is a useful selection early on in the system design stage
before the final selection of the specific AOUT module type is known.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
AOUT Generic 4 point module
This module is assigned a unique module
address between 0 and 15. No other AOUTtype module may use this module address.
Holding Register
First register of any unused
4xxxx
block of 4 consecutive holding
registers.
Last register of block
4xxxx + 3
4 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Analog output 0
Analog output 1
Analog output 2
Analog output 3
Notes
Four holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
32
1.5
Configuration I/O Modules
Configuration modules are used to assign data from the I/O Database coil and holding registers to
controller configuration settings. The configuration data is used to configure controller settings such
as clearing protocol and serial counters, real time clock settings, HART protocol interface and PID
control blocks.
Configuration I/O modules assign data to I/O database coil or holding registers, depending on the
type of data. Configuration I/O modules may assign data to any coil or holding registers in the I/O
database that are not being used by another I/O module.
All I/O database coil or holding registers that are not assigned to any other I/O modules may be used
as general purpose coil or holding registers in a ladder program. The configuration modules available
are described in the following pages.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
33
1.5.1
CNFG Clear Protocol Counters
Description
The module, CNFG Clear protocol counters, provides a way of clearing the protocol event
counters for a specific serial port. The protocol event counters for the serial port are cleared when the
assigned coil register is set to 1. Once the counters are cleared, the assigned coil register is
automatically reset to zero.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Clear protocol counters
com1, com2, com3, or com4.
Coil Register
Any unused coil register.
Same as start register.
1 coil register.
None
None
0xxxx
Register Data
Registers
Start Register
Assignment to Module Hardware
Clear protocol event counters.
Notes
Refer to the module, DIAG Serial port protocol status, for a description of the individual counters.
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported only
when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported only when the
SCADAPack 5602 I/O module is installed. To optimize performance, minimize the length of
messages on com3 and com4. Examples of recommended uses for com3 and com4 are for local
operator terminals, and for programming and diagnostics using the TelePACE program.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
34
1.5.2
CNFG Clear Serial Port Counters
Description
The module, CNFG Clear serial port counters, provides a way of clearing the communication
event counters for a specific serial port. The serial port counters are cleared when the assigned coil
register is set to 1. Once the counters are cleared the assigned coil register is automatically reset to 0.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Clear serial port counters
Com1, com2, com3, or com4.
Coil Register
Any unused coil register.
0xxxx
Same as start register.
1 coil register.
None
None
Register Data
Registers
Start Register
Assignment to Module Hardware
Clear communication event counters.
Notes
Refer to the module, DIAG Serial port comm. status, for a description of the individual counters.
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported only
when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported only when the
SCADAPack 5602 I/O module is installed. To optimize performance, minimize the length of
messages on com3 and com4. Examples of recommended uses for com3 and com4 are for local
operator terminals, and for programming and diagnostics using the TelePACE program.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
35
1.5.3
CNFG DTR Off
Description
The module, CNFG DTR Off, provides a way of controlling the DTR signal for a specific serial
port. When the assigned coil is energized DTR for the serial port is de-asserted. DTR is constantly
turned off when the coil is energized.
When the assigned coil is de-energized DTR for the serial port is asserted. The DTR signal is not
constantly asserted. It is asserted on the transition from an energized coil to a de-energized coil.
Since DTR is not constantly re-asserted other programs will be able to control the DTR setting. This
way other ladder blocks and programs will be able to control the DTR settings.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG DTR Off
com1, com2, com3, or com4.
Coil Register
Any unused coil register.
Same as start register.
1 coil register.
None
None
0xxxx
Register Data
Registers
Start Register
Assignment to Module Hardware
Controls DTR signal
0 = DTR asserted
1 = DTR not asserted
Default: 0 = DTR asserted
Notes
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported only
when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported only when the
SCADAPack 5602 I/O module is installed. To optimize performance, minimize the length of
messages on com3 and com4. Examples of recommended uses for com3 and com4 are for local
operator terminals, and for programming and diagnostics using the TelePACE program.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
36
1.5.4
CNFG 5904 HART Interface Module
Description
The module, CNFG 5904 HART Interface provides control of 5904 HART Interface modules.
When configured the module maintains communication with a 5904 interface. Up to four 5904
interfaces may be attached to a controller.
The interface settings are assigned from four consecutive holding registers. The registers are
initialized with the current value of the module parameters when the controller is reset, and when the
Register Assignment is downloaded to the controller. Thereafter the data from all four holding
registers are written to the module parameters, whenever any of the registers change.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG 5904 HART Interface
0 to 3
Holding Register
The first register of any
4xxxx
unused block of 4
consecutive holding
registers.
The last register of the
4xxxx + 3
block
4 holding registers
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Attempts: the number of times each HART command will be sent.
Valid values are 1 to 4.
Default : = 3
Preambles: number of preambles to send if fixed preambles selected.
Valid values are 2 to 15. This value must be set as it is used by link
initialization.
Default : = 15
Auto-preamble control:
0 = use fixed number of preambles
1 = use number of preambles requested by device except for link
initialization
Default : = 1
Device type
0 = secondary master device
1 = primary master device (recommended)
Default : = 1
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
37
Notes
This module provides the basis for communication with HART devices connected to the 5904
interface module. It does not send commands to the HART devices. Use the Ladder Logic HART
element or the C Tools HART API functions to send commands to the HART devices.
The number of preambles must be set even if the auto-preamble control is selected. The preambles
value will be used for the link initialization command which determines the number of preambles
requested by the device.
In most sensor networks, the controller is the primary master device. A hand-held programmer is
typically a secondary master device. Set the device type to primary unless another HART primary
master device is connected to the network.
The settings can be saved to EEPROM with the CNFG Save Settings to EEPROM module.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
38
1.5.5
CNFG IP Settings
Description
The module, CNFG IP settings, provides control of the IP settings for a specific communication
interface. Settings are assigned from thirteen consecutive holding registers. The registers are
initialized with the current value of the module parameters on power-up, and when the Register
Assignment is downloaded to the controller. Thereafter the data from all thirteen holding registers is
written to the module parameters, whenever any of the registers change.
This module is used by the SCADAPack 32 controller series only.
Use this module only when IP settings need to be changed within a Ladders program. It is more
convenient to use the Controller TCP/IP Settings dialog to download IP settings with the Ladders
program.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the TCP/IP communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG IP settings
Ethernet1
Holding Register
First register of any unused
block of 13 consecutive
holding registers.
Last register of block
13 holding registers.
None
None
4xxxx
4xxxx + 12
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Assignment to Module Hardware
Byte1 of the IP Address using format: Byte1.Byte2.Byte3.Byte4
Default: 0
Byte2 of the IP Address
Default: 0
Byte3 of the IP Address
Default: 0
Byte4 of the IP Address
Default: 0
Byte1 of the Subnet Mask using format: Byte1.Byte2.Byte3.Byte4
Default: 255
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
39
Registers
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Assignment to Module Hardware
Byte2 of the Subnet Mask
Default: 255
Byte3 of the Subnet Mask
Default: 255
Byte4 of the Subnet Mask
Default: 255
Byte1 of the Default Gateway using format
Byte1.Byte2.Byte3.Byte4
Default: 0
Byte2 of the Default Gateway
Default: 0
Byte3 of the Default Gateway
Default: 0
Byte4 of the Default Gateway
Default: 0
IP Configuration Mode
0 = Default gateway is on the LAN subnet
1 = Default gateway is on the com1 PPP subnet
2 = Default gateway is on the com2 PPP subnet
3 = Default gateway is on the com3 PPP subnet
4 = Default gateway is on the com4 PPP subnet
Notes
Thirteen holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
40
1.5.6
CNFG LED Power Settings
Description
The module, CNFG LED power settings, provides control of the power settings for the controller
LEDs. The state of the assigned coil register is the default state for the LED power. The time to
return to the Default State is contained within the assigned holding register.
The registers are initialized with the current value of the module parameters on power-up, and when
the Register Assignment is downloaded to the controller. Thereafter the module parameters are
updated continuously with data read from the assigned registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
CNFG LED power settings
No physical address is required.
Coil Register
Any unused coil register.
0xxxx
Same as start register.
1 coil register.
default state
Holding Register
Any unused holding register
4xxxx
Same as start register
1 holding register
time to return to default state
None
Coil Register Data
Registers
Start
Register
Assignment to Module Hardware
Default state for power to the controller
LEDs
0 = off
1 = on
Default Value: 1 = on
Holding Register Data
Registers
Start
Register
Assignment to Module Hardware
Time in minutes to return to the default
state.
1 to 65535 minutes
Default Value: 5 minutes
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
41
Notes
One holding register and one coil register are always assigned to the I/O Database when this module
is used.
Refer to the System Manual for further information on LED power settings.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
42
1.5.7
CNFG Modbus IP Interface
Description
The module, CNFG Modbus IP Interface, provides control of the protocol interface settings used
by all Modbus IP protocols on the specified communication interface. Settings are assigned from five
consecutive holding registers. The registers are initialized with the current value of the module
parameters on power-up, and when the Register Assignment is downloaded to the controller.
Thereafter the data from all five holding registers is written to the module parameters, whenever any
of the registers change.
This module is used by the SCADAPack 32 controller series only.
Use this module only when Modbus IP protocol interface settings need to be changed within a
Ladders program. It is more convenient to use the Controller Modbus IP Protocols dialog to
download protocol interface settings with the Ladders program.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the Modbus IP communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Modbus IP Interface
Ethernet1
Holding Register
First register of any unused
block of 5 consecutive holding
registers.
Last register of block
5 holding registers.
None
None
4xxxx
4xxxx + 4
Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Modbus station number
1 to 255 in standard Modbus
1 to 65534 in extended Modbus
Default: 1
Modbus store and forward enable
0 = disabled
1 = enabled
Default: 0 = disabled
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
43
Registers
Start Register + 2
Start Register + 3
Start Register + 4
Assignment to Module Hardware
Modbus addressing mode
0 = standard
1 = extended
Default: 0 = standard
Enron Modbus enable
0 = disabled
1 = enabled
Default: 0 = disabled
Enron Modbus station number
1 to 255 in standard Modbus
1 to 65534 in extended Modbus
Default: 1
Notes
Five holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
44
1.5.8
CNFG Modbus IP Protocols
Description
The module, CNFG Modbus IP Protocols, provides control of the settings for a Modbus IP
protocol. Settings are assigned from ten consecutive holding registers. The registers are initialized
with the current value of the module parameters on power-up, and when the Register Assignment is
downloaded to the controller. Thereafter the data from all ten holding registers is written to the
module parameters, whenever any of the registers change.
This module is used by the SCADAPack 32 controller series only.
Use this module only when Modbus IP protocol settings need to be changed within a Ladders
program. It is more convenient to use the Controller Modbus IP Protocols dialog to download
protocol settings with the Ladders program.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the Modbus IP communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Modbus IP Protocols
1 = Modbus/TCP,
2 = Modbus RTU over UDP, or
3 = Modbus ASCII over UDP
Holding Register
First register of any unused
block of 10 consecutive
holding registers.
Last register of block
10 holding registers.
None
None
4xxxx
4xxxx + 9
Register Data
Registers
Start Register
Assignment to Module Hardware
Protocol Port Number: 1 to 65534
Modbus/TCP
Default: 502
Modbus RTU over UDP
Default: 49152
Modbus ASCII over UDP
Default: 49153
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
45
Registers
Start Register + 1 and
Start Register + 2
Start Register + 3 and
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Assignment to Module Hardware
Master Idle Timeout: The length of time, in seconds,
that a master connection will wait for the user to send
the next command before ending the connection. This
allows the slave device to free unused connections
while the master application may retain the connection
allocation. (32 bit register)
0 = disable timeout and let application close the
connection.
Default: 10
TCP protocols only. Not used by UDP protocols.
Server Idle Timeout: The length of time, in seconds,
that a server connection will wait for a message
before ending the connection. (32 bit register)
0 = disable timeout and let client close connection.
Default: 250
TCP protocols only. Not used by UDP protocols.
Protocol Server Enable:
0 = disable server.
1 = enable server.
Default: 1
Reserved
Reserved
Reserved
Reserved
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
46
1.5.9
CNFG Modbus/TCP Settings
Description
The module, CNFG Modbus/TCP settings, provides control of the Modbus/TCP protocol
settings. Settings are assigned from six consecutive holding registers. The registers are
initialized with the current value of the module parameters on power-up, and when the
Register Assignment is downloaded to the controller. Thereafter the data from all six
holding registers is written to the module parameters, whenever any of the registers change.
This module is used by the SCADAPack 32 controller series only.
Use this module only when Modbus/TCP settings need to be changed within a Ladders
program. It is more convenient to use the Controller Modbus/TCP Settings dialog to
download Modbus/TCP settings with the Ladders program.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the Modbus/TCP communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Modbus/TCP settings
No physical address is required.
Holding Register
First register of any unused
4xxxx
block of 6 consecutive holding
registers.
Last register of block
4xxxx + 5
6 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1 and
Start Register + 2
Assignment to Module Hardware
Port for Modbus/TCP protocol
Default: 502
Master Idle Timeout: The length of time, in seconds,
that a master connection will wait for the user to send
the next command before ending the connection. (32
bit register)
0 = disable timeout and let user close the connection.
Default: 10
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
47
Registers
Start Register + 3 and
Start Register + 4
Start Register + 5
Assignment to Module Hardware
Server Idle Timeout: The length of time, in seconds,
that a server connection will wait for a message
before ending the connection. (32 bit register)
0 = disable timeout and let client close connection.
Default: 250
Maximum number of server connections up to the
capacity available (typical capacity is 20 connections)
Default: 20
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
48
1.5.10
CNFG PID Control Block
Description
The module, CNFG PID control block, provides control over the configuration of a PID
control block and provides access to the control block parameters. Control block parameters
are assigned to 25 consecutive holding registers. The module address refers to the PID
control block number.
The holding registers are updated continuously with data read from the module parameters.
Whenever a Ladder Logic program or C Application changes any of the registers, only data
from the changed register is written to the corresponding module parameter.
Register Assignment
Module
CNFG PID control block
Address
This module is assigned a unique module
address between 0 and 31. No other PIDtype module may use this module address.
Holding Register
Type
End
First register of any unused
block of 25 consecutive
holding registers.
Last register of block
Registers
25 holding registers.
Description
None
Extended Parameters
None
Start
4xxxx
4xxxx +24
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Assignment to Module Hardware
Process Value
(PV)
Error
(ER)
Output Quantity
(OP)
Status Register
SR)
Integrated Error
(IN)
Setpoint
(SP)
Deadband
(DB)
Gain
(GA)
Reset Time
(RE)
Rate Time
(RA)
Full Scale Output Limit
(FS)
Zero Scale Output Limit
(ZE)
High Alarm Level
(HI)
Low Alarm Level
(LO)
Control Register
(CR)
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
49
Registers
Start Register + 15
Start Register + 16
Start Register + 17
Start Register + 18
Start Register + 19
Start Register + 20
Start Register + 21
Start Register + 22
Start Register + 23
Start Register + 24
Assignment to Module Hardware
Input Source
(IP)
Increase Output Address
(IO)
Decrease Output Address
(DO)
Input Bias
(IB)
Output Bias
(OB)
Inhibit Execution Address
(IH)
Alarm Output Address
(AO)
Cascade Setpoint Source
(CA)
Execution Period
Execution Period at Power Up
Notes
Twenty-five holding registers are always assigned to the I/O Database when this module is
used.
Refer to the TelePACE PID Controller Reference Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
50
1.5.11
CNFG Power Mode
Description
The module, CNFG Power Mode, provides control over the power consumption of the
controller. The LAN port and USB host port can be individually disabled to conserve
power. The controller can also run at a reduced speed to conserve power.
The status registers are updated continuously with the current LAN, controller, and USB
host power states. The current settings can be changed by writing to the appropriate holding
register.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
CNFG Power Mode
fixed
Holding Register
First register of any unused block of 3
consecutive holding registers.
Last register of block
3 holding registers
None
4xxxx
4xxxx + 2
Holding Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Assignment to Module Hardware
LAN Operation State (0 = LAN Enabled, 1 = LAN
Disabled)
Controller Power State (0 = Normal Power Mode, 1
= Reduced Power Mode)
USB Host Port Power State (0 = USB host port
enabled, 1 = USB host port disabled)
Notes
Three holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
51
1.5.12
CNFG Protocol Settings Method 1
Description
The module, CNFG Protocol settings method 1, provides control of the protocol settings
for a specific serial port. Settings are assigned from three consecutive holding registers. The
registers are initialized with the current value of the module parameters on power-up, and
when the Register Assignment is downloaded to the controller. Thereafter the data from all
three holding registers is written to the module parameters, whenever any of the registers
change.
Use this module only when protocol settings need to be changed within a Ladders program.
It is more convenient to use the Controller Serial Ports Settings dialog to download protocol
settings with the program. Refer to the Serial Ports section in this manual for further
information on serial port settings.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the serial communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Protocol settings
com1, com2, com3, or com4.
Holding Register
First register of any unused
block of 3 consecutive holding
registers.
Last register of block
3 holding registers.
None
None
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
4xxxx
4xxxx + 2
52
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Assignment to Module Hardware
Protocol type
0 = none
1 = Modbus RTU
2 = Modbus ASCII
3 = DF1 Full Duplex BCC
4 = DF1 Full Duplex CRC
5 = DF1 Half Duplex BCC
6 = DF1 Half Duplex CRC
7 = DNP
8 = PPP
Default : 1 = Modbus RTU
Protocol station number
1 to 255 in Modbus
0 to 254 in DF1
Default : 1
Store and forward enable
0 = disabled
1 = enabled
Default : 0 = disabled
Notes
This register assignment module replaces the CNFG Protocol Settings module used in
earlier versions of TelePACE.
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported
only when the SCADAPack 5601 or 5604 I/O module is installed. Com4 is supported only
when the SCADAPack 5602 I/O module is installed. To optimize performance, minimize
the length of messages on com3 and com4. Examples of recommended uses for com3 and
com4 are for local operator terminals, and for programming and diagnostics using the
TelePACE program.
Refer to the TeleBUS Protocols User Manual for further information on protocols.
Three holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
53
1.5.13
CNFG Protocol Settings Method 2
The module, CNFG Protocol settings method 2, provides control of the protocol settings
for a specific serial port. This module supports the use of extended addressing.
Settings are assigned from four consecutive holding registers. The registers are initialized
with the current value of the module parameters on power-up, and when the Register
Assignment is downloaded to the controller. Thereafter the data from all four holding
registers is written to the module parameters, whenever any of the registers change.
Use this module only when protocol settings need to be changed within a Ladders program.
It is more convenient to use the Controller Serial Ports Settings dialog to download protocol
settings with the program. Refer to the Serial Ports section in this manual for further
information on serial port settings.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the serial communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Protocol Extended Settings
com1, com2, com3, or com4.
Holding Register
First register of any unused
4xxxx
block of 4 consecutive holding
registers.
Last register of block
4xxxx + 3
4 holding registers.
None
None
Register Data
Registers
Start Register
Assignment to Module Hardware
Protocol type
0 = none
1 = Modbus RTU
2 = Modbus ASCII
3 = DF1 Full Duplex BCC
4 = DF1 Full Duplex CRC
5 = DF1 Half Duplex BCC
6 = DF1 Half Duplex CRC
7 = DNP
8 = PPP
Default : 1 = Modbus RTU
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
54
Registers
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Protocol station number
1 to 255 in standard Modbus
1 to 65534 in extended Modbus
0 to 254 in DF1
Default : 1
Store and forward enable
0 = disabled
1 = enabled
Default : 0 = disabled
Protocol addressing mode
0 = standard
1 = extended
Default: 0 = standard
Notes
This register assignment module replaces the CNFG Protocol Extended Settings module
used in earlier versions of TelePACE.
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported
only when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported
only when the SCADAPack 5602 I/O module is installed. To optimize performance,
minimize the length of messages on com3 and com4. Examples of recommended uses for
com3 and com4 are for local operator terminals, and for programming and diagnostics using
the TelePACE program.
Extended addressing is supported only by the Modbus RTU and Modbus ASCII protocols.
To optimize performance, minimize the length of messages on com3 and com4. Examples of
recommended uses for com3 and com4 are for local operator terminals, and for
programming and diagnostics using the TelePACE program.
Refer to the TeleBUS Protocols User Manual for further information on protocols.
Four holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
55
1.5.14
CNFG Protocol Settings Method 3
Description
The module, CNFG Protocol Settings Method 3, provides control of the protocol settings
for a specific serial port. This module supports extended addressing and Enron Modbus
parameters.
Settings are assigned from six consecutive holding registers. The registers are initialized
with the current value of the module parameters on power-up, and when the Register
Assignment is downloaded to the controller. Thereafter the data from all six holding
registers is written to the module parameters, whenever any of the registers change.
Use this module only when protocol settings need to be changed within a Ladders program.
It is more convenient to use the Controller Serial Ports Settings dialog to download protocol
settings with the program. Refer to the Serial Ports section in this manual for further
information on serial port settings.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the serial communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Protocol Settings Method3
com1, com2, com3, or com4.
Holding Register
First register of any unused
4xxxx
block of 6 consecutive holding
registers.
Last register of block
4xxxx + 5
6 holding registers.
None
None
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
56
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Assignment to Module Hardware
Protocol type
0 = none
1 = Modbus RTU
2 = Modbus ASCII
3 = DF1 Full Duplex BCC
4 = DF1 Full Duplex CRC
5 = DF1 Half Duplex BCC
6 = DF1 Half Duplex CRC
7 = DNP
8 = PPP
Default : 1 = Modbus RTU
Protocol station number
1 to 255 in standard Modbus
1 to 65534 in extended Modbus
0 to 254 in DF1
Default : 1
Store and forward enable
0 = disabled
1 = enabled
Default : 0 = disabled
Protocol addressing mode
0 = standard
1 = extended
Default: 0 = standard
Enron Modbus enable
0 = disabled
1 = enabled
Default : 0 = disabled
Enron Modbus station number
1 to 255 in standard Modbus
1 to 65534 in extended Modbus
Default : 1
Notes
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported
only when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported
only when the SCADAPack 5602 I/O module is installed. To optimize performance,
minimize the length of messages on com3 and com4. Examples of recommended uses for
com3 and com4 are for local operator terminals, and for programming and diagnostics using
the TelePACE program. Extended addressing is supported only by the Modbus RTU and
Modbus ASCII protocols.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
57
To optimize performance, minimize the length of messages on com3 and com4. Examples of
recommended uses for com3 and com4 are for local operator terminals, and for
programming and diagnostics using the TelePACE program.
Refer to the TeleBUS Protocols User Manual for further information on protocols.
Six holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
58
1.5.15
CNFG Real Time Clock and Alarm
Description
The module, CNFG Real time clock and alarm, provides access to the controller real time
clock data and alarm settings. Real Time Clock and Alarm settings are assigned from eleven
consecutive holding registers. The registers are initialized with the current value of the
module parameters on power-up, and when the Register Assignment is downloaded to the
controller.
The clock data from the first 7 holding registers is written to the module parameters,
whenever any of these registers are changed by a Ladders program or C Application.
Otherwise, these holding registers are updated continuously with data read from the real
time clock.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
continuously energized the controller real time clock will not change.
The alarm settings are updated continuously with data read from the last 4 holding registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Real time clock and alarm
No physical address is required.
Holding Register
First register of any unused
4xxxx
block of 11 consecutive
holding registers.
Last register of block
4xxxx +10
11 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Real time clock hour
0 to 23
Real time clock minute 0 to 59
Real time clock second 0 to 59
Real time clock year
00 to 99
Real time clock month 1 to 12
Real time clock day
1 to 31
Real time clock day of week
1 to 7,
1=Sunday, 2=Monday…7=Saturday
Alarm hour
0 to 23
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
59
Registers
Start Register + 8
Start Register + 9
Start Register + 10
Assignment to Module Hardware
Alarm minute 0 to 59
Alarm second 0 to 59
Alarm control 0 = no alarm
1 = absolute time
2 = elapsed time alarm
(relative from now)
** See note below.
** The Alarm Control register (Start Register + 10) enables or disables the alarm. A value
of 0 in this register disables the alarm. A value of 1 sets an alarm to be triggered in absolute
time, based on the values in the preceding three registers. A value of 2 sets the alarm to be
triggered at a latter time, starting now.
Note that the alarm settings above and those in the Sleep (SLP) function block will trigger
the same interrupt. See the Ladder Logic Function Reference in this book for details on the
SLP function. Using both alarm settings, therefore, in the same program is not
recommended.
Additional Notes
The 5203/4 Controllers have a hardware based real-time clock that independently maintains
the time and date for the operating system. The time and date remain accurate during poweroff. The calendar automatically handles leap years.
One method for setting the clock is to use the Edit/Force Register dialog to write the current
time to the appropriate module registers. Leave the force box in the dialog unchecked so that
the data is only written, not forced.
All seven registers for the real time clock must be set to valid values for the clock to operate
properly. Refer to real time clock specifications in the Controller System Manual for further
information.
Eleven holding registers are always assigned to the I/O Database when this module is used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
60
1.5.16
CNFG Save Settings to EEPROM
Description
The module, CNFG Save settings to EEPROM, provides a way to save controller settings
to EEPROM. Saving to EEPROM is controlled by one assigned coil register. The controller
settings are saved when the coil register is set to 1. Once saved the coil register is
automatically reset to 0.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Save settings to EEPROM
No physical address is required.
Coil Register
Any unused coil register.
0xxxx
Same as start register.
1 coil register.
None
None
Register Data
Registers
Start Register
Assignment to Module Hardware
Save the following controller settings:
Serial port settings
Protocol settings
Enable store and forward settings
LED power settings
Mask for wake-up sources
HART interface configuration
Execution period on power-up for each PID
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
61
1.5.17
CNFG Serial Port Settings
Description
The module, CNFG Serial port settings, controls the configuration settings for a serial
port. Settings are assigned from nine consecutive holding registers. The holding registers are
initialized with the current value of the module parameters on power-up, and when the
Register Assignment is downloaded to the controller. Thereafter the data from all 9 holding
registers is written to the module parameters, whenever any of the registers change.
Use this module only when serial port settings need to be changed within a Ladders
program. It is more convenient to use the Controller Serial Ports Settings dialog to
download settings with the program. Refer to the Serial Ports section under Controller
Menu, in this manual, for further information on serial port settings.
Note: Any block transfer Ladder Logic function may be used to write data to the holding
registers used for this module. The data in the holding registers is written to the
module parameters only when the ladder function is energized. Users must ensure
the ladder function is only energized for one program scan. If the ladder function is
always energized problems with the serial communication will result.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNFG Serial port settings
Com1, com2, com3, or com4.
Holding Register
First register of any unused
block of 9 consecutive
holding registers.
Last register of block
9 holding registers.
None
None
4xxxx
4xxxx +8
Register Data
Registers
Start Register
Assignment to Module Hardware
Baud rate
0 = 75 baud
1 = 110 baud
2 = 150 baud 3 = 300 baud
4 = 600 baud 5 = 1200 baud
6 = 2400 baud 7 = 4800 baud
8 = 9600 baud 9 = 19200 baud
10 =38400
11 = 115200 com3, com4 only
12 = 57600 com3, com4 only
Default : 8 = 9600 baud
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
62
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Duplex
0 = half duplex
1 = full duplex
com1, com2 Default : 1 = full
com3, com4 Default : 0 = half
Parity
0 = none
1 = even
2 = odd
Default : 0 = none
Data bits
0 = 7 bits
1 = 8 bits
Default : 1 = 8 bits
Stop bits
0 = 1 bit
1 = 2 bits
Default : 0 = 1 bit
Receiver flow control
Com1, Com2 0 = none (default)
1 = XON/XOFF
Com3, Com4 0 = none
1 = Receive Disable (default)
Transmitter flow control
Com1, Com2 0 = none (default)
1 = XON/XOFF
Com3, Com4 0 = none (default)
1 = Ignore CTS
Port type
0 = automatic
1 = RS232
3 = RS485
6 = RS232 MODEM
7 = RS232 Collision Avoidance
Default : 1 = RS232
Serial time-out delay
0 to 65535 (x 0.1 seconds)
Default : 600 = 60 seconds
Notes
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported
only when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported
only when the SCADAPack 5602 I/O module is installed. To optimize performance,
minimize the length of messages on com3 and com4. Examples of recommended uses for
com3 and com4 are for local operator terminals, and for programming and diagnostics using
the TelePACE program.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
63
1.5.18
CNFG Store and Forward
Description
The module, CNFG Store and forward, controls the store and forward table. Store and
Forward table data is assigned from 512 consecutive holding registers. One coil register is
assigned to clear the translation table.
This module is used by the SCADAPack controller series only. For SCADAPack 32
controllers use the Store and Forward command in TelePACE.
The holding registers are initialized with the current value of the module parameters on
power-up, and when the Register Assignment is downloaded to the controller. Thereafter the
table is updated continuously with data read from the holding registers. The table is cleared
when the coil register is set to 1. Once cleared the coil register is automatically reset to 0.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
CNFG Store and Forward
No physical address is required.
Coil Register
Any unused coil register.
0xxxx
Same as start register.
1 coil register.
clear Store and Forward table
Holding Register
First register of any unused
4xxxx
block of 512 consecutive
holding registers.
Last register in block.
4xxxx +511
512 holding registers
Translation table
None
Coil Register Data
Registers
Start Register
Assignment to Module Hardware
Clear Translation table
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
64
Holding Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4 to
Start Register + 7
Start Register + 8 to
Start Register + 11
Start Register + 12 to
Start Register + 511
Assignment to Module Hardware
Translation table entry 0
Port A
0 = com1
1 = com2
2 = com3
3 = com4
Default : 0
Translation table entry 0
Station A
0 to 255 standard addressing
0 to 65534 extended addressing
65535 = disable
Default : 65535
Translation table entry 0
Port B
0 = com1
1 = com2
2 = com3
3 = com4
Default : 0
Translation table entry 0
Station B
0 to 255 standard addressing
0 to 65534 extended addressing
65535 = disable
Default : 65535
Translation table entry 1
Translation table entry 2
Translation table entries 3 to 127
Notes
Refer to the TeleBUS Protocols User Manual for further information on Store and Forward
messaging.
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported
only when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported
only when the SCADAPack 5602 I/O module is installed. To optimize performance,
minimize the length of messages on com3 and com4. Examples of recommended uses for
com3 and com4 are for local operator terminals, and for programming and diagnostics using
the TelePACE program.
Store and forward messaging is enabled on the required serial ports using the module CNFG
Protocol settings.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
65
1.6
Counter I/O Modules
Counter input modules are used to assign data from physical counter inputs to input registers
in the I/O Database. The physical counter inputs are specific 5000 Series I/O modules and
controller counter inputs.
Counter input modules may assign data to any input registers that are not used by another
Analog Input module or Counter input module. There are 1024 I/O database input registers
available. These input registers are numbered 30001 - 31024. Input registers are referred to
as 3xxxx registers throughout this manual.
All I/O database input registers that are not assigned to any other I/O modules may be used
as general purpose input registers in a ladder program. The I/O modules available are
described in the following pages.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
66
1.6.1
CNTR Controller Counter Inputs
Description
The module, CNTR controller counter inputs, reads the three counter inputs on the
Micro16, SCADAPack, SCADAPack Light, SCADAPack, SCADAPack Plus, SCADAPack
32 and SCADAPack 32P controllers. Data is assigned to six consecutive input registers. The
input registers are updated continuously with data read from the counters.
Each counter is a 32-bit number, stored in two 16-bit registers. The first register holds the
least significant 16 bits of the counter. The second register holds the most significant 16 bits
of the counter. To obtain the correct count, both registers must be read with the same
protocol read command. Ladder Logic programs can read the registers in any order,
provided both registers are examined on the same pass through the program.
The maximum count is 4,294,967,295. Counters roll over to 0 when the maximum count is
exceeded.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNTR controller counter inputs
No physical address is required.
Input Register
First register of any unused
3xxxx
block of 6 consecutive input
registers.
Last register of block
3xxxx +5
6 input registers.
None
None
Register Data
Registers
Start Register and
Start Register + 1
Start Register + 2 and
Start Register + 3
Start Register + 4 and
Start Register + 5
Assignment to Module Hardware
Controller counter input 0
(32 bit register)
Controller counter input 1
(32 bit register)
Controller counter input 2
(32 bit register)
Notes
Refer to the Hardware User Manual for further information on controller board counter
inputs.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
67
1.6.2
CNTR Controller Interrupt Input
Description
The module, CNTR controller interrupt input, reads the interrupt input on the Micro16,
SCADAPack, SCADAPack Light, SCADAPack, SCADAPack Plus, SCADAPack 32 and
SCADAPack 32P controllers as a counter input. Data is assigned to two consecutive input
registers. The input registers are updated continuously with data read from the counter.
The counter is a 32-bit number, stored in two 16-bit registers. The first register holds the
least significant 16 bits of the counter. The second register holds the most significant 16 bits
of the counter. To obtain the correct count, both registers must be read with the same
protocol read command. Ladder Logic programs can read the registers in any order,
provided both registers are examined on the same pass through the program.
The maximum count is 4,294,967,295. The counter rolls over to 0 when the maximum count
is exceeded.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNTR controller interrupt input
No physical address is required.
Input Register
First register of any unused
3xxxx
block of 2 consecutive input
registers.
Last register of block
3xxxx +1
2 input registers.
None
None
Register Data
Registers
Start Register
and
Start Register + 1
Assignment to Module Hardware
Interrupt input counter
(32 bit register)
Notes
Refer to the SCADAPack and Micro16 System Manual for further information on controller
board counter inputs.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
68
1.6.3
CNTR 5410 input module
Description
The module, CNTR 5410 input module, provides four counter inputs. Data is assigned to
eight consecutive input registers. The input registers are updated continuously with data
read from the counters.
Each counter is a 32-bit number, stored in two 16-bit registers. The first register holds the
least significant 16 bits of the counter. The second register holds the most significant 16 bits
of the counter. To obtain the correct count, both registers must be read with the same
Modbus protocol read command. Ladder Logic programs can read the registers in any order,
provided both registers are examined on the same pass through the program.
The maximum count is 4,294,967,295. Counters roll back to 0 when the maximum count is
exceeded.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
CNTR 5203/4 counter inputs
This module is assigned a unique module
address between 0 and 15. No other CNTRtype module may use this module address.
Input Register
First register of any unused
3xxxx
block of 8 consecutive input
registers.
Last register of block
3xxxx +7
8 input registers.
None
None
Register Data
Registers
Start Register and
Start Register + 1
Start Register + 2 and
Start Register + 3
Start Register + 4 and
Start Register + 5
Start Register + 6 and
Start Register + 7
Assignment to Module Hardware
Counter input 0
(32 bit register)
Counter input 1
(32 bit register)
Counter input 2
(32 bit register)
Counter input 3
(32 bit register)
Notes
Refer to the 5410 High Speed Counter Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
69
1.7
Diagnostic I/O Modules
Diagnostic modules are used to assign diagnostic data from the controller to input or status
registers in the I/O Database. The diagnostic data is used to monitor internal controller data
such as controller status code, the force LED, serial communication status and protocol
status.
Diagnostic I/O modules assign data to I/O database input or status registers, depending on
the type of data. Diagnostic I/O modules may assign data to any input or status registers in
the I/O database that are not being used by another I/O module.
All I/O database input and status registers that are not assigned to any other I/O modules
may be used as general purpose input or status registers in a ladder program. The I/O
modules available are described in the following pages.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
70
1.7.1
DIAG Controller Status Code
Description
The module, DIAG Controller Status Code, reads the controller status code and assigns it
in one input register. The input register is updated continuously with the status code.
The Status LED blinks a binary sequence equal to the controller status code. Note that if a
“Register assignment table checksum error” occurs, only the Status LED will indicate this
status code. The I/O scan is disabled if this error occurs, so that the module DIAG
Controller status code is no longer updated.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIAG Controller Status Code
No physical address is required.
Input Register
Any unused input register.
3xxxx
Same as start register.
1 input register.
None
None
Register Data
Registers
Start Register
Assignment to Module Hardware
Controller status code:
0 = Normal
1 = I/O module communication failure
2 = Register Assignment Checksum error
Status LED - I/O Error Indication
When the Status LED flashes the error code 1 (i.e. a short flash, once every second), there is
a communication failure with one or more I/O module. To correct the problem, do one of the
following:
1. Ensure that every module contained in the Register Assignment is connected to the
controller. Check that the module address selected for each module agrees with the
selection made in the Register Assignment.
2. If a module is currently not connected to the controller, delete it from the Register
Assignment. Download the new Register Assignment to the controller.
3. If a module is still suspect of having failed, confirm the failure by removing the module
from the Register Assignment. Download the new Register Assignment to the controller.
The Status LED should stop flashing.
4. If unused modules must be intentionally left in the Register Assignment, the I/O error
indication may be disabled from a selection box on the Register Assignment dialog.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
71
Notes
Refer to the 5203/4 System Manual or the SCADAPack System Manual for further information on the
Status LED and Status Output.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
72
1.7.2
DIAG DNP Connection Status
Description
This module determines the connection status of a remote DNP station, by repeatedly
sending a short message to the selected remote station and monitoring the response.
The connection status information is assigned to an input register, which is updated
continuously.
One holding register is assigned to specify the repeat time period for polling the
remote station. A second holding register specifies the remote station address.
This register assignment is available for the SCADAPack 32 controller only.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
DIAG DNP connection status
No address is required
Input Register
Any unused input register
Same as start register
1 input register
Connection status:
0 = connection OK
1 = connection failed
Holding Register
First register of any unused block of 2
consecutive holding registers.
Last register of block
2 holding registers.
Configuration data
None
3xxxx
4xxxx
4xxxx +1
Holding Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
DNP station address
Repeat rate (in seconds) for connection request message
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
73
1.7.3
DIAG DNP Event Status Module
Description
This module provides diagnostic data about DNP change events. The number of change
events stored in the event buffers is totalled for all DNP classes, and for all DNP point types.
The status information is assigned to nine consecutive input registers. The input registers are
updated continuously with data concerning the DNP change events.
One coil register is assigned to clear the change event buffers. The data is cleared when the
coil register is set to 1. Once the data is cleared the coil register is automatically reset to 0.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
DIAG DNP event status
No address is required
Input Register
First register of any unused block of 9
consecutive input registers.
Last register of block
12 input registers
diagnostic data
Coil Register
Any unused coil register
Same as start register
1 coil register
clear event buffers
None
3xxxx
3xxxx +8
0xxxx
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register
+10
Start Register
+11
Assignment to Module Hardware
DNP event count for Binary Inputs
DNP event count for 16-bit Counter Inputs
DNP event count for 32-bit Counter Inputs
DNP event count for 16-bit Analog Inputs
DNP event count for 32-bit Analog Inputs
DNP event count for Short Float Analog Inputs
DNP event count for Class 1 Data
DNP event count for Class 2 Data
DNP event count for Class 3 Data
reserved for future use
reserved for future use
reserved for future use
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
74
Coil Register Data
Registers
Start Register
Assignment to Module Hardware
Clear change event buffers
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
75
1.7.4
DIAG DNP Port Status Module
Description
This module provides DNP diagnostic data for a specific communication port. Diagnostic
information is totaled for all DNP connections on the selected communication port.
The status information is assigned to nine consecutive input registers. The input registers are
updated continuously with the DNP diagnostic data.
One coil register is assigned to clear the diagnostic data. The data is cleared when the coil
register is set to 1. Once the data is cleared the coil register is automatically reset to 0.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
DIAG DNP port status
com1, com2, com3, com4, or LAN1
Input Register
First register of any unused block of 7
consecutive input registers.
Last register of block
10 input registers
diagnostic data
Coil Register
Any unused coil register
Same as start register
1 coil register
clear diagnostic data
None
3xxxx
3xxxx +6
0xxxx
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Assignment to Module Hardware
DNP message successes
Number of successful DNP message transactions initiated by this
station
DNP message failures
Number of failed DNP message transactions initiated by this station
DNP fails since last success
Number of consecutive failed DNP message transactions initiated by
this station since the last success
DNP format errors
Number of received DNP message frames with formatting errors
(including checksum errors and unrecognized commands)
DNP message frames received
Number of DNP message frames received
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
76
Registers
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Assignment to Module Hardware
DNP message frames sent
Number of DNP message frames sent. This includes any message
retries at application or data link layer.
DNP messages received
Number of complete DNP messages received
DNP messages sent
Number of complete DNP messages sent. This includes any
message retries at the application layer.
reserved for future use
reserved for future use
Coil Register Data
Registers
Start Register
Assignment to Module Hardware
Clear diagnostic data
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
77
1.7.5
DIAG DNP Station Status
Description
This module provides DNP diagnostic data for a specific DNP remote station address.
Diagnostic information is totaled for all DNP communication with the station.
The status information is assigned to nine consecutive input registers. The input registers are
updated continuously with data concerning the DNP status of the specific interface.
One coil register is assigned to clear the diagnostic data. The data is cleared when the coil
register is set to 1. Once the data is cleared the coil register is automatically reset to 0.
One holding register specifies the remote station address.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
DIAG DNP station status
No address is required
Input Register
First register of any unused block of 10
consecutive input registers.
Last register of block
10 input registers
diagnostic data
Coil Register
Any unused coil register
Same as start register
1 coil register
clear diagnostic data
Holding Register
Any unused holding register.
Same as start register
1 holding register.
DNP station address
None
3xxxx
3xxxx +9
0xxxx
4xxxx
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Assignment to Module Hardware
DNP message successes
Number of successful DNP message transactions initiated by this
station
DNP message failures
Number of failed DNP message transactions initiated by this station
DNP fails since last success
Number of consecutive failed DNP message transactions initiated by
this station since the last success
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
78
Registers
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Assignment to Module Hardware
DNP format errors
Number of received DNP message frames with formatting errors
(including checksum errors and unrecognized commands)
DNP message frames received
Number of DNP message frames received
DNP message frames sent
Number of DNP message frames sent. This includes any message
retries at application or data link layer.
DNP messages received
Number of complete DNP messages received
DNP messages sent
Number of complete DNP messages sent. This includes any
message retries at the application layer.
reserved for future use
reserved for future use
Coil Register Data
Registers
Start Register
Assignment to Module Hardware
Clear diagnostic data
Holding Register Data
Registers
Start Register
Assignment to Module Hardware
DNP station address
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
79
1.7.6
DIAG Force
Description
All user accessible Modbus registers in a SCADAPack controller can be forced to a desired
state or value. The DIAG Force module is used to determine if a Modbus register in a
SCADAPack controller is forced to some state or value. This module reads the ‘forced’ state
of a SCADAPack controller, and assigns it to one status register. The status register is
updated continuously with the current ‘forced’ state of the controller.
Note that the Force LED on SCADAPack controllers, excluding the SCADASense
programmable controllers, also indicates if a Modbus register is forced.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIAG Force
No physical address is required.
Status Register
Any unused status register.
1xxxx
Same as start register.
1 status register.
None
None
Register Data
Registers
Start Register
Assignment to Module Hardware
0 = Modbus register is not forced
1 = Modbus register is forced
Force LED:
0 = Force LED is OFF
1 = Force LED is ON
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
80
1.7.7
DIAG IP Connections
Description
The module, DIAG IP connections, provides a summary of the IP connections. The
connection information is assigned to three consecutive input registers. The input registers
are updated continuously with connection data.
This module is used by the SCADAPack 32 controller series only. The connection statistics
include all IP connection types.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIAG IP connections
No physical address is required.
Input Register
First register of any unused
3xxxx
block of 3 consecutive input
registers.
Last register of block
3xxxx + 2
3 input registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Assignment to Module Hardware
Number of current slave IP connections.
Number of current master IP connections.
Number of free IP connections.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
81
1.7.8
DIAG Logic Status
Description
The module, DIAG Logic Status, reads the Ladder Logic Application status in the RAM
and FLASH memory and assigns it to two input registers. The input registers are updated
continuously with the current application status.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
DIAG Logic Status
No physical address is required.
Input Register
Any unused input register.
3xxxx
Last register in block.
3xxxx+1
2 input registers
None
Input Register Data
Registers
Assignment to Module Hardware
Start Register
Ladder Logic Program Status
0 = No Program
1 = Program Stopped
2 = Program Running in Debug Mode
3 = Program Running
Type of memory where Ladder Logic program is loaded:
0 = No program in RAM or FLASH;
1 = Program loaded in RAM
2 = Program loaded in FLASH
3 = Program loaded in RAM and FLASH
Start Register + 1
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
82
1.7.9
DIAG Modbus Protocol Status
Description
The module, DIAG Modbus protocol status, provides diagnostic data about Modbus
protocols for a specific communication interface. Diagnostic information is totaled for all
Modbus protocols on the selected communication interface. When multiple Modbus IP
connections exist on the same interface, diagnostic information is totaled for all connections.
This module is used by the SCADAPack 32 controller series only.
The status information is assigned to nine consecutive input registers. The input registers are
updated continuously with data concerning the Modbus protocol status of the specific
interface.
One coil register is assigned to clear the diagnostic data. The data is cleared when the coil
register is set to 1. Once the data is cleared the coil register is automatically reset to 0.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
DIAG Modbus protocol status
com1, com2, com3, com4, or Ethernet1
Input Register
First register of any unused block of 9
consecutive input registers.
Last register of block
9 input registers
diagnostic data
Coil Register
Any unused coil register.
Same as start register.
1 coil register.
clear diagnostic data
None
3xxxx
3xxxx +8
0xxxx
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Assignment to Module Hardware
Modbus command errors
Modbus format errors
Modbus checksum errors
Modbus slave commands received
Modbus master commands sent
Modbus master responses received
Modbus slave responses sent
Modbus stored messages
Modbus forwarded messages
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
83
Coil Register Data
Registers
Start Register
Assignment to Module Hardware
Clear diagnostic data
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
84
1.7.10
DIAG Serial Port Comm. Status
Description
The module, DIAG Serial port comm. status, provides diagnostic data about a specific
serial port. The status information is assigned to five consecutive input registers. The input
registers are updated continuously with data concerning the communication status of the
serial port.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIAG Serial port comm. Status
com1, com2, com3, or com4.
Input Register
First register of any unused
block of 5 consecutive input
registers.
Last register of block
5 input registers.
None
None
3xxxx
3xxxx + 4
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Assignment to Module Hardware
Framing errors
Parity errors
Character overrun errors
Buffer overrun errors
Integer value indicating the status of
Port I/O lines CTS and DCD:
The LSB = state of the CTS line.
Second to LSB = state of DCD input
Example:
Value of 3 implies CTS and DCD is
ON.
Value of 1 implies CTS is ON and DCD
is OFF.
Notes
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported
only when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported
only when the SCADAPack 5602 I/O module is installed. To optimize performance,
minimize the length of messages on com3 and com4. Examples of recommended uses for
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
85
com3 and com4 are for local operator terminals, and for programming and diagnostics using
the TelePACE program.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
86
1.7.11
DIAG Serial Port Protocol Status
Description
The module, DIAG Serial port protocol status, provides diagnostic data about a specific
serial port. The status information is assigned to ten consecutive input registers. The input
registers are updated continuously with data concerning the protocol status of the serial port.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIAG Serial port comm. Status
com1, com2, com3, or com4.
Input Register
First register of any unused
block of 10 consecutive input
registers.
Last register of block
10 input registers.
None
None
3xxxx
3xxxx + 9
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Assignment to Module Hardware
Protocol command errors
Protocol format errors
Protocol checksum errors
Protocol slave commands received
Protocol master commands sent
Protocol master responses received
Protocol slave responses sent
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
87
Registers
Start Register + 7
Start Register + 8
Start Register + 9
Assignment to Module Hardware
Protocol master command status
0 = message sent, waiting for response
1 = response received, no error occurred
2 = not used
3 = bad value in function code register
4 = bad value in slave controller address register
5 = bad value in slave register address
6 = bad value in length register
7 = serial port or protocol is invalid
8 = not used
9 = specified protocol is not supported by this controller
11 = an unexpected length response was received
This means corrupt messages for regular Modbus. Check the
format and checksum counters. For Enron Modbus, this is
normal.
12 = response timeout
24 = exception response: invalid function code
25 = exception response: invalid address
26 = exception response: invalid value
27 = protocol is invalid or serial port queue is full
28 = slave and master stations are equal; they must be different
29 = exception response: slave device failure
30 = exception response: slave device busy
Protocol stored messages
Protocol forwarded messages
Notes
For SCADAPack, SCADAPack Light and SCADAPack Plus controllers Com3 is supported
only when the SCADAPack 5601 and 5604 I/O module is installed. Com4 is supported
only when the SCADAPack 5602 I/O module is installed. To optimize performance,
minimize the length of messages on com3 and com4. Examples of recommended uses for
com3 and com4 are for local operator terminals, and for programming and diagnostics using
the TelePACE program.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
88
1.8
Digital Input I/O Modules
Digital input modules are used to assign data from physical digital inputs to status registers
in the I/O Database. The physical digital inputs are specific 5000 Series I/O modules,
generic I/O modules, and controller digital inputs.
Digital input modules may assign data to any status registers in the I/O database that are not
being used by another Digital input module. There are 4096 I/O database status registers
available. These status registers are numbered 10001 - 14096. Status registers are referred to
as 1xxxx registers throughout this manual.
All I/O database status registers that are not assigned to any other I/O modules may be used
as general-purpose status registers in a ladder program. The I/O modules available are
described in the following pages.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
89
1.8.1
DIN Controller Digital Inputs
Description
The module, DIN controller digital inputs, reads the three digital inputs on the Micro16,
SCADAPack, SCADAPack Light, SCADAPack, SCADAPack Plus, SCADAPack 32 and
SCADAPack 32P controllers. Data is assigned to three consecutive status registers. The
status registers are updated continuously with data read from the digital inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN controller digital inputs
No physical address is required.
Status Register
First register of any unused
1xxxx
block of 3 consecutive status
registers.
Last register of block
1xxxx + 2
3 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Assignment to Module Hardware
Controller board digital input 0
Controller board digital input 1
Controller board digital input 2
Notes
Refer to the Hardware User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
90
1.8.2
DIN Controller Interrupt Input
Description
The module, DIN controller interrupt input, reads the state of the interrupt input on the
Micro16, SCADAPack, SCADAPack Light, SCADAPack, SCADAPack Plus, SCADAPack
32 and SCADAPack 32P controllers. Data is assigned to one status register. The status
register is updated continuously with the state of the interrupt input.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN controller interrupt input
No physical address is required.
Status Register
Any unused status register.
1xxxx
Same as start register.
1 status registers.
None
None
Register Data
Registers
Start Register
Assignment to Module Hardware
Controller board Interrupt Input
Notes
Refer to the Hardware User Manual for further information on the Controller interrupt input.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
91
1.8.3
DIN Controller Option Switches
Description
The module, DIN Controller option switches, reads the state of the three option switches
on the Micro16, SCADAPack, SCADAPack Light, SCADAPack, SCADAPack Plus,
SCADAPack 32 and SCADAPack 32P controllers. Data is assigned to three status registers.
The status registers are updated continuously with data read from the option switches.
Register Assignment
Module
DIN 5203/4 option switches
Address
No physical address is required.
Type
Status Register
Start
End
First register of any unused
block of 3 consecutive status
registers.
Last register of block
Registers
3 status registers.
Description
None
Extended Parameters
None
1xxxx
1xxxx + 2
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Assignment to Module Hardware
Controller board option switch 1
Controller board option switch 2
Controller board option switch 3
Notes
The option switches are also used as configuration switches for the SCADAPack I/O
modules. Refer to these I/O modules for details.
Refer to the 5203/4 System Manual or the SCADAPack System Manual for further
information on the controller option switches.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
92
1.8.4
DIN SCADAPack 32 Option Switches
Description
The module, DIN SCADAPack 32 option switches, reads the state of the four option
switches on the SCADAPack 32 controller board. Data is assigned to four status registers.
The status registers are updated continuously with data read from the option switches.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN SCADAPack 32 option switches
No physical address is required.
Status Register
First register of any unused
1xxxx
block of 4 consecutive status
registers.
Last register of block
1xxxx + 3
4 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Controller board option switch 1
Controller board option switch 2
Controller board option switch 3
Controller board option switch 4
Notes
The option switches are also used as configuration switches for the SCADAPack I/O
modules. Refer to these I/O modules for details.
Refer to the SCADAPack 32 System Manual for further information on the controller option
switches.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
93
1.8.5
DIN 5401 Module
Description
The DIN 5401 module provides eight digital inputs. Data is assigned to eight consecutive
status registers. The status registers are updated continuously with data read from the digital
inputs.
When there are digital outputs being used in combination with digital inputs on the 5401, a
full 8 status registers must still be assigned to the DIN 5401 module. When this is the case,
a DOUT 5401 module must also be added to the Register Assignment with the same
module address.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN 5401 module
This module is assigned a unique module
address between 0 and 7. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 8 consecutive status
registers.
Last register of block
1xxxx + 7
8 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Notes
Refer to the 5401 Digital I/O Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
94
1.8.6
DIN 5402 Module
Description
The DIN 5402 module provides sixteen digital inputs. Data is assigned to sixteen
consecutive status registers. The status registers are updated continuously with data read
from the digital inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN 5402 module
This module is assigned a unique module
address between 0 and 15. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 16 consecutive
status registers.
Last register of block
1xxxx + 15
16 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Digital input 13
Digital input 14
Digital input 15
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
95
Notes
Refer to the 5402 Digital I/O Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
96
1.8.7
DIN 5403 Module
Description
The DIN 5403 module provides eight digital inputs. Data is assigned to eight consecutive
status registers. The status registers are updated continuously with data read from the digital
inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN 5403 module
This module is assigned a unique module
address between 0 and 7. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 8 consecutive status
registers.
Last register of block
1xxxx + 7
8 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Notes
Refer to the 5403 Digital Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
97
1.8.8
DIN 5404 Module
Description
The DIN 5404 module provides sixteen digital inputs. Data is assigned to sixteen
consecutive status registers. The status registers are updated continuously with data read
from the digital inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN 5404 module
This module is assigned a unique module
address between 0 and 15. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 16 consecutive
status registers.
Last register of block
1xxxx + 15
16 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Digital input 13
Digital input 14
Digital input 15
Notes
Refer to the 5404 Digital Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
98
1.8.9
DIN 5405 Module
Description
The DIN 5405 module provides thirty-two digital inputs. Data is assigned to thirty-two
consecutive status registers. The status registers are updated continuously with data read
from the digital inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN 5404 module
This module is assigned a unique module
address between 0 and 15. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 32 consecutive
status registers.
Last register of block
1xxxx + 31
32 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Start Register + 16
Start Register + 17
Start Register + 18
Start Register + 19
Start Register + 20
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Digital input 13
Digital input 14
Digital input 15
Digital input 16
Digital input 17
Digital input 18
Digital input 19
Digital input 20
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
99
Registers
Start Register + 21
Start Register + 22
Start Register + 23
Start Register + 24
Start Register + 25
Start Register + 26
Start Register + 27
Start Register + 28
Start Register + 29
Start Register + 30
Start Register + 31
Assignment to Module Hardware
Digital input 21
Digital input 22
Digital input 23
Digital input 24
Digital input 25
Digital input 26
Digital input 27
Digital input 28
Digital input 29
Digital input 30
Digital input 31
Notes
Refer to the 5405 Digital Input Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
100
1.8.10
DIN 5421 Module
Description
The DIN 5421 module provides eight digital inputs. Data is assigned to eight consecutive
status registers. The status registers are updated continuously with data read from the digital
inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN 5421 module
This module is assigned a unique module
address between 0 and 7. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 8 consecutive status
registers.
Last register of block
1xxxx + 7
8 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Notes
Refer to the 5421 Switch Input Module Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
101
1.8.11
DIN Generic 16 Point Module
Description
The DIN Generic 16 point module provides sixteen digital inputs. Data is assigned to
sixteen consecutive status registers. The status registers are updated continuously with data
read from the digital inputs. The DIN Generic 16 point module may be used in place of
any other 16 point DIN-type module.
The DIN Generic 16 point module type is a useful selection early on in the system design
stage before the final selection of the specific DIN module type is known.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN Generic 16 point module
This module is assigned a unique module
address between 0 and 15. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 16 consecutive
status registers.
Last register of block
1xxxx + 15
16 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Digital input 13
Digital input 14
Digital input 15
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
102
Notes
For further information, refer to the User Manual for the specific 16 point DIN module
used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
103
1.8.12
DIN Generic 8 Point Module
Description
The DIN Generic 8 point module provides eight digital inputs. Data is stored in eight
consecutive status registers. The status registers are updated continuously with data read
from the digital inputs. The DIN Generic 8 point module may be used in place of any other
8 point DIN-type module.
The DIN Generic 8 point module type is a useful selection early on in the system design stage
before the final selection of the specific DIN module type is known.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DIN Generic 8 point module
This module is assigned a unique module
address between 0 and 7. No other DINtype module may use this module address.
Status Register
First register of any unused
1xxxx
block of 8 consecutive status
registers.
Last register of block
1xxxx + 7
8 status registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Notes
For further information, refer to the User Manual for the specific 8 point DIN module used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
104
1.9
Digital Output I/O Modules
Digital output modules are used to assign data from the I/O Database to physical digital
outputs. The physical digital outputs are specific 5000 Series I/O modules or generic I/O
modules.
Digital output modules may assign data to any coil registers in the I/O database that are not
being used by another Digital output module. There are 4096 I/O database coil registers
available. These coil registers are numbered 00001 - 04096. Coil registers are referred to as
0xxxx registers throughout this manual.
All I/O database coil registers that are not assigned to any other I/O modules may be used as
general-purpose coil registers in a ladder program. The I/O modules available are described
in the following pages.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
105
1.9.1
DOUT 5401 Module
Description
The DOUT 5401 module provides eight digital outputs. Data is assigned from eight
consecutive coil registers. The digital outputs are updated continuously with data read from
the coil registers.
When there are digital inputs being used in combination with digital outputs on the 5401, a
full 8 coil registers must still be assigned to the DOUT 5401 module. When this is the case,
a DIN 5401 module must also be added to the Register Assignment with the same module
address.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT 5401 module
This module is assigned a unique module
address between 0 and 7. No other DOUTtype module may use this module address.
Coil Register
First register of any unused
0xxxx
block of 8 consecutive coil
registers.
Last register of block
0xxxx + 7
8 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Notes
Refer to the 5401 Digital I/O Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
106
1.9.2
DOUT 5402 Module
Description
The DOUT 5402 module provides sixteen digital outputs. Data is assigned from sixteen
consecutive coil registers. The digital outputs are updated continuously with data read from
the coil registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT 5402 module
This module is assigned a unique module
address between 0 and 15. No other
DOUT-type module may use this module
address.
Coil Register
First register of any unused
0xxxx
block of 16 consecutive coil
registers.
Last register of block
0xxxx + 15
16 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Digital output 8
Digital output 9
Digital output 10
Digital output 11
Digital output 12
Digital output 13
Digital output 14
Digital output 15
Notes
Refer to the 5402 Digital I/O Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
107
1.9.3
DOUT 5406 Module
Description
The DOUT 5406 module provides sixteen digital outputs. Data is assigned from sixteen
consecutive coil registers. The digital outputs are updated continuously with data read from
the coil registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT 5406 module
This module is assigned a unique module
address between 0 and 15. No other
DOUT-type module may use this module
address.
Coil Register
First register of any unused
0xxxx
block of 16 consecutive coil
registers.
Last register of block
0xxxx + 15
16 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Digital output 8
Digital output 9
Digital output 10
Digital output 11
Digital output 12
Digital output 13
Digital output 14
Digital output 15
Notes
Refer to the 5406 Digital Output Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
108
1.9.4
DOUT 5407 Module
Description
The DOUT 5407 module provides eight digital outputs. Data is assigned from eight
consecutive coil registers. The digital outputs are updated continuously with data read from
the coil registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT 5407 module
This module is assigned a unique module
address between 0 and 7. No other DOUTtype module may use this module address.
Coil Register
First register of any unused
0xxxx
block of 8 consecutive coil
registers.
Last register of block
0xxxx + 7
8 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Notes
Refer to the 5407 Relay Output Module Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
109
1.9.5
DOUT 5408 Module
Description
The DOUT 5408 module provides eight digital outputs. Data is assigned from eight
consecutive coil registers. The digital outputs are updated continuously with data read from
the coil registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT 5408 module
This module is assigned a unique module
address between 0 and 7. No other DOUTtype module may use this module address.
Coil Register
First register of any unused
0xxxx
block of 8 consecutive coil
registers.
Last register of block
0xxxx + 7
8 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Notes
Refer to the 5408 Digital Output Module Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
110
1.9.6
DOUT 5409 Module
Description
The DOUT 5409 module provides eight digital outputs. Data is assigned from eight
consecutive coil registers. The digital outputs are updated continuously with data read from
the coil registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT 5409 module
This module is assigned a unique module
address between 0 and 7. No other DOUTtype module may use this module address.
Coil Register
First register of any unused
0xxxx
block of 8 consecutive coil
registers.
Last register of block
0xxxx + 7
8 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Notes
Refer to the 5409 Digital Output Module Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
111
1.9.7
DOUT 5411 Module
Description
The DOUT 5411 module provides thirty-two digital outputs. Data is assigned from thirtytwo consecutive coil registers. The digital outputs are updated continuously with data read
from the coil registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT 5411 module
This module is assigned a unique module
address between 0 and 15. No other
DOUT-type module may use this module
address.
Coil Register
First register of any unused
0xxxx
block of 32 consecutive coil
registers.
Last register of block
0xxxx + 31
32 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Start Register + 16
Start Register + 17
Start Register + 18
Start Register + 19
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Digital output 8
Digital output 9
Digital output 10
Digital output 11
Digital output 12
Digital output 13
Digital output 14
Digital output 15
Digital output 16
Digital output 17
Digital output 18
Digital output 19
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
112
Registers
Start Register + 20
Start Register + 21
Start Register + 22
Start Register + 23
Start Register + 24
Start Register + 25
Start Register + 26
Start Register + 27
Start Register + 28
Start Register + 29
Start Register + 30
Start Register + 31
Assignment to Module Hardware
Digital output 20
Digital output 21
Digital output 22
Digital output 23
Digital output 24
Digital output 25
Digital output 26
Digital output 27
Digital output 28
Digital output 29
Digital output 30
Digital output 31
Notes
Refer to the 5411 Digital Output Module User Manual for further information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
113
1.9.8
DOUT Generic 16 Point Module
Description
The DOUT Generic 16 point module provides sixteen digital outputs. Data is assigned
from sixteen consecutive coil registers. The digital outputs are updated continuously with
data read from the coil registers. The DOUT Generic 16 point module may be used in
place of any other 16 point DOUT-type module.
The DOUT Generic 16 point module type is a useful selection early on in the system
design stage before the final selection of the specific DOUT module type is known.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
Generic 16 point module
This module is assigned a unique module
address between 0 and 15. No other
DOUT-type module may use this module
address.
Coil Register
First register of any unused
0xxxx
block of 16 consecutive coil
registers.
Last register of block
0xxxx + 15
16 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Digital output 8
Digital output 9
Digital output 10
Digital output 11
Digital output 12
Digital output 13
Digital output 14
Digital output 15
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
114
Notes
For further information, refer to the Digital Output Module User Manual for the specific 16point DOUT module used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
115
1.9.9
DOUT Generic 8 Point Module
Description
The DOUT Generic 8 point module provides eight digital outputs. Data is assigned from
eight consecutive coil registers. The digital outputs are updated continuously with data read
from the coil registers. The DOUT Generic 8 point module may be used in place of any
other 8 point DOUT-type module.
The DOUT Generic 8 point module type is a useful selection early on in the system design
stage before the final selection of the specific DOUT module type is known.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
DOUT Generic 8 point module
This module is assigned a unique module
address between 0 and 7. No other DOUTtype module may use this module address.
Coil Register
First register of any unused
0xxxx
block of 8 consecutive coil
registers.
Last register of block
0xxxx + 7
8 coil registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Notes
For further information, refer to the Digital Output Module Manual for the specific 8 point
DOUT module used.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
116
1.10
SCADAPack and SCADASense Series I/O Modules
SCADAPack and SCADASense Series I/O modules assign data from registers to physical
outputs, and assign data from physical inputs to registers. These I/O modules provide analog
I/O points, digital I/O points and may assign data to registers that are not used by any other
I/O module.
The following modules interface with SCADAPack and SCADASense Series I/O hardware.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
117
1.10.1
4202 DR Extended/4203 DR IO
Description
The SCADASense 4203 DR, and a SCADASense 4202 DR manufactured after July 13,
2004, may use the 4202 DR Extended/4203 DR I/O register assignment. The 4202 DR must
have controller board version 5 and terminal board version 6.
A SCADASense 4203 DR, or 4202 DR with Extended I/O, provides one digital point, which
may operate as a digital input/counter or as a digital output. The digital output shares the
same physical connections as the digital input. When the output is turned OFF, the point
may be used as input. When the output is turned on it functions only as a digital output.
Digital point data is assigned to a single coil register and a single status register. The coil
register is updated continuously with data read from the coil register. The status register is
updated continuously with data read from the digital input.
Analog and counter input data is assigned to five consecutive input registers. One input
register is used to monitor the controller input power and two counter input double registers
(32 bit). These input registers are updated continuously with data read from the analog
inputs and counter input.
Analog output data is assigned to a single analog output register. The analog output is
updated continuously with the data read from the holding register.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
4202 DR Extended/4203 DR I/O Module
Fixed
Coil Register
Any unused coil register.
Same as first register.
1 coil registers
digital output
Status Register
Any unused status register
Same as first register.
1 status register
Digital input
Input Register
First register of any unused block of 5
consecutive status registers.
Last register of block
5 input registers
Analog and counter inputs
Analog Output Register
Any unused analog output register
Same as first register
1 analog output register
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
0xxxx
0xxxx
1xxxx
1xxxx
3xxxx
3xxxx + 4
4xxxx
4xxxx
118
Description
Extended Parameters
Analog outputs
None
Coil Register Data
Registers
Start Register
Assignment to Module Hardware
Digital output 0
Status Register Data
Registers
Start Register
Assignment to Module Hardware
Digital input 0
Analog and Counter Input Register Data
Registers
Start Register
Start Register + 1 and +2
Start Register + 3 and +4
Assignment to Module Hardware
Analog input Supply Voltage (mV)
Counter input, 32 bit register
Counter input, 32 bit register
Analog Output Register Data
Registers
Start Register
Assignment to Module Hardware
Analog output – Input Voltage (mV)
Notes
Only one 4202 DR Extended/4203 DR I/O may be assigned.
Refer to the SCADASense 4202 DR Hardware Manual for information on analog and
digital I/O usage.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
119
1.10.2
4202 DR I/O
Description
Digital input data is assigned to a single status register. The status register is updated
continuously with data read from the digital input.
Analog and counter input data is assigned to five consecutive input registers. One input
register is used to monitor the controller input power and two counter input double registers
(32 bit). These input registers are updated continuously with data read from the analog
inputs and counter input.
Analog output data is assigned to a single analog output register. The analog output is
updated continuously with the data read from the holding register.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
4202 DR I/O Module
Fixed
Status Register
Any unused status register
Same as first register.
1 status register
Digital input
Input Register
First register of any unused block of 5
consecutive status registers.
Last register of block
5 input registers
Analog and counter inputs
Analog Output Register
Any unused analog output register
Same as first register
1 analog output register
Analog outputs
None
1xxxx
1xxxx
3xxxx
3xxxx + 4
4xxxx
4xxxx
Status Register Data
Registers
Start Register
Assignment to Module Hardware
Digital input 0
Analog and Counter Input Register Data
Registers
Start Register
Start Register + 1 and +2
Assignment to Module Hardware
Analog input Supply Voltage (mV)
Counter input, 32 bit register
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
120
Registers
Start Register + 3 and +4
Assignment to Module Hardware
Counter input, 32 bit register
Analog Output Register Data
Registers
Start Register
Assignment to Module Hardware
Analog output – Input Voltage (mV)
Notes
Only one 4202 DR I/O may be assigned.
Refer to the SCADASense 4202 DR Hardware Manual for information on analog and
digital I/O usage.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
121
1.10.3
4202/4203 DS I/O
Description
The 4202/4203 DS I/O register assignment is used for the SCADASense DS Series of controllers
(4202 DS and 4203 DS). This module provides two digital input/output (I/O) points point. The first
DI/O point may be used as a digital input/counter or as a digital output. The digital output shares the
same physical connections as the digital input/counter. When the output is turned OFF, the point
may be used as input/counter. When the output is turned on it functions only as a digital output.
Digital point data is assigned to a single coil register and a single status register. The coil register is
updated continuously with data read from the coil register. The status register is updated
continuously with data read from the digital input.
The second DI/O point may be used as a turbine meter counter input or as a digital output. The
digital output shares the same physical connections as the turbine meter counter input. When the
output is turned OFF, the point may be used as a turbine meter counter input. When the output is
turned on it functions only as a digital output. Digital point data is assigned to a single coil register.
The coil register is updated continuously with data read from the coil register.
Analog and counter input data is assigned to seven consecutive input registers. Two input registers
are used for the two analog inputs; one input register is used to monitor the controller input power;
two input registers are used for the counter input (32 bit double word uses two registers) and two
input registers are used for the turbine meter counter input (32 bit double word uses two registers).
These input registers are updated continuously with data read from the analog inputs and counter
inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
4202/4203 DS I/O Module
Fixed
Coil Register
Any unused coil register.
Last register of block.
2 coil registers
Digital output
Status Register
Any unused status register
Same as first register.
1 status register
Digital input
Input Register
First register of any unused block of 7
consecutive status registers.
Last register of block
7 input registers
Analog and counter inputs
None
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
0xxxx
0xxxx + 1
1xxxx
1xxxx
3xxxx
3xxxx + 6
122
Coil Register Data
Registers
Start Register
Start Register +1
Assignment to Module Hardware
Digital output 0
Digital output 1
Status Register Data
Registers
Start Register
Assignment to Module Hardware
Digital input 0
Analog and Counter Input Register Data
Registers
Start Register
Start Register +1
Start Register +2
Start Register +3 and +4
Start Register +5 and +6
Assignment to Module Hardware
Analog Input 0
Analog Input 1
Analog input Supply Voltage (mV)
Counter 0 input, 32 bit register
Counter 1 input, 32 bit register
Notes
Only one 4202/4203 DS I/O may be assigned.
Refer to the SCADASense 4202 DS Hardware Manual for information on analog and
digital I/O usage.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
123
1.10.4
SCADAPack AOUT Module
Description
The SCADAPack AOUT module provides two analog outputs. Data is read from two consecutive
holding (4xxxx) registers. The analog outputs are updated continuously with the data read from the
holding registers.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Extended Parameters
SCADAPack AOUT module
This module has a fixed module address of
0. No other AOUT-type module may use
this module address when this module is
used.
Holding Register
First register of any unused
4xxxx
block of 2 consecutive holding
registers.
Last register of block
4xxxx + 1
2 holding registers.
None
None
Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Analog output 0
Analog output 1
Output Range Selection
The SCADAPack Option Switch 2 selects the signal range. Both analog outputs are set to
the same range.
The figure below shows the switch settings for selecting the output range.
0-20 mA Outputs
0
1
2
H/W RST
1
2
3
4-20 mA Outputs
0
1
2
H/W RST
1
2
3
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
How to Set the Range Switch
• Determine the desired range.
• Press the side of the switch
shown in gray.
Press this side
for 0-20 mA
Press this side
for 4-20 mA
124
Notes
Refer to the SCADAPack Hardware Manual for further information on the option
switches.
Option Switch 2 functions as the Output Range Switch regardless of whether the module,
5203/4 option switches, is added to the Register Assignment or not.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
125
1.10.5
SCADAPack 5601 I/O Module
Description
Digital output data is assigned from twelve consecutive coil registers. The digital outputs are
updated continuously with data read from the coil registers.
Digital input data is assigned to sixteen consecutive status registers. The status registers are
updated continuously with data read from the digital inputs.
Analog input data is assigned to eight consecutive input registers. The input registers are
updated continuously with data read from the analog inputs.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
SCADAPack 5601 I/O Module
fixed at 0
Coil Register
First register of any unused block of 12
consecutive coil registers.
Last register of block
12 coil registers
digital outputs
Status Register
First register of any unused block of 16
consecutive status registers.
Last register of block
16 status registers
digital inputs
Input Register
First register of any unused block of 8
consecutive input registers.
Last register of block
8 input registers
analog inputs
None
0xxxx
0xxxx + 11
1xxxx
1xxxx + 15
3xxxx
3xxxx +7
Coil Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
126
Registers
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Assignment to Module Hardware
Digital output 8
Digital output 9
Digital output 10
Digital output 12
Status Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Digital input 13
Digital input 14
Digital input 15
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Analog Input Measurement Range Selection
The SCADAPack Option Switch 1 selects the measurement range. All 8 analog inputs are
set to the same range.
The figure below shows the switch settings for selecting the measurement range.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
127
0-20 mA (0-5 V) AINs
4-20 mA (1-5 V) AINs
0
1
2
H/W RST
1
2
3
0
1
2
H/W RST
1
2
3
How to Set the Range Switch
Determine the desired range.
Press the side of the switch
shown in gray.
•
•
Press this side
for 0-20 mA
(0-5 V)
Press this side
for 4-20 mA
(1-5 V)
Line Frequency Selection
The SCADAPack I/O board may select 50 or 60 Hz line frequency for digital and analog
input processing. The SCADAPack Option Switch 3 selects this option. The figure below
shows the switch settings for selecting the line frequency.
60 Hz Operation
0
1
2
H/W RST
1
2
3
50 Hz Operation
0
1
2
H/W RST
1
2
3
How to Set the Frequency Switch
• Determine the frequency.
• Press the side of the switch
shown in gray.
Press this side
for 60 Hz
Press this side
for 50 Hz
Notes
Only one SCADAPack 5601 or 5604 I/O module may be assigned to the same controller.
Option switches 1 and 3 function as described above regardless of whether the module, DIN
5203/4 option switches, is added to the Register Assignment or not.
Refer to the SCADAPack Hardware Manual for information on the option switches.
Two analog outputs are available for the SCADAPack 5601 I/O module. Refer to the
SCADAPack AOUT module for more information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
128
1.10.6
SCADAPack 5602 I/O Module
Description
Digital output data is assigned from two consecutive coil registers. The digital outputs are
updated continuously with data read from the coil registers.
Analog input data is assigned to five consecutive input registers. The input registers are
updated continuously with data read from the analog inputs.
The same five analog inputs are also read as digital inputs. The digital input data is assigned
to five consecutive status registers. The status registers are updated continuously with data
read from the analog inputs.
A digital input is ON if the corresponding filtered analog input value is greater than or equal
to 20% of its full-scale value, otherwise it is OFF.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
SCADAPack 5602 I/O Module
fixed at 0
Coil Register
First register of any unused block of 2
consecutive coil registers.
Last register of block
2 coil registers
digital outputs
Status Register
First register of any unused block of 5
consecutive status registers.
Last register of block
5 status registers
analog inputs read as digital inputs
Input Register
First register of any unused block of 5
consecutive input registers.
Last register of block
5 input registers
analog inputs
None
0xxxx
0xxxx + 1
1xxxx
1xxxx + 4
3xxxx
3xxxx +4
Coil Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Digital output 0
Digital output 1
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
129
Status Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Assignment to Module Hardware
Analog input 0 *
Analog input 1 *
Analog input 2 *
Analog input 3 *
Analog input 4 *
* Analog inputs are read again as digital inputs.
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog Input Measurement Range Selection
The SCADAPack Option Switch 1 selects the measurement range. All 5 analog inputs are
set to the same range.
The figure below shows the switch settings for selecting the measurement range.
0-20 mA (0-5 V) AINs
4-20 mA (1-5 V) AINs
0
1
2
H/W RST
1
2
3
0
1
2
H/W RST
1
2
3
How to Set the Range Switch
Determine the desired range.
Press the side of the switch
shown in gray.
•
•
Press this side
for 0-20 mA
(0-5 V)
Press this side
for 4-20 mA
(1-5 V)
Line Frequency Selection
The SCADAPack I/O board may select 50 or 60 Hz line frequency for analog input
processing. The SCADAPack Option Switch 3 selects this option. The figure below shows
the switch settings for selecting the line frequency.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
130
60 Hz Operation
0
1
2
H/W RST
1
2
3
50 Hz Operation
0
1
2
H/W RST
1
2
3
How to Set the Frequency Switch
Determine the frequency.
Press the side of the switch
shown in gray.
•
•
Press this side
for 60 Hz
Press this side
for 50 Hz
Notes
Only one SCADAPack 5602 I/O module may be assigned to the same controller. Option
switches 1 and 3 function as described above regardless of whether the module, DIN 5203/4
option switches, is added to the Register Assignment or not. Refer to the SCADAPack
Hardware Manual for information on the option switches.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
131
1.10.7
SCADAPack 5604 I/O Module
Description
The SCADAPack 5604 I/O Module is comprised of four different types of I/O channels.
The SCADAPack 5604 I/O hardware contains ten analog inputs, two analog outputs, thirtyfive digital inputs and thirty-six digital outputs.
The analog input assignment provides ten I/O channels for the analog input data from the
SCADAPack 5604 I/O Module hardware.
•
Analog input channels 0 to 7 provide eight external analog inputs (0-10V or 0-40mA)
•
Analog input channel 8 provides an external analog input for battery monitoring (0 to
32.768V)
•
Analog input channel 9 provides an internal analog input for DC/DC converter
monitoring.
The analog output assignment provides two I/O channels for the analog output data for the
SCADAPack 5604 I/O Module hardware.
The digital input assignment provides thirty-five I/O channels for the digital input data
from the SCADAPack 5604 I/O Module hardware.
The SCADAPack 5604 I/O Module provides thirty-two universal digital inputs or outputs.
The inputs are for use with dry contacts such as switches and relay contacts.
•
These are defined as digital input channels 0 to 31.
0 = contact open (LED off)
1 = contact closed (LED on)
The SCADAPack 5604 I/O Module also provides three internal digital inputs.
•
Digital input channel 32 returns the DC/DC converter status.
0 = DC/DC converter off
1 = DC/DC converter on
•
Digital input channel 33 returns the DC/DC converter over current status.
0 = Over current not detected
1 = Over current detected
•
Digital output channel 34 returns the digital output mismatch status.
0 = No mismatch
1 = One or more digital outputs mismatch
The digital output assignment provides thirty-six I/O channels for the digital outputs of the
SCADAPack 5604 I/O Module I/O hardware.
The SCADAPack 5604 I/O Module provides thirty-two universal digital inputs or
outputs. Outputs are open-collector/open drain type.
•
These are defined as digital output channels 0 to 31.
0 = output transistor off
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
132
1 = output transistor on
The SCADAPack 5604 I/O Module also provides two internal digital outputs.
•
Digital output channel 32 is used to control the DC/DC converter.
0 = DC/DC converter off
1 = DC/DC converter on
•
Digital output channel 33 is used to control the VLoop power supply.
0 = VLoop output off
1 = VLoop output on
•
Digital output channels 34 and 35 control the SCADAPack 5604 I/O Module Analog
Input filters.
Filter Setting
< 3 Hz
6 Hz
11 Hz
30 Hz
Digital Output 34
OFF
OFF
ON
ON
Digital Output 35
OFF
ON
OFF
ON
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
SCADAPack 5604 I/O Module
Fixed at 0
Coil Register
First register of any unused block of 36
consecutive coil registers.
Last register of block
36 coil registers
Digital outputs
Status Register
First register of any unused block of 35
consecutive status registers.
Last register of block
35 status registers
Digital inputs
Input Register
First register of any unused block of 10
consecutive input registers.
Last register of block
10 input registers
analog inputs
Holding Register
First register of any unused block of 2
consecutive holding registers.
Last register of block
2 input registers
analog outputs
None
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
0xxxx
0xxxx + 35
1xxxx
1xxxx + 34
3xxxx
3xxxx +9
4xxxx
4xxxx +1
133
Coil Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Start Register + 16
Start Register + 17
Start Register + 18
Start Register + 19
Start Register + 20
Start Register + 21
Start Register + 22
Start Register + 23
Start Register + 24
Start Register + 25
Start Register + 26
Start Register + 27
Start Register + 28
Start Register + 29
Start Register + 30
Start Register + 31
Start Register + 32
Start Register + 33
Start Register + 34
Start Register + 35
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Digital output 8
Digital output 9
Digital output 10
Digital output 11
Digital output 12
Digital output 13
Digital output 14
Digital output 15
Digital output 16
Digital output 17
Digital output 18
Digital output 19
Digital output 20
Digital output 21
Digital output 22
Digital output 23
Digital output 24
Digital output 25
Digital output 26
Digital output 27
Digital output 28
Digital output 29
Digital output 30
Digital output 31
Digital output 32
Digital output 33
Digital output 34
Digital output 35
Status Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
134
Registers
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Start Register + 16
Start Register + 17
Start Register + 18
Start Register + 19
Start Register + 20
Start Register + 21
Start Register + 22
Start Register + 23
Start Register + 24
Start Register + 25
Start Register + 26
Start Register + 27
Start Register + 28
Start Register + 29
Start Register + 30
Start Register + 31
Start Register + 32
Start Register + 33
Start Register + 34
Assignment to Module Hardware
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Digital input 13
Digital input 14
Digital input 15
Digital input 16
Digital input 17
Digital input 18
Digital input 19
Digital input 20
Digital input 21
Digital input 22
Digital input 23
Digital input 24
Digital input 25
Digital input 26
Digital input 27
Digital input 28
Digital input 29
Digital input 30
Digital input 31
Digital input 32
Digital input 33
Digital input 34
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
135
Holding Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Analog output 0
Analog output 1
Analog Input Measurement Range Selection
The SCADAPack Option Switch 1 selects the measurement range. All 8 analog inputs are
set to the same range.
The figure below shows the switch settings for selecting the measurement range.
0-20 mA (0-5 V) AINs
4-20 mA (1-5 V) AINs
0
1
2
H/W RST
1
2
3
0
1
2
H/W RST
1
2
3
How to Set the Range Switch
• Determine the desired range.
• Press the side of the switch
shown in gray.
Press this side
for 0-20 mA
(0-5 V)
Press this side
for 4-20 mA
(1-5 V)
Line Frequency Selection
The SCADAPack I/O board may select 50 or 60 Hz line frequency for digital and analog
input processing. The SCADAPack Option Switch 3 selects this option. The figure below
shows the switch settings for selecting the line frequency.
60 Hz Operation
0
1
2
H/W RST
1
2
3
50 Hz Operation
0
1
2
H/W RST
1
2
3
How to Set the Frequency Switch
• Determine the frequency.
• Press the side of the switch
shown in gray.
Press this side
for 60 Hz
Press this side
for 50 Hz
Notes
Only one SCADAPack 5601 or 5604 I/O module may be assigned to the same controller.
Option switches 1 and 3 function as described above regardless of whether the module, DIN
5203/4 option switches, is added to the Register Assignment or not.
Refer to the SCADAPack Hardware Manual for information on the option switches.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
136
Two analog outputs are available for the SCADAPack 5601 I/O module. Refer to the
SCADAPack AOUT module for more information.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
137
1.10.8
SCADAPack 5606 I/O Module
Description
The SCADAPack 5606 I/O Module is comprised of four types of I/O channels, digital inputs,
digital outputs, analog inputs, and analog outputs.
The digital input assignment provides forty I/O channels for the digital input data from the
SCADAPack 5606 I/O Module hardware.
•
The 5606 I/O Module provides thirty-two external digital inputs. These are externally wetted
inputs.
•
The module provides 8 internal digital inputs, which indicate if the corresponding analog input is
in or out of range.
The digital output assignment provides sixteen digital outputs. All are digital output relays.
The analog input assignment provides eight I/O channels for the analog input data from the
SCADAPack 5606 I/O Module hardware.
The analog output assignment provides two I/O channels for the analog output data for the
SCADAPack 5606 I/O Module hardware when the optional analog output module is installed.
Register Assignment
The register assignment for the SCADAPack 5606 I/O Module is used to configure the registers used
for the module data and the Extended Parameters available for the module. To open the register
assignment dialog for the SCADAPack 5606 I/O module:
•
Select Register Assignment from the Controller menu in TelePACE.
•
In the Register Assignment window select the Add button.
•
In the Add Register Assignment dialog select the SCADAPack 5606 I/O Module from the list
presented in the Module window.
The register assignment dialog for the SCADAPack 5606 I/O Module is shown below.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
138
The Module selection displays the name of the SCADAPack 5606 I/O module used for the register
assignment.
The Address selection displays the module address of the physical SCADAPack 5606 I/O module.
The address on the module is selected via dip switches on the module. A maximum of eight
SCADAPack 5606 I/O type modules may be added to a system.
The register type 0xxxx defines the register range for the digital output data. Sixteen sequential
registers are needed for the SCADAPack 5606 I/O module digital output data. Any unused block of
sixteen registers may be used. See the Digital Output Register Data section below for an
explanation of the digital output data.
The register type 1xxxx defines the register range for the digital input status data. Forty sequential
registers are needed for the SCADAPack 5606 I/O module digital Input data. Any unused block of
forty registers may be used. See the Digital Input Register Data section below for an explanation of
the digital input status data.
The register type 3xxxx defines the register range for the analog input data. Eight sequential registers
are needed for the SCADAPack 5606 I/O module analog input data. Any unused block of eight
registers may be used. See the Input Register Data section below for an explanation of the analog
input data.
The register type 4xxxx defines the register range for the analog output data. Two sequential
registers are needed for the SCADAPack 5606 I/O module analog output data. Any unused block of
two registers may be used. See the Analog Output Register Data section below for an explanation
of the analog output data.
The Extended Parameters grouping defines the type of data returned from the SCADAPack 5606
I/O module analog inputs, the type of analog output signal, filtering used by all analog inputs and the
scan frequency.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
139
The AIN Type selection for each input (AIN 0, 1, 2, 3, 4, 5, 6, and 7) defines the input measurement
type for the analog input.
•
The 0-5V selection sets the input type to measure 0 to 5V input signals.
•
The 1-5V selection sets the input type to measure 1 to 5V input signals.
•
The 0-20 mA selection sets the input type to measure 0 to 20mA input signals.
•
The 4-20 mA selection sets the input type to measure 4 to 20mA input signals.
The AIN Filter selection set the input filter for all analog inputs. Filtering is used to dampen process
variations or noise.
•
The 3 Hz filter selection sets the response time to 155ms at 60Hz and 185ms at 50Hz.
•
The 6 Hz filter selection sets response time to 85ms at 60Hz and 85ms at 50Hz.
•
The 11 Hz filter selection sets response time to 45ms at 60Hz and 55ms at 50Hz.
•
The 30 Hz filter selection sets response time to 30ms at 60Hz and 30ms at 50Hz.
The Scan Frequency selection set the input scan rate for all analog inputs. The scan rate selection is
not critical but AC noise rejection is improved at the correct frequency. If the module is used in a DC
environment, the 60 Hz setting will yield slightly faster response time.
•
The 60 Hz selection synchronies the input scanning to 60Hz.
•
The 50 Hz selection synchronies the input scanning to 50Hz.
The AOUT Type selection for each input (AOUT 0 and 1) defines the output signal type for the
analog output.
•
The 0-20 mA selection sets the output type for 0 to 20mA signals.
•
The 4-20 mA selection sets the output type for 4 to 20mA signals.
Digital Output Register Data
Digital output data is assigned to sixteen consecutive digital output (0xxxx) registers. The following
table begins at the Start address defined in the Register Assignment and continues for sixteen
registers.
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Assignment to Module Hardware
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
140
Registers
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
0 = OFF (relay open); 1= ON (relay closed)
Digital Input Register Data
Status register data is assigned to forty consecutive status (1xxxx) registers. The following table
begins at the Start address defined in the Register Assignment and continues for forty registers.
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Start Register + 16
Start Register + 17
Start Register + 18
Start Register + 19
Start Register + 20
Start Register + 21
Start Register + 22
Start Register + 23
Start Register + 24
Start Register + 25
Start Register + 26
Start Register + 27
Start Register + 28
Start Register + 29
Start Register + 30
Start Register + 31
Start Register + 32
Start Register + 33
Assignment to Module Hardware
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
0 = OFF (led off); 1= ON (led on)
OFF = AIN channel 0 is OK
ON = AIN channel 0 is over or under range
OFF = AIN channel 1 is OK
ON = AIN channel 1 is over or under range
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
141
Registers
Start Register + 34
Start Register + 35
Start Register + 36
Start Register + 37
Start Register + 38
Start Register + 39
Assignment to Module Hardware
OFF = AIN channel 2 is OK
ON = AIN channel 2 is over or under range
OFF = AIN channel 3 is OK
ON = AIN channel 3is over or under range
OFF = AIN channel 4 is OK
ON = AIN channel 4 is over or under range
OFF = AIN channel 5 is OK
ON = AIN channel 5 is over or under range
OFF = AIN channel 6 is OK
ON = AIN channel 6is over or under range
OFF = AIN channel 7 is OK
ON = AIN channel 7 is over or under range
Input Register Data
Input register data is assigned to eight consecutive analog input (3xxxx) registers. The following
table begins at the Start address defined in the Register Assignment and continues for eight
registers.
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Analog Output Register Data
Analog output register data is assigned to two consecutive analog output (4xxxx) registers. The
following table begins at the Start address defined in the Register Assignment.
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Analog input 0
Analog input 1
Notes
Refer to the SCADAPack Hardware Manual for information on the SCADAPack 5606 I/O
module.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
142
1.10.9
SCADAPack LP I/O
Description
The SCADAPack LP I/O Module is comprised of four different types of I/O channels. The
SCADAPack LP I/O hardware contains eight analog inputs, two analog outputs, sixteen digital
inputs and twelve digital outputs.
The analog input assignment provides seven I/O channels for the analog input data. Analog input
data is a signed value in the range –32768 to 32767.
•
Analog input channels 0 to 4 provide eight external analog inputs (0-10V or 0-40mA)
•
Analog input channel 5 provides an external analog input for battery monitoring (0 to 32.768V)
•
Analog input channel 6 provides an internal analog input for DC/DC converter monitoring.
The analog output assignment provides two I/O channels for the analog output data. Analog input
data is a signed value in the range –32768 to 32767.
The digital input assignment provides sixteen I/O channels for the digital input data.
The SCADAPack LP provides eight universal digital inputs or outputs. The inputs are for use with
dry contacts such as switches and relay contacts.
•
These are defined as digital input channels 0 to 7.
0 = contact open (LED off)
1 = contact closed (LED on)
The SCADAPack LP also provides eight internal digital inputs.
•
Digital input channel 8 returns the Com1 (RS-485) power status.
0 = off
1 = on
•
Digital input channel 9 returns the Com3 (HMI) power output status.
0 = off
1 = on
•
Digital input channel 10 returns the VLOOP output status.
0 = off
1 = on
•
Digital input channel 11 returns the DC/DC converter status. This bit reports the true status of
the DC/DC converter. If over-current causes the converter to be turned off, this bit will clear.
0 = off
1 = on
•
Digital input channel 12 returns the VLOOP over-current status. This indicates VLOOP overcurrent has been detected. This input clears when VLOOP output is off, or the over-current
condition clears.
0= off
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
143
1 = on
•
Digital input channel 13 returns the digital output mismatch status.
0= No mismatch
1 = One or more digital outputs mismatch
•
Digital input channel 14 returns the SCADAPack Vision power.
0 = No power to SCADAPack Vision
1 = Power to SCADAPack Vision
The digital output assignment provides twelve I/O channels for the digital outputs of the
SCADAPack LP.
The SCADAPack LP provides eight universal digital inputs or outputs. Outputs are opencollector/open drain type.
•
These are defined as digital output channels 0 to 7.
0 = output transistor off
1 = output transistor on
The SCADAPack LP also provides four internal digital outputs.
•
Digital output channel 8 is not used. This is for internal use only.
•
Digital output channel 9 is used to control com3 (HMI) power.
0= off
1 = on
•
Digital output channel 10 is used to control the VLoop power supply.
0= VLoop output off
1= VLoop output on
•
Digital output channel 11 is used to control the DC/DC converter.
0= off
1 = on
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
SCADAPack LP I/O Module
fixed
Coil Register
First register of any unused block of 12
consecutive coil registers.
Last register of block
12 coil registers
digital outputs
Status Register
First register of any unused block of 16
consecutive status registers.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
0xxxx
0xxxx + 11
1xxxx
144
Module
Address
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
SCADAPack LP I/O Module
fixed
Last register of block
16 status registers
digital inputs
Input Register
First register of any unused block of 8
consecutive input registers.
Last register of block
8 input registers
analog inputs
Holding Register
First register of any unused block of 2
consecutive holding registers.
Last register of block
2 output registers
analog outputs
None
1xxxx + 15
3xxxx
3xxxx +7
4xxxx
4xxxx +1
Coil Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Digital output 8
Digital output 9
Digital output 10
Digital output 11
Status Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
145
Registers
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Start Register + 13
Start Register + 14
Start Register + 15
Assignment to Module Hardware
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Digital input 13
Digital input 14
Digital input 15
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Analog Output Register Data
Registers
Start Register
Start Register + 1
Assignment to Module Hardware
Analog output 0
Analog output 1
Notes
Only one SCADAPack LP I/O may be assigned to the same controller.
Refer to the SCADAPack LP Hardware Manual for information on analog and digital I/O usage.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
146
1.10.10
SCADAPack 100 I/O
Description
Digital output data is assigned from six consecutive coil registers. The digital outputs are updated
continuously with data read from the coil registers.
Digital input data is assigned to six consecutive status registers. The status registers are updated
continuously with data read from the digital inputs.
Analog and counter input data is assigned to eight consecutive input registers. There are six analog
input registers, and a counter input double register (32 bit). These input registers are updated
continuously with data read from the analog inputs and counter input.
Register Assignment
Module
Address
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Extended Parameters
SCADAPack 100 I/O Module
Fixed
Coil Register
First register of any unused block of 6
consecutive coil registers.
Last register of block
6 coil registers
digital outputs
Status Register
First register of any unused block of 6
consecutive status registers.
Last register of block
8 status registers
digital inputs
Input Register
First register of any unused block of 4
consecutive input registers.
Last register of block
8 input registers
analog inputs
None
0xxxx
0xxxx + 5
1xxxx
1xxxx + 5
3xxxx
3xxxx +8
Coil Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
147
Status Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Analog and Counter Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6 and + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4 Board Temperature (°C)
Analog input 5 Ram Battery Voltage (mV)
Counter input, 32 bit register
Notes
Only one SCADAPack 100 I/O may be assigned to the same controller.
Refer to the SCADAPack 100 Hardware Manual for information on analog and digital I/O usage.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
148
1.10.11
SCADAPack 350 I/O
Description
The SCADAPack 350 I/O is comprised of four different types of I/O channels: eight analog inputs,
two analog outputs, thirteen digital inputs and eleven digital outputs.
The analog input assignment provides eight I/O channels for the analog input data.
•
Analog input channels 0 to 4 provide five external analog inputs (0-10V or 0-40mA)
•
Analog input channel 5 provides an external analog input for battery monitoring (0 to 32.768V)
•
Analog input channel 6 provides an internal analog input for DC/DC converter monitoring.
•
Analog input channel 7 is used internally by the SCADAPack 350.
The analog output assignment provides two I/O channels for the analog output data.
The digital input assignment provides thirteen I/O channels for the digital input data.
The SCADAPack 350 provides eight universal digital inputs or outputs. The inputs are for use with
dry contacts such as switches and relay contacts.
•
These are defined as digital input channels 0 to 7.
0 = contact open (LED off)
1 = contact closed (LED on)
The SCADAPack 350 I/O hardware also provides five internal digital inputs.
•
Digital input channel 8 returns the VLOOP output status.
0 = off
1 = on
•
Digital input channel 9 returns the DC/DC converter status. This bit reports the true status of the
DC/DC converter. If over-current causes the converter to be turned off, this bit will clear.
0 = off
1 = on
•
Digital input channel 10 returns the VLOOP over-current status. This indicates VLOOP overcurrent has been detected. This input clears when VLOOP output is off, or the over-current
condition clears.
0 = off
1 = on
•
Digital input channel 11 returns the digital output mismatch status.
0 = No mismatch
1 = One or more digital outputs mismatch
•
Digital input channel 12 returns the Com3 (HMI) power control status.
0 = off
1 = on
The digital output assignment provides eleven I/O channels for the digital outputs of the
SCADAPack 350.
The SCADAPack 350 provides eight universal digital inputs or outputs. Outputs are opencollector/open drain type.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
149
•
These are defined as digital output channels 0 to 7.
0 = output transistor off
1 = output transistor on
The SCADAPack 350 I/O hardware also provides three internal digital outputs.
•
Digital output channel 8 is used to control the VLoop power supply.
0 = VLoop output off
1 = VLoop output on
•
Digital output channel 9 is used to control the DC/DC converter.
0 = off
1 = on
•
Digital output channel 10 is used to control the Com3 (HMI) power.
0 = off
1 = on
Register Assignment
Module
Address
SCADAPack 350 I/O
fixed
Type
Start
Coil Register
First register of any unused block of 11
consecutive coil registers.
Last register of block
10 coil registers
digital outputs
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Type
Start
End
Registers
Description
Status Register
First register of any unused block of 13
consecutive status registers.
Last register of block
12 status registers
digital inputs
Input Register
First register of any unused block of 8
consecutive input registers.
Last register of block
8 input registers
analog inputs
Holding Register
First register of any unused block of 2
consecutive holding registers.
Last register of block
2 output registers
analog outputs
0xxxx
0xxxx + 9
1xxxx
1xxxx + 11
3xxxx
3xxxx +7
4xxxx
4xxxx +1
Coil Register Data
Registers
Assignment to Module Hardware
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
150
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Assignment to Module Hardware
Digital output 0
Digital output 1
Digital output 2
Digital output 3
Digital output 4
Digital output 5
Digital output 6
Digital output 7
Digital output 8
Digital output 9
Digital output 10
Status Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Start Register + 8
Start Register + 9
Start Register + 10
Start Register + 11
Start Register + 12
Assignment to Module Hardware
Digital input 0
Digital input 1
Digital input 2
Digital input 3
Digital input 4
Digital input 5
Digital input 6
Digital input 7
Digital input 8
Digital input 9
Digital input 10
Digital input 11
Digital input 12
Input Register Data
Registers
Start Register
Start Register + 1
Start Register + 2
Start Register + 3
Start Register + 4
Start Register + 5
Start Register + 6
Start Register + 7
Assignment to Module Hardware
Analog input 0
Analog input 1
Analog input 2
Analog input 3
Analog input 4
Analog input 5
Analog input 6
Analog input 7
Analog Output Register Data
Registers
Start Register
Assignment to Module Hardware
Analog output 0
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
151
Start Register + 1
Analog output 1
Notes
Only one SCADAPack 350 I/O may be assigned to the same controller.
Refer to the SCADAPack 350 Hardware Manual for information on analog and digital I/O usage.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
152
1.11
Controller Default Register Assignments
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
153
1.11.1
4202 DR Extended/4203 DR I/O Register Assignment
A default Register Assignment is provided for the SCADASense series of controllers. The table
below provides the default register assignment for these controllers.
To enable the default register assignment for a SCADASense controller:
•
Select Type from the Controller menu.
•
Select the appropriate SCADASense controller.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
If the controller type selected is a SCADASense 4202 DR, the user is presented with the default
register assignment for a 4202 DR and 4202 DR Extended/4203 DR. Select the appropriate
module depending on your controller type.
Module
Address
SCADASense 4202 DR I/O
Fixed
digital inputs
analog inputs
analog outputs
SCADASense 4202 DR Extended/4203 DR
I/O
Digital output
digital inputs
analog inputs
analog outputs
Note:
Default Register
Assignment
10001 to 10001
30001 to 30005
40500 to 40500
Fixed
00001 to 00001
10001 to 10001
30001 to 30005
40500 to 40500
Note that the SCADASense 4202 DR Extended/4203 DR I/O module, while the default for
the SCADASense 4203 DR, applies to the SCADASense 4202 DR series controllers
manufactured after July 13, 2004.
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
154
1.11.2
SCADASense 4202/4203 DS I/O Default Register Assignment
A default Register Assignment is provided for the SCADASense DS series of controllers (4202 or
4203 DR). The table below contains a convenient assignment for the 4202 DR and 4203 DR
controllers.
To enable the default register assignment:
•
Select Type from the Controller menu.
•
Select the appropriate SCADASense DS series controller.
•
Select Register Assignment from the Controller menu.
Select the Default button in the Register Assignment dialog.
The following table summarizes the Default Register Assignment for the SCADAPack.
Module
Address
SCADASense 4202/4203 DS I/O
Digital output
digital inputs
analog inputs
Fixed
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Default
Register
Assignment
00001 to 00002
10001 to 10001
30001 to 30007
155
1.11.3
Micro16 Default Register Assignment (Backwards Compatible
Modules)
The purpose of the Default Register Assignment is to provide backward compatibility to programs
written for older TeleSAFE Micro16 controller firmware (versions 1.22 or earlier).
Instead of configurable Register Assignment older versions of the firmware use fixed mapping of the
I/O hardware to the I/O database. The Default Register Assignment assigns all possible I/O modules
according the previously fixed mapping used by the older firmware.
Note 1: It is recommended that all unused modules in the default table be deleted in order to
optimize performance of the I/O scan.
Note 2: Only those I/O modules that were available to the older firmware are assigned in the
default table.
To enable the default register assignment:
•
Select Type from the Controller menu.
•
Select Micro16.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select Backwards Compatible Modules in the Select Register Assignment Option dialog.
•
Use the Delete button to delete from the default table all modules that are not needed in your
program.
The Default Register Assignment results in the following unassigned I/O database registers:
Coil Registers
Status Registers
Input Registers
Holding Register
01025 to 04096
11025 to 14096
30513 to 31024
41712 to 49999
These registers may be used as general purpose registers in ladder logic programs.
1.11.3.1
Default Analog Input Module Assignment
Module Type
AIN Generic 8 point
AIN Generic 8 point
AIN Generic 8 point
AIN Generic 8 point
AIN Generic 8 point
AIN Generic 8 point
AIN Generic 8 point
AIN Generic 8 point
AIN 5203/4 temperature
AIN 5203/4 RAM battery voltage
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Module Address
0
1
2
3
4
5
6
7
N/A
N/A
Default Register Assignment
30001 to 30008
30009 to 30016
30017 to 30024
30025 to 30032
30033 to 30040
30041 to 30048
30049 to 30056
30057 to 30064
30193 to 30194
30195
156
1.11.3.2
Default Analog Output Module Assignment
Module Type
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
AOUT Generic 2 point
1.11.3.3
Module Address
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Default Register Assignment
40001 to 40002
40003 to 40004
40005 to 40006
40007 to 40008
40009 to 40010
40011 to 40012
40013 to 40014
40015 to 40016
40017 to 40018
40019 to 40020
40021 to 40022
40023 to 40024
40025 to 40026
40027 to 40028
40029 to 40030
40031 to 40032
Default Configuration Module Assignment
Module Type
CNFG Clear serial port counters
CNFG Clear serial port counters
CNFG Clear protocol counters
CNFG Clear protocol counters
CNFG Save settings to EEPROM
CNFG LED power settings
• default state
• time to return to default state
CNFG Serial port settings
CNFG Protocol settings
CNFG Serial port settings
CNFG Protocol settings
CNFG Real time clock and alarm
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Module Address
0
1
0
1
N/A
N/A
Default Register Assignment
00209
00210
00217
00218
00225
00242
40211
0
0
1
1
N/A
0
1
2
3
4
5
6
7
8
9
10
40131 to 40139
40140 to 40142
40146 to 40154
40155 to 40157
40191 to 40201
40220 to 40244
40250 to 40274
40280 to 40304
40310 to 40334
40340 to 40364
40370 to 40394
40400 to 40424
40430 to 40454
40460 to 40484
40490 to 40514
40520 to 40544
157
Module Type
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG PID control block
CNFG Store and forward
Translation table
Clear store and forward table
1.11.3.4
Module Address
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
N/A
Default Register Assignment
40550 to 40574
40580 to 40604
40610 to 40634
40640 to 40664
40670 to 40694
40700 to 40724
40730 to 40754
40760 to 40784
40790 to 40814
40820 to 40844
40850 to 40874
40880 to 40904
40910 to 40934
40940 to 40964
40970 to 40994
41000 to 41024
41030 to 41054
41060 to 41084
41090 to 41114
41120 to 41144
41150 to 41174
41200 to 41711
00226
Default Counter Input Module Assignment
Module Type
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5410 input
CNTR 5203/4 counter inputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Module Address
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
N/A
Default Register Assignment
30201 to 30208
30209 to 30216
30217 to 30224
30225 to 30232
30233 to 30240
30241 to 30248
30249 to 30256
30257 to 30264
30265 to 30272
30273 to 30280
30281 to 30288
30289 to 30296
30297 to 30304
30305 to 30312
30313 to 30320
30321 to 30328
30329 to 30334
158
1.11.3.5
Default Diagnostic Module Assignment
Module Type
DIAG Controller status code
DIAG Serial port comm. Status
DIAG Serial port protocol status
DIAG Serial port comm. Status
DIAG Serial port protocol status
1.11.3.6
Default Register Assignment
30196
30401 to 30405
30406 to 30415
30421 to 30425
30426 to 30435
Default Digital Input Module Assignment
Module Type
DIN Generic 8 point
DIN Generic 8 point
DIN Generic 8 point
DIN Generic 8 point
DIN Generic 8 point
DIN Generic 8 point
DIN Generic 8 point
DIN Generic 8 point
DIN Generic 16 point
DIN Generic 16 point
DIN Generic 16 point
DIN Generic 16 point
DIN Generic 16 point
DIN Generic 16 point
DIN Generic 16 point
DIN Generic 16 point
DIN 5203/4 digital inputs
DIN 5203/4 option switches
DIN 5203/4 interrupt input
1.11.3.7
Module Address
N/A
0
0
1
1
Module Address
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
N/A
N/A
N/A
Default Register Assignment
10001 to 10008
10009 to 10016
10017 to 10024
10025 to 10032
10033 to 10040
10041 to 10048
10049 to 10056
10057 to 10064
10065 to 10080
10081 to 10096
10097 to 10112
10113 to 10128
10129 to 10144
10145 to 10160
10161 to 10176
10177 to 10192
10193 to 10195
10196 to 10198
10199
Default Digital Output Module Assignment
Module Type
DOUT Generic 8 point
DOUT Generic 8 point
DOUT Generic 8 point
DOUT Generic 8 point
DOUT Generic 8 point
DOUT Generic 8 point
DOUT Generic 8 point
DOUT Generic 8 point
DOUT Generic 16 point
DOUT Generic 16 point
DOUT Generic 16 point
DOUT Generic 16 point
DOUT Generic 16 point
Module Address
0
1
2
3
4
5
6
7
8
9
10
11
12
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Default Register Assignment
00001 to 00008
00009 to 00016
00017 to 00024
00025 to 00032
00033 to 00040
00041 to 00048
00049 to 00056
00057 to 00064
00065 to 00080
00081 to 00096
00097 to 00112
00113 to 00128
00129 to 00144
159
Module Type
DOUT Generic 16 point
DOUT Generic 16 point
DOUT Generic 16 point
Module Address
13
14
15
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Default Register Assignment
00145 to 00160
00161 to 00176
00177 to 00192
160
1.11.4
Micro16 Default Register Assignment (Controller I/O Only)
A default Register Assignment is provided for the Micro16 controller. The table contains a
convenient assignment for the Micro16 controller board only.
To enable the SCADAPack LIGHT default register assignment:
•
Select Type from the Controller menu.
•
Select Micro16.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select Controller I/O Only in the Select Register Assignment Option dialog.
The following table summarizes the Default Register Assignment for the Micro16.
Module
DIN Controller digital inputs
DIN Controller interrupt input
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10001 to 10003
10004 to 10004
161
1.11.5
SCADAPack (5601 I/O Module) Default Register Assignment
A default Register Assignment is provided for the SCADAPack controller. The table contains a
convenient assignment for the SCADAPack controller and 5601 I/O module.
To enable the SCADAPack default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select 5601 I/O Module in the Select Register Assignment Option dialog.
The following table summarizes the Default Register Assignment for the SCADAPack.
See the SCADAPack 5601 I/O Module section for information on the registers used.
Module
DIN Controller digital inputs
DIN Controller interrupt input
SCADAPack 5601 I/O module
digital outputs
digital inputs
analog inputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10017 to 10019
10020 to 10020
Fixed
00001 to 00012
10001 to 10016
30001 to 30008
162
1.11.6
SCADAPack (5604 I/O Module) Default Register Assignment
A default Register Assignment is provided for the SCADAPack controller. The table contains a
convenient assignment for the SCADAPack controller and 5604 I/O module.
To enable the SCADAPack default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select 5604 I/O Module in the Select Register Assignment Option dialog.
The following table summarizes the Default Register Assignment for the SCADAPack.
See the SCADAPack 5604 I/O Module section for information on the registers used.
Module
DIN Controller digital inputs
DIN Controller interrupt input
SCADAPack 5604 I/O module
digital outputs
digital inputs
analog inputs
analog outputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10017 to 10019
10020 to 10020
Fixed
00001 to 00036
10001 to 10035
30001 to 30010
40001 to 40002
163
1.11.7
SCADAPack LIGHT Default Register Assignment
A default Register Assignment is provided for the SCADAPack LIGHT controller. The table
contains a convenient assignment for the SCADAPack controller and 5602 I/O module.
To enable the SCADAPack LIGHT default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack LIGHT.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
The following table summarizes the Default Register Assignment for the SCADAPack LIGHT.
See the SCADAPack 5602 I/O Module section for information on the registers used.
Module
DIN Controller digital inputs
DIN Controller interrupt input
SCADAPack 5602 I/O module
digital outputs
digital inputs
analog inputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10006 to 10008
10009 to 10009
Fixed
00001 to 00002
10001 to 10005
30001 to 30005
164
1.11.8
SCADAPack PLUS (5601 I/O Module) Default Register
Assignment
A default Register Assignment is provided for the SCADAPack PLUS controller. The table contains
a convenient assignment for the SCADAPack controller the 5601I/O module and 5602 I/O module.
To enable the SCADAPack PLUS default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack PLUS.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select 5601 I/O Module in the Select Register Assignment Option dialog.
The following table summarizes the Default Register Assignment for the SCADAPack PLUS.
See the SCADAPack 5601 I/O Module and SCADAPack 5602 I/O Module sections for information
on the registers used.
Module
DIN Controller digital inputs
DIN Controller interrupt input
SCADAPack 5601 I/O module
digital outputs
digital inputs
analog inputs
SCADAPack 5602 I/O module
digital outputs
digital inputs
analog inputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10022 to 10024
10025 to 10025
fixed
00001 to 00012
10001 to 10016
30001 to 30008
Fixed
00013 to 00014
10017 to 10021
30009 to 30013
165
1.11.9
SCADAPack Plus (5604 I/O Module) Default Register Assignment
A default Register Assignment is provided for the SCADAPack controller. The table contains a
convenient assignment for the SCADAPack controller and 5604 I/O module.
To enable the SCADAPack default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack Plus.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select 5604 I/O Module in the Select Register Assignment Option dialog.
The following table summarizes the Default Register Assignment for the SCADAPack. See the
SCADAPack 5604 I/O Module section for information on the registers used.
Module
DIN Controller digital inputs
DIN Controller interrupt input
SCADAPack 5604 I/O module
digital outputs
digital inputs
analog inputs
analog outputs
SCADAPack 5602 I/O module
digital outputs
digital inputs
analog inputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10041 to 10043
10044 to 10044
Fixed
00001 to 00036
10001 to 10035
30001 to 30010
40001 to 40002
Fixed
00037 to 00038
10036 to 10040
30011 to 30015
166
1.11.10
SCADAPack LP Default Register Assignment
A default Register Assignment is provided for the SCADAPack LP controller. The table contains a
convenient assignment for the SCADAPack LP controller.
To enable the SCADAPack LP default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack LP.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
The following table summarizes the Default Register Assignment for the SCADAPack LP.
See the SCADAPack LP I/O section for information on the registers used.
Module
CNTR Controller counter inputs
SCADAPack LP I/O
digital outputs
digital inputs
analog inputs
analog outputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
30009 to 30014
fixed
00001 to 00012
10001 to 10016
30001 to 30008
40001 to 40002
167
1.11.11
SCADAPack 350 Default Register Assignment
A default Register Assignment is provided for the SCADAPack 350 controller. The table contains a
convenient assignment for the SCADAPack 350 controller.
To enable the SCADAPack 350 default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack 350.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
The following table summarizes the Default Register Assignment for the SCADAPack 350.
See the SCADAPack 5606 I/O Module section for information on the registers used.
Module
CNTR Controller counter
inputs
SCADAPack 350 I/O
• digital outputs
• digital inputs
• analog inputs
• analog outputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default
Register
Assignment
30009 to
30014
fixed
00001 to
00011
10001 to
10013
30001 to
30008
40001 to
40002
168
1.11.12
SCADAPack 32 (5601 I/O Module) Default Register Assignment
A default Register Assignment is provided for the SCADAPack 32 controller. The table contains a
convenient assignment for the SCADAPack 32 controller.
To enable the SCADAPack 32 default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack 32.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select 5601 I/O Module in the Select Register Assignment Option dialog.
The following table summarizes the Default Register Assignment for the SCADAPack 32.
See the SCADAPack 5601 I/O Module section for information on the registers used.
Module
DIN Controller digital inputs
DIN Controller interrupt input
SCADAPack 5601 I/O module
digital outputs
digital inputs
analog inputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10017 to 10019
10020 to 10020
Fixed
00001 to 00012
10001 to 10016
30001 to 30008
169
1.11.13
SCADAPack 32 (5604 I/O Module) Default Register Assignment
A default Register Assignment is provided for the SCADAPack 32 controller. The table contains a
convenient assignment for the SCADAPack 32 controller.
To enable the SCADAPack 32 default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack 32.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
•
Select 5601 I/O Module in the Select Register Assignment Option dialog.
The following table summarizes the Default Register Assignment for the SCADAPack 32.
See the SCADAPack 5604 I/O Module section for information on the registers used.
Module
DIN Controller digital inputs
DIN Controller interrupt input
SCADAPack LP I/O
digital outputs
digital inputs
analog inputs
analog outputs
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10017 to 10019
10020 to 10020
fixed
00001 to 00012
10001 to 10016
30001 to 30008
40001 to 40002
170
1.11.14
SCADAPack 32P Default Register Assignment
A default Register Assignment is provided for the SCADAPack 32P controller. The table contains a
convenient assignment for the SCADAPack 32P controller.
To enable the SCADAPack 32P default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack 32P.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
The following table summarizes the Default Register Assignment for the SCADAPack 32P.
Module
DIN Controller digital inputs
DIN Controller interrupt input
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Address
Default Register Assignment
10001 to 10003
10004 to 10004
171
1.11.15
SCADAPack 100 Default Register Assignment
A default Register Assignment is provided for the SCADAPack 100 controller. The table contains a
convenient assignment for the SCADAPack 100 controller.
To enable the SCADAPack 100 default register assignment:
•
Select Type from the Controller menu.
•
Select SCADAPack 100.
•
Select Register Assignment from the Controller menu.
•
Select the Default button in the Register Assignment dialog.
The following table summarizes the Default Register Assignment for the SCADAPack 100.
See the SCADAPack 100 I/O section for information on the registers used.
Module
SCADAPack 100 I/O
digital outputs
digital inputs
analog inputs and counters
Address
fixed
TelePACE Ladder Logic Register Assignment Reference
May 8, 2007
Default Register Assignment
00001 to 00006
10001 to 10006
30001 to 30008
172
TeleBUS Protocols
User and Reference Manual
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
TeleBUS Protocols User and Reference Manual
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE,
TeleSAFE Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus,
SCADAPack 32, SCADAPack 32P, SCADAPack 350, SCADAPack LP,
SCADAPack 100, SCADASense 4202 DS, SCADASense 4202 DR,
SCADASense 4203 DS, SCADASense 4203 DR, SCADASense 4102,
SCADASense 4012, SCADASense 4032 and TeleBUS are registered
trademarks of Control Microsystems.
All other product names are copyright and registered trademarks or trade names
of their respective owners.
Material used in the User and Reference manual section titled SCADAServer
OLE Automation Reference is distributed under license from the OPC
Foundation.
TeleBUS Protocols User and Reference Manual
May 8, 2007
1
Table of Contents
TABLE OF CONTENTS .......................................................................................................... 2
TELEBUS PROTOCOLS OVERVIEW .................................................................................... 4
Compatibility........................................................................................................................ 4
SERIAL PORT CONFIGURATION ......................................................................................... 5
Communication Parameters ............................................................................................... 5
RTU Protocol Parameters.............................................................................................. 5
ASCII Protocol Parameters............................................................................................ 5
Baud Rate ...................................................................................................................... 6
Duplex............................................................................................................................ 6
Protocol Parameters ........................................................................................................... 7
Protocol Type................................................................................................................. 7
Station Number .............................................................................................................. 7
Task Priority ................................................................................................................... 7
Store and Forward Messaging ...................................................................................... 7
I/O DATABASE........................................................................................................................ 9
Accessing the I/O Database ............................................................................................... 9
Coil and Status Registers .............................................................................................. 9
Input and Holding Registers ........................................................................................ 10
Exception Status .......................................................................................................... 10
Slave ID ....................................................................................................................... 10
EXTENDED STATION ADDRESSING.................................................................................. 11
Theory of Operation .......................................................................................................... 11
SLAVE MODE........................................................................................................................ 12
Broadcast Messages ........................................................................................................ 12
Function Codes ................................................................................................................. 12
Read Coil Status .......................................................................................................... 12
Read Input Status ........................................................................................................ 13
Read Holding Register................................................................................................. 13
Read Input Register..................................................................................................... 13
Force Single Coil ......................................................................................................... 13
Preset Single Register ................................................................................................. 13
Read Exception Status ................................................................................................ 13
Force Multiple Coils ..................................................................................................... 13
Preset Multiple Registers............................................................................................. 13
Report Slave ID............................................................................................................ 13
MODBUS MASTER MODE ................................................................................................... 15
Modbus Function Codes ................................................................................................... 15
TeleBUS Protocols User and Reference Manual
May 8, 2007
2
Read Coil Status .......................................................................................................... 15
Read Input Status ........................................................................................................ 15
Read Holding Register................................................................................................. 15
Read Input Register..................................................................................................... 16
Force Single Coil ......................................................................................................... 16
Preset Single Register ................................................................................................. 16
Force Multiple Coils ..................................................................................................... 16
Preset Multiple Registers............................................................................................. 16
Enron Modbus Master Mode............................................................................................. 17
Variable Types ............................................................................................................. 17
Enron Modbus Function Codes ................................................................................... 18
Sending Messages ........................................................................................................... 19
STORE AND FORWARD MESSAGING ............................................................................... 20
Translation Table .............................................................................................................. 20
Table Size .................................................................................................................... 21
Invalid Translations ........................................................................................................... 21
Store and Forward Configuration...................................................................................... 21
SCADAPack Controller................................................................................................ 21
SCADAPack Light Controller ....................................................................................... 23
SCADAPack Plus Controller........................................................................................ 24
SCADAPack LP Controller .......................................................................................... 26
SCADAPack 100 Controller......................................................................................... 27
SCADAPack 350, SCADAPack 32 and 32P Controller............................................... 28
Diagnostics Counters........................................................................................................ 30
POINT–TO–POINT PROTOCOL (PPP) ................................................................................ 31
PPP Client Setup in Windows 2000.................................................................................. 31
Direct Serial PPP Connection using Windows 2000 ................................................... 31
Dial-up PPP Connection using Windows 2000 ........................................................... 42
TeleBUS Protocols User and Reference Manual
May 8, 2007
3
TeleBUS Protocols Overview
The TeleBUS communication protocols provide a standard communication interface to
SCADAPack and TeleSAFE controllers. The TeleBUS protocols are compatible with the
widely used Modbus RTU and ASCII protocols. Additional TeleBUS commands provide
remote programming and diagnostics capability.
The TeleBUS protocols operate on a wide variety of serial data links. These include RS-232
serial ports, RS-485 serial ports, radios, leased line modems, and dial up modems. The
protocols are generally independent of the communication parameters of the link, with a few
exceptions.
TeleBUS protocol commands may be directed to a specific device, identified by its station
number, or broadcast to all devices. Using extended addressing up to 65534 devices may
connect to one communication network.
The TeleBUS protocols provide full access to the I/O database in the controller. The I/O
database contains user-assigned registers and general purpose registers. Assigned
registers map directly to the I/O hardware or system parameter in the controller. General
purpose registers can be used by ladder logic and C application programs to store
processed information, and to receive information from a remote device.
Application programs can initiate communication with remote devices. A multiple port
controller can be a data concentrator for remote devices, by polling remote devices on one
port and responding as a slave on another port.
The protocol type, communication parameters and station address are configured separately
for each serial port on a controller. One controller can appear as different stations on
different communication networks. The port configuration can be set from an application
program, from the TelePACE programming software, or from another Modbus compatible
device.
Compatibility
There are two TeleBUS protocols. The TeleBUS RTU protocol is compatible with the
Modbus RTU protocol. The TeleBUS ASCII protocol is compatible with the Modbus ASCII
protocol.
Compatibility refers to communication only. The protocol defines communication aspects
such as commands, syntax, message framing, error handling and addressing. The
controllers do not mimic the internal functioning of any programmable controller. Device
specific functions – those that relate to the hardware or programming of a specific
programmable controller – are not implemented.
TeleBUS Protocols User and Reference Manual
May 8, 2007
4
Serial Port Configuration
Communication Parameters
The TeleBUS protocols are, in general, independent of the serial communication
parameters. The baud rate, word length and parity may be chosen to suit the host computer
and the characteristics of the data link.
The port configuration can be set in four ways:
• using the TelePACE program;
• using the set_port function from a C application program;
• writing to the I/O database from a C or ladder logic application program; or
• writing to the I/O database remotely from a Modbus compatible device.
To configure a serial port through the I/O database, add the module, CNFG Serial port
settings, to the Register Assignment Table.
RTU Protocol Parameters
The TeleBUS RTU protocol is an eight bit binary protocol. The table below shows possible
and recommended communication parameters.
Parameter
Baud Rate
Data Bits
Parity
Possible Settings
see Baud Rate section below
8 data bits
None
Even
Odd
Stop bits
1 stop bit
2 stop bits1
Flow control
Disabled
Duplex
see Duplex section below
1
Not applicable to SCADAPack 350
Recommended Setting
see Baud Rate section below
8 data bits
none
1 stop bit
disabled
see Duplex section below
ASCII Protocol Parameters
The TeleBUS ASCII protocol is an seven bit character based protocol. The table below
shows possible and recommended communication parameters.
Parameter
Baud Rate
Data Bits
Parity
Stop Bits
Possible Settings
see Baud Rate section below
7 data bits
8 data bits
None
Even
Odd
1 stop bit
2 stop bits1
TeleBUS Protocols User and Reference Manual
May 8, 2007
Recommended Setting
see Baud Rate section below
7 data bits
none
1 stop bit
5
Parameter
Flow Control
Possible Settings
Enabled
Disabled
see Duplex section below
Duplex
1
Recommended Setting
disabled
see Duplex section below
Not applicable to SCADAPack 350
NOTE: Flow control should never be enabled with modems or in noisy environments. Noise
can result in the accidental detection of an XOFF character, which shuts down
communication. Flow control is not recommended for any environment, but can be
used on high quality, full duplex, direct wiring where speeds greater than 4800 baud
are required.
Baud Rate
The baud rate sets the communication speed. The type of serial data link used determines
the possible settings. The table below shows the possible settings for SCADAPack and
TeleSAFE controllers. Note that not all port types and baud rates are available on all
controller ports.
Port Type
RS-232 or
RS-232
Dial-up
modem
RS-485
Possible Settings
75 baud
110 baud
150 baud
300 baud
600 baud
1200 baud
2400 baud
4800 baud
9600 baud
19200 baud
38400 baud
57600 baud
115200 baud
75 baud
110 baud
150 baud
300 baud
600 baud
1200 baud
2400 baud
4800 baud
9600 baud
19200 baud
38400 baud
57600 baud
115200 baud
Recommended Setting
Use the highest rate supported
by all devices on the network.
Use the highest rate supported
by all devices on the network.
Duplex
The TeleBUS protocols communicate in one direction at a time. However the type of serial
data link used determines the duplex setting. The table below shows the possible settings
for SCADAPack and TeleSAFE controllers. Note that not all port types are available on all
controllers.
TeleBUS Protocols User and Reference Manual
May 8, 2007
6
Port Type
RS-232 or
RS-232
Dial-up
modem
RS-485
Possible Settings
half duplex
full duplex
half duplex
full duplex
Recommended Setting
Use full duplex wherever
possible.
Use half duplex for most
external modems.
Slave stations always use half
duplex.
Master stations can use full
duplex only on 4 wire systems.
Protocol Parameters
The TeleBUS protocols operate independently on each serial port. Each port may set the
protocol type, station number, protocol task priority and store-and-forward messaging
options.
The port configuration can be set in four ways:
• using the TelePACE or ISaGRAF programs;
• using the set_protocol function from a C or C++ application program;
• writing to the I/O database from a C, C++, ISaGRAF or ladder logic application program;
• writing to the I/O database remotely from a Modbus compatible device.
To configure protocol settings through the I/O database, add the module, CNFG Protocol
settings, to the Register Assignment for TelePACE applications or use the setprot function in
ISaGRAF applications.
Protocol Type
The protocol type may be set to emulate the Modbus ASCII and Modbus RTU protocols, or it
may be disabled. When the protocol is disabled, the port functions as a normal serial port.
Station Number
The TeleBUS protocol allows up to 254 devices on a network using standard addressing
and up to 65534 devices using extended addressing. Station numbers identify each device.
A device responds to commands addressed to it, or to commands broadcast to all stations.
The station number is in the range 1 to 254 for standard addressing and 1 to 65534 for
extended addressing. Address 0 indicates a command broadcast to all stations, and cannot
be used as a station number. Each serial port may have a unique station number.
Task Priority
A task is responsible for monitoring each serial port for messages. The real time operating
system (RTOS) schedules the tasks with the application program tasks according to the task
priority. The priority can be changed only with the set_protocol function from an application
program.
The default task priority is 3. Changing the priority is not recommended.
Store and Forward Messaging
Store and forward messaging re-transmits messages received by a controller. Messages
may be re-transmitted on any serial port, with or without station address translation. A user-
TeleBUS Protocols User and Reference Manual
May 8, 2007
7
defined translation table determines actions performed for each message. The Store and
Forward Messaging section below describes this feature in detail.
Store and forward messaging may be enabled or disabled on each port. It is disabled by
default.
TeleBUS Protocols User and Reference Manual
May 8, 2007
8
I/O Database
The TeleBUS protocols read and write information from the I/O database. The I/O database
contains user-assigned registers and general purpose registers.
User-assigned registers map directly to the I/O hardware or system parameter in the
controller. Assigned registers are initialized to the default hardware state or system
parameter when the controller is reset. Assigned output registers do not maintain their
values during power failures. However, output registers do retain their values during
application program loading.
General purpose registers are used by ladder logic and C application programs to store
processed information, and to receive information from remote devices. General purpose
registers retain their values during power failures and application program loading. The
values change only when written by an application program or a communication protocol.
The I/O database is divided into four sections.
• Coil registers are single bits which the protocols can read and write. Coil registers are
located in the digital output section of the I/O database. The number of registers depends
on the controller. Coil registers are numbered from 1 to the maximum for the controller.
• Status registers are single bits which the protocol can read. Status registers are located
in the digital input section of the I/O database. The number of registers depends on the
controller. Status registers are numbered from 10001 to the maximum for the controller.
• Input registers are 16 bit registers which the protocol can read. Input registers are located
in the analog input section of the I/O database. The number of registers depends on the
controller. Input registers are numbered from 30001 to the maximum for the controller.
• Holding registers are 16 bit registers that the protocol can read and write. Holding
registers are located in the analog output section of the I/O database. The number of
registers depends on the controller. Holding registers are numbered from 40001 to the
maximum for the controller.
Accessing the I/O Database
TelePACE ladder logic programs access the I/O database through function blocks. All
function blocks can access the I/O database. Refer to the TelePACE Ladder Logic
Reference and User Manual for details.
ISaGRAF applications access the I/O database through dictionary variables with assigned
network addresses or using Permanent Non-Volatile Modbus registers. See the ISaGRAF
User and Reference Manual for details.
C language programs access the I/O database with two functions. The dbase function reads
a value from the I/O database. The setdbase function writes a value to the I/O database.
Refer to the TelePACE C Tools Reference and User Manual for full details on these
functions.
Coil and Status Registers
Coil and status registers contain one bit of information, that is, whether a signal is off or on.
TeleBUS Protocols User and Reference Manual
May 8, 2007
9
Writing any non-zero value to the register turns the bit on. Writing zero to the register turns
the bit off. If the register is assigned to an I/O module, the bit status is written to the module
output hardware or parameter.
Reading a coil or status register returns –1 if the bit is on, or 0 if the bit is off. The stored
value is returned from general purpose registers. The I/O module point status is returned
from assigned registers.
Input and Holding Registers
Input and holding registers contain 16 bit values.
Writing any value to a general purpose register stores the value in the register. Writing a
value to an assigned register, writes the value to the assigned I/O module.
Reading a general purpose register returns the value stored in the register. Reading an
assigned register returns the value read from the I/O module.
Exception Status
The exception status is a single byte containing controller specific status information. It is
returned in response to the Read Exception Status function (see the Slave Mode section).
A C language application program can define the status information. The
modbusExceptionStatus function sets the status information. Ladder logic programs
cannot set this information.
Slave ID
The slave ID is a variable length message containing controller specific information. It is
returned in response to the Report Slave ID function (see the Slave Mode section).
A C language application program can define the information and the length of the message.
The modbusSlaveID function sets the information. Ladder logic programs cannot set this
information.
TeleBUS Protocols User and Reference Manual
May 8, 2007
10
Extended Station Addressing
The TeleBUS RTU and ASCII protocols support two type of Modbus station addressing.
Standard Modbus addressing allows a maximum of 255 stations and is compatible with
standard Modbus devices.
Extended Modbus addressing allows a maximum of 65534 stations. Extended Modbus
addressing is fully compatible with standard Modbus addressing for addresses between 0
and 254.
Theory of Operation
The address field of a Modbus message is a single byte. Address 0 is a broadcast address;
messages sent to this address are sent to all stations. Addresses 1 to 255 are station
addresses. Figure 1 shows the format of a standard Modbus message.
Field
Size
Address
1
Function
1
...
N
Figure 1: Standard Modbus Message
The address field extension adds a two-byte extended address field to the message. Figure
2 shows the format of an extended address Modbus message.
Field
Addres
s = 255
Size
1
Extended
Address
(high)
1
Extended
Address
(low)
1
Function
...
1
n
Figure 2: Extended Address Modbus Message
Messages for addresses 0 to 254 use the standard format message. The station address is
stored in the address byte.
Messages for stations 255 to 65534 use the extended address format message. The
address byte is set to 255. This indicates the extended address format is used. The actual
address is stored in the two extended address bytes.
Station address 65535 is reserved and cannot be used as a station number. This station
address is used in store-and-forward tables to indicate a disabled station.
Slave, master and store-and-forward stations treat the addresses in the same manner. The
application program controls the use of the extended addressing format. It may enable or
disable the extended addressing.
TeleBUS Protocols User and Reference Manual
May 8, 2007
11
Slave Mode
The TeleBUS protocols operate in slave and master modes simultaneously. In slave mode
the controller responds to commands sent by another device. Commands may be sent to a
specific device or broadcast to all devices.
The TeleBUS protocols emulate the Modbus protocol functions required for communication
with a host device. These functions are described below. It also implements functions for
programming and remote diagnostics. These functions are not required for host
communication, so are not described here.
A technical specification for the TeleBUS protocol is available from Control Microsystems. It
describes all the functions in detail. In most cases knowledge of the actual commands is not
required.
Broadcast Messages
A broadcast message is sent to all devices on a network. Each device executes the
command. No device responds to a broadcast command. The device sending the command
must query each device to determine if the command was received and processed.
Broadcast messages are supported for some function codes that write information.
A broadcast message is sent to station number 0.
Function Codes
The table summarizes the implemented function codes. The maximum number of registers
that can be read or written with one message is shown in the maximum column.
Function
01
02
03
04
05
06
07
15
16
17
Name
Read Coil Status
Read Input Status
Read Holding Register
Read Input Register
Force Single Coil
Preset Single Register
Read Exception
Status
Force Multiple Coils
Preset Multiple
Registers
Report Slave ID
Description
Reads digital output registers.
Reads digital input registers.
Reads analog output registers.
Reads analog input registers.
Writes digital output register.
Writes analog output registers.
Reads special information.
Maximum
2000
2000
125
125
1
1
N/A
Writes digital output registers.
Writes analog output registers.
880
60
Reads controller type
information
N/A
Functions 5, 6, 15, and 16 support broadcast messages. The functions are described in
detail below.
Read Coil Status
The Read Coil Status function reads data from the digital output section of the I/O database.
Any number of registers may be read up to the maximum number. The read may start at any
address, provided the entire block is within the valid register range. Each register is one bit.
TeleBUS Protocols User and Reference Manual
May 8, 2007
12
Read Input Status
The Read Input Status function reads data from the digital input section of the I/O database.
Any number of registers may be read up to the maximum number. The read may start at any
address, provided the entire block is within the valid register range. Each register is one bit.
Read Holding Register
The Read Holding Register function reads data from the analog output section of the I/O
database. Any number of registers may be read up to the maximum number. The read may
start at any address, provided the entire block is within the valid register range. Each
register is 16 bits.
Read Input Register
The Read Input Register function reads data from the analog input section of the I/O
database. Any number of registers may be read up to the maximum number. The read may
start at any address, provided the entire block is within the valid register range. Each
register is 16 bits.
Force Single Coil
The Force Single Coil function writes one bit into the digital output section of the I/O
database. The write may specify any valid register.
Preset Single Register
The Preset Single Register function writes one 16 bit value into the analog output section of
the I/O database. The write may specify any valid register.
Read Exception Status
The Read Exception Status function reads a single byte containing controller specific status
information. The information is defined by the application program. This function is included
for compatibility with devices expecting to communicate with a Modicon PLC.
Force Multiple Coils
The Force Multiple Coils function writes single bit values into the digital output section of the
I/O database. Any number of registers may be written up to the maximum number. The write
may start at any address, provided the entire block is within the valid register range. Each
register is 1 bit.
Preset Multiple Registers
The Preset Multiple Register function writes 16 bit values into the analog output section of
the I/O database. Any number of registers may be written up to the maximum number. The
write may start at any address, provided the entire block is within the valid register range.
Each register is 16 bits.
Report Slave ID
The Report Slave ID function reads a variable length message containing controller specific
information. The information and the length of the message is defined by the application
TeleBUS Protocols User and Reference Manual
May 8, 2007
13
program. This function is included for compatibility with devices expecting to communicate
with a Modicon PLC.
TeleBUS Protocols User and Reference Manual
May 8, 2007
14
Modbus Master Mode
The TeleBUS protocol may act as a communication master on any serial port. In master
mode, the controller sends commands to other devices on the network. Simultaneous
master messages may be active on all ports.
The protocol cannot support master mode and store-and-forward mode simultaneously on a
serial port. Enabling store and forward messaging disables processing of responses to
master mode commands. Master mode may be used on one port and store-and-forward
mode on another port.
Modbus Function Codes
The table shows the implemented function codes. The maximum number of registers that
can be read or written with one message is shown in the maximum column. The slave
device may support fewer registers than shown; consult the manual for the device for
details.
Function
01
02
03
04
05
06
15
16
Name
Read Coil Status
Read Input Status
Read Holding Register
Read Input Register
Force Single Coil
Preset Single Register
Force Multiple Coils
Preset Multiple
Registers
Description
Reads digital output registers.
Reads digital input registers.
Reads analog output registers.
Reads analog input registers.
Writes digital output register.
Writes analog output registers.
Writes digital output registers.
Writes analog output registers.
Maximum
2000
2000
125
125
1
1
880
60
Read Coil Status
The Read Coil Status function reads data from coil registers in the remote device. Data can
be written into the digital input or the digital output sections of the I/O database.
Any number of registers may be read up to the maximum number supported by the slave
device or the maximum number above, whichever is less. The read may start at any
address, provided the entire block is within the valid register range. Each register is one bit.
Read Input Status
The Read Input Status function reads data from input registers in the remote device. Data
can be written into the digital input or the digital output sections of the I/O database.
Any number of registers may be read up to the maximum number supported by the slave
device or the maximum number above, whichever is less. The read may start at any
address, provided the entire block is within the valid register range. Each register is one bit.
Read Holding Register
The Read Holding Register function reads data from holding registers in the remote device.
Data can be written into the analog input or the analog output sections of the I/O database.
TeleBUS Protocols User and Reference Manual
May 8, 2007
15
Any number of registers may be read up to the maximum number supported by the slave
device or the maximum number above, whichever is less. The read may start at any
address, provided the entire block is within the valid register range. Each register is 16 bits.
Read Input Register
The Read Input Register function reads data from input registers in the remote device. Data
can be written into the analog input or the analog output sections of the I/O database.
Any number of registers may be read up to the maximum number supported by the slave
device or the maximum number above, whichever is less. The read may start at any
address, provided the entire block is within the valid register range. Each register is 16 bits.
Force Single Coil
The Force Single Coil function writes one bit into a coil register in the remote device. The
data may come from the digital input or digital output sections of the I/O database.
The write may specify any valid coil register in the remote device.
Preset Single Register
The Preset Single Register function writes one 16 bit value into a holding register in the
remote device. The data may come from the analog input or output sections of the I/O
database.
The write may specify any valid holding register in the remote device.
Force Multiple Coils
The Force Multiple Coils function writes single bit values coil registers in the remote device.
The data may come from the digital input or digital output sections of the I/O database.
Any number of registers may be written up to the maximum number supported by the slave
device or the maximum number above, which ever is less. The write may start at any
address, provided the entire block is within the valid register range of the remote device.
Each register is 1 bit.
Preset Multiple Registers
The Preset Multiple Register function writes 16 bit values into holding registers of the remote
device. The data may come from the analog input or output sections of the I/O database.
Any number of registers may be written up to the maximum number supported by the slave
device or the maximum number above, which ever is less. The write may start at any
address, provided the entire block is within the valid register range of the remote device.
Each register is 16 bits.
TeleBUS Protocols User and Reference Manual
May 8, 2007
16
Enron Modbus Master Mode
The Enron Modbus protocol is based on the Modbus ASCII and RTU protocols. Message
framing is identical to the Modbus protocols. However, there are many differences in
message formatting and register numbering, at both the logical and protocol levels.
The document Specifications and Requirements for an Electronic Flow Measurement
Remote Terminal Unit describes the Enron Modbus protocol.
Variable Types
There are ranges of Enron registers to hold short integers, long integers and single precision
floats. The ranges are as follows.
Range
1001 - 1999
3001 - 3999
5001 - 5999
7000 - 9999
Data Type
Boolean
Short integer
Long integer
Float
In general, both Numeric and Boolean function codes can be used to read and write all
types of registers. Consult the Enron Modbus specification for details.
Boolean Registers
Enron Modbus Boolean registers are usually numbered 1001 to 1999.
Boolean registers are read using Modbus command 1. Boolean registers are written using
Modbus command 5 for single registers and 15 for multiple registers.
The address offset in the message is equal to the register number.
The number of Modbus registers is equal to the number of Enron registers.
The response format is identical to the Modbus response format.
Short Integer Registers
Enron Modbus Short Integer registers are usually numbered 3001 to 3999.
Short Integer registers are read using Modbus command 3. Short Integer registers are
written using Modbus command 6 for single registers and 16 for multiple registers.
The address offset in the message is equal to the register number.
The number of Modbus registers is equal to the number of Enron registers.
The response format is identical to the Modbus response format.
Long Integer Registers
Enron Modbus Long Integer registers are usually numbered 5001 to 5999.
Long Integer registers are read using Modbus command 3. Long Integer registers are
written using Modbus command 6 for single registers and 16 for multiple registers.
The address offset in the message is equal to the register number.
The number of Modbus registers requested is equal to the number of Enron registers.
The number of Modbus registers expected in the response is equal to two times the number
of Enron registers.
TeleBUS Protocols User and Reference Manual
May 8, 2007
17
Floating Point Registers
Enron Modbus Floating-point registers are usually numbered 7001 to 7999.
Floating-point registers are read using Modbus command 3. Floating-point registers are
written using Modbus command 6 for single registers and 16 for multiple registers.
The address offset in the message is equal to the register number.
The number of Modbus registers requested is equal to the number of Enron registers.
The number of Modbus registers expected in the response is equal to two times the number
of Enron registers.
Enron Modbus Function Codes
The following table shows the implemented function codes for Enron Modbus. The maximum
number of registers that can be read or written with one message is shown in the maximum
column. The slave device may support fewer registers than shown; consult the manual for
the device for details.
Functions 129, 130, 132, 133, 135, 136, 138, and 139 may be broadcast, but some Enron
Modbus slave devices may not support broadcast messages. Consult the manual for the
device for details.
Function
128
129
130
131
Name
Read Enron Boolean
Write Enron Boolean
Write Enron Multiple
Boolean
Read Enron Short Integer
132
Write Enron Short Integer
133
134
Write Enron Multiple Short
Integer
Read Enron Long Integer
135
Write Enron Long Integer
136
137
Write Enron Multiple Long
Integer
Read Enron Floating Point
138
Write Enron Floating Point
139
Write Enron Multiple Floating
Point
TeleBUS Protocols User and Reference Manual
May 8, 2007
Description
Read Enron Boolean registers
Write Enron Boolean register
Write Enron Boolean registers
Maximum
2000
1
880
Read Enron short integer
register
Write Enron short integer
register
Write Enron short integer
registers
Read Enron long integer
register
Write Enron long integer
register
Write Enron long integer
registers
Read Enron floating-point
register
Write Enron floating-point
register
Write Enron floating-point
registers
125
1
60
62
1
30
62
1
30
18
Sending Messages
A master message is initiated in one of five ways:
• using the master_message function from a C or C++ application program; or
• using the MSTR function block from a TelePACE ladder logic program; or
• using the MSIP function block from a TelePACE ladder logic program; or
• using the master function in an ISaGRAF program; or
• using the masterip function in an ISaGRAF program.
These functions specify the port on which to issue the command, the function code, the type
of station addressing, the slave station number, and the location and size of the data in the
slave and master devices. The protocol driver, independent of the application program
receives the response to the command.
The application program detects the completion of the transaction by:
• calling the get_protocol_status function in a C application program; or
• using the output of the MSTR function block in a TelePACE ladder logic program; or
• using the output of the master function in an ISaGRAF program.
A communication error has occurred if the slave does not respond within the expected
maximum time for the complete command and response. The application program is
responsible for detecting this condition. When errors occur, it is recommended that the
application program retry several times before indicating a communication failure.
The completion time depends on the length of the message, the length of the response, the
number of transmitted bits per character, the transmission baud rate, and the maximum
message turn-around time. One to three seconds is usually sufficient. Radio systems may
require longer delays.
TeleBUS Protocols User and Reference Manual
May 8, 2007
19
Store and Forward Messaging
Store and forward messaging is required on systems where there is no direct link between a
host computer and all the remote sites. This occurs on radio systems where the host
computer transmission cannot be heard by all remote sites. It occurs on systems where one
controller is used as a data concentrator for several remote units. With store and forward
messaging, a request to a controller that cannot be directly accessed by a host is routed
through an intermediate controller, which can communicate with both the host and the
remote controller.
The TeleBUS protocol provides store and forward messaging through address translation. A
controller configured for store and forward operation receives messages destined for a
remote station, re-addresses them according to translation table, and forwards the message
to the remote station. Responses from the remote station are processed in the same
manner.
The TeleBUS protocol allows messages to be re-transmitted on the same port with address
translation. This is used with radio systems. The radio at the intermediate site is used as a
type of repeater. The protocol allows messages to be re-transmitted on a different port, with
or without address translation. This is used where the intermediate controller is a bridge
between two networks.
The TeleBUS protocol driver maintains diagnostics counters at the store and forward site on
the number of messages received and transmitted to aid in the diagnosing of communication
problems.
The protocol cannot support master mode and store-and-forward mode simultaneously on a
serial port. Enabling store and forward messaging disables processing of responses to
master mode commands. Master mode may be used on one port and store-and-forward
mode on another port. Applications requiring both modes on a single port must switch the
modes under control of the application program.
Translation Table
The translation table specifies address and communication port translation. The translation
table differs for SCADAPack and SCADAPack 32 controllers. Each entry in the translation
table for SCADAPack controllers has four components, as shown in the table entry below.
Port A Station Address A Port B Station Address B
The entry defines a bi-directional transfer. A message (poll or reply) received for station A on
port A is re-transmitted to station B on port B. A message received for station B on port B is
re-transmitted to station A on port A.
Each entry in the translation table for SCADAPack 32 controllers has five components, as
shown in the table entry below.
Slave Interface
Slave Station
Forward
Interface
Forward Station
Forward IP
Address
The Slave Interface entry contains the receiving slave interface the message is received
from for each translation.
The Slave Station entry contains the Modbus station address of the slave message.
The Forward Interface entry contains the interface the message is forwarded from. When
forwarding to a TCP or UDP network, the protocol type is selected for the Forward Interface.
TeleBUS Protocols User and Reference Manual
May 8, 2007
20
The IP Stack automatically determines the exact interface (e.g. Ethernet1) to use when it
searches the network for the Forward IP Address.
The Forward Station entry contains the Modbus station address of the forwarded message.
The Forward IP Address entry contains the IP address of the Forward Station. This field is
blank unless a TCP or UDP network is selected for Forward Interface.
Table Size
The translation table holds 128 translation entries. This is sufficient to re-transmit one-half of
256 possible addresses. On a single port controller only 128 translations are required since
each address must translate to a different address for re-transmission on the same port see
Invalid Translations.
Invalid Translations
The following translations are not valid. The described action is taken when these
translations are encountered.
• Re-transmission on the same port with the same address is not valid, except for
broadcast messages. This restriction is required because many message responses are
identical to the command. It is impossible for the master station to distinguish between
the re-transmitted message and the response from the slave. The re-transmitted
message would appear to be the response.
• The protocol re-transmits broadcast messages on the same port. Some stations will
receive the broadcast message twice. The master station will also receive the message
and may execute it if it is able to operate as a slave. The user must bear these
consequences in mind when forwarding broadcast messages.
• The store and forward controller also processes broadcast messages.
• Translations where either of the station addresses are the same as the controller station
address for the port, are not valid. The protocol processes these messages as if they
were directed to the controller. It does not look up the address in the translation table.
• Translations with non-existent port numbers or invalid addresses are not valid.
• Multiple translations for a port and station address combination are not valid.
• Translations where one station is DISABLED and the other station is not, are not valid. A
DISABLED translation is a valid translation.
Store and Forward Configuration
The Store and Forward configuration varies depending on the controller you are configuring.
The configuration for each type of controller is described in the following sections.
SCADAPack Controller
An application program, written in TelePACE Ladder Logic or TelePACE C Tools and
ISaGRAF IEC61131 or ISaGRAF IEC61131 C Tools programming, enables and configures
store and forward messaging. A HMI host may enable and configure store and forward
messaging through the controller I/O database.
TeleBUS Protocols User and Reference Manual
May 8, 2007
21
TelePACE Ladder Logic
1. To enable the use of store and forward messaging on one or more serial ports the
Configuration I/O Module CNFG Protocol Settings Method 1, 2 or 3 must be added to
the register assignment. The store and forward enable register must be set to enable.
2. Add the Configuration I/O Module CNFG Store and Forward to the register assignment
to configure the translation table.
3. Configure the translation table by writing the necessary translation table entries to the
registers defined in the CNFG Store and Forward I/O module.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when TelePACE programming software or a SERVICE
boot initializes the controller. This prevents inadvertent forwarding of messages when new
controllers are installed on networks.
TelePACE C Tools
The TelePACE C language application program interface provides the following functions.
Refer to the TelePACE C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to DISABLED (station
256).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
ISaGRAF IEC61131
1. To enable the use of store and forward messaging on one or more serial ports the
Custom Function setprot or setprot2 must be added to the project. The SandFEnabled
input must be set to TRUE.
2. Configure the translation table by using the setsf function to write the necessary
translation table entries.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when ISaGRAF IEC61131 programming software or a
SERVICE boot initializes the controller. This prevents inadvertent forwarding of messages
when new controllers are installed on networks.
ISaGRAF IEC61131 C Tools
The ISaGRAF C language application program interface provides the following functions.
Refer to the ISaGRAF C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
TeleBUS Protocols User and Reference Manual
May 8, 2007
22
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
SCADAPack Light Controller
An application program, written in TelePACE Ladder Logic or TelePACE C Tools and
ISaGRAF IEC61131 or ISaGRAF IEC61131 C Tools programming, enables and configures
store and forward messaging. A HMI host may enable and configure store and forward
messaging through the controller I/O database.
TelePACE Ladder Logic
1. To enable the use of store and forward messaging on one or more serial ports the
Configuration I/O Module CNFG Protocol Settings Method 1, 2 or 3 must be added to
the register assignment. The store and forward enable register must be set to enable.
2. Add the Configuration I/O Module CNFG Store and Forward to the register assignment
to configure the translation table.
3. Configure the translation table by writing the necessary translation table entries to the
registers defined in the CNFG Store and Forward I/O module.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when TelePACE programming software or a SERVICE
boot initializes the controller. This prevents inadvertent forwarding of messages when new
controllers are installed on networks.
TelePACE C Tools
The TelePACE C language application program interface provides the following functions.
Refer to the TelePACE C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
TeleBUS Protocols User and Reference Manual
May 8, 2007
23
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
ISaGRAF IEC61131
1. To enable the use of store and forward messaging on one or more serial ports the
Custom Function setprot or setprot2 must be added to the project. The SandFEnabled
input must be set to TRUE.
2. Configure the translation table by using the setsf function to write the necessary
translation table entries.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when ISaGRAF IEC61131 programming software or a
SERVICE boot initializes the controller. This prevents inadvertent forwarding of messages
when new controllers are installed on networks.
ISaGRAF IEC61131 C Tools
The ISaGRAF C language application program interface provides the following functions.
Refer to the ISaGRAF C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
SCADAPack Plus Controller
An application program, written in TelePACE Ladder Logic or TelePACE C Tools and
ISaGRAF IEC61131 or ISaGRAF IEC61131 C Tools programming, enables and configures
store and forward messaging. A HMI host may enable and configure store and forward
messaging through the controller I/O database.
TelePACE Ladder Logic
1. To enable the use of store and forward messaging on one or more serial ports the
Configuration I/O Module CNFG Protocol Settings Method 1, 2 or 3 must be added to
the register assignment. The store and forward enable register must be set to enable.
2. Add the Configuration I/O Module CNFG Store and Forward to the register assignment
to configure the translation table.
3. Configure the translation table by writing the necessary translation table entries to the
registers defined in the CNFG Store and Forward I/O module.
TeleBUS Protocols User and Reference Manual
May 8, 2007
24
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when TelePACE programming software or a SERVICE
boot initializes the controller. This prevents inadvertent forwarding of messages when new
controllers are installed on networks.
TelePACE C Tools
The TelePACE C language application program interface provides the following functions.
Refer to the TelePACE C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
ISaGRAF IEC61131
1. To enable the use of store and forward messaging on one or more serial ports the
Custom Function setprot or setprot2 must be added to the project. The SandFEnabled
input must be set to TRUE.
2. Configure the translation table by using the setsf function to write the necessary
translation table entries.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when ISaGRAF IEC61131 programming software or a
SERVICE boot initializes the controller. This prevents inadvertent forwarding of messages
when new controllers are installed on networks.
ISaGRAF IEC61131 C Tools
The ISaGRAF C language application program interface provides the following functions.
Refer to the ISaGRAF C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
TeleBUS Protocols User and Reference Manual
May 8, 2007
25
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
SCADAPack LP Controller
An application program, written in TelePACE Ladder Logic or TelePACE C Tools and
ISaGRAF IEC61131 or ISaGRAF IEC61131 C Tools programming, enables and configures
store and forward messaging. A HMI host may enable and configure store and forward
messaging through the controller I/O database.
TelePACE Ladder Logic
1. To enable the use of store and forward messaging on one or more serial ports the
Configuration I/O Module CNFG Protocol Settings Method 1, 2 or 3 must be added to
the register assignment. The store and forward enable register must be set to enable.
2. Add the Configuration I/O Module CNFG Store and Forward to the register assignment
to configure the translation table.
3. Configure the translation table by writing the necessary translation table entries to the
registers defined in the CNFG Store and Forward I/O module.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when TelePACE programming software or a SERVICE
boot initializes the controller. This prevents inadvertent forwarding of messages when new
controllers are installed on networks.
TelePACE C Tools
The TelePACE C language application program interface provides the following functions.
Refer to the TelePACE C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
ISaGRAF IEC61131
1. To enable the use of store and forward messaging on one or more serial ports the
Custom Function setprot or setprot2 must be added to the project. The SandFEnabled
input must be set to TRUE.
2. Configure the translation table by using the setsf function to write the necessary
translation table entries.
TeleBUS Protocols User and Reference Manual
May 8, 2007
26
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when ISaGRAF IEC61131 programming software or a
SERVICE boot initializes the controller. This prevents inadvertent forwarding of messages
when new controllers are installed on networks.
ISaGRAF IEC61131 C Tools
The ISaGRAF C language application program interface provides the following functions.
Refer to the ISaGRAF C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
SCADAPack 100 Controller
An application program, written in TelePACE Ladder Logic or TelePACE C Tools and
ISaGRAF IEC61131 or ISaGRAF IEC61131 C Tools programming, enables and configures
store and forward messaging. A HMI host may enable and configure store and forward
messaging through the controller I/O database.
TelePACE Ladder Logic
1. To enable the use of store and forward messaging on one or more serial ports the
Configuration I/O Module CNFG Protocol Settings Method 1, 2 or 3 must be added to
the register assignment. The store and forward enable register must be set to enable.
2. Add the Configuration I/O Module CNFG Store and Forward to the register assignment
to configure the translation table.
3. Configure the translation table by writing the necessary translation table entries to the
registers defined in the CNFG Store and Forward I/O module.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when TelePACE programming software or a SERVICE
boot initializes the controller. This prevents inadvertent forwarding of messages when new
controllers are installed on networks.
TelePACE C Tools
The TelePACE C language application program interface provides the following functions.
Refer to the TelePACE C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
TeleBUS Protocols User and Reference Manual
May 8, 2007
27
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
ISaGRAF IEC61131
1. To enable the use of store and forward messaging on one or more serial ports the
Custom Function setprot or setprot2 must be added to the project. The SandFEnabled
input must be set to TRUE.
2. Configure the translation table by using the setsf function to write the necessary
translation table entries.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when ISaGRAF IEC61131 programming software or a
SERVICE boot initializes the controller. This prevents inadvertent forwarding of messages
when new controllers are installed on networks.
ISaGRAF IEC61131 C Tools
The ISaGRAF C language application program interface provides the following functions.
Refer to the ISaGRAF C Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
SCADAPack 350, SCADAPack 32 and 32P Controller
An application program, written in TelePACE Ladder Logic or TelePACE C++ Tools and
ISaGRAF IEC61131 or ISaGRAF IEC61131 C++ Tools programming, enables and
configures store and forward messaging. A HMI host may enable and configure store and
forward messaging through the controller I/O database.
TeleBUS Protocols User and Reference Manual
May 8, 2007
28
TelePACE Ladder Logic
When a SCADAPack 350, SCADAPack 32 or SCADAPack 32P controllers are used the
store and forward translation table is configured using an Element Configuration dialog.
From the Controller menu select the Store and Forward command to access the element
configuration. Refer to the TelePACE Ladder Logic Program Reference Manual for complete
information on using the Store and Forward element configuration.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when TelePACE programming software or a SERVICE
boot initializes the controller. This prevents inadvertent forwarding of messages when new
controllers are installed on networks.
TelePACE C++ Tools
The SCADAPack 32 C++ language application program interface provides the following
functions. Refer to the SCADAPack 32 C++ Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
ISaGRAF IEC61131
1. To enable the use of store and forward messaging on one or more serial ports the
Custom Function setprot or setprot2 must be added to the project. The SandFEnabled
input must be set to TRUE.
2. Configure the translation table by using the setsfip2 function to write the necessary
translation table entries.
The translation table must be initialized before store and forward messaging is enabled.
Forwarding of messages is disabled when ISaGRAF IEC61131 programming software or a
SERVICE boot initializes the controller. This prevents inadvertent forwarding of messages
when new controllers are installed on networks.
ISaGRAF IEC61131 C++ Tools
The SCADAPack 32 C++ language application program interface provides the following
functions. Refer to the SCADAPack 32 C++ Tools Reference and User Manual for details.
• The getSFTranslation function returns an entry from the store and forward translation
table. The entry consists of two port and station address pairs.
• The setSFTranslation function writes an entry into the store and forward translation
table. The entry consists of two port and station address pairs. The function checks for
invalid translations; if the translation is not valid it is not stored. The function returns a
TeleBUS Protocols User and Reference Manual
May 8, 2007
29
status code indicating success or an error if the translation is not valid. A translation is
cleared from the table by writing a translation with both stations set to
DISABLED_STATION (65535).
• The clearSFTranslationTable function clears all entries in the translation table. A
cleared entry has the port set to 0 (com1) and the station set to DISABLED_STATION
(65535).
• The checkSFTranslationTable function checks the translation table for invalid entries. It
returns a status structure indicating if the table is valid and the location and type of the
first error if it is not valid.
Diagnostics Counters
The TeleBUS protocol provides diagnostics counters for each serial port. The counters aid in
determining the source of communication errors. Store and forward messaging provides the
following counters for each communication port. All counters have a maximum count of
65535. Counters roll back to zero on the next event.
• Stored Message Counter: the number of messages received, which qualified for
forwarding. A message qualifies for forwarding if a valid translation is found for the port
and station in the translation table.
• Forwarded Message Counter: the number of messages forwarded (transmitted) on this
port.
Refer to the user manual for the controller and programming environment you are using for
information on the diagnostics counters.
TeleBUS Protocols User and Reference Manual
May 8, 2007
30
Point–To–Point Protocol (PPP)
SCADAPack 32 and SCADAPack 32P controllers support Point-to-Point Protocol (PPP) on
the serial ports. Any serial port may be configured for the PPP protocol. Once a PPP
connection is established the serial port has access to all IP protocol servers enabled on the
controller.
A serial port configured for PPP supports an auto answer mode when dialed up through a
modem. After answering the modem the serial port performs the login steps according to the
authentication option selected for the port.
PPP provides two authentication protocols, which automates logins - PAP (Password
Authentication Protocol) and CHAP (Challenge-Handshake Authentication Protocol).
PPP settings are configurable for each serial port on the SCADAPack 32 or SCADAPack
32P controller.
An inactivity timeout closes the PPP connection and hangs up the modem when the
connection becomes idle. The timeout may also be disabled. Timeout range is 1 to 65535
minutes (~1092 hours maximum).
When the PPP protocol is selected for a serial port, the serial port must be assigned a
unique IP address, different from the IP address assigned to Ethernet or any other active
PPP connection.
The remote end of a PPP connection may request an IP address from the controller PPP
Server. The PPP Server will provide this IP address if requested.
Only one default gateway may be assigned to the controller. A PPP connection may be
configured as the gateway.
PPP Client Setup in Windows 2000
This section describes the procedure for setting up a PPP client from a Windows 2000 PC.
Client setup for a dialup PPP connection and a direct serial PPP connection are presented.
Direct Serial PPP Connection using Windows 2000
Connection Setup
Use this connection when an only serial cable is used to establish a PPP connection
between a Windows 2000 PC and a SCADAPack 32, without a dialup modem.
1. From the Start menu, right click Network and Dial-up Connections from the Settings
group, and select Open. The Network and Dial-up Connections dialog is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
31
2. Double click the item Make New Connection from the Network and Dial-up
Connections dialog. The connection wizard dialog is displayed.
3. Select the Next button to display the connection type options dialog.
TeleBUS Protocols User and Reference Manual
May 8, 2007
32
4. For Network Connection Type select the type Connect directly to another computer and
select the Next button. The Host or Guest options dialog is displayed.
5. Select the Guest option and the Next button. The Select a Device dialog is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
33
6. From the menu select the serial port on your PC that will be used to connect to the
SCADAPack 32. Select the Next button. The Connection Availability dialog is displayed.
7. Select either option and then select the Next button. The Connection Name dialog is
displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
34
8. Enter a name for the connection and select the Finish button. The username and password
prompt is displayed.
9. Select the Cancel button. The Network and Dial-up Connections dialog should be visible
again.
TeleBUS Protocols User and Reference Manual
May 8, 2007
35
10. Right click your new Direct Connection icon from the Network and Dial-up Connections
dialog and select Properties from the list. The Properties dialog is displayed.
11. Select the Configure button from the General page. The Modem Configuration dialog is
displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
36
12. There is no modem in this direct serial connection so uncheck all items including hardware
flow control. Select the baud rate you intend to use (e.g. 9600 bps). Select OK to return to
the Properties dialog.
13. From the Properties dialog select the Networking page.
TeleBUS Protocols User and Reference Manual
May 8, 2007
37
14. Uncheck all components except the component Internet Protocol (TCP/IP). Select the
component Internet Protocol (TCP/IP) and select the Properties button. The Internet
Protocol (TCP/IP) Properties dialog is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
38
15. The SCADAPack 32 does not have a DHCP server to automatically provide an IP address.
Instead the PC’s serial port must be given a fixed IP address to use for PPP connections.
Select the option Use the following IP address. Enter an IP address to assign to your PC’s
serial port. Obtain this IP address from your Network Administrator. Then select OK to return
to the Properties dialog.
16. Select OK again to close the dialog.
Making a PPP Connection to the SCADAPack 32
A connection can only be made after successfully setting up a Direct Connection icon as
described in the section Connection Setup above. Also, a serial port on the SCADAPack 32
must already be configured for the PPP protocol using the Controller IP Configuration dialog
and must be downloaded to the SCADAPack 32.
1. From the Start menu, double click Network and Dial-up Connections from the
Settings group. The Network and Dial-up Connections dialog is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
39
2. Right click your Direct Connection icon that was setup in the previous section and select
Connect from the list. A prompt for username and password is displayed.
3. Enter a valid PAP or CHAP username and password. Valid usernames and passwords
are configured on the PPP Login page of the Controller IP Configuration dialog and must
be downloaded to the SCADAPack 32. Then select the Connect button. If neither PAP
nor CHAP is being used, ignore the prompt and just select the Connect button.
4. A progress message is displayed. If the connection is successful the following message
is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
40
5. You may now connect to the IP address assigned to SCADAPack 32 PPP serial port
using an appropriate application and a supported protocol (e.g. Modbus/TCP). In the
example below, Firmware Loader is used to connect over PPP to the SCADAPack 32.
From the PC Communication Settings dialog, the IP address assigned to the
SCADAPack 32 PPP serial port is selected as the Connect to Host.
Disconnecting a PPP Connection
To disconnect a PPP connection made using the Windows PPP Client, do the following:
TeleBUS Protocols User and Reference Manual
May 8, 2007
41
1. From the Start menu, double click Network and Dial-up Connections from the
Settings group. The Network and Dial-up Connections dialog is displayed.
2. Your Direct Connection icon should display the word Connected in the Status column.
To disconnect, right click your Direct Connection icon and select Disconnect from the
list.
Dial-up PPP Connection using Windows 2000
Connection Setup using Windows 2000
Use this connection when a dial-up modem is used to establish a PPP connection between
a Windows 2000 PC and a SCADAPack 32.
1. From the Start menu, right click Network and Dial-up Connections from the Settings
group, and select Open. The Network and Dial-up Connections dialog is displayed.
2. Double click the item Make New Connection from the Network and Dial-up
Connections dialog. The connection wizard dialog is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
42
3. Select the Next button to display the connection type options dialog.
4. For Network Connection Type select the type Dial-up to private network and select the
Next button. If there is more than one modem installed on the PC, the Select a Device
dialog is displayed. If not, proceed to the next step.
TeleBUS Protocols User and Reference Manual
May 8, 2007
43
5. From the menu select the modem installed on your PC that will be used to connect to
the SCADAPack 32. Select the Next button. The Phone Number to Dial dialog is
displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
44
6. Enter the phone number to dial (this can be changed later) and select the Next button.
The Connection Availability dialog is displayed.
7. Select either option and then select the Next button. The Connection Name dialog is
displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
45
8. Enter a name for the connection and select the Finish button. The username and
password prompt is displayed.
9. Select the Cancel button. The Network and Dial-up Connections dialog should be visible
again.
10. Right click your new Dial-up Connection icon from the Network and Dial-up Connections
dialog and select Properties from the list. The Properties dialog is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
46
11. From the Properties dialog select the Networking page.
TeleBUS Protocols User and Reference Manual
May 8, 2007
47
12. Uncheck all components except the component Internet Protocol (TCP/IP). Select the
component Internet Protocol (TCP/IP) and select the Properties button. The Internet
Protocol (TCP/IP) Properties dialog is displayed.
13. The SCADAPack 32 does not have a DHCP server to automatically provide an IP
address. Instead the PC’s serial port must be given a fixed IP address to use for PPP
connections. Select the option Use the following IP address. Enter an IP address to
assign to your PC’s serial port. Obtain this IP address from your Network Administrator.
Then select OK to return to the Properties dialog.
14. Select OK again to close the dialog.
Making a PPP Dial-up Connection to the SCADAPack 32 using Windows
2000
A connection can only be made after successfully setting up a Dial-up Connection icon as
described in the section Connection Setup above. Also, a serial port on the SCADAPack 32
must already be configured for the PPP protocol using the Controller IP Configuration dialog
and must be downloaded to the SCADAPack 32.
1. From the Start menu, right click Network and Dial-up Connections from the Settings
group, and select Open. The Network and Dial-up Connections dialog is displayed.
TeleBUS Protocols User and Reference Manual
May 8, 2007
48
2. Right click your Dial-up Connection icon that was setup in the previous section and
select Connect from the list. A prompt for username and password is displayed.
3. Enter a valid PAP or CHAP username and password. Valid usernames and passwords
are configured on the PPP Login page of the Controller IP Configuration dialog and must
be downloaded to the SCADAPack 32. Then select the Dial button. If neither PAP nor
CHAP is being used, ignore the prompt and just select the Dial button.
4. A progress message is displayed. If the connection is successful your Dial-up
Connection icon should display the word Connected in the Status column.
5. You may now connect to the IP address assigned to SCADAPack 32 PPP serial port
using an appropriate application and a supported protocol (e.g. Modbus/TCP). In the
example below, Firmware Loader is used to connect over PPP to the SCADAPack 32.
From the PC Communication Settings dialog, the IP address assigned to the
SCADAPack 32 PPP serial port is selected as the Connect to Host.
TeleBUS Protocols User and Reference Manual
May 8, 2007
49
Disconnecting a PPP Connection using Windows 2000
To disconnect a PPP connection made using the Windows PPP Client, do the following:
1. From the Start menu, right click Network and Dial-up Connections from the Settings
group, and select Open. The Network and Dial-up Connections dialog is displayed.
2. Your Dial-up Connection icon should display the word Connected in the Status column.
To disconnect, right click your Dial-up Connection icon and select Disconnect from the
list.
TeleBUS Protocols User and Reference Manual
May 8, 2007
50
TelePACE Ladder Logic
DF1 Protocol User Manual
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
TelePACE Ladder Logic Warranty and License
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE, TeleSAFE
Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus, SCADAPack 32, SCADAPack
32P, SCADAPack 350, SCADAPack LP, SCADAPack 100, SCADASense 4202 DS,
SCADASense 4202 DR, SCADASense 4203 DS, SCADASense 4203 DR, SCADASense
4102, SCADASense 4012, SCADASense 4032 and TeleBUS are registered trademarks of
Control Microsystems.
All other product names are copyright and registered trademarks or trade names of their
respective owners.
Material used in the User and Reference manual section titled SCADAServer OLE
Automation Reference is distributed under license from the OPC Foundation.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
1
Table of Contents
TABLE OF CONTENTS .......................................................................................................... 2
TELEBUS DF1 PROTOCOL OVERVIEW............................................................................... 4
Compatibility........................................................................................................................ 4
SERIAL PORT CONFIGURATION ......................................................................................... 5
Communication Parameters ............................................................................................... 5
Protocol Parameters ...................................................................................................... 5
Baud Rate ...................................................................................................................... 5
Duplex............................................................................................................................ 6
Protocol Parameters ........................................................................................................... 7
Protocol Type................................................................................................................. 7
Station Number .............................................................................................................. 7
Task Priority ................................................................................................................... 7
Store and Forward Messaging ...................................................................................... 7
Default Parameters ............................................................................................................. 7
I/O DATABASE........................................................................................................................ 9
Coil and Status Registers ................................................................................................... 9
Input and Holding Registers................................................................................................ 9
Accessing the I/O Database Using TelePACE ................................................................. 10
Modbus Addressing ..................................................................................................... 10
DF1 Addressing ........................................................................................................... 11
Converting Modbus to DF1 Addresses........................................................................ 11
Accessing the I/O Database Using ISaGRAF .................................................................. 13
Modbus Addressing ..................................................................................................... 13
DF1 Addressing ........................................................................................................... 13
Converting Modbus to DF1 Addresses........................................................................ 14
SLAVE MODE........................................................................................................................ 16
Broadcast Messages ........................................................................................................ 16
Function Codes ................................................................................................................. 16
Protected Write ............................................................................................................ 17
Unprotected Read........................................................................................................ 17
Protected Bit Write ....................................................................................................... 17
Unprotected Bit Write................................................................................................... 17
Unprotected Write........................................................................................................ 17
MASTER MODE .................................................................................................................... 18
Function Codes ................................................................................................................. 18
Protected Write ............................................................................................................ 18
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
2
Unprotected Read........................................................................................................ 18
Protected Bit Write ....................................................................................................... 19
Unprotected Bit Write................................................................................................... 19
Unprotected Write........................................................................................................ 19
Sending Messages ........................................................................................................... 19
Polling DF1 PLCs ........................................................................................................ 20
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
3
TeleBUS DF1 Protocol Overview
TeleBUS communication protocols provide a standard communication interface to the
controller. The protocols operate on a wide variety of serial data links. These include RS-232
serial ports, RS-485 serial ports, radios, leased line modems, and dial up modems. The
protocols are generally independent of the communication parameters of the link, with a few
exceptions.
TeleBUS protocol commands may be directed to a specific device, identified by its station
number, or broadcast to all devices. Up to 255 devices may connect to one communication
network.
The TeleBUS protocols provide full access to the I/O database in the controller. The I/O
database contains user-assigned registers and general purpose registers. Assigned
registers map directly to the I/O hardware or system parameter in the controller. General
purpose registers can be used by ladder logic and C application programs to store
processed information, and to receive information from a remote device.
Application programs can initiate communication with remote devices. A multiple port
controller can be a data concentrator for remote devices, by polling remote devices on one
port and responding as a slave on another port.
The protocol type, communication parameters and station address are configured separately
for each serial port on a controller. One controller can appear as different stations on
different communication networks. The port configuration can be set from an application
program, from the TelePACE programming software, or from another Modbus or DF1
compatible device.
Compatibility
There are four TeleBUS DF1 protocols:
• The TeleBUS DF1 Full-Duplex BCC protocol is compatible with the DF1 Full-Duplex data
link layer protocol with block check character (BCC) error checking.
• The TeleBUS DF1 Full-Duplex CRC protocol is compatible with the DF1 Full-Duplex data
link layer protocol with 16-bit cyclic redundancy check (CRC-16) error checking.
• The TeleBUS DF1 Half-Duplex BCC protocol is compatible with the DF1 Half-Duplex data
link layer protocol with block check character (BCC) error checking.
• The TeleBUS DF1 Half-Duplex CRC protocol is compatible with the DF1 Half-Duplex data
link layer protocol with 16-bit cyclic redundancy check (CRC-16) error checking.
Compatibility refers to communication only. The protocol defines communication aspects
such as commands, syntax, message framing, error handling and addressing. The
controllers do not mimic the internal functioning of any programmable controller. Device
specific functions – those that relate to the hardware or programming of a specific
programmable controller – are not implemented.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
4
Serial Port Configuration
Communication Parameters
The TeleBUS DF1 protocols are, in general, independent of the serial communication
parameters. The baud rate and parity may be chosen to suit the host computer and the
characteristics of the data link.
The port configuration can be set in four ways:
• using the TelePACE program;
• using the set_port function from a C application program;
• writing to the I/O database from a C or ladder logic application program; or
• writing to the I/O database remotely from a Modbus or DF1 compatible device.
To configure a serial port through the I/O database, add the module, CNFG Serial port
settings, to the Register Assignment.
Protocol Parameters
The TeleBUS DF1 protocols are eight bit character-oriented protocols. The table below
shows possible and recommended communication parameters.
Parameter
Possible Settings
Baud Rate
Recommended
Setting
see Baud Rate
section below
8 data bits
none
see Baud Rate
section below
Data Bits
8 data bits
Parity
none
even
odd
Stop bits
1 stop bit
1 stop bit
2 stop bits1
Flow control
disabled
disabled
Duplex
see Duplex section see Duplex section
below
below
1
Not applicable on the SCADAPack 350
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
5
Baud Rate
The baud rate sets the communication speed. The possible settings are determined by the
type of serial data link used. The table below shows the possible settings for the controller.
Note that not all port types and baud rates are available on all controller ports.
Port Type
RS-232 or
RS-232
Dial-up
modem
RS-485
Possible
Settings
75 baud
110 baud
150 baud
300 baud
600 baud
1200 baud
2400 baud
4800 baud
9600 baud
19200 baud
38400 baud
57600 baud
115200 baud
75 baud
110 baud
150 baud
300 baud
600 baud
1200 baud
2400 baud
4800 baud
9600 baud
19200 baud
38400 baud
Recommended Setting
Use the highest rate
supported by all devices on
the network.
Use the highest rate
supported by all devices on
the network.
Duplex
The TeleBUS DF1 protocols communicate in one direction at a time. However the duplex
setting is determined by the type of serial data link used. The table below shows the possible
settings for the controller. Note that not all port types are available on all controllers.
Port Type
RS-232 or
RS-232
Dial-up
modem
RS-485
Possible
Settings
half duplex
full duplex
half duplex
full duplex
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
Recommended Setting
Use full duplex wherever
possible.
Use half duplex for most
external modems.
Slave stations always use
half duplex.
Master stations can use full
duplex only on 4 wire
systems.
6
Protocol Parameters
The TeleBUS DF1 protocols operate independently on each serial port. Each port may set
the protocol type, station number, protocol task priority and store-and-forward messaging
options.
The protocol configuration can be set in four ways:
• using the TelePACE or ISaGRAF programs;
• using the set_protocol function from a C application program;
• writing to the I/O database from a C or ladder logic application program; or
• writing to the I/O database remotely from a Modbus or DF1 compatible device.
To configure protocol settings through the I/O database, add the module, CNFG Protocol
settings, to the Register Assignment.
Protocol Type
The protocol type may be set to emulate the DF1 or Modbus protocols, or it may be
disabled. When the protocol is disabled, the port functions as a normal serial port.
Station Number
The TeleBUS DF1 protocols allow up to 255 devices on a network. Station numbers identify
each device. A device responds to commands addressed to it, or to commands broadcast to
all stations.
The station number is in the range 0 to 254. Address 255 indicates a command broadcast to
all stations, and cannot be used as a station number. Each serial port may have a unique
station number.
Task Priority
A task is responsible for monitoring each serial port for messages. The real time operating
system (RTOS) schedules the tasks with the application program tasks according to the task
priority. The priority can be changed only with the set_protocol function from a C
application program.
The default task priority is 3. Changing the priority is not recommended.
Store and Forward Messaging
Store and forward messaging is not supported by the TeleBUS DF1 protocols.
Default Parameters
All ports are configured at reset with default parameters when the controller is started in
SERVICE mode. The ports use user-defined parameters when the controller is reset in the
RUN mode. The default parameters are listed below.
Parameter
Baud rate
Parity
Data bits
com1
9600
none
8
com2
9600
none
8
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
Com3
9600
None
8
com4
9600
none
8
7
Parameter
Stop bits
Duplex
Protocol
Station
Rx flow control
Tx flow control
Serial time out
Type
Minimum
Protected DF1
Address
Maximum
Protected DF1
Address
com1
1
full
Modbus
RTU
1
none
com2
1
full
Modbus
RTU
1
none
none
60 s
RS-232
0
Com3
1
Half
Modbus
RTU
1
Rx
disable
None
60 s
RS-232
0
com4
1
half
Modbus
RTU
1
Rx
disable
none
60 s
RS-232
0
none
60 s
RS-232
0
11534
11534
11534
11534
Notes
com3 is supported only when the SCADAPack Lower I/O module is installed. com4 is
supported only when the SCADAPack Upper I/O module is installed.
To optimize performance, minimize the length of messages on com3 and com4. Examples
of recommended uses for com3 and com4 are for local operator display terminals, and for
programming and diagnostics using the TelePACE program.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
8
I/O Database
The TeleBUS protocols read and write information from the I/O database. The I/O database
is an area of memory that can be accessed by C programs, Ladder Logic programs,
ISaGRAF programs and communication protocols. The I/O database allows data to be
shared between these programs. The I/O database contains user-assigned registers and
general purpose registers.
User-assigned registers map directly to the I/O hardware or system parameter in the
controller. Assigned registers are initialized to the default hardware state or system
parameter when the controller is reset. Assigned output registers do not maintain their
values during power failures. However, output registers do retain their values during
application program loading.
General purpose registers are used by ladder logic, ISaGRAFand C application programs to
store processed information, and to receive information from remote devices. General
purpose registers retain their values during power failures and application program loading.
The values change only when written by an application program or a communication
protocol.
Coil and Status Registers
Coil and status registers contain one bit of information, that is whether a signal is off or on.
For TelePACE firmware coil registers are single bits, which the protocols can read and write.
There are 4096 coil registers located in the digital output section of the I/O database. Coil
registers are contained within the DF1 16-bit addresses 0 to 255.
For TelePACE firmware status registers are single bits, which the protocols can read. There
are 4096 status registers located in the digital input section of the I/O database. Status
registers are contained within the DF1 16-bit addresses 256 to 511.
For ISaGRAF firmware coil registers are single bits, which the protocols can read and write.
There are 9999 coil registers located in the digital output section of the I/O database. Coil
registers are contained within the DF1 16-bit addresses 0 to 624.
For ISaGRAF firmware status registers are single bits, which the protocols can read. There
are 9999 status registers located in the digital input section of the I/O database. Status
registers are contained within the DF1 16-bit addresses 625 to 1249.
Coil and status registers are accessed 16 at a time or individually (in some commands)
using a bitmask. Writing a one to a bit within the 16-bit address turns the bit on. Writing zero
to the bit turns the bit off. If the register is assigned to an I/O module, the bit status is written
to the module output hardware or parameter.
Reading a coil or status register returns 1 if the bit is on, or 0 if the bit is off. The stored value
is returned from general purpose registers. The I/O module point status is returned from
assigned registers.
Input and Holding Registers
Input and holding registers contain 16-bit values.
Input registers are 16-bit registers, which the protocol can read. For TelePACE firmware,
there are 1024 input registers located in the analog input section of the I/O database. Input
registers are contained within the DF1 addresses 512 to 1535.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
9
For ISaGRAF firmware there are 9999 input registers located in the analog input section of
the I/O database. Input registers are contained within the DF1 addresses 1250 to 11247.
Holding registers are 16-bit registers that the protocol can read and write. For TelePACE
firmware there are 9999 holding registers located in the analog output section of the I/O
database. Holding registers are contained within the DF1 addresses 1536 to 11534.
For ISaGRAF firmware there are 9999 holding registers located in the analog output section
of the I/O database. Holding registers are contained within the DF1 addresses 11248 to
21247.
Writing any value to a general purpose register stores the value in the register. Writing a
value to an assigned register, writes the value to the assigned I/O module.
Reading a general purpose register returns the value stored in the register. Reading an
assigned register returns the value read from the I/O module.
Accessing the I/O Database Using TelePACE
Ladder logic programs access the I/O database through function blocks. All function blocks
can access the I/O database. The function blocks in ladder logic use only the Modbus
addressing scheme. Refer to the TelePACE Ladder Logic Reference and User Manual for
details.
C language programs access the I/O database with two functions. The dbase function reads
a value from the I/O database. The setdbase function writes a value to the I/O database.
These functions use either Modbus or DF1 physical addressing. Refer to the TelePACE C
Tools Reference and User Manual for full details on these functions.
Modbus Addressing
Modbus addressing is used in all ladder logic program functions. The controller’s Register
Assignment is also configured using Modbus addresses. The C functions dbase and
setdbase support Modbus addressing. When the specified port is configured for one of the
Modbus protocols, the function master_message uses Modbus addressing.
The range of Modbus registers available depends on the controller being used. The
following sections list the Modbus registers available for each controller type.
SCADAPack, SCADAPack 100: 1024K and SCADASense 4202 Series
Coil registers are single bit addresses ranging from 00001 to 04096.
Status registers are single bit addresses ranging from 10001 to 14096.
Input registers are 16-bit addresses in the range 30001 to 31024.
Holding registers are 16-bit addresses in the range 40001 to 49999.
SCADAPack 100: 256K Controllers
Coil registers are single bit addresses ranging from 00001 to 04096.
Status registers are single bit addresses ranging from 10001 to 14096.
Input registers are 16-bit addresses in the range 30001 to 30512.
Holding registers are 16-bit addresses in the range 40001 to 44000.
SCADAPack 350, SCADAPack 32, and SCADASense 4203 Series
Coil registers are single bit addresses ranging from 00001 to 04096.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
10
Status registers are single bit addresses ranging from 10001 to 14096.
Input registers are 16-bit addresses in the range 30001 to 39999.
Holding registers are 16-bit addresses in the range 40001 to 49999.
DF1 Addressing
DF1 addressing is used by the MSTR ladder logic function when the specified port is
configured for one of the DF1 protocols. Modbus addressing must be used in all other ladder
logic program functions.
DF1 addressing is used by function master_message when the specified port is configured
for one of the DF1 protocols. The functions dbase, setdbase, setABConfiguration and
getABConfiguration also support DF1 addressing.
All DF1 addresses are absolute word addresses beginning with the first 16-bit register in the
I/O database at address 0.
Converting Modbus to DF1 Addresses
I/O database registers are assigned within the controller’s Register Assignment using
Modbus addressing. When polling the controller from a DF1 device it is necessary to know
the DF1 address corresponding to each assigned register. Refer to the section for the
controller type being used.
SCADAPack, SCADAPack 100: 1024K and SCADASense 4202 Series
In general, the cross-reference between Modbus and DF1 addressing is shown in the
following table. DF1 addresses in this table are described in the format word/bit where
word is the address of a 16-bit word and bit is the bit within that word. The bit address is
optional.
Address Range
Modbus 00001 to 04096
DF1
0/0 to 255/15
Modbus 10001 to 14096
DF1
256/0 to 511/15
Modbus 30001 to 31024
DF1
512 to 1535
Modbus 40001 to 49999
DF1
1536 to 11534
Description
Digital Output Database
(single bit registers)
Digital Input Database
(single bit registers)
Analog Input Database
(16-bit registers)
Analog Output Database
(16-bit registers)
Coil Registers
To convert a Modbus coil register, ModbusCoil, to a DF1 address word/bit:
word
bit
= ( ModbusCoil - 00001 ) / 16
= remainder of { ( ModbusCoil - 00001 ) / 16 }
Status Registers
To convert a Modbus status register, ModbusStatus, to a DF1 address word/bit:
word
bit
= ( ModbusStatus - 10001 ) / 16 + 256
= remainder of { ( ModbusStatus - 10001 ) / 16 }
Input Registers
To convert a Modbus input register, ModbusInput, to a DF1 address word:
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
11
word
= ( ModbusInput - 30001 ) + 512
Holding Registers
To convert a Modbus holding register, ModbusHolding, to a DF1 address word:
word
= ( ModbusHolding - 40001 ) + 1536
Example
In this example the equivalent DF1 addresses are shown next to a sample SCADAPack
Register Assignment specified with Modbus addresses.
Start
Register
End
Register
00001
10001
30001
00012
10016
30008
0/0 to 0/11
256/0 to 256/15
512 to 519
DIN Controller digital inputs
10017
10019
257/0 to 257/2
DIAG Force LED
10020
10020
257/3
SCADAPack AOUT module
40001
40002
1536 to 1537
Module
SCADAPack
5601 I/O module
digital outputs
digital inputs
analog inputs
DF1 Address
Range
SCADAPack 350 and SCADAPack 32 Controllers
In general, the cross-reference between Modbus and DF1 addressing is shown in the
following table. DF1 addresses in this table are described in the format word/bit where
word is the address of a 16-bit word and bit is the bit within that word. The bit address is
optional.
Address Range
Modbus 00001 to 04096
DF1
0/0 to 255/15
Modbus 10001 to 14096
DF1
256/0 to 511/15
Modbus 30001 to 39999
DF1
512 to 10510
Modbus 40001 to 49999
DF1
10511 to 20511
Description
Digital Output Database
(single bit registers)
Digital Input Database
(single bit registers)
Analog Input Database
(16-bit registers)
Analog Output Database
(16-bit registers)
Coil Registers
To convert a Modbus coil register, ModbusCoil, to a DF1 address word/bit:
word
bit
= ( ModbusCoil - 00001 ) / 16
= remainder of { ( ModbusCoil - 00001 ) / 16 }
Status Registers
To convert a Modbus status register, ModbusStatus, to a DF1 address word/bit:
word
bit
= ( ModbusStatus - 10001 ) / 16 + 256
= remainder of { ( ModbusStatus - 10001 ) / 16 }
Input Registers
To convert a Modbus input register, ModbusInput, to a DF1 address word:
word
= ( ModbusInput - 30001 ) + 512
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
12
Holding Registers
To convert a Modbus holding register, ModbusHolding, to a DF1 address word:
word
= ( ModbusHolding - 40001 ) + 10511
Example
In this example the equivalent DF1 addresses are shown next to a sample SCADAPack
Register Assignment specified with Modbus addresses.
Start
Register
End
Register
00001
10001
30001
00012
10016
30008
0/0 to 0/11
256/0 to 256/15
512 to 519
DIN Controller digital inputs
10017
10019
257/0 to 257/2
DIAG Force LED
10020
10020
257/3
SCADAPack AOUT module
40001
40002
10511 to 10512
Module
SCADAPack
5601 I/O module
digital outputs
digital inputs
analog inputs
DF1 Address
Range
Accessing the I/O Database Using ISaGRAF
ISaGRAF programs access the I/O database through function blocks. The function blocks in
ISaGRAF may use the Modbus addressing scheme when a Network Address is defined for
a variable. Refer to the IEC 61131 User Manual for details.
C language programs access the I/O database with two functions. The dbase function reads
a value from the I/O database. The setdbase function writes a value to the I/O database.
These functions use either Modbus or DF1 physical addressing. Refer to the IEC 61131
User Manual for full details on these functions.
Modbus Addressing
Modbus addressing can be used in ISaGRAF program functions.
The C functions dbase and setdbase support Modbus addressing. When the specified port
is configured for one of the Modbus protocols, the function master_message uses Modbus
addressing.
Modbus addresses coil registers with a single bit address ranging from 00001 to 09999.
Status registers are also addressed with single bit addresses ranging from 10001 to 19999.
Input registers are addressed with 16-bit addresses in the range 30001 to 39999. And
holding registers are addressed with a 16-bit address in the range 40001 to 49999.
DF1 Addressing
DF1 addressing is used by the master function when the specified port is configured for one
of the DF1 protocols. Modbus addressing must be used in all other ladder logic program
functions.
DF1 addressing is used by function master_message when the specified port is configured
for one of the DF1 protocols. The functions dbase, setdbase, setABConfiguration and
getABConfiguration also support DF1 addressing.
All DF1 addresses are absolute word addresses beginning with the first 16-bit register in the
I/O database at address 0 and ending at address 21247.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
13
Converting Modbus to DF1 Addresses
I/O database registers are assigned within the controller’s Register Assignment using
Modbus addressing. When polling the controller from an DF1 device it is necessary to know
the DF1 address corresponding to each assigned register.
In general, the cross-reference between Modbus and DF1 addressing is shown in the
following table. DF1 addresses in this table are described in the format word/bit where
word is the address of a 16-bit word and bit is the bit within that word. The bit address is
optional.
Address Range
Modbus 00001 to 09999
DF1
0/0 to 624/15
Modbus 10001 to 19999
DF1
625/0 to 1249/15
Modbus 30001 to 39999
DF1
1250 to 11248
Modbus 40001 to 49999
DF1
11249 to 21247
Description
Digital Output Database
(single bit registers)
Digital Input Database
(single bit registers)
Analog Input Database
(16-bit registers)
Analog Output Database
(16-bit registers)
Coil Registers
To convert a Modbus coil register, ModbusCoil, to an DF1 address word/bit:
word
= ( ModbusCoil - 00001 ) / 16
bit
= remainder of { ( ModbusCoil - 00001 ) / 16 }
Status Registers
To convert a Modbus status register, ModbusStatus, to an DF1 address word/bit:
word
= ( ModbusStatus - 10001 ) / 16 + 625
bit
= remainder of { ( ModbusStatus - 10001 ) / 16 }
Input Registers
To convert a Modbus input register, ModbusInput, to an DF1 address word:
word
= ( ModbusInput - 30001 ) + 1250
Holding Registers
To convert a Modbus holding register, ModbusHolding, to an DF1 address word:
word
= ( ModbusHolding - 40001 ) + 11249
Example
In this example the equivalent DF1 addresses are shown next to a sample SCADAPack
Register Assignment specified with Modbus addresses.
Module
SCADAPack
5601 I/O module
digital outputs
digital inputs
analog inputs
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
Start
Register
00001
10001
30001
End
Register
00012
10016
30008
DF1 Address
Range
0/0 to 0/11
625/0 to 625/15
1250 to 1257
14
Start
Register
10017
End
Register
10019
DIAG Force LED
10020
10020
626/3
SCADAPack AOUT module
40001
40002
11249 to 111250
Module
DIN Controller digital inputs
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
DF1 Address
Range
626/0 to 626/2
15
Slave Mode
The TeleBUS DF1 protocols operate in slave and master modes simultaneously. In slave
mode the controller responds to commands sent by another device. Commands may be
sent to a specific device or broadcast to all devices.
The TeleBUS DF1 protocols emulate the protocol functions required for communication with
a host device which uses the Non-Privileged commands from the DF1 Basic Command Set.
These functions are described below.
Consult the DF1 I/O driver documentation included with the SCADA package, or specific
DF1 documentation, for details on these commands. In most cases a knowledge of the
actual commands is not required to set up the host system.
Broadcast Messages
A broadcast message is sent to all devices on a network. Each device executes the
command. No device responds to a broadcast command. The device sending the command
must query each device to determine if the command was received and processed.
Broadcast messages are supported for function codes that write information.
A broadcast message is sent to station number 255.
Function Codes
The table summarizes the implemented function codes. Note that slave commands at the
protocol layer access the I/O database in physical byte addresses. However, in master
mode the interface to the TeleBUS DF1 protocol accesses the I/O database in physical 16bit word addresses. The interface function block MSTR and C function master_message
are described in the Master Mode section below.
The maximum number of 16-bit words that can be read or written with one slave command
message is shown in the maximum column.
Function
00
01
02
05
08
Name
Description
Protected
Write
Unprotected
Read
Protected Bit
Write
Writes words of data to limited
areas of the database.
Reads words of data from any
area of the database.
Sets or resets individual bits
within limited areas of the
database.
Sets or resets individual bits in
any area of the database.
Writes words of data to any area
of the database.
Unprotected Bit
Write
Unprotected
Write
Maximum
121
122
30
30
121
Functions 0, 2, 5 and 8 support broadcast messages. The functions are described in detail
below.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
16
Protected Write
The Protected Write function writes 8 bit values into limited areas of the I/O database.
Access to the I/O database is limited to the protected address range.
Any number of bytes may be written up to the maximum number. The write may start at any
byte address, provided the entire block is within the protected address range.
The protected address range is set using the setABConfiguration function from a C
application program.
Unprotected Read
The Unprotected Read function reads 8 bit values from any area of the I/O database.
Access to the I/O database is limited to the unprotected address range.
Any number of bytes may be read up to the maximum number. The read may start at any
byte address, provided the entire block is within the unprotected address range.
Protected Bit Write
The Protected Bit Write function sets or resets individual bits within limited areas of the I/O
database. Access to the I/O database is limited to the protected address range.
Bits are accessed one byte at a time and may be written up to the maximum number of
bytes. The write may start at any byte address, provided the entire block is within the
protected address range.
Unprotected Bit Write
The Unprotected Bit Write function sets or resets individual bits in any area of the I/O
database. Access to the I/O database is limited to the unprotected address range.
Bits are accessed one byte at a time and may be written up to the maximum number of
bytes. The write may start at any byte address, provided the entire block is within the
unprotected address range.
Unprotected Write
The Unprotected Write function writes 8 bit values into any area of the I/O database. Access
to the I/O database is limited to the unprotected address range.
Any number of bytes may be written up to the maximum number. The write may start at any
byte address, provided the entire block is within the unprotected address range.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
17
Master Mode
The TeleBUS DF1 protocols may act as a communication master on any serial port. In
master mode, the controller sends commands to other devices on the network.
Simultaneous master messages may be active on all ports.
Function Codes
The table shows the implemented function codes. Note that slave commands at the protocol
layer access the I/O database in physical byte addresses. However, in master mode the
interface to the TeleBUS DF1 protocol accesses the I/O database in physical 16-bit word
registers. The interface function block MSTR and C function master_message are
described in the Sending Messages section below.
The maximum number of 16-bit registers that can be read or written with one message is
shown in the maximum column. The slave device may support fewer registers than shown;
consult the manual for the device for details.
Function
00
01
02
05
08
Name
Protected
Write
Unprotected
Read
Protected Bit
Write
Unprotected Bit
Write
Unprotected
Write
Description
Writes words of data to limited
areas of the database.
Reads words of data from any
area of the database.
Sets or resets individual bits
within limited areas of the
database.
Sets or resets individual bits in
any area of the database.
Writes words of data to any
area of the database.
Maximum
121
122
1
1
121
Protected Write
The Protected Write function writes 16-bit values into the I/O database of the slave device.
Access to the I/O database is limited to the protected address range of the slave device. The
data may come from any area of the master I/O database within its unprotected address
range.
Any number of 16-bit registers may be written up to the maximum number supported by the
slave device or the maximum number above, which ever is less. The write may start at any
16-bit register, provided the entire block is within the protected address range of the slave
device.
Unprotected Read
The Unprotected Read function reads 16-bit values from any area of the I/O database of the
slave device. Access to the I/O database is limited to the unprotected address range of the
slave device. Data can be written into any area of the master I/O database within its
unprotected address range.
Any number of 16-bit registers may be read up to the maximum number supported by the
slave device or the maximum number above, which ever is less. The read may start at any
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
18
16-bit register, provided the entire block is within the unprotected address range of the slave
device.
Protected Bit Write
The Protected Bit Write function sets or resets individual bits in the I/O database of the slave
device. Access to the I/O database is limited to the protected address range of the slave
device. The data may come from any area of the master I/O database within the unprotected
address range.
One 16-bit register with a bitmask is used to write up to 16 bits of data. The register must be
within the protected address range of the slave device.
Unprotected Bit Write
The Unprotected Bit Write function sets or resets individual bits in any area of the I/O
database of the slave device. Access to the I/O database is limited to the unprotected
address range of the slave device. The data may come from any area of the master I/O
database within its unprotected address range.
One 16-bit register with a bitmask is used to write up to 16 bits of data. The register must be
within the unprotected address range of the slave device.
Unprotected Write
The Unprotected Write function writes 16-bit values into any area of the I/O database of the
slave device. Access to the I/O database is limited to the unprotected address range of the
slave device. The data may come from any area of the master I/O database within its
unprotected address range.
Any number of 16-bit registers may be written up to the maximum number supported by the
slave device or the maximum number above, which ever is less. The write may start at any
16-bit register, provided the entire block is within the unprotected address range of the slave
device.
Sending Messages
A master message is initiated in two ways:
• using the master_message function from a C application program; or
• using the MSTR function block from a ladder logic program.
These functions specify the port on which to issue the command, the function code, the
slave station number, and the location and size of the data in the slave and master devices.
The protocol driver, independent of the application program, receives the response to the
command.
The application program detects the completion of the transaction by:
• calling the get_protocol_status function in a C application program; or
• using the output of the MSTR function block in a ladder logic program.
A communication error has occurred if the slave does not respond within the expected
maximum time for the complete command and response. The application program is
responsible for detecting this condition. When errors occur, it is recommended that the
application program retry several times before indicating a communication failure.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
19
The completion time depends on the length of the message, the length of the response, the
number of transmitted bits per character, the transmission baud rate, and the maximum
message turn-around time. One to three seconds is usually sufficient. Radio systems may
require longer delays.
Polling DF1 PLCs
All DF1 PLCs, except the PLC-5/VME, will support some portion of the basic commands
implemented.
AB PLC
MicroLogix
4
1000
SLC500
SLC5/01
SLC5/02
SLC5/03
1,3
1,3
1,2,3
2,3
2,3
SLC5/04
1774-PLC
PLC-2
PLC-3
PLC-5
5
5
5
PLC-5/250
PLC-5/VME
Unprotected
Read
Unprotected
Write
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
Protected
Write
√
√
√
√
Protected
Bit Write
√
√
√
√
√
Unprotected
Bit Write
√
√
√
√
√
Notes
1
At the protocol level these commands convert and send the slave word address as a byte
address. The SLC500, 5/01 (and 5/02, prior to Series C FRN 3) treat this byte address as if
it were a word address in the SLC500. This means that the (desired word address)/2 must
be specified for the Slave Register Address in MSTR or master_message. Note that this
always results in an even starting word address in the slave SLC. (E.g. Slave word address
of 7 specified in MSTR accesses SLC word address 14.)
2
The SLC5/02, 5/03 and 5/04 have a status selection bit (S:2/8) which allows selection of
either word or byte addressing when interpreting only these commands. (Setting SLC bit
S:2/8 = 1 selects byte addressing so that, for example, a slave word address of 7 specified
in MSTR accesses SLC word address 7.)
3
These commands can access SLC memory only in the CIF or Common Interface File: N9.
See further details in section 12-15 of the SLC500 Instruction Set manual.
4
These commands can access MicroLogix memory only in the CIF or Common Interface
File: N7. See further details in section 12-15 of the MicroLogix 1000 Instruction Set manual.
5
These commands can access memory only in the CIF or “PLC-2 compatibility file”: N7.
See further details in section 16-7 of the PLC-5 manual.
TeleBUS DF1 Protocol User and Reference Manual
May 9, 2007
20
DNP3
User and Reference Manual
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE,
TeleSAFE Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus,
SCADAPack 32, SCADAPack 32P, SCADAPack 350, SCADAPack LP,
SCADAPack 100, SCADASense 4202 DS, SCADASense 4202 DR,
SCADASense 4203 DS, SCADASense 4203 DR, SCADASense 4102,
SCADASense 4012, SCADASense 4032 and TeleBUS are registered
trademarks of Control Microsystems.
All other product names are copyright and registered trademarks or trade names
of their respective owners.
Material used in the User and Reference manual section titled SCADAServer
OLE Automation Reference is distributed under license from the OPC
Foundation.
DNP3 User and Reference Manual
May 9, 2007
1
Table of Contents
1
USING THIS MANUAL .................................................................................. 5
2
DNP3 OVERVIEW ......................................................................................... 6
2.1
2.1.1
2.1.1.1
2.1.2
2.1.3
2.1.4
2.1.5
DNP Architecture ...................................................................................... 6
Object Library ...................................................................................... 6
Internal Indication (IIN) Flags ......................................................... 7
Application Layer ................................................................................. 8
Pseudo-Transport Layer...................................................................... 9
Data Link Layer ................................................................................... 9
Physical Layer ..................................................................................... 9
2.2
Modbus Database Mapping ...................................................................... 9
3
DNP NETWORK ARCHITECTURES........................................................... 10
3.1
DNP Master and Outstation .................................................................... 10
3.2
DNP Master and Multidrop Outstations .................................................. 10
3.3
DNP Mimic Mode.................................................................................... 10
3.4
DNP Routing........................................................................................... 12
3.5
DNP Address Mapping ........................................................................... 12
4
CONFIGURATION OF DNP OPERATION MODES .................................... 14
4.1
4.1.1
DNP Outstation Configuration................................................................. 14
Configuration Steps ........................................................................... 14
4.2
4.2.1
DNP Master Configuration ...................................................................... 16
Configuration Steps ........................................................................... 16
4.3
4.3.1
DNP Data Router Configuration.............................................................. 18
Configuration Steps ........................................................................... 19
4.4
4.4.1
DNP Mimic Mode Configuration.............................................................. 20
Configuration Steps ........................................................................... 21
5
DNP CONFIGURATION MENU................................................................... 24
5.1
Application Layer Configuration .............................................................. 25
5.2
Data Link Layer Configuration ................................................................ 29
5.3
Master..................................................................................................... 32
5.4
Master Poll.............................................................................................. 33
DNP3 User and Reference Manual
May 9, 2007
2
5.4.1
5.4.2
Add/Edit Master Poll Dialog............................................................... 34
Poll Offset Example ........................................................................... 38
5.5
5.5.1
Address Mapping.................................................................................... 39
Add/Edit Address Mapping Dialog ..................................................... 40
5.6
5.6.1
5.6.2
Routing ................................................................................................... 41
Add/Edit DNP Route Dialog............................................................... 43
Dynamic Routing ............................................................................... 44
5.7
5.7.1
Binary Inputs Configuration..................................................................... 44
Adding Binary Inputs ......................................................................... 46
5.8
5.8.1
Binary Outputs Configuration.................................................................. 47
Adding Binary Outputs....................................................................... 48
5.9
5.9.1
16–Bit Analog Inputs Configuration ........................................................ 50
Adding 16-Bit Analog Inputs .............................................................. 51
5.10
5.10.1
32-Bit Analog Inputs Configuration ......................................................... 53
Adding 32-Bit Analog Inputs .............................................................. 54
5.11
5.11.1
Short Floating Point Analog Inputs ......................................................... 56
Adding Short Floating Point Analog Inputs ........................................ 58
5.12
5.12.1
16-Bit Analog Outputs Configuration ...................................................... 60
Adding 16-Bit Analog Outputs ........................................................... 61
5.13
5.13.1
32-Bit Analog Outputs Configuration ...................................................... 62
Adding 32-Bit Analog Outputs ........................................................... 63
5.14
5.14.1
Short Floating Point Analog Outputs....................................................... 65
Adding Short Floating Point Analog Outputs ..................................... 66
5.15
5.15.1
16–Bit Counter Inputs Configuration....................................................... 67
Adding 16-Bit Counter Inputs ............................................................ 69
5.16
5.16.1
32-Bit Counter Inputs Configuration........................................................ 71
Adding 32-Bit Counter Inputs ............................................................ 72
6
DNP DIAGNOSTICS.................................................................................... 75
6.1
6.1.1
6.1.2
DNP Status ............................................................................................. 75
Overview Tab .................................................................................... 76
Point Status Tabs .............................................................................. 77
6.2
6.2.1
6.2.2
6.2.3
DNP Master Status ................................................................................. 78
All Stations Tab ................................................................................. 79
Remote Overview Tab....................................................................... 80
Remote Point Status Tabs................................................................. 82
DNP3 User and Reference Manual
May 9, 2007
3
7
DNP DEVICE PROFILE DOCUMENT - MASTER....................................... 83
8
DNP DEVICE PROFILE DOCUMENT - SLAVE .......................................... 93
DNP3 User and Reference Manual
May 9, 2007
4
1
Using This Manual
The manual details implementation of the Distributed Network Protocol (DNP3) on SCADAPack
controllers. The manual describes the functionality of SCADAPack controllers under certain DNP
network topologies and fully details each DNP configuration parameter available on SCADAPack
controllers. Although we continuously add tidbits of relevant information, especially when
explaining each SCADAPack parameter in the overall scheme of the DNP3 concept, this manual
does not serve as a complete DNP3 Technical Reference guide.
The manual is arranges as follows:
Section 2- DNP3 Overview provides background information on DNP.
Section 3-DNP Network describes network configurations for using DNP in a SCADA system.
Section 4-Configuration of DNP Operation Modes describes the configuration guidelines for using
SCADAPack controllers in DNP networks.
Section 5-DNP Configuration is the complete reference for the DNP Configuration command when
selected in TelePACE, ISaGRAF, and RealFLO applications.
Section 6.1-DNP Status is the complete reference for the DNP Status command when selected in
TelePACE, ISaGRAF, and RealFLO applications. DNP Status provides run-time DNP diagnostics
and current data values for the local DNP points.
Section 6.2-DNP Master Status section is the complete reference for the DNP Master Status
command when selected in TelePACE, ISaGRAF, and RealFLO applications. DNP Status provides
run-time DNP diagnostics and status of the DNP outstations defined in the Master station and current
data values for the DNP points in these outstations.
Section 7-DNP Device Profile Document - Master contains the DNP device profile for SCADAPack
DNP master stations. All objects and function codes supported by the DNP master are listed in this
document.
Section 8-DNP Device Profile Document - Slave contains the DNP device profile for SCADAPack
DNP slave stations. All objects and function codes supported by the DNP slave are listed in this
document.
DNP3 User and Reference Manual
May 9, 2007
5
2
DNP3 Overview
DNP, the Distributed Network Protocol, is a standards-based communications protocol developed to
achieve interoperability among systems in the electric utility, oil & gas, water/waste water and
security industries. This robust, flexible non-proprietary protocol is based on existing open standards
to work within a variety of networks.
DNP offers flexibility and functionality that go far beyond conventional communications protocols.
Among its robust and flexible features DNP 3.0 includes:
•
Multiple data types (Data Objects) may be included in both request and response messages.
•
Multiple master stations are supported for outstations.
•
Unsolicited responses may be initiated from outstations to master stations.
•
Data types (Objects) may be assigned priorities (Class) and be requested based on the priority.
•
Addressing for over 65,000 devices on a single link.
•
Time synchronization and time-stamped events.
•
Broadcast messages
•
Data link and application layer confirmation
2.1
DNP Architecture
DNP is a layered protocol that is based on the Open System Connection (OSI) 7-layer protocol. DNP
supports the physical, data link and application layers only and terms this the Enhanced Performance
Architecture (EPA). In addition to these three layers an additional layer, the pseudo-transport layer,
is added to allow for larger application layer messages to be broken down into smaller frames for the
data link layer to transmit.
Object Library
The data objects (Binary Inputs, Binary Outputs, and Analog Inputs
etc.) that reside in the master or outstation.
Application Layer
Application tasks for sending of solicited requests (master
messages) to outstations or sending of unsolicited responses from
outstations. These request and response messages are referred to as
fragments in DNP.
Pseudo-Transport Layer
Breaks the application layer messages into smaller packets that can
be handled by the data link layer. These packets are referred to as
frames in DNP.
Data Link Layer
Handles the transmission and reception of data frames across the
physical layer.
Physical Layer
This is the physical media, such as serial or Ethernet, which DNP
communicates.
These layers are described in the following sections of this manual.
2.1.1
Object Library
The data types that are used in DNP are broadly grouped together into Object Groups such as Binary
Input Objects and Analog Input Objects etc. Individual data points, or objects within each group, are
further defined using Object Variations such as Binary Input Change with Time and 16-Bit Analog
Inputs for example.
DNP3 User and Reference Manual
May 9, 2007
6
The data objects and variations supported by the SCADAPack series controllers are found in the
DNP Device Profile Document - Slave and DNP Device Profile Document - Master sections of this
user manual.
In general there are two categories of data within each data type, static objects and event objects.
Static objects contain the current value of the field point or software point. Event objects are
generated as a result of the data changing.
In addition to the object group and variation data objects can be assigned to classes. In DNP there are
four object classes, Class 0, Class 1, Class 2 and Class 3. Class 0 contains all static data. Classes 1, 2
and 3 provide a method to assign priority to event objects. While there is no fixed rule for assigning
classes to data objects typically class 1 is assigned to the highest priority data and class 3 is assigned
to the lowest priority data.
This object library structure enables the efficient transfer of data between master stations and
outstations. The master station can poll for high priority data (class 1) more often than it polls for
low priority data (class 3). As the data objects assigned to classes is event data when the master polls
for a class only the changed, or event data, is returned by the outstation. For data in an outstation that
is not assigned a class the master uses a class 0 poll to retrieve all static data from the outstation.
DNP allows outstations to report data to one or more master stations using unsolicited responses
(report by exception) for event data objects. The outstation reports data based on the assigned class
of the data. For example the outstation can be configured to only report high priority class 1 data.
2.1.1.1
Internal Indication (IIN) Flags
An important data object is the Internal Indications (IIN) object. The Internal Indication (IIN) flags
are set by a slave station to indicate internal states and diagnostic results. The following tables show
the IIN flags supported by SCADAPack controllers. All bits except Device Restarted and Time
Synchronization required are cleared when the slave station receives any poll or read data command.
The IIN is set as a 16 bit word divided into two octets of 8 bits. The order of the two octets is:
First Octet
Second Octet
2.1.1.1.1
7
IIN First Octet
6
5
4
3
2
1
0
Bit Number
First
Octet
Bit
Description
0
1
2
3
4
5
6
last received message was a broadcast message
Class 1 data available
Class 2 data available
Class 3 data available
Time Synchronization required
not used (returns 0)
Device trouble
• Indicates memory allocation error in the slave, or
•
For master in mimic mode indicates communication failure with the
DNP3 User and Reference Manual
May 9, 2007
7
First
Octet
Bit
Description
slave device.
7
Device restarted (set on a power cycle)
2.1.1.1.2
7
IIN Second Octet
6
5
4
2
1
0
Bit Number
Second
Octet
Bit
Description
0
1
2
3
Function Code not implemented
Requested object unknown or there were errors in the application data
Parameters out of range
Event buffer overflowed
Indicates event buffer overflow in the slave or master. The slave will set
this bit if the event buffer in the slave is overflowed. The master will set
this bit if the event buffer in the master has overflowed with events read
from the slave. Ensure the event buffer size, in the master and slave, is
set to a value that will ensure the buffer does not overflow and events are
lost.
not used (returns 0)
not used (returns 0)
not used (returns 0)
not used (returns 0)
4
5
6
7
2.1.2
3
Application Layer
The application layer in DNP is responsible for the processing of complete messages for requesting,
or responding to requests, for data.
The following shows the sequence of Application Layer messages between one master and one
outstation.
Master
Outstation
Send Request
-------------------->
<--------------------
Accept request and process
Optional Application
Confirmation
Accept response
Optional Application
Confirmation
<--------------------
Send Response
-------------------->
Important change detected
Accept response
Optional Application
Confirmation
DNP3 User and Reference Manual
May 9, 2007
<---------------------
Send Unsolicited Response
-------------------->
8
The complete messages are received from and passed to the pseudo-transport layer. Application layer
messages are broken into fragments with each fragment size usually a maximum of 2048 bytes. An
application layer message may be one or more fragments in size and it is the responsibility of the
application layer to ensure the fragments are properly sequenced.
Application layer fragments are sent with or without a confirmation request. When a confirmation is
requested the receiving device replies with a confirmation indicating the message was received and
parsed without any errors.
2.1.3
Pseudo-Transport Layer
The pseudo-transport layer formats the larger application layer messages into smaller packets that
can be handled by the data link layer. These packets are referred to as frames in DNP. The pseudotransport layer inserts a single byte of information in the message header of each frame. This byte
contains information such as whether the frame is the first or last frame of a message as well as a
sequence number for the frame.
2.1.4
Data Link Layer
The data link layer handles the transmission and reception of data frames across the physical layer.
Each data link frame contains a source and destination address to ensure the receiving device knows
where to send the response. To ensure data integrity data link layer frames contain two CRC bytes
every 16 bytes.
Data link layer frames are sent with or without a confirmation request. When a confirmation is
requested the receiving device replies with a confirmation indicating the message was received and
the CRC checks passed.
2.1.5
Physical Layer
The physical layer handles the physical media, such as serial or Ethernet, which DNP communicates.
2.2
Modbus Database Mapping
In SCADAPack series controllers static DNP objects such as binary input, analog input, binary
counter and analog output are associated with Modbus registers. Whenever a DNP object is created
an associated Modbus register(s) is also assigned. Application programs executing in the
SCADAPack controller, C or logic, are able to assign physical I/O to Modbus registers using the
TelePACE Register Assignment or the ISaGRAF I/O Connection and these physical I/O points can
then be assigned to DNP objects. User application data such as runtimes, flow totals etc. may be also
be assigned to DNP objects.
This architecture enables DNP master stations and outstations to pass not only physical data points
between them but also to monitor and control user applications executing in the SCADAPack
controller. For example a master station can monitor a level in an outstation and then, based on the
application program, send a setpoint value to another outstation to control the level.
DNP3 User and Reference Manual
May 9, 2007
9
3
DNP Network Architectures
This section of the manual describes some of the DNP networks in which SCADAPack controllers
are used. The network descriptions provide an overview of network. A step-by-step procedure for
configuring a SCADAPack for each network implementation is described in proceeding sections.
3.1
DNP Master and Outstation
This configuration is a simple DNP Master (Client) and Outstation (Server). The SCADAPack DNP
Master may be configured to periodically poll the SCADAPack Outstation for Class 0, 1, 2, and 3
data objects and receive unsolicited responses from the outstation. The SCADAPack outstation may
be configured to report change event data to the master station using unsolicited responses.
The arrowed line between the Master and Outstation in the diagram below represents a
communication path connecting the two stations. This communication medium may be any type that
is supported by both controllers, such as direct serial, leased line modem, dial-up modem and radio
for example.
See the sections DNP Master and DNP Outstation for configuration details on this type of network.
SCADAPack 32
Master
Note:
3.2
SCADAPack
Outstation A
A DNP Master can be configured on SCADAPack 350 and SCADAPack32 controllers only.
DNP Master and Multidrop Outstations
This configuration is a modification of the above example. In this configuration a DNP Master is
connected to a number of Outstations. The SCADAPack DNP Master may be configured to
periodically poll each SCADAPack Outstation for Class 0, 1,2, and 3 data objects and receive
unsolicited responses from the outstations. The SCADAPack Outstations may be configured to
report change event data to the master station using unsolicited responses.
The arrowed line between the Master and Outstations in the diagram below represents the
communication path connecting the stations. This communication path may be any type that is
supported by the controllers, such as leased line modem, dial-up modem and radio for example.
See the sections 4.2- DNP Master and 4.1-DNP Outstation for configuration details.
SCADAPack 32
Master
Note:
3.3
SCADAPack
Outstation A
SCADAPack
Outstation B
SCADAPack
Outstation C
A DNP Master can be configured on SCADAPack 350 and SCADAPack32 controllers
only.
DNP Mimic Mode
DNP3 User and Reference Manual
May 9, 2007
10
In a typical DNP network a SCADA Host master communicates with a number of outstations. The
SCADA Host will poll each outstation for data and may receive change event data in the form of
unsolicited responses from the outstations. This type of DNP network is shown in the following
diagram.
SCADA Host
Master
SCADAPack
Outstation A
SCADAPack
Outstation B
In the above configuration the SCADA Host manages the communication path with each outstation
as represented by the arrowed lines in the diagram. When the communication path is slow, such as
with dial-up communication, or subject to high error rates, such as with some radio communication
the data update rate at the SCADA host can become very slow.
Adding a SCADAPack 32 master configured for Mimic Mode to the network, for instance, allows
for the SCADA Host Master to poll the SCADAPack 32 (Mimic Master) for all outstation data
instead. The following diagram shows the addition of the SCADAPack 32 master.
SCADAPack 32
Mimic
SCADA Host
Master
Slave
Master
SCADAPack
Outstation A
SCADAPack
Outstation B
In this configuration the outstation side of the network has been decoupled from the host side of the
network, as the SCADAPack 32 mimic master now manages all the communication with the
outstations. The SCADA Host still communicates as before, through one link, targeting each
outstation. However the SCADAPack 32 master now intercepts all these messages, and responds on
behalf of the targeted outstation. From the perspective of the SCADA Host, the response is coming
back from the remote outstation.
In order to provide current outstation data to the SCADA Host, the SCADAPack mimicking master
independently communicates with each outstation to update a local copy of its database with data
from the outstations. This communication may be initiated by the SCADAPack mimicking master,
either by polling each outstation in turn using solicited messages; or the outstations could initiate
unsolicited messages back to the mimicking master. There could also be a combination of solicited
and unsolicited messages between the mimicking master and the outstations.
In the Mimic mode diagram above the SCADAPack mimic master polls each outstation, A and B, for
data and holds images of this data in its memory. When the SCADA Host poll outstations A and B
for data, the mimic master replies from its own images of the outstations. The SCADA Host can also
poll the SCADAPack master for its own local data. See Section 4.4-DNP Mimic Mode
Configuration for configuration details on the Mimic Mode.
Typically the messaging strategy chosen will depend on the relative importance of the data, and the
required maximum end-to-end delays for data being transferred through the network. If the
requirement is for a reasonably short end-to-end delay for all data points, a round-robin polling
scheme is best, without any unsolicited messages. If there are some data points, which are higher
priority and must be transferred as fast as possible, unsolicited messages should be used.
DNP3 User and Reference Manual
May 9, 2007
11
The advantage of having the SCADA system communicating with the SCADAPack 32 mimic,
instead of direct communication to the outstations is that communication delays and high error rates
are effectively removed. The physical connection between the SCADA system and mimic master
SCADAPack is typically a direct high-speed reliable connection and all message transactions are
fast. Outstations may often be connected via slow PSTN or radio links, and therefore message
transactions are subject to substantial delays. They may also be unreliable communication links
subject to high error rates.
By having a multiple-level network the communication between the SCADAPack master and
outstations is separated from communication between SCADA system and the SCADAPack master.
The delays and error rates, which may be inherent in the outstation communication paths, can be
isolated from communications with the SCADA system, thereby increasing overall system
performance.
One particular advantage of Mimic Mode is that the master SCADAPack does not need to
know, or be configured with, any details of the DNP points configured in the outstations. This
makes it relatively simple to insert such a SCADAPack master into any existing DNP network. The
SCADAPack master in Mimic Mode behaves transparently to the higher-level SCADA system, and
can easily be configured with communication paths and polling instructions for each connected
outstation.
3.4
DNP Routing
DNP Routing is similar to DNP Mimic mode in that the SCADA Host has only one connection to a
SCADAPack configured for DNP routing. The following diagram shows a simple DNP routing
system.
SCADAPack
DNP Router
SCADA Host
Master
Outstation A
SCADAPack
Outstation B
SCADAPack
Outstation C
In this configuration the SCADAPack DNP router (Outstation A above) manages all the
communication with the outstations. The SCADAPack DNP router receives messages from the
SCADA Host for each outstation and routes the messages to the outstations. Change event data in
the form of unsolicited responses from the outstations are routed by the SCADAPack DNP router, to
the SCADA Host in the same manner.
As with Mimic mode, the advantage of using DNP Routing is that the responsibility of managing
multiple communications paths is removed from the SCADA Host. The SCADAPack DNP router
handles all communications paths to outstations, including such tasks as dial-up radio
communication. In contrast to Mimic mode, however, the SCADA Host system still has to handle
the long delays and high error rates that may be present on the communications links to the
outstations.
See the section DNP Data Router for configuration details for using DNP Routing in a SCADA
system.
3.5
DNP Address Mapping
DNP3 User and Reference Manual
May 9, 2007
12
Setting up a SCADAPack controller as a DNP Mimic Master or even a DNP router is relatively
straight forward, as one does not need to explicitly map data from the remote devices into the local
DNP database of the SCADAPack master.
In certain cases, however, data from the remote DNP devices may need to be accessible to an
application program running in the master SCADAPack controller. DNP Address Mapping allows
this capability, by providing a method to map outstation DNP points into local Modbus registers in
the SCADAPack master controller.
By configuring the Address Mapping table these remote DNP points are mapped to local Modbus
registers in the SCADAPack master. As mapped Modbus points the data is available for use in
application programs such as TelePACE and ISaGRAF. In addition a Modbus SCADA Host polling
the SCADAPack master may access these points. See the Section 5.5- Address Mapping for
information on configuring DNP Address Mapping.
The following diagram shows a simple DNP Address Mapping network.
SCADA Host
Modbus Master
SCADAPack 32
Modbus DNP3
Slave
Master
SCADAPack
Outstation A
SCADAPack
Outstation B
In this network the SCADAPack master updates is local database with mapped outstation data. The
manner and frequency with which the SCADAPack master updates the local Modbus registers,
depends on the number and type of I/O object types the registers are mapped to.
For 'Input' object types, address mapping simply links the remote DNP points to local Modbus Input
registers (1xxxx or 3xxxx). These local Modbus registers are updated after the corresponding DNP
point gets updated (usually by a class 0 poll to the remote DNP device).
For ‘Output' object types, there is a similar relationship between the local Modbus registers (0xxxx
or 4xxxx) and the remote DNP point, with one significant difference in the way local changes are
propagated to the remote DNP device. Changes made to the local Modbus register will affect the
value of the associated DNP point, subsequently triggering a DNP Write message to the remote DNP
outstation.
It is, therefore, necessary to ensure that all local Modbus addresses mapped to a remote device via
Address Mapping, are associated with a local DNP address.
Note:
Mapping numerous local Modbus output registers (0xxxx and 4xxxx), to a remote DNP
device may cause frequent communications between the master and the slave, if the
associated registers are being changed frequently in the master. On limited bandwidth or
radio networks, care must be taken to ensure that your network capacity can handle all the
traffic that will be generated from these local changes.
DNP3 User and Reference Manual
May 9, 2007
13
4
Configuration of DNP Operation Modes
SCADAPack controllers support a number of DNP operating modes. In this section of the user
manual the operating modes supported and the steps required to configure the operating modes is
explained.
The DNP operating modes described in this section include:
•
DNP Outstation
•
DNP Master
•
DNP Data Router
•
DNP Mimic Mode
4.1
DNP Outstation Configuration
A DNP outstation is the basic configuration for a SCADAPack controller operating in a DNP
network. When configured as a DNP outstation a SCADAPack controller is able to:
•
Map physical I/O data to DNP points.
•
Define DNP points as Class 1, Class 2 or Class 3 data types.
•
Respond to requests from one or more master stations such as a SCADA hosts or SCADAPack
32 controllers that are configured for DNP master operation.
•
Initiate unsolicited responses to one or more master stations.
See the section DNP Network for examples of where an outstation may be used in typical DNP
networks.
The following describes the general steps required to configure a SCADAPack series controller as a
DNP outstation.
4.1.1
Configuration Steps
The steps below provide an outline of the configuration needed for an outstation. References are
made to sections of this manual and to other user manuals. These sections and manual should be
referred to for complete information.
1. Enable DNP for the serial or Ethernet port.
The SCADAPack controller is connected to a DNP network through one of the serial ports or in the
case of a SCADAPack 32 controller through a serial port or Ethernet port. The serial or Ethernet
ports need to be set to use DNP protocol and to enable DNP Routing.
•
For TelePACE applications see the section Controller Menu >> Serial Ports and Controller
Menu >> IP Configuration in the TelePACE User and Reference Manual.
•
For ISaGRAF Applications see the section Controller Menu Commands >> Controller Serial
Port Command and Controller Menu Commands >> Controller IP in the ISaGRAF User and
Reference Manual.
2. Configure Register Assignment or I/O Connections.
The physical I/O for a SCADAPack controller is made available to application programs and
protocols by assigning the physical I/O to Modbus registers in TelePACE and to Dictionary
Variables (with Modbus network addresses) in ISaGRAF. SCADAPack controllers use the Modbus
addresses when DNP objects are created.
DNP3 User and Reference Manual
May 9, 2007
14
•
For TelePACE applications see the section Controller Menu >> Register Assignment in the
TelePACE User and Reference Manual.
•
For ISaGRAF Applications see the section I/O Connection Reference in the ISaGRAF User and
Reference Manual.
3. Configure Application Layer Parameters.
The application layer parameters primarily define how the application layer communicates; how
often time synchronization is done, whether the station initiates unsolicited responses and if
application layer confirmation is used in the communication. In addition the global Operate Timeout
parameter is set for Select Before Operate binary output objects and the Dial Up parameters are set if
dial up communication is used.
•
See the section DNP Configuration >> Application Layer Configuration in this manual for
information on the parameters used in the Application layer.
4. Configure Data Link Layer Parameters.
The data link layer parameters define the outstation DNP address, the master station address(s) the
outstation will communicate with and whether data link layer confirmation will be used in the
communication.
•
See the section DNP Configuration >> Data Link Layer Configuration in this manual for
information on the parameters used in the Data Link Layer.
5. Configure DNP Routing.
SCADAPack controllers use DNP routing to direct DNP messages based on instructions in the
routing table. The routing table defines which serial port or Ethernet port messages will be sent to
other DNP stations. In the case of an outstation DNP routing defines the station address of the master
station and the communication port to be used when communicating with the master station.
•
See the section DNP Configuration >> Routing in this manual for information on the routing
table and adding entries to the routing table.
6. Configure Data Objects.
The SCADAPack controller physical I/O and user application data may be assigned to DNP objects
and given DNP point addresses. DNP input points can be assigned a class (1,2 or 3) for event data.
These change events can be sent to the master station(s) if unsolicited responses are enable for the
assigned class.
The DNP objects that are supported in the SCADAPack controller are shown below. See the
appropriate section in the DNP Configuration section of this manual for complete information on
configuring DNP data objects.
•
Binary Inputs
•
Binary Outputs
•
16-bit Analog Inputs
•
32-bit Analog Inputs
•
Short Floating Point Analog Inputs
•
16-bit Analog Outputs
•
32-bit Analog Outputs
DNP3 User and Reference Manual
May 9, 2007
15
•
Short Floating Point Analog Outputs
•
16-bit Counter Inputs
•
32-bit Counter Inputs
4.2
DNP Master Configuration
This option is available on the SCADAPack 350 and SCADAPack 32 controllers only.
The SCADAPack 350 and SCADAPack 32 controllers can be configured as a DNP master station in
a DNP network. When configured as a DNP master station the controller is able to:
•
Map local physical I/O data to DNP points.
•
Define local DNP points as Class 1, Class 2 or Class 3 data types.
•
Respond to requests from one or more master stations such as a SCADA hosts or other
controllers that are configured for DNP master operation.
•
Initiate unsolicited responses to one or more master stations.
•
Poll DNP outstations for static (Class 0) data and Class 1, 2 and 3 event data.
•
Accept unsolicited response messages from polled outstations.
•
Map Outstation DNP data to local DNP points and Modbus registers. This data can then be used
in application programs executing in the local controller or made available to other DNP master
station(s) that poll this local controller.
See Section 3-DNP Network Architectures for examples of where a DNP master may be used in
typical DNP networks.
The following describes the general steps required to configure a SCADAPack controller as a DNP
master station.
Note:
4.2.1
Only the SCADAPack 350 or SCADAPack32 controller can be configured as a DNP master.
Configuration Steps
The steps below provide an outline of the configuration needed for a SCADAPack master station.
References are made to sections of this manual and to other user manuals. These sections and manual
should be referred to for complete information.
1. Enable DNP for the serial or Ethernet port.
The SCADAPack controller is connected to a DNP network through one of the serial ports or the
Ethernet port. The serial or Ethernet ports need to be set to use DNP protocol and to enable DNP
Routing.
•
For TelePACE applications see the section Controller Menu >> Serial Ports and Controller
Menu >> IP Configuration in the TelePACE User and Reference Manual.
•
For ISaGRAF Applications see the section Controller Menu Commands >> Controller Serial
Port Command and Controller Menu Commands >> Controller IP in the ISaGRAF User and
Reference Manual.
2. Configure Register Assignment or I/O Connections.
The physical I/O for a SCADAPack controller is made available to application programs and
protocols by assigning the physical I/O to Modbus registers in TelePACE and to Dictionary
DNP3 User and Reference Manual
May 9, 2007
16
Variables (with Modbus network addresses) in ISaGRAF. SCADAPack controllers use the Modbus
addresses when DNP objects are created.
•
For TelePACE applications see the section Controller Menu >> Register Assignment in the
TelePACE User and Reference Manual.
•
For ISaGRAF Applications see the section I/O Connection Reference in the ISaGRAF User and
Reference Manual.
3. Configure Application Layer Parameters.
The application layer parameters primarily define how the application layer communicates; how
often time synchronization is done, whether the station initiates unsolicited responses and if
application layer confirmation is used in the communication. In addition the global Operate Timeout
parameter is set for Select Before Operate binary output objects and the Dial Up parameters are set if
dial up communication is used.
•
See the section DNP Configuration >> Application Layer Configuration in this manual for
information on the parameters used in the Application layer.
4. Configure Data Link Layer Parameters.
The data link layer parameters define the SCADAPack outstation DNP address, the master station
address(s) the SCADAPack master will communicate with and whether data link layer confirmation
will be used in the communication.
•
See the section DNP Configuration >> Data Link Layer Configuration in this manual for
information on the parameters used in the Data Link Layer.
5. Configure Master Parameters ( Applicable for SCADAPack 350 and SCADAPack 32 only)
There are two Master parameters, Mimic Mode enable or disable and the Base Poll Interval. The
concept behind Mimic Mode operation is described in section 3.3-DNP Mimic Mode.
The Base Poll interval is used to determine the frequency of master polling of outstations. Each type
of master poll, Class 0, 1, 2 or 3 is polled at a frequency that is based on the Base Poll Interval.
•
See the section DNP Configuration >> Master in this manual for information on the parameters
used in the Master.
6. Configure Master Poll Parameters
The Master Poll parameters define how often the master station polls each outstation, how often to
request time synchronization and whether unsolicited responses are accepted from the outstation.
The polling frequency is configured independently for outstation Class 0,1,2 and 3 data. Master
polling interval, or frequency, is based on the number of base poll intervals as set in the Master
parameters.
•
See the section DNP Configuration >> Master Poll in this manual for information on the
parameters used in for the Master Poll.
7. Configure Address Mapping Parameters
The Address Mapping parameters define the mapping rules, which allow outstation DNP objects to
be mapped into local SCADAPack master Modbus registers. This allows the outstation data to be
used locally in application programs.
•
See the section DNP Configuration >> Address Mapping in this manual for information on the
parameters used in for Address Mapping.
DNP3 User and Reference Manual
May 9, 2007
17
8. Configure DNP Routing.
SCADAPack controllers use DNP routing to direct DNP messages based on instructions in the
routing table. The routing table defines which serial port or Ethernet port messages will be sent to
other DNP outstations or master stations. The DNP routing table defines the station address of the
master station and the communication port to be used when communicating with the master station
and the station addresses of the outstations the SCADAPack master station is polling.
9. See the section DNP Configuration >> Routing in this manual for information on the routing
table and adding entries to the routing table.
10. Configure Data Objects.
The SCADAPack controller physical I/O and user application data may be assigned to DNP objects
and given DNP point addresses. DNP input points can be assigned a class (1,2 or 3) for event data.
These change events can be sent to the master station(s) if unsolicited responses are enable for the
assigned class.
The DNP objects that are supported in the SCADAPack controllers are shown below. See the
appropriate section in the DNP Configuration section of this manual for complete information on
configuring DNP data objects.
•
Binary Inputs
•
Binary Outputs
•
16-bit Analog Inputs
•
32-bit Analog Inputs
•
Short Floating Point Analog Inputs
•
16-bit Analog Outputs
•
32-bit Analog Outputs
•
Short Floating Point Analog Outputs
•
16-bit Counter Inputs
•
32-bit Counter Inputs
4.3
DNP Data Router Configuration
All SCADAPack controllers can be configured as a DNP Router. When configured as a DNP router
a SCADAPack controller is able to:
•
Map local physical I/O data to DNP points.
•
Define local DNP points as Class 1, Class 2 or Class 3 data types.
•
Respond to requests from one or more master stations such as a SCADA hosts or other
SCADAPack 32 controllers that are configured for DNP master operation.
•
Initiate unsolicited responses to one or more master stations.
•
Route DNP messages as defined in the Routing table.
See the Section 3-3-Modbus Database Mapping for examples of where a DNP Data Router may be
used in typical DNP networks.
The following describes the general steps required to configure a SCADAPack series controller as a
DNP Data Router.
DNP3 User and Reference Manual
May 9, 2007
18
4.3.1
Configuration Steps
The steps below provide an outline of the configuration needed for a SCADAPack DNP router.
References are made to sections of this manual and to other user manuals. These sections and manual
should be referred to for complete information.
1. Enable DNP for the serial or Ethernet port.
The SCADAPack controller 32 is connected to a DNP network through one of the serial ports or the
Ethernet port. The serial or Ethernet ports need to be set to use DNP protocol and to enable DNP
Routing.
•
For TelePACE applications see the section Controller Menu >> Serial Ports and Controller
Menu >> IP Configuration in the TelePACE User and Reference Manual.
•
For ISaGRAF Applications see the section Controller Menu Commands >> Controller Serial
Port Command and Controller Menu Commands >> Controller IP in the ISaGRAF User and
Reference Manual.
2. Configure Register Assignment or I/O Connections.
The physical I/O for a SCADAPack 32 controller is made available to application programs and
protocols by assigning the physical I/O to Modbus registers in TelePACE and to Dictionary
Variables (with Modbus network addresses) in ISaGRAF. SCADAPack controllers use the Modbus
addresses when DNP objects are created.
•
For TelePACE applications see the section Controller Menu >> Register Assignment in the
TelePACE User and Reference Manual.
•
For ISaGRAF Applications see the section I/O Connection Reference in the ISaGRAF User and
Reference Manual.
3. Configure Application Layer Parameters.
The application layer parameters primarily define how the application layer communicates; how
often time synchronization is done, whether the station initiates unsolicited responses and if
application layer confirmation is used in the communication. In addition the global Operate Timeout
parameter is set for Select Before Operate binary output objects and the Dial Up parameters are set if
dial up communication is used.
•
See the section DNP Configuration >> Application Layer Configuration in this manual for
information on the parameters used in the Application layer.
4. Configure Data Link Layer Parameters.
The data link layer parameters define the SCADAPack 32 outstation DNP address, the master station
address(s) the SCADAPack 32 master will communicate with and whether data link layer
confirmation will be used in the communication.
•
See the section DNP Configuration >> Data Link Layer Configuration in this manual for
information on the parameters used in the Data Link Layer.
5. Configure DNP Routing.
SCADAPack series controllers use DNP routing to direct DNP messages based on instructions in the
routing table. The routing table defines which serial port or Ethernet port messages will be sent to
other DNP outstations or master stations. The DNP routing table defines the station address of each
outstation and the communication port to be used when communicating with outstations.
DNP3 User and Reference Manual
May 9, 2007
19
•
See the section DNP Configuration >> Routing in this manual for information on the routing
table and adding entries to the routing table.
6. Configure Data Objects.
The SCADAPack controller physical I/O and user application data may be assigned to DNP objects
and given DNP point addresses. DNP input points can be assigned a class (1,2 or 3) for event data.
These change events can be sent to the master station(s) if unsolicited responses are enable for the
assigned class.
The DNP objects that are supported in the SCADAPack controller are shown below. See the
appropriate section in the DNP Configuration section of this manual for complete information on
configuring DNP data objects.
•
Binary Inputs
•
Binary Outputs
•
16-bit Analog Inputs
•
32-bit Analog Inputs
•
Short Floating Point Analog Inputs
•
16-bit Analog Outputs
•
32-bit Analog Outputs
•
Short Floating Point Analog Outputs
•
16-bit Counter Inputs
•
32-bit Counter Inputs
4.4
DNP Mimic Mode Configuration
This option is applicable to the SCADAPack 350 and SCADPack32 controllers only.
The SCADAPack 350 and SCADAPack 32 controller can be configured as a DNP master station, in
mimic mode, in a DNP network. When configured as a Mimic Mode DNP master station a
SCADAPack 32 controller is able to:
•
Map local physical I/O data to DNP points.
•
Define local DNP points as Class 1, Class 2 or Class 3 data types.
•
Respond to requests from one or more master stations such as a SCADA hosts or other
SCADAPack controllers that are configured for DNP master operation.
•
Initiate unsolicited responses to one or more master stations.
•
Poll DNP outstations for static (Class 0) data and Class 1, 2 and 3 event data.
•
Accept unsolicited response messages from polled outstations.
•
Respond directly to SCADA Host polls that are destined for outstations that are defined in its
Master Poll table.
See Section 3-DNP Network Architectures for examples of where a DNP master may be used in
typical DNP networks.
The following describes the general steps required to configure a SCADAPack controller as a Mimic
Mode DNP master station.
DNP3 User and Reference Manual
May 9, 2007
20
4.4.1
Configuration Steps
The steps below provide an outline of the configuration needed for a SCADAPack DNP Mimic
Mode master station. References are made to sections of this manual and to other user manuals.
These sections and manual should be referred to for complete information.
1. Enable DNP for the serial or Ethernet port.
The SCADAPack controller is connected to a DNP network through one of the serial ports or the
Ethernet port.
•
For TelePACE applications see the section Controller Menu >> Serial Ports and Controller
Menu >> IP Configuration in the TelePACE User and Reference Manual.
•
Enable Routing on the serial or Ethernet ports that have been configured for DNP
communication.
•
For ISaGRAF Applications see the section Controller Menu Commands >> Controller Serial
Port Command and Controller Menu Commands >> Controller IP in the ISaGRAF User and
Reference Manual.
2. Configure Register Assignment or I/O Connections.
The physical I/O for a SCADAPack controller is made available to application programs and
protocols by assigning the physical I/O to Modbus registers in TelePACE and to Dictionary
Variables (with Modbus network addresses) in ISaGRAF. SCADAPack controllers use the Modbus
addresses when DNP objects are created.
•
For TelePACE applications see the section Controller Menu >> Register Assignment in the
TelePACE User and Reference Manual.
•
For ISaGRAF Applications see the section I/O Connection Reference in the ISaGRAF User and
Reference Manual.
3. Configure Application Layer Parameters.
The application layer parameters primarily define how the application layer communicates; how
often time synchronization is done, whether the station initiates unsolicited responses and if
application layer confirmation is used in the communication. In addition the global Operate Timeout
parameter is set for Select Before Operate binary output objects and the Dial Up parameters are set if
dial up communication is used.
•
See the section DNP Configuration >> Application Layer Configuration in this manual for
information on the parameters used in the Application layer.
4. Configure Data Link Layer Parameters.
The data link layer parameters define the SCADAPack outstation DNP address, the master station
address(s) the SCADAPack Mimic master will communicate with and whether data link layer
confirmation will be used in the communication.
•
See the section DNP Configuration >> Data Link Layer Configuration in this manual for
information on the parameters used in the Data Link Layer.
5. Configure Master Parameters
There are two Master parameters, Mimic Mode enable or disable and the Base Poll Interval. The
Mimic Mode must be set to enable for Mimic Mode. Mimic Mode operation is described in Section
4.4-DNP Mimic Mode.
DNP3 User and Reference Manual
May 9, 2007
21
he Base Poll interval is used to determine the frequency of master polling of outstations. Each type
of master poll, Class 0, 1, 2 or 3 is polled at a frequency that is based on the Base Poll Interval.
•
See the section DNP Configuration >> Master in this manual for information on the parameters
used in the Master.
6. Configure Master Poll Parameters
The Master Poll parameters define how often the master station polls each outstation, how often to
request time synchronization and whether unsolicited responses are accepted from the outstation.
The polling frequency is configured independently for outstation Class 0,1,2 and 3 data. Master
polling interval, or frequency, is based on the number of base poll intervals as set in the Master
parameters.
•
See the section DNP Configuration >> Master Poll in this manual for information on the
parameters used in for the Master Poll.
7. Configure Address Mapping Parameters
The Address Mapping parameters define the mapping rules, which allow outstation DNP objects to
be mapped into local SCADAPack master Modbus registers and DNP points. This allows the
outstation data to be used locally in application programs.
•
See the section DNP Configuration >> Address Mapping in this manual for information on the
parameters used in for Address Mapping.
8. Configure DNP Routing.
SCADAPack controllers use DNP routing to direct DNP messages based on instructions in the
routing table. The routing table defines which serial port or Ethernet port messages will be sent to
other DNP outstations or master stations. The DNP routing table defines the station address of the
master station and the communication port to be used when communicating with the master station
and the station addresses of the outstations the SCADAPack master station is polling.
•
See the section DNP Configuration >> Routing in this manual for information on the routing
table and adding entries to the routing table.
9. Configure Data Objects.
The SCADAPack controller physical I/O and user application data may be assigned to DNP objects
and given DNP point addresses. DNP input points can be assigned a class (1,2 or 3) for event data.
These change events can be sent to the master station(s) if unsolicited responses are enable for the
assigned class.
The DNP objects that are supported in the SCADAPack controller are shown below. See the
appropriate section in the DNP Configuration section of this manual for complete information on
configuring DNP data objects.
•
Binary Inputs
•
Binary Outputs
•
16-bit Analog Inputs
•
32-bit Analog Inputs
•
Short Floating Point Analog Inputs
•
16-bit Analog Outputs
•
32-bit Analog Outputs
DNP3 User and Reference Manual
May 9, 2007
22
•
Short Floating Point Analog Outputs
•
16-bit Counter Inputs
•
32-bit Counter Inputs
DNP3 User and Reference Manual
May 9, 2007
23
5
DNP Configuration Menu
The DNP command is used to configure the DNP protocol settings for the controller. When selected
the DNP Settings window is opened, as shown below.
The DNP Settings window has a tree control on the left side of the window. The tree control appears
differently depending on the controller type selected. The SCADAPack 350, SCADAPack 32 and
SCADAPack 32P controllers support DNP master and include the bolded items in the following list.
Other SCADAPack controllers do not support DNP master and do not include the bolded items.
This tree control contains headings for:
•
Application Layer
•
Data Link Layer
•
Master
•
Master Poll
•
Address Mapping
•
Routing
•
Binary Inputs
•
Binary Outputs
•
16-Bit Analog Inputs
•
32-Bit Analog Inputs
DNP3 User and Reference Manual
May 9, 2007
24
•
Short Floating Point Analog Inputs
•
16-Bit Analog Outputs
•
32-Bit Analog Outputs
•
Short Floating Point Analog Outputs
•
16-Bit Counter Inputs
•
32-Bit Counter Inputs
When a tree control is selected by clicking the mouse on a heading a property page is opened for the
header selected. From the property page the DNP configuration parameters for the selected header is
displayed.
As DNP objects are defined they are added as leaves to the object branch of the tree control. When
an object is defined the object branch will display a collapse / expand control to the left of the
branch.
The Allow Duplicate Modbus Addresses checkbox (in the bottom left corner) determines if the
Modbus I/O database addresses assigned to the DNP data points must be unique. Check this box if
you want to allow more than one point to use the same Modbus address.
Uncheck the box if you want to be warned about duplicate addresses. If an attempt is made to use a
Modbus address that has already been used for another DNP point the following warning is
displayed.
5.1
Application Layer Configuration
The Application Layer property page is selected for editing by clicking Application Layer in the tree
control section of the DNP Settings window. When selected the Application Link Layer property
page is active.
DNP3 User and Reference Manual
May 9, 2007
25
Application Layer parameters are set in this property page. Each parameter is described in the
following paragraphs.
The Communication section of the dialog contains the configurable application layer
communication parameters.
When the Application Confirmation feature is enabled, the SCADAPack controller requests a
confirmation from the master station for any data transmitted. When it is disabled, the controller does
not request a confirmation from the master station and assumes that the master receives the data it
sends successfully. However if the data includes event data (including unsolicited messages), the
controller requests a confirmation from the master regardless of whether this feature is enabled or
disabled. Valid selections for this parameter are:
•
Enabled
•
Disabled
The Maximum Fragment Length is maximum size of a single response fragment that the RTU will
send. If the complete response message is too large to fit within a single fragment, then the
SCADAPack controller will send the response in multiple fragments. Valid values are between 100
and 2048 bytes.
This parameter is adjustable to allow for interoperability with simple DNP3 devices that require
smaller application layer fragments. Devices with limited memory may restrict the application layer
fragment size to as low as 249 bytes.
DNP3 User and Reference Manual
May 9, 2007
26
Note:
The Maximum Fragment Length parameter applies to responses from read commands only.
It does not affect unsolicited responses.
The Retries entry maximum number of times the application layer will retry sending a response or
an unsolicited response to the master station. This does not include any retries performed by the data
link layer. Valid values are between 0 and 255.
Note:
Using application layer Confirmation and Retries is inherently more efficient than using data
link layer Confirmation and Retries. Each fragment sent by the Application layer may
require as many as 10 data link layer frames to be sent, each with its own confirmation
message. The application layer is typically preferred for message confirmation for this
reason.
The Application Timeout is the expected time duration (in milliseconds) that the master station's
application layer requires to process and respond to a response from the SCADAPack controller.
This SCADAPack controller uses this value in setting its time-out interval for master station
responses. This value should be large enough to prevent response time-outs. The value must be kept
small enough so as not to degrade system throughput. The value of this element is dependent on the
master station. Valid values are between 100 and 60000 milliseconds.
The Time Synchronization section of the dialog defines when and how often the SCADAPack
outstation prompts the master station to synchronize the SCADAPack controller time. Messages
must be sent between the Master and Remote stations for Time Synchronization to work. Valid
selections for this parameter are:
•
The None selection will cause the SCADAPack controller to never request Time
Synchronization.
•
The At Start Up Only selection will cause the SCADAPack controller to request Time
Synchronization at startup only.
•
The Interval selection will cause the SCADAPack controller to request Time Synchronization at
startup and then every Interval minutes after receiving a time synchronization from the master.
Valid entries for Interval are between 1 and 32767 minutes. The default value is 60 minutes.
Note:
Time Synchronization may instead be initiated by the Master for each Outstation. This may
be selected in the Add/Edit Master Poll dialog. It is not required to enable Time
Synchronization at both the Master and the Outstation.
The Unsolicited Response section of the dialog defines which class objects are enabled or disabled
from generating report by exception responses. Unsolicited responses are individually configured for
Class 1, Class 2, and Class 3 data.
The Enable Unsolicited controls enables or disables unsolicited responses for Class 1, Class 2 or
Class 3 data. If unsolicited responses are disabled for a Class the controller never sends unsolicited
responses for that Class. If unsolicited responses are enabled the controller does not start sending
responses until the master enables the classes to report. Valid selections are:
•
Enabled
•
Disabled
The Hold Time parameter is used only when unsolicited responses are enabled for a Class. This
parameter defines the maximum period (in seconds) the RTU will be allowed to hold its events
before reporting them to the DNP master station. When the hold time has elapsed since the first event
DNP3 User and Reference Manual
May 9, 2007
27
occurred, the RTU will report to the DNP master station all events accumulated up to then. This
parameter is used in conjunction with the Hold Count parameter in customizing the unsolicited
event reporting characteristics. The value used for the Hold Time depends on the frequency of event
generation, topology and performance characteristics of the system. The valid values for this
parameter are 0 - 65535. The default value is 60 seconds.
The Hold Count parameter is used only when unsolicited responses are enabled for a Class. This
parameter defines the maximum number of events the RTU will be allowed to hold before reporting
them to the DNP master station. When the hold count threshold is reached, the RTU will report to
the master, all events accumulated up to that point. This parameter is used in conjunction with the
Hold Time in customizing the unsolicited event reporting characteristics. To guarantee an
unsolicited response is sent as soon as an event occurs, set the Hold Count parameter to 1. The valid
values for this parameter are 1 - 65535. The default value is 10.
The Enable Unsolicited Responses on Start Up parameter enables or disables unsolicited responses
on startup. This affects the default controller behaviour after a start-up or restart. Some hosts require
devices to start up with unsolicited responses enabled. It should be noted this is non-conforming
behaviour according to the DNP standard. Valid selections are:
•
Yes
•
No
The default selection is Yes.
The Send Initial Unsolicited Response on Startup parameter enables or disables Send Initial
unsolicited responses on startup. This parameter controls whether an initial unsolicited response with
null data is sent after a start-up or restart. Valid selections are:
Yes
No
The default selection is No.
The Dial Up section of the dialog defines modem parameters used when a dial up modem is used to
communicate with stations that use dial up communication. The phone numbers for the stations are
defined in the Routing table.
The Modem Initialization is the string that will be sent to the modem prior to each call. This is an
ASCII null-terminated string. The maximum length of the string is 64 characters, including the null
terminator.
The Attempts controls the maximum number of dial attempts that will be made to establish a Dial
Up connection. The valid values for this parameter are 1 – 10. The default value is 2.
The Dial Type parameter controls whether tone or pulse dialing will be used for the call. Valid
values are Tone dialing or Pulse dialing. The default value is Tone dialing.
The Connect Timeout controls the maximum time (in seconds) after initiating a dial sequence that
the firmware will wait for a carrier signal before hanging up. The valid values for this parameter are
1 – 65535. The default value is 45.
The Inactivity Timeout controls the maximum time after message activity that a connection will be
left open before hanging up. The valid values for this parameter are 1 – 65535 seconds. The default
value is 45 seconds.
The Pause Time controls the delay time (in seconds) between dial events, to allow time for
incoming calls. The valid values for this parameter are 1 – 65535. The default value is 10.
DNP3 User and Reference Manual
May 9, 2007
28
The Operate Timeout parameter specifies the timeout interval between a Select and Operate request
from the Master. If after receiving a valid Select control output request from the master, the RTU
does not receive the corresponding Operate request within this time-out interval, the control output
request fails. The value of this parameter, expressed in seconds, is dependent on the master station,
the data link and physical layer. Valid values are 1 to 6500 seconds. The default value is 15 seconds.
The Master must have the Select/Operate functionally in order to use this feature.
The Report only Level 2 Compliant Objects in Class Polls parameter affects how Short Float
Analog Input, Short Float Analog Output, and 32-bit Analog Output objects are reported. These
objects are converted to 32-bit Analog Input and 16-bit Analog Output objects when this parameter
is selected. Valid selections are:
•
Yes
•
No
The default selection is No.
The Limit Maximum Events in Read Response parameter allows limiting the number of events in
a read response. Select the checkbox to enable the limit. Valid values are 1 to 65535. The default
value is disabled.
Note:
The Maximum Events parameter applies to responses from read commands only. It does not
affect unsolicited responses.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
•
Click the OK button to accept the configuration changes and close the DNP Settings dialog.
•
Click the Cancel button to close the dialog without saving any changes.
5.2
Data Link Layer Configuration
The Data Link Layer property page is selected for editing by clicking Data Link Layer in the tree
control section of the DNP Settings window. When selected the Data Link Layer property page is
active.
DNP3 User and Reference Manual
May 9, 2007
29
Data Link Layer parameters are set in this property page. Each parameter is described in the
following paragraphs.
The Master Station Addresses list box contains a list of Master station addresses that the
SCADAPack controller will respond to. The default list contains one master address of 100. This
address may be edited, or changed, and up to 8 master stations may be added to the list. Valid entries
for Master Station Addresses are 0 to 65519.
•
When a master station polls for event data, the controller will respond with any events that have
not yet been reported to that master station.
•
When an unsolicited response becomes due, it will be sent to each configured master station in
turn. A complete unsolicited response message transaction, including retries, will be sent to the
first configured master station. When this transaction has finished, a complete unsolicited
response message transaction including retries will be sent to the next configured master station,
and so on for all the configured master stations.
•
Change events will be retained in the event buffer until they have been successfully reported to
all configured master stations.
Select the Add button to enter a new address to the Master Station Address list. Selecting the Add
button opens the Add Master Station Address dialog. Up to 8 entries can be added to the table. An
error message is displayed if the table is full.
DNP3 User and Reference Manual
May 9, 2007
30
Select the Edit button to edit address in the Master Station Address list. Selecting the Edit button
opens the Edit Master Station Address dialog. The button is disabled if there are no entries in the
list.
The Master Station Address edit box specifies the Master Station Address. Enter any valid Station
address from 0 to 65519.
•
The OK button adds the Master Station Address to the list and closes the dialog. An error is
displayed if the Master Station Address is invalid, if the address is already in the list, or if the
address conflicts with the RTU station address.
•
The Cancel button closes the dialog without making any changes.
The RTU Station Address parameter specifies the address of this RTU. It is the source address used
by this DNP driver when communicating with a master station. Each DNP station in a network must
have a unique address, including the Master station. Valid entries for RTU Station Address are 0 to
65519.
The Data Link Confirmation parameter specifies whether or not the RTU requests the underlying
data link transmitting its response to use a high quality service, which generally means that the data
link requires the receiving data link to confirm receipt of all messages.
The Retries parameter specifies the maximum number of times the data link layer will retry sending
a message to the master station. This parameter is only used when responding to a request from a
Master station, when there is no corresponding entry in the Routing dialog for that station. This is
independent of the application layer retries. The valid values for this parameter are 0 - 255. Setting
the value to 0 disables sending retries.
Note:
Using data link layer Confirmation and Retries is inherently less efficient than application
layer Confirmation and Retries. Each fragment sent by the Application layer may require as
many as 10 data link layer frames to be sent, each with its own confirmation message. The
data link layer is typically not used for message confirmation for this reason.
The Data Link Timeout parameter specifies the expected time duration that the master station's data
link layer requires to process and respond to a message from the RTUs data link layer. It is used by
the RTU in setting its time-out interval for master station responses. This value should be large
enough to prevent response time-outs. The value must be kept small enough so as not to degrade
system throughput. The value of this element is dependent on the master station. It is expressed in
milliseconds. Valid values are 10 to 60000 milliseconds. The default value is 500 milliseconds.
•
Click the OK button to accept the configuration changes and close the DNP Settings dialog.
•
Click the Cancel button to close the dialog without saving any changes.
•
Click the Delete button to remove the selected rows from the list. This button is disabled if there
are no entries in the list.
DNP3 User and Reference Manual
May 9, 2007
31
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.3
Master
The Master property page is selected for editing by clicking Master in the tree control section of the
DNP Settings window. This selection is only visible if the controller type is SCADAPack 350,
SCADAPack 32 or SCADAPack 32P. These controllers support DNP Master. When selected the
Master Application Link Layer property page is active.
Master parameters are set in this property page. Each parameter is described in the following
paragraphs.
The Mimic Mode parameter specifies the DNP Mimic Mode. The valid selections are Enable or
Disable. When DNP Mimic Mode is enabled the controller will intercept DNP messages destined for
a remote DNP station address, and will respond directly, as though the controller were the designated
target. For read commands, the controller will respond with data from its Remote DNP Objects
corresponding with the intended target address. For write commands, the controller will write data
into its Remote DNP Objects, and issue a direct response to acknowledge the command. It will then
issue a new command to write the data to the designated target. See Section 3.3-DNP Mimic Mode
section for an explanation of the concept around Mimic Mode. The default selection is Disabled.
The Base Poll Interval parameter is the base interval (in seconds) for polling slave devices. The poll
rates and issuing time synchronisation will be configured in multiples of the base poll interval. The
DNP3 User and Reference Manual
May 9, 2007
32
slave devices with the same poll rates will be polled in the order they appear in the poll table. The
valid values for this parameter are 1 to 65535. The default value is 10 seconds.
5.4
Master Poll
The Master Poll property page is selected for editing by clicking Master Poll in the tree control
section of the DNP Settings window. This selection is only visible if the controller type is a
SCADAPack 350, SCADAPack 32 or SCADAPack 32P. These controllers support DNP Master.
When selected the Master Poll property page is active and button Copy is renamed to Edit.
The Master Poll displays slave devices to be polled by this master station as a row, with column
headings, in the table. The table may have up to 1000 entries. A vertical scroll bar is used if the list
exceeds the window size.
Note:
All slave devices in the Master Poll table need to be added to the Routing table.
The Station column displays the address of the DNP slave device to be polled. Each entry in the
table should have unique DNP Station Address.
The Class 0 Rate column displays the rate of polling for Class 0 data, as a multiple of the base poll
interval.
The Class 1 Rate column displays the rate of polling for Class 1 data, as a multiple of the base poll
interval.
DNP3 User and Reference Manual
May 9, 2007
33
The Class 2 Rate column displays the rate of polling for Class 2 data, as a multiple of the base poll
interval.
The Class 3 Rate column displays the rate of polling for Class 3 data, as a multiple of the base poll
interval.
•
The OK button saves the table data and closes the DNP Settings dialog.
•
The Cancel button closes the dialog without saving changes.
Select the Add button to enter a new row in the Master Poll. Selecting the Add button opens the
Add/Edit Master Poll dialog.
Select the Edit button to modify the selected row in the Master Poll. Selecting the Edit button opens
the Add/Edit Master Poll dialog containing the data from the selected row. This button is disabled
if more than one row is selected or if there are no entries in the table.
The Delete button removes the selected rows from the table. This button is disabled if there are no
entries in the table.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click on the column headings to sort the data. Clicking once sorts the data in ascending order.
Clicking again sorts the data in descending order.
5.4.1
Add/Edit Master Poll Dialog
This dialog is used to edit an entry or add a new entry in the Master Poll.
DNP3 User and Reference Manual
May 9, 2007
34
The Station edit control displays the address of the DNP slave device to be polled. Valid values are
0 to 65519.
The Class 0 Polling section of the dialog specifies the type and rate of polling for Class 0 data.
•
The None selection disables class 0 polling for the slave station. This is the default selection.
•
The At Start Up Only selection will cause the master to poll the slave station at startup only.
•
The Interval selection will cause the master to poll the slave station at startup and then every
Interval of the base poll interval. For example if the base poll interval is 60 seconds and the
Interval parameter is set to 60 then the master will poll the slave station every hour. Valid values
are 1 to 32767. The default value is 60.
•
The Poll Offset parameter is used to distribute the load on the communication network. The Poll
Offset is entered in multiples of the base poll interval. Valid values for this parameter are 0 to the
Poll Interval value minus 1. Any non-zero value delays the start of polling for the specified
objects by that amount. The default value is 0. This control is disabled when None is selected,
and enabled otherwise. For an example of using the Poll Offset parameter see the Poll Offset
Example at the end of this section.
The Class 1 Polling section of the dialog specifies the type and rate of polling for Class 1 data.
•
The None selection disables class 1 polling for the slave station. This is the default selection.
•
The At Start Up Only selection will cause the master to poll the slave station at startup only.
•
The Interval selection will cause the master to poll the slave station at startup and then every
Interval of the base poll interval. For example if the base poll interval is 60 seconds and the
Interval parameter is set to 60 then the master will poll the slave station every hour. Valid values
are 1 to 32767. The default value is 60.
DNP3 User and Reference Manual
May 9, 2007
35
•
The Poll Offset parameter is used to distribute the load on the communication network. The Poll
Offset is entered in multiples of the base poll interval. Valid values for this parameter are 0 to the
Poll Interval value minus 1. Any non-zero value delays the start of polling for the specified
objects by that amount. The default value is 0. This control is disabled when None is selected,
and enabled otherwise. For an example of using the Poll Offset parameter see the Poll Offset
Example at the end of this section.
•
Limit Maximum Events allows limiting the number of events in poll responses for Class 1/2/3
data. The checkbox is not checked by default, meaning there is no limit on the number of events.
Select the checkbox to specify a limit. The valid values for this parameter are 1 to 65535. The
default value is 65535. This control is disabled when None is selected, and enabled otherwise.
The Maximum Events parameter can be used to manage communication load on a system.
Consider the example of a master polling some data logging remotes, and the case where one of
the remotes has been offline for a long time. The remote will have built up a large number of
buffered events. If the master polled it for all events, the reply might take a long time, and cause
an unwanted delay in the master's polling cycle. However if the master limits the number of
events returned, the reply message duration will be more deterministic and the master can ensure
its poll loop timing is maintained. In this case, the event retrieval from the data logger will be
distributed over a number of poll cycles.
The Class 2 Polling section of the dialog specifies the type and rate of polling for Class 2 data.
•
The None selection disables class 1 polling for the slave station. This is the default selection.
•
The At Start Up Only selection will cause the master to poll the slave station at startup only.
•
The Interval selection will cause the master to poll the slave station at startup and then every
Interval of the base poll interval. For example if the base poll interval is 60 seconds and the
Interval parameter is set to 60 then the master will poll the slave station every hour. Valid values
are 1 to 32767. The default value is 60.
•
The Poll Offset parameter is used to distribute the load on the communication network. The Poll
Offset is entered in multiples of the base poll interval. Valid values for this parameter are 0 to the
Poll Interval value minus 1. Any non-zero value delays the start of polling for the specified
objects by that amount. The default value is 0. This control is disabled when None is selected,
and enabled otherwise. For an example of using the Poll Offset parameter see the Poll Offset
Example at the end of this section.
•
Limit Maximum Events allows limiting the number of events in poll responses for Class 1/2/3
data. The checkbox is not checked by default, meaning there is no limit on the number of events.
Select the checkbox to specify a limit. The valid values for this parameter are 1 to 65535. The
default value is 65535. This control is disabled when None is selected, and enabled otherwise.
The Maximum Events parameter can be used to manage communication load on a system.
Consider the example of a master polling some data logging remotes, and the case where one of
the remotes has been offline for a long time. The remote will have built up a large number of
buffered events. If the master polled it for all events, the reply might take a long time, and cause
an unwanted delay in the master's polling cycle. However if the master limits the number of
events returned, the reply message duration will be more deterministic and the master can ensure
its poll loop timing is maintained. In this case, the event retrieval from the data logger will be
distributed over a number of poll cycles.
The Class 3 Polling section of the dialog specifies the type and rate of polling for Class 3 data.
•
The None selection disables class 1 polling for the slave station. This is the default selection.
DNP3 User and Reference Manual
May 9, 2007
36
•
The At Start Up Only selection will cause the master to poll the slave station at startup only.
•
The Interval selection will cause the master to poll the slave station at startup and then every
Interval of the base poll interval. For example if the base poll interval is 60 seconds and the
Interval parameter is set to 60 then the master will poll the slave station every hour. Valid values
are 1 to 32767. The default value is 60.
•
The Poll Offset parameter is used to distribute the load on the communication network. The Poll
Offset is entered in multiples of the base poll interval. Valid values for this parameter are 0 to the
Poll Interval value minus 1. Any non-zero value delays the start of polling for the specified
objects by that amount. The default value is 0. This control is disabled when None is selected,
and enabled otherwise. For an example of using the Poll Offset parameter see the Poll Offset
Example at the end of this section.
•
Limit Maximum Events allows limiting the number of events in poll responses for Class 1/2/3
data. The checkbox is not checked by default, meaning there is no limit on the number of events.
Select the checkbox to specify a limit. The valid values for this parameter are 1 to 65535. The
default value is 65535. This control is disabled when None is selected, and enabled otherwise.
The Maximum Events parameter can be used to manage communication load on a system.
Consider the example of a master polling some data logging remotes, and the case where one of
the remotes has been offline for a long time. The remote will have built up a large number of
buffered events. If the master polled it for all events, the reply might take a long time, and cause
an unwanted delay in the master's polling cycle. However if the master limits the number of
events returned, the reply message duration will be more deterministic and the master can ensure
its poll loop timing is maintained. In this case, the event retrieval from the data logger will be
distributed over a number of poll cycles.
The Time Synchronization Rate section of the dialog specifies the rate of issuing a time
synchronization to this device, as a multiple of the base poll interval. Valid selections for this
parameter are:
•
The None selection will disable issuing a time sync to this device. This is the default selection.
•
The At Start Up Only selection will cause issuing a time synchronization at startup only.
•
The Interval selection will cause the RTU to issue a time synchronization at startup and then
every Interval of the base poll interval seconds. Valid entries for Interval are between 1 and
32767 the base poll interval seconds. The default value is 60.
The Unsolicited Responses section is used in conjunction with the Enable Unsolicited Responses on
Start Up parameter on the Application Layer page. Certain non-SCADAPack slave devices are
designed to start with their Enable Unsolicited Responses on Start Up parameter set to No. Selecting
Enabled for any class causes the master to (after it detects the slave come online) send a command
allowing the slave to begin sending Unsolicited Responses of that class.
With SCADAPack slaves the Enable Unsolicited Responses on Start Up parameter may be set to
Yes, and the Accept Class parameters may be left at Disabled.
•
The Accept Class 1 selection displays the enable/disable status of unsolicited responses from the
slave device for Class 1 events. The default selection is disabled.
•
The Accept Class 2 selection displays the enable/disable status of unsolicited responses from the
slave device for Class 1 events. The default selection is disabled.
•
The Accept Class 3 selection displays the enable/disable status of unsolicited responses from the
slave device for Class 1 events. The default selection is disabled.
DNP3 User and Reference Manual
May 9, 2007
37
The Save IIN Flags checkbox enables storing the IIN (Internal Indications) flags from the slave
station in a Modbus database register. When this parameter is checked the IIN flags are saved to the
entered Modbus register address. Valid entries are Modbus register addresses 30001 to 39999 and
40001 to 49999. The default value is 0.
The IIN flags are set by the slave to indicate the events in the following table. The events are bit
mapped to the Modbus register. All bits except Device Restarted and Time Synchronization required
are cleared when the slave station receives any poll or read data command. The master will write to
bits 5 and 11 depending on the local conditions in the master.
Bit
Description
0
1
2
3
4
5
6
last received message was a broadcast message
Class 1 data available
Class 2 data available
Class 3 data available
Time Synchronization required
not used (returns 0)
Device trouble
Indicates memory allocation error in the slave, or
For master in mimic mode indicates communication failure with the slave
device.
Device restarted (set on a power cycle)
Function Code not implemented
Requested object unknown or there were errors in the application data
Parameters out of range
Event buffer overflowed
Indicates event buffer overflow in the slave or master. The slave will set this
bit if the event buffer in the slave is overflowed. The master will set this bit if
the event buffer in the master has overflowed with events read from the
slave. Ensure the event buffer size, in the master and slave, is set to a value
that will ensure the buffer does not overflow and events are lost.
not used (returns 0)
not used (returns 0)
not used (returns 0)
not used (returns 0)
7
8
9
10
11
12
13
14
15
The OK button checks the data for this table entry. If the data is valid the dialog is closed. If the
table data entered is invalid, an error message is displayed and the dialog remains open. The table
entry is invalid if any of the fields is out of range. The data is also invalid if it conflicts with another
entry in the table. Such conflict occurs when the station number is not unique. The ordering of items
in this table is important.
The Cancel button closes the dialog without saving changes.
5.4.2
Poll Offset Example
The Poll Offset parameter enhances the control over timing of master poll messages, by allowing
master poll messages to be staggered.
For example, a master station may have 10 slaves to poll, and must poll them every hour. If these are
included in the poll table without any poll offset, they will all be polled in quick succession on the
hour – resulting in a large burst of communication activity once per hour. On some types of
DNP3 User and Reference Manual
May 9, 2007
38
communications networks (particularly radio) it is desirable to distribute communication load more
evenly, to minimize the chance of collisions and to avoid the possibility of consuming bandwidth
continuously for an extended period of time.
The poll offset parameter enables you to distribute the communication load evenly. In the above
example, it is possible to stagger the master polls so slave stations are polled at 6-minute intervals.
To do this, set the base poll interval to 6 minutes, and for each slave station set the poll rate and poll
offset parameters as follows:
5.5
Base Poll
Poll Rate
Poll Offset
6
6
6
6
6
6
6
6
6
6
10
10
10
10
10
10
10
10
10
10
0
1
2
3
4
5
6
7
8
9
Address Mapping
The Address Mapping property page is selected for editing by clicking Address Mapping in the tree
control section of the DNP Settings window. This selection is only visible if the controller type is a
SCADAPack 350, SCADAPack 32 or SCADAPack 32P. These controllers support DNP Master.
The Address Mapping contains a set of mapping rules, which will allow the Remote DNP Objects to
be mapped into local Modbus registers. This makes the data accessible locally, to be read and/or
DNP3 User and Reference Manual
May 9, 2007
39
written locally in logic. It is also possible to perform data concentration – to map the remote DNP
Objects into the local DNP address space – by defining local DNP objects and then mapping the
remote DNP objects to the same Modbus registers. Change events can also be mapped in the same
way - there is a configuration option to allow mapping of change events from a remote DNP slave
into the local DNP change event buffer. The table may have up to 1000 entries. See the DNP
Address Mapping section for further information. A vertical scroll bar is used if the list exceeds the
window size.
The Station column displays the address of the remote DNP station.
The Object Type column displays the DNP data object type.
The First Point column displays the starting address of the remote DNP data points.
The Number column displays the number of remote points to be mapped.
The First Register column displays the starting address of local Modbus register where the remote
data points are to be mapped.
The Map Change Events combo box enables or disables mapping of change events from a remote
DNP slave into the local DNP change event buffer. Mapped change events may trigger an
Unsolicited message to be sent, after the Hold Count or Hold Time is reached. It may be desired
instead to map only static (live) values into local Modbus registers. The default selection is Disabled.
The default selection is Disabled.
The OK button saves the table data. No error checking is done on the table data.
The Cancel button closes the dialog without saving changes.
Select the Add button to enter a new row in the Address Mapping. Selecting the Add button opens
the Add/Edit Address Mapping dialog.
Select the Edit button to modify the selected row in the Address Mapping. Selecting the Edit button
opens the Add/Edit Address Mapping dialog containing the data from the selected row. This button
is disabled if more than one row is selected. This button is disabled if there are no entries in the table.
The Delete button removes the selected rows from the table. This button is disabled if there are no
entries in the table.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click on the column headings to sort the data. Clicking once sorts the data in ascending order.
Clicking again sorts the data in descending order.
5.5.1
Add/Edit Address Mapping Dialog
This dialog is used to edit an entry or add a new entry in the Address Mapping.
DNP3 User and Reference Manual
May 9, 2007
40
The Station edit control displays the address of the remote DNP station. Valid values for this field
are from 0 to 65519.
The Object Type combo box displays the DNP data Object Type. The list of available types
includes: Binary Input, Binary Output, 16-bit Analog Input, 32-bit Analog Input, Short Floating
Point Analog Input, 16-bit Analog Output, 32-bit Analog Output, Short Floating Point Analog
Output, 16-bit Counter Input, 32-bit Counter Input. The Default selection is Binary Input.
The First Point edit control displays the starting address of the remote DNP data points. Valid
values are from 0 to 65519.
The Number edit control displays the number of remote points to be mapped. Valid values for this
field are from 1 to 9999.
The First Register edit control displays the starting address of local Modbus register where the
remote data points are to be mapped. Valid values depend on the selection of DNP Object Type and
are as follows:
For Binary Inputs valid range is from 10001 to 14096.
For Binary Outputs valid range is from 00001 to 04096.
For Analog Inputs and Counter Inputs valid range is from 30001 to 39999.
For Analog Outputs valid range is from 40001 to 49999.
The OK button checks the data for this table entry. If the data is valid the dialog is closed. If the
table data entered is invalid, an error message is displayed and the dialog remains open. The table
entry is invalid if any of the fields is out of range. The data is also invalid if it conflicts with another
entry in the table. Such conflict occurs when the combination of station number, object type, and
object address is not unique. The ordering of items in this table is not important.
The Cancel button closes the dialog without saving changes.
5.6
Routing
In a typical application the SCADAPack controller, configured for DNP, will act as a DNP slave
station in a network. The SCADA system will communicate directly with all the DNP slave stations
in the SCADA system.
DNP routing is a method for routing, or forwarding, of messages received from the SCADA system,
through the SCADAPack controller, to a remote DNP slave station. The SCADAPack DNP slave
station will respond to all messages sent to it from the SCADA system, as well as broadcast
messages. When it receives a message that is not sent to it the message is sent on the serial port
defined in the routing table. See section 3.4-DNP Routing for an explanation of using and
configuring DNP Routing.
DNP3 User and Reference Manual
May 9, 2007
41
The advantage of this routing ability is that the SCADA system can communicate directly with the
SCADAPack controller and the SCADAPack controller can handle the communication to remote
DNP slave stations.
The DNP Routing table displays each routing translation as a row, with column headings, in the
table. Entries may be added, edited or deleted using the button selections on the table. The table will
hold a maximum of 128 entries.
The DNP Routing property page is selected for editing by clicking DNP Routing in the tree control
section of the DNP Settings window. When selected the DNP Routing property page is displayed.
Notes:
•
Routing must be enabled for the controller serial port in order to enable DNP routing.
•
TelePACE version 2.63 cannot open files created with version 2.64, unless the Routing table is
empty.
•
TelePACE version 2.64 cannot open files created with version 2.65, unless the Routing table is
empty.
The Station column displays the address of the remote DNP station.
The Port column displays the serial communications port, which should be used to communicate
with this DNP station.
The Retries column displays the maximum number of Data Link retries, which should be used for
this DNP station in the case of communication errors.
The Timeout column displays the maximum time (in milliseconds) to wait for a Data Link response
before retrying or failing the message.
DNP3 User and Reference Manual
May 9, 2007
42
The IP Address column displays the IP address of the remote DNP station.
The OK button saves the table data. No error checking is done on the table data.
The Cancel button closes the dialog without saving changes.
Select the Add button to enter a new row in the DNP Routing table. Selecting the Add button opens
the Add/Edit DNP Route dialog.
Select the Edit button to modify the selected row in the DNP Routing table. Selecting the Edit button
opens the Add/Edit DNP Route dialog containing the data from the selected row. This button is
disabled if more than one row is selected. This button is disabled if there are no entries in the table.
The Delete button removes the selected rows from the table. This button is disabled if there are no
entries in the table.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click on the column headings to sort the data. Clicking once sorts the data in ascending order.
Clicking again sorts the data in descending order.
5.6.1
Add/Edit DNP Route Dialog
This dialog is used to edit an entry or add a new entry in the DNP Routing table.
The Station edit control displays the address of the remote DNP station. Valid values for this field
are from 0 to 65519.
The Port combo box displays the communications port, which should be used to communicate with
the remote DNP station. This combo box contains list of the valid communications ports, which will
depend on the type of controller. For SCADAPack 350, SCADAPack 32 and SCADAPack 32P
controllers the list will contain DNP in TCP and DNP in UDP in addition to the serial port
designations, COM1, COM2 etc.
The IP Address edit control is only enabled if the controller type is a SCADAPack 350,
SCADAPack 32 or SCADAPack 32P. Enter the IP address of the remote DNP station.
The Data Link Retries edit control displays the maximum number of Data Link retries which
should be used for this DNP station in the case of communication errors. This field overrides the
DNP3 User and Reference Manual
May 9, 2007
43
Data Link Retries field in the global DNP parameters set in the Data Link Layer configuration. Valid
values for this field are 0 to 255.
The Data Link Timeout edit control displays the maximum time (in milliseconds) to wait for a Data
Link response before retrying or failing the message. This field overrides the Data Link Timeout
field in the global DNP parameters in the Data Link Layer configuration. Valid values for this field
are 100 to 60000, in multiples of 100.
The phone number parameters allow automatic dialing for stations that use dial-up ports. The Phone
Number parameters are enabled only when the Port selected is a serial port.
The Primary Phone Number is the dialing string that will be used for the primary connection to the
station. The controller will make 1 or more attempts, as configured in the Application layer, to
connect using this number. If this connection fails then the Secondary Phone Number will be dialed,
if it is entered.
Valid values are any ASCII string. The maximum length is 32 characters. Leave this blank if you are
not using a dial-up connection. The default value is blank. The serial port type must be set to RS-232
Modem for dial-up operation.
The Secondary Phone Number is the dialing string that will be used for the secondary connection
to the station. The controller will make 1 or more attempts, as configured in the Application layer, to
connect using this number. This number is used after the primary connection fails on all attempts.
Valid values are any ASCII string. The maximum length is 32 characters. Leave this blank if you are
not using a dial-up connection. The default value is blank. The serial port type must be set to RS-232
Modem for dial-up operation.
The OK button checks the data for this table entry. If the data is valid the dialog is closed. If the
table data entered is invalid, an error message is displayed and the dialog remains open. The table
entry is invalid if any of the fields is out of range. The data is also invalid if it conflicts with another
entry in the table.
The Cancel button closes the dialog without saving changes.
5.6.2
Dynamic Routing
In addition to the configured routing table, there is an internal dynamic routing entry. This entry is
not shown in the routing table. The dynamic routing entry listens to incoming messages and learns
the address of the remote station and the communication port used for communicating with it.
If there is no entry in the routing table, the RTU will use the dynamic routing entry to respond to a
message on the same communication port as the incoming message.
The dynamic routing entry is not cleared on initialization. This is deliberate, and is important for
controllers that need to be remotely reconfigured. In this case the host can initialize the controller
without losing the communications link.
Note:
5.7
Dynamic routing should not be used in a master station. Configure all slave stations in the
routing table.
Binary Inputs Configuration
The Binary Inputs property page is selected for editing by clicking Binary Inputs in the tree control
section of the DNP Settings window. When selected the Binary Inputs property page is active.
DNP3 User and Reference Manual
May 9, 2007
44
Binary Inputs parameters are set in this property page. Each parameter is described in the following
paragraphs.
The Number of Points displays number of binary inputs reported by this RTU. This value will
increment with the addition of each configured Binary Input point. The maximum number of points
is 9999. The maximum number of actual points will depend on the memory available in the
controller.
The Starting Address parameter specifies the starting DNP address of the first Binary Input point.
The Event Reporting Method selection specifies how binary input events are reported. A Change
Of State event is an event object, without time, that is generated when the point changes state. Only
one event is retained in the buffer for each point. If a subsequent event occurs for a point, the
previous event object will be overwritten. The main purpose of this mode is to allow a master station
to efficiently poll for changed data. A Log All Events is event object with absolute time will be
generated when the point changes state. All events will be retained. The main purpose of this mode is
to allow a master station to obtain a complete historical data log. The selections are:
•
Change of State
•
Log All Events
The Event Buffer Size is the maximum number of binary input change events, which can be
buffered by the DNP driver. The buffer holds all binary input change events, regardless of the class
to which they are assigned. If the buffer fills to 90 percent the RTU will send a buffer overflow event
to the master station. If the buffer is completely full the RTU will lose the oldest events and retain
the newest. The size of the event buffer should be at least equivalent to the number of Binary Inputs
defined with a Class. This will allow all Binary Inputs to change simultaneously without losing any
events. The value of this parameter is dependent on how often change events occur and the rate at
DNP3 User and Reference Manual
May 9, 2007
45
which the events are reported to the master station. The valid values for this parameter are 0 - 65535.
Default value is 16.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.7.1
Adding Binary Inputs
Binary Inputs are added to the DNP configuration using the Binary Input property page. To add a
Binary Input:
•
Select Binary Inputs in the tree control section of the DNP Settings window.
•
Click the Add button in the Binary Inputs property page.
•
The Binary Input property page is now displayed.
•
Edit the Binary Input parameters as required and then click the Add button.
As Binary Inputs are defined they are added as leaves to the Binary Inputs branch of the tree control.
When Binary Inputs are defined the Binary Inputs branch will display a collapse / expand control to
the left of the branch. Click this control to display all defined Binary Inputs.
The Binary Input parameters are described in the following paragraphs.
The DNP Address window displays the DNP Binary Input address of the point. Each Binary Input is
assigned a DNP address as they are defined. The DNP point address starts at the value defined in the
Binary Inputs configuration dialog and increments by one with each defined Input.
DNP3 User and Reference Manual
May 9, 2007
46
The Modbus Address parameter specifies the Modbus address of the Binary Input assigned to the
DNP Address. The SCADAPack and Micro16 controllers use Modbus addressing for all digital
inputs. Refer to the I/O Database Registers section of the TelePACE Ladder Logic Reference and
User Manual for complete information on digital input addressing in the SCADAPack and Micro16
controllers. Valid Modbus addresses are:
•
00001 through 09999
•
10001 through 19999
The Class of Event Object parameter specifies the event object class the Binary Input is assigned.
The selections are:
•
None
•
Class 1
•
Class 2
•
Class 3
The Debounce parameter limits the frequency of change events. The input must remain in the same
state for the debounce time for a change of state to be detected. Note that the input is sampled every
0.1s. Changes shorter than the sample time cannot be detected. Valid values are 0 to 65535 tenths of
seconds. The value 0 means no debounce. The default value is 0.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the Binary Input parameters and close the DNP Settings dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current Binary Input to the DNP configuration.
Click the Copy button to copy the current Binary Input parameters to the next DNP Address.
Click the Delete button to delete the current Binary Input.
Click the Move Up button to move the current Binary Input up one position in the tree control
branch.
Click the Move Down button to move the current Binary Input down one position in the tree control
branch.
5.8
Binary Outputs Configuration
The Binary Outputs property page is selected for editing by clicking Binary Outputs in the tree
control section of the DNP Settings window. When selected the Binary Outputs property page is
active.
DNP3 User and Reference Manual
May 9, 2007
47
Binary Outputs parameters are viewed in this property page.
The Number of Points displays the number of binary outputs reported by this RTU. This value will
increment with the addition of each configured Binary Output point. The maximum number of points
is 9999. The maximum number of actual points will depend on the memory available in the
controller.
The Starting Address parameter specifies the starting DNP address of the first Binary Output point.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.8.1
Adding Binary Outputs
Binary Outputs are added to the DNP configuration using the Binary Output property page. To add a
Binary Output:
•
Select Binary Outputs in the tree control section of the DNP Settings window.
•
Click the Add button in the Binary Outputs property page.
•
The Binary Output property page is now displayed.
•
Edit the Binary Output parameters as required and then click the Add button.
As Binary Outputs are defined they are added as leaves to the Binary Outputs branch of the tree
control. When Binary Outputs are defined the Binary Outputs branch will display a collapse / expand
control to the left of the branch. Click this control to display all defined Binary Outputs.
DNP3 User and Reference Manual
May 9, 2007
48
The Binary Output parameters are described in the following paragraphs.
The DNP Address window displays the DNP Binary Output address of the point. Each Binary
Output is assigned a DNP address as they are defined. The DNP point address starts at the value
defined in the Binary Outputs dialog and increments by one with each defined Output.
The Modbus Address 1 parameter specifies the Modbus address of the Binary Output assigned to
the DNP Address. The SCADAPack and Micro16 controllers use Modbus addressing for all digital
outputs. Refer to the I/O Database Registers section of the TelePACE Ladder Logic Reference
Manual for complete information on digital output addressing in the SCADAPack and Micro16
controllers. Valid Modbus addresses are:
•
00001 through 09999
The Modbus Address 2 parameter specifies the second Modbus address of the second Binary
Output assigned to the DNP Address when the Paired control type is selected. This selection is not
active when the control type is Not Paired. Valid Modbus addresses are:
•
00001 through 09999
The Control Type parameter specifies whether the Binary Output is a paired control or not. If it is a
paired control, i.e. trip/close output type, this means that the DNP address is associated to two
physical control outputs and requires two Modbus addresses per DNP address. Control type
selections are:
•
Paired
•
Not Paired
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to
allow more than one point to use the same Modbus address.
DNP3 User and Reference Manual
May 9, 2007
49
Click the OK button to accept the Binary Output parameters and close the DNP Settings dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current Binary Output to the DNP configuration.
Click the Copy button to copy the current Binary Output parameters to the next DNP Address.
Click the Delete button to delete the current Binary Output.
Click the Move Up button to move the current Binary Output up one position in the tree control
branch.
Click the Move Down button to move the current Binary Output down one position in the tree
control branch.
5.9
16–Bit Analog Inputs Configuration
The 16-Bit Analog Inputs property page is selected for editing by clicking 16-Bit Analog Inputs in
the tree control section of the DNP Settings window. When selected the 16-Bit Analog Inputs
property page is active.
16-Bit Analog Inputs parameters are set in this property page. Each parameter is described in the
following paragraphs.
The Number of Points displays the number of 16 bit analog inputs reported by the RTU. This value
will increment with the addition of each configured 16-Bit Analog Input point. The maximum
number of points is 9999. The maximum number of actual points will depend on the memory
available in the controller.
The Starting Address parameter specifies the DNP address of the first 16-bit Analog Input point.
DNP3 User and Reference Manual
May 9, 2007
50
The Event Reporting Method selection specifies how 16-bit Analog Input events are reported. A
Change Of State event is an event object, without time, that is generated when the point changes
state. Only one event is retained in the buffer for each point. If a subsequent event occurs for a point,
the previous event object will be overwritten. The main purpose of this mode is to allow a master
station to efficiently poll for changed data. A Log All Events event object with absolute time will be
generated when the point changes state. All events will be retained. The main purpose of this mode is
to allow a master station to obtain a complete historical data log. The selections are:
•
Change of State
•
Log All Events
The Event Buffer Size parameter specifies the maximum number of 16-Bit Analog Input change
without time events buffered by the RTU. The buffer holds all 16-Bit Analog Input events,
regardless of the class to which they are assigned. If the buffer fills to 90 percent the RTU will send a
buffer overflow event to the master station. If the buffer is completely full the RTU will lose the
oldest events and retain the newest. The Event Buffer size should be at least equivalent to the
number of 16-Bit Analog Inputs defined as Change of State type. That will allow all 16-Bit Analog
Inputs to exceed the deadband simultaneously without losing any events. The value of this parameter
is dependent on how often 16-Bit Analog Input events occur and the rate at which the events are
reported to the master station. The valid values for this parameter are 0 - 65535. Default value is 16.
For SCADAPack 32 and SCADAPack 32P controllers analog input events are processed by the DNP
driver at a rate of 100 events every 100 ms. If more than 100 analog input events need to be
processed they are processed sequentially in blocks of 100 until all events are processed. This allows
the processing of 1000 analog input events per second.
For SCADASense Series of controllers, SCADAPack 100, SCADAPack LP, SCADAPack and
Micro16 controllers analog input events are processed by the DNP driver at a rate of 20 events every
100 ms. If more than 20 analog input events need to be processed they are processed sequentially in
blocks of 20 until all events are processed. This allows the processing of 200 analog input events per
second.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.9.1
Adding 16-Bit Analog Inputs
16-Bit Analog Inputs are added to the DNP configuration using the 16-Bit Analog Input property
page. To add a 16-Bit Analog Input:
•
Select 16-Bit Analog Inputs in the tree control section of the DNP Settings window.
•
Click the Add button in the 16-Bit Analog Inputs property page.
•
The 16-Bit Analog Input property page is now displayed.
•
Edit the 16-Bit Analog Input parameters as required and then click the Add button.
As 16-Bit Analog Inputs are defined they are added as leaves to the 16-Bit Analog Inputs branch of
the tree control. When 16-Bit Analog Inputs are defined the 16-Bit Analog Inputs branch will display
a collapse / expand control to the left of the branch. Click this control to display all defined 16-Bit
Analog Inputs.
DNP3 User and Reference Manual
May 9, 2007
51
The 16-Bit Analog Input parameters are described in the following paragraphs.
The DNP Address window displays the DNP 16-Bit Analog Input address of the point. Each 16-Bit
Analog Input is assigned a DNP address as they are defined. The DNP point address starts at the
value set in the 16-bit Analog Input configuration dialog and increments by one with each defined
16-Bit Analog Input.
The Modbus Address parameter specifies the Modbus address of the 16-Bit Analog Input assigned
to the DNP Address. The SCADAPack and Micro16 controllers use Modbus addressing for all
analog inputs. Refer to the I/O Database Registers section of the TelePACE Ladder Logic
Reference and User Manual for complete information on analog input addressing in the
SCADAPack and Micro16 controllers. Valid Modbus addresses are:
•
30001 through 39999
•
40001 through 49999
The Class of Event Object parameter specifies the event object class assigned to the 16-Bit Analog
Input is assigned. If Unsolicited reporting is not required for a point, it is recommended to set its
Class to None. All data points automatically become members of Class 0 or None (static data). The
selections are:
•
None
•
Class 1
•
Class 2
•
Class 3
The Deadband parameter specifies the minimum number of counts that the 16-Bit Analog Input
must change since it was last reported in order to generate an event. Valid deadband values are 0 to
65535. A deadband of zero will cause any change to create an event.
DNP3 User and Reference Manual
May 9, 2007
52
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the 16-Bit Analog Input parameters and close the DNP Settings
dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current 16-Bit Analog Input to the DNP configuration.
Click the Copy button to copy the current 16-Bit Analog Input parameters to the next DNP Address.
Click the Delete button to delete the current 16-Bit Analog Input.
Click the Move Up button to move the current 16-Bit Analog Input up one position in the tree
control branch.
Click the Move Down button to move the current 16-Bit Analog Input down one position in the tree
control branch.
5.10
32-Bit Analog Inputs Configuration
The 32-Bit Analog Inputs property page is selected for editing by clicking 32-Bit Analog Inputs in
the tree control section of the DNP Settings window. When selected the 32-Bit Analog Inputs
property page is active.
32-Bit Analog Inputs parameters are set in this property page. Each parameter is described in the
following paragraphs.
The Number of Points displays the number of 32- bit analog inputs reported by the RTU. This value
will increment with the addition of each configured 32-Bit Analog Input point. The maximum
number of points is 9999. The maximum number of actual points will depend on the memory
available in the controller.
DNP3 User and Reference Manual
May 9, 2007
53
The Starting Address parameter specifies the DNP address of the first 32-bit Analog Input point.
The Event Reporting Method selection specifies how 32-bit Analog Input events are reported. A
Change Of State event is an event object, without time, that is generated when the point changes
state. Only one event is retained in the buffer for each point. If a subsequent event occurs for a point,
the previous event object will be overwritten. The main purpose of this mode is to allow a master
station to efficiently poll for changed data. A Log All Events is event object with absolute time will
be generated when the point changes state. All events will be retained. The main purpose of this
mode is to allow a master station to obtain a complete historical data log. The selections are:
•
Change of State
•
Log All Events
The Event Buffer Size parameter specifies the maximum number of 32-Bit Analog Input change
without time events buffered by the RTU. The buffer holds all 32-Bit Analog Input events,
regardless of the class to which they are assigned. If the buffer fills to 90 percent the RTU will send a
buffer overflow event to the master station. If the buffer is completely full the RTU will lose the
oldest events and retain the newest. The Event Buffer size should be at least equivalent to the
number of 32-Bit Analog Inputs defined as Change of State type. That will allow all 32-Bit Analog
Inputs to exceed the deadband simultaneously without losing any events. The value of this parameter
is dependent on how often 32-Bit Analog Input events occur and the rate at which the events are
reported to the master station. The valid values for this parameter are 0 - 65535. Default value is 16.
For SCADAPack 32 and SCADAPack 32P controllers analog input events are processed by the DNP
driver at a rate of 100 events every 100 ms. If more than 100 analog input events need to be
processed they are processed sequentially in blocks of 100 until all events are processed. This allows
the processing of 1000 analog input events per second.
For SCADASense Series of controllers, SCADAPack 100, SCADAPack LP, SCADAPack and
Micro16 controllers analog input events are processed by the DNP driver at a rate of 20 events every
100 ms. If more than 20 analog input events need to be processed they are processed sequentially in
blocks of 20 until all events are processed. This allows the processing of 200 analog input events per
second.
The Word Order selection specifies the word order of the 32-bit value. The selections are:
•
TelePACE Least Significant Word in first register.
•
ISaGRAF Most Significant Word in first register.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.10.1
Adding 32-Bit Analog Inputs
32-Bit Analog Inputs are added to the DNP configuration using the 16-Bit Analog Input property
page. To add a 32-Bit Analog Input:
•
Select 32-Bit Analog Inputs in the tree control section of the DNP Settings window.
•
Click the Add button in the 32-Bit Analog Inputs property page.
•
The 32-Bit Analog Input property page is now displayed.
•
Edit the 32-Bit Analog Input parameters as required and then click the Add button.
DNP3 User and Reference Manual
May 9, 2007
54
As 32-Bit Analog Inputs are defined they are added as leaves to the 32-Bit Analog Inputs branch of
the tree control. When 32-Bit Analog Inputs are defined the 32-Bit Analog Inputs branch will display
a collapse / expand control to the left of the branch. Click this control to display all defined 32-Bit
Analog Inputs.
The 32-Bit Analog Input parameters are described in the following paragraphs.
The DNP Address window displays the DNP 32-Bit Analog Input address of the point. Each 32-Bit
Analog Input is assigned a DNP address as they are defined. The DNP point address starts at the
value set in the 32-bit Analog Input configuration dialog and increments by one with each defined
32-Bit Analog Input.
The Modbus Address parameter specifies the Modbus addresses of the 32-Bit Analog Input
assigned to the DNP Address. 32-Bit Analog Inputs use two consecutive Modbus registers for each
assigned DNP Address, the address that is entered in this box and the next consecutive Modbus
register. The SCADAPack and Micro16 controllers use Modbus addressing for all analog inputs.
Refer to the I/O Database Registers section of the TelePACE Ladder Logic Reference and User
Manual for complete information on analog input addressing in the SCADAPack and Micro16
controllers. Valid Modbus addresses are:
•
30001 through 39998
•
40001 through 49998
The Class of Event Object parameter specifies the event object class the 32-Bit Analog Input is
assigned. If Unsolicited reporting is not required for a DNP point, it is recommended to set its Class
0 or None. All data points automatically become members of Class 0 or None (static data).The
selections are:
•
None
•
Class 1
DNP3 User and Reference Manual
May 9, 2007
55
•
Class 2
•
Class 3
The Deadband parameter specifies whether the RTU generates events. The value entered is the
minimum number of counts that the 32-Bit Analog Input must change since it was last reported.
Valid deadband values are 0 to 4,294,967,295. A deadband of zero will cause any change to create
an event.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the 32-Bit Analog Input parameters and close the DNP Settings
dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current 32-Bit Analog Input to the DNP configuration.
Click the Copy button to copy the current 32-Bit Analog Input parameters to the next DNP Address.
Click the Delete button to delete the current 32-Bit Analog Input.
Click the Move Up button to move the current 32-Bit Analog Input up one position in the tree
control branch.
Click the Move Down button to move the current 32-Bit Analog Input down one position in the tree
control branch.
5.11
Short Floating Point Analog Inputs
The Short Floating Point Analog Inputs property page is selected for editing by clicking Short
Floating Point Analog Inputs in the tree control section of the DNP Settings window. When selected
the Short Floating Point Analog Inputs property page is active.
DNP3 User and Reference Manual
May 9, 2007
56
Short Floating Point Analog Input parameters are set in this property page. Each parameter is
described in the following paragraphs.
The Number of Points displays the number of Short Floating Point Analog Inputs reported by the
RTU. This value will increment with the addition of each configured Short Floating Point Analog
Input point. The maximum number of points is 9999. The maximum number of actual points will
depend on the memory available in the controller.
The Starting Address parameter specifies the DNP address of the first Short Floating Point Analog
Input point.
The Event Reporting Method selection specifies how Short Floating Point Analog Input events are
reported. A Change Of State event is an event object, without time, that is generated when the point
changes state. Only one event is retained in the buffer for each point. If a subsequent event occurs for
a point, the previous event object will be overwritten. The main purpose of this mode is to allow a
master station to efficiently poll for changed data. A Log All Events is event object with absolute
time will be generated when the point changes state. All events will be retained. The main purpose of
this mode is to allow a master station to obtain a complete historical data log. The selections are:
•
Change of State
•
Log All Events
The Event Buffer Size parameter specifies the maximum number of Short Floating Point Analog
Input changes without time events buffered by the RTU. The buffer holds all Short Floating Point
Analog Input events, regardless of the class to which they are assigned. If the buffer fills to 90
percent the RTU will send a buffer overflow event to the master station. If the buffer is completely
full the RTU will lose the oldest events and retain the newest. The Event Buffer size should be at
least equivalent to the number of Short Floating Point Analog Inputs defined as Change of State
type. That will allow all Short Floating Point Analog Inputs to exceed the deadband simultaneously
without losing any events. The value of this parameter is dependent on how often Short Floating
DNP3 User and Reference Manual
May 9, 2007
57
Point Analog Input events occur and the rate at which the events are reported to the master station.
The valid values for this parameter are 0 - 65535. Default value is 16.
For SCADAPack 32 and SCADAPack 32P controllers analog input events are processed by the DNP
driver at a rate of 100 events every 100 ms. If more than 100 analog input events need to be
processed they are processed sequentially in blocks of 100 until all events are processed. This allows
the processing of 1000 analog input events per second.
For SCADASense Series of controllers, SCADAPack 100, SCADAPack LP, SCADAPack and
Micro16 controllers analog input events are processed by the DNP driver at a rate of 20 events every
100 ms. If more than 20 analog input events need to be processed they are processed sequentially in
blocks of 20 until all events are processed. This allows the processing of 200 analog input events per
second.
The Word Order selection specifies the word order of the 32-bit value. The selections are:
•
TelePACE / ISaGRAF (MSW First)
Most Significant Word in first register.
•
Reverse (LSW First)
Least Significant Word in first register.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.11.1
Adding Short Floating Point Analog Inputs
Short Floating Point Analog Inputs are added to the DNP configuration using the 16-Bit Analog
Input property page. To add a Short Floating Point Analog Input:
•
Select Short Floating Point Analog Input in the tree control section of the DNP Settings
window.
•
Click the Add button in the Short Floating Point Analog Inputs property page.
•
The Short Floating Point Analog Input property page is now displayed.
•
Edit the Short Floating Point Analog Input parameters as required and then click the Add button.
As Short Floating Point Analog Inputs are defined they are added as leaves to the Short Floating
Point Analog Inputs branch of the tree control. When Short Floating Point Analog Inputs are defined
the Short Floating Point Analog Inputs branch will display a collapse / expand control to the left of
the branch. Click this control to display all defined Short Floating Point Analog Inputs.
DNP3 User and Reference Manual
May 9, 2007
58
The Short Floating Point Analog Input parameters are described in the following paragraphs.
The DNP Address window displays the DNP Short Floating Point Analog Input address of the
point. Each Short Floating Point Analog Input is assigned a DNP address as they are defined. The
DNP point address starts at the value set in the Short Floating Point Analog Input configuration
dialog and increments by one with each defined Short Floating Point Analog Input.
The Modbus Address parameter specifies the Modbus addresses of the Short Floating Point Analog
Input assigned to the DNP Address. Short Floating Point Analog Inputs use two consecutive Modbus
registers for each assigned DNP Address, the address that is entered in this box and the next
consecutive Modbus register. The SCADAPack and Micro16 controllers use Modbus addressing for
all analog inputs. Refer to the I/O Database Registers section of the TelePACE Ladder Logic
Reference and User Manual for complete information on analog input addressing in the
SCADAPack and Micro16 controllers. Valid Modbus addresses are:
•
30001 through 39998
•
40001 through 49998
The Class of Event Object parameter specifies the event object class the Short Floating Point Analog
Input is assigned. If Unsolicited reporting is not required for a DNP point, it is recommended to set
its Class 0 or None. The selections are:
•
None
•
Class 1
•
Class 2
•
Class 3
The Deadband parameter specifies whether the RTU generates events. The value entered is the
minimum number of counts that the Short Floating Point Analog Input must change since it was last
DNP3 User and Reference Manual
May 9, 2007
59
reported. Setting this value to zero disables generating events for the Short Floating Point Analog
Inputs.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the Short Floating Point Analog Input parameters and close the DNP
Settings dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current Short Floating Point Analog Input to the DNP configuration.
Click the Copy button to copy the current Short Floating Point Analog Input parameters to the next
DNP Address.
Click the Delete button to delete the current Short Floating Point Analog Input.
Click the Move Up button to move the current Short Floating Point Analog Input up one position in
the tree control branch.
Click the Move Down button to move the current Short Floating Point Analog Input down one
position in the tree control branch.
5.12
16-Bit Analog Outputs Configuration
The 16-Bit Analog Outputs property page is selected for editing by clicking 16-Bit Analog Outputs
in the tree control section of the DNP Settings window. When selected the 16-Bit Analog Outputs
property page is active.
16-Bit Analog Outputs parameters are viewed in this property page.
DNP3 User and Reference Manual
May 9, 2007
60
The Number of Points displays the number of 16-Bit Analog Outputs reported by this RTU. This
value will increment with the addition of each configured 16-Bit Analog Input point. The maximum
number of points is 9999. The maximum number of actual points will depend on the memory
available in the controller.
The Starting Address parameter specifies the DNP address of the first 16-bit Analog Output point.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.12.1
Adding 16-Bit Analog Outputs
16-Bit Analog Outputs are added to the DNP configuration using the 16-Bit Analog Outputs
property page. To add a 16-Bit Analog Output:
•
Select 16-Bit Analog Outputs in the tree control section of the DNP Settings window.
•
Click the Add button in the 16-Bit Analog Outputs property page.
•
The 16-Bit Analog Output property page is now displayed.
•
Edit the 16-Bit Analog Outputs parameters as required and then click the Add button.
As 16-Bit Analog Outputs are defined they are added as leaves to the 16-Bit Analog Output branch
of the tree control. When 16-Bit Analog Outputs are defined the 16-Bit Analog Outputs branch will
display a collapse / expand control to the left of the branch. Click this control to display all defined
16-Bit Analog Outputs.
The 16-Bit Analog Outputs parameters are described in the following paragraphs.
The DNP Address window displays the DNP 16-Bit Analog Output address of the point. Each 16Bit Analog Output is assigned a DNP address as they are defined. The DNP point address starts at
DNP3 User and Reference Manual
May 9, 2007
61
the value set in the 16-bit Analog Output configuration dialog and increments by one with each
defined 16-Bit Analog Output.
The Modbus Address parameter specifies the Modbus address of the 16-Bit Analog Output assigned
to the DNP Address. The SCADAPack and Micro16 controllers use Modbus addressing for all
analog outputs. Refer to the I/O Database Registers section of the TelePACE Ladder Logic
Reference and User Manual for complete information on analog output addressing in the
SCADAPack and Micro16 controllers. Valid Modbus addresses are:
•
40001 through 49999
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the 16-Bit Analog Output parameters and close the DNP Settings
dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current 16-Bit Analog Output to the DNP configuration.
Click the Copy button to copy the current 16-Bit Analog Output parameters to the next DNP
Address.
Click the Delete button to delete the current 16-Bit Analog Output.
Click the Move Up button to move the current 16-Bit Analog Output up one position in the tree
control branch.
Click the Move Down button to move the current 16-Bit Analog Output down one position in the
tree control branch.
5.13
32-Bit Analog Outputs Configuration
The 32-Bit Analog Outputs property page is selected for editing by clicking 32-Bit Analog Outputs
in the tree control section of the DNP Settings window. When selected the 32-Bit Analog Outputs
property page is active.
DNP3 User and Reference Manual
May 9, 2007
62
32-Bit Analog Outputs parameters are viewed in this property page.
The Number of Points displays the number of 32-Bit Analog Outputs reported by this RTU. This
value will increment with the addition of each configured 32-Bit Analog Output point. The
maximum number of points is 9999. The maximum number of actual points will depend on the
memory available in the controller.
The Starting Address parameter specifies the DNP address of the first 16-bit Analog Output point.
The Word Order selection specifies the word order of the 32-bit value. The selections are:
•
TelePACE Least Significant Word in first register.
•
ISaGRAF Most Significant Word in first register.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.13.1
Adding 32-Bit Analog Outputs
32-Bit Analog Outputs are added to the DNP configuration using the 32-Bit Analog Outputs
property page. To add a 32-Bit Analog Output:
•
Select 32-Bit Analog Outputs in the tree control section of the DNP Settings window.
•
Click the Add button in the 16-Bit Analog Outputs property page.
•
The 32-Bit Analog Output property page is now displayed.
•
Edit the 32-Bit Analog Outputs parameters as required and then click the Add button.
DNP3 User and Reference Manual
May 9, 2007
63
As 32-Bit Analog Outputs are defined they are added as leaves to the Binary Inputs branch of the
tree control. When 32-Bit Analog Outputs are defined the 32-Bit Analog Outputs branch will display
a collapse / expand control to the left of the branch. Click this control to display all defined 32-Bit
Analog Outputs.
The 32-Bit Analog Outputs parameters are described in the following paragraphs.
The DNP Address window displays the DNP 32-Bit Analog Output address of the point. Each 16Bit Analog Output is assigned a DNP address s they are defined. The DNP point address starts at the
value set in the 32-bit Analog Output configuration dialog and increments by one with each defined
32-Bit Analog Output.
The Modbus Address parameter specifies the Modbus address of the 32-Bit Analog Output assigned
to the DNP Address. 32-Bit Analog Outputs use two consecutive Modbus registers for each assigned
DNP Address, the address that is entered in this box and the next consecutive Modbus register. The
SCADAPack and Micro16 controllers use Modbus addressing for all analog outputs. Refer to the I/O
Database Registers section of the TelePACE Ladder Logic Reference and User Manual for
complete information on analog output addressing in the SCADAPack and Micro16 controllers.
Valid Modbus addresses are:
•
40001 through 49998
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the 16-Bit Analog Output parameters and close the DNP Settings
dialog.
Click the Cancel button to close the dialog without saving any changes.
DNP3 User and Reference Manual
May 9, 2007
64
Click the Add button to add the current 32-Bit Analog Output to the DNP configuration.
Click the Copy button to copy the current 32-Bit Analog Output parameters to the next DNP
Address.
Click the Delete button to delete the current 32-Bit Analog Output.
Click the Move Up button to move the current 32-Bit Analog Output up one position in the tree
control branch.
Click the Move Down button to move the current 32-Bit Analog Output down one position in the
tree control branch.
5.14
Short Floating Point Analog Outputs
The Short Floating Point Analog Outputs property page is selected for editing by clicking Short
Floating Point Analog Outputs in the tree control section of the DNP Settings window. When
selected the Short Floating Point Analog Outputs property page is active.
Short Floating Point Analog Output parameters are set in this property page. Each parameter is
described in the following paragraphs.
The Number of Points displays the number of Short Floating Point Analog Outputs reported by the
RTU. This value will increment with the addition of each configured Short Floating Point Analog
Input point. The maximum number of points is 9999. The maximum number of actual points will
depend on the memory available in the controller.
The Starting Address parameter specifies the DNP address of the first Short Floating Point Analog
Output point.
The Word Order selection specifies the word order of the 32-bit value. The selections are:
DNP3 User and Reference Manual
May 9, 2007
65
•
TelePACE / ISaGRAF (MSW First)
Most Significant Word in first register.
•
Reverse (LSW First)
Least Significant Word in first register.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.14.1
Adding Short Floating Point Analog Outputs
Short Floating Point Analog Outputs are added to the DNP configuration using the Short Floating
Point Analog Output property page. To add a Short Floating Point Analog Output:
•
Select Short Floating Point Analog Output in the tree control section of the DNP Settings
window.
•
Click the Add button in the Short Floating Point Analog Inputs property page.
•
The Short Floating Point Analog Output property page is now displayed.
•
Edit the Short Floating Point Analog Output parameters as required and then click the Add
button.
As Short Floating Point Analog Outputs are defined they are added as leaves to the Short Floating
Point Analog Outputs branch of the tree control. When Short Floating Point Analog Outputs are
defined the Short Floating Point Analog Outputs branch will display a collapse / expand control to
the left of the branch. Click this control to display all defined Short Floating Point Analog Outputs.
The Short Floating Point Analog Output parameters are described in the following paragraphs.
The DNP Address window displays the DNP Short Floating Point Analog Output address of the
point. Each Short Floating Point Analog Output is assigned a DNP address as they are defined. The
DNP3 User and Reference Manual
May 9, 2007
66
DNP point address starts at the value set in the Short Floating Point Analog Output configuration
dialog and increments by one with each defined Short Floating Point Analog Output.
The Modbus Address parameter specifies the Modbus addresses of the Short Floating Point Analog
Output assigned to the DNP Address. Short Floating Point Analog Outputs use two consecutive
Modbus registers for each assigned DNP Address, the address that is entered in this box and the next
consecutive Modbus register. The SCADAPack and Micro16 controllers use Modbus addressing for
all analog inputs. Refer to the I/O Database Registers section of the TelePACE Ladder Logic
Reference and User Manual for complete information on analog input addressing in the
SCADAPack and Micro16 controllers. Valid Modbus addresses are:
•
30001 through 39998
•
40001 through 49998
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the Short Floating Point Analog Input parameters and close the DNP
Settings dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current Short Floating Point Analog Input to the DNP configuration.
Click the Copy button to copy the current Short Floating Point Analog Input parameters to the next
DNP Address.
Click the Delete button to delete the current Short Floating Point Analog Input.
Click the Move Up button to move the current Short Floating Point Analog Input up one position in
the tree control branch.
Click the Move Down button to move the current Short Floating Point Analog Input down one
position in the tree control branch.
5.15
16–Bit Counter Inputs Configuration
The 16-Bit Counter Inputs property page is selected for editing by clicking 16-Bit Counter Inputs in
the tree control section of the DNP Settings window. When selected the 16-Bit Counter Inputs
property page is active.
DNP3 User and Reference Manual
May 9, 2007
67
16-Bit Counter Inputs parameters are set in this property page. Each parameter is described in the
following paragraphs.
The Number of Points displays the number of 16-Bit Counter Inputs reported by the RTU. This
value will increment with the addition of each configured 16-Bit Counter Inputs point. The
maximum number of points is 9999. The maximum number of actual points will depend on the
memory available in the controller.
The Starting Address parameter specifies the DNP address of the first 16-Bit Counter Input point.
The Event Reporting Method selection specifies how 16-Bit Counter Input events are reported. A
Change Of State event is an event object, without time, that is generated when the point changes
state. Only one event is retained in the buffer for each point. If a subsequent event occurs for a point,
the previous event object will be overwritten. The main purpose of this mode is to allow a master
station to efficiently poll for changed data. A Log All Events is event object with absolute time will
be generated when the point changes state. All events will be retained. The main purpose of this
mode is to allow a master station to obtain a complete historical data log. The selections are:
•
Change of State
•
Log All Events
The Event Buffer Size parameter specifies the maximum number of 16-Bit Counter Input change
without time events buffered by the RTU. The buffer holds all 16-Bit Counter Input events,
regardless of the class to which they are assigned. If the buffer fills to 90 percent the RTU will send a
buffer overflow event to the master station. If the buffer is completely full the RTU will lose the
oldest events and retain the newest. The Event Buffer size should be at least equivalent to the
number of 16-Bit Analog Inputs defined as Change of State type. That will allow all 16-Bit Counter
Inputs to exceed the threshold simultaneously without losing any events. The value of this parameter
is dependent on how often 16-Bit Counter Input events occur and the rate at which the events are
reported to the master station. The valid values for this parameter are 0 - 65535. Default value is 16.
DNP3 User and Reference Manual
May 9, 2007
68
For SCADAPack 32 and SCADAPack 32P controllers counter input events are processed by the
DNP driver at a rate of 100 events every 100 ms. If more than 100 counter input events need to be
processed they are processed sequentially in blocks of 100 until all events are processed. This allows
the processing of 1000 counter input events per second.
For SCADASense Series of controllers, SCADAPack 100, SCADAPack LP, SCADAPack and
Micro16 controllers counter input events are processed by the DNP driver at a rate of 20 events
every 100 ms. If more than 20 counter input events need to be processed they are processed
sequentially in blocks of 20 until all events are processed. This allows the processing of 200 counter
input events per second.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.15.1
Adding 16-Bit Counter Inputs
16-Bit Counter Inputs are added to the DNP configuration using the 16-Bit Counter Inputs property
page. To add a 16-Bit Counter Input:
•
Select 16-Bit Counter Inputs in the tree control section of the DNP Settings window.
•
Click the Add button in the 16-Bit Counter Inputs property page.
•
The 16-Bit Counter Input property page is now displayed.
•
Edit the 16-Bit Counter Inputs parameters as required and then click the Add button.
As 16-Bit Counter Inputs are defined they are added as leaves to the 16-Bit Counter Inputs branch of
the tree control. When 16-Bit Counter Inputs are defined the 16-Bit Counter Inputs branch will
display a collapse / expand control to the left of the branch. Click this control to display all defined
16-Bit Counter Inputs.
DNP3 User and Reference Manual
May 9, 2007
69
The 16-Bit Counter Input parameters are described in the following paragraphs.
The DNP Address window displays the DNP 16-Bit Counter Input address of the point. Each 16-Bit
Counter Input is assigned a DNP address s they are defined. The DNP point address starts at the
value set in the 16-Bit Counter Input configuration dialog and increments by one with each defined
16-Bit Counter Input.
The Modbus Address parameter specifies the Modbus address of the 16-Bit Counter Input assigned
to the DNP Address. The SCADAPack and Micro16 controllers use Modbus addressing for all
counter inputs. Refer to the I/O Database Registers section of the TelePACE Ladder Logic
Reference and User Manual for complete information on analog input addressing in the
SCADAPack and Micro16 controllers. Valid Modbus addresses are:
•
30001 through 39999
•
40001 through 49999
The Class of Event Object parameter specifies the event object class the 16-Bit Counter Input is
assigned. If Unsolicited reporting is not required for a DNP point, it is recommended to set its Class
0 or None. The selections are:
•
None
•
Class 1
•
Class 2
•
Class 3
The Threshold parameter specifies whether the RTU generates events. The value entered is the
minimum number of counts that the 16-Bit Counter Input must change since it was last reported.
DNP3 User and Reference Manual
May 9, 2007
70
Setting this value to zero disables generating events for the 16-Bit Counter Input point. Valid
deadband values are 0 to 65535.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the 16-Bit Analog Counter parameters and close the DNP Settings
dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current 16-Bit Analog Input to the DNP configuration.
Click the Copy button to copy the current 16-Bit Analog Input parameters to the next DNP Address.
Click the Delete button to delete the current 16-Bit Analog Input.
Click the Move Up button to move the current 16-Bit Analog Input up one position in the tree
control branch.
Click the Move Down button to move the current 16-Bit Analog Input down one position in the tree
control branch.
5.16
32-Bit Counter Inputs Configuration
The 32-Bit Counter Inputs property page is selected for editing by clicking 32-Bit Counter Inputs in
the tree control section of the DNP Settings window. When selected the 32-Bit Counter Inputs
property page is active.
32-Bit Counter Inputs parameters are set in this property page. Each parameter is described in the
following paragraphs.
DNP3 User and Reference Manual
May 9, 2007
71
The Number of Points displays the number of 32-Bit Counter Inputs reported by the RTU. This
value will increment with the addition of each configured 32-Bit Counter Inputs point. The
maximum number of points is 9999. The maximum number of actual points will depend on the
memory available in the controller.
The Starting Address parameter specifies the DNP address of the first 32-Bit Counter Input point.
The Event Reporting Method selection specifies how 32-Bit Counter Input events are reported. A
Change Of State event is an event object, without time, that is generated when the point changes
state. Only one event is retained in the buffer for each point. If a subsequent event occurs for a point,
the previous event object will be overwritten. The main purpose of this mode is to allow a master
station to efficiently poll for changed data. A Log All Events is event object with absolute time will
be generated when the point changes state. All events will be retained. The main purpose of this
mode is to allow a master station to obtain a complete historical data log. The selections are:
•
Change of State
•
Log All Events
The Event Buffer Size parameter specifies the maximum number of 32-Bit Counter Input change
without time events buffered by the RTU. The buffer holds all 32-Bit Counter Input events,
regardless of the class to which they are assigned. If the buffer fills to 90 percent the RTU will send a
buffer overflow event to the master station. If the buffer is completely full the RTU will lose the
oldest events and retain the newest. The Event Buffer size should be at least equivalent to the
number of 32-Bit Counter Inputs defined as Change of State type. That will allow all 32-Bit Counter
Inputs to exceed the deadband simultaneously without losing any events. The value of this parameter
is dependent on how often 32-Bit Analog Input events occur and the rate at which the events are
reported to the master station. The valid values for this parameter are 0 - 65535. Default value is 16.
For SCADAPack 32 and SCADAPack 32P controllers counter input events are processed by the
DNP driver at a rate of 100 events every 100 ms. If more than 100 counter input events need to be
processed they are processed sequentially in blocks of 100 until all events are processed. This allows
the processing of 1000 counter input events per second.
For SCADASense Series of controllers, SCADAPack 100, SCADAPack LP, SCADAPack and
Micro16 controllers counter input events are processed by the DNP driver at a rate of 20 events
every 100 ms. If more than 20 counter input events need to be processed they are processed
sequentially in blocks of 20 until all events are processed. This allows the processing of 200 counter
input events per second.
The Word Order selection specifies the word order of the 32-bit value. The selections are:
•
TelePACE Least Significant Word in first register.
•
ISaGRAF Most Significant Word in first register.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
5.16.1
Adding 32-Bit Counter Inputs
32-Bit Counter Inputs are added to the DNP configuration using the 16-Bit Counter Input property
page. To add a 32-Bit Analog Input:
•
Select 32-Bit Counter Inputs in the tree control section of the DNP Settings window.
•
Click the Add button in the 32-Bit Counter Inputs property page.
DNP3 User and Reference Manual
May 9, 2007
72
•
The 32-Bit Counter Input property page is now displayed.
•
Edit the 32-Bit Counter Input parameters as required and then click the Add button.
As 32-Bit Counter Inputs are defined they are added as leaves to the 32-Bit Counter Inputs branch of
the tree control. When 32-Bit Counter Inputs are defined the 32-Bit Counter Inputs branch will
display a collapse / expand control to the left of the branch. Click this control to display all defined
32-Bit Counter Inputs.
The 32-Bit Counter Input parameters are described in the following paragraphs.
The DNP Address window displays the DNP 32-Bit Counter Input address of the point. Each 32-Bit
Counter Input is assigned a DNP address as they are defined. The DNP point address starts at the
value set in the 32-Bit Counter Input configuration dialog and increments by one with each defined
32-Bit Counter Input.
The Modbus Address parameter specifies the Modbus addresses of the 32-Bit Counter Input
assigned to the DNP Address. 32-Bit Counter Inputs use two consecutive Modbus registers for each
assigned DNP Address, the address that is entered in this box and the next consecutive Modbus
register. The SCADAPack and Micro16 controllers use Modbus addressing for all counter inputs.
Refer to the I/O Database Registers section of the TelePACE Ladder Logic Reference and User
Manual for complete information on analog input addressing in the SCADAPack and Micro16
controllers. Valid Modbus addresses are:
•
30001 through 39998
•
40001 through 49998
The Class of Event Object parameter specifies the event object class the 32-Bit Counter Input is
assigned. If Unsolicited reporting is not required for a DNP point, it is recommended to set its Class
0 or None. The selections are:
DNP3 User and Reference Manual
May 9, 2007
73
•
None
•
Class 1
•
Class 2
•
Class 3
The Threshold parameter specifies whether the RTU generates events. The value entered is the
minimum number of counts that the 32-Bit Counter Input must change since it was last reported.
Setting this value to zero disables generating events for the 32-Bit Counter Input point. Valid
threshold values are 0 to 4,294,967,295.
The Allow Duplicate Modbus Addresses checkbox determines if the Modbus I/O database
addresses assigned to the DNP data points must be unique. Check this box if you want to allow more
than one point to use the same Modbus address.
Click the OK button to accept the 32-Bit Counter Input parameters and close the DNP Settings
dialog.
Click the Cancel button to close the dialog without saving any changes.
Click the Add button to add the current 32-Bit Counter Input to the DNP configuration.
Click the Copy button to copy the current 32-Bit Counter Input parameters to the next DNP Address.
Click the Delete button to delete the current 32-Bit Counter Input.
Click the Move Up button to move the current 32-Bit Counter Input up one position in the tree
control branch.
Click the Move Down button to move the current 32-Bit Counter Input down one position in the
tree control branch.
DNP3 User and Reference Manual
May 9, 2007
74
6
DNP Diagnostics
DNP Diagnostics provide Master station and Outstation DNP diagnostics. The diagnostics provide
detailed information on the status of DNP communication and DNP data points. This information is
useful when debugging DNP station and network problems that may arise.
DNP diagnostics are available for local DNP information using the DNP Status command.
•
For TelePACE applications select Controller >> DNP Status from the menu bar. See the
section DNP Status for information on DNP Status diagnostics.
•
For ISaGRAF applications select Tools >> Controller >> DNP Status from the program
window menu bar. See the section DNP Status for information on DNP Status diagnostics.
SCADAPack 32 controllers support DNP master operations. DNP diagnostics are available for
master stations using the DNP Master Status command.
•
For TelePACE applications select Controller >> DNP Master Status from the menu bar. See
the section DNP Master Status for information on DNP Master Status diagnostics.
•
For ISaGRAF applications select Tools >> Controller >> DNP Master Status from the
program window menu bar. See the section 4.2- DNP Master Status for information on DNP
Master Status diagnostics.
DNP Diagnostics require firmware version 2.20 or newer for SCADAPack controllers and firmware
version 1.50 or newer for SCADAPack 32 controllers. When an attempt is made to select the DNP
Status or DNP Master Status command for controllers with firmware that does not support the
commands an error message is displayed. An example of the error message is shown below.
To enable the use of DNP diagnostics you will need to upgrade the firmware in the controller to the
newer version.
6.1
DNP Status
When the DNP Status command is selected the DNP Status dialog is displayed. This dialog shows
the run-time DNP diagnostics and current data values for the local DNP points.
The DNP Status dialog has a number of selectable tabs and opens with the Overview tab selected.
The following tabs are displayed.
•
Overview
•
Binary In (binary inputs information)
•
Binary Out (binary outputs information)
•
AIN-16 (16-bit analog inputs information)
•
AIN-32 (32-bit analog inputs information)
•
AIN-Float (short float analog inputs information)
DNP3 User and Reference Manual
May 9, 2007
75
•
AOUT-16 (16-bit analog outputs information)
•
AOUT-32 (32-bit analog outputs information)
•
AOUT-Float (short float analog outputs information)
•
Counter-16 (16-bit counter inputs information)
•
Counter-32 (32-bit counter inputs information)
Clicking on any tab opens the tab and displays the selected information.
6.1.1
Overview Tab
The Overview Tab displays the run-time diagnostics for the local DNP station. The Overview
display is divided into five areas of diagnostic information: DNP Status, Internal Indications,
Communication Statistics, Last Message and Event Buffer. Each of these is explained in the
following paragraphs.
The DNP Status window provides information on the status of the DNP protocol running in the
controller. Depending on the status the window may contain the following text.
•
Enabled or Disabled indicates whether the controller firmware supports DNP protocol.
•
Configured or Not Configured indicates whether the controller has been configured with DNP
protocol on at least one communications port.
•
Running or Not Running indicates whether the DNP tasks are running in the controller.
The Internal Indications window displays the current state of the DNP internal indications (IIN)
flags in the controller. For a detailed description of the IIN flags see the section Internal Indication
DNP3 User and Reference Manual
May 9, 2007
76
(IIN) Flags section of this manual. Note that bits 0 – 7 (the first octet) are displayed on the left, then
bits 8 - 15 (second octet) on the right.
The Communication Statistics window displays the message statistics for each DNP
communication port. The statistics include the total number of messages transmitted and received
and the total number of successes, failures, and failures since last success (which will only be
updated for messages sent by this controller) for each communication port. The counters increment
whenever a new DNP message is sent or received on the port, and roll over after 65535 messages.
•
Click the Reset button to reset the counters to zero.
The Last Message window displays information about the most recent DNP message. The
information is updated each time a new message is received or transmitted. The Last Message
window contains the following information.
•
Direction displays whether the message was received or transmitted.
•
Time displays the time at which the message was received or sent.
•
Port displays which communication port was used for the message.
•
Source displays the source DNP station address for the message.
•
Dest displays the destination DNP station address for the message.
•
Length displays the message length in bytes.
•
Link Func displays the Link Layer function code.
•
Appl Func displays the Application Layer function code.
•
IIN displays the Internal indications received with the last message
The Event Buffers window displays the number of events in each type of event buffer and the
allocated buffer size. The event buffers displayed are:
•
Binary In (binary inputs)
•
AIN-16 (16-bit analog inputs)
•
AIN-32 (32-bit analog inputs)
•
AIN-Float (floating point analog inputs)
•
Counter-16 (16-bit counter inputs)
•
Counter-32 (32-bit counter inputs)
•
Class 1 (class 1 events)
•
Class 2 (class 2 events)
•
Class 3 (class 3 events)
6.1.2
Point Status Tabs
The point status tabs display the state of each point of the selected type in the controller. The
following tabs are displayed.
•
Binary In (binary inputs information)
•
Binary Out (binary outputs information)
DNP3 User and Reference Manual
May 9, 2007
77
•
AIN-16 (16-bit analog inputs information)
•
AIN-32 (32-bit analog inputs information)
•
AIN-Float (short float analog inputs information)
•
AOUT-16 (16-bit analog outputs information)
•
AOUT-32 (32-bit analog outputs information)
•
AOUT-Float (short float analog outputs information)
•
Counter-16 (16-bit counter inputs information)
•
Counter-32 (32-bit counter inputs information)
Each of the tabs displays information in the same format. The example below shows the appearance
of the binary input page.
The DNP Address column shows the DNP address of the point.
The Modbus Address column shows the Modbus register address of the point.
The Value column shows the value of the point. Binary points are shown as OFF or ON. Numeric
points show the numeric value of the point.
6.2
DNP Master Status
When the DNP Master Status command is selected the DNP Master Status dialog is displayed. This
dialog shows the run-time DNP diagnostics and status of the DNP outstations and current data values
for the DNP points in these outstations.
DNP3 User and Reference Manual
May 9, 2007
78
The DNP Master Status dialog has a number of selectable tabs and opens with the All Stations tab
selected. The following tabs are displayed.
•
All Stations
•
Remote Overview
•
Binary In (binary inputs information)
•
Binary Out (binary outputs information)
•
AIN-16 (16-bit analog inputs information)
•
AIN-32 (32-bit analog inputs information)
•
AIN-Float (short float analog inputs information)
•
AOUT-16 (16-bit analog outputs information)
•
AOUT-32 (32-bit analog outputs information)
•
AOUT-Float (short float analog outputs information)
•
Counter-16 (16-bit counter inputs information)
•
Counter-32 (32-bit counter inputs information)
6.2.1
All Stations Tab
The All Stations tab displays the run-time communications diagnostics for all outstations polled by
the master or outstations reporting unsolicited data to the master.
The Communication Statistics window displays a list of all outstations and the communication
statistics for each station in the list. The statistics counters increment whenever a new DNP message
is sent or received, and roll over after 65535 messages. The following statistics are displayed.
•
DNP Address displays the DNP address of the outstation.
DNP3 User and Reference Manual
May 9, 2007
79
•
Successes display the number of successful message transactions between this master and the
corresponding remote station. This number includes master polls to the remote station and
unsolicited responses from the outstation.
•
Fails displays the number of failed message transactions between this master and the
corresponding remote station. This counter increments by 1 for a failed message transaction
irrespective of the number of application layer retries.
•
FailsNew displays the number failed message transactions between this master and the
corresponding remote station since the last successful poll.
•
Msgs Rx displays the number of DNP packets (frames) received from the outstation station. This
number includes frames containing unsolicited responses from the outstation.
•
Last Rx Msg Time displays the time the last DNP packet (frame) was received from the
outstation.
•
Msgs Tx displays the number of DNP packets (frames) sent to the outstation.
•
Last Tx Msg Time displays the time the last DNP packet (frame) was sent to the outstation.
Note:
6.2.2
The Msgs Tx and Msgs Rx counters could be greater than or equal to the Successes and
Fails counters.
Remote Overview Tab
The Remote Overview tab displays the run-time diagnostics and current data values for a selected
remote station. The data shown is from the image of the data in the master station.
The Remote Station window is where the DNP address of the remote station is entered. When the
Remote station field is changed all data fields on this tab and the following I/O tabs are updated with
the values for the newly selected Remote Station.
DNP3 User and Reference Manual
May 9, 2007
80
The Internal Indications window displays the current state of the DNP internal indications (IIN)
flags for the selected remote station. For a detailed description of the IIN flags see the section
Internal Indication (IIN) Flags section of this manual.
The Communication Statistics window displays communication statistics for the remote station
selected. The statistics counters increment whenever a new DNP message is sent or received, and roll
over after 65535 messages. The following statistics are displayed.
•
Successes displays the number of successful messages received in response to master polls sent
to the station. This number includes unsolicited responses from the outstation.
•
Fails displays the number of failed or no responses to master polls sent to the outstation.
•
FailsNew displays the number failed or no responses to master polls sent to the outstation since
the last successful poll.
•
Msgs Rx displays the number of messages received from the outstation station. This number
includes unsolicited responses from the outstation.
•
Last Rx Msg Time displays the time the last message was received from the outstation.
•
Msgs Tx displays the number of messages sent to the outstation station.
•
Last Tx Msg Time displays the time the last message was sent to the outstation.
Click Reset to reset the counters to zero.
Event Buffers shows the number of events in each type of event buffer and the allocated buffer size.
The buffers shown are for binary inputs, 16-bit analog inputs, 32-bit analog inputs, Floating point
analog inputs, 16-bit counter inputs, and 32-bit counter inputs, and Class 1, 2, and 3 events.
The Event Buffers window displays the number of events in each type of event buffer and the
allocated buffer size for the selected remote station. The event buffers displayed are:
•
Binary In (binary inputs)
•
AIN-16 (16-bit analog inputs)
•
AIN-32 (32-bit analog inputs)
•
AIN-Float (floating point analog inputs)
•
Counter-16 (16-bit counter inputs)
•
Counter-32 (32-bit counter inputs)
•
Class 1 (class 1 events)
•
Class 2 (class 2 events)
•
Class 3 (class 3 events)
Note:
Due to a limitation of the DNP3 protocol, an Unsolicited message from an outstation is not
capable of including information stating which data class generated the message. As a result,
all Unsolicited events when received by the master will be counted as Class 1 events. Events
which are polled by the master, however, do contain class information and will be counted in
the Event Buffer for the appropriate class.
DNP3 User and Reference Manual
May 9, 2007
81
6.2.3
Remote Point Status Tabs
The point status tabs show the state of each point of the selected type in the remote station selected
on the Remote Overview tab. The values shown are from the image of the remote station in the
master station.
Note:
Class 0 polling of an outstation must be enabled in the master in order to allow that
outstation’s DNP points to be listed on these tabs. This is the only way for the master to
retrieve a complete list of all points in an outstation.
The example below shows the appearance of the Binary In tab.
The DNP Address column shows the DNP address of the point.
The Modbus Address column shows the Modbus register address of the point. This is only relevant
for points that have an address mapping in the master station. For points that have an address
mapping, this will show the Modbus register address of the point. For points which do not have an
address mapping, this will show ‘---‘.
The Value column shows the value of the point. Binary points are shows as OFF or ON. Numeric
points show the numeric value of the point.
DNP3 User and Reference Manual
May 9, 2007
82
7
DNP Device Profile Document - Master
DNP v3.00
DEVICE PROFILE DOCUMENT
Vendor Name: Control Microsystems Inc.
Device Name: SCADAPack controllers
Highest DNP Level Supported:
Device Function:
For Requests
g Master
2
Slave
For Responses 2
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels
Supported (the complete list is described in the attached table):
•
Function code 14 (warm restart)
•
Function code 20 (Enable Unsolicited Messages) for class 1, 2, 3 objects only.
•
Function code 21 (Disable Unsolicited Messages) for class 1, 2, 3 objects only.
•
Object 41, variation 1 (32-bit analog output block)
Maximum Data Link Frame Size (octets):
Maximum Application Fragment Size (octets):
Transmitted
Received
Transmitted
Received
292
(must be 292)
DNP3 User and Reference Manual
May 9, 2007
2048
2048
83
Maximum Data Link Re-tries:
g
Maximum Application Layer Re-tries:
None
Fixed at
Configurable, range 0 to 255
g
None
Configurable, range 0 to 255
Requires Data Link Layer Confirmation:
Never
Always
Sometimes
If 'Sometimes', when?
g Configurable for Always or Never
Requires Application Layer Confirmation:
Never
Always (not recommended)
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Sometimes
If 'Sometimes', when?
______________________________________________
gConfigurable for always or only when Reporting Event Data and Unsolicited Messages
Timeouts while waiting for:
Data Link Confirm
Complete Appl. Fragment
Application Confirm
Complete Appl. Response
None
None
None
None
Fixed at _________
Fixed at _________
Fixed at _________
Fixed at _________
Variable
Variable
Variable
Variable
g Configurable
g Configurable
g Configurable
g Configurable
Others __________________________________________________________________________
Sends/Executes Control Operations:
WRITE Binary Outputs
SELECT/OPERATE
DIRECT OPERATE
DIRECT OPERATE - NO ACK
Never
Never
Never
Never
Always
Always
Always
Always
Sometimes
Sometimes
Sometimes
Sometimes
g Configurable
g Configurable
g Configurable
g Configurable
Count > 1
Never
Always
Sometimes
g Configurable
DNP3 User and Reference Manual
May 9, 2007
84
Never
Never
Never
Never
Always
Always
Always
Always
Sometimes
Sometimes
Sometimes
Sometimes
g Configurable
g Configurable
g Configurable
g Configurable
g Never
g Never
Always
Always
Sometimes
Sometimes
Configurable
Configurable
Pulse On
Pulse Off
Latch On
Latch Off
Queue
Clear Queue
FILL OUT THE FOLLOWING ITEM FOR MASTER DEVICES ONLY:
Expects Binary Input Change Events:
g
Either time-tagged or non-time-tagged for a single event
Both time-tagged and non-time-tagged for a single event
Configurable (attach explanation)
FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:
Reports Binary Input Change Events when no
specific variation requested:
Never
Only time-tagged
Only non-time-tagged
Configurable to send both, one or the
other (attach explanation)
Sends Unsolicited Responses:
Never
Configurable by class
Only certain objects
Sometimes (attach explanation)
Reports time-tagged Binary Input Change Events
when no specific variation requested:
Never
Binary Input Change With Time
Binary Input Change With Relative Time
Configurable (attach explanation)
Sends Static Data in Unsolicited Responses:
Never
When Device Restarts
When Status Flags Change
No other options are permitted.
g
ENABLE/DISABLE UNSOLICITED
Default Counter Object/Variation:
No Counters Reported
Configurable (attach explanation)
Default Object 20
Default Variation 05
DNP3 User and Reference Manual
May 9, 2007
Counters Roll Over at:
No Counters Reported
Configurable (attach explanation)
16 Bits
32 Bits
85
Point-by-point list attached
Sends Multi-Fragment Responses:
DNP3 User and Reference Manual
May 9, 2007
16 Bits for 16-bit counters
32 Bits for 32-bit counters
Point-by-point list attached
g Yes
No
86
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
1
0
Binary Input - All Variations
1
1
Binary Input
129, 130
00, 01
1
2
Binary Input with Status
129, 130
00, 01
2
0
Binary Input Change - All Variations
1
06,07,08
2
1
Binary Input Change without Time
1
06,07,08
129, 130
17, 28
2
2
Binary Input Change with Time
1
06,07,08
129, 130
17, 28
2
3
Binary Input Change with Relative Time
1
06,07,08
129, 130
17, 28
10
0
Binary Output - All Variations
1
06
10
1
Binary Output
10
2
Binary Output Status
129, 130
00, 01
12
0
Control Block - All Variations
12
1
Control Relay Output Block
129
echo of
request
12
2
Pattern Control Block
12
3
Pattern Mask
20
0
Binary Counter - All Variations
20
1
32-Bit Binary Counter
129, 130
00, 01
20
2
16-Bit Binary Counter
129, 130
00, 01
20
3
32-Bit Delta Counter
20
4
16-Bit Delta Counter
20
5
32-Bit Binary Counter without Flag
129, 130
00, 01
20
6
16-Bit Binary Counter without Flag
129, 130
00, 01
20
7
32-Bit Delta Counter without Flag
DNP3 User and Reference Manual
May 9, 2007
Func
Codes
(dec)
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
3, 4, 5,
6
17, 28
1, 7, 8,
9, 10
06
87
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
20
8
16-Bit Delta Counter without Flag
21
0
Frozen Counter - All Variations
21
1
32-Bit Frozen Counter
129, 130
00, 01
21
2
16-Bit Frozen Counter
129, 130
00, 01
21
3
32-Bit Frozen Delta Counter
21
4
16-Bit Frozen Delta Counter
21
5
32-Bit Frozen Counter with Time of Freeze
21
6
16-Bit Frozen Counter with Time of Freeze
21
7
32-Bit Frozen Delta Counter with Time of
Freeze
21
8
16-Bit Frozen Delta Counter with Time of
Freeze
21
9
32-Bit Frozen Counter without Flag
129, 130
00, 01
21
10
16-Bit Frozen Counter without Flag
129, 130
00, 01
21
11
32-Bit Frozen Delta Counter without Flag
21
12
16-Bit Frozen Delta Counter without Flag
22
0
Counter Change Event - All Variations
22
1
32-Bit Counter Change Event without Time
129, 130
17, 28
22
2
16-Bit Counter Change Event without Time
129, 130
17, 28
22
3
32-Bit Delta Counter Change Event without
Time
22
4
16-Bit Delta Counter Change Event without
Time
22
5
32-Bit Counter Change Event with Time
22
6
16-Bit Counter Change Event with Time
22
7
32-Bit Delta Counter Change Event with Time
22
8
16-Bit Delta Counter Change Event with Time
DNP3 User and Reference Manual
May 9, 2007
Func
Codes
(dec)
1
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
06,07,08
88
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
23
0
Frozen Counter Event - All Variations
23
1
32-Bit Frozen Counter Event without Time
23
2
16-Bit Frozen Counter Event without Time
23
3
32-Bit Frozen Delta Counter Event without Time
23
4
16-Bit Frozen Delta Counter Event without Time
23
5
32-Bit Frozen Counter Event with Time
23
6
16-Bit Frozen Counter Event with Time
23
7
32-Bit Frozen Delta Counter Event with Time
23
8
16-Bit Frozen Delta Counter Event with Time
30
0
Analog Input - All Variations
30
1
32-Bit Analog Input
129, 130
00, 01
30
2
16-Bit Analog Input
129, 130
00, 01
30
3
32-Bit Analog Input without Flag
129, 130
00, 01
30
4
16-Bit Analog Input without Flag
129, 130
00, 01
30
5
Short Floating Point Analog Input
129, 130
00, 01
31
0
Frozen Analog Input - All Variations
31
1
32-Bit Frozen Analog Input
31
2
16-Bit Frozen Analog Input
31
3
32-Bit Frozen Analog Input with Time of Freeze
31
4
16-Bit Frozen Analog Input with Time of Freeze
31
5
32-Bit Frozen Analog Input without Flag
31
6
16-Bit Frozen Analog Input without Flag
32
0
Analog Change Event - All Variations
32
1
32-Bit Analog Change Event without Time
129,130
17,28
32
2
16-Bit Analog Change Event without Time
129,130
17,28
DNP3 User and Reference Manual
May 9, 2007
Func
Codes
(dec)
1
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
06,07,08
89
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
Func
Codes
(dec)
32
3
32-Bit Analog Change Event with Time
129,130
17,28
32
4
16-Bit Analog Change Event with Time
129,130
17,28
32
5
Short Floating Point Analog Change Event
without Time
129,130
17,28
33
0
Frozen Analog Event - All Variations
33
1
32-Bit Frozen Analog Event without Time
33
2
16-Bit Frozen Analog Event without Time
33
3
32-Bit Frozen Analog Event with Time
33
4
16-Bit Frozen Analog Event with Time
40
0
Analog Output Status - All Variations
40
1
32-Bit Analog Output Status
129, 130
00, 01
40
2
16-Bit Analog Output Status
129, 130
00, 01
40
3
Short Floating Point Analog Output Status
129, 130
00, 01
41
0
Analog Output Block - All Variations
41
1
32-Bit Analog Output Block
3, 4, 5,
6
17, 28
129
echo of
request
41
2
16-Bit Analog Output Block
3, 4, 5,
6
17, 28
129
echo of
request
41
3
Short Floating Point Analog Output Block
3, 4, 5,
6
17, 28
129
echo of
request
50
0
Time and Date - All Variations
50
1
Time and Date
2 (see
4.14)
07 where
quantity = 1
50
2
Time and Date with Interval
51
0
Time and Date CTO - All Variations
51
1
Time and Date CTO
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
129, 130
07,
quantity=1
DNP3 User and Reference Manual
May 9, 2007
90
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Obj
Var
51
2
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Func
Codes
(dec)
Qual
Codes
(hex)
Unsynchronized Time and Date CTO
Func
Codes
129, 130
Qual
Codes
(hex)
07,
quantity=1
52
0
Time Delay - All Variations
52
1
Time Delay Coarse
129
07,
quantity=1
52
2
Time Delay Fine
129
07,
quantity=1
60
0
60
1
Class 0 Data
1
06
60
2
Class 1 Data
1
20,21
06,07,08
06
60
3
Class 2 Data
1
20,21
06,07,08
06
60
4
Class 3 Data
1
20,21
06,07,08
06
70
1
File Identifier
80
1
Internal Indications
2
00
index=7
81
1
Storage Object
82
1
Device Profile
83
1
Private Registration Object
83
2
Private Registration Object Descriptor
90
1
Application Identifier
100
1
Short Floating Point
100
2
Long Floating Point
100
3
Extended Floating Point
101
1
Small Packed Binary-Coded Decimal
101
2
Medium Packed Binary-Coded Decimal
DNP3 User and Reference Manual
May 9, 2007
91
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Obj
Var
101
3
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Func
Codes
(dec)
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
Large Packed Binary-Coded Decimal
No Object
13
No Object
14
No Object
23
(see
4.14)
DNP V3.00
TIME SYNCHRONISATION PARAMETERS
This table describes the worst-case time parameters relating to time synchronisation,
as required by DNP Level 2 Certification Procedure section 8.7
PARAMETER
VALUE
Time base drift
+/- 1 minute/month at 25°C
+1 / -3 minutes/month 0 to 50°C
Time base drift over a 10-minute interval
+/- 14 milliseconds at 25°C
+14 / -42 milliseconds 0 to 50°C
Maximum delay measurement error
+/- 100 milliseconds
Maximum internal time reference error when set
from the protocol
+/- 100 milliseconds
Maximum response time
100 milliseconds
DNP3 User and Reference Manual
May 9, 2007
92
8
DNP Device Profile Document - Slave
DNP v3.00
DEVICE PROFILE DOCUMENT
Vendor Name: Control Microsystems Inc.
Device Name: SCADAPack controllers
Highest DNP Level Supported:
For Requests
2
Device Function:
Master
g Slave
For Responses 2
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels
Supported (the complete list is described in the attached table):
Function code 14 (warm restart)
Function code 20 (Enable Unsolicited Messages) for class 1, 2, 3 objects only.
Function code 21 (Disable Unsolicited Messages) for class 1, 2, 3 objects only.
Object 41, variation 1 (32-bit analog output block)
Maximum Data Link Frame Size (octets):
Maximum Application Fragment Size (octets):
Transmitted
Received
Transmitted
Received
292
(must be 292)
DNP3 User and Reference Manual
May 9, 2007
2048
2048
93
Maximum Data Link Re-tries:
g
Maximum Application Layer Re-tries:
None
Fixed at
Configurable, range 0 to 255
g
None
Configurable, range 0 to 255
Requires Data Link Layer Confirmation:
Never
Always
Sometimes
If 'Sometimes', when?
g Configurable for Always or Never
Requires Application Layer Confirmation:
Never
Always (not recommended)
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Sometimes
If 'Sometimes', when?
______________________________________________
gConfigurable for always or only when Reporting Event Data and Unsolicited Messages
Timeouts while waiting for:
Data Link Confirm
Configurable
Complete Appl. Fragment
Application Confirm
Complete Appl. Response
None
None
None
None
Fixed at _________
Fixed at _________
Fixed at _________
Fixed at _________
Variable
Variable
Variable
Variable
g
g Configurable
g Configurable
g Configurable
Others __________________________________________________________________________
Sends/Executes Control Operations:
WRITE Binary Outputs
SELECT/OPERATE
DIRECT OPERATE
DIRECT OPERATE - NO ACK
DNP3 User and Reference Manual
May 9, 2007
Never
Never
Never
Never
Always
Always
Always
Always
Sometimes
Sometimes
Sometimes
Sometimes
g Configurable
g Configurable
g Configurable
g Configurable
94
Never
Never
Never
Never
Never
Always
Always
Always
Always
Always
Sometimes
Sometimes
Sometimes
Sometimes
Sometimes
g Configurable
g Configurable
g Configurable
g Configurable
g Configurable
g Never
g Never
Always
Always
Sometimes
Sometimes
Configurable
Configurable
Count > 1
Pulse On
Pulse Off
Latch On
Latch Off
Queue
Clear Queue
FILL OUT THE FOLLOWING ITEM FOR MASTER DEVICES ONLY:
Expects Binary Input Change Events:
Either time-tagged or non-time-tagged for a single event
Both time-tagged and non-time-tagged for a single event
Configurable (attach explanation)
FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:
Reports Binary Input Change Events when no
specific variation requested:
Reports time-tagged Binary Input Change Events
when no specific variation requested:
Never
Only time-tagged
g
Only non-time-tagged
Configurable to send both, one or the
other (attach explanation)
g
Sends Unsolicited Responses:
Sends Static Data in Unsolicited Responses:
g
Never
Configurable by class
Only certain objects
Sometimes (attach explanation)
g
Never
Binary Input Change With Time
Binary Input Change With Relative Time
Configurable (attach explanation)
Never
When Device Restarts
When Status Flags Change
No other options are permitted.
g
ENABLE/DISABLE UNSOLICITED
Default Counter Object/Variation:
g
No Counters Reported
Configurable (attach explanation)
Default Object 20
DNP3 User and Reference Manual
May 9, 2007
Counters Roll Over at:
No Counters Reported
Configurable (attach explanation)
16 Bits
95
Default Variation 05
Point-by-point list attached
Sends Multi-Fragment Responses:
DNP3 User and Reference Manual
May 9, 2007
g
g Yes
32 Bits
16 Bits for 16-bit counters
32 Bits for 32-bit counters
Point-by-point list attached
No
96
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
1
0
Binary Input - All Variations
1
1
Binary Input
129, 130
00, 01
1
2
Binary Input with Status
129, 130
00, 01
2
0
Binary Input Change - All Variations
1
06,07,08
2
1
Binary Input Change without Time
1
06,07,08
129, 130
17, 28
2
2
Binary Input Change with Time
1
06,07,08
129, 130
17, 28
2
3
Binary Input Change with Relative Time
1
06,07,08
129, 130
17, 28
10
0
Binary Output - All Variations
1
06
10
1
Binary Output
10
2
Binary Output Status
129, 130
00, 01
12
0
Control Block - All Variations
12
1
Control Relay Output Block
129
echo of
request
12
2
Pattern Control Block
12
3
Pattern Mask
20
0
Binary Counter - All Variations
20
1
32-Bit Binary Counter
129, 130
00, 01
20
2
16-Bit Binary Counter
129, 130
00, 01
20
3
32-Bit Delta Counter
20
4
16-Bit Delta Counter
20
5
32-Bit Binary Counter without Flag
129, 130
00, 01
20
6
16-Bit Binary Counter without Flag
129, 130
00, 01
20
7
32-Bit Delta Counter without Flag
DNP3 User and Reference Manual
May 9, 2007
Func
Codes
(dec)
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
3, 4, 5,
6
17, 28
1, 7, 8,
9, 10
06
97
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
20
8
16-Bit Delta Counter without Flag
21
0
Frozen Counter - All Variations
21
1
32-Bit Frozen Counter
129, 130
00, 01
21
2
16-Bit Frozen Counter
129, 130
00, 01
21
3
32-Bit Frozen Delta Counter
21
4
16-Bit Frozen Delta Counter
21
5
32-Bit Frozen Counter with Time of Freeze
21
6
16-Bit Frozen Counter with Time of Freeze
21
7
32-Bit Frozen Delta Counter with Time of
Freeze
21
8
16-Bit Frozen Delta Counter with Time of
Freeze
21
9
32-Bit Frozen Counter without Flag
129, 130
00, 01
21
10
16-Bit Frozen Counter without Flag
129, 130
00, 01
21
11
32-Bit Frozen Delta Counter without Flag
21
12
16-Bit Frozen Delta Counter without Flag
22
0
Counter Change Event - All Variations
22
1
32-Bit Counter Change Event without Time
129, 130
17, 28
22
2
16-Bit Counter Change Event without Time
129, 130
17, 28
22
3
32-Bit Delta Counter Change Event without
Time
22
4
16-Bit Delta Counter Change Event without
Time
22
5
32-Bit Counter Change Event with Time
22
6
16-Bit Counter Change Event with Time
22
7
32-Bit Delta Counter Change Event with Time
22
8
16-Bit Delta Counter Change Event with Time
DNP3 User and Reference Manual
May 9, 2007
Func
Codes
(dec)
1
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
06,07,08
98
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
23
0
Frozen Counter Event - All Variations
23
1
32-Bit Frozen Counter Event without Time
23
2
16-Bit Frozen Counter Event without Time
23
3
32-Bit Frozen Delta Counter Event without Time
23
4
16-Bit Frozen Delta Counter Event without Time
23
5
32-Bit Frozen Counter Event with Time
23
6
16-Bit Frozen Counter Event with Time
23
7
32-Bit Frozen Delta Counter Event with Time
23
8
16-Bit Frozen Delta Counter Event with Time
30
0
Analog Input - All Variations
30
1
32-Bit Analog Input
129, 130
00, 01
30
2
16-Bit Analog Input
129, 130
00, 01
30
3
32-Bit Analog Input without Flag
129, 130
00, 01
30
4
16-Bit Analog Input without Flag
129, 130
00, 01
30
5
Short Floating Point Analog Input
129, 130
00, 01
31
0
Frozen Analog Input - All Variations
31
1
32-Bit Frozen Analog Input
31
2
16-Bit Frozen Analog Input
31
3
32-Bit Frozen Analog Input with Time of Freeze
31
4
16-Bit Frozen Analog Input with Time of Freeze
31
5
32-Bit Frozen Analog Input without Flag
31
6
16-Bit Frozen Analog Input without Flag
32
0
Analog Change Event - All Variations
32
1
32-Bit Analog Change Event without Time
129,130
17,28
32
2
16-Bit Analog Change Event without Time
129,130
17,28
DNP3 User and Reference Manual
May 9, 2007
Func
Codes
(dec)
1
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
06,07,08
99
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Obj
Var
Func
Codes
(dec)
32
3
32-Bit Analog Change Event with Time
129,130
17,28
32
4
16-Bit Analog Change Event with Time
129,130
17,28
32
5
Short Floating Point Analog Change Event
without Time
129,130
17,28
33
0
Frozen Analog Event - All Variations
33
1
32-Bit Frozen Analog Event without Time
33
2
16-Bit Frozen Analog Event without Time
33
3
32-Bit Frozen Analog Event with Time
33
4
16-Bit Frozen Analog Event with Time
40
0
Analog Output Status - All Variations
40
1
32-Bit Analog Output Status
129, 130
00, 01
40
2
16-Bit Analog Output Status
129, 130
00, 01
40
3
Short Floating Point Analog Output Status
129, 130
00, 01
41
0
Analog Output Block - All Variations
41
1
32-Bit Analog Output Block
3, 4, 5,
6
17, 28
129
echo of
request
41
2
16-Bit Analog Output Block
3, 4, 5,
6
17, 28
129
echo of
request
41
3
Short Floating Point Analog Output Block
3, 4, 5,
6
17, 28
129
echo of
request
50
0
Time and Date - All Variations
50
1
Time and Date
2 (see
4.14)
07 where
quantity = 1
50
2
Time and Date with Interval
51
0
Time and Date CTO - All Variations
51
1
Time and Date CTO
1
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
06
129, 130
07,
quantity=1
DNP3 User and Reference Manual
May 9, 2007
100
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Obj
Var
51
2
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Func
Codes
(dec)
Qual
Codes
(hex)
Unsynchronized Time and Date CTO
Func
Codes
129, 130
Qual
Codes
(hex)
07,
quantity=1
52
0
Time Delay - All Variations
52
1
Time Delay Coarse
129
07,
quantity=1
52
2
Time Delay Fine
129
07,
quantity=1
60
0
60
1
Class 0 Data
1
06
60
2
Class 1 Data
1
20,21
06,07,08
06
60
3
Class 2 Data
1
20,21
06,07,08
06
60
4
Class 3 Data
1
20,21
06,07,08
06
70
1
File Identifier
80
1
Internal Indications
2
00
index=7
81
1
Storage Object
82
1
Device Profile
83
1
Private Registration Object
83
2
Private Registration Object Descriptor
90
1
Application Identifier
100
1
Short Floating Point
100
2
Long Floating Point
100
3
Extended Floating Point
101
1
Small Packed Binary-Coded Decimal
101
2
Medium Packed Binary-Coded Decimal
DNP3 User and Reference Manual
May 9, 2007
101
DNP V3.00
DEVICE PROFILE DOCUMENT
IMPLEMENTATION OBJECT
This table describes the objects, function codes and qualifiers used in the device:
OBJECT
Obj
Var
101
3
Description
REQUEST
RESPONSE
(slave must parse)
(master must parse)
Func
Codes
(dec)
Qual
Codes
(hex)
Func
Codes
Qual
Codes
(hex)
Large Packed Binary-Coded Decimal
No Object
13
No Object
14
No Object
23
(see
4.14)
DNP V3.00
TIME SYNCHRONISATION PARAMETERS
This table describes the worst-case time parameters relating to time synchronization,
as required by DNP Level 2 Certification Procedure section 8.7
PARAMETER
VALUE
Time base drift
+/- 1 minute/month at 25°C
+1 / -3 minutes/month 0 to 50°C
Time base drift over a 10-minute interval
+/- 14 milliseconds at 25°C
+14 / -42 milliseconds 0 to 50°C
Maximum delay measurement error
+/- 100 milliseconds
Maximum internal time reference error when set
from the protocol
+/- 100 milliseconds
Maximum response time
100 milliseconds
DNP3 User and Reference Manual
May 9, 2007
102
TelePACE C Tools
User and Reference Manual
CONTROL
MICROSYSTEMS
SCADA products... for the distance
48 Steacie Drive
Kanata, Ontario
K2K 2A9
Canada
Telephone:
613-591-1943
Facsimile:
613-591-1022
Technical Support: 888-226-6876
888-2CONTROL
TelePACE C Tools User and Reference Manual
©2007 Control Microsystems Inc.
All rights reserved.
Printed in Canada.
Trademarks
TelePACE, SCADASense, SCADAServer, SCADALog, RealFLO, TeleSAFE, TeleSAFE
Micro16, SCADAPack, SCADAPack Light, SCADAPack Plus, SCADAPack 32, SCADAPack
32P, SCADAPack 350, SCADAPack LP, SCADAPack 100, SCADASense 4202 DS,
SCADASense 4202 DR, SCADASense 4203 DS, SCADASense 4203 DR, SCADASense
4102, SCADASense 4012, SCADASense 4032 and TeleBUS are registered trademarks of
Control Microsystems.
All other product names are copyright and registered trademarks or trade names of their
respective owners.
Material used in the User and Reference manual section titled SCADAServer OLE
Automation Reference is distributed under license from the OPC Foundation.
TelePACE C Tools User and Reference Manual
May 9, 2007
1
Table of Contents
TABLE OF CONTENTS .......................................................................................................... 2
TELEPACE C TOOLS OVERVIEW......................................................................................... 3
GETTING STARTED ............................................................................................................... 6
C PROGRAM DEVELOPMENT ............................................................................................ 11
REAL TIME OPERATING SYSTEM...................................................................................... 24
OVERVIEW OF PROGRAMMING FUNCTIONS .................................................................. 37
TELEPACE C TOOLS FUNCTION SPECIFICATIONS........................................................ 73
TELEPACE C TOOLS MACRO DEFINITIONS .................................................................. 431
TELEPACE C TOOLS STRUCTURES AND TYPES ......................................................... 441
C COMPILER KNOWN PROBLEMS .................................................................................. 469
TELEPACE C TOOLS WARRANTY AND LICENSE ......................................................... 472
TelePACE C Tools User and Reference Manual
May 9, 2007
2
TelePACE C Tools Overview
The TelePACE C Tools are ideal for engineers and programmers who require advanced
programming tools for SCADA applications and process control. The SCADAPack, 4000
Series and TeleSAFE families of controllers execute ladder logic and C application
programs simultaneously, providing you with maximum flexibility in implementing your
control strategy.
This manual provides full documentation on the TelePACE C program loader and the library
of C language process control and SCADA functions. We strongly encourage you to read it,
and to notify us if you find any errors or additional items you feel should be included in our
documentation.
We sincerely hope that the reliability and flexibility afforded by this fully programmable
controller enable you and your company to solve your automation problems in a cost
effective and efficient manner.
The TelePACE C Tools include an ANSI C cross compiler; a customized library of functions
for industrial automation and data acquisition; a real time operating system; and the
TelePACE C program loader. The C function library is similar to many other C
implementations, but contains additional features for real time control, digital and analog I/O.
An overview of the application development environment and its features follows.
Program Development
C programs are written using any text editor. The MCCM77 compiler is used to compile,
assemble and link the programs on a personal computer.
The memory image, which results from this process may then be, loaded either into the
RAM, committed to an EPROM, or both may be used together. Programs may be executed
either manually or automatically at power up.
Modularity
Programs written in TelePACE C may be split into many separately compiled modules.
These modules may be tested individually before being linked together in the final program.
Command files specify how the various files are to be linked.
Assembly Language Code
Assembly language source code may be included directly within C programs. The #asm and
#endasm statements are used to enclose in-line assembly language code, which is then
assembled without passing through the compiler.
C programs are converted to assembly language by the MCCM77 compiler, and this code
may be viewed and modified. The resulting code may also be combined with programs
written directly in assembler.
Program Options
A C application program may reside in RAM or ROM. The normal method of program
development has the program in RAM. The program may call library routines in the
operating system ROM. The RAM is nonvolatile (battery backed), so the program may
remain in RAM once development is completed and the unit is installed.
Application programs may also be committed to EPROM. The RAM is used for data storage
in this case.
TelePACE C Tools User and Reference Manual
May 9, 2007
3
Supported Language Features
The TelePACE C Tools use the Microtec® MCCM77 C compiler. The compiler is ANSI C
compliant, and provides a code optimizer and assembler.
In addition to the standard C operators, data types and library functions, the C tools provide
a set of routines specifically designed for control applications. Some applications and the
descriptions of these functions may be found on the following pages.
Serial Communication
An extensive serial communication library supports simple ASCII communication,
communication protocols and serial port configuration. The default communication mode
uses the TeleBUS RTU communication protocol. It supports access to the I/O database,
serial port reconfiguration and program loading.
The application program can disable the TeleBUS protocol, and use the serial ports for other
purposes.
TeleBUS protocols are compatible with the widely supported, Modbus ASCII and RTU
protocols.
Clock/Calendar
The processor's hardware clock calendar is supported by the C Tools. The time, date and
day of week can be read and set by the application software.
Timers
The controller provides 32 software timers. They are individually programmable for tick rates
from ten per second to once every 25.5 seconds. Timers may be linked to digital outputs to
cause external devices to turn on/off after a specified period. All timers operate in the
background from a hardware interrupt generated by the main system clock.
Duty Cycle and Pulse Outputs
The digital I/O driver provides duty cycle and pulse train outputs. Duty cycle outputs
generate continuous square waves. Pulse train outputs generate finite sequences of pulses.
Outputs are generated independent of the application program.
Watchdog Timer
The controller supports a hardware watchdog timer to detect and respond to hardware or
software failures. Watchdog timer trigger pulses may be generated by the user program or
by the system clock.
Checksums
To simplify the implementation of self-checking communication algorithms, the C Tools
provide four types of checksums: additive, CRC-16, CRC-CCITT, and byte-wise exclusiveOR. The CRC algorithms are particularly reliable, employing various polynomial methods to
detect nearly all communication errors. Additional types of checksums are easily
implemented using library functions.
TelePACE C Tools User and Reference Manual
May 9, 2007
4
Standard I/O Functions
The TelePACE C Tools are an enhanced version of standard C libraries. Most of the usual
C programming techniques apply. However, with respect to I/O, there are some differences.
The C Tools function library supports all the standard I/O functions. There are no disk-drives
or peripherals associated with the controller. Thus many file handling functions return fixed
responses, indicating that the operation could not be performed.
All standard devices are opened automatically by the operating system and cannot be
closed. The route function may be used to redirect stdin, stdout and stderr.
The TelePACE Program
TelePACE is an easy-to-use interface providing, among several other features, a C Program
Loader and a Ladder Logic program editor. On-line help provides a full reference to all the
features of the TelePACE program. TelePACE runs on the Microsoft Windows operating
system.
This manual references only those features of TelePACE pertaining to the C Program
Loader dialog. Please refer to the section TelePACE Program Reference for a complete
description of TelePACE menus, which will be useful during C Program development.
Additional Documentation
Additional documentation on TelePACE Ladder Logic and the TeleSAFE and SCADAPack
controllers is found in the following documents.
The on-line help for the TelePACE C program loader contains a complete reference to the
operation of the loader. To display on-line help, select Contents from the Help menu.
The SCADAPack & Micro16 System Manual is a complete reference to controller and I/O
modules used with SCADAPack and Micro16 controllers. It contains the SCADAPack
Controller Hardware Manual, the TeleSAFE Micro16 System Manual and hardware
manuals for all 5000 Series I/O modules.
The TelePACE Ladder Logic Reference and User Manual describes the creation of
application programs in the Ladder Logic language.
The TeleBUS Protocols User Manual describes communication using Modbus compatible
protocols.
The TelePACE PID Controller Reference Manual describes PID control concepts and
provides examples using the PID functions.
TelePACE C Tools User and Reference Manual
May 9, 2007
5
Getting Started
This section of the C Tools User Manual describes the installation of C Tools and includes a
Program Development Tutorial. The Program Development Tutorial leads the user through
the steps involved in writing, compiling, linking and loading a C application program.
System Requirements
TelePACE requires the following minimum system configuration.
• Personal computer using 80386 or higher microprocessor.
• Microsoft Windows™ operating system versions including Windows 2000, NT and XP™ .
• Minimum 4 MB of memory.
• Mouse or compatible pointing device.
• Hard disk with approximately 2.5 Mbytes of free disk space.
Making Backup Disks
You should make a backup copy of the TelePACE disk and Microtec C compiler disks
before using the software. A backup copy protects you against damage to the disk. Always
work with the backup copy – if it fails, you can make a new copy from the original disk. Store
the original disk in a safe location.
• In My Computer, click the icon for the disk you want to copy.
• On the File menu, click Copy Disk.
• Click the drive you want to copy from and the drive you want to copy to, and then click
Start.
Installation of C Compiler
Install the Microtec C compiler as described in the installation manuals supplied with the
system.
To run the Microtec Compiler and Linker from any directory, without the need to specify the
full path, you will have to setup the following System Environmental Variables:
Variable
mri_m77_bin
mri_m77_inc
mri_m77_lib
mri_m77_tmp
Value
c:\mccm77;c:\asmm77
c:\mccm77
c:\mccm77
c:\mccm77\tmp
In addition you would need to add these values to the Path System Variable:
C:\MCCM77;C:\ASMM77;C:\XHSM77
Note that spaces are not tolerated in between entries in the Path value.
TelePACE C Tools User and Reference Manual
May 9, 2007
6
On a Windows XP Control Panel, select System | Advanced | Environmental Variables to
access the dialog where the above variables need to be set.
Installation of TelePACE
Install TelePACE as described in the installation section of the TelePACE Ladder Logic
Reference and User Manual.
Some virus checking software may interfere with Setup. If you experience problems with the
Setup, disable your virus checker and run Setup again.
Installing C Tools as an Upgrade
If you are installing TelePACE as an upgrade to a previous C Tools installation for the
Micro16, note that the C Tools are installed in the new directory
c:\telepace\ctools\520x instead of the directory c:\telepace\ctools\micro16.
If the older version of C Tools is not needed, copy all user data files out of the micro16
directory and delete the directory and its contents.
When linking older programs you will need to modify all older linker command (.cmd) files to
reference the new 520x directory instead of the micro16 directory, or see the sample linker
file appram.cmd for the correct file contents.
The sample linker command file appram.cmd also loads the new ctools.lib library. This
library contains the new C Tools functions defined in the header file ctools.h.
Program Development Tutorial
Program development consists of three stages: writing and editing; compiling and linking;
and loading the program into the controller. Each uses separate tools. To demonstrate these
steps a sample program will be prepared.
Refer to the C Program Development section for a full description of the program
development process.
Traditionally, the first program that is run on a new C compiler is the hello, world program. It
prints the message “hello, world”.
Writing and Editing
A controller C program is written using any text editor or word processor in text mode. The
syntax should correspond to that described in the Microtec MCCM77 Documentation Set,
and the C Program Development section of this manual. This chapter describes nonstandard functions, which are unique to the controller. It should be read carefully to make full
use of the special purpose routines available.
Using your text editor, open the file hello.c file. It is located in the
telepace\ctools\520x directory. The program looks a little different from the traditional
hello, world program.
/* ----------------------------------------------hello.c
SCADAPack and TeleSAFE Micro16 Test Program
The infamous hello, world program.
-------------------------------------------- */
#include
TelePACE C Tools User and Reference Manual
May 9, 2007
7
void main(void)
{
PROTOCOL_SETTINGS settings;
/* Disable the protocol on serial port 1 */
settings.type
= NO_PROTOCOL;
settings.station
= 1;
settings.mode
= AM_standard;
settings.priority
= 3;
settings.SFMessaging = FALSE;
setProtocolSettings(com1, &settings);
/* Print the message */
fprintf(com1, "hello, world\r\n");
/* Wait here forever */
while (TRUE)
{
NULL;
}
}
The “hello, world” message will be output to the com1 serial port of the controller. A terminal
connected to the port will display the message.
The controller normally communicates on all ports using the TeleBUS communication
protocol. The first section of the program disables the com1 protocol so the serial port can
be used as a normal RS-232 port.
The fprintf function prints the message to the com1 serial port.
When you have completed examining the program, close the hello.c file. It is now ready
to be compiled and linked.
Compiling and Linking
Compiling and linking convert the source code into executable code for the controller. The
TelePACE C Tools use a C cross compiler and linker from Microtec, a respected supplier of
embedded system tools. The compiler produces tight, well-optimized code. The compiler
and linker run under the Microsoft MS-DOS operating system.
The compiler has many command line options. The basic command line and options
required to compile code for the controller are:
mccm77 -v -nQ -Ml -c filename.c
This should be repeated for each file in the application. Note that the command line options
are case sensitive. The character following the M is a lower case l (ell).
Files are linked together using linker command files. To link a program execute the
command:
lnkm77 -c filename.cmd
Sample command files for RAM and ROM based applications are located in the
telepace\ctools\520x directory.
Example
The hello.c program is found in the telepace\ctools\520x directory. To compile and
link the program:
• switch to the telepace\ctools\520x directory;
TelePACE C Tools User and Reference Manual
May 9, 2007
8
• enter the commands
mccm77 -v -nQ -Ml -c hello.c
lnkm77 -c hello.cmd
The file hello.abs contains the executable code in a format ready to load into the
controller.
Loading and Executing
The TelePACE C Program Loader transfers executable files from a PC to the controller and
controls execution of programs in the controller. The loader can also initialize program
memory and serial port configuration.
Controller Initialization
The memory of the controller has to be initialized when beginning a new programming
project or when it is desired to start from default conditions. It is not necessary to initialize
the controller before every program load.
To initialize the controller, first perform a SERVICE boot. A SERVICE boot preserves
programs and data in nonvolatile RAM, but does not start the programs running. Default
communication parameters are used.
To perform a service boot:
• Remove power from the controller.
• Press and hold the LED POWER switch.
• Apply power to the controller.
• Wait until the STAT LED on the top of the board turns on.
• Release the LED POWER switch.
Second, initialize the program and data memory in the controller. A new controller will
require all initializations to be performed. Selected initializations can be performed on a
controller that is in use.
• Run the TelePACE program under Microsoft Windows.
• Connect the PC to the controller with the appropriate serial cable. The hello, world
program will print data on the com1 serial port. Therefore connect to the com2 serial port
on the controller. (All communication ports work the same. We use com2 here because
the sample program is using com1.)
• From the Controller menu, select under Type the controller type that is connected. A
check mark appears beside the desired type when it is selected.
• From the Controller menu, select the Initialize command.
• Select all options: Erase Ladder Logic Program, Erase C Program, Initialize
Controller and Erase Register Assignment Table.
• Click on the OK button.
The controller is now ready for a program.
Loading the Program
To load the hello, world program into the controller:
TelePACE C Tools User and Reference Manual
May 9, 2007
9
• Run the TelePACE program.
• From the Controller menu, select the C Program Loader command.
• Enter hello.abs in the edit box for the C Program file name.
• Select all write options: C Program, Register Assignment and Serial port settings.
• Click on the Write button. The file will be downloaded.
• A warning message about the empty register assignment will appear. Click on the OK
button.
Executing the Program
• Connect a terminal to com1 on the controller. It will display the output of the program. Set
the communication parameters to 9600 baud, 8 data bits, 1 stop bit, and no parity.
• From the C Program Loader dialog, click on the Run button to execute the program.
The “hello, world” message will be displayed on the terminal.
Serial Communication Parameters
When the controller is powered up in the SERVICE mode the serial ports are configured as:
• 9600 baud
• 8 data bits
• 1 stop bit
• no parity
• Modbus RTU protocol emulation
• station address = 1
A program may change these settings with the set_port function. When the controller is
powered up in RUN position, the custom parameters, as stored by the most recent save
function, are used.
TelePACE C Tools User and Reference Manual
May 9, 2007
10
C Program Development
Program Architecture
A C application program may be contained in a single file or in a number of separate files,
called modules. A single file is simple to compile and link. It can become cumbersome to edit
and time-consuming to compile as the file grows in size.
An application stored in separate modules by function is easier to edit, promotes function reuse, and is quicker to compile when only a few modules are changed. Compiled modules
can be combined into object libraries and shared among users.
The TelePACE C Tools support both single file and multiple module programs. A C
application program consists of support functions provided by the C Tools and the main()
and other functions written by the user.
Main Function Structure
The program sample below shows a typical structure for the main() function.
void main(void)
{
/* Perform initialization actions */
/* Start support tasks */
/* Main Loop*/
while (TRUE)
{
/* Perform application functions */
}
}
Initialization actions typically consist of variable declarations, variable initialization and onetime actions that must be performed when the program starts running.
Supporting tasks (see Real Time Operating System section) are typically created before
the main loop of the program. Tasks can be created and ended dynamically during the
execution of a program as well.
The main loop of a program is always an infinite loop that continually performs the actions
required by the program. The main() function normally never returns.
Example
The following is an example of a three-module program. Each function is stored in a
separate file. This program will be used in subsequent examples.
File: func1.c
#include
void func1(void)
{
fputs("This is function 1\r\n", com1);
}
File: func2.c
TelePACE C Tools User and Reference Manual
May 9, 2007
11
#include
void func2(void)
{
fputs("This is function 2\r\n ", com1);
}
File: main.c
#include
extern void func1(void);
extern void func2(void);
void main(void)
{
func1();
while (TRUE)
{
func2();
}
}
Start-Up Function Structure
The user’s main() function is called from the appstart function of the C Tools. It is not
necessary to understand the appstart function to write programs. However it performs a
number of useful functions that can be modified by the user.
The start-up code has five major functions:
• create and initialize the application program heap (for dynamic memory allocation);
• specify the number of stack blocks allocated to the main task;
• initialize application program variables;
• control execution of the protocol, ladder logic and background I/O tasks;
• execute the main function.
Source code for the function is supplied with the C Tools. The following discussion refers to
statements found in the file appstart.c.
The heap is a section of memory used by dynamic memory allocation functions such as
malloc. The heap starts at the end of RAM used by the program and continues to the end
of physical RAM. The limit is set by the statement:
end_of_heap
.EQU
41ffffh
The limit is set by default to the smallest memory option available for the controller. If your
controller has more memory, change the value of the constant according to the following
table.
RAM Installed
128 Kbytes
256 Kbytes
640 Kbytes
1024 Kbytes
C Application Program RAM
Addresses
none (ladder logic only)
400000h – 41FFFFh
400000h – 47FFFFh
388000h – 3E7FFFh
400000h – 47FFFFh
TelePACE C Tools User and Reference Manual
May 9, 2007
12
The application program signature section of the file contains a constant that determines the
size of the stack allocated to the main task. The stack size is sufficient for most applications.
It can be changed by modifying the statement:
.WORD 4
;stack size in blocks
Refer to the Real Time Operating System section for more information on the stack
required by tasks.
The appstart function begins by initializing the heap pointers, setting all non-initialized
variables to zero, and initializing system variables.
It then starts the communication protocols for each serial port, according to the stored
values in the EEPROM (or the standard values on a SERVICE boot). If your application
program never uses the communication protocols, some or all of the following commands
can be removed, to free the stack space used by the protocol tasks.1
start_protocol(com1);
start_protocol(com2);
start_protocol(com3);2
start_protocol(com4);3
The background I/O task is required for the timer functions, dial-up modem communications,
and PID controller functions to operate. If you do not intend to use these functions, you can
reduce the CPU load by changing TRUE to FALSE in the following statement:
runBackgroundIO(TRUE);
The ladder logic interpreter is required for ladder logic programs. If you do not intend to use
ladder logic, you can reduce the CPU load by changing TRUE to FALSE in the following
statement:
runLadderLogic(TRUE);
The final operation is execution of the main function. The _initcopy function copies the
initial values for initialized variables from the __INITDATA section in the program to the
variables. If there are no errors in the data then the user’s application program runs. (An
error is likely only if the program in RAM has been damaged or improperly linked.)
if (_initcopy() == 0)
{
main();
}
If the main function returns, the task is ended. First, any modem control sessions started by
the application are terminated.
abortAllDialupApps();
Then the task is ended. This will cause all other APPLICATION tasks created by main to be
stopped as well.
taskStatus = getTaskInfo(0);
end_task(taskStatus.taskID);
1
2
3
Stack space is required to create additional tasks. Refer to the create_task function for more
information.
com3 is used only in the SCADAPack and SCADAPack PLUS controllers.
com4 is used only in the SCADAPack LIGHT and SCADAPack PLUS controllers.
TelePACE C Tools User and Reference Manual
May 9, 2007
13
Data Storage
All non-initialized variables (local and global) are initialized to zero on program startup by the
Microtec C Compiler. The I/O database is the only section of memory that is not initialized to
zero on startup. Data stored in the I/O database is maintained when power to the controller
is lost, and remains until the controller is initialized from the TelePACE program.
In most cases the I/O database provides adequate space for data storage. However, if
additional non-initialized memory is required, for example for an array of custom data
structures, an non-initialized section of memory can be created as shown in the example
below.
/* ---------------------------------------------------------------datalog.c
This file contains the global variable definitions for a datalogger
database.
These global variables are placed in a non-initialized section
called "savedata". All data in these variables will be maintained
over powerup.
------------------------------------------------------------------ */
#include
/* define a non-initialized section called savedata */
#pragma option -NZsavedata
#pragma option -Xp
/* Global variable definitions */
/* log index */
unsigned logIndex;
/* log database */
struct dataLog
logData[DATA_LOG_SIZE];
Any variable defined in this file datalog.c will be placed in the non-initialized section
arbitrarily named savedata. Code operating on these variables should be placed in a
separate file, which references these global variables through external definitions placed in a
header file (e.g. datalog.h).
The #pragma option directive is documented in the Microtec MCCM77 Documentation
Set.
Compiling Source Code
The C Compiler converts source code into object files. The basic command line and options
required to compile code for the controller are:
mccm77 -v -nQ -Ml -c filename.c
A complete description of the command line options is given in the Microtec MCCM77 User’s
Guide. The options used here are:
Option
-v
-nQ
-Ml
Description
Issue warnings for features in source file. This option allows you to
detect potential errors in your source code before running the program.
Do not suppress diagnostic messages. This option provides additional
warnings that allow you to detect potential errors in your source code
before running the program.
Compile for large memory model (note that the character following the
TelePACE C Tools User and Reference Manual
May 9, 2007
14
M is a lower case ell).
Compiler output is an object file.
-c
The following options may be useful.
Option
-Jdir
-O
-Ot
-nOc
Description
Specify the directory containing the standard include files. Adding Jc:\telepace\ctools\520x to the command line allows you to
locate your application program files in a different directory. This helps
in organizing your files if you have more than one application program.
Enable standard optimizations. This produces smaller and faster
executable code.
Optimize in favor of execution time rather than code size where a
choice can be made.
Pop the stack after each function call. This increases code size and
execution time. This option should only be used if there is a large
number of consecutive function calls in your program.
A large number of consecutive calls requires a large stack allocation
for a task. Since the number of stack blocks is limited, using this option
can reduce the stack requirements for a task. See the description for
the create_task function for more information.
Each module in an application should be compiled to produce an object file. The object files
are then linked together to form an executable program.
Example
The following commands are required to compile the program described in the previous
sections.
mccm77 -v -nQ -Ml -c main.c
mccm77 -v -nQ -Ml -c func1.c
mccm77 -v -nQ -Ml -c func2.c
This produces three output files: main.obj; func1.obj and func2.obj. In the next
section these object files will be combined into an executable program.
Linking Object Files
The linker converts object files and object file libraries into an executable program. The
basic command line and options to link a program are:
lnkm77 -c filename.cmd
Controller programs can execute from RAM, Flash or ROM. The linker command file
determines the location of the program.
RAM Based Applications
A sample linker command file for a RAM based program is appram.cmd located in the
telepace\ctools\520x directory.
The file begins by specifying the location and order of memory sections. The far_appcode
section is the first section in all controller C programs. It contains the start-up code that calls
the main() function. In a RAM based program, the start-up code is located at the start of C
application program RAM. This address is fixed at 00400000h.
TelePACE C Tools User and Reference Manual
May 9, 2007
15
The order commands specify the order of the sections. The sections are grouped so all the
code and static data sections are first. The variable data sections follow. The heap is the last
section. It is allowed to grow from the end of the program data to the end of memory (see
Start Up Function Structure section for more information).
The sections may be rearranged, and new sections added, according to the following rules:
• The far_appcode section must be first in the order listing.
• All code sections must follow the far_appcode section.
• The far_endcode section must be the last code section.
• All data sections must follow the code sections.
• The heap section must be last in the order listing.
; ---------------------------------------------; Specify location and order of memory sections
; ---------------------------------------------sect far_appcode = 00400000h
order far_appcode, far_code, (CODE), const
order strings, literals, __INITDATA, far_endcode
order far_zerovars, far_initvars, (DATA), heap
The next section of the command file creates initialized data sections. All variables
in the specified section are initialized at start-up of the program. The linker creates a
copy of the data in these sections and stores it in the __INITDATA section.
; ---------------------------------------------; Create initialized variables section
; ---------------------------------------------initdata far_initvars
The next section of the command file lists the application program object modules (files) to
be included in the program. You may also include libraries of functions you create here. The
sample command file includes one object module: app.obj.
; ---------------------------------------------; Load application program object modules
; ---------------------------------------------load app
The next section of the command file lists the start-up routines and standard libraries to be
included. There are three object modules and two libraries:
Module
Appstart.obj
Romfunc.obj
Ctools.lib
cm77islf.lib
cm77islc.lib
Description
This file contains the application program start up routine
(see Program Architecture section above). If you modify the
start-up routine for a particular application, be sure to specify
the path to the modified routine.
This file contains addresses of the jump table for calling
functions in the operating system ROM. Only the symbols
are loaded as only the addresses are needed.
This is the C Tools library, which contains C Tools functions
not found in the operating system ROM.
This is the standard Microtec floating point library.
This is the standard Microtec function library.
; ---------------------------------------------; Load start up and library routines
; ---------------------------------------------load c:\telepace\ctools\520x\appstart
TelePACE C Tools User and Reference Manual
May 9, 2007
16
load_symbols c:\telepace\ctools\520x\romfunc
load c:\telepace\ctools\520x\ctools.lib
load c:\mccm77\cm77islf.lib
load c:\mccm77\cm77islc.lib
The final section of the command file specifies the output file format. The listmap
command specifies what information is to be included in the map file. Refer to the Microtec
manuals for more information on map files.
The format command specifies the executable output will be in Motorola S2 record format.
The TelePACE C Program Loader requires this format.
; ---------------------------------------------; Specify output file formats and options
; ---------------------------------------------listmap nopublics, nointernals, nocrossref
format S2
Example
The standard command file must be modified to link the application described in the
previous example. Copy the appram.cmd file to myapp.cmd. Modify the application object
modules section to read:
; ---------------------------------------------; Load application program object modules
; ---------------------------------------------load main
load func1
load func2
Link the file with the command
lnkm77 -c myapp.cmd
This will produce one output file: myapp.abs. The next step is to load it into the controller
using the TelePACE C Program Loader.
Flash Based Applications
A sample command file for a Flash based program is appflash.cmd located in the
telepace\ctools\520x directory. This file is very similar to the command file for RAM
based programs.
The file begins by specifying the location and order of memory sections. There are two types
of sections in a Flash based program. The code and static data sections must be stored in
the Flash. The variable data sections must be stored in RAM.
The far_appcode section is the first code section in all controller C programs. In a Flash
based program, the far_appcode section is located at 110000h.
The far_zerovars section is the first data section. In a ROM based program it is normally
located at the start of application program RAM (00400000h). It is possible to start this
section at any RAM address, if your application requires it.
The order commands specify the order of the sections. The sections may be rearranged,
and new sections added, according to the following rules:
• The far_appcode section must be first in the order listing.
• All code sections must follow the far_appcode section.
• The far_endcode section must be the last code section.
TelePACE C Tools User and Reference Manual
May 9, 2007
17
• The far_zerovars section must be the first data section.
• All other data sections must follow the far_zerovars section.
• The heap section must be the last data section.
; ---------------------------------------------; Specify location and order of memory sections
; ---------------------------------------------sect far_appcode = 00110000h
sect far_zerovars = 00400000h
order far_appcode, far_code, (CODE), const
order strings, literals, __INITDATA, far_endcode
order far_zerovars, far_initvars, (DATA), heap
The remaining sections of the file are identical to the RAM command file. Refer to the RAM
Based Applications section for a description.
The final section of the command file specifies the output file format. The default format
command specifies the executable output will be in Motorola S2 record format. This is the
format required by the TelePACE Flash Loader.
Example – C Program in Flash
The standard command file must be modified to link the application described in the
previous example. Copy the appflash.cmd file to myapp.cmd. Modify the application
object modules section to read:
; ---------------------------------------------; Load application program object modules
; ---------------------------------------------load main
load func1
load func2
Link the file with the command
lnkm77 -c myapp.cmd
This will produce one output file: myapp.abs. The next step is to write the file to the
controller using TelePACE. Use the Flash Loader command on the Controller menu. Consult
the TelePACE documentation for details.
ROM Based Applications
A ROM based program is very similar to a Flash based application. However, an EPROM
programmer must be used to create the ROM. ROM based programs have access to more
program (code) memory than Flash based applications.
It is recommended that Flash based programs be used, unless there is not enough program
memory available.
If a ROM based program is created it should be stored in an EPROM. If a Flash based part
is used the commands in TelePACE to erase Flash may not work as expected. Contact
Control Microsystems for more information about this.
A sample command file for a ROM based program is approm.cmd located in the
telepace\ctools\520x directory. This file is very similar to the command file for Flash
based programs.
The file begins by specifying the location and order of memory sections. There are two types
of sections in a ROM based program. The code and static data sections must be stored in
the ROM. The variable data sections must be stored in RAM.
TelePACE C Tools User and Reference Manual
May 9, 2007
18
The far_appcode section is the first code section in all controller C programs. In a ROM
based program, the far_appcode section can be located at any address that is a multiple
of 100h in the application ROM. The start of application ROM is fixed at 100000h.
A C application program may share the application ROM space with a ladder logic program.
If only a C program is stored in the ROM the far_appcode section is located at 100000h. If
a ladder logic program is stored in ROM it must start at 100000h. The C application can start
anywhere after the end of the ladder logic program. This location is determined by the size
of the ladder logic program and is best determined by examining the memory image of the
ladder logic program in your EPROM programmer.
The far_zerovars section is the first data section. In a ROM based program it is normally
located at the start of application program RAM (00400000h). It is possible to start this
section at any RAM address, if your application requires it.
The order commands specify the order of the sections. The sections may be rearranged,
and new sections added, according to the following rules:
• The far_appcode section must be first in the order listing.
• All code sections must follow the far_appcode section.
• The far_endcode section must be the last code section.
• The far_zerovars section must be the first data section.
• All other data sections must follow the far_zerovars section.
• The heap section must be the last data section.
; ---------------------------------------------; Specify location and order of memory sections
;
; Note: the far_appcode section address must
;
be a multiple of 100h.
; ---------------------------------------------sect far_appcode = 00100000h
sect far_zerovars = 00400000h
order far_appcode, far_code, (CODE), const
order strings, literals, __INITDATA, far_endcode
order far_zerovars, far_initvars, (DATA), heap
The remaining sections of the file are identical to the RAM command file. Refer to the RAM
Based Applications section for a description.
The final section of the command file specifies the output file format. The default format
command specifies the executable output will be in Motorola S2 record format. Your
EPROM programmer may require a different output format. The following options are
available. Refer to the Microtec Linker manual for a complete description.
Command
format ASCII
format IEEE
format S1
format S2
Description
Intel ASCII hex format. This is also known as Intel-86 or
Extended Intel Hex format.
Microtec extended IEEE-695 format.
Motorola S1 record format.
Motorola S2 record format.
Example – C Program in ROM
The standard command file must be modified to link the application described in the
previous example. Copy the approm.cmd file to myapp.cmd. Modify the application object
modules section to read:
TelePACE C Tools User and Reference Manual
May 9, 2007
19
; ---------------------------------------------; Load application program object modules
; ---------------------------------------------load main
load func1
load func2
Link the file with the command
lnkm77 -c myapp.cmd
This will produce one output file: myapp.abs. The next step is to program an EPROM using
this file.
Example – C and Ladder Logic Program in ROM
The C application program may share the ROM with a ladder logic program. The ladder
logic program is always located at 100000h. The C program may start at any address that is
a multiple of 100h following the ladder logic program.
The standard command file must be modified to link the application described in the
previous examples. Copy the approm.cmd file to myapp.cmd.
Assume for this example that the ladder logic program ends at address 100417h. The next
multiple of 100h after this address is 100500h. Modify the section locations to read:
; ---------------------------------------------; Specify location and order of memory sections
;
; Note: the far_appcode section address must
;
be a multiple of 100h.
; ---------------------------------------------sect far_appcode = 00100500h
Modify the application object modules section to read:
; ---------------------------------------------; Load application program object modules
; ---------------------------------------------load main
load func1
load func2
Link the file with the command
lnkm77 -c myapp.cmd
This will produce one output file: myapp.abs. The next step is to program an EPROM using
this file.
Controller Initialization
You should initialize the memory of the controller when beginning a new programming
project or when you wish to start from default conditions. It is not necessary to initialize the
controller before every program load.
To initialize the controller, first perform a SERVICE boot. A SERVICE boot preserves
programs and data in nonvolatile RAM, but does not start the programs running. Default
communication parameters are used.
To perform a service boot:
• Remove power from the controller.
TelePACE C Tools User and Reference Manual
May 9, 2007
20
• Press and hold the LED POWER switch.
• Apply power to the controller.
• Wait until the STAT LED on the top of the board turns on.
• Release the LED POWER switch.
Second, initialize the program and data memory in the controller. A new controller will
require all initializations be performed. Selected initializations can be performed on a
controller that is in use.
• Run the TelePACE program under Microsoft Windows.
• Connect the PC to the controller with the appropriate serial cable.
• From the Controller menu, select under Type the controller type that is connected. A
check mark appears beside the desired type when it is selected.
• From the Controller menu, select the Initialize command.
• Select all options: Erase Ladder Logic Program, Erase C Program, Initialize
Controller and Erase Register Assignment Table.
• Click on the OK button.
Loading Programs into RAM
The C Program Loader dialog transfers executable files from a PC to the controller.
To load a program into RAM:
• Initialize the controller (see Controller Initialization section above).
• Load the program into the controller:
• Run the TelePACE program.
• From the Controller menu, select the C Program Loader command.
• Enter the executable (.abs) file in the edit box for the C Program file name.
• Select the C Program write option and any other write options desired.
• Click on the Write button. The file will be downloaded.
A checksum is calculated for the complete C program. The checksum is verified each time
the program is run. This prevents a damaged program from running.
Loading Programs into EPROM
The procedure for creating an EPROM depends on your EPROM programmer. In general
you must follow these steps:
•
Load the executable file into the programmer and program the EPROM.
•
Install the EPROM in the controller.
The controller can accept the following EPROMs. Other EPROMs may be compatible.
Contact Control Microsystems if you are considering using an EPROM not in this list.
Size
(Kbytes)
64
Manufacturer
Part Number
AMD
AM27C512-70DC
TelePACE C Tools User and Reference Manual
May 9, 2007
21
64
128
128
128
128
256
256
SGS-Thomson
AMD
Atmel
SGS-Thomson
Toshiba
AMD
SGS-Thomson
M27C512-80F1
AM27C010-70DC
AT27C010-70PI (one time programmable)
M27C1001-80F1
TC57H1000AD-85
AM27C020-70DC
M27C2001-80F1
C Programs may be loaded into Flash memory or EPROM when using TelePACE firmware
1.64 or older.
TelePACE firmware 1.65 or newer no longer supports C Programs in Flash memory. C
Programs may be loaded in RAM memory only.
Creating the EPROM
Load the executable (.abs) file into the memory of the EPROM programmer, according to
the instructions for the programmer.
The first byte of the EPROM (offset 0 in the EPROM) maps to address 100000h when the
EPROM is installed in the controller. The linker generates an executable file with address
offsets starting at 100000h. These offsets must be removed with most programmers, so that
the memory image can be placed at offset 0 in the EPROM itself. (Note that this does not
affect the addresses in the program itself, just the address at which it loads.)
Consult your EPROM programmer documentation to determine how to remove the offset.
This is typically done in one of two ways:
•
Specify the data is to be loaded from file address 100000h. You may have to specify that
the file is loaded to offset 0h.
•
Or, specify a load offset of –100000h when reading the executable file. The programmer
will add –100000h to all load addresses in the file, resulting in a memory image at offset
0h.
Program the EPROM according to the instructions for your programmer.
Installing the EPROM
Install the EPROM in the application ROM socket on the 5203 or 5204 controller board:
•
Locate the socket labeled U14. This is the application ROM socket.
•
Orient the EPROM so the notch on the EPROM is at the same end as the notch in the
socket.
•
Align all pins of the EPROM with the socket.
•
Press the EPROM gently into the socket.
•
Check that all pins are inserted correctly and that none are bent.
Initialize the controller (see Controller Initialization section above). The Erase C Program
option must be specified. Other initializations may be performed if desired.
Executing Programs
C application programs are executed when a run program command is received from the
TelePACE C Program Loader; or power is applied to the controller (except when a
SERVICE boot is performed).
TelePACE C Tools User and Reference Manual
May 9, 2007
22
To start a program from the program loader:
•
Run the TelePACE program.
•
From the C Program Loader dialog, click on the Run button to execute the program.
The controller will execute either the program in RAM or the program in ROM. It chooses the
program to execute in the following order:
•
C application program in RAM;
•
C application program in ROM;
•
no C application (standard start-up sequence for other components).
This mode of operation is useful in the following scenario. A controller is installed with a
program in ROM. If new features or corrections are required, a program can be downloaded
into RAM, either locally or remotely. This program will take precedence over the program in
ROM.
If the RAM program is lost or damaged, the ROM program will execute. The ROM program
can be used as a fallback, performing minimal functions to maintain a process in a fail-safe
condition.
TelePACE C Tools User and Reference Manual
May 9, 2007
23
Real Time Operating System
The real time operating system (RTOS) provides the programmer with tools for building
sophisticated applications. The RTOS allows pre-emptive scheduling of event driven tasks
to provide quick response to real-world events. Tasks multi-task cooperatively. Inter-task
communication and event notification functions pass information between tasks. Resource
functions facilitate management of non-sharable resources.
Task Management
The task management functions provide for the creation and termination of tasks. Tasks are
independently executing routines. The RTOS uses a cooperative multi-tasking scheme, with
pre-emptive scheduling of event driven tasks.
The initial task (the main function) may create additional tasks. The RTOS supports up to 16
tasks. There are 5 task priority levels to aid in scheduling of task execution.
Task Execution
SCADAPack controllers can execute one task at a time. The RTOS switches between the
tasks to provide parallel execution of multiple tasks. The application program can be event
driven, or tasks can execute round-robin (one after another).
Task execution is based upon the priority of tasks. There are 5 priority levels. Level 0 is
reserved for the null task. This task runs when there are no other tasks available for
execution. Application programs can use levels 1 to 4. The main task is created at priority
level 1.
Tasks that are not running are held in queues. The Ready Queue holds all tasks that are
ready to run. Event queues hold tasks that are waiting for events. Message queues hold
tasks waiting for messages. Resource queues hold tasks that are waiting for resources. The
envelope queue holds tasks that are waiting for envelopes.
Priority Inversion Prevention
When a higher priority task, Task H, requests a resource, which is already obtained by a
lower priority task, Task L, the higher priority task, is blocked until Task L releases the
resource. If Task L is unable to execute to the point where its releases the resource, Task H
will remain blocked. This is called a Priority Inversion.
To prevent this from occurring, the prevention method known as Priority Inheritance has
been implemented. In the example already described, the lower priority task, Task L, is
promoted to the priority of Task H until it releases the needed resource. At this point Task L
is returned to its original priority. Task H will obtain the resource now that it is available.
Note that this does not prevent deadlocks that occur when each task requests a resource
that the other has already obtained. This “deadly embrace” is a design error in the
application program.
Task Management Functions
There are five RTOS functions for task management. Refer to the Function Specification
section for details on each function listed.
TelePACE C Tools User and Reference Manual
May 9, 2007
24
create_task
Create a task and make it ready to execute.
end_task
Terminate a task and free the resources and envelopes allocated to
it.
end_application
Terminate all application program type tasks. This function is used by
communication protocols to stop the application program prior to
loading new code.
installExitHandler
Specify a function that is called when a task is ended with the
end_task or end_application functions.
getTaskInfo
Return information about a task.
Task Management Macros
The ctools.h file defines the following macros used for task management. Refer to the C
Tools Macros section for details on each macro listed.
RTOS_PRIORITIES
Number of RTOS task priorities.
RTOS_TASKS
Number of RTOS tasks.
STACK_SIZE
Size of the machine stack.
TS_EXECUTING
Task status indicating task is executing
TS_READY
Task status indicating task is ready to execute
TS_WAIT_RESOURCE
Task status indicating task is blocked waiting for a resource
TS_WAIT_ENVELOPE
Task status indicating task is blocked waiting for an envelope
TS_WAIT_EVENT
Task status indicating task is blocked waiting for an event
TS_WAIT_MESSAGE
Task status indicating task is blocked waiting for a message
Task Management Structures
The ctools.h file defines the structure Task Information Structure for task management
information. Refer to the C Tools Structures and Types section for complete information
on structures and enumeration types.
Resource Management
The resource management functions arbitrate access to non-sharable resources. These
resources include physical devices such as serial ports, and software that is not re-entrant.
The RTOS defines nine system resources, which are used by components of the I/O drivers,
memory allocation functions and communication protocols.
An application program may define other resources as required. Care must be taken not to
duplicate any of the resource numbers declared in ctools.h as system resources.
Resource Management Functions
There are three RTOS functions for resource management. Refer to the Function
Specification section for details on each function listed.
request_resource
Request access to a resource and wait if the resource is not
available.
TelePACE C Tools User and Reference Manual
May 9, 2007
25
poll_resource
Request access to a resource. Continue execution if the resource is
not available
release_resource
Free a resource for use by other tasks.
IO_SYSTEM Resource
The IO_SYSTEM resource regulates access to all functions using the I/O system. C
application programs, ladder logic programs, communication protocols and background I/O
operations share the I/O system. It is imperative the resource is obtained to prevent a
conflict, as protocols and background operations are interrupt driven. Do not retain control of
the resource for more that 0.1 seconds, or background operations will not execute properly.
DYNAMIC_MEMORY Resource
The DYNAMIC_MEMORY resource regulates access to all memory allocation functions.
These functions allocate memory from the system heap. The heap is shared amongst all
tasks. The allocation functions are non-reentrant.
The DYNAMIC_MEMORY resource must be obtained before using any of the following
functions.
calloc
allocates data space dynamically
free
frees dynamically allocated memory
malloc
allocates data space dynamically
realloc
changes the size of dynamically allocated space
AB_PARSER Resource
This resource is used by the DF1 communication protocol tasks to allocate access to the
common message parser for each serial port. This resource is of no interest to an
application program. However, an application program may not use the resource number
assigned to it.
MODBUS_PARSER Resource
This resource is used by Modbus communication protocol drivers to allocate access to the
common message parser by tasks for each serial port. This resource is of no interest to an
application program.
Resource Management Macros
The ctools.h file defines the following macros used for resource management. Refer to the
C Tools Macros section for details on each macro listed.
AB_PARSER
DF1 protocol message parser.
COM1_DIALUP
Resource for dialing functions on com1.
COM2_DIALUP
Resource for dialing functions on com2.
COM3_DIALUP
Resource for dialing functions on com3.
COM4_DIALUP
Resource for dialing functions on com4.
DYNAMIC_MEMORY Memory
HART
allocation functions.
HART modem resource.
TelePACE C Tools User and Reference Manual
May 9, 2007
26
IO_SYSTEM
I/O system hardware functions.
MODBUS_PARSER
Modbus protocol message parser.
RTOS_RESOURCES Number
of RTOS resource flags.
Inter-task Communication
The inter-task communication functions pass information between tasks. These functions
can be used for data exchange and task synchronization. Messages are queued by the
RTOS until the receiving task is ready to process the data.
Inter-task Communication Functions
There are five RTOS functions for inter-task communication. Refer to the Function
Specification section for details on each function listed.
send_message
Send a message envelope to another task.
receive_message
Read a received message from the task's message queue or wait if
the queue is empty.
poll_message
Read a received message from the task's message queue. Continue
execution of the task if the queue is empty.
allocate_envelope
Obtain a message envelope from free pool maintained by the RTOS,
or wait if none is available.
deallocate_envelope Return a message envelope to the free pool maintained by the
RTOS.
Inter-task Communication Macros
The ctools.h file defines the following macros used for inter-task communication. Refer to
the C Tools Macros section for details on each macro listed.
MSG_DATA
Specifies the data field in an envelope contains a data value.
MSG_POINTER
Specifies the data field in an envelope contains a pointer.
RTOS_ENVELOPES
Number of RTOS envelopes.
Inter-task Communication Structures
The ctools.h file defines the structure Message Envelope Structure for inter-task
communication information. Refer to the C Tools Structures and Types section for
complete information on structures and enumeration types.
Event Notification
The event notification functions provide a mechanism for communicating the occurrence
events without specifying the task that will act upon the event. This is different from intertask communication, which communicates to a specific task.
Multiple occurrences of a single type of event are queued by the RTOS until a task waits for
or polls the event.
TelePACE C Tools User and Reference Manual
May 9, 2007
27
Event Notification Functions
There are four RTOS functions for event notification. Refer to the Function Specification
section for details on each function listed.
wait_event
Wait for an event to occur.
poll_event
Check if an event has occurred. Continue execution if one has not
occurred.
signal_event
Signal that an event has occurred.
interrupt_signal_event Signal that an event has occurred from an interrupt handler. This
function must only be called from within an interrupt handler.
There are two support functions, which are not part of the RTOS that may be used with
events.
startTimedEvent
Enables signaling of an event at regular intervals.
endTimedEvent
Terminates signaling of a regular event.
Event Notification Macros
The ctools.h file defines the following macro used for event notification. Refer to the C
Tools Macros section for details.
Defines the number of available RTOS events.
RTOS_EVENTS
System Events
The RTOS defines events for communication port management and background I/O
operations. An application program may define other events as required. Care must be
taken not to duplicate any of the event numbers declared in ctools.h as system events.
BACKGROUND
This event triggers execution of the background I/O routines. An application
program cannot use it.
COM1_RCVR
This event is used by communication protocols to signal a character or
message received on com1. It can be used in a custom character handler
(see install_handler).
COM2_RCVR
This event is used by communication protocols to signal a character or
message received on com2. It can be used in a custom character handler
(see install_handler).
COM3_RCVR
This event is used by communication protocols to signal a character or
message received on com3. It can be used in a custom character handler
(see install_handler).
COM4_RCVR
This event is used by communication protocols to signal a character or
message received on com4. It can be used in a custom character handler
(see install_handler).
This event is used when a Foxcom message is received. An
application program cannot use it.
FOXCOM_MSG_RECEIVED
This event is used when Foxcom communication has been
established with the sensor. An application program cannot use it.
FOXCOM_STARTED
NEVER
This event is guaranteed never to occur. It can be used to disable a task by
waiting for it to occur. However, to end a task it is better to use end_task.
This frees all resources and stack space allocated to the task.
TelePACE C Tools User and Reference Manual
May 9, 2007
28
Error Reporting
Sharable I/O drivers to return error information to the calling task use the error reporting
functions. These functions ensure that an error code generated by one task is not reported
in another task. The errno global variable used by some functions may be modified by
another task, before the current task can read it.
Error Reporting Functions
There are two RTOS functions for error reporting. Refer to the Function Specification
section for details on each function listed.
check_error
Check the error code for the current task.
report_error
Set the error code for the current task.
Error Reporting Macros
The ctools.h file defines the following macro used for error reporting. Refer to the C Tools
Macros section for details.
NO_ERROR
Error code indicating no error has occurred.
TelePACE C Tools User and Reference Manual
May 9, 2007
29
SCADAPack Task Architecture
The diagram shows the tasks present in the SCADAPack controller.
Background I/O Task
Timer Interrupt
Optional User Tasks
Executes every 0.1 s
240 Hz Interrupt
Created by user from
the Main Task.
Processes:
• software timers
• dialup modem
• PID controllers
Processes:
• Ladders timers
• jiffy timer
• watchdog timer
• timed events
Priority = 4
Priority = 1 to 4
Priority = h/w interrupt
Com1 Protocol Task
Com2 Protocol Task
Com3 Protocol Task
Com4 Protocol Task
Executes when message event occurs
Executes when message event occurs
Executes when message event occurs
Executes when message event occurs
Processes:
• message
Processes:
• message
Processes:
• message
Processes:
• message
Priority = 3
Priority = 3
Priority = 3
Priority = 3
Ladders & I/O Scan Task
Main Task (typical)
Task loop runs continuously:
Task loop runs continuously:
while (TRUE)
{
request_resource(IO_SYSTEM);
while (TRUE)
{
request_resource(IO_SYSTEM);
read data from input modules to I/O database
(Register Assignment)
functions requiring IO_SYSTEM resource
release_resource(IO_SYSTEM);
if program is in RUN mode
execute ladder logic program
write data from I/O database to output modules
(Register Assignment)
functions not requiring IO_SYSTEM resource
release_processor();
}
release_resource(IO_SYSTEM);
release_processor();
}
Priority = 1
Priority = 1
The highest priority routines that execute are hardware interrupt handlers. Most hardware
interrupt handlers perform their functions transparently. The Timer Interrupt handler is
important to application programs, because it updates several timers that can be used in
application programs. It also triggers the background I/O task.
The background I/O task is the highest priority task in the system. It processes software
timers, PID controllers and dialup modem control routines.
There is one protocol task for each serial port where a protocol is enabled. The protocol
tasks wait for an event signaled by an interrupt handler. This event is signaled when a
complete message is received. The protocol tasks process the received message and
transmit a response when needed. Protocol tasks may be disabled and replaced with
protocol tasks from the application program.
The Ladder Logic and I/O Scan task executes the Ladder Logic program and performs an
I/O scan based on the register assignment. This task is the same priority as the main user
application task.
TelePACE C Tools User and Reference Manual
May 9, 2007
30
The main task is the central task of the user application. It performs the functions required by
the user. Typically, it executes at the same priority as the Ladder Logic and I/O Scan task. It
may start other user tasks if needed.
RTOS Example Application Program
The following program is used in the explanation of the RTOS functions. It creates several
simple tasks that demonstrate how tasks execute. A task is a C language function that has
as its body an infinite loop so it continues to execute forever.
The main task creates two tasks. The echoData task is higher priority than main. The
auxiliary task is the same priority as main. The main task then executes round robin
with other tasks of the same priority.
The auxiliary task is a simple task that executes round robin with the other tasks of its
priority. Only the code necessary for task switching is shown to simplify the example.
The echoData task waits for a character to be received on a serial port, then echoes it back
out the port. It waits for the event of the character being received to allow lower priority tasks
to execute. It installs a character handler function – signalCharacter – that signals an
event each time a character is received. This function is hooked into the receiver interrupt
handler for the serial port.
The execution of this program is explained in the Explanation of Task Execution section.
/* -------------------------------------------------------------------SCADAPack Real Time Operating System Sample
Copyright (c) 1998, Control Microsystems Inc.
Version History
version 1.00
Wayne Johnston
November 10, 1998
-------------------------------------------------------------------- */
/* ---- Version 1.00 -------------------------------------------------This program creates several simple tasks for demonstration of the
functionality of the real time operation system.
-------------------------------------------------------------------- */
#include
#include
#include "ctools,h"
/* -------------------------------------------------------------------Constants
-------------------------------------------------------------------- */
#define CHARACTER_RECEIVED
10
/* -------------------------------------------------------------------signalCharacter
The signalCharacter function signals an event when a character is
received. This function must be called from an interrupt handler.
-------------------------------------------------------------------- */
void signalCharacter(unsigned character, unsigned error)
{
/* If there was no error, signal that a character was received */
if (error == 0)
{
interrupt_signal_event(CHARACTER_RECEIVED);
}
/* Prevent compiler unused variables warning (generates no code) */
character;
}
/* --------------------------------------------------------------------
TelePACE C Tools User and Reference Manual
May 9, 2007
31
echoData
The echoData function is a task that waits for a character
to be received on com6 and echoes the character back. It installs
a character handler for com6 to generate events on the reception
of characters.
-------------------------------------------------------------------- */
void echoData(void)
{
struct prot_settings protocolSettings;
struct pconfig portSettings;
int character;
3
/* Disable communication protocol */
get_protocol(com6, &protocolSettings);
protocolSettings.type = NO_PROTOCOL;
set_protocol(com6, &protocolSettings);
/* Set serial communication parameters */
portSettings.baud
= BAUD9600;
portSettings.duplex
= FULL;
portSettings.parity
= NONE;
portSettings.data_bits = DATA8;
portSettings.stop_bits = STOP1;
portSettings.flow_rx
= DISABLE;
portSettings.flow_tx
= DISABLE;
portSettings.type
= RS232;
portSettings.timeout
= 600;
set_port(com6, &portSettings);
/* Install handler for received character */
install_handler(com6, signalCharacter);
while (TRUE)
{
/* Wait for a character to be received */
wait_event(CHARACTER_RECEIVED);
4 9
/* Echo the character back */
character = fgetc(com6);
fputc(character, com6);
}
8
}
/* -------------------------------------------------------------------auxiliary
The auxiliary function is a task that performs some action
required by the program. It does not have specific function so
that the real time operating system features are clearer.
-------------------------------------------------------------------- */
void auxiliary(void)
{
while (TRUE)
{
/* ... add application specific code here ... */
7
/* Allow other tasks of this priority to run */
release_processor();
}
}
/* -------------------------------------------------------------------main
This function creates two tasks: one at priority three and one at
priority 1 to demonstrate the functions of the RTOS.
-------------------------------------------------------------------- */
void main(void)
{
/* Create serial communication task */
TelePACE C Tools User and Reference Manual
May 9, 2007
1
2
32
create_task(echoData, 3, APPLICATION, 3);
/* Create a task - same priority as main() task */
create_task(auxiliary, 1, APPLICATION, 2);
5
while (TRUE)
{
/* ... add application specific code here ... */
/* Allow other tasks of this priority to execute */
release_processor();
}
6
}
Explanation of Task Execution
SCADAPack controllers can execute one task at a time. The Real Time Operating System
(RTOS) switches between the tasks to provide parallel execution of multiple tasks. The
application program can be event driven, or tasks can execute round-robin (one after
another). This program illustrates both types of execution.
Task execution is based upon the priority of tasks. There are 5 priority levels. Level 0 is
reserved for the null task. This task runs when there are no other tasks available for
execution. Application programs can use levels 1 to 4. The main task is created at priority
level 1.
Tasks that are not running are held in queues. The Ready Queue holds all tasks that are
ready to run. Event queues hold tasks that are waiting for events. Message queues hold
tasks waiting for messages. Resource queues hold tasks that are waiting for resources. The
envelope queue holds tasks that are waiting for envelopes.
The execution of the tasks is illustrated by examining the state of the queues at various
points in the program. These points are indicated on the program listing above. The
examples show only the Ready queue, the Event 10 queue and the executing task. These
are the only queues relevant to the example.
Execution Point 1
This point occurs just before the main task begins. The main task has not been created by
the RTOS. The null task has been created, but is not running. No task is executing.
Ready Queue
Event 10 Queue
4
4
3
3
2
2
1
1
0
null()
Running Task
none
0
Figure 1: Queue Status before Execution of main Task
Execution Point 2
This point occurs just after the creation of the main task. It is the running task. On the next
instruction it will create the echoData task.
TelePACE C Tools User and Reference Manual
May 9, 2007
33
Ready Queue
Event 10 Queue
4
4
3
3
2
2
1
1
0
null()
Running Task
main()
0
Figure 2: Queue Status at Start of main Task
Execution Point 3
This point occurs just after the echoData task is created. The echoData task is higher
priority than the main task so it is made the running task. The main task is placed into the
ready queue. It will execute when it becomes the highest priority task.
The echoData task initializes the serial port and installs the serial port handler function
signalCharacter. It will then wait for an event. This will suspend the task until the event
occurs.
The signalCharacter function will generate an event each time a character is received
without an error.
Ready Queue
Event 10 Queue
4
4
3
3
2
2
1
main()
1
0
null()
0
Running Task
echoData()
Figure 3: Queue Status after Creation of echoData Task
Execution Point 4
This point occurs just after the echoData task waits for event 10. It has been placed on the
event queue for event 10.
The highest priority task on the ready queue was the main task. It is now running. On the
next instruction it will create another task at the same priority as main.
TelePACE C Tools User and Reference Manual
May 9, 2007
34
Ready Queue
Event 10 Queue
4
4
3
3
2
2
1
1
0
null()
Running Task
main()
echoData()
0
Figure 4: Queue Status After echoData Task Waits for Event
Execution Point 5
This point occurs just after the creation of the auxiliary task. This task is the same priority as
the main task. Therefore the main task remains the running task. The auxiliary task is
ready to run and it is placed on the Ready queue.
Ready Queue
Event 10 Queue
4
4
3
3
2
2
1
auxiliary()
1
0
null()
0
Running Task
main()
echoData()
Figure 5 Queue Status after Creation of auxiliary Task
Execution Point 6
This point occurs just after the main task releases the processor, but before the next task is
selected to run. The main task is added to the end of the priority 1 list in the Ready queue.
On the next instruction the RTOS will select the highest priority task in the Ready queue.
Event 10 Queue
Ready Queue
4
4
3
3
2
2
1
auxiliary()
0
null()
main()
Running Task
none
echoData()
1
0
Figure 6: Queue Status After main Task Releases Processor
TelePACE C Tools User and Reference Manual
May 9, 2007
35
Execution Point 7
This point is just after the auxiliary task has started to run. The main and auxiliary
tasks will continue to alternate execution, as each task releases the processor to the other.
Ready Queue
Event 10 Queue
4
4
3
3
2
2
1
main()
1
0
nullTask()
0
Running Task
auxiliary()
echoData()
Figure 7: Queue Status at Start of auxiliary Task
Execution Point 8
This point occurs just after a character has been received. The signalCharacter function
executes and signals an event. The RTOS checks the event queue for the event, and makes
the highest priority task ready to execute. In this case the echoData task is made ready.
The RTOS then determines if the new task is higher priority than the executing task. Since
the echoData task is higher priority than the auxiliary task, a task switch occurs. The
auxiliary task is placed on the Ready queue. The echoData task executes.
Note the position of auxiliary in the Ready queue. The main task will execute before it at
the next task switch.
Event 10 Queue
Ready Queue
4
4
3
3
2
2
1
main()
0
null()
auxiliary()
Running Task
echoData()
1
0
Figure 8: Queue Status after Character Received
Execution Point 9
This point occurs just after the echoData task waits for the character-received event. It is
placed on the event 10 queue. The highest priority task on the ready queue – main – is
given the processor and executes.
TelePACE C Tools User and Reference Manual
May 9, 2007
36
Event 10 Queue
Ready Queue
4
4
3
3
2
2
1
auxiliary()
1
0
null()
0
Running Task
main()
echoData()
Figure 9: Queue Status after echoData Waits for Event
Overview of Programming
Functions
This section of the User Manual provides and overview of the Functions, Macros, Structure
and Types available to the user. The Functions, Macros, Structure and Types overview is
separated into sections of related functions. Refer to the Function Specification, C Tools
Macros and C Tools Structures and Types section of this manual for detailed explanations of
the Functions, Macros, Structure and Types described here.
Controller Operation
This section of the manual provides an overview of the TelePACE functions relating to
controller operation. These functions are provided in addition to the run-time library supplied
with the Microtec C compiler.
Start Up Functions
There are two library functions related to the system or application start up task. Refer to the
Function Specification section for details on each function listed.
startup_task
Returns the address of the system start up routine.
system_start
The default start up routine.
Start Up Macros
The ctools.h file defines the following macros for use with the start up task. Refer to the C
Tools Macros section for details on each macro listed.
STARTUP_APPLICATION
Specifies the application start up task.
STARTUP_SYSTEM
Specifies the system start up task.
Start Up Task Info Structure
The ctools.h file defines the structure Start Up Information Structure for use with the
startup_task function. Refer to the C Tools Structures and Types section for complete
information on structures and enumeration types.
TelePACE C Tools User and Reference Manual
May 9, 2007
37
Program Status Information Functions
There are five library functions related to controller program status information. Refer to the
Function Specification section for details on each function listed.
applicationChecksum Returns the application program checksum.
getBootType
Returns the controller boot up status.
getProgramStatus
Returns the application program execution status.
setBootType
Sets the controller boot up status.
setProgramStatus
Sets the application program execution status.
Program Status Information Macros
The ctools.h file defines the following macros for use with controller program information.
Refer to the C Tools Macros section for details on each macro listed.
NEW_PROGRAM
Application program is newly loaded.
PROGRAM_EXECUTED
Application program has been executed.
COLD_BOOT
Controller started in COLD BOOT mode.
RUN
Controller started in RUN mode.
SERVICE
Controller started in SERVICE mode.
REENTRY_BOOT
Controller Information Functions
There is one library function related to controller information. Refer to the Function
Specification section for details on the function listed.
getControllerID
Returns the controller ID string.
Controller Information Macros
The ctools.h file defines the following macros for use with controller information. Refer to
the Function Specification section for details on each macro listed.
protocol firmware option
AB_PROTOCOL
DF1
BASE_TYPE_MASK
Controller type bit mask
FT_NONE
Unknown firmware type
FT_TELEPACE
TelePACE firmware type
FT_ISAGRAF
ISaGRAF firmware type
GASFLOW
Gas Flow calculation firmware option
RUNS_2
Set if Gas Flow supports two meter runs
SCADAPACK
SCADAPack controller
SCADAPACK_LIGHT
SCADAPack LIGHT controller
SCADAPACK_PLUS
SCADAPack PLUS controller
UNKNOWN_CONTOLLER
Unknown controller type
TelePACE C Tools User and Reference Manual
May 9, 2007
38
Firmware Version Information Functions
There is one function related to the controller firmware version. Refer to the Function
Specification section for details.
getVersion
Returns controller firmware version information.
Firmware Version Information Macros
The ctools.h file defines the following macros for use with the firmware version function.
Refer to the C Tools Macros section for details on each macro listed.
VI_DATE_SIZE
Number of characters in the version information date field.
VI_STRING_SIZE
Number of characters in the version information copyright field.
Firmware Version Information Structure
The ctools.h file defines the structure Version Information Structure for controller
firmware version information. Refer to the C Tools Structures and Types section for
complete information on structures and enumeration types.
Sleep Mode Functions
SCADAPack controllers are capable of extremely low power operation when in sleep mode.
SCADAPack controllers enter the sleep mode under control of the application program.
Refer to the SCADAPack System Hardware Manual for further information on controller
sleep mode. The SCADAPack 100 and the SCADASesne series of controllers do not
support sleep mode.
There are three library functions related to sleep mode. Refer to the Function Specification
section for details on each function listed.
getWakeSource
Gets wake up sources
setWakeSource
Sets wake up sources
sleep
Put controller into sleep mode
Sleep Mode Macros
The ctools.h file defines the following macros for use sleep mode. Refer to the C Tools
Macros section for details on each macro listed.
SLEEP_MODE_SUPPORTED
Defined if sleep function is supported
WS_ALL
All wake up sources enabled
WS_COUNTER_0_OVERFLOW
Bit mask to enable counter 0 overflow as wake up source
WS_COUNTER_1_OVERFLOW
Bit mask to enable counter 1 overflow as wake up source
WS_COUNTER_2_OVERFLOW
Bit mask to enable counter 2 overflow as wake up source
WS_INTERRUPT_INPUT
Bit mask to enable interrupt input as wake up source
WS_LED_POWER_SWITCH
Bit mask to enable LED power switch as wake up source
WS_NONE
No wake up source enabled
WS_REAL_TIME_CLOCK
Bit mask to enable real time clock as wake up source
WS_UNDEFINED
Undefined wake up source
TelePACE C Tools User and Reference Manual
May 9, 2007
39
Power Management Functions
Under normal operation, the SCADAPack 350 operates on a CPU clock frequency of 32
MHz. However, the SCADAPack 350 controller is capable of operating on a reduced CPU
clock frequency of 8 MHz, known as Reduced Power Mode.
Further power savings can be realized on the SCADAPack 350 controller by disabling the
LAN or USB peripheral and host ports. Activation of Reduced Power mode as well as the
deactivation of the communication ports can be performed by the application program.
The library functions associated with the aforementioned power management allows for the
following:
•
The CPU speed can be changed from full speed (32 MHz) to reduced speed (8 MHz).
•
The LAN port can be enabled or disabled
•
The USB peripheral port can be enabled or disabled
•
The USB host port can be enabled or disabled.
The Power Mode LED blinks once a second when the controller is operating in Reduced
Power Mode.
The library functions associated with the power management features are listed below.
Refer to the Function Specification section for details on each function listed.
getPowerMode
Gets the current power mode
setPowerMode
Sets the power mode
Power Management Macros
The ctools.h file defines the following macros for use in the power management functions.
Refer to the C Tools Macros section for details on each macro listed.
PM_CPU_FULL
The CPU is set to run at full speed
PM_CPU_REDUCED
The CPU is set to run at a reduced speed
PM_CPU_SLEEP
The CPU is set to sleep mode
PM_LAN_ENABLED
The LAN is enabled
PM_LAN_DISABLED
The LAN is disabled
PM_USB_PERIPHERAL_ENABLED
The USB peripheral port is enabled
PM_USB_PERIPHERAL_DISABLED
The USB peripheral port is disabled
PM_USB_HOST_ENABLED
The USB host port is enabled
PM_USB_HOST_DISABLED
The USB host port is disabled
PM_UNAVAILABLE
The status of the device could not be read
Configuration Data EEPROM Functions
The EEPROM is nonvolatile memory used to store configuration parameters. The
application program cannot store application data into this memory. It can cause the system
configuration parameters to be written, using the save function.
The contents of the EEPROM are copied to RAM under two conditions: during a RUN boot
of the controller; and when the application program executes the load function.
The following data is loaded on a RUN boot; otherwise default information is used:
TelePACE C Tools User and Reference Manual
May 9, 2007
40
•
serial port configuration tables
•
protocol configuration tables
•
enable store and forward settings
•
LED power settings
•
mask for wake-up sources
•
execution period on power-up for each PID
There are two library functions related to the configuration data EEPROM. Refer to the
Function Specification section for details on each function listed.
Save
Writes configuration data from RAM to EEPROM
load
Reads configuration data from EEPROM into RAM
Configuration Data EEPROM Macros
The ctools.h file defines the following macros for use with the configuration data EEPROM.
Refer to the C Tools Macros section for details on each macro listed.
EEPROM_EVERY
EEPROM section loaded to RAM on every CPU reboot.
EEPROM_RUN
EEPROM section loaded to RAM on RUN type boots only.
EEPROM_SUPPORTED
If defined, indicates that there is an EEPROM in the controller.
I/O Bus Communication Functions
The ctools.h file defines the following functions that access the I/O bus. The I/O bus is I2C
compatible. Refer to the Function Specification section for details on each function listed.
ioBusReadByte
Reads one byte from an I2C slave device
ioBusReadLastByte
Reads one byte from an I2C slave device and terminates read
ioBusReadMessage
Reads a message from an I2C slave device
ioBusSelectForRead Selects an I2C slave device for reading
ioBusSelectForWrite Selects an I2C slave device for writing
ioBusStart
Issues an I2C bus START condition
ioBusStop
Issues an I2C bus STOP condition
ioBusWriteByte
Writes one byte to an I2C slave device
ioBusWriteMessage
Writes a message to an I2C slave device
I/O Bus Communication Macros
The ctools.h file defines the following macros for use with I/O Bus Communication. Refer to
the C Tools Macros section for details on each macro listed.
The ctools.h file defines the following macros.
READSTATUS
enumeration type ReadStatus
WRITESTATUS
enumeration type WriteStatus
TelePACE C Tools User and Reference Manual
May 9, 2007
41
I/O Bus Communication Types
The ctools.h file defines the enumeration types ReadStatus and WriteStatus. Refer to the
C Tools Structures and Types section for complete information on structures and
enumeration types.
System Functions
The ctools.h file defines the following functions for system initialization and for retrieving
system information. Some of these functions are primarily used in the appstart.c routine,
having limited use in an application program.
Refer to the Function Specification section for details on each function listed.
applicationChecksum Returns the application program checksum.
ioClear
Clears all I/O points
ioDatabaseReset
Resets the controller to default settings.
ioRefresh
Refresh outputs with internal data
ioReset
Reset all I/O modules
Controller I/O Hardware
This section of the manual provides an overview of the TelePACE C Tools functions relating
to controller signal input and output (I/O). These functions are provided in addition to the runtime library supplied with the Microtec C compiler.
Analog Input Functions
The controller supports internal analog inputs and external analog input modules. Refer to
the SCADAPack System Hardware Manual for further information on controller analog
inputs and analog input modules.
There are several library functions related to internal analog inputs and analog input
modules. Refer to the Function Specification section for details on each function listed.
readBattery
Read the controller RAM battery voltage.
readThermistor
Read the controller ambient temperature sensor.
readInternalAD
Read the controller internal AD converter.
ioRead4Ain
Read 4 analog inputs into I/O database.
ioRead8Ain
Read 8 analog inputs into I/O database.
IoRead4202Inputs
Read the digital, counter and analog inputs from a SCADASense
4202 DR.
IoRead4202DSInputs Read the digital, counter and analog inputs from a SCADASense
4202 DS.
ioRead5505Inputs
Read the digital and analog inputs from a 5505 I/O Module.
ioRead5506Inputs
Read the digital and analog inputs from a 5506 I/O Module.
ioRead5601Inputs
Read the digital and analog inputs from a SCADAPack 5601 I/O
Module.
TelePACE C Tools User and Reference Manual
May 9, 2007
42
ioRead5602Inputs
Read the digital and analog inputs from a SCADAPack 5602 I/O
Module.
ioRead5604Inputs
Read the digital and analog inputs from a SCADAPack 5604 I/O
Module.
ioRead5606Inputs
Read the digital and analog inputs from a 5606 I/O Module.
ioReadLPInputs
Read the digital and analog inputs from the SCADAPack LP I/O.
ioReadSP100Inputs Read the digital and analog inputs from the SCADAPack 100 I/O.
Analog Input Macros
The ctools.h file defines the following macros for use with controller analog inputs. Refer to
the C Tools Macros section for details on each macro listed.
AD_BATTERY
Internal AD channel connected to lithium battery.
AD_THERMISTOR
Internal AD channel connected to thermistor.
T_CELSIUS
Specifies temperatures in degrees Celsius.
T_FAHRENHEIT
Specifies temperatures in degrees Fahrenheit.
T_KELVIN
Specifies temperatures in degrees Kelvin.
T_RANKINE
Specifies temperatures in degrees Rankine.
Analog Output Functions
The controller supports external analog output modules. Refer to the SCADAPack System
Hardware Manual for further information on these modules.
There are three library functions related to analog output modules. Refer to the Function
Specification section for details on each function listed.
ioWriteAout
Write to 4 analog outputs from I/O database.
ioWrite2Aout
Write to 2 analog outputs from I/O database.
ioWrite4Aout
Write to 4 analog outputs from I/O database.
IoWrite4202Outputs Write to the analog outputs of a SCADASense 4202 DR.
IoWrite4202OutputsEx Write to analog outputs of a SCADASense 4202 DR with extended
IO (4202 DR with a digital output).
ioWrite5303Aout
Write to analog outputs of the 5303 module from I/O database.
ioWrite5606Outputs Write to the digital and analog outputs of 5606 I/O Module.
ioWriteLPOutputs
Writes data to the digital and analog outputs of the SCADAPack LP
I/O.
Digital Input Functions
The controller supports internal digital inputs and external digital input modules. Refer to the
SCADAPack System Hardware Manual for further information on controller digital inputs
and digital input modules.
There are several library functions related to digital inputs and external digital input modules.
Refer to the Function Specification section for details on each function listed.
interruptInput
Read the controller interrupt input.
TelePACE C Tools User and Reference Manual
May 9, 2007
43
readCounterInput
Read the status of the counter input points on the controller board.
ioRead8Din
read 8 digital inputs into I/O database.
ioRead16Din
read 16 digital inputs into I/O database.
IoRead32Din
read 32 digital inputs into I/O database.
IoRead4202Inputs
Read the digital, counter and analog inputs from a SCADASense
4202 DR.
IoRead4202DSInputs Read the digital, counter and analog inputs from a SCADASense
4202 DS.
ioRead5505Inputs
Read the digital and analog inputs from a 5505 I/O Module.
ioRead5506Inputs
Read the digital and analog inputs from a 5506 I/O Module.
ioRead5601Inputs
Read the digital and analog inputs from a 5601 I/O Module.
ioRead5602Inputs
Read the digital or analog inputs from a 5602 I/O Module.
ioRead5604Inputs
Read the digital and analog inputs from a SCADAPack 5604 I/O
Module.
ioRead5606Inputs
Read the digital and analog inputs from a 5606 I/O Module.
ioReadLPInputs
Read the digital and analog inputs from the SCADAPack LP I/O.
ioReadSP100Inputs Read the digital and analog inputs from the SCADAPack 100 I/O.
Digital Output Functions
The controller supports external digital output modules. Refer to the SCADAPack System
Hardware Manual for further information on controller digital output modules.
There are several library functions related to digital output modules. Refer to the Function
Specification section for details on each function listed.
interruptInput
Read the controller interrupt input.
ioWrite16Dout
Write data to any 16 point Digital output module.
IoWrite32Dout
Write data to any 32 point Digital output module.
IoWrite4202OutputsEx Write to digital and analog outputs of the SCADASense 4202 DR
with extended IO (with digital output) from I/O database.
IoWrite4202DSOutputs Write to digital outputs of the SCADASense 4202 DS from I/O
database.
ioWrite5601Outputs Write to the digital and analog outputs of SCADAPack 5601 I/O
Module.
ioWrite5602Outputs Write to the digital and analog outputs of SCADAPack 5602 I/O
Module.
ioWrite5604Outputs Write to the digital and analog outputs of SCADAPack 5604 I/O
Module.
ioWrite5606Outputs Write to the digital and analog outputs of 5606 I/O Module.
ioWrite8Dout
Write data to any 8 point Digital output module.
ioWriteLPOutputs
Writes data to the digital and analog outputs of the SCADAPack LP
I/O.
TelePACE C Tools User and Reference Manual
May 9, 2007
44
ioWriteSP100utputs Writes data to the digital outputs of the SCADAPack 100 I/O.
Counter Input Functions
The controller supports internal counters and external counter modules. The counter
registers are 32 bits, for a maximum count of 4,294,967,295. They roll over to 0 on the next
count. The counter inputs measure the number of rising inputs. Refer to the SCADAPack
System Hardware Manual for further information on controller counter inputs and counter
input modules.
There are four library functions related to counters. Refer to the Function Specification
section for details on each function listed.
readCounter
Read a SCADAPack, SCADAPack LP or SCADAPack 100 counter
with or without automatic clearing of the counter register.
interruptCounter
Read the SCADAPack or SCADAPack LP interrupt input as a
counter with or without automatic clearing of the counter value.
ioRead4Counter
Read any 4 point Counter input module.
IoRead4202Inputs
Read the digital, counter and analog inputs from a SCADASense
4202 DR.
IoRead4202DSInputs Read the digital, counter and analog inputs from a SCADAense
4202 DS.
Counter Input Macros
The ctools.h file defines the following macro for use with counter inputs. Refer to the C
Tools Macros section for details.
LOCAL_COUNTERS
Number of controller counter inputs.
Status LED and Output Functions
The status LED and output indicate alarm conditions. The STAT LED blinks and the
STATUS output opens when an alarm occurs. The STAT LED turns off and the STATUS
output closes when all alarms clear.
The STAT LED blinks a binary sequence indicating alarm codes. The sequences consist of
long and short flashes, followed by an off delay of 1 second. The sequence then repeats.
The sequence may be read as the Controller Status Code.
Refer to the SCADAPack System Hardware Manual for further information on the status
LED and digital output. There is no status output on the SCADASense series of
programmable controllers.
There are two library functions related to the status LED and digital output. Refer to the
Function Specification section for details on each function listed.
clearStatusBit
Clears bits in controller status code.
setStatusBit
Sets the bits
in controller status code.
Status LED and Output Macros
The ctools.h file defines the following macros for use with the status LED and digital output.
Refer to the C Tools Macros section for details on each macro listed.
TelePACE C Tools User and Reference Manual
May 9, 2007
45
S_MODULE_FAILURE
Status LED code for I/O module communication failure
S_NORMAL
Status LED code for normal status
Options Switches Functions
The controller has three option switches located under the cover of the controller module.
These switches are labeled OPTION 1,2 and 3. The option switches are user defined except
when a SCADAPack I/O module or SCADAPack AOUT module used. In this case option
switches 1 and 2 select the analog ranges. Refer to the SCADAPack System Hardware
Manual for further information on option switches.
There are no option switches on the SCADAPack 100, SCADAPack LP or the SCADASense
series of programmable controllers.
There is one library function related to the controller option switches. Refer to the Function
Specification section for details.
optionSwitch
Read option switch states.
Option Switches Macros
The ctools.h file defines the following macros for use with option switches. Refer to the C
Tools Macros section for details on each macro listed.
CLOSED
Specifies switch is in closed position
OPEN
Specifies switch is in open position
LED Indicators Functions
An application program can control three LED indicators.
The RUN LED indicates the execution status of the program. The LED can be on or off. It
remains in the last state until changed.
The STAT LED indicates error conditions. It outputs an error code as a binary sequence.
The sequence repeats until a new error code is output. If the error code is zero, the status
LED turns off.
The FORCE LED indicates locked I/O variables. Use this function with caution in application
programs.
There are three library functions related to the LED indicators. Refer to the Function
Specification section for details on each function listed.
runLed
Controls the RUN LED status.
setStatus
Sets controller status code.
forceLed
Sets state of the force LED.
LED Indicators Macros
The ctools.h file defines the following macros for use with LED power control. Refer to the C
Tools Macros section for details on each macro listed.
LED_OFF
Specifies LED is to be turned off.
LED_ON
Specifies LED is to be turned on.
TelePACE C Tools User and Reference Manual
May 9, 2007
46
LED Power Control Functions
The controller board can disable the LEDs on the controller board, the 5601, 5602 or 5604
I/O modules and the 5000 Series I/O modules to conserve power. This is particularly useful
in solar powered or unattended installations. Refer to the SCADAPack System Hardware
Manual for further information on LED power control.
There are four library functions related to LED power control. Refer to the Function
Specification section for details on each function listed.
ledGetDefault
Get default LED power state
ledPow er
Set LED power state
ledPow erSwitch
Read LED power switch
ledSetDefault
Set default LED power state
LED Power Control Macros
The ctools.h file defines the following macros for use with LED power control. Refer to the C
Tools Macros section for details on each macro listed.
LED_OFF
Specifies LED is to be turned off.
LED_ON
Specifies LED is to be turned on.
LED Power Control Structure
The ctools.h file defines the structure LED Power Control Structure for LED power control
information. Refer to the C Tools Structures and Types section for complete information
on structures and enumeration types.
Software Timer Functions
The controller provides 32 powerful software timers, which greatly simplify the task of
programming time-related functions. Uses include:
•
generation of time delays
•
timing of process events such as tank fill times
•
generation of time-based interrupts to schedule regular activities
•
control of digital outputs by time periods
The 32 timers are individually programmable for tick rates from ten per second to once every
25.5 seconds. Time periods from 0.1 second to greater than nineteen days can be
measured and controlled.
All timers operate in the background from a hardware interrupt generated by the main
system clock. Once loaded, they count without intervention from the main program.
There are four library functions related to timers. Refer to the Function Specification
section for details on each function listed.
interval
Set timer tick interval in tenths of seconds.
settimer
Set a timer. Timers count down from the set value to zero.
timer
Read the time period remaining in a timer.
read_timer_info
Read information about a software timer.
TelePACE C Tools User and Reference Manual
May 9, 2007
47
Software Timer Macros
The ctools.h file defines the following macros for use with timers. Refer to the C Tools
Macros section for details on each macro listed.
NORMAL
Specifies normal count down timer.
TIMED_OUT
Specifies timer is has reached zero.
TIMER_BADINTERVAL
Error code indicating invalid timer interval.
TIMER_BADTIMER
Error code indicating invalid timer.
TIMER_BADVALUE
Error code indicating invalid time value.
TIMER_MAX
Number of last valid software timer.
Timer Information Structure
The ctools.h file defines the structure Timer Information for timer information. Refer to the
C Tools Structures and Types section for complete information on structures and
enumeration types.
Timer Example Programs
Example 1: Turn on a digital output assigned to coil register 1 and w ait 5 seconds
before turning it off.
interval(0,10); /* timer 0 tick rate = 1 second */
request_resource(IO_SYSTEM);
setdbase(MODBUS, 1, 1); /* turn on output */
release_resource(IO_SYSTEM);
settimer(0,5);
/* load timer 0 with 5 seconds */
while(timer(0)) /* wait until time expires */
{
/* Allow other tasks to execute */
release_processor();
}
request_resource(IO_SYSTEM);
setdbase(MODBUS, 1, 0); /* shut off output */
release_resource(IO_SYSTEM);
Example 2: Time the duration a contact is on but wait in loop to measure time.
Contact is assigned to status register 10001.
interval(0,1);
/* tick rate = 0.1 second */
request_resource(IO_SYSTEM);
if (dbase(MODBUS, 10001)) /* test if contact is on */
{
settimer(0,63000); /* start timer */
while(dbase(MODBUS, 10001)) /* wait for turn off */
{
/* Allow other tasks to execute */
release_resource(IO_SYSTEM);
release_processor();
request_resource(IO_SYSTEM);
}
printf("time period = %u\r\n",63000-timer(0));
}
release_resource(IO_SYSTEM);
Example 3: Open valve to fill tank and print alarm message if not full in 1 minute.
Contact is assigned to status register 10001. Valve is controlled by coil register 1.
TelePACE C Tools User and Reference Manual
May 9, 2007
48
interval(0,10); /* timer 0 tick rate = 1 second */
request_resource(IO_SYSTEM);
setdbase(MODBUS, 1, 1);
/* open valve */
settimer(0,60); /* set timer for 1 minute */
/* tank not full if contact is off */
while((dbase(MODBUS, 10001)== 0) && timer(0))
{
/* Allow other tasks to execute */
release_resource(IO_SYSTEM);
release_processor();
request_resource(IO_SYSTEM);
}
if (dbase(MODBUS, 10001)== 0)
puts("tank is not filling!!\r\n");
else
puts("tank full\r\n");
setdbase(MODBUS, 1, 0); /* close valve */
release_resource(IO_SYSTEM);
Real Time Clock Functions
The controller is provided with a hardware based real time clock that independently
maintains the time and date for the operating system. The time and date remain accurate
during power-off. This allows the controller to be synchronized to time of day for such
functions as shift production reports, automatic instrument calibration, energy logging, etc.
The calendar can be used to automatically take the controller off-line during weekends and
holidays. The calendar automatically handles leap years.
There are eight library functions, which access the real-time clock. Refer to the Function
Specification section for details on each function listed.
alarmIn
Returns absolute time of alarm given elapsed time
getclock
Read the real time clock.
getClockAlarm
Reads the real time clock alarm settings.
getClockTime
Read the real time clock.
installClockHandler Installs a handler for real time clock alarms.
resetClockAlarm
Resets the real time clock alarm so it will recur at the same time next
day.
setclock
Set the real time clock.
setClockAlarm
Sets real time clock alarm.
Real Time Clock Macros
The ctools.h file defines the following macros for real time clock alarms. Refer to the C
Tools Macros section for details on each macro listed.
AT_ABSOLUTE
Specifies a fixed time of day alarm.
AT_NONE
Disables alarms
Real Time Clock Structures
The ctools.h file defines the structures Real Time Clock Structure and Alarm Settings
Structure for real time clock information. Refer to the C Tools Structures and Types
section for complete information on structures and enumeration types.
TelePACE C Tools User and Reference Manual
May 9, 2007
49
Real Time Clock Program Example
The following program illustrates how the date and time can be set and displayed. All fields
of the clock structure must be set with valid values for the clock to operate properly.
#include
void main(void)
{
struct clock now;
/* Set to 12:01:00 on January 1, 1994 */
now.hour
now.minute
now.second
now.day
now.month
now.year
now.dayofweek
=
=
=
=
=
=
=
12;
1;
0;
1;
1;
94;
6;
/* set the time */
/* set the date */
/* day is Sat. */
request_resource(IO_SYSTEM);
setclock(&now);
now = getclock();
release_resource(IO_SYSTEM);
/* Display current hour, minute and second */
printf("%2d:%2d:%2d", now.hour, now.minute,
now.second);
}
The Jiffy Clock
The jiffy clock is a counter that increments 60 times per second. The jiffy clock is useful for
measuring execution times or generating delays where a fine time base is required. The
clock is reset to zero each time power is applied to the controller. It rolls over to zero after it
reaches a value of 5183999. This is the number of 1/60-second intervals in 24 hours.
There are two library functions, which access the real-time clock. Refer to the Function
Specification C Function Library chapter for a complete description.
setjiffy
set the jiffy clock
jiffy
read the jiffy clock
Watchdog Timer Functions
A watchdog timer is a hardware device, which enables rapid detection of computer hardware
or software problems. In the event of a major problem, the CPU resets and the application
program restarts.
The controller provides an integral watchdog timer to ensure reliable operation. The
watchdog timer resets the CPU if it detects a problem in either the hardware or system
firmware. A user program can take control of the watchdog timer, so it will detect abnormal
execution of the program.
A watchdog timer is a retriggerable, time delay timer. It begins a timing sequence every time
it receives a reset pulse. The time delay is adjusted so that regular reset pulses prevent the
timer from expiring. If the reset pulses cease, the watchdog timer expires and turns on its
output, signifying a malfunction. The timer output in the controller resets the CPU and turns
off all outputs at the I/O system.
TelePACE C Tools User and Reference Manual
May 9, 2007
50
The watchdog timer is normally reset by the operating system. This is transparent to the
application program. Operating in such a fashion, the watchdog timer detects any hardware
or firmware problems.
The watchdog timer can detect failure of an application program. The program takes control
of the timer, and resets it regularly. If unexpected operation of the program occurs, the reset
pulses cease, and the watchdog timer resets the CPU. The program restarts from the
beginning.
There are three library functions related to the watchdog timer. Refer to the Function
Specification section for details on each function listed.
wd_auto
Gives control of the watchdog timer to the operating system (default).
w d_manual
Gives control of the watchdog timer to an application program.
w d_pulse
Generates a watchdog reset pulse.
A watchdog reset pulse must be generated at least every 500 ms. The CPU resets, and
program execution starts from the beginning of the program, if the watchdog timer is not
reset.
Watchdog Timer Program Example
The following program segment shows how the watchdog timer could be used to detect the
failure of a section of a program.
wd_manual(); /* take control of watchdog timer */
do {
/* program code */
wd_pulse();
/* reset the watchdog timer */
}
while (condition)
wd_auto();
/* return control to OS */
Note:
Always pass control of the watchdog timer back to the operating system before
stopping a program, or switching to another task that expects the operating system
to reset the timer.
Checksum Functions
To simplify the implementation of self-checking communication algorithms, the C Tools
provide four types of checksums: additive, CRC-16, CRC-CCITT, and byte-wise exclusiveOR. The CRC algorithms are particularly reliable, employing various polynomial methods to
detect nearly all communication errors. Additional types of checksums are easily
implemented using library functions.
There are two library functions related to checksums. Refer to the Function Specification
section for details on each function listed.
checksum
Calculates additive, CRC-16, CRC-CCITT and exclusive-OR type
checksums
crc_reverse
Calculates custom CRC type checksum using reverse CRC
algorithm.
Checksum Macros
The ctools.h file defines macros for specifying checksum types. Refer to the C Tools
Macros section for details on each macro listed.
TelePACE C Tools User and Reference Manual
May 9, 2007
51
ADDITIVE
Additive checksum
BYTE_EOR
Byte-wise exclusive OR checksum
CRC_16
CRC-16 type CRC checksum (reverse algorithm)
CRC_CCITT
CCITT type CRC checksum (reverse algorithm)
Serial Communication
The SCADAPack family of controllers offers three or four RS-232 serial ports. The
TeleSAFE Micro16 has two RS-232 serial communication ports. (com1 on all controllers is
also available as an RS-485 port.) The ports are configurable for baud rate, data bits, stop
bits, parity and communication protocol.
To optimize performance, minimize the length of messages on com3 and com4. Examples
of recommended uses for com3 and com4 are for local operator display terminals, and for
programming and diagnostics using the ISaGRAF program.
For the SCADASense series of programmable controllers, com1 is not available for C
applications.
Default Serial Parameters
All ports are configured at reset with default parameters when the controller is powered up in
SERVICE mode. The ports use stored parameters when the controller is reset in the RUN
mode. The default parameters are listed below.
Parameter
Baud rate
Parity
Data bits
Stop bits
Duplex
Protocol
Station
Rx flow control
Tx flow control
Serial time out
Type
com1
9600
none
8
1
full
Modbus
RTU
1
off
off
60 s
RS-232
com2
9600
none
8
1
full
Modbus
RTU
1
off
off
60 s
RS-232
Com3
9600
None
8
1
Half
Modbus
RTU
1
Rx disable
Off
60 s
RS-232
Com4
9600
None
8
1
Half
Modbus RTU
1
Rx disable
Off
60 s
RS-232
Serial Communication Time Out
When the controller is transmitting data on the communication ports, the transmit buffer may
become full due to receipt of an XOFF character, a slow baud rate, or improper hardware
handshaking.
If the transmit buffers become full, the task transmitting data is blocked until space is
available or the serial time out period expires. If no space is available at the conclusion of
this time period, the transmit buffer is emptied. The task then continues execution.
Debugging Serial Communication
Serial communication can be difficult to debug. This section describes the most common
causes of communication failures.
TelePACE C Tools User and Reference Manual
May 9, 2007
52
•
To communicate, the controller and an external device must use the same
communication parameters. Check the parameters in both units.
•
If some but not all characters transmit properly, you probably have a parity or stop bit
mismatch between the devices.
The connection between two RS-232 Data Terminal Equipment (DTE) devices is made with
a null-modem cable. This cable connects the transmit data output of one device to the
receive data input of the other device – and vice versa. The controller is a DTE device. This
cable is described in the System Hardware Manual for your controller.
The connection between a DTE device and a Data Communication Equipment (DCE) device
is made with a straight cable. The transmit data output of the DTE device is connected to the
transmit data input of the DCE device. The receive data input of the DTE device is
connected to the receive data output of the DCE device. Modems are usually DCE devices.
This cable is described in the System Hardware Manual for your controller.
Many RS-232 devices require specific signal levels on certain pins. Communication is not
possible unless the required signals are present. In the controller the CTS line must be at
the proper level. The controller will not transmit if CTS is OFF. If the CTS line is not
connected, the controller will force it to the proper value. If an external device controls this
line, it must turn it ON for the controller to transmit.
Serial Communication Functions
The ctools.h file defines the following serial communication related functions. Refer to the
Function Specification section for details on each function listed. Additional serial
communication functions are included in the Microtec run-time library.
clear_errors
Clear serial port error counters.
clear_tx
Clear serial port transmit buffer.
get_port
Read serial port communication parameters.
GetPortCharacteristics
Read information about features supported by a serial port.
get_status
Read serial port status and error counters.
install_handler
Install serial port character received handler.
portConfiguration
Get pointer to port configuration table
portIndex
Get array index for serial port
portStream
Get serial port corresponding to index
queue_mode
Set serial port transmitter mode.
route
Redirect standard I/O streams.
setDTR
Control RS232 port DTR signal.
set_port
Set serial port communication parameters.
Serial Communication Macros
The ctools.h file defines macros for specifying serial communication parameters. Refer to
the C Tools Macros section for details on each macro listed.
BAUD75
Specifies 75-baud port speed.
BAUD110
Specifies 110-baud port speed.
BAUD150
Specifies 150-baud port speed.
TelePACE C Tools User and Reference Manual
May 9, 2007
53
BAUD300
Specifies 300-baud port speed.
BAUD600
Specifies 600-baud port speed.
BAUD1200
Specifies 1200-baud port speed.
BAUD2400
Specifies 2400-baud port speed.
BAUD4800
Specifies 4800-baud port speed.
BAUD9600
Specifies 9600-baud port speed.
BAUD19200
Specifies 19200-baud port speed.
BAUD38400
Specifies 38400-baud port speed.
BAUD57600
Specifies 57600-baud port speed.
BAUD115200
Specifies 115200-baud port speed.
com1
Points to a file object for com1 serial port.
com2
Points to a file object for com2 serial port.
com3
Points to a file object for com3 serial port.
com4
Points to a file object for com4 serial port.
DATA7
Specifies 7 bit world length.
DATA8
Specifies 8 bit word length.
DISABLE
Specifies flow control is disabled.
ENABLE
Specifies flow control is enabled.
EVEN
Specifies even parity.
FULL
Specifies full duplex.
FOPEN_MAX
Redefinition of macro from stdio.h
HALF
Specifies half duplex.
NONE
Specifies no parity.
NOTYPE
Specifies serial port type is not known.
ODD
Specifies odd parity.
PC_FLOW_RX_RECEIVE_STOP
Receiver disabled after receipt of a message.
PC_FLOW_RX_XON_XOFF
Receiver Xon/Xoff flow control.
PC_FLOW_TX_IGNORE_CTS
Transmitter flow control ignores CTS.
PC_FLOW_TX_XON_XOFF
Transmitter Xon/Xoff flow control.
RS232
Specifies serial port is an RS-232 port.
RS232_MODEM
Specifies serial port is an RS-232 dial-up modem.
RS485_4WIRE
Specifies serial port is a 4 wire RS-485 port.
SERIAL_PORTS
Number of serial ports.
SIGNAL_CTS
I/O line bit mask: clear to send signal
SIGNAL_DCD
I/O line bit mask: carrier detect signal
SIGNAL_OFF
Specifies a signal is de-asserted
SIGNAL_OH
I/O line bit mask: off hook signal
TelePACE C Tools User and Reference Manual
May 9, 2007
54
SIGNAL_ON
Specifies a signal is asserted
SIGNAL_RING
I/O line bit mask: ring signal
SIGNAL_VOICE
I/O line bit mask: voice/data switch signal
STOP1
Specifies 1 stop bit.
STOP2
Specifies 2 stop bits.
Serial Communication Structures
The ctools.h file defines the structures Serial Port Configuration, Serial Port Status and
Serial Port Characteristics for serial port configuration and information. Refer to the C
Tools Structures and Types section for complete information on structures and
enumeration types.
Microtec Serial I/O Functions
These library functions are related to serial communication. They are documented in the
Microtec MCCM77 Documentation Set.
fgetc
reads a character from a stream
fgets
reads a string from a stream
fputc
writes a character to a stream
fputs
writes a string to a stream
fread
reads from a stream
fwrite
writes to a stream
getc
reads a character from a stream
getchar
reads a character from standard input device
gets
reads a string from a stream
initport
re-initializes serial port
printf
formatted output to a stream
putc
writes a character to a stream
putchar
reads a character to standard output device
puts
writes a string to a stream
scanf
formatted input from a stream
Dial-Up Modem Functions
These library functions provide control of dial-up modems. They are used with external
modems connected to a serial port. An external modem normally connects to the RS-232
port with a DTE to DCE cable. Consult the System Hardware Manual for your controller for
details. Refer to the Function Specification section for details on each function listed.
Note:
The SCADAPack 100 does not support dial up connections on com port 1.
The SCADASense series of controllers do not support dial up connections.
modemInit
send initialization string to dial-up modem.
modemInitStatus
read status of modem initialization operation.
TelePACE C Tools User and Reference Manual
May 9, 2007
55
modemInitEnd
terminate modem initialization operation.
modemDial
connect with an external device using a dial-up modem.
modemDialStatus
read status of connection with external device using a dial-up
modem.
modemDialEnd
terminate connection with external device using a dial-up modem.
modemAbort
unconditionally terminate connection with external device or modem
initialization (used in task exit handler).
modemAbortAll
unconditionally terminate connections with external device or
modem initializations (used in task exit handler).
modemNotification
notify the dial-up modem handler that an interesting event has
occurred. This function is usually called whenever a message is
received by a protocol.
Dial-Up Modem Macros
The ctools.h file defines the following macros of interest to a C application program. Refer
to the C Tools Macros section for details on each macro listed.
MODEM_CMD_MAX_LEN
Maximum length of the modem initialization command string
PHONE_NUM_MAX_LEN
Maximum length of the phone number string
Dial-Up Modem Enumeration Types
The ctools.h file defines the enumerated types DialError and DialState. Refer to the
C Tools Structures and Types section for complete information on structures and
enumeration types.
Dial-up Modem Structures
The ctools.h file defines the structures ModemInit and ModemSetup. Refer to the C
Tools Structures and Types section for complete information on structures and
enumeration types.
Modem Initialization Example
The following code shows how to initialize a modem. Typically, the modem initialization is
used to prepare a modem to answer calls. The example sets up a Hayes modem to answer
incoming calls.
#include
void main(void)
{
struct ModemInit initSettings;
reserve_id portID;
enum DialError status;
enum DialState state;
struct pconfig portSettings;
/* Configure serial port
portSettings.baud
=
portSettings.duplex
=
portSettings.parity
=
portSettings.data_bits =
portSettings.stop_bits =
portSettings.flow_rx
=
portSettings.flow_tx
=
TelePACE C Tools User and Reference Manual
May 9, 2007
1 */
BAUD1200;
FULL;
NONE;
DATA8;
STOP1;
DISABLE;
DISABLE;
56
portSettings.type
portSettings.timeout
= RS232_MODEM;
= 600;
request_resource(IO_SYSTEM);
set_port(com1, &portSettings);
release_resource(IO_SYSTEM);
/* Initialize Hayes modem to answer incoming calls */
initSettings.port = com1;
strcpy(initSettings.modemCommand, " F1Q0V1X1 S0=1");
if (modemInit(&initSettings, &portID) == DE_NoError)
{
do
{
/* Allow other tasks to execute */
release_processor();
/* Wait for the initialization to complete */
modemInitStatus(com1, portID, &status, &state);
}
while (state == DS_Calling);
/* Terminate the initialization */
modemInitEnd(com1, portID, &status);
}
}
Connecting with a Remote Controller Example
The following code shows how to connect to a remote controller using a modem. The
example uses a US Robotics modem. It also demonstrates the use of the modemAbort
function in an exit handler.
#include
/* -------------------------------------------The shutdown function aborts any active
modem connections when the task is ended.
-------------------------------------------- */
void shutdown(void)
{
modemAbort(com1);
}
void main(void)
{
struct ModemSetup dialSettings;
reserve_id portID;
enum DialError status;
enum DialState state;
struct pconfig portSettings;
TASKINFO taskStatus;
/* Configure serial port 1 */
portSettings.baud
= BAUD19200;
portSettings.duplex
= FULL;
portSettings.parity
= NONE;
portSettings.data_bits = DATA8;
portSettings.stop_bits = STOP1;
portSettings.flow_rx
= DISABLE;
portSettings.flow_tx
= DISABLE;
portSettings.type
= RS232_MODEM;
portSettings.timeout
= 600;
request_resource(IO_SYSTEM);
set_port(com1, &portSettings);
release_resource(IO_SYSTEM);
/* Configure US Robotics modem */
dialSettings.port
= com1;
dialSettings.dialAttempts = 3;
dialSettings.detectTime
= 60;
dialSettings.pauseTime
= 30;
dialSettings.dialmethod
= 0;
strcpy(dialSettings.modemCommand, "&F1 &A0 &K0 &M0 &B1");
TelePACE C Tools User and Reference Manual
May 9, 2007
57
strcpy(dialSettings.phoneNumber, "555-1212");
/* set up exit handler for this task */
taskStatus = getTaskInfo(0);
installExitHandler(taskStatus.taskID, shutdown);
/* Connect to the remote controller */
if (modemDial(&dialSettings, &portID) == DE_NoError)
{
do
{
/* Allow other tasks to execute */
release_processor();
/* Wait for initialization to complete */
modemDialStatus(com1, portID, &status, &state);
}
while (state == DS_Calling);
/* If the remote controller connected */
if (state == DS_Connected)
{
/* Talk to remote controller here */
}
/* Terminate the connection */
modemDialEnd(com1, portID, &status);
}
}
Note that a pause of a few seconds is required between terminating a connection and
initiating a new call. This pause allows the external modem time to hang up.
Communication Protocols
The TeleBUS protocols are compatible with the widely used Modbus RTU and ASCII
protocols. The TeleBUS communication protocols provide a standard communication
interface to SCADAPack controllers. Additional TeleBUS commands provide remote
programming and diagnostics capability.
The TeleBUS protocols provide full access to the I/O database in the controller. The I/O
database contains user-assigned registers and general purpose registers. Assigned
registers map directly to the I/O hardware or system parameter in the controller. General
purpose registers can be used by ladder logic and C application programs to store
processed information, and to receive information from a remote device.
The TeleBUS protocols operate on a wide variety of serial data links. These include RS-232
serial ports, RS-485 serial ports, radios, leased line modems, and dial up modems. The
protocols are generally independent of the communication parameters of the link, with a few
exceptions.
Application programs can initiate communication with remote devices. A multiple port
controller can be a data concentrator for remote devices, by polling remote devices on one
port(s) and responding as a slave on another port(s).
The protocol type, communication parameters and station address are configured separately
for each serial port on a controller. One controller can appear as different stations on
different communication networks. The port configuration can be set from an application
program, from the TelePACE programming software, or from another Modbus or DF1
compatible device.
Protocol Type
The protocol type may be set to emulate the Modbus ASCII and Modbus RTU protocols, or it
may be disabled. When the protocol is disabled, the port functions as a normal serial port.
TelePACE C Tools User and Reference Manual
May 9, 2007
58
The DF1 option enables the emulation of the DF1 protocols.
The DNP (Distributed Network Protocol) option enables DNP. See the DNP
Communication Protocol section for details on this protocol.
Station Number
The TeleBUS protocol allows up to 254 devices on a network using standard addressing
and up to 65534 devices using extended addressing. Station numbers identify each device.
A device responds to commands addressed to it, or to commands broadcast to all stations.
The station number is in the range 1 to 254 for standard addressing and 1 to 65534 for
extended addressing. Address 0 indicates a command broadcast to all stations, and cannot
be used as a station number. Each serial port may have a unique station number.
The TeleBUS DF1 protocols allow up to 255 devices on a network. Station numbers identify
each device. A device responds to commands addressed to it, or to commands broadcast to
all stations. The station number is in the range 0 to 254. Address 255 indicates a command
broadcast to all stations, and cannot be used as a station number. Each serial port may
have a unique station number.
Store and Forward Messaging
Store and forward messaging re-transmits messages received by a controller. Messages
may be re-transmitted on any serial port, with or without station address translation. A userdefined translation table determines actions performed for each message. Store and forward
messaging may be enabled or disabled on each port. It is disabled by default.
Store and forward messaging is not supported by DNP or TeleBUS DF1 protocol.
Communication Protocols Functions
There are several library functions related to TeleBUS communication protocol. Refer to the
Function Specification section for details on each function listed.
checkSFTranslationTable
Check translation table for invalid entries.
clear_protocol_status
Clears protocol message and error counters.
clearSFTranslationTable
Clear all store and forward translation table entries.
enronInstallCommandHandler
Installs handler for Enron Modbus commands.
getABConfiguration
Reads DF1 protocol configuration parameters.
get_protocol
Reads protocol parameters.
getProtocolSettings
Reads extended addressing protocol parameters for a
serial port.
getProtocolSettingsEx
Reads extended addressing and Enron Modbus protocol
parameters for a serial port.
get_protocol_status
Reads protocol message and error counters.
getSFMapping
This function is a stub and no longer performs a necessary
operation.
getSFTranslation
Read store and forward translation table entry.
installModbusHandler
This function allows user-defined extensions to standard
Modbus protocol.
TelePACE C Tools User and Reference Manual
May 9, 2007
59
master_message
Sends a protocol message to another device.
modbusExceptionStatus
Sets response for the read exception status function.
modbusSlaveID
Sets response for the read slave ID function.
pollABSlave
Requests a response from a slave controller using the halfduplex version of the protocol.
resetAllABSlaves
Clears responses from the response buffers of half-duplex
slave controllers.
setABConfiguration
Defines DF1 protocol configuration parameters.
set_protocol
Sets protocol parameters and starts protocol.
setProtocolSettings
Sets extended addressing protocol parameters for a serial
port.
setProtcolSettingEx
Sets extended addressing and Enron Modbus protocol
parameters for a serial port.
setSFMapping
This function is a stub and no longer performs a necessary
operation.
setSFTranslation
Write store and forward translation table entry.
start_protocol
Starts protocol execution based on stored parameters.
Communication Protocols Macros
The ctools.h file defines macros for specifying communication protocol parameters. Refer to
the C Tools Macros section for details on each macro listed.
AB_FULL_BCC
Specifies the DF1 Full Duplex protocol emulation for
the serial port. (BCC checksum)
AB_FULL_CRC
Specifies the DF1 Full Duplex protocol emulation for
the serial port. (CRC checksum)
AB_HALF_BCC
Specifies the DF1 Half Duplex protocol emulation for
the serial port. (BCC checksum)
AB_HALF_CRC
Specifies the DF1 Half Duplex protocol emulation for
the serial port. (CRC checksum)
FORCE_MULTIPLE_COILS
Modbus function code
FORCE_SINGLE_COIL
Modbus function code
LOAD_MULTIPLE_REGISTERS
Modbus function code
LOAD_SINGLE_REGISTER
Modbus function code
MM_BAD_ADDRESS
Master message status: invalid database address
MM_BAD_FUNCTION
Master message status: invalid function code
MM_BAD_LENGTH
Master message status: invalid message length
MM_BAD_SLAVE
Master message status: invalid slave station address
MM_NO_MESSAGE
Master message status: no message was sent.
MM_PROTOCOL_NOT_SUPPORTED
Master message status: selected protocol is not
supported.
MM_RECEIVED
Master message status: response was received.
TelePACE C Tools User and Reference Manual
May 9, 2007
60
MM_SENT
Master message status: message was sent.
MM_EOT
Master message status: DF1 slave response was an
EOT message
MM_WRONG_RSP
Master message status: DF1 slave response did not
match command sent
MM_CMD_ACKED
Master message status: DF1 half duplex command
has been acknowledged by slave – Master may now
send poll command
MM_EXCEPTION_FUNCTION
Master message status: Modbus slave returned a
function exception
MM_EXCEPTION_ADDRESS
Master message status: Modbus slave returned an
address exception
MM_EXCEPTION_VALUE
Master message status: Modbus slave returned a
value exception
MM_RECEIVED_BAD_LENGTH
Master message status: response received with
incorrect amount of data.
MODBUS_ASCII
Specifies the Modbus ASCII protocol emulation for
the serial port.
MODBUS_RTU
Specifies the Modbus RTU protocol emulation for the
serial port.
NO_PROTOCOL
Specifies no communication protocol for the serial
port.
READ_COIL_STATUS
Modbus function code
READ_EXCEPTION_STATUS
Modbus function code
READ_HOLDING_REGISTER
Modbus function code
READ_INPUT_REGISTER
Modbus function code
READ_INPUT_STATUS
Modbus function code
REPORT_SLAVE_ID
Modbus function code
SF_ALREADY_DEFINED
Result code: translation is already defined in the
table
SF_INDEX_OUT_OF_RANGE
Result code: invalid translation table index
SF_NO_TRANSLATION
Result code: entry does not define a translation
SF_PORT_OUT_OF_RANGE
Result code: serial port is not valid
SF_STATION_OUT_OF_RANGE
Result code: station number is not valid
SF_TABLE_SIZE
Number of entries in the store and forward table
SF_VALID
Result code: translation is valid
Communication Protocols Enumeration Types
The ctools.h file defines the enumeration type ADDRESS_MODE. Refer to the C Tools
Structures and Types section for complete information on structures and enumeration
types.
TelePACE C Tools User and Reference Manual
May 9, 2007
61
Communication Protocols Structures
The ctools.h file defines the structures Protocol Status Information, Protocol Settings,
Extended Protocol Settings, Store and Forward Message and Store and Forward
Status. Refer to the C Tools Structures and Types section for complete information on
structures and enumeration types.
DNP Communication Protocol
DNP, the Distributed Network Protocol, is a standards-based communications protocol
developed to achieve interoperability among systems in the electric utility, oil & gas,
water/waste water and security industries. This robust, flexible non-proprietary protocol is
based on existing open standards to work within a variety of networks. The IEEE has
recommended DNP for remote terminal unit to intelligent electronic device messaging. DNP
can also be implemented in any SCADA system for efficient and reliable communications
between substation computers, RTUs, IEDs and master stations; over serial or LAN-based
systems.
DNP offers flexibility and functionality that go far beyond conventional communications
protocols. Among its robust and flexible features DNP 3.0 includes:
•
Output options
•
Addressing for over 65,000 devices on a single link
•
Time synchronization and time-stamped events
•
Broadcast messages
•
Data link and application layer confirmation
DNP 3.0 was originally designed based on three layers of the OSI seven-layer model:
application layer, data link layer and physical layer. The application layer is object-based
with objects provided for most generic data formats. The data link layer provides for several
methods of retrieving data such as polling for classes and object variations. The physical
layer defines most commonly a simple RS-232 or RS-485 interface.
Refer to the DNP User Manual for complete information on DNP protocol, including the
Device Profile Document.
DNP Communication Protocols Functions
There are several library functions related to DNP communication protocol. Refer to the
Function Specification section for details on each function listed.
dnpInstallConnectionHandler Configures the connection handler for DNP.
dnpClearEventLog
Deletes all change events from the DNP change event
buffers.
dnpConnectionEvent
Report a DNP connection event
dnpCreateRoutingTable
Allocates memory for a new routing table.
dnpGenerateEventLog
Generates a change event for the DNP point.
dnpGetConfiguration
Reads the DNP protocol configuration.
dnpGetConfigurationEx
Reads the extended DNP configuration parameters.
dnpSaveConfiguration
Writes the DNP protocol configuration parameters.
dnpSaveConfigurationEx
Writes the extended DNP configuration parameters
TelePACE C Tools User and Reference Manual
May 9, 2007
62
dnpGetBIConfig
Reads the configuration of a DNP binary input point.
dnpSaveBIConfig
Writes the configuration of a DNP binary input point.
dnpSaveBIConfigEx
Writes the configuration of an extended DNP Binary Input
point
dnpGetBOConfig
Reads the configuration of a DNP binary output point.
dnpGetBIConfigEx
Reads the configuration of an extended DNP Binary Input
point.
dnpSaveBOConfig
Sets the configuration of a DNP binary output point.
dnpGetAI16Config
Reads the configuration of a DNP 16-bit analog input point.
dnpSaveAI16Config
Sets the configuration of a DNP 16-bit analog input point.
dnpGetAI32Config
Reads the configuration of a DNP 32-bit analog input point.
dnpSaveAISFConfig
Sets the configuration of a DNP 32-bit short floating analog
input point
dnpGetAISFConfig
Reads the configuration of a DNP 32-bit short floating
analog input point.
dnpSaveAI32Config
Sets the configuration of a DNP 32-bit analog input point.
dnpGetAO16Config
Reads the configuration of a DNP 16-bit analog output
point.
dnpSaveAO16Config
Sets the configuration of a DNP 32-bit analog output point.
dnpGetAO32Config
Reads the configuration of a DNP 32-bit analog output
point.
dnpSaveAO32Config
Sets the configuration of a DNP 32-bit analog output point.
dnpSaveAOSFConfig
Sets the configuration of a DNP 32-bit short floating analog
output point.
dnpGetAOSFConfig
Sets the configuration of a DNP 32-bit short floating analog
output point.
dnpGetCI16Config
Reads the configuration of a DNP 16-bit counter input point.
dnpSaveCI16Config
Sets the configuration of a DNP 16-bit counter input point.
dnpGetCI32Config
Reads the configuration of a DNP 32-bit counter input point.
dnpSaveCI32Config
Sets the configuration of a DNP 32-bit counter input point.
dnpGetRuntimeStatus
Reads the current status of all DNP change event buffers.
dnpSendUnsolicited
Sends an ‘Unsolicited Response’ message in DNP protocol.
dnpSendUnsolicitedResponse
Sends an Unsolicited Response message in DNP,
with data from the specified classes.
dnpWriteRoutingTableEntry
Wwrites an entry in the DNP routing table.
dnpReadRoutingTableEntry
Reads an entry from the routing table.
dnpReadRoutingTableSize
Reads the total number of entries in the routing table.
dnpSearchRoutingTable
Searches the routing table for a specific DNP address.
dnpWriteRoutingTableDialStrings
Writes a primary and secondary dial string into an
entry in the DNP routing table.
TelePACE C Tools User and Reference Manual
May 9, 2007
63
dnpReadRoutingTableDialStrings
Reads a primary and secondary dial string from an
entry in the DNP routing table.
DNP Communication Protocol Structures and Types
The ctools.h file defines the structures DNP Configuration, Binary Input Point, Binary
Output Point, Analog Input Point, Analog Output Point and Counter Input Point. Refer
to the C Tools Structures and Types section for complete information on structures and
enumeration types.
I/O Database
The I/O database allows data to be shared between C programs, Ladder Logic programs
and communication protocols. A simplified diagram of the I/O Database is shown below.
Controller I/O
Database
Ladder Logic
Programs
C Tools
Programs
TeleBUS
Protocols
Coil Registers
00001 to 04096
Status Registers
10001 to 14096
Input Registers
30001 to 31024
Holding Registers
40001 to 49999
Controller Register
Assignment Table
5000 Series
I/O Modules
System
Parameters
The I/O database contains general purpose and user-assigned registers. General purpose
registers may be used by Ladder Logic and C application programs to store processed
information and to receive information from a remote device. Initially all registers in the I/O
Database are general purpose registers.
User-assigned registers are mapped directly from the I/O database to physical I/O hardware,
or to controller system configuration and diagnostic parameters. The Register Assignment
performs the mapping of registers from the I/O database to physical I/O hardware and
system parameters.
User-assigned registers are initialized to the default hardware state or system parameter
when the controller is reset. Assigned output registers do not maintain their values during
power failures. Assigned output registers do retain their values during application program
loading.
General purpose registers retain their values during power failures and application program
loading. The values change only when written by an application program or a
communication protocol.
The TeleBUS communication protocols provide a standard communication interface to the
controller. The TeleBUS protocols are compatible with the widely used Modbus RTU and
ASCII protocols and provide full access to the I/O database in the controller.
TelePACE C Tools User and Reference Manual
May 9, 2007
64
I/O Database Register Types
The I/O database is divided into four types of I/O registers. Each of these types are initially
configured as general purpose registers by the controller.
Coil Registers
Coil registers are single bit registers located in the digital output section of the I/O database.
Coil, or digital output, database registers may be assigned to 5000 Series digital output
modules or SCADAPack I/O modules through the Register Assignment. Coil registers may
also be assigned to controller on-board digital outputs and to system configuration modules.
There are 4096 coil registers numbered 00001 to 04096. Ladder logic programs, C language
programs, and the TeleBUS protocols can read from and write to these registers.
Status Registers
Status registers are single bit registers located in the digital input section of the I/O
database. Status, or digital input, database registers may be assigned to 5000 Series digital
input modules or SCADAPack I/O modules through the Register Assignment. Status
registers may also be assigned to controller on-board digital inputs and to system diagnostic
modules.
There are 4096 status registers are numbered 10001 to 14096. Ladder logic programs and
the TeleBUS protocols can only read from these registers. C language application programs
can read data from and write data to these registers.
Input Registers
Input registers are 16 bit registers located in the analog input section of the I/O database.
Input, or analog input, database registers may be assigned to 5000 Series analog input
modules or SCADAPack I/O modules through the Register Assignment. Input registers may
also be assigned to controller internal analog inputs and to system diagnostic modules.
There are 1024 input registers numbered 30001 to 31024. Ladder logic programs and the
TeleBUS protocols can only read from these registers. C language application programs can
read data from and write data to these registers.
The I/O database for the SCADAPack 100 controller has 512 input registers numbered
30001 to 30512. Ladder logic programs and the TeleBUS protocols can only read from
these registers. C language programs can read data from and write data to these registers.
Holding Registers
Holding registers are 16 bit registers located in the analog output section of the I/O
database. Holding, or analog output, database registers may be assigned to 5000 Series
analog output modules or SCADAPack analog output modules through the Register
Assignment. Holding registers may also be assigned to system diagnostic and configuration
modules.
There are 9999 input registers numbered 40001 to 49999. Ladder logic programs, C
language programs, and the TeleBUS protocols can read from and write to these registers.
The I/O database for the SCADAPack 100 controller has 4000 holding registers numbered
40001 to 44000. Ladder logic programs, C language programs, and the TeleBUS protocols
can read from and write to these registers.
TelePACE C Tools User and Reference Manual
May 9, 2007
65
I/O Database Functions
There are two library functions related to the I/O database. Refer to the Function
Specification section for details on each function listed.
dbase
Reads a value from the I/O database.
setdbase
Writes a value to the I/O database.
I/O Database Macros
The ctools.h file defines library functions for the I/O database. Refer to the C Tools Macros
section for details on each macro listed.
AB
Specifies Allan-Bradley database addressing.
DB_BADSIZE
Error code: out of range address specified
DB_BADTYPE
Error code: bad database addressing type specified
DB_OK
Error code: no error occurred
LINEAR
Specifies linear database addressing.
MODBUS
Specifies Modbus database addressing.
NUMAB
Number of registers in the Allan-Bradley database.
NUMCOIL
Number of registers in the Modbus coil section.
NUMHOLDING
Number of registers in the Modbus holding register section.
NUMINPUT
Number of registers in the Modbus input registers section.
NUMLINEAR
Number of registers in the linear database.
NUMSTATUS
Number of registers in the Modbus status section.
START_COIL
Start of the coil section in the linear database.
START_HOLDING
Start of the holding registers section in the linear database.
START_INPUT
Start of the input register section in the linear database.
START_STATUS
Start of the status section in the linear database.
Register Assignment Functions
All I/O hardware that is used by the controller must be assigned to I/O database registers in
order for these I/O points to be scanned continuously. I/O data may then be accessed
through the I/O database within the C program. C programs may read data from, or write
data to the I/O hardware through user- assigned registers in the I/O database.
The Register Assignment assigns I/O database registers to user-assigned registers using
I/O modules. An I/O Module can refer to an actual I/O hardware module (e.g. 5401 Digital
Input Module) or it may refer to a set of controller parameters, such as serial port settings.
The chapter Register Assignment Reference of the TelePACE Ladder Logic Reference
and User Manual contains a description of what each module is used for and the register
assignment requirements for the I/O module.
Register assignments configured using the TelePACE Register Assignment dialog may be
stored in the TelePACE program file or downloaded directly to the controller. To obtain error
checking that prevents invalid register assignments, use the TelePACE Register Assignment
dialog to initially build the Register Assignment. The Register Assignment can then be saved
in a Ladder Logic file (e.g. filename.lad) and downloaded with the C program.
TelePACE C Tools User and Reference Manual
May 9, 2007
66
There are several library functions related to register assignment. Refer to the Function
Specification section for details on each function listed.
clearRegAssignment
Erases the current Register Assignment.
addRegAssignment
Adds one I/O module to the current Register Assignment.
getIOErrorIndication
Gets the control flag for the I/O module error indication
getOutputsInStopMode
Gets the control flags for state of Outputs in Ladders Stop
Mode
setIOErrorIndication
Sets the control flag for the I/O module error indication
setOutputsInStopMode
Sets the control flags for state of Outputs in Ladders Stop
Mode
Register Assignment Enumeration Types
The ctools.h file defines one enumeration type. The ioModules enumeration type defines a
list of results of sending a command. Refer to the C Tools Structures and Types section
for complete information on structures and enumeration types.
Register Assignment Structure
The ctools.h file defines the structure RegAssign. Refer to the C Tools Structures and
Types section for complete information on structures and enumeration types.
HART Communication
The HART ® protocol is a field bus protocol for communication with smart transmitters.
The HART protocol driver provides communication between TeleSAFE Micro16 and
SCADAPack controllers and HART devices. The protocol driver uses the model 5904 HART
modem for communication. Four HART modem modules are supported per controller.
The driver allows HART transmitters to be used with C application programs and with
RealFLO. The driver can read data from HART devices.
HART Command Functions
The ctools.h file defines the following HART command related functions. Refer to the
Function Specification section for details on each function listed.
hartIO
Reads data from the 5904 interface module, processes HART
responses, processes HART commands, and writes commands
and configuration data to the 5904 interface module.
hartCommand
send a HART command string and specify a function to handle the
response
hartCommand0
read unique identifier using short-address algorithm
hartCommand1
read primary variable
hartCommand2
read primary variable current and percent of span
hartCommand3
read primary variable current and dynamic variables
hartCommand11
read unique identifier associated with tag
hartCommand33
read specified transmitter variables
TelePACE C Tools User and Reference Manual
May 9, 2007
67
hartStatus
return status of last HART command sent
hartGetConfiguration
read HART module settings
hartSetConfiguration
write HART module settings
hartPackString
convert string to HART packed string
hartUnpackString
convert HART packed string to string
HART Command Macros
The ctools.h file defines the following macro of interest to a C application program. Refer to
the C Tools Macros section for details.
DATA_SIZE
Maximum length of the HART command or response field.
HART Command Enumeration Types
The ctools.h file defines one enumeration type. The HART_RESULT enumeration type
defines a list of results of sending a command. Refer to the C Tools Structures and Types
section for complete information on structures and enumeration types.
HART Command Structures
The ctools.h file defines five structures. Refer to the C Tools Structures and Types
section for complete information on structures and enumeration types.
The HART_DEVICE type is a structure containing information about the HART device.
The HART_VARIABLE type is a structure containing a variable read from a HART device.
The HART_SETTINGS type is a structure containing the configuration for the HART modem
module.
The HART_COMMAND type is a structure containing a command to be sent to a HART
slave device.
The HART_RESPONSE type is a structure containing a response from a HART slave
device.
PID Control
TelePACE C Tools provides a total of 32 independent PID (Proportional, Integral, and
Derivative) controllers. PID control blocks operate independent of application programs. An
elaborate control program need not be written to use the control blocks. A simple program to
set up the control blocks is all that is required.
The PID control blocks are not limited to the PID control algorithm. They also provide ratio
control, ratio/bias control, alarm scanning and square root functions. Control blocks may be
interconnected to exchange setpoints, output limits, and other parameters.
Refer to the PID Controllers section of the TelePACE Ladder Logic User Manual for
complete information on configuring and using PID controllers.
PID Control Functions
The ctools.h file defines the following PID control related functions. Refer to the Function
Specification section for details on each function listed.
auto_pid
Set a PID block to execute automatically at the specified rate.
TelePACE C Tools User and Reference Manual
May 9, 2007
68
clear_pid
Set all PID block variables to zero.
get_pid
This function returns the value of a PID control block variable.
set_pid
This function assigns value to a PID control block variable.
PID Control Macros
The ctools.h file defines the following macros for PID block access. Refer to the C Tools
Macros section for details on each function listed.
AO
Variable name: alarm output address
CA
Variable name: cascade setpoint source
CR
Variable name: control register
DB
Variable name: deadband
DO
Variable name: decrease output
ER
Variable name: error
EX
Variable name: automatic execution period
FS
Variable name: full scale output limit
GA
Variable name: gain
HI
Variable name: high alarm setpoint
IB
Variable name: input bias
IH
Variable name: inhibit execution address
IN
Variable name: integrated error
IO
Variable name: increase output
IP
Variable name: input source
LO
Variable name: low alarm setpoint
OB
Variable name: output bias
OP
Variable name: output
PE
Variable name: period
PID_ALARM
Control register mask: alarms enabled
PID_ALARM_ABS
Control register mask: absolute alarms
PID_ALARM_ACK
Status register mask: alarm acknowledged
PID_ALARM_DEV
Control register mask: deviation alarms
PID_ALARM_ONLY
Control register mask: alarm only block
PID_ALARM_RATE
Control register mask: rate alarms
PID_ANALOG_IP
Control register mask: analog input
PID_ANALOG_OP
Control register mask: analog output
PID_BAD_BLOCK
Return code: bad block number specified.
PID_BAD_IO_IP
Status register mask: I/O failure on block input
PID_BAD_IO_OP
Status register mask: I/O failure on block output
TelePACE C Tools User and Reference Manual
May 9, 2007
69
PID_BLOCK_IP
Control register mask: input from output of another block
PID_BLOCKS
Number of PID blocks.
PID_CLAMP_FULL
Status register mask: output is clamped at full scale
PID_CLAMP_ZERO
Status register mask: output is clamped at zero scale
PID_ER_SQR
Control register mask: take square root of error
PID_HI_ALARM
Status register mask: high alarm detected
PID_INHIBIT
Status register mask: external inhibit input is on
PID_LO_ALARM
Status register mask: low alarm detected
PID_MANUAL
Status register mask: block is in manual mode
PID_MODE_AUTO
Control register mask: automatic mode
PID_MODE_MANUAL
Control register mask: manual mode
PID_MOTOR_OP
Control register mask: motor pulse duration output
PID_NO_ALARM
Control register mask: alarms disabled
PID_NO_ER_SQR
Control register mask: normal error
PID_NO_IP
Control register mask: no input (other than IP)
PID_NO_OP
Control register mask: no output
PID_NO_PV_SQR
Control register mask: normal PV
PID_NO_SP_TRACK
Control register mask: setpoint tracking disabled
PID_OK
Return code: operation completed successfully.
PID_OUT_DB
Status register mask: PID controller outside of deadband
PID_PID
Control register mask: PID control block
PID_PULSE_OP
Control register mask: pulse duration output
PID_PV_SQR
Control register mask: take square root of PV
PID_RATE_CLAMP
Status register mask: rate gain clamed at maximum
PID_RATIO_BIAS
Control register mask: ratio/bias control block
PID_RUNNING
Status register mask: block is executing
PID_SP_CASCADE
Control register mask: cascade setpoint
PID_SP_NORMAL
Control register mask: setpoint stored in SP
PID_SP_TRACK
Control register mask: setpoint tracking enabled
PV
Variable name: process value
RA
Variable name: rate time
RE
Variable name: reset time
SP
Variable name: setpoint
SR
Variable name: status register
ZE
Variable name: zero scale output limit
TelePACE C Tools User and Reference Manual
May 9, 2007
70
Backward Compatibility Functions
The following functions are provided for backward compatibility. They cannot access all
5000 series I/O modules. It is recommended that these functions not be used in new
programs. Instead use Register Assignment or call the specific I/O module driver function
directly.
These functions are defined in ctools.h for backward compatibility with these programs.
ain
Reads analog input
aioError
Reads analog I/O communication status
aout
Writes analog output
counter
Reads counter module input channel
counterError
Reads counter module error flag
din
Reads digital input channel (8 I/O points)
dout
Writes digital output channel (8 I/O points)
off
Tests If one digital I/O point is OFF
on
Tests If one digital I/O point is ON
pulse
Generates a square wave on a digital output point
pulse_train
Generates a series of pulses on a digital output point
timeout
Performs time delayed action on a digital output point
turnoff
Writes one digital output point to OFF status
turnon
Writes one digital output point to ON status
Backward Compatibility Macros
The following macros may have been used in C programs written for a controller with
firmware version 1.22 or older to support the functions: ain, aioError, aout, counter,
counterError, din, dout, off, on, pulse, pulse_train, timeout, turnoff or turnon.
These macros are defined in ctools.h for backward compatibility with these programs.
AIN_END
Number of last analog input channel.
AIN_START
Number of first analog input channel.
AIO_BADCHAN
Error code: bad analog input channel specified.
AIO_TIMEOUT
Error code: input device did not respond.
AIO_SUPPORTED
If defined indicates analog I/O supported.
AOUT_END
Number of last analog output channel.
AOUT_START
Number of first analog output channel.
COUNTER_CHANNELS
Specifies number of 5000 Series counter input channels
COUNTER_END
Number of last counter input channel
COUNTER_START
Number of first counter input channel
COUNTER_SUPPORTED
If defined indicates counter I/O hardware supported.
DIN_END
Number of last regular digital input channel.
TelePACE C Tools User and Reference Manual
May 9, 2007
71
DIN_START
Number of first regular digital input channel
DIO_SUPPORTED
If defined indicates digital I/O hardware supported.
DOUT_END
Number of last regular digital output channel.
DOUT_START
Number of first regular digital output channel
DUTY_CYCLE
Specifies timer is generating square wave output.
EXTENDED_DIN_END
Number of last extended digital input channel.
EXTENDED_DIN_START
Number of first extended digital input channel
EXTENDED_DOUT_END
Number of last extended digital output channel.
EXTENDED_DOUT_START
Number of first extended digital output channel
NORMAL
Specifies normal count down timer.
PULSE_TRAIN
Specifies timer is generating pulse train output.
TIMEOUT
Specifies timer is generating timed output change.
TIMER_BADADDR
Error code: invalid digital I/O address.
TelePACE C Tools User and Reference Manual
May 9, 2007
72
TelePACE C Tools Function
Specifications
The controller C function specifications are formatted as follows. The functions are listed
alphabetically.
Name
Each specification begins with the name of the function and a brief description.
Syntax
The syntax shows a prototype for the function, indicating the return type and the
types of its arguments. Any necessary header files are listed.
Description
This defines the calling parameters for the function and its return values.
Notes
This section contains additional information on the function, and considerations for
its use.
See Also
This section lists related functions.
Example
The example gives a brief sample of the use of the function.
TelePACE C Tools User and Reference Manual
May 9, 2007
73
addRegAssignment
Add Register Assignment
Syntax
#include
unsigned addRegAssignment(
unsigned moduleType,
unsigned moduleAddress,
unsigned startingRegister1,
unsigned startingRegister2,
unsigned startingRegister3,
unsigned startingRegister4);
Description
The addRegAssignment function adds one I/O module to the current Register Assignment
of type moduleType. The following symbolic constants are valid values for moduleType:
AIN_520xTemperature
AIN_520xRAMBattery
AIN_5501
AIN_5502
AIN_5503
AIN_5504
AIN_5521
AIN_generic8
AOUT_5301
AOUT_5302
AOUT_5304
AOUT_generic2
AOUT_generic4
CNFG_5904Modem
CNFG_clearPortCounters
CNFG_clearProtocolCounters
CNFG_IPSettings
CNFG_LEDPower
CNFG_MTCPIfSettings
CNFG_MTCPSettings
CNFG_PIDBlock
CNFG_portSettings
CNFG_protocolExtended
CNFG_protocolExtendedEx
CNFG_protocolSettings
CNFG_realTimeClock
CNFG_saveToEEPROM
CNFG_setSerialPortDTR
CNFG_storeAndForward
CNTR_520xCounterInputs
CNTR_5410
CNTR_520xInterruptInput
DIAG_commStatus
DIAG_controllerStatus
DIAG_LogicStatus
DIAG_forceLED
DIAG_IPConnections
DIAG_ModbusStatus
DIAG_protocolStatus
DIN_520xDigitalInputs
DIN_520xInterruptInput
DIN_520xOptionSwitches
DIN_5401
DIN_5402
DIN_5403
DIN_5404
DIN_5405
DIN_5421
DIN_generic16
DIN_generic8
DIN_SP32OptionSwitches
DOUT_5401
DOUT_5402
DOUT_5406
DOUT_5407
DOUT_5408
DOUT_5409
DOUT_5411
DOUT_generic16
DOUT_generic8
SCADAPack_AOUT
SCADAPack_lowerIO
SCADAPack_upperIO
SCADAPack_LPIO
SCADAPack_100IO
SCADAPack_5604IO
GFC_4202IO
GFC_4202IOEx
GFC_4202DSIO
moduleAddress specifies a unique address for the module. For the valid range for
moduleAddress refer to the list of modules in the chapter Register Assignment Reference of
the TelePACE Ladder Logic Reference and User Manual. For module addresses com1,
TelePACE C Tools User and Reference Manual
May 9, 2007
74
com2, com3 or com4 specify 0, 1, 2 or 3 respectively for moduleAddress. For module types
that have no module address (e.g. CNFG_LEDPower) specify -1 for moduleAddress. For
SCADAPack module types that have a module address fixed at 0, specify 0 for
moduleAddress.
startingRegister1 specifies the first register of any unused block of consecutive registers.
Refer to the list of modules in the Register Assignment Reference for the type and number
of registers required for this block. Data read from or written to the module is stored in this
block of registers.
If the module type specified has more than one type of I/O, use startingRegister2,
startingRegister3, and startingRegister4 as applicable. Each start register specifies the first
register of an unused block of consecutive registers for each type of input or output on the
module. Refer to the list of modules in the Register Assignment Reference for the module
I/O types. Specify 0 for startingRegister2, startingRegister3, or startingRegister4 if not
applicable.
Notes
Up to 150 modules may be added to the Register Assignment. If the Register Assignment is
full or if an incorrect value is specified for any argument this function returns FALSE;
otherwise TRUE is returned.
Output registers specified for certain CNFG type modules are initialized with the current
parameter values when the module is added to the Register Assignment (e.g.
CNFG_realTimeClock).
Call clearRegAssignment first before using the addRegAssignment function when
creating a new Register Assignment.
Duplicate or overlapping register assignments are not checked for by this function.
Overlapping register assignments may result in unpredictable I/O activity.
To obtain error checking that prevents invalid register assignments such as these, use the
TelePACE Register Assignment dialog to build the Register Assignment. Then save the
Register Assignment in a Ladder Logic file (e.g. filename.lad) and download it with the C
program, or transfer the Register Assignment to the C program using the
clearRegAssignment and addRegAssignment functions.
The IO_SYSTEM resource must be requested before calling this function.
See Also
clearRegAssignment
Example
#include
void main(void)
{
request_resource(IO_SYSTEM);
/* Create the Register Assignment */
clearRegAssignment();
addRegAssignment(SCADAPack_lowerIO, 0, 1,
10001, 30001, 0);
addRegAssignment(SCADAPack_AOUT, 0, 40001, 0,
0, 0);
addRegAssignment(AOUT_5302, 1, 40003, 0, 0, 0);
TelePACE C Tools User and Reference Manual
May 9, 2007
75
addRegAssignment(DIAG_forceLED, -1, 10017, 0,
0, 0);
addRegAssignment(DIAG_controllerStatus, -1,
30009, 0, 0, 0);
addRegAssignment(DIAG_protocolStatus, 2, 30010,
0, 0, 0);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
76
addRegAssignmentEx
Add Register Assignment
Syntax
#include
BOOLEAN addRegAssignmentEx(
UINT16 moduleType,
UINT16 moduleAddress,
UINT16 startingRegister1,
UINT16 startingRegister2,
UINT16 startingRegister3,
UINT16 startingRegister4,
UINT16 parameters[16]
);
Description
The addRegAssignmentEx function adds one I/O module to the current Register
Assignment of type moduleType. The following symbolic constants are valid values for
moduleType:
AIN_5209Temperature
AIN_5209RAMBattery
AIN_5501
AIN_5502
AIN_5503
AIN_5504
AIN_5505
AIN_5506
AIN_5521
AIN_generic8
AOUT_5301
AOUT_5302
AOUT_5304
AOUT_generic2
AOUT_generic4
CNFG_5904Modem
CNFG_clearPortCounters
CNFG_clearProtocolCounters
CNFG_IPSettings
CNFG_LEDPower
CNFG_modbusIpProtocol
CNFG_MTCPIfSettings
CNFG_MTCPSettings
CNFG_PIDBlock
CNFG_portSettings
CNFG_protocolExtended
CNFG_protocolExtendedEx
CNFG_protocolSettings
CNFG_realTimeClock
CNFG_saveToEEPROM
CNFG_setSerialPortDTR
CNFG_storeAndForward
TelePACE C Tools User and Reference Manual
May 9, 2007
CNTR_5209CounterInputs
CNTR_5410
CNTR_5209InterruptInput
DIAG_commStatus
DIAG_controllerStatus
DIAG_forceLED
DIAG_IPConnections
DIAG_ModbusStatus
DIAG_protocolStatus
DIN_5209DigitalInputs
DIN_5209InterruptInput
DIN_5401
DIN_5402
DIN_5403
DIN_5404
DIN_5405
DIN_5421
DIN_generic16
DIN_generic8
DOUT_5401
DOUT_5402
DOUT_5406
DOUT_5407
DOUT_5408
DOUT_5409
DOUT_5411
DOUT_generic16
DOUT_generic8
SCADAPack_AOUT
SCADAPack_lowerIO
SCADAPack_upperIO
SCADAPack_LPIO
SCADAPack_100IO
SCADAPack_5209IO
SCADAPack_5606IO
77
moduleAddress specifies a unique address for the module. For the valid range for
moduleAddress refer to the list of modules in the chapter Register Assignment Reference of
the TelePACE Ladder Logic Reference and User Manual. For module addresses com1,
com2, com3 or com4 specify 0, 1, 2 or 3 respectively for moduleAddress. For module
address Ethernet1 specify 4 for moduleAddress. For module types that have no module
address (e.g. CNFG_LEDPower) specify -1 for moduleAddress. For SCADAPack module
types that have a module address fixed at 0, specify 0 for moduleAddress.
startingRegister1 specifies the first register of any unused block of consecutive registers.
Refer to the list of modules in the Register Assignment Reference for the type and number
of registers required for this block. Data read from or written to the module is stored in this
block of registers.
If the module type specified has more than one type of I/O, use startingRegister2,
startingRegister3, and startingRegister4 as applicable. Each start register specifies the first
register of an unused block of consecutive registers for each type of input or output on the
module. Refer to the list of modules in the Register Assignment Reference for the module
I/O types. Specify 0 for startingRegister2, startingRegister3, or startingRegister4 if not
applicable.
parameters is an array of configuration parameters for the register assignment module.
Most modules do not use the parameters. Use the addRegAssignment function to
configure these modules. Use parameters with the following modules.
5505 I/O Module: parameters[0] to [3] define the analog input type for the
corresponding input. Valid values are:
•
•
•
•
0 = RTD in deg Celsius
1 = RTD in deg Fahrenheit
2 = RTD in deg Kelvin
3 = resistance measurement in ohms.
5505 I/O Module: parameter[4] defines the analog input filter. Valid values are:
•
•
•
•
0 = 0.5 s (minimum)
1=1s
2=2s
3 = 4 s (maximum)
5506 I/O Module: parameters[0] to [7] define the analog input type for the
corresponding input. Valid values are:
•
•
•
•
0 = 0 to 5 V input
1 = 1 to 5 V input
2 = 0 to 20 mA input
3 = 4 to 20 mA input
5506 I/O Module: parameter[8] defines the analog input filter. Valid values are:
•
•
•
•
0 = < 3 Hz (maximum filter)
1 = 6 Hz
2 = 11 Hz
3 = 30 Hz (minimum filter)
5506 I/O Module: parameter[9] defines the scan frequency. Valid values are:
•
•
0 = 60 Hz
1 = 50 Hz
5606 I/O Module: parameters[0] to [7] define the analog input type for the
corresponding input. Valid values are:
TelePACE C Tools User and Reference Manual
May 9, 2007
78
•
•
•
•
0 = 0 to 5 V input
1 = 1 to 5 V input
2 = 0 to 20 mA input
3 = 4 to 20 mA input
5606 I/O Module: parameter[8] defines the analog input filter. Valid values are:
•
•
•
•
0 = < 3 Hz (maximum filter)
1 = 6 Hz
2 = 11 Hz
3 = 30 Hz (minimum filter)
5606 I/O Module: parameter[9] defines the scan frequency. Valid values are:
•
•
0 = 60 Hz
1 = 50 Hz
5606 I/O Module: parameter[10] defines the analog output type. Valid values are:
•
•
0 = 0 to 20 mA output
1 = 4 to 20 mA output
Notes
Up to 150 modules may be added to the Register Assignment. If the Register Assignment is
full or if an incorrect value is specified for any argument this function returns FALSE;
otherwise TRUE is returned.
Output registers specified for certain CNFG type modules are initialized with the current
parameter values when the module is added to the Register Assignment (e.g.
CNFG_realTimeClock).
Call clearRegAssignment first before using the addRegAssignmentEx function when
creating a new Register Assignment.
Duplicate or overlapping register assignments are not checked for by this function.
Overlapping register assignments may result in unpredictable I/O activity.
To obtain error checking that prevents invalid register assignments such as these, use the
TelePACE Register Assignment dialog to build the Register Assignment. Then save the
Register Assignment in a Ladder Logic file (e.g. filename.lad) and download it with the C
program, or transfer the Register Assignment to the C program using the
clearRegAssignment and addRegAssignmentEx functions.
The IO_SYSTEM resource must be requested before calling this function.
See Also
addRegAssignment, clearRegAssignment
TelePACE C Tools User and Reference Manual
May 9, 2007
79
ain
Read an Analog Input
Syntax
#include
int ain(unsigned channel);
Description
The ain function reads from the analog input or output specified by channel. Input channels
read from the analog input hardware. Output channels read the value output to the channel
with the aout function.
The valid range for channel is 0 to AIO_MAX. If an invalid channel is selected, the ain
function returns INT_MIN and the current task's error code is set to AIO_BADCHAN. The
error code is obtained with the check_error function.
The ain function normally returns a value in the range –32767 to +32767.
Notes
Use offsets from the symbolic constants AIN_START, AIN_END, AOUT_START and
AOUT_END to reference analog channels. The constants make programs more portable
and protect against future changes to the analog I/O channel numbering.
The IO_SYSTEM resource must be requested before calling this function.
This function is provided for backward compatibility. It cannot access all 5000 series I/O
modules. It is recommended that this function not be used in new programs. Instead use
Register Assignment or call the I/O driver ioRead8Ain directly.
See also
aout, check_error, ioRead8Ain
Example
#include
void main(void)
{
request_resource(IO_SYSTEM);
printf("ain(%d)=%d\r\n", 2, ain(2));
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
80
aioError
Read Analog I/O Error Flags
Syntax
#include
int aioError(unsigned channel);
Description
The aioError function reads the I/O error flag for an analog channel.
It returns the error flag for the channel, if the channel number is valid; otherwise it returns
INT_MIN. A value of 0 indicates no error occurred. A positive value indicates an error.
Notes
This function is provided for backward compatibility. It cannot access all 5000 series I/O
modules. It is recommended that this function not be used in new programs. Instead use
Register Assignment or call the I/O driver ioRead8Ain directly.
See Also
aout, check_error, ioRead8Ain
TelePACE C Tools User and Reference Manual
May 9, 2007
81
alarmIn
Determine Alarm Time from Elapsed Time
Syntax
#include
ALARM_SETTING alarmIn(unsigned hours, unsigned minutes, unsigned seconds);
Description
The alarmIn function calculates the alarm settings to configure a real time clock alarm to
occur in hours, minutes and seconds from the current time.
The function returns an ALARM_SETTING structure suitable for passing to the
setClockAlarm function. The structure specifies an absolute time alarm at the time offset
specified by the call to alarmIn. Refer to the Structures and Types section for a description
of the fields in the ALARM_SETTING structure.
Notes
If second is greater than 60 seconds, the additional time is rolled into the minutes. If minute
is greater than 60 minutes, the additional time is rolled into the hours.
If the offset time is greater that one day, then the alarm time will roll over within the current
day.
The IO_SYSTEM resource must be requested before calling this function.
See Also
getClockAlarm, setClockAlarm,
Example
#include
/* -------------------------------------------conservePower
The conservePower function places the
controller into sleep mode for 10 minutes.
-------------------------------------------- */
void conservePower(void)
{
ALARM_SETTING alarm;
request_resource(IO_SYSTEM);
/* Alarm in 10 minutes */
alarm = alarmIn(0, 10, 0);
setClockAlarm(alarm)
/* Put controller in low power mode */
sleep();
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
82
allocate_envelope
Obtain an Envelope from the RTOS
Syntax
#include envelope *allocate_envelope(void);
Description
The allocate_envelope function obtains an envelope from the operating system. If no
envelope is available, the task is blocked until one becomes available.
The allocate_envelope function returns a pointer to the envelope.
Notes
Envelopes are used to send messages between tasks. The RTOS allocates envelopes from
a pool of free envelopes. It returns envelopes to the pool when they are de-allocated.
An application program must ensure that unneeded envelopes are de-allocated. Envelopes
may be reused.
See Also
deallocate_envelope
Example
#include
extern unsigned other_task_id;
void task1(void)
{
envelope *letter;
/* send a message to another task */
/* assume it will deallocate the envelope */
letter = allocate_envelope();
letter->destination = other_task_id;
letter->type = MSG_DATA;
letter->data = 5;
send_message(letter);
/* receive a message from any other task */
letter = receive_message();
/* ... process the data here */
deallocate_envelope(letter);
/* ... the rest of the task */
}
TelePACE C Tools User and Reference Manual
May 9, 2007
83
aout
Write to Analog Output
Syntax
#include
int aout(unsigned channel, int value);
Description
The aout function writes value to the analog output specified by channel. The range for
channel is AOUT_START to AOUT_END inclusive. The range for value is -32767 to 32767.
aout returns the value written to the hardware, or -1 if the channel is not an analog output.
Notes
The value output may be limited by the analog output module.
Use offsets from the symbolic constants AIN_START, AIN_END, AOUT_START and
AOUT_END to reference analog channels. The constants make programs more portable
and protect against future changes to the analog I/O channel numbering.
The IO_SYSTEM resource must be requested before calling this function.
This function is provided for backward compatibility. It cannot access all 5000 series I/O
modules. It is recommended that this function not be used in new programs. Instead use
Register Assignment or call the I/O driver ioWrite4Aout directly.
See Also
addRegAssignment, ioWrite4Aout
Example
#include
void main(void)
{
int value;
/* ramp output from zero to full scale */
for (value = 0; value < 32767; value++)
{
request_resource(IO_SYSTEM);
aout(AOUT_START, value);
release_resource(IO_SYSTEM);
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
84
auto_pid
Execute a PID Block Automatically
Syntax
#include
void auto_pid(unsigned block, unsigned period);
Description
The auto_pid routine configures a PID control block to execute automatically at the
specified period. period is measured in 0.1 second increments. block must be in the range 0
to PID_BLOCKS – 1.
Setting the period to 0 stops execution of the control block.
Notes
See the TelePACE PID Controllers Reference Manual for a detailed description of PID
control.
The control block must be configured properly before it is engaged, or indeterminate
operation may result.
The IO_SYSTEM resource must be requested before calling this function.
See Also
set_pid, getPowerMode
Get Current Power Mode
Syntax
#include
BOOLEAN getPowerMode(UCHAR* cpuPower, UCHAR* lan, UCHAR* usbPeripheral,
UCHAR* usbHost);
Description
The getPowerMode function places the current state of the CPU, LAN, USB peripheral port,
and USB host port in the passed parameters. The following table lists the possible return
values and their meaning.
Macro
PM_CPU_FULL
PM_CPU_REDUCED
PM_CPU_SLEEP
PM_LAN_ENABLED
PM_LAN_DISABLED
PM_USB_PERIPHERAL_ENABLED
PM_USB_PERIPHERAL_DISABLED
PM_USB_HOST_ENABLED
PM_USB_HOST_DISABLED
PM_UNAVAILABLE
TelePACE C Tools User and Reference Manual
May 9, 2007
Meaning
The CPU is set to run at full speed
The CPU is set to run at a reduced speed
The CPU is set to sleep mode
The LAN is enabled
The LAN is disabled
The USB peripheral port is enabled
The USB peripheral port is disabled
The USB host port is enabled
The USB host port is disabled
The status of the device could not be read.
85
TRUE is returned if the values placed in the passed parameters are valid, otherwise FALSE
is returned.
The application program may set the current power mode with the setPowerMode function.
See Also
setPowerMode, setWakeSource, getWakeSource
get_pid, clear_pid
TelePACE C Tools User and Reference Manual
May 9, 2007
86
check_error
Get Error Code for Current Task
Syntax
#include
int check_error(void);
Description
The check_error function returns the error code for the current task. The error code is set
by various I/O routines, when errors occur. A separate error code is maintained for each
task.
Notes
Some routines in the standard C library, return errors in the global variable errno. This
variable is not unique to a task, and may be modified by another task, before it can be read.
See Also
report_error
TelePACE C Tools User and Reference Manual
May 9, 2007
87
checksum
Calculate a Checksum
Syntax
#include
unsigned checksum(unsigned char *start, unsigned char *end, unsigned
algorithm);
Description
The checksum function calculates a checksum on memory. The memory starts at the byte
pointed to by start, and ends with the byte pointed to by end. The algorithm may be one of:
ADDITIVE
CRC_16
CRC_CCITT
BYTE_EOR
16 bit byte-wise sum
CRC-16 polynomial checksum
CRC-CCITT polynomial checksum
8 bit byte-wise exclusive OR
The CRC checksums use the crc_reverse function.
See Also
crc_reverse
Example
This function displays two types of checksums.
#include
void checksumExample(void)
{
char str[] = "This is a test";
unsigned sum;
/* Display additive checksum */
sum = checksum(str, str+strlen(str), ADDITIVE);
printf("Additive checksum: %u\r\n", sum);
/* Display CRC-16 checksum */
sum = checksum(str, str+strlen(str), CRC_16);
printf("CRC-16 checksum: %u\r\n", sum);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
88
checkSFTranslationTable
Test for Store and Forward Configuration Errors
Syntax
#include
struct SFTranslationStatus checkSFTranslationTable(void);
Description
The checkSFTranslationTable function checks all entries in the address translation table
for validity. It detects the following errors:
The function returns a SFTranslationStatus structure. Refer to the Structures and Types
section for a description of the fields in the SFTranslationStatus structure. The code field of
the structure is set to one of the following. If there is an error, the index field is set to the
location of the translation that is not valid.
Result code
SF_VALID
SF_NO_TRANSLATION
SF_PORT_OUT_OF_RANGE
SF_STATION_OUT_OF_RANG
E
Meaning
All translations are valid
The entry defines re-transmission of the same
message on the same port
One or both of the serial port indexes is not valid
One or both of the stations is not valid
Notes
The TeleBUS Protocols User Manual describes store and forward messaging mode.
See Also
getSFTranslation, setSFTranslation, checkSFTranslationTable
Example
See the example for the setSFTranslation function.
TelePACE C Tools User and Reference Manual
May 9, 2007
89
clearAllForcing
Clear All Forcing
Syntax
#include
void clearAllForcing(void);
Description
The clearAllForcing function removes all forcing conditions from all I/O database registers.
The IO_SYSTEM resource must be requested before calling this function.
See Also
setForceFlag, overrideDbase
TelePACE C Tools User and Reference Manual
May 9, 2007
90
clear_errors
Clear Serial Port Error Counters
Syntax
#include
void clear_errors(FILE *stream);
Description
The clear_errors function clears the serial port error counters for the serial port specified by
stream. If stream does not point to a valid serial port the function has no effect.
The IO_SYSTEM resource must be requested before calling this function.
See Also
get_status
TelePACE C Tools User and Reference Manual
May 9, 2007
91
clear_pid
Clear PID Block Variables
Syntax
#include
void clear_pid(unsigned block);
Description
The clear_pid routine sets all variables in the specified control block to 0. clear_pid is
normally used as the first step of control block configuration. block must be in the range 0 to
PID_BLOCKS – 1.
Notes
See the TelePACE PID Controllers Reference Manual for a detailed description of PID
control.
Values stored in PID blocks are not initialized when a program is run, and are guaranteed to
retain their values during power failures and program loading. PID block variables must
always be initialized by the user program.
The IO_SYSTEM resource must be requested before calling this function.
See Also
set_pid, getPowerMode
Get Current Power Mode
Syntax
#include
BOOLEAN getPowerMode(UCHAR* cpuPower, UCHAR* lan, UCHAR* usbPeripheral,
UCHAR* usbHost);
Description
The getPowerMode function places the current state of the CPU, LAN, USB peripheral port,
and USB host port in the passed parameters. The following table lists the possible return
values and their meaning.
Macro
PM_CPU_FULL
PM_CPU_REDUCED
PM_CPU_SLEEP
PM_LAN_ENABLED
PM_LAN_DISABLED
PM_USB_PERIPHERAL_ENABLED
PM_USB_PERIPHERAL_DISABLED
PM_USB_HOST_ENABLED
PM_USB_HOST_DISABLED
PM_UNAVAILABLE
TelePACE C Tools User and Reference Manual
May 9, 2007
Meaning
The CPU is set to run at full speed
The CPU is set to run at a reduced speed
The CPU is set to sleep mode
The LAN is enabled
The LAN is disabled
The USB peripheral port is enabled
The USB peripheral port is disabled
The USB host port is enabled
The USB host port is disabled
The status of the device could not be read.
92
TRUE is returned if the values placed in the passed parameters are valid, otherwise FALSE
is returned.
The application program may set the current power mode with the setPowerMode function.
See Also
setPowerMode, setWakeSource, getWakeSource
get_pid, auto_pid
TelePACE C Tools User and Reference Manual
May 9, 2007
93
clear_protocol_status
Clear Protocol Counters
Syntax
#include
void clear_protocol_status(FILE *stream);
Description
The clear_protocol_status function clears the error and message counters for the serial
port specified by stream. If stream does not point to a valid serial port the function has no
effect.
The IO_SYSTEM resource must be requested before calling this function.
See Also
get_protocol_status
TelePACE C Tools User and Reference Manual
May 9, 2007
94
clearRegAssignment
Clear Register Assignment
Syntax
#include
void clearRegAssignment(void);
Description
The clearRegAssignment function erases the current Register Assignment. Call this
function first before using the addRegAssignment function to create a new Register
Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
addRegAssignment
Example
See example for addRegAssignment.
TelePACE C Tools User and Reference Manual
May 9, 2007
95
clearSFTranslationTable
Clear Store and Forward Translation Configuration
Syntax
#include
void clearSFTranslationTable(void);
Description
The clearSFTranslationTable function clears all entries in the store and forward translation
table.
Notes
The TeleBUS Protocols User Manual describes store and forward messaging mode.
The IO_SYSTEM resource must be requested before calling this function.
See Also
getSFTranslation, setSFTranslation, checkSFTranslationTable
Example
See the example for the setSFTranslation function.
TelePACE C Tools User and Reference Manual
May 9, 2007
96
clearStatusBit
Clear Bits in Controller Status Code
Syntax
#include
unsigned clearStatusBit(unsigned bitMask);
Description
The clearStatusBit function clears the bits indicated by bitMask in the controller status
code. When the status code is non-zero, the STAT LED blinks a binary sequence
corresponding to the code. If code is zero, the STAT LED turns off.
The function returns the value of the status register.
Notes
The status output opens if code is non-zero. Refer to the System Hardware Manual for
more information.
The binary sequence consists of short and long flashes of the error LED. A binary zero is
indicated by a short flash of 1/10th of a second. A longer flash of approximately 1/2 of a
second indicates a binary one. The least significant digit is output first. As few bits as
possible are displayed – all leading zeros are ignored. There is a two-second delay between
repetitions.
The STAT LED is the LED located on the top left hand corner of the 5203 or 5204 controller
board.
Bits 0 and 1 of the status code are used by the Register Assignment.
See Also
setStatusBit, setStatus, getStatusBit
TelePACE C Tools User and Reference Manual
May 9, 2007
97
clear_tx
Clear Serial Port Transmit Buffer
Syntax
#include
void clear_tx(FILE *stream);
Description
The clear_tx function clears the transmit buffer for the serial port specified by stream. If
stream does not point to a valid serial port the function has no effect.
See Also
get_status
TelePACE C Tools User and Reference Manual
May 9, 2007
98
counter
Read Counter Input Module
Syntax
#include
long counter(unsigned counter);
Description
The counter function reads data from the counter input specified by channel. If the channel
number is not valid a COUNTER_BADCOUNTER error is reported for the current task. The
value returned by counter is not valid.
Notes
Refer to the TelePACE Ladder Logic User Manual for an explanation of counter input
channel assignments.
Use offsets from the symbolic constants COUNTER_START and COUNTER_END to
reference counter channels. The constants make programs more portable and protect
against future changes to the counter input channel numbering.
The IO_SYSTEM resource must be requested before calling this function.
This function is provided for backward compatibility. It cannot access all 5000 series I/O
modules. It is recommended that this function not be used in new programs. Instead use
Register Assignment or call the I/O driver ioRead4Counter directly.
See Also
counterError, check_error, request_resource, release_resource, ioRead4Counter
TelePACE C Tools User and Reference Manual
May 9, 2007
99
counterError
Read Counter Input Error Flag
Syntax
#include
long counterError(unsigned counter);
Description
The counterError function returns the I/O error flag for a counter channel. It returns TRUE if
an error occurred and FALSE if no occurred on the last read of the input module.
If the channel number is not valid a COUNTER_BADCOUNTER error is reported for the
current task. The value returned is not valid.
Notes
Refer to the TelePACE Ladder Logic User Manual for a explanation of counter input
channel assignments.
Use offsets from the symbolic constants COUNTER_START and COUNTER_END to
reference counter channels. The constants make programs more portable and protect
against future changes to the counter input channel numbering.
This function is provided for backward compatibility. It cannot access all 5000 series I/O
modules. It is recommended that this function not be used in new programs. Instead use
Register Assignment or call the I/O driver ioRead4Counter directly.
See Also
counter, check_error, ioRead4Counter
TelePACE C Tools User and Reference Manual
May 9, 2007
100
crc_reverse
Calculate a CRC Checksum
Syntax
#include
unsigned crc_reverse(unsigned char *start, unsigned char *end, unsigned
poly, unsigned initial);
Description
The crc_reverse function calculates a CRC type checksum on memory using the reverse
algorithm. The memory starts at the byte pointed to by start, and ends with the byte pointed
to by end. The generator polynomial is specified by poly. poly may be any value, but must be
carefully chosen to ensure good error detection. The checksum accumulator is set to initial
before the calculation is started.
Notes
The reverse algorithm is named for the direction bits are shifted. In the reverse algorithm,
bits are shifted towards the least significant bit. This produces different checksums than the
classical, or forward algorithm, using the same polynomials.
See Also
checksum
TelePACE C Tools User and Reference Manual
May 9, 2007
101
create_task
Create a New Task
Syntax
#include
int create_task(void *function, unsigned priority, unsigned type, unsigned
stack);
Description
The create_task function allocates stack space for a task and places the task on the ready
queue. function specifies the start address of the routine to be executed. The task will
execute immediately if its priority is higher than the current task.
priority is an execution priority between 1 and 4 for the created task. The 4 task priority
levels aid in scheduling task execution.
type specifies if the task is ended when an application program is stopped. Valid values for
type are:
SYSTEM
system tasks do not terminate when the program stops
APPLICATION application tasks terminate when the program stops
It is recommended that only APPLICATION type tasks be created.
The stack parameter specifies how many stack blocks are allocated for the task. Each stack
block is 256 bytes.
The create_task function returns the task ID (TID) of the task created. If an error occurs, -1
is returned.
Notes
Refer to the Real Time Operating System section for more information on tasks.
Note that the main task and the Ladder Logic and I/O scanning task have a priority of 1. If
the created task is continuously running processing code, create the task with a priority of 1
and call release_processor periodically; otherwise the remaining priority 1 tasks will be
blocked from executing.
For tasks such as a protocol handler, that wait for an event using the wait_event or
receive_message function, a priority greater than 1 may be selected without blocking other
lower priority tasks.
The number of stack blocks required depends on the functions called within the task, and
the size of local variables created. Most tasks require 2 stack blocks. If any of the printf
functions are used, then at least 4 stack blocks are required. Add local variable usage to
these limits, if large local arrays or structures are created. Large structures and arrays are
usually best handled as static global variables within the task source file. (The variables are
global to all functions in the task, but cannot be seen by functions in other files.)
Additional stack space may be made available by disabling unused protocol tasks. See the
section Program Development or the set_protocol() function for more information.
See Also
end_task
TelePACE C Tools User and Reference Manual
May 9, 2007
102
Example
#include
#define
TIME_TO_PRINT
20
void task1(void)
{
int a, b;
while (TRUE)
{
/* body of task 1 loop - processing I/O */
request_resource(IO_SYSTEM);
a = dbase(MODBUS, 30001);
b = dbase(MODBUS, 30002);
setdbase(MODBUS, 40020, a * b);
release_resource(IO_SYSTEM);
/* Allow other tasks to execute */
release_processor();
}
}
void task2(void)
{
while(TRUE)
{
/* body of task 2 loop - event handler */
wait_event(TIME_TO_PRINT);
printf("It’s time for a coffee break\r\n");
}
}
/* -------------------------------------------The shutdown function stops the signalling
of TIME_TO_PRINT events when application is
stopped.
-------------------------------------------- */
void shutdown(void)
{
endTimedEvent(TIME_TO_PRINT);
}
void main(void)
{
TASKINFO taskStatus;
/* continuos processing task at priority 1 */
create_task(task1, 1, APPLICATION, 2);
/* event handler needs larger stack for printf function */
create_task(task2, 3, APPLICATION, 4);
/* set up task exit handler to stop
signalling of events when this task ends */
taskStatus = getTaskInfo(0);
installExitHandler(taskStatus.taskID, shutdown);
/* start timed event to occur every 10 sec */
startTimedEvent(TIME_TO_PRINT, 100);
interval(0, 10);
while(TRUE)
{
/* body of main task loop */
/* other processing code */
/* Allow other tasks to execute */
TelePACE C Tools User and Reference Manual
May 9, 2007
103
release_processor();
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
104
databaseRead
Read Value from I/O Database
Syntax
#include
BOOLEAN databaseRead(UINT16 type, UINT16 address, INT16* value)
Description
The databaseRead function reads a value from the database. The value is written to the
variable pointed to by value. The variable is not changed if type and address are not valid.
The function has three parameters. type specifies the method of addressing the database.
Valid values are MODBUS and LINEAR. address specifies the location in the database.
value is a pointer to a variable to hold the result.
The function returns TRUE if the specified address is valid and FALSE if the register does not
exist.
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
databaseWrite
Example
#include
void main(void)
{
INT16 value;
BOOLEAN status;
request_resource(IO_SYSTEM);
/* Read Modbus status input point */
status = databaseRead(MODBUS, 10001, &value);
/* Read 16 bit register */
status = databaseRead(LINEAR, 3020, &value);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
105
databaseWrite
Write Value to I/O Database
Syntax
#include
BOOLEAN databaseWrite(UINT16 type, UINT16 address, INT16 value)
Description
The databaseWrite function writes value to the I/O database.
The function has three parameters. type specifies the method of addressing the database.
Valid values are MODBUS and LINEAR. address specifies the location in the database.
value is the data to write.
The function returns TRUE if the value was written. The function returns FALSE if
•
the type is invalid
•
the address is not valid for the controller
•
the address is read only on the SCADASense 4202 controller (some registers in the
range 40001 to 40499).
•
the data is not valid for the address on the SCADASense 4202 controller (some
registers in the range 40001 to 40499).
•
the hardware write protect is installed on the SCADASense 4202 controller (registers in
the range 40001 to 40499).
•
the flow computer is running on the SCADASense 4202 controller (registers in the range
40001 to 40499).
Notes
When writing to LINEAR digital addresses, value is a bit mask which writes data to 16 1-bit
registers at once. If any of these 1-bit registers is invalid, only the valid registers are written
and FALSE is returned.
The IO_SYSTEM resource must be requested before calling this function.
See Also
databaseRead
Example
#include
void main(void)
{
BOOLEAN status;
request_resource(IO_SYSTEM);
status = databaseWrite(MODBUS, 40001, 102);
/* Turn ON the first 16 coils */
status = databaseWrite(LINEAR, 0, 255);
TelePACE C Tools User and Reference Manual
May 9, 2007
106
/* Write to a 16 bit register */
status = databaseWrite(LINEAR, 3020, 240);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
107
datalogCreate
Create Data Log Function
Syntax
#include
DATALOG_STATUS datalogCreate(
UINT16 logID,
DATALOG_CONFIGURATION * pLogConfiguration
);
Description
This function creates a data log with the specified configuration. The data log is created in
the data log memory space.
The function has two parameters. logID specifies the data log to be created. The valid
range is 0 to 15. pLogConfiguration points to a structure with the configuration for the
data log.
The function returns the status of the operation.
Notes
The configuration of an existing data log cannot be changed. The log must be deleted and
recreated to change the configuration.
All data logs are stored in memory from a pool for all data logs. If there is insufficient
memory the creation operation fails. The function returns DLS_NOMEMORY.
If the data log already exists the creation operation fails. The function returns DLS_EXISTS.
If the log ID is not valid the creation operation fails. The function returns DLS_BADID.
If the configuration is not valid the creation operation fails. The function returns
DLS_BADCONFIG.
See Also
datalogDelete datalogSettings
Example
/*---------------------------------------------The following code shows how to create a
data log and how to write one record into it.
----------------------------------------------*/
#include "ctools.h"
/*--------------------------------Structure used only to copy one
record into data log
---------------------------------*/
struct dataRecord
{
UINT16
value1;
int
value2;
double
value3;
float
value4;
TelePACE C Tools User and Reference Manual
May 9, 2007
108
float
value5;
};
int logID;
/*--------------------------------Declare a structure for the log
---------------------------------*/
DATALOG_CONFIGURATION dLogConfig;
/*--------------------------------Declare a struture to hold the
data that will be copied in log
---------------------------------*/
struct dataRecord data;
/*--------------------Function declaration
----------------------*/
void ConfigureLog(void);
void InitRecord(void);
void main(void)
{
ConfigureLog();
InitRecord();
/* function call to cofigure log */
if(datalogCreate(logID, &dLogConfig) == DLS_CREATED)
{
/* Start writing records in log */
if( datalogWrite(logID, (UINT16 *)&data) )
{
/* one record was written in data log */
}
}
}
/* Log configuration */
void ConfigureLog(void)
{
/* Assign a number to the data log */
logID = 10;
/* Fill in the log configuration structure */
dLogConfig.records = 200;
dLogConfig.fields = 5;
dLogConfig.typesOfFields[0] = DLV_UINT16;
dLogConfig.typesOfFields[1] = DLV_INT32;
dLogConfig.typesOfFields[2] = DLV_DOUBLE;
dLogConfig.typesOfFields[3] = DLV_FLOAT;
dLogConfig.typesOfFields[4] = DLV_FLOAT;
}
/* One record initialization */
void InitRecord(void)
{
/* Assign some data for the log */
data.value1 = 100;
data.value2 = 200;
data.value3 = 30000;
data.value4 = 40.3;
data.value5 = 50.75;
}
TelePACE C Tools User and Reference Manual
May 9, 2007
109
datalogDelete
Delete Data Log Function
Syntax
#include
BOOLEAN datalogDelete(
UINT16 logID
);
Description
This function destroys the specified data log. The memory used by the data log is returned
to the freed.
The function has one parameter. logID specifies the data log to be deleted. The valid range
is 0 to 15.
The function returns TRUE if the data log was deleted. The function returns FALSE if the log
ID is not valid or if the log had not been created.
See Also
datalogCreate
Example
/* The following code shows the only way to
change the configuration of an existing log
is to delete the log and recreate the data
log
*/
#include
int logID;
/* Declare a structure for the log */
DATALOG_CONFIGURATION dLogConfig;
/* Select logID #10 */
logID = 10;
/* Read the configuration of logID #10 */
if( datalogSettings( logID, &dLogConfig ) )
{
if(dLogConfig.typesOfFields[0] == DLV_INT16)
{
/* Wrong type. Delete whole log and start from scratch */
if(datalogDelete(logID) )
{
/* Re-enter the log configuration */
dLogConfig.records = 200;
dLogConfig.fields = 5;
dLogConfig.typesOfFields[0] = DLV_UINT16;
dLogConfig.typesOfFields[1] = DLV_INT32;
dLogConfig.typesOfFields[2] = DLV_DOUBLE;
dLogConfig.typesOfFields[3] = DLV_FLOAT;
TelePACE C Tools User and Reference Manual
May 9, 2007
110
dLogConfig.typesOfFields[4] = DLV_FLOAT;
datalogCreate(logID, &dLogConfig);
}
else
{
/* could not delete log */
}
}
}
else
{
/* Could not read settings */
}
TelePACE C Tools User and Reference Manual
May 9, 2007
111
datalogPurge
Purge Data Log Function
Syntax
#include
BOOLEAN datalogPurge(
UINT16 logID,
BOOLEAN purgeAll,
UINT32 sequenceNumber
);
Description
This function removes records from a data log. The function can remove all the records, or a
group of records starting with the oldest in the log.
The function has three parameters. logID specifies the data log. The valid range is 0 to 15.
If purgeAll is TRUE, all records are removed, otherwise the oldest records are removed.
sequenceNumber specifies the sequence number of the most recent record to remove. All
records up to and including this record are removed. This parameter is ignored if purgeAll
is TRUE.
The function returns TRUE if the operation succeeds. The function returns FALSE if the log
ID is invalid, if the log has not been created, or if the sequence number cannot be found in
the log.
Notes
Purging the oldest records in the log is usually done after reading the log. The sequence
number used is that of the last record read from the log. This removes the records that have
been read and leaves any records added since the records were read.
If the sequence number specifies a record that is not in the log, no records are removed.
See Also
datalogReadStart datalogReadNext datalogWrite
Example
#include
int logID, sequenceNumber;
/* Declare flag to purge entire of data log or part of it */
BOOLEAN purgeAll;
/* Which data log to purge? */
logID = 10;
/* Set flag to purge only part of data log */
purgeAll = FALSE;
/* How many of the oldest records to purge */
sequenceNumber = 150;
TelePACE C Tools User and Reference Manual
May 9, 2007
112
if( datalogPurge(logID, purgeAll, sequenceNumber) )
{
/* Successful at purging the first 150 records of log */
/* Start writing records again */
}
/* To purge the entire data log, simply set flag to TRUE */
purgeAll = TRUE;
/* Call up function with same parameters */
if( datalogPurge(logID, purgeAll, sequenceNumber) )
{
/* Successful at purging the entire data log */
/* Start writing records again */
}
TelePACE C Tools User and Reference Manual
May 9, 2007
113
datalogReadNext
Read Data Log Next Function
This function returns the next record in the data log.
Syntax
#include
BOOLEAN datalogReadNext(
UINT16 logID,
UINT32 sequenceNumber,
UINT32 * pSequenceNumber,
UINT32 * pNextSequenceNumber,
UINT16 * pData
);
Description
This function reads the next record from the data log starting at the specified sequence
number. The function returns the record with the specified sequence number if it is present
in the log. If the record no longer exists it returns the next record in the log.
The function has five parameters. logID specifies the data log. The valid range is 0 to 15.
sequenceNumber is sequence number of the record to be read. pSequenceNumber is a
pointer to a variable to hold the sequence number of the record read.
pNextSequenceNumber is a pointer to a variable to hold the sequence number of the next
record in the log. This is normally used for the next call to this function. pData is a pointer to
memory to hold the data read from the log.
The function returns TRUE if a record is read from the log. The function returns FALSE if the
log ID is not valid, if the log has not been created or if there are no more records in the log.
Notes
Use the datalogReadStart function to obtain the sequence number of the oldest record
in the data log.
The pData parameter must point to memory of sufficient size to hold all the data in a record.
It is normally necessary to call this function until it returns FALSE in order to read all the data
from the log. This accommodates cases where data is added to the log while it is being
read.
If data is read from the log at a slower rate than it is logged, it is possible that the sequence
numbers of the records read will not be sequential. This indicates that records were
overwritten between calls to read data.
The sequence number rolls over after reaching its maximum value.
See Also
datalogReadStart datalogPurge datalogWrite
Example
See the example for datalogReadStart.
TelePACE C Tools User and Reference Manual
May 9, 2007
114
datalogReadStart
Read Data Log Start Function
Syntax
#include
BOOLEAN datalogReadStart(
UINT16 logID,
UINT32 * pSequenceNumber
);
Description
This function returns the sequence number of the record at the start of the data log. This is
the oldest record in the log.
The function has two parameters. logID specifies the data log. The valid range is 0 to 15.
pSequenceNumber is a pointer to a variable to hold the sequence number.
The function returns TRUE if the operation succeeded. The function returns FALSE if the log
ID is not valid or if the log has not been created.
Notes
Use the datalogReadNext function to read records from the log.
The function will return a sequence number even if the log is empty. In this case the next call
to datalogReadNext will return no data.
See Also
datalogReadNext datalogPurge datalogWrite
Example
/************************************************
The following code shows how to read records
from data log.
************************************************/
#include "ctools.h"
#include
UINT16 recordSize,
logID,
*pData; /* Pointer to memory to hold data read from log. */
UINT32 sequenceNumber,/* Sequence number of record to be read. */
nextSequenceNumber; /* Sequence number of next record. */
void main(void)
{
/* Select data log #10 */
logID = 10;
/* Find first record in data log #10 and store
its sequence number into sequenceNumber */
TelePACE C Tools User and Reference Manual
May 9, 2007
115
if( datalogReadStart(logID, &sequenceNumber) )
{
/* Get the size of this record */
if( datalogRecordSize(logID, &recordSize) )
{
/* Allocate memory of size recordSize */
pData = (UINT16 *) malloc(recordSize);
/* Read all records from data log #10. */
while( datalogReadNext(logID, sequenceNumber,
&sequenceNumber, &nextSequenceNumber, pData) )
{
/* Use pData and its contents.
Set next sequence number of record to be read. */
sequenceNumber =
nextSequenceNumber;
}
}
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
116
datalogRecordSize
Data Log Record Size Function
Syntax
#include < ctools.h >
BOOLEAN datalogRecordSize(
UINT16 logID,
UINT16 * pRecordSize;
);
Description
This function returns the size of a record for the specified data log. The log must have been
previously created with the datalogCreate function.
The function has two parameters. logID specifies the data log. The valid range is 0 to 15.
pRecordSize points to a variable that will hold the size of a record in the log.
The function returns TRUE if the operation succeeded. The function returns FALSE if the log
ID is invalid or if the data log does not exist.
Notes
This function is useful in determining how much memory must be allocated for a call to
datalogReadNext or datalogWrite.
See Also
datalogSettings
Example
See the example for datalogReadStart.
TelePACE C Tools User and Reference Manual
May 9, 2007
117
datalogSettings
Data Log Settings Function
Syntax
#include < ctools.h >
BOOLEAN datalogSettings(
UINT16 logID,
DATALOG_CONFIGURATION * pLogConfiguration
);
Description
This function reads the configuration of the specified data log. The log must have been
previously created with the datalogCreate function.
The function has two parameters. logID specifies the data log. The valid range is 0 to 15.
pLogConfiguration points to a structure that will hold the data log configuration.
The function returns TRUE if the operation succeeded. The function returns FALSE if the log
ID is invalid or if the data log does not exist.
Notes
The configuration of an existing data log cannot be changed. The log must be deleted and
recreated to change the configuration.
See Also
datalogRecordSize
Example
See example for datalogDelete.
TelePACE C Tools User and Reference Manual
May 9, 2007
118
datalogWrite
Write Data Log Function
Syntax
#include
BOOLEAN datalogWrite(
UINT16 logID,
UINT16 * pData
);
Description
This function writes a record to the specified data log. The log must have been previously
created with the datalogCreate function.
The function has two parameters. logID specifies the data log. The valid range is 0 to 15.
pData is a pointer to the data to be written to the log. The amount of data copied using the
pointer is determined by the configuration of the data log.
The function returns TRUE if the data is added to the log. The function returns FALSE if the
log ID is not valid or if the log does not exist.
Notes
Refer to the datalogCreate function for details on the configuration of the data log.
If the data log is full, then the oldest record in the log is replaced with this record.
See Also
datalogReadStart datalogReadNext datalogPurge
Example
See the example for datalogDelete.
TelePACE C Tools User and Reference Manual
May 9, 2007
119
dbase
Read Value from I/O Database
Syntax
#include
int dbase(unsigned type, unsigned address);
Description
The dbase function reads a value from the I/O database. type specifies the method of
addressing the database. address specifies the location in the database. The table below
shows the valid address types and ranges
Type
Address Ranges
MODBUS
00001 to NUMCOIL
10001 to 10000 + NUMSTATUS
30001 to 30000 + NUMINPUT
40001 to 40000 + NUMHOLDING
0 to NUMLINEAR-1
LINEAR
Register
Size
1 bit
1 bit
16 bit
16 bit
16 bit
Notes
Refer to the I/O Database and Register Assignment chapter for more information.
If the specified register is currently forced, dbase returns the forced value for the register.
The I/O database is not modified when the controller is reset. It is a permanent storage area,
which is maintained during power outages.
The IO_SYSTEM resource must be requested before calling this function.
See Also
setdbase
Example
#include
void main(void)
{
int a;
request_resource(IO_SYSTEM);
/* Read Modbus status input point */
a = dbase(MODBUS, 10001);
/* Read 16 bit register */
a = dbase(LINEAR, 3020);
/* Read 16 bit register beginning at first
status register */
a = dbase(LINEAR, START_STATUS);
/* Read 6th input register */
a = dbase(LINEAR, START_INPUT + 5);
TelePACE C Tools User and Reference Manual
May 9, 2007
120
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
121
deallocate_envelope
Return Envelope to the RTOS
Syntax
#include
void deallocate_envelope(envelope *penv);
Description
The deallocate_envelope function returns the envelope pointed to by penv to the pool of
free envelopes maintained by the operating system.
See Also
allocate_envelope
Example
See the example for the allocate_envelope function.
TelePACE C Tools User and Reference Manual
May 9, 2007
122
din
Read Digital I/O
Syntax
#include
int din(unsigned channel);
Description
The din function reads the value of a digital input or output channel. Reading an input
channel returns data read from a digital input module. Reading an output channel returns
the last value written to the output module.
The din function returns a value corresponding to the sum of the binary states of all 8 bits of
the channel.
Notes
The din function reads the status of digital input signals, and digital output modules.
The din function may be used to read the current values in the I/O disable, forced status and
I/O form tables, and I/O type tables.
Use offsets from the symbolic constants DIN_START, DIN_END, DOUT_START,
DOUT_END, EXTENDED_DIN_START, EXTENDED_DIN_END,
EXTENDED_DOUT_START and EXTENDED_DOUT_END to reference digital channels.
The constants make programs more portable and protect against future changes to the
digital I/O channel numbering.
The IO_SYSTEM resource must be requested before calling this function.
This function is provided for backward compatibility. It cannot access all 5000 series I/O
modules. It is recommended that this function not be used in new programs. Instead use
Register Assignment or call the I/O driver ioRead8Din directly.
See Also
pulse, timeout, turnon, turnoff, on, off
Example
This program displays the first 8 digital inputs in binary.
#include
void main(void)
{
int loop, value;
/* Read the first digital input channel */
request_resource(IO_SYSTEM);
value = din(DIN_START);
release_resource(IO_SYSTEM);
printf("Channel =");
/* For each bit in the channel */
for(loop = 8; loop; loop--)
TelePACE C Tools User and Reference Manual
May 9, 2007
123
{
putchar((value & 0x80) ? '1' :'0')
/* Select the next bit */
value <<= 1;
}
puts( "\r\n" );
}
TelePACE C Tools User and Reference Manual
May 9, 2007
124
dnpInstallConnectionHandler
Configures the connection handler for DNP.
Syntax
#include
void dnpInstallConnectionHandler(void (* function)
(DNP_CONNECTION_EVENT event));
Description
This function installs a handler that will permit user-defined actions to occur when DNP
requires a connection, message confirmation is received, or a timeout occurs.
function is a pointer to the handler function. If function is NULL the handler is disabled.
The function has no return value.
Notes
The handler function must process the event and return immediately. If the required action
involves waiting this must be done outside of the handler function. See the example below
for one possible implementation.
The application must disable the handler when the application ends. This prevents the
protocol driver from calling the handler while the application is stopped. Call the
dnpInstallConnectionHandler with a NULL pointer. The usual method is to create a
task exit handler function to do this. See the example below for details.
The handler function has one parameter.
•
event is DNP event that has occurred. It may be one of DNP_CONNECTION_REQUIRED,
DNP_MESSAGE_COMPLETE, or DNP_MESSAGE_TIMEOUT. See the structure definition for
the meaning of these events.
The handler function has no return value.
By default no connection handler is installed and no special steps are taken when DNP
requires a connection, receives a message confirmation, or a timeout occurs.
See Also
dnpConnectionEvent
Example
This example shows how a C application can handle the events and inform a logic
application of the events. The logic application is responsible for making and ending the dialup connection.
The program uses the following registers.
•
10001 turns on when a connection is requested by DNP for unsolicited reporting.
•
10002 turns on when the unsolicited report is complete.
•
10003 turns on when the unsolicited report is fails.
TelePACE C Tools User and Reference Manual
May 9, 2007
125
•
The ladder logic program turns on register 1 when the connection is complete and turns
off the register when the connection is broken.
/* ----------------------------------------------------------------------dnp.c
Demonstration program for using the DNP connection handler.
Copyright 2001, Control Microsystems Inc.
----------------------------------------------------------------------- */
/* ----------------------------------------------------------------------Include Files
----------------------------------------------------------------------- */
#include
/* ----------------------------------------------------------------------Constants
----------------------------------------------------------------------- */
#define CONNECTION_REQUIRED 10001
/* register for signaling connection required */
#define MESSAGE_COMPLETE
10002
/* register for signaling unsolicited message is
complete */
#define MESSAGE_FAILED
10003
/* register for signaling unsolicited message
failed */
#define CONNECTION_STATUS
1
/* connection status register */
/* ----------------------------------------------------------------------Private Functions
----------------------------------------------------------------------- */
/* ----------------------------------------------------------------------sampleDNPHandler
This function is the user defined DNP connection handler. It will be
called by internal DNP routines when a connection is required, when
confirmation of a message is received, and when a communication timeout
occurs.
The function takes a variable of type DNP_CONNECTION_EVENT as an input.
This input instructs the handler as to what functionality is required.
The valid choices are connection required (DNP_CONNECTION_REQUIRED),
message confirmation received (DNP_MESSAGE_COMPLETE), and timeout occurred
(DNP_MESSAGE_TIMEOUT).
The function does not return any values.
----------------------------------------------------------------------- */
static void sampleDNPHandler(DNP_CONNECTION_EVENT event)
{
/* Determine what connection event is required or just occurred */
switch(event)
{
case DNP_CONNECTION_REQUIRED:
/* indicate connection is needed and clear other bits */
request_resource(IO_SYSTEM);
setdbase(MODBUS, CONNECTION_REQUIRED, 1);
setdbase(MODBUS, MESSAGE_COMPLETE, 0);
setdbase(MODBUS, MESSAGE_FAILED, 0);
release_resource(IO_SYSTEM);
break;
case DNP_MESSAGE_COMPLETE:
/* indicate message sent and clear other bits */
request_resource(IO_SYSTEM);
setdbase(MODBUS, CONNECTION_REQUIRED, 0);
setdbase(MODBUS, MESSAGE_COMPLETE, 1);
setdbase(MODBUS, MESSAGE_FAILED, 0);
release_resource(IO_SYSTEM);
break;
case DNP_MESSAGE_TIMEOUT:
/* indicate message failed and clear other bits */
request_resource(IO_SYSTEM);
setdbase(MODBUS, CONNECTION_REQUIRED, 0);
setdbase(MODBUS, MESSAGE_COMPLETE, 0);
setdbase(MODBUS, MESSAGE_FAILED, 1);
release_resource(IO_SYSTEM);
TelePACE C Tools User and Reference Manual
May 9, 2007
126
break;
default:
/* ignore invalid requests */
break;
}
}
/* ----------------------------------------------------------------------Public Functions
----------------------------------------------------------------------- */
/* ----------------------------------------------------------------------main
This function is the main task of a user application. It monitors a
register from the ladder logic application. When the register value
changes, the function signals DNP events.
The function has no parameters.
The function does not return.
----------------------------------------------------------------------- */
void main(void)
{
int lastConnectionState;
/* last state of connection register */
int currentConnectionState;
/* current state of connection register */
/* install DNP connection handler */
dnpInstallConnectionHandler(sampleDNPHandler);
/* get the current connection state */
lastConnectionState = dbase(MODBUS, CONNECTION_STATUS);
/* loop forever */
while (TRUE)
{
request_resource(IO_SYSTEM);
/* get the current connection state */
currentConnectionState = dbase(MODBUS, CONNECTION_STATUS);
/* if the state has changed */
if (currentConnectionState != lastConnectionState)
{
/* if the connection is active */
if (currentConnectionState)
{
/* Inform DNP that a connection exists */
dnpConnectionEvent(DNP_CONNECTED);
/* clear the request flag */
setdbase(MODBUS, CONNECTION_REQUIRED, 0);
}
else
{
/* Inform DNP that the connection is closed */
dnpConnectionEvent(DNP_DISCONNECTED);
/* clear the message flags */
setdbase(MODBUS, MESSAGE_COMPLETE, 0);
setdbase(MODBUS, MESSAGE_FAILED, 0);
}
/* save the new state */
lastConnectionState = currentConnectionState;
}
/* release the processor so other tasks can run */
release_resource(IO_SYSTEM);
release_processor();
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
127
dnpClearEventLog
Clear DNP Event Log
Syntax:
#include
BOOLEAN dnpClearEventLog(void);
Description:
The dnpClearEventLogs function deletes all change events from the DNP change event
buffers, for all point types.
Example:
See the example in the section dnpSendUnsolicited.
TelePACE C Tools User and Reference Manual
May 9, 2007
128
dnpConnectionEvent
Report a DNP connection event
Syntax
#include
void dnpConnectionEvent(DNP_CONNECTION_EVENT event);
Description
dnpConnectionEvent is used to report a change in connection status to DNP. This
function is only used if a custom DNP connection handler has been installed.
event is current connection status. The valid connection status settings are
DNP_CONNECTED, and DNP_DISCONNECTED.
See Also
dnpInstallConnectionHandler
Example
See the dnpInstallConnectionHandler example.
TelePACE C Tools User and Reference Manual
May 9, 2007
129
dnpCreateRoutingTable
Create Routing Table
Syntax
#include
BOOLEAN createRoutingTable (UINT16 size);
Description
This function destroys any existing DNP routing table, and allocates memory for a new
routing table according to the ‘size’ parameter.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
The function returns TRUE if successful, FALSE otherwise.
Example
See the example in the section dnpSendUnsolicited.
TelePACE C Tools User and Reference Manual
May 9, 2007
130
dnpGenerateEventLog
Generate DNP Event Log
Syntax
#include
BOOLEAN dnpGenerateEventLog(
UINT16 pointType,
UINT16 pointAddress
);
Description
The dnpGenerateEventLog function generates a change event for the DNP point
specified by pointType and pointAddress.
pointType specifies the type of DNP point. Allowed values are:
BI_POINT
binary input
AI16_POINT
16 bit analog input
AI32_POINT
32 bit analog input
AISF_POINT
short float analog input
CI16_POINT
16 bit counter output
CI32_POINT
32 bit counter output
pointAddress specifies the DNP address of the point.
A change event is generated for the specified point (with the current time and current value),
and stored in the DNP event buffer.
The format of the event will depend on the Event Reporting Method and Class of Event
Object that have been configured for the point.
The function returns TRUE if the event was generated. It returns FALSE if the DNP point is
invalid, or if the DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
Example
See the example in the section dnpSendUnsolicited.
TelePACE C Tools User and Reference Manual
May 9, 2007
131
dnpGetAI16Config
Get DNP 16-bit Analog Input Configuration
Syntax
#include
BOOLEAN dnpGetAI16Config(
UINT16 point,
dnpAnalogInput * pAnalogInput
);
Description
This function reads the configuration of a DNP 16-bit analog input point.
The function has two parameters: the point number; and a pointer to an analog input point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpSaveAI16Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
132
dnpGetAI32Config
Get DNP 32-bit Analog Input Configuration
Syntax
#include
BOOLEAN dnpGetAI32Config(
UINT32 point,
dnpAnalogInput * pAnalogInput
);
Description
This function reads the configuration of a DNP 32-bit analog input point.
The function has two parameters: the point number; and a pointer to an analog input point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpSaveAI32Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
133
dnpGetAISFConfig
Get Short Floating Point Analog Input Configuration
Syntax
#include
BOOLEAN dnpGetAISFConfig (
UINT16 point,
dnpAnalogInput *pAnalogInput;
);
Description
This function reads the configuration of a DNP short floating point analog input point.
The function has two parameters: the point number, and a pointer to a configuration
structure.
The function returns TRUE if the configuration was successfully read, or FALSE otherwise (if
the point number is not valid, or pointer is NULL, or if the DNP configuration has not been
created).
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
TelePACE C Tools User and Reference Manual
May 9, 2007
134
dnpGetAO16Config
Get DNP 16-bit Analog Output Configuration
Syntax
#include
BOOLEAN dnpGetAO16Config(
UINT16 point,
dnpAnalogOutput * pAnalogOutput
);
Description
This function reads the configuration of a DNP 16-bit analog output point.
The function has two parameters: the point number; and a pointer to an analog output point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpSaveAO16Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
135
dnpGetAO32Config
Get DNP 32-bit Analog Output Configuration
Syntax
#include
BOOLEAN dnpGetAO32Config(
UINT32 point,
dnpAnalogOutput * pAnalogOutput
);
Description
This function reads the configuration of a DNP 32-bit analog output point.
The function has two parameters: the point number; and a pointer to an analog output point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpSaveAO32Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
136
dnpGetAOSFConfig
Get Short Floating Point Analog Output Configuration
Syntax
#include
BOOLEAN dnpGetAOSFConfig (
UINT16 point,
dnpAnalogOutput *pAnalogOutput;
);
Description
This function reads the configuration of a DNP short floating point analog output point.
The function has two parameters: the point number, and a pointer to a configuration
structure.
The function returns TRUE if the configuration was successfully read, or FALSE otherwise (if
the point number is not valid, or pointer is NULL, or if the DNP configuration has not been
created).
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
TelePACE C Tools User and Reference Manual
May 9, 2007
137
dnpGetBIConfig
Get DNP Binary Input Configuration
Syntax
#include
BOOLEAN dnpGetBIConfig(
UINT16 point,
dnpBinaryInput * pBinaryInput
);
Description
This function reads the configuration of a DNP binary input point.
The function has two parameters: the point number; and a pointer to a binary input point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpSaveBIConfig
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
138
dnpGetBIConfigEx
Read DNP Binary Input Extended Point
Syntax
BOOLEAN dnpGetBIConfigEx(
UINT16 point,
dnpBinaryInputEx *pBinaryInput
);
Description
This function reads the configuration of an extended DNP Binary Input point.
The function has two parameters: the point number, and a pointer to an extended binary
input point configuration structure.
The function returns TRUE if the configuration was successfully read. It returns FALSE if the
point number is not valid, if the configuration is not valid, or if the DNP configuration has not
been created.
This function supersedes dnpSaveBIConfig.
TelePACE C Tools User and Reference Manual
May 9, 2007
139
dnpGetBOConfig
Get DNP Binary Output Configuration
Syntax
#include
BOOLEAN dnpGetBOConfig(
UINT16 point,
dnpBinaryOutput * pBinaryOutput
);
Description
This function reads the configuration of a DNP binary output point.
The function has two parameters: the point number; and a pointer to a binary output point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
140
dnpGetCI16Config
Get DNP 16-bit Counter Input Configuration
Syntax
#include
BOOLEAN dnpGetCI16Config(
UINT16 point,
dnpCounterInput * pCounterInput
);
Description
This function reads the configuration of a DNP 16-bit counter input point.
The function has two parameters: the point number; and a pointer to a counter input point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpSaveCI16Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
141
dnpGetCI32Config
Get DNP 32-bit Counter Input Configuration
Syntax
#include
BOOLEAN dnpGetCI32Config(
UINT32 point,
dnpCounterInput * pCounterInput
);
Description
This function reads the configuration of a DNP 32-bit counter input point.
The function has two parameters: the point number; and a pointer to a counter input point
configuration structure.
The function returns TRUE if the configuration was read. It returns FALSE if the point
number is not valid, if the pointer is NULL, or if DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpSaveCI32Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
142
dnpGetConfiguration
Get DNP Configuration
Syntax
#include
BOOLEAN dnpGetConfiguration(
dnpConfiguration * pConfiguration
);
Description
This function reads the DNP configuration.
The function has one parameter: a pointer to a DNP configuration structure.
The function returns TRUE if the configuration was read and FALSE if an error occurred.
See Also
dnpSaveConfiguration
Example
The following program demonstrates how to configure DNP for operation on com2. To
illustrate creation of points it uses a sequential mapping of Modbus registers to points. This
is not required. Any mapping may be used.
void main(void)
{
UINT16 index;
struct prot_settings settings;
dnpConfiguration configuration;
dnpBinaryInput binaryInput;
dnpBinaryOutput binaryOutput;
dnpAnalogInput analogInput;
dnpAnalogOutput analogOutput;
dnpCounterInput counterInput;
/*
/*
/*
/*
/*
/*
/*
/*
loop index */
protocol settings */
configuration settings */
binary input settings */
binary output settings */
analog input settings */
analog output settings */
counter input settings */
/* Stop any protocol currently active on com port 2 */
get_protocol(com2,&settings);
settings.type = NO_PROTOCOL;
set_protocol(com2,&settings);
/* Load the Configuration Parameters */
configuration.masterAddress
= DEFAULT_DNP_MASTER;
configuration.rtuAddress
= DEFAULT_DNP_RTU;
configuration.datalinkConfirm
= TRUE;
configuration.datalinkRetries
= DEFAULT_DLINK_RETRIES;
configuration.datalinkTimeout
= DEFAULT_DLINK_TIMEOUT;
configuration.operateTimeout
configuration.applicationConfirm
configuration.maximumResponse
configuration.applicationRetries
configuration.applicationTimeout
configuration.timeSynchronization
=
=
=
=
=
=
DEFAULT_OPERATE_TIMEOUT;
TRUE;
DEFAULT_MAX_RESP_LENGTH;
DEFAULT_APPL_RETRIES;
DEFAULT_APPL_TIMEOUT;
TIME_SYNC;
configuration.BI_number
configuration.BI_cosBufferSize
configuration.BI_soeBufferSize
configuration.BO_number
configuration.CI16_number
configuration.CI16_bufferSize
configuration.CI32_number
=
=
=
=
=
=
=
8;
DEFAULT_COS_BUFF;
DEFAULT_SOE_BUFF;
8;
24;
48;
12;
TelePACE C Tools User and Reference Manual
May 9, 2007
143
configuration.CI32_bufferSize
configuration.AI16_number
configuration.AI16_reportingMethod
configuration.AI16_bufferSize
configuration.AI32_number
configuration.AI32_reportingMethod
configuration.AI32_bufferSize
configuration.AO16_number
configuration.AO32_number
=
=
=
=
=
=
=
=
=
24;
24;
CURRENT_VALUE;
24;
12;
CURRENT_VALUE;
12;
8;
8;
configuration.unsolicited
= TRUE;
configuration.holdTime
configuration.holdCount
= DEFAULT_HOLD_TIME;
= DEFAULT_HOLD_COUNT;
dnpSaveConfiguration(&configuration);
/* Start DNP protocol on com port 2 */
get_protocol(com2,&settings);
settings.type = DNP;
set_protocol(com2,&settings);
/* Save port settings so DNP protocol will automatically start */
request_resource(IO_SYSTEM);
save(EEPROM_RUN);
release_resource(IO_SYSTEM);
/* Configure Binary Output Points */
for (index = 0; index < configuration.BO_number; index++)
{
binaryOutput.modbusAddress1 = 1 + index;
binaryOutput.modbusAddress2 = 1 + index;
binaryOutput.controlType
= NOT_PAIRED;
dnpSaveBOConfig(index, &binaryOutput);
}
/* Configure Binary Input Points */
for (index = 0;index < configuration.BI_number; index++)
{
binaryInput.modbusAddress = 10001 + index;
binaryInput.class
= CLASS_1;
binaryInput.eventType
= COS;
dnpSaveBIConfig(index, &binaryInput);
}
/* Configure 16 Bit Analog Input Points */
for (index = 0; index < configuration.AI16_number; index++)
{
analogInput.modbusAddress = 30001 + index;
analogInput.class
= CLASS_2;
analogInput.deadband
= 1;
dnpSaveAI16Config(index, &analogInput);
}
/* Configure32 Bit Analog Input Points */
for (index = 0; index < configuration.AI32_number; index++)
{
analogInput.modbusAddress = 30001 + index * 2;
analogInput.class
= CLASS_2;
analogInput.deadband
= 1;
dnpSaveAI32Config(index,&analogInput);
}
/* Configure 16 Bit Analog Output Points */
for (index = 0;index < configuration.AO16_number; index++)
{
analogOutput.modbusAddress = 40001 + index;
dnpSaveAO16Config(index, &analogOutput);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
144
/* Configure 32 Bit Analog Output Points */
for (index = 0; index < configuration.AO32_number; index++)
{
analogOutput.modbusAddress = 40101 + index * 2;
dnpSaveAO32Config(index, &analogOutput);
}
/* Configure 16 Bit Counter Input Points */
for (index = 0; index < configuration.CI16_number; index++)
{
counterInput.modbusAddress = 30001 + index;
counterInput.class
= CLASS_3;
counterInput.threshold
= 1;
dnpSaveCI16Config(index, &counterInput);
}
/* Configure 32 bit Counter Input Points */
for (index = 0; index < configuration.CI32_number; index++)
{
counterInput.modbusAddress = 30001 + index * 2;
counterInput.class
= CLASS_3;
counterInput.threshold
= 1;
dnpSaveCI32Config(index, &counterInput);
}
/* add additional initialization code for your application here ... */
/* loop forever */
while (TRUE)
{
/* add additional code for your application here ... */
/* allow other tasks of this priority to execute */
release_processor();
}
return;
}
TelePACE C Tools User and Reference Manual
May 9, 2007
145
dnpGetConfigurationEx
Read DNP Extended Configuration
Syntax
BOOLEAN dnpGetConfigurationEx (
dnpConfigurationEx *pDnpConfigurationEx
);
Description
This function reads the extended DNP configuration parameters.
The function has one parameter: a pointer to the DNP extended configuration structure.
The function returns TRUE if the configuration was successfully read, or FALSE otherwise (if
the pointer is NULL, or if the DNP configuration has not been created).
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
This function supersedes the dnpGetConfiguration function.
TelePACE C Tools User and Reference Manual
May 9, 2007
146
dnpGetRuntimeStatus
Get DNP Runtime Status
Syntax:
#include
BOOLEAN dnpGetRuntimeStatus(
DNP_RUNTIME_STATUS *status
);
Description:
The dnpGetRuntimeStatus function reads the current status of all DNP change event
buffers, and returns information in the status structure.
DNP must be enabled before calling this function in order to create the DNP configuration.
Example:
See the example in the section dnpSendUnsolicited.
TelePACE C Tools User and Reference Manual
May 9, 2007
147
dnpReadRoutingTableDialStrings
Read DNP Routing Table Entry Dial Strings
Syntax
BOOLEAN dnpReadRoutingTableDialStrings(
UINT16 index,
UINT16 maxPrimaryDialStringLength,
CHAR *primaryDialString,
UINT16 maxSecondaryDialStringLength,
CHAR *secondaryDialString
);
Description
This function reads a primary and secondary dial string from an entry in the DNP routing
table.
index specifies the index of an entry in the DNP routing table.
maxPrimaryDialStringLength specifies the maximum length of primaryDialString
excluding the null-terminator character. The function uses this to limit the size of the returned
string to prevent overflowing the storage passed to the function.
primaryDialString returns the primary dial string of the target station. It must point to an
array of size maxPrimaryDialStringLength.
maxSecondaryDialStringLength specifies the maximum length of
secondaryDialString excluding the null-terminator character. The function uses this to
limit the size of the returned string to prevent overflowing the storage passed to the function.
secondaryDialString returns the secondary dial string of the target station. It must point
to an array of size maxSecondaryDialStringLength.
Notes
This function must be used in conjunction with the dnpReadRoutingTableEntry function
to read a complete entry in the DNP routing table.
TelePACE C Tools User and Reference Manual
May 9, 2007
148
dnpReadRoutingTableEntry
Read Routing Table entry
Syntax
#include
BOOLEAN dnpReadRoutingTableEntry (
UINT16 index,
routingTable *pRoute
);
Description
This function reads an entry from the routing table.
pRoute is a pointer to a table entry; it is written by this function.
The return value is TRUE if pRoute was successfully written or FALSE otherwise.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
The function returns the total number of entries in the DNP routing table.
TelePACE C Tools User and Reference Manual
May 9, 2007
149
dnpReadRoutingTableSize
Read Routing Table size
Syntax
#include
UINT16 dnpReadRoutingTableSize (void);
Description
This function reads the total number of entries in the routing table.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
The function returns the total number of entries in the routing table.
TelePACE C Tools User and Reference Manual
May 9, 2007
150
dnpSaveAI16Config
Save DNP 16-Bit Analog Input Configuration
Syntax
#include
BOOLEAN dnpSaveAI16Config(
UINT16 point,
dnpAnalogInput * pAnalogInput
);
Description
This function sets the configuration of a DNP 16-bit analog input point.
The function has two parameters: the point number; and a pointer to an analog input point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpGetAI16Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
151
dnpSaveAI32Config
Save DNP 32-Bit Analog Input Configuration
Syntax
#include
BOOLEAN dnpSaveAI32Config(
UINT32 point,
dnpAnalogInput * pAnalogInput
);
Description
This function sets the configuration of a DNP 32-bit analog input point.
The function has two parameters: the point number; and a pointer to an analog input point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpGetAI32Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
152
dnpSaveAISFConfig
Save Short Floating Point Analog Input Configuration
Syntax
#include
BOOLEAN dnpSaveAISFConfig (
UINT16 point,
dnpAnalogInput *pAnalogInput;
);
Description
This function sets the configuration of a DNP short floating point analog input point.
The function has two parameters: the point number, and a pointer to a configuration
structure.
The function returns TRUE if the configuration was successfully written, or FALSE otherwise
(if the point number is not valid, or the configuration is not valid, or if the DNP configuration
has not been created).
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
TelePACE C Tools User and Reference Manual
May 9, 2007
153
dnpSaveAO16Config
Save DNP 16-Bit Analog Output Configuration
Syntax
#include
BOOLEAN dnpSaveAO16Config(
UINT16 point,
dnpAnalogOutput * pAnalogOutput
);
Description
This function sets the configuration of a DNP 16-bit analog output point.
The function has two parameters: the point number; and a pointer to an analog output point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
154
dnpSaveAO32Config
Save DNP 32-Bit Analog Output Configuration
Syntax
#include
BOOLEAN dnpSaveAO32Config(
UINT32 point,
dnpAnalogOutput * pAnalogOutput
);
Description
This function sets the configuration of a DNP 32-bit analog output point.
The function has two parameters: the point number; and a pointer to an analog output point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpGetAO32Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
155
dnpSaveAOSFConfig
Save Short Floating Point Analog Output Configuration
Syntax
#include
BOOLEAN dnpSaveAOSFConfig (
UINT16 point,
dnpAnalogOutput *pAnalogOutput;
);
Description
This function sets the configuration of a DNP short floating point analog output point.
The function has two parameters: the point number, and a pointer to a configuration
structure.
The function returns TRUE if the configuration was successfully written, or FALSE otherwise
(if the point number is not valid, or the configuration is not valid, or if the DNP configuration
has not been created).
Notes
DNP must be enabled before calling this function in order to create the DNP
TelePACE C Tools User and Reference Manual
May 9, 2007
156
dnpSaveBIConfig
Save DNP Binary Input Configuration
Syntax
#include
BOOLEAN dnpSaveBIConfig(
UINT16 point,
dnpBinaryInput * pBinaryInput
);
Description
This function sets the configuration of a DNP binary input point.
The function has two parameters: the point number; and a pointer to a binary input point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
157
dnpSaveBIConfigEx
Write DNP Binary Input Extended Point
Syntax
BOOLEAN dnpSaveBIConfigEx(
UINT16 point,
dnpBinaryInputEx *pBinaryInput
);
Description
This function writes the configuration of an extended DNP Binary Input point.
The function has two parameters: the point number, and a pointer to an extended binary
input point configuration structure.
The function returns TRUE if the configuration was successfully written. It returns FALSE if
the point number is not valid, if the configuration is not valid, or if the DNP configuration has
not been created.
This function supersedes dnpSaveBIConfig.
TelePACE C Tools User and Reference Manual
May 9, 2007
158
dnpSaveBOConfig
Save DNP Binary Output Configuration
Syntax
#include
BOOLEAN dnpSaveBOConfig(
UINT16 point,
dnpBinaryOutput * pBinaryOutput
);
Description
This function sets the configuration of a DNP binary output point.
The function has two parameters: the point number; and a pointer to a binary output point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
159
dnpSaveCI16Config
Save DNP 16-Bit Counter Input Configuration
Syntax
#include
BOOLEAN dnpSaveCI16Config(
UINT16 point,
dnpCounterInput * pCounterInput
);
Description
This function sets the configuration of a DNP 16-bit counter input point.
The function has two parameters: the point number; and a pointer to a counter input point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpGetCI16Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
160
dnpSaveCI32Config
Save DNP 32-Bit Counter Input Configuration
Syntax
#include
BOOLEAN dnpSaveCI32Config(
UINT32 point,
dnpCounterInput * pCounterInput
);
Description
This function sets the configuration of a DNP 32-bit counter input point.
The function has two parameters: the point number; and a pointer to a counter input point
configuration structure.
The function returns TRUE if the configuration was written. It returns FALSE if the point
number is not valid, if the configuration is not valid, or if DNP configuration has not been
created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
See Also
dnpGetCI32Config
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
161
dnpSaveConfiguration
Save DNP Configuration
Syntax
#include
BOOLEAN dnpSaveConfiguration(
dnpConfiguration * pConfiguration
);
Description
This function sets the DNP configuration.
The function has one parameter: a pointer to a DNP configuration structure.
The function returns TRUE if the configuration was updated and FALSE if an error occurred.
No changes are made to any parameters if an error occurs.
Notes
This function must be called before enabling DNP.
The following parameters cannot be changed if DNP is enabled. The function will not make
any changes and will return FALSE if this is attempted. The protocol must be disabled in
order to make a change involving these parameters.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
BI_number
BI_cosBufferSize
BI_soeBufferSize
BO_number
CI16_number
CI16_bufferSize
CI32_number
CI32_bufferSize
AI16_number
AI16_reportingMethod
AI16_bufferSize
AI32_number
AI32_reportingMethod
AI32_bufferSize
AO16_number
AO32_number
The following parameters can be changed when DNP is enabled.
•
•
•
•
•
•
•
masterAddress;
rtuAddress;
datalinkConfirm;
datalinkRetries;
datalinkTimeout;
operateTimeout
applicationConfirm
TelePACE C Tools User and Reference Manual
May 9, 2007
162
•
•
•
•
•
•
•
maximumResponse
applicationRetries
applicationTimeout
timeSynchronization
unsolicited
holdTime
holdCount
See Also
dnpGetConfiguration
Example
See example in the dnpGetConfiguration function section.
TelePACE C Tools User and Reference Manual
May 9, 2007
163
dnpSaveConfigurationEx
Write DNP Extended Configuration
Syntax
BOOLEAN dnpSaveConfigurationEx (
dnpConfigurationEx *pDnpConfigurationEx
);
Description
This function writes the extended DNP configuration parameters.
The function has one parameter: a pointer to the DNP extended configuration structure.
The function returns TRUE if the configuration was successfully written, or FALSE otherwise
(if the pointer is NULL, or if the DNP configuration has not been created).
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
This function supersedes the dnpSaveConfiguration function.
TelePACE C Tools User and Reference Manual
May 9, 2007
164
dnpSearchRoutingTable
Search Routing Table
Syntax
#include
BOOLEAN dnpSearchRoutingTable (
UINT16 Address
routingTable *pRoute
);
Description
This function searches the routing table for a specific DNP address.
pRoute is a pointer to a table entry; it is written by this function.
The return value is TRUE if pRoute was successfully written or FALSE otherwise.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
TelePACE C Tools User and Reference Manual
May 9, 2007
165
dnpSendUnsolicited
Send DNP Unsolicited Response
Syntax
#include
UINT16 dnpSendUnsolicitedResponse(
UINT16 classFlags
);
Description
The dnpSendUnsolicitedResponse function sends an ‘Unsolicited Response’ message in
DNP protocol, with data from the specified class(es).
•
class specifies the class(es) of event data to include in the message.
•
Allowed values are
#define CLASS0_FLAG 0x01
*/
/* flag for enabling Class 0 Unsolicited Responses
#define CLASS1_FLAG 0x02
*/
/* flag for enabling Class 1 Unsolicited Responses
#define CLASS2_FLAG 0x04
*/
/* flag for enabling Class 2 Unsolicited Responses
#define CLASS3_FLAG 0x08
*/
/* flag for enabling Class 3 Unsolicited Responses
DNP must be enabled before calling this function in order to create the DNP configuration.
Example
/* -----------------------------------------------------------------SCADAPack 32 C++ Application Main Program
Copyright 2001 - 2002, Control Microsystems Inc.
Test application for new DNP API Functions.
written by James Wiles May 2003
This app was written for a ScadaPack 32P, running DNP on comm port
4.
--------------------------------------------------------------- */
#include
#include
/* -----------------------------------------------------------------Constants
--------------------------------------------------------------- */
/*
* Event Triggers :
* This application detects when these registers have been set,
* then performs the specified action and clears the register.
*/
#define CLEAR_EVENTS
100 /* Clear all DNP Event Log Buffers */
#define GENERATE_BI_EVENT 101 /* Generate a change event for BI
channel 0 */
TelePACE C Tools User and Reference Manual
May 9, 2007
166
#define GENERATE_AI16_EVENT
102 /* Generate a change event for 16bit AI channel 0 */
#define CLASS0_REPORT
103 /* Send an unsolicited report of Class
0 data */
/*
* Status Flags
*/
#define EVENTS_CLASS1
#define EVENTS_CLASS2
#define EVENTS_CLASS3
110
111
112
/*
* Status Registers
*/
#define EVENT_COUNT_AI16
#define EVENT_COUNT_BI
#define EVENT_COUNT_CLASS1
#define EVENT_COUNT_CLASS2
#define EVENT_COUNT_CLASS3
40102
40104
40106
40108
40110
/* -----------------------------------------------------------------main
This routine is the main application loop.
--------------------------------------------------------------- */
void main(void)
{
UINT16 index;
/* loop index */
struct prot_settings protocolSettings; /* protocol settings */
dnpConfiguration configuration;
dnpBinaryInput binaryInput;
dnpAnalogInput analogInput;
DNP_RUNTIME_STATUS dnpStatus;
int clear_events_flag;
int bi_event_flag;
int ai16_event_flag;
int class0_report_flag;
/* Set DNP Configuration */
configuration.masterAddress
configuration.rtuAddress
configuration.datalinkConfirm
configuration.datalinkRetries
configuration.datalinkTimeout
=
=
=
=
=
100;
1;
FALSE;
DEFAULT_DLINK_RETRIES;
DEFAULT_DLINK_TIMEOUT;
configuration.operateTimeout
configuration.applicationConfirm
configuration.maximumResponse
configuration.applicationRetries
configuration.applicationTimeout
configuration.timeSynchronization
=
=
=
=
=
=
DEFAULT_OPERATE_TIMEOUT;
FALSE;
DEFAULT_MAX_RESP_LENGTH;
DEFAULT_APPL_RETRIES;
DEFAULT_APPL_TIMEOUT;
NO_TIME_SYNC;
configuration.BI_number
configuration.BI_startAddress
configuration.BI_reportingMethod
configuration.BI_soeBufferSize
configuration.BO_number
configuration.BO_startAddress
configuration.CI16_number
configuration.CI16_startAddress
configuration.CI16_reportingMethod
configuration.CI16_bufferSize
configuration.CI32_number
configuration.CI32_startAddress
=
=
=
=
=
=
=
=
=
=
=
=
2;
0;
REPORT_ALL_EVENTS;
1000;
0;
0;
0;
0;
REPORT_ALL_EVENTS;
0;
0;
100;
TelePACE C Tools User and Reference Manual
May 9, 2007
167
configuration.CI32_reportingMethod
configuration.CI32_bufferSize
configuration.CI32_wordOrder
configuration.AI16_number
configuration.AI16_startAddress
configuration.AI16_reportingMethod
configuration.AI16_bufferSize
configuration.AI32_number
configuration.AI32_startAddress
configuration.AI32_reportingMethod
configuration.AI32_bufferSize
configuration.AI32_wordOrder
configuration.AISF_number
configuration.AISF_startAddress
configuration.AISF_reportingMethod
configuration.AISF_bufferSize
configuration.AISF_wordOrder
configuration.AO16_number
configuration.AO16_startAddress
configuration.AO32_number
configuration.AO32_startAddress
configuration.AO32_wordOrder
configuration.AOSF_number
configuration.AOSF_startAddress
configuration.AOSF_wordOrder
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
REPORT_ALL_EVENTS;
0;
MSW_FIRST;
2;
0;
REPORT_ALL_EVENTS;
1000;
0;
100;
REPORT_ALL_EVENTS;
0;
MSW_FIRST;
0;
200;
REPORT_CHANGE_EVENTS;
0;
MSW_FIRST;
0;
0;
0;
100;
MSW_FIRST;
0;
200;
MSW_FIRST;
configuration.autoUnsolicitedClass1
configuration.holdTimeClass1
configuration.holdCountClass1
configuration.autoUnsolicitedClass2
configuration.holdTimeClass2
configuration.holdCountClass2
configuration.autoUnsolicitedClass3
configuration.holdTimeClass3
configuration.holdCountClass3
=
=
=
=
=
=
=
=
=
TRUE;
10;
3;
TRUE;
10;
3;
TRUE;
10;
3;
dnpSaveConfiguration(&configuration);
/* Start DNP protocol on com port 4 */
get_protocol(com4, &protocolSettings);
protocolSettings.type = DNP;
set_protocol(com4, &protocolSettings);
/* Configure Binary Input Points */
for (index = 0;index < configuration.BI_number; index++)
{
binaryInput.modbusAddress = 10001 + index;
binaryInput.eventClass
= CLASS_1;
dnpSaveBIConfig(configuration.BI_startAddress + index,
&binaryInput);
}
/* Configure 16 Bit Analog Input Points */
for (index = 0; index < configuration.AI16_number; index++)
{
analogInput.modbusAddress = 40002 + index * 2;
analogInput.eventClass
= CLASS_2;
analogInput.deadband
= 1;
dnpSaveAI16Config(configuration.AI16_startAddress + index,
&analogInput);
}
/*
* Configure DNP Routing Table :
* station 100 via com4
* station 101 via com4
TelePACE C Tools User and Reference Manual
May 9, 2007
168
*/
dnpCreateRoutingTable(2);
dnpWriteRoutingTableEntry(0, 100, CIF_Com4, DEFAULT_DLINK_RETRIES,
DEFAULT_DLINK_TIMEOUT);
dnpWriteRoutingTableEntry(1, 101, CIF_Com4, DEFAULT_DLINK_RETRIES,
DEFAULT_DLINK_TIMEOUT);
/*
* main loop
*/
while (TRUE)
{
/* request IO resource */
request_resource(IO_SYSTEM);
/* read DNP status */
dnpGetRuntimeStatus(&dnpStatus);
setdbase(MODBUS, EVENTS_CLASS1, dnpStatus.eventCountClass1 ? 1
: 0);
setdbase(MODBUS, EVENTS_CLASS2, dnpStatus.eventCountClass2 ? 1
: 0);
setdbase(MODBUS, EVENTS_CLASS3, dnpStatus.eventCountClass3 ? 1
: 0);
setdbase(MODBUS, EVENT_COUNT_AI16, dnpStatus.eventCountAI16);
setdbase(MODBUS, EVENT_COUNT_BI, dnpStatus.eventCountBI);
setdbase(MODBUS, EVENT_COUNT_CLASS1,
dnpStatus.eventCountClass1);
setdbase(MODBUS, EVENT_COUNT_CLASS2,
dnpStatus.eventCountClass2);
setdbase(MODBUS, EVENT_COUNT_CLASS3,
dnpStatus.eventCountClass3);
release_resource(IO_SYSTEM);
clear_events_flag = FALSE;
bi_event_flag = FALSE;
ai16_event_flag = FALSE;
class0_report_flag = FALSE;
/* Read Event Triggers */
if (dbase(MODBUS, CLEAR_EVENTS))
{
setdbase(MODBUS, CLEAR_EVENTS, 0);
clear_events_flag = TRUE;
}
if (dbase(MODBUS, GENERATE_BI_EVENT))
{
setdbase(MODBUS, GENERATE_BI_EVENT, 0);
bi_event_flag = FALSE;
}
if (dbase(MODBUS, GENERATE_AI16_EVENT))
{
setdbase(MODBUS, GENERATE_AI16_EVENT, 0);
ai16_event_flag = FALSE;
}
if (dbase(MODBUS, CLASS0_REPORT))
{
setdbase(MODBUS, CLASS0_REPORT, 0);
class0_report_flag = FALSE;
}
/* release IO resource */
release_resource(IO_SYSTEM);
TelePACE C Tools User and Reference Manual
May 9, 2007
169
/* Clear DNP Event Log buffer if requested */
if (clear_events_flag)
{
dnpClearEventLog();
}
/* Generate a DNP Change Event for BI Point 0 if requested */
if (bi_event_flag)
{
dnpGenerateEventLog(BI_POINT, 0);
}
/* Generate a DNP Change Event for 16-bit AI Point 0 if
requested */
if (ai16_event_flag)
{
dnpGenerateEventLog(AI16_POINT, 0);
}
/* Send DNP Class 0 Unsolicited Report if requested */
if (class0_report_flag)
{
dnpSendUnsolicitedResponse(CLASS0_FLAG);
}
/* release processor to other tasks */
release_processor();
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
170
dnpSendUnsolicitedResponse
Send DNP Unsolicited Response
Syntax
BOOLEAN dnpSendUnsolicitedResponse(
UINT16 classFlags
);
Description
The dnpSendUnsolicitedResponse function sends an Unsolicited Response message
in DNP, with data from the specified classes.
class specifies the class or classes of event data to include in the message. It can contain
any combination of the following values; if multiple values are used they should be ORed
together:
CLASS0_FLAG
enables Class 0 Unsolicited Responses
CLASS1_FLAG
enables Class 1 Unsolicited Responses
CLASS2_FLAG
enables Class 2 Unsolicited Responses
CLASS3_FLAG
enables Class 3 Unsolicited Responses
The function returns TRUE if the DNP unsolicited response message was successfully
triggered. It returns FALSE if an unsolicited message of the same class is already pending,
or if the DNP configuration has not been created.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
If no events are pending an empty unsolicited message will be sent.
TelePACE C Tools User and Reference Manual
May 9, 2007
171
dnpWriteRoutingTableEntry
Write Routing Table Entry
Syntax
#include
BOOLEAN dnpWriteRoutingTableEntry (
UINT16 index,
UINT16 dnpAddress,
UINT16 commPort,
UINT16 DataLinkRetries,
UINT16 DataLinkTimeout
);
Description
This function writes an entry in the DNP routing table.
Notes
DNP must be enabled before calling this function in order to create the DNP configuration.
The function returns TRUE if successful, FALSE otherwise.
Example
See the example in the section dnpSendUnsolicited.
TelePACE C Tools User and Reference Manual
May 9, 2007
172
dnpWriteRoutingTableDialStrings
Write DNP Routing Table Entry Dial Strings
Syntax
BOOLEAN dnpWriteRoutingTableDialStrings(
UINT16 index,
UINT16 primaryDialStringLength,
CHAR *primaryDialString,
UINT16 secondaryDialStringLength,
CHAR *secondaryDialString
);
Description
This function writes a primary and secondary dial string into an entry in the DNP routing
table.
index specifies the index of an entry in the DNP routing table.
primaryDialStringLength specifies the length of primaryDialString excluding the
null-terminator character.
primaryDialString specifies the dial string used when dialing the target station. This
string is used on the first attempt.
secondaryDialStringLength specifies the length of secondaryDialString
excluding the null-terminator character.
secondaryDialString specifies the dial string to be used when dialing the target station.
It is used for the next attempt if the first attempt fails.
Notes
This function must be used in conjunction with the dnpWriteRoutingTableEntry
function to write a complete entry in the DNP routing table.
TelePACE C Tools User and Reference Manual
May 9, 2007
173
dout
Write Digital Outputs
Syntax
#include
int dout(unsigned channel, unsigned value);
Description
The dout function outputs value to the digital input or output specified by channel. It sets the
status of 8 digital points.
The dout function returns the value output to the channel, as modified by the channel
configuration tables. If channel is not valid, –1 is returned.
Notes
The dout function modifies all 8 bits (points) in a channel. Use the turnon and turnoff
functions to write to single bits.
Use offsets from the symbolic constants DIN_START, DIN_END, EXTENDED_DIN_START,
EXTENDED_DIN_END, DOUT_START, DOUT_END, EXTENDED_DOUT_START and
EXTENDED_DOUT_END to reference digital channels. The constants make programs more
portable and protect against future changes to the digital I/O channel numbering.
The IO_SYSTEM resource must be requested before calling this function.
This function is provided for backward compatibility. It cannot access all 5000 series I/O
modules. It is recommended that this function not be used in new programs. Instead use
Register Assignment or call the I/O driver ioWrite8Dout directly.
See Also
ioWrite8Dout, din, pulse, timeout, turnon, turnoff, on, off
Example
This program sends all bit combinations to the second digital output channel.
#include
void main(void)
{
unsigned value;
/* output values */
for (value = 0; value; value++)
{
request_resource(IO_SYSTEM);
dout(DOUT_START + 1, value);
release_resource(IO_SYSTEM);
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
174
end_application
Terminates all Application Tasks
Syntax
#include
void end_application(void);
Description
The end_application function terminates all APPLICATION type tasks created with the
create_task function. Stack space and resources used by the tasks are freed.
Notes
This function is used normally by communication protocols to stop an executing application
program, prior to loading a new program into memory.
See Also
create_task, end_task
TelePACE C Tools User and Reference Manual
May 9, 2007
175
end_task
Terminate a Task
Syntax
#include
void end_task(unsigned task_ID);
Description
The end_task function terminates the task specified by task_ID. Stack space and resources
used by the task are freed. The end_task function terminates both APPLICATION and
SYSTEM type tasks.
See Also
create_task, end_application, getTaskInfo
TelePACE C Tools User and Reference Manual
May 9, 2007
176
endTimedEvent
Terminate Signaling of a Regular Event
Syntax
#include
unsigned endTimedEvent(unsigned event);
Description
This endTimedEvent function cancels signaling of a timed event, initialized by the
startTimedEvent function.
The function returns TRUE if the event signaling was canceled.
The function returns FALSE if the event number is not valid, or if the event was not
previously initiated with the startTimedEvent function. The function has no effect in these
cases.
Notes
Valid events are numbered 0 to RTOS_EVENTS - 1. Any events defined in ctools.h are not
valid events for use in an application program.
Example
See the examples for startTimedEvent.
See Also
startTimedEvent
TelePACE C Tools User and Reference Manual
May 9, 2007
177
enronInstallCommandHandler
Installs handler for Enron Modbus commands.
Syntax
#include
void enronInstallCommandHandler(
UINT16 (* function)(
UINT16
length,
UCHAR * pCommand,
UINT16
responseSize,
UINT16 * pResponseLength,
UCHAR * pResponse
)
);
Description
This function installs a handler function for Enron Modbus commands. The protocol driver
calls this handler function each time a command is received for the Enron Modbus station.
function is a pointer to the handler function. If function is NULL the handler is disabled.
The function has no return value.
Notes
The application must disable the handler when the application ends. This prevents the
protocol driver from calling the handler while the application is stopped. Call the
enronInstallCommmandHandler with a NULL pointer. The usual method is to create a
task exit handler function to do this. See the example below for details.
The handler function has five parameters.
•
length is the number of characters in the command message.
•
pCommand is a pointer to the command message. The first byte in the message is the
function code, followed by the Enron Modbus message. See the Enron Modbus protocol
specification for details on the message formats.
•
responseSize is the size of the response buffer in characters.
•
pResponseLength is a pointer to a variable that will hold the number of characters in
the response. If the handler returns TRUE, it must set this variable.
•
pResponse is a pointer to a buffer that will hold the response message. The buffer size
is responseSize characters. The handler must not write beyond the end of the buffer.
If the handler returns TRUE, it must set this variable. The data must start with the
function code and end with the last data byte. The protocol driver will add the station
address, checksum, and message framing to the response.
The handler function returns the following values.
Value
NORMAL
ILLEGAL_FUNCTION
TelePACE C Tools User and Reference Manual
May 9, 2007
Description
Indicates protocol handler should send a normal
response message. Data are returned using
pResponse and pResponseLength.
Indicates protocol handler should send an Illegal
Function exception response message. This
178
Value
ILLEGAL_DATA_ADDRESS
ILLEGAL_DATA_VALUE
Description
response should be used when the function code
in the command is not recognised.
Indicates protocol handler should send an Illegal
Data Address exception response message. This
response should be used when the data address
in the command is not recognised.
Indicates protocol handler should send an Illegal
Data Value exception response message. This
response should be used when invalid data is
found in the command.
If the function returns NORMAL then the protocol driver sends the response message in the
buffer pointed to by pResponse. If the function returns an exception response protocol
driver returns the exception response to the caller. The buffer pointed to by pResponse is
not used.
Example
This program installs a simple handler function.
#include
/* ----------------------------------------------------This function processes Enron Modbus commands.
----------------------------------------------------- */
UINT16 commandHandler(
UINT16
length,
UCHAR * pCommand,
UINT16
responseSize,
UINT16 * pResponseLength,
UCHAR * pResponse
)
{
UCHAR command;
UINT16 result;
/* if a command byte was received */
if (length >= 1)
{
/* get the command byte */
command = pCommand[0];
switch (command)
{
/* read unit status command */
case 7:
/* if the response buffer is large enough */
if (responseSize > 2)
{
/* build the response header */
pResponse[0] = pCommand[0];
/* set the unit status */
pResponse[1] = 17;
/* set response length */
*pResponseLength = 2;
TelePACE C Tools User and Reference Manual
May 9, 2007
179
/* indicate the command worked */
result = NORMAL;
}
else
{
/* buffer is to small to respond */
result = ILLEGAL_FUNCTION;
}
break;
/* add cases for other commands here */
default:
/* command is invalid */
result = ILLEGAL_FUNCTION;
}
}
else
{
/* command is too short so return error */
result = ILLEGAL_FUNCTION;
}
return result;
}
/* ----------------------------------------------------This function unhooks the protocol handler when the
main task ends.
----------------------------------------------------- */
void mainExitHandler(void)
{
/* unhook the handler function */
enronInstallCommandHandler(NULL);
}
void main(void)
{
TASKINFO thisTask;
/* install handler to execute when this task ends */
thisTask = getTaskInfo(0);
installExitHandler(thisTask.taskID, mainExitHandler);
/* install handler for Enron Modbus */
enronInstallCommandHandler(commandHandler);
/* infinite loop of main task */
while (TRUE)
{
/* add application code here */
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
180
forceLed
Set State of Force LED
Syntax
#include
void forceLed(unsigned state);
Description
The forceLed function sets the state of the FORCE LED. state may be either LED_ON or
LED_OFF.
Notes
The FORCE LED is used to indicate forced I/O. Use this function with caution in application
programs.
See Also
setStatus
TelePACE C Tools User and Reference Manual
May 9, 2007
181
getABConfiguration
Get DF1 Protocol Configuration
Syntax
#include
struct ABConfiguration *getABConfiguration(FILE *stream, struct
ABConfiguration *ABConfig);
Description
The getABConfiguration function gets the DF1 protocol configuration parameters for the
stream. If stream does not point to a valid serial port the function has no effect. ABConfig
must point to an DF1 protocol configuration structure.
The getABConfiguration function copies the DF1 configuration parameters into the
ABConfig structure and returns a pointer to it.
Example
This program displays the DF1 configuration parameters for com1.
#include
void main(void)
{
struct ABConfiguration ABConfig;
getABConfiguration(com1, &ABConfig);
printf("Min protected address:
%u\r\n",
ABConfig.min_protected_address);
printf("Max protected address:
%u\r\n",
ABConfig.max_protected_address);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
182
getBootType
Get Controller Boot Up State
Syntax
#include
unsigned getBootType(void);
Description
The getBootType function returns the boot up state of the controller. The possible return
values are:
SERVICE
RUN
controller started in SERVICE mode
controller started in RUN mode
Example
#include
void main(void)
{
struct prot_settings settings;
/* Disable the protocol on serial port 1 */
settings.type = NO_PROTOCOL;
settings.station = 1;
settings.priority = 3;
settings.SFMessaging = FALSE;
request_resource(IO_SYSTEM);
set_protocol(com1, &settings);
release_resource(IO_SYSTEM);
/* Display the boot status information */
printf("Boot type: %d\r\n", getBootType());
}
TelePACE C Tools User and Reference Manual
May 9, 2007
183
getclock
Read the Real Time Clock
Syntax
#include
struct clock getclock(void);
Description
The getclock function reads the time and date from the real time clock hardware.
The getclock function returns a struct clock containing the time and date information.
Notes
The time format returned by the getclock function is not compatible with the standard UNIX
style functions supplied by Microtec.
The IO_SYSTEM resource must be requested before calling this function.
See Also
setclock, getClockTime
Example
This program displays the current date and time.
#include
main(void)
{
struct clock now;
request_resource(IO_SYSTEM);
now = getclock();
/* read the clock */
release_resource(IO_SYSTEM);
printf("%2d/%2d/%2d", now.day,
now.month, now.year);
printf("%2d:%2d\r\n",now.hour, now.minute);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
184
getClockAlarm
Read the Real Time Clock Alarm Settings
Syntax
#include
ALARM_SETTING getClockAlarm(void);
Description
The getClockAlarm function returns the alarm setting in the real time clock. The alarm is
used to wake the controller from sleep mode.
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
alarmIn, setClockAlarm
TelePACE C Tools User and Reference Manual
May 9, 2007
185
getClockTime
Read the Real Time Clock
Syntax
#include
void getClockTime(long * pDays, long * pHundredths);
Description
The getClockTime function reads the read time clock and returns the value as the number of
whole days since 01/01/97 and the number of hundredths of a second since the start of the
current day. The function works for 100 years from 01/01/97 to 12/31/96 then rolls over.
The function has two parameters: a pointer to the variable to hold the days; and a pointer to
a variable to hold the hundredths of a second.
The function has no return value.
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
setclock, getclock
TelePACE C Tools User and Reference Manual
May 9, 2007
186
getControllerID
Get Controller ID
Syntax
#include
void getControllerID(CHAR * pID)
Description
This function writes the Controller ID to the string pointed to by pID. The Controller ID is a
unique ID for the controller set at the factory. The pointer pID must point to a character string
of length CONTROLLER_ID_LEN.
Example
This program displays the Controller ID.
#include
void main(void)
{
char
ctlrID[CONTROLLER_ID_LEN];
UINT16 index;
getControllerID(ctlrID);
fprintf(com1, "\r\nController ID : ");
for (index=0; index
unsigned getForceFlag(unsigned type, unsigned address, unsigned *value);
Description
The getForceFlag function copies the value of the force flag for the specified database
register into the integer pointed to by value. The valid range for address is determined by the
database addressing type.
The force flag value is either 1 or 0, or a 16-bit mask for LINEAR digital addresses.
If the address or addressing type is not valid, FALSE is returned and the integer pointed to
by value is 0; otherwise TRUE is returned. The table below shows the valid address types
and ranges.
Type
Address Ranges
MODBUS
00001 to NUMCOIL
10001 to 10000 + NUMSTATUS
30001 to 30000 + NUMINPUT
40001 to 40000 + NUMHOLDING
0 to NUMLINEAR-1
LINEAR
Register
Size
1 bit
1 bit
16 bit
16 bit
16 bit
Notes
Force Flags are not modified when the controller is reset. Force Flags are in a permanent
storage area, which is maintained during power outages.
Refer to the I/O Database and Register Assignment chapter for more information.
See Also
setForceFlag, clearAllForcing, overrideDbase
Example
This program obtains the force flag state for register 40001, for the 16 status registers at
linear address 302 (i.e. registers 10737 to 10752), and for the holding register at linear
address 1540 (i.e. register 40005).
#include
void main(void)
{
unsigned flag, bitmask;
getForceFlag(MODBUS, 40001, &flag);
getForceFlag(LINEAR, 302, &bitmask);
getForceFlag(LINEAR, 1540, &flag);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
188
getIOErrorIndication
Get I/O Module Error Indication
Syntax
#include
unsigned getIOErrorIndication(void);
Description
The getIOErrorIndication function returns the state of the I/O module error indication.
TRUE is returned if the I/O module communication status is currently reported in the
controller status register and Status LED. FALSE is returned if the I/O module
communication status is not reported.
Notes
Refer to the 5203/4 System Manual or the SCADAPack System Manual for further
information on the Status LED and Status Output.
See Also
setIOErrorIndication
TelePACE C Tools User and Reference Manual
May 9, 2007
189
getOutputsInStopMode
Get Outputs In Stop Mode
Syntax
#include
void getOutputsInStopMode( unsigned *doutsInStopMode, unsigned
*aoutsInStopMode);
Description
The getOutputsInStopMode function copies the values of the output control flags into the
integers pointed to by doutsInStopMode and aoutsInStopMode.
If the value pointed to by doutsInStopMode is TRUE, then digital outputs are held at their
last state when the Ladder Logic program is stopped.
If the value pointed to by doutsInStopMode is FALSE, then digital outputs are turned OFF
when the Ladder Logic program is stopped.
If the value pointed to by aoutsInStopMode is TRUE, then analog outputs are held at their
last value when the Ladder Logic program is stopped.
If the value pointed to by aoutsInStopMode is FALSE, then analog outputs go to zero when
the Ladder Logic program is stopped.
See Also
setOutputsInStopMode
Example
See the example for setOutputsInStopMode function.
TelePACE C Tools User and Reference Manual
May 9, 2007
190
getPortCharacteristics
Get Serial Port Characteristics
Syntax
#include
unsigned getPortCharacteristics(FILE *stream, PORT_CHARACTERISTICS
*pCharacteristics);
Description
The getPortCharacteristics function gets information about features supported by the
serial port pointed to by stream. If stream does not point to a valid serial port the function
has no effect and FALSE is returned; otherwise TRUE is returned.
The getPortCharacteristics function copies the serial port characteristics into the structure
pointed to by pCharacteristics.
Notes
Refer to the Overview of Functions section for detailed information on serial ports.
Refer to the Structures and Types section for a description of the fields in the
PORT_CHARACTERISTICS structure.
See Also
get_port
Example
#include
void main(void)
{
PORT_CHARACTERISTICS options;
getPortCharacteristics(com3, &options);
fprintf(com1, "Dataflow options: %d\r\n",
options.dataflow);
fprintf(com1, "Protocol options: %d\r\n",
options.protocol);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
191
getPowerMode
Get Current Power Mode
Syntax
#include
BOOLEAN getPowerMode(UCHAR* cpuPower, UCHAR* lan, UCHAR* usbPeripheral,
UCHAR* usbHost);
Description
The getPowerMode function places the current state of the CPU, LAN, USB peripheral port,
and USB host port in the passed parameters. The following table lists the possible return
values and their meaning.
Macro
PM_CPU_FULL
PM_CPU_REDUCED
PM_CPU_SLEEP
PM_LAN_ENABLED
PM_LAN_DISABLED
PM_USB_PERIPHERAL_ENABLED
PM_USB_PERIPHERAL_DISABLED
PM_USB_HOST_ENABLED
PM_USB_HOST_DISABLED
PM_UNAVAILABLE
Meaning
The CPU is set to run at full speed
The CPU is set to run at a reduced speed
The CPU is set to sleep mode
The LAN is enabled
The LAN is disabled
The USB peripheral port is enabled
The USB peripheral port is disabled
The USB host port is enabled
The USB host port is disabled
The status of the device could not be read.
TRUE is returned if the values placed in the passed parameters are valid, otherwise FALSE
is returned.
The application program may set the current power mode with the setPowerMode function.
See Also
setPow erMode, setWakeSource, getWakeSource
TelePACE C Tools User and Reference Manual
May 9, 2007
192
get_pid
Get PID Variable
Syntax
#include
int get_pid(unsigned name, unsigned block);
Description
The get_pid function returns the value of a PID control block variable. name must be
specified by one of the variable name macros in pid.h. block must be in the range 0 to
PID_BLOCKS-1.
Notes
See the TelePACE PID Controllers Manual for a detailed description of PID control.
Values stored in PID blocks are not initialized when a program is run, and are guaranteed to
retain their values during power failures and program loading. The user program must
always initialize PID block variables.
The IO_SYSTEM resource must be requested before calling this function.
See Also
set_pid, auto_pid, clear_pid
TelePACE C Tools User and Reference Manual
May 9, 2007
193
get_port
Get Serial Port Configuration
Syntax
#include
struct pconfig *get_port(FILE *stream, struct pconfig *settings);
Description
The get_port function gets the serial port configuration for the stream. If stream does not
point to a valid serial port the function has no effect.
The get_port function copies the serial port settings into the structure pointed to by settings
and returns a pointer to the structure.
Notes
Refer to the Overview of Functions section for detailed information on serial ports.
Refer to the Structure and Types section for a description of the fields in the pconfig
structure.
See Also
set_port
Example
#include
void main(void)
{
struct pconfig settings;
get_port(com1, &settings);
printf("Baud rate: %d\r\n", settings.baud);
printf("Duplex:
%d\r\n", settings.duplex);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
194
getProgramStatus
Get Program Status Flag
Syntax
#include
unsigned getProgramStatus( void );
Description
The getProgramStatus function returns the application program status flag. The status flag
is set to NEW_PROGRAM when the C program is erased or downloaded to the controller
from the program loader.
The application program may modify the status flag with the setProgramStatus function.
See Also
setPowerMode
Set Current Power Mode
Syntax
#include
BOOLEAN setPowerMode(UCHAR cpuPower, UCHAR lan, UCHAR usbPeripheral, UCHAR
usbHost);
Description
The setPowerMode function returns TRUE if the new settings were successfully applied.
The setPowerMode function allows for power savings to be realized by controlling the power
to the LAN port, changing the clock speed, and individually controlling the host and
peripheral USB power. The following table of macros summarizes the choices available.
Macro
PM_CPU_FULL
PM_CPU_REDUCED
PM_CPU_SLEEP
PM_LAN_ENABLED
PM_LAN_DISABLED
PM_USB_PERIPHERAL_ENABLED
PM_USB_PERIPHERAL_DISABLED
PM_USB_HOST_ENABLED
PM_USB_HOST_DISABLED
PM_NO_CHANGE
Meaning
The CPU is set to run at full speed
The CPU is set to run at a reduced speed
The CPU is set to sleep mode
The LAN is enabled
The LAN is disabled
The USB peripheral port is enabled
The USB peripheral port is disabled
The USB host port is enabled
The USB host port is disabled
The current value will be used
TRUE is returned if the requested change was made, otherwise FALSE is returned.
The application program may view the current power mode with the getPowerMode
function.
See Also
getPowerMode, setWakeSource, getWakeSource
TelePACE C Tools User and Reference Manual
May 9, 2007
195
setProgramStatus
Example
This program stores a default alarm limit into the I/O database the first time it is run. On
subsequent executions, it uses the limit in the database. The limit in the database can be
modified by a communication protocol during execution.
#include
#define HI_ALARM
41000
#define ALARM_OUTPUT
1026
void main( void )
{
int inputValue;
if (getProgramStatus() == NEW_PROGRAM)
{
/* Set default alarm limit */
request_resource(IO_SYSTEM);
setdbase(MODBUS, HI_ALARM, 4000);
release_resource(IO_SYSTEM);
/* Use values in database from now on */
setProgramStatus(PROGRAM_EXECUTED);
}
while (TRUE)
{
request_resource(IO_SYSTEM);
/* Test input against alarm limits */
if (ain(INPUT) > dbase(MODBUS, HI_ALARM))
setdbase(MODBUS, ALARM_OUTPUT, 1);
else
setdbase(MODBUS, ALARM_OUTPUT, 0);
release_resource(IO_SYSTEM);
/* Allow other tasks to execute */
release_processor();
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
196
get_protocol
Get Protocol Configuration
Syntax
#include
struct prot_settings *get_protocol(FILE *stream, struct prot_settings
*settings);
Description
The get_protocol function gets the communication protocol configuration for the stream. If
stream does not point to a valid serial port the function has no effect. settings must point to a
protocol configuration structure, prot_settings.
The get_protocol function copies the protocol settings into the structure pointed to by
settings and returns a pointer to that structure.
Refer to the ctools.h file for a description of the fields in the prot_settings structure.
Refer to the Overview of Functions section for detailed information on communication
protocols.
See Also
set_protocol
Example
This program displays the protocol configuration for com1.
#include
void main(void)
{
struct prot_settings settings;
get_protocol(com1, &settings);
printf("Type:
%d\r\n", settings.type);
printf("Station: %d\r\n", settings.station);
printf("Priority: %d\r\n", settings.priority);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
197
getProtocolSettings
Get Protocol Extended Addressing Configuration
Syntax
#include
BOOLEAN getProtocolSettings(
FILE * stream,
PROTOCOL_SETTINGS * settings
);
Description
The getProtocolSettings function reads the protocol parameters for a serial port. This
function supports extended addressing.
The function has two parameters: stream is one of com1, com2, com3 or com4; and
settings, a pointer to a PROTOCOL_SETTINGS structure. Refer to the description of the
structure for an explanation of the parameters.
The function returns TRUE if the structure was changed. It returns FALSE if the stream is
not valid.
Notes
Extended addressing is available on the Modbus RTU and Modbus ASCII protocols only.
See the TeleBUS Protocols User Manual for details.
Refer to the TeleBUS Protocols User Manual section for detailed information on
communication protocols.
See Also
setProtocolSettings, get_protocol
Example
This program displays the protocol configuration for com1.
#include
void main(void)
{
PROTOCOL_SETTINGS settings;
if (getProtocolSettings(com1, &settings)
{
printf("Type: %d\r\n", settings.type);
printf("Station: %d\r\n", settings.station);
printf("Address Mode: %d\r\n", settings.mode);
printf("SF Messaging: %d\r\n", settings.SFMessaging);
printf("Priority: %d\r\n", settings.priority);
}
else
{
printf(“Serial port is not valid\r\n”);
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
198
getProtocolSettingsEx
Reads extended protocol settings for a serial port.
Syntax
#include
BOOLEAN getProtocolSettingsEx(
FILE * stream,
PROTOCOL_SETTINGS_EX * pSettings
);
Description
The setProtocolSettingsEx function sets protocol parameters for a serial port. This
function supports extended addressing and Enron Modbus parameters.
The function has two arguments:
•
stream specifies the serial port. It is one of com1, com2, com3 or com4.
•
pSettings is a pointer to a PROTOCOL_SETTINGS_EX structure. Refer to the
description of the structure for an explanation of the parameters.
The function returns TRUE if the settings were retrieved. It returns FALSE if the stream is not
valid.
Notes
Extended addressing and the Enron Modbus station are available on the Modbus RTU and
Modbus ASCII protocols only. See the TeleBUS Protocols User Manual for details.
See Also
setProtocolSettingsEx
Example
This program displays the protocol configuration for com1.
#include
void main(void)
{
PROTOCOL_SETTINGS_EX settings;
if (getProtocolSettingsEx(com1, &settings)
{
printf("Type: %d\r\n", settings.type);
printf("Station: %d\r\n", settings.station);
printf("Address Mode: %d\r\n", settings.mode);
printf("SF: %d\r\n", settings.SFMessaging);
printf("Priority: %d\r\n", settings.priority);
printf("Enron: %d\r\n", settings.enronEnabled);
printf("Enron station: %d\r\n",
settings.enronStation);
}
else
{
printf(“Serial port is not valid\r\n”);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
199
}
TelePACE C Tools User and Reference Manual
May 9, 2007
200
get_protocol_status
Get Protocol Information
Syntax
#include
struct prot_status get_protocol_status(FILE *stream);
Description
The get_protocol_status function returns the protocol error and message counters for
stream. If stream does not point to a valid serial port the function has no effect.
Refer to the Overview of Functions section for detailed information on communication
protocols.
See Also
clear_protocol_status
Example
This program displays the checksum error counter for com2.
#include
void main(void)
{
struct prot_status status;
status = get_protocol_status(com2);
printf("Checksum: %d\r\n",
status.checksum_errors);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
201
getSFMapping
Read Translation Table Mapping Control
Syntax
#include
unsigned getSFMapping(void);
Description
The getSFMapping and setSFMapping functions no longer perform any useful function but
are maintained as stubs for backward compatibility. Include the CNFG_StoreAndForward
module in the Register Assignment to assign a store and forward table to the I/O database.
Notes
The TeleBUS Protocols User Manual describes store and forward messaging mode.
See Also
addRegAssignment
TelePACE C Tools User and Reference Manual
May 9, 2007
202
getSFTranslation
Read Store and Forward Translation
Syntax
#include
struct SFTranslation getSFTranslation(unsigned index);
Description
The getSFTranslation function returns the entry at index in the store and forward address
translation table. If index is invalid, a disabled table entry is returned.
The function returns a SFTranslation structure. It is described in the Structures and Types
section.
Notes
The TeleBUS Protocols User Manual describes store and forward messaging mode.
See Also
setSFTranslation, clearSFTranslationTable, checkSFTranslationTable
Example
See the example for the setSFTranslation function.
TelePACE C Tools User and Reference Manual
May 9, 2007
203
get_status
Get Serial Port Status
Syntax
#include
struct pstatus *get_status(FILE *stream, struct pstatus *status);
Description
The get_status function returns serial port error counters, I/O lines status and I/O driver
buffer information for stream. If stream does not point to a valid serial port the function has
no effect. status must point to a valid serial port status structure, pstatus.
The get_status function copies the serial port status into the structure pointed to by status
and returns a pointer to that structure settings.
Refer to the Overview of Functions section for detailed information on serial ports.
See Also
clear_errors
Example
This program displays the framing and parity errors for com1.
#include
void main(void)
{
struct pstatus status;
get_status(com1, &status);
printf("Framing: %d\r\n", status.framing);
printf("Parity: %d\r\n", status.parity);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
204
getStatusBit
Read Bits in Controller Status Code
Syntax
#include
unsigned getStatusBit(unsigned bitMask);
Description
The getStatusBit function returns the values of the bits indicated by bitMask in the controller
status code.
See Also
setStatusBit, setStatus, clearStatusBit
TelePACE C Tools User and Reference Manual
May 9, 2007
205
getTaskInfo
Get Information on a Task
Syntax
#include
TASKINFO getTaskInfo(unsigned taskID);
Description
The getTaskInfo function returns information about the task specified by taskID. If taskID is
0 the function returns information about the current task.
Notes
If the specified task ID does not identify a valid task, all fields in the return data are set to
zero. The calling function should check the taskID field in the TASKINFO structure: if it is
zero the remaining information is not valid.
Refer to the Structures and Types section for a description of the fields in the TASKINFO
structure.
Example
The following program displays information about all valid tasks.
#include
#include
void main(void)
{
struct prot_settings settings;
TASKINFO taskStatus;
unsigned task;
char state[6][20];
char type[2][20];
/* Set up state strings */
strcpy(state[TS_READY], "Ready");
strcpy(state[TS_EXECUTING], "Executing");
strcpy(state[TS_WAIT_ENVELOPE], "Waiting for Envelope");
strcpy(state[TS_WAIT_EVENT], "Waiting for Event");
strcpy(state[TS_WAIT_MESSAGE], "Waiting for Message");
strcpy(state[TS_WAIT_RESOURCE], "Waiting for Resource");
/* Set up type strings */
strcpy(type[APPLICATION], "Application");
strcpy(type[SYSTEM], "System");
/* Disable the protocol on serial port 1 */
settings.type = NO_PROTOCOL;
settings.station = 1;
settings.priority = 3;
settings.SFMessaging = FALSE;
request_resource(IO_SYSTEM);
set_protocol(com1, &settings);
release_resource(IO_SYSTEM);
/* display information about all tasks */
for (task = 0; task <= RTOS_TASKS; task++)
{
taskStatus = getTaskInfo(task);
if (taskStatus.taskID != 0)
{
/* show information for valid task */
TelePACE C Tools User and Reference Manual
May 9, 2007
206
fprintf(com1, "\r\n\r\nInformation about task %d:\r\n", task);
fprintf(com1, "
Task ID: %d\r\n", taskStatus.taskID);
fprintf(com1, "
Priority: %d\r\n", taskStatus.priority);
fprintf(com1, "
Status:
%s\r\n", state[taskStatus.status]);
if (taskStatus.status == TS_WAIT_EVENT)
{
fprintf(com1, "
Event:
%d\r\n", taskStatus.requirement);
}
if (taskStatus.status == TS_WAIT_RESOURCE)
{
fprintf(com1, "
Resource: %d\r\n", taskStatus.requirement);
}
fprintf(com1, "
Error:
%d\r\n", taskStatus.error);
fprintf(com1, "
Type:
%s\r\n", type[taskStatus.type]);
}
}
while (TRUE)
{
/* Allow other tasks to execute */
release_processor();
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
207
getVersion
Get Firmware Version Information
Syntax
#include
VERSION getVersion(void);
Description
The getVersion function obtains firmware version information. It returns a VERSION
structure. Refer to the Structures and Types section for a description of the fields in the
VERSION structure.
Notes
The version information can be used to adapt a program to a specific type of controller or
version of firmware. For example, a bug work-around could be executed only if older
firmware is detected.
Example
This program displays the version information.
#include
void main(void)
{
struct prot_settings settings;
VERSION versionInfo;
/* Disable the protocol on serial port 1 */
settings.type =
NO_PROTOCOL;
settings.station =
1;
settings.priority =
3;
settings.SFMessaging = FALSE;
request_resource(IO_SYSTEM);
set_protocol(com1, &settings);
release_resource(IO_SYSTEM);
/* Display the ROM version information */
versionInfo = getVersion();
fprintf(com1, "\r\nFirmware Information\r\n");
fprintf(com1, "
BASE_TYPE_MASK);
fprintf(com1, "
fprintf(com1, "
fprintf(com1, "
Controller type:
%d\r\n", versionInfo.controller &
Firmware version: %d\r\n", versionInfo.version);
Creation date:
%s\r\n", versionInfo.date);
Copyright:
%s\r\n", versionInfo.copyright);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
208
getWakeSource
Gets Conditions for Waking from Sleep Mode
Syntax
#include
unsigned getWakeSource(void);
Description
The getWakeSource function returns a bit mask of the active wake up sources. Valid wake
up sources are listed below.
•
WS_REAL_TIME_CLOCK
•
WS_INTERRUPT_INPUT
•
WS_LED_POWER_SWITCH
•
WS_COUNTER_0_OVERFLOW
•
WS_COUNTER_1_OVERFLOW
•
WS_COUNTER_2_OVERFLOW
See Also
setWakeSource, sleep
Example
The following code fragment displays the enabled wake up sources.
unsigned enabled;
enabled = getWakeSource();
fputs("Enabled wake up sources:\r\n", com1);
if (enabled & WS_REAL_TIME_CLOCK)
fputs(" Real Time Clock\r\n", com1);
if (enabled & WS_INTERRUPT_INPUT)
fputs(" Interrupt Input\r\n", com1);
if (enabled & WS_LED_POWER_SWITCH)
fputs(" LED Power Switch\r\n", com1);
if (enabled & WS_COUNTER_0_OVERFLOW)
fputs(" Counter 0 Overflow\r\n", com1);
if (enabled & WS_COUNTER_1_OVERFLOW)
fputs(" Counter 1 Overflow\r\n", com1);
if (enabled & WS_COUNTER_2_OVERFLOW)
fputs(" Counter 2 Overflow\r\n", com1);
TelePACE C Tools User and Reference Manual
May 9, 2007
209
hartIO
Read and Write 5904 HART Interface Module
Syntax
#include
BOOLEAN hartIO(unsigned module);
Description
This function reads the specified 5904 interface module. It checks if a response has been
received and if a corresponding command has been sent. If so, the response to the
command is processed.
This function writes the specified 5904 interface module. It checks if there is a new
command to send. If so, this command is written to the 5904 interface.
The function has one parameter: the module number of the 5904 interface (0 to 3).
The function returns TRUE if the 5904 interface responded and FALSE if it did not or if the
module number is not valid.
Notes
This function is called automatically if the 5904 module is in the register assignment. Use
this function to implement communication with the 5904 if register assignment is not used.
See Also
hartSetConfiguration, hartGetConfiguration, hartCommand
TelePACE C Tools User and Reference Manual
May 9, 2007
210
hartIOFromDbase
Read and Write 5904 HART Interface Module with Settings from Database
Syntax
#include
BOOLEAN hartIOFromDbase(unsigned module, unsigned firstRegister);
Description
This function reads the specified 5904 interface module. It checks if a response has been
received and if a corresponding command has been sent. If so, the response to the
command is processed.
This function writes configuration and commands to the specified 5904 interface module.
Configuration data is read from the I/O database. It checks if there is a new command to
send. If so, this command is written to the 5904 interface.
The function has two parameters: the module number of the 5904 interface (0 to 3); and the
address of the first register of a group of four containing the HART interface configuration.
The function returns TRUE if the 5904 interface responded and FALSE if it did not or if the
module number is not valid or there is an error in the settings.
See Also
hartIO, hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
211
hartCommand
Send Command using HART Interface Module
Syntax
#include
BOOLEAN hartCommand(
unsigned module,
HART_DEVICE * const device,
HART_COMMAND * const command,
void (* processResponse)( unsigned,
HART_RESPONSE)
);
Description
This function sends a command to a HART slave device using a HART interface module.
This function can be used to implement HART commands not provided by the Network
Layer API.
The function has four parameters. The first is the module number of the 5904 interface (0 to
3). The second is the device to which the command is to be sent.
The third parameter is a structure describing the command to send. This contains the
command number, and the data field of the HART message. See the HART protocol
documentation for your device for details.
The fourth parameter is a pointer to a function that will process the response. This function
is called when a response to the command is received by the HART interface. The function
is defined as follows:
void function_name(HART_RESPONSE response)
The single parameter is a structure containing the response code and the data field from the
message.
The function returns TRUE if the 5904 interface responded and FALSE if it did not or if the
module number is not valid or there is an error in the command.
Notes
The function returns immediately after the command is sent. The calling program must wait
for the response to be received. Use the hartStatus command to read the status of the
command.
The number of attempts and the number of preambles sent are set with the
hartSetConfiguration command.
A program must initialize the link before executing any other commands.
The function determines if long or short addressing is to be used by the command number.
Long addressing is used for all commands except commands 0 and 11.
The functions hartCommand0, hartCommand1, etc. are used to send commands provided
by the Network Layer.
See Also
hartStatus, hartSetConfiguration, hartCommand0, hartCommand1
TelePACE C Tools User and Reference Manual
May 9, 2007
212
TelePACE C Tools User and Reference Manual
May 9, 2007
213
hartCommand0
Read Unique Identifier
Syntax
#include
BOOLEAN hartCommand0(unsigned module, unsigned address, HART_DEVICE * const
device);
Description
This function reads the unique identifier of a HART device using command 0 with a shortform address. This is a link initialization function.
The function has three parameters: the module-number of the 5904 module (0 to 3); the
short-form address of the HART device (0 to 15); and a pointer to a HART_DEVICE
structure. The information read by command 0 is written into the HART_DEVICE structure
when the response is received by the 5904 interface.
The function returns TRUE if the command was sent. The function returns FALSE if the
module number is invalid, or if the device address is invalid.
Notes
The function returns immediately after the command is sent. The calling program must wait
for the response to be received. Use the hartStatus command to read the status of the
command.
The number of attempts and the number of preambles sent are set with the
hartSetConfiguration command.
A program must initialize the link before executing any other commands.
See Also
hartCommand11, hartStatus, hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
214
hartCommand1
Read Primary Variable
Syntax
#include
BOOLEAN hartCommand1(unsigned module, HART_DEVICE * const device,
HART_VARIABLE * primaryVariable);
Description
This function reads the primary variable of a HART device using command 1.
The function has three parameters: the module-number of the 5904 module (0 to 3); the
device to be read; and a pointer to the primary variable. The variable pointed to by
primaryVariable is updated when the response is received by the 5904 interface.
The primaryVariable must be a static modular or global variable. A primaryVariable should
be declared for each HART I/O module in use. A local variable or dynamically allocated
variable may not be used because a late command response received after the variable is
freed will write data over the freed variable space.
The function returns TRUE if the command was sent. The function returns FALSE if the
module number is invalid.
Notes
The HART_DEVICE structure must be initialized using hartCommand0 or hartCommand11.
The function returns immediately after the command is sent. The calling program must wait
for the response to be received. Use the hartStatus command to read the status of the
command.
The number of attempts and the number of preambles sent are set with the
hartSetConfiguration command.
The code field of the HART_VARIABLE structure not changed. Command 1 does not return
a variable code.
See Also
hartCommand2, hartStatus, hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
215
hartCommand2
Read Primary Variable Current and Percent of Range
Syntax
#include
BOOLEAN hartCommand2(unsigned module, HART_DEVICE * const device,
HART_VARIABLE * pvCurrent, HART_VARIABLE * pvPercent);
Description
This function reads the primary variable (PV), as current and percent of range, of a HART
device using command 2.
The function has four parameters: the module-number of the 5904 module (0 to 3); the
device to be read; a pointer to the PV current variable; and a pointer to the PV percent
variable. The pvCurrent and pvPercent variables are updated when the response is received
by the 5904 interface.
The pvCurrent and pvPercent variables must be static modular or global variables. A
pvCurrent and pvPercent variable should be declared for each HART I/O module in use. A
local variable or dynamically allocated variable may not be used because a late command
response received after the variable is freed will write data over the freed variable space.
The function returns TRUE if the command was sent. The function returns FALSE if the
module number is invalid.
Notes
The HART_DEVICE structure must be initialized using hartCommand0 or hartCommand11.
The function returns immediately after the command is sent. The calling program must wait
for the response to be received. Use the hartStatus command to read the status of the
command.
The number of attempts and the number of preambles sent are set with the
hartSetConfiguration command.
The code field of both HART_VARIABLE structures is not changed. The response from the
HART device to command 2 does not include variable codes.
The units field of the pvCurrent variable is set to 39 (units = mA). The units field of the
pvPercent variable is set to 57 (units = percent). The response from the HART device to
command 2 does not include units.
See Also
hartCommand1, hartStatus, hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
216
hartCommand3
Read Primary Variable Current and Dynamic Variables
Syntax
#include
BOOLEAN hartCommand3(unsigned module, HART_DEVICE * const device,
HART_VARIABLE * variables);
Description
This function reads dynamic variables and primary variable current from a HART device
using command 3.
The function has three parameters: the module number of the 5904 module (0 to 3); the
device to be read; and a pointer to an array of five HART_VARIABLE structures.
The variables array must be static modular or global variables. An array of variables should
be declared for each HART I/O module in use. A local variable or dynamically allocated
variable may not be used because a late command response received after the variable is
freed will write data over the freed variable space.
The variables array is updated when the response is received by the 5904 interface as
follows.
Variable
variables[0]
variables[1]
variables[2]
variables[3]
variables[4]
Contains
primary variable current
primary variable
secondary variable
tertiary variable
fourth variable
The function returns TRUE if the command was sent. The function returns FALSE if the
module number is invalid.
Notes
The HART_DEVICE structure must be initialized using hartCommand0 or hartCommand11.
The function returns immediately after the command is sent. The calling program must wait
for the response to be received. Use the hartStatus command to read the status of the
command.
The number of attempts and the number of preambles sent are set with the
hartSetConfiguration command.
Not all devices return primary, secondary, tertiary and fourth variables. If the device does not
support a variable, zero is written into the value and units code for that variable.
The code field of both HART_VARIABLE structures is not changed. The response from the
HART device to command 3 does not include variable codes.
The units field of variable[0] is set to 39 (units = mA). The response from the HART device to
command 3 does not include units.
See Also
hartCommand33, hartStatus, hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
217
hartCommand11
Read Unique Identifier Associated with Tag
Syntax
#include
BOOLEAN hartCommand11(unsigned module, char * deviceTag, HART_DEVICE *
device);
Description
This function reads the unique identifier of a HART device using command 11. This is a link
initialization function.
The function has three parameters: the module number of the 5904 module (0 to 3); a
pointer to a null terminated string containing the tag of the HART device; and a pointer to a
HART_DEVICE structure. The information read by command 11 is written into the
HART_DEVICE structure when the response is received by the 5904 interface.
The function returns TRUE if the command was sent. The function returns FALSE if the
module number is invalid.
Notes
The function returns immediately after the command is sent. The calling program must wait
for the response to be received. Use the hartStatus command to read the status of the
command.
The number of attempts and the number of preambles sent are set with the
hartSetConfiguration command.
A program must initialize the link before executing any other commands.
See Also
hartCommand0, hartStatus, hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
218
hartCommand33
Read Transmitter Variables
Syntax
#include
BOOLEAN hartCommand33(unsigned module, HART_DEVICE * const device, unsigned
variableCode[4], HART_VARIABLE * variables);
Description
This function reads selected variables from a HART device using command 33.
The function has four parameters: the module number of the 5904 module (0 to 3); the
device to be read; an array of codes; and a pointer to an array of four HART_VARIABLE
structures.
The variables array must be static modular or global variables. An array of variables should
be declared for each HART I/O module in use. A local variable or dynamically allocated
variable may not be used because a late command response received after the variable is
freed will write data over the freed variable space.
The variableCode array specifies which variables are to be read from the transmitter.
Consult the documentation for the transmitter for valid values.
The variables array is updated when the response is received by the 5904 interface as
follows.
Variable
variables[0]
variables[1]
variables[2]
variables[3]
Contains
transmitter variable, code and units specified by variableCode[0]
transmitter variable, code and units specified by variableCode[1]
transmitter variable, code and units specified by variableCode[2]
transmitter variable, code and units specified by variableCode[3]
The function returns TRUE if the command was sent. The function returns FALSE if the
module number is invalid.
Notes
The HART_DEVICE structure must be initialized using hartCommand0 or hartCommand11.
The pointer variables must point to an array with at least four elements.
The function returns immediately after the command is sent. The calling program must wait
for the response to be received. Use the hartStatus command to read the status of the
command.
The number of attempts and the number of preambles sent are set with the
hartSetConfiguration command.
The function always requests four variables and expects four variables in the response.
See Also
hartCommand3, hartStatus, hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
219
hartStatus
Return Status of Last HART Command Sent
Syntax
#include
BOOLEAN hartStatus(unsigned module, HART_RESULT * status, unsigned * code);
Description
This function returns the status of the last HART command sent by a 5904 module (0 to 3).
Use this function to determine if a response has been received to a command sent.
The function has three parameters: the module number of the 5904 module; a pointer to the
status variable; and a pointer to the additional status code variable. The status and code
variables are updated with the following information.
Result
HART interface module is
not communicating
Command ready to be sent
Command sent to device
Response received
Status
HR_NoModuleResponse
code
not used
HR_CommandPending
HR_CommandSent
HR_Response
not used
current attempt number
response code from HART
device (see Notes)
0=no response from HART
device.
Other = error response code
from HART device (see
Notes)
not used
No valid response received
after all attempts made
HR_NoResponse
HART interface module is
not ready to transmit
HR_WaitTransmit
The function returns TRUE if the status was read. The function returns FALSE if the module
number is invalid.
Notes
The response code from the HART device contains communication error and status
information. The information varies by device, but there are some common values.
•
If bit 7 of the high byte is set, the high byte contains a communication error summary.
This field is bit-mapped. The table shows the meaning of each bit as defined by the
HART protocol specifications. Consult the documentation for the HART device for more
information.
Bit
6
5
4
3
2
1
0
Description
vertical parity error
overrun error
framing error
longitudinal parity error
reserved – always 0
buffer overflow
Undefined
TelePACE C Tools User and Reference Manual
May 9, 2007
220
•
If bit 7 of the high byte is cleared, the high byte contains a command response
summary. The table shows common values. Other values may be defined for specific
commands. Consult the documentation for the HART device.
Code
32
64
•
Description
Busy – the device is performing a function
that cannot be interrupted by this command
Command not Implemented – the command
is not defined for this device.
The low byte contains the field device status. This field is bit-mapped. The table shows
the meaning of each bit as defined by the HART protocol specifications. Consult the
documentation for the HART device for more information.
Bit
7
6
5
4
3
2
1
0
Description
field device malfunction
configuration changed
cold start
more status available (use command 48 to
read)
primary variable analog output fixed
primary variable analog output saturated
non-primary variable out of limits
primary variable out of limits
See Also
hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
221
hartGetConfiguration
Read HART Module Settings
Syntax
#include
BOOLEAN hartGetConfiguration(unsigned module, HART_SETTINGS * settings);
Description
This function returns the configuration settings of a 5904 module.
The function has two parameters: the module number of the 5904 module (0 to 3); and a
pointer to the settings structure.
The function returns TRUE if the settings were read. The function returns FALSE if the
module number is invalid.
See Also
hartSetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
222
hartSetConfiguration
Write HART Module Settings
Syntax
#include
BOOLEAN hartSetConfiguration(unsigned module, HART_SETTINGS settings);
Description
This function writes configuration settings to a 5904 module.
The function has two parameters: the module number of the 5904 module (0 to 3); and a
settings structure.
The function returns TRUE if the settings were written. The function returns FALSE if the
module number or the settings are invalid.
Notes
The configuration settings are stored in the EEPROM_RUN section of the EEPROM. The
user-defined settings are used when the controller is reset in the RUN mode. Default
settings are used when the controller is reset in the SERVICE or COLD BOOT modes.
If a CNFG 5904 HART Interface module is in the register assignment, forced registers from
it take precedence over the settings supplied here.
See Also
hartGetConfiguration
TelePACE C Tools User and Reference Manual
May 9, 2007
223
hartPackString
Convert String to HART Packed String
Syntax
#include
void hartPackString(char * pPackedString, const char * pString, unsigned
sizePackedString);
Description
This function stores an ASCII string into a HART packed ASCII string.
The function has three parameters: a pointer to a packed array; a pointer to an unpacked
array; and the size of the packed array. The packed array must be a multiple of three in size.
The unpacked array must be a multiple of four in size. It should be padded with spaces at
the end if the string is not long enough.
The function has no return value.
See Also
hartUnpackString
TelePACE C Tools User and Reference Manual
May 9, 2007
224
hartUnpackString
Convert HART Packed String to String
Syntax
#include
void hartUnpackString(char * pString, const char * pPackedString, unsigned
sizePackedString);
Description
This function unpacks a HART packed ASCII string into a normal ASCII string.
The function has three parameters: a pointer to an unpacked array; a pointer to a packed
array; and the size of the packed array. The packed array must be a multiple of three in size.
The unpacked array must be a multiple of four in size.
The function has no return value.
See Also
hartPackString
TelePACE C Tools User and Reference Manual
May 9, 2007
225
install_handler
Install Serial Port Handler
Syntax
#include
void install_handler(FILE *stream, void *function(unsigned, unsigned));
Description
The install_handler function installs a serial port character handler function. The serial port
driver calls this function each time it receives a character. If stream does not point to a valid
serial port the function has no effect.
function specifies the handler function, which takes two arguments. The first argument is the
received character. The second argument is an error flag. A non-zero value indicates an
error. If function is NULL, the default handler for the port is installed. The default handler
does nothing.
Notes
The install_handler function can be used to write custom communication protocols.
The handler is called at the completion of the receiver interrupt handler. RTOS calls (see
functions listed in the section Real Time Operating System Functions at the start of this
chapter) may not be made within the interrupt handler, with one exception. The
interrupt_signal_event RTOS call can be used to signal events.
To optimize performance, minimize the length of messages on com3 and com4. Examples
of recommended uses for com3 and com4 are for local operator display terminals, and for
programming and diagnostics using the TelePACE program.
Example
#include
#define CHAR_RECEIVED 11
/* -------------------------------------------signal
This routine signals an event when a character
is received on com1. If there is an error, the
character is ignored.
-------------------------------------------- */
void signal(unsigned character, unsigned error)
{
if (error == 0)
interrupt_signal_event( CHAR_RECEIVED );
character;
}
/* -------------------------------------------main
This program displays all characters received
on com1 using an installed handler to signal
TelePACE C Tools User and Reference Manual
May 9, 2007
226
the reception of a character.
-------------------------------------------- */
void main(void)
{
struct prot_settings protocolSettings;
int character;
/* Disable protocol */
get_protocol(com1, &protocolSettings);
protocolSettings.type = NO_PROTOCOL;
request_resource(IO_SYSTEM);
set_protocol(com1, &protocolSettings);
release_resource(IO_SYSTEM);
/* Enable character handler */
install_handler(com1, signal);
/* Print each character as it is recevied */
while (TRUE)
{
wait_event(CHAR_RECEIVED);
character = fgetc(com1);
fputs("character: ", com1);
fputc(character, com1);
fputs("\r\n", com1);
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
227
installClockHandler
Install Handler for Real Time Clock
Syntax
#include
void installClockHandler(void (*function)(void));
Description
The installClockHandler function installs a real time clock alarm handler function. The real
time clock alarm function calls this function each time a real time clock alarm occurs.
function specifies the handler function. If function is NULL, the handler is disabled.
Notes
RTOS calls (see functions listed in the section Real Time Operating System Functions at the
start of this chapter) may not be made within the interrupt handler, with one exception. The
interrupt_signal_event RTOS call can be used to signal events.
See Also
setClockAlarm
Example
/* -------------------------------------------This program demonstrates how to call a
function at a specific time of day.
-------------------------------------------- */
#include
#define
ALARM_EVENT
20
/* -------------------------------------------This function signals an event when the alarm
occurs.
-------------------------------------------- */
void alarmHandler(void)
{
interrupt_signal_event( ALARM_EVENT );
}
/* -------------------------------------------This task processes alarms signaled by the
clock handler
-------------------------------------------- */
void processAlarms(void)
{
while(TRUE)
{
wait_event(ALARM_EVENT);
/* Reset the alarm for the next day */
request_resource(IO_SYSTEM);
resetClockAlarm();
release_resource(IO_SYSTEM);
TelePACE C Tools User and Reference Manual
May 9, 2007
228
fprintf(com1, "It’s quitting time!\r\n");
}
}
void main(void)
{
struct prot_settings settings;
ALARM_SETTING alarm;
/* Disable the protocol on serial port 1 */
settings.type = NO_PROTOCOL;
settings.station = 1;
settings.priority = 3;
settings.SFMessaging = FALSE;
request_resource(IO_SYSTEM);
set_protocol(com1, &settings);
release_resource(IO_SYSTEM);
/* Install clock handler function */
installClockHandler(alarmHandler);
/* Create task for processing alarm events */
create_task(processAlarms, 3, APPLICATION, 4);
/* Set real time clock alarm */
alarm.type
= AT_ABSOLUTE;
alarm.hour
= 16;
alarm.minute = 0;
alarm.second = 0;
request_resource(IO_SYSTEM);
setClockAlarm(alarm);
release_resource(IO_SYSTEM);
while(TRUE)
{
/* body of main task loop */
/* other processing code */
/* Allow other tasks to execute */
release_processor();
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
229
installExitHandler
Install Handler Called when Task Ends
Syntax
#include
unsigned installExitHandler(unsigned taskID, void (*function)(void));
Description
The installExitHandler function defines a function that is called when the task, specified by
taskID, is ended. function specifies the handler function. If function is NULL, the handler is
disabled.
Notes
The exit handler function will be called when:
•
the task is ended by the end_task function
•
the end_application function is executed and the function is an APPLICATION type
function
•
the program is stopped from the TelePACE program and the task is an APPLICATION
type function
•
the C program is erased by the TelePACE program.
The exit handler function is not called if power to the controller is removed. In this case all
execution stops when power fails. The application program starts from the beginning when
power is reapplied.
Do not call any RTOS functions from the exit handler.
Example
See the example for startTimedEvent.
TelePACE C Tools User and Reference Manual
May 9, 2007
230
installModbusHandler
Install User Defined Modbus Handler
Syntax
#include
void installModbusHandler(
unsigned (* handler)(unsigned char *, unsigned,
unsigned char *, unsigned *)
);
Description
The installModbusHandler function allows user-defined extensions to standard Modbus
protocol. This function specifies a function to be called when a Modbus message is received
for the station, but is not understood by the standard Modbus protocol. The installed handler
function is called only if the message is addressed to the station, and the message
checksum is correct.
The function has one parameter: a pointer to a function to handle the messages. See the
section Handler Function for a full description of the function and it’s parameters. If the
pointer is NULL, no function is called for non-standard messages.
The function has no return value.
Notes
This function is used to create a user-defined extension to the standard Modbus protocol.
Call this function with the NULL pointer to disable processing of non-standard Modbus
messages. This must be done when the application program is ended with an exit handler.
Use the installExitHandler function to install the exit handler.
If the Modbus handler is not disabled within an exit handler, it will remain installed and
continue to operate until the controller power is cycled. Changing the protocol type or
Erasing the C Program from TelePACE Initialize dialog will not remove the Modbus handler.
If the handler is located in a RAM-based application and left enabled while a different C
application is downloaded, the original handler will be corrupted and the system will likely
crash.
See Also
installExitHandler, Handler Function
TelePACE C Tools User and Reference Manual
May 9, 2007
231
Handler Function
User Specified Handler Function
The handler function is a user-specified function that handles processing of Modbus
messages not recognized by the protocol. The function can have any name; handler is used
in the description below.
Syntax
#include
unsigned handler(
unsigned char * message,
unsigned messageLength,
unsigned char * response,
unsigned * responseLength
);
Description
This function handler is a user-defined handler for processing Modbus messages. The
function is called for each Modbus message with a function code that is not recognized by
the standard Modbus protocol.
The handler function should process the message string and create a response string. IF the
message is not understood, one of the error codes should be returned.
The function has four parameters.
•
The message parameter is a pointer to the first character of the received message. The
first character of the message is the function code. The format of the data after the
function code is defined by the function code.
•
The messageLength parameter is the number of characters in the message.
•
The response parameter is a pointer to the first character of a buffer to hold the
response. The function should write the response into this buffer. The buffer is 253
characters long. The first character of the buffer is the function code of the message.
The format of the data after the function code is defined by the function code.
•
The responseLength parameter is a pointer to the length of the response. The function
should set the length of the response using this pointer. The length is the number of
characters placed into the response buffer.
The function must return one of four values. The first causes a normal response to be sent.
The others cause an exception response to be sent.
•
NORMAL indicates the response and responseLength have been set to valid values.
The Modbus protocol will add the station address and checksum to this string and
transmit the reply to the master station.
•
ILLEGAL_FUNCTION indicates the function code in the message was not understood.
The handler function must return this value for all function codes it does not process.
The Modbus protocol will return an Illegal Function exception response.
•
ILLEGAL_DATA_ADDRESS indicates the function code in the message was
understood, but that the command referenced an address that is not valid. The Modbus
protocol will return an Illegal Data Address exception response.
TelePACE C Tools User and Reference Manual
May 9, 2007
232
•
ILLEGAL_DATA_VALUE indicates the function code in the message was understood,
but that the command included data that is not valid. The Modbus protocol will return an
Illegal Data Address exception response.
Function Codes Used
The following function codes are currently used by the TeleBUS Modbus-compatible
protocol. All other function codes are available for use. For maximum compatibility with other
Modbus and Modbus-compatible devices it is recommended that codes in the user-defined
function code range be used first.
Code
1
2
3
4
5
6
7
15
16
17
65
66
67
68
69
70
Type
Modbus standard
Modbus standard
Modbus standard
Modbus standard
Modbus standard
Modbus standard
Modbus standard
Modbus standard
Modbus standard
Modbus standard
TeleBUS extension
TeleBUS extension
TeleBUS extension
TeleBUS extension
TeleBUS extension
TeleBUS extension
Description
Read coil registers from I/O database
Read status registers from I/O database
Read holding registers from I/O database
Read input registers from I/O database
Write a single coil register
Write a single holding register
Read exception status
Write multiple coil registers
Write multiple holding registers
Report slave identification string
Used by TelePACE
Used by TelePACE
Used by TelePACE
Used by TelePACE
Used by TelePACE
Used by TelePACE
Notes
One handler function is used for all serial ports. Only one port will be active at any time.
Therefore, the function does not have to be re-entrant.
The handler function is called from the Modbus protocol task. This task may pre-empt the
execution of another task. If there are shared resources, the handler function must request
and release the appropriate resources to ensure proper operation.
The station address is not included in the message or response string. It will be added to the
response string before sending the reply.
The checksum is not included in the message or the response string. It will be added to the
response string before sending the reply.
The maximum size of the response string is 253 bytes. If a longer response length is
returned, the Modbus protocol will report an ILLEGAL_DATA_VALUE exception. The
response will not be returned.
See Also
installModbusHandler
Example
/* ----------------------------------------------handler.c
TelePACE C Tools User and Reference Manual
May 9, 2007
233
This is a sample program for the InstallModbusHandler function. This
sample
program uses function code 71 to demonstrate a
simple method
for using the
installModbusHandler function.
When the handler is installed Modbus ASCII messages using function code
71 that are received on com2 of the controller will
be processed as shown in the program text.
To turn on digital output 00001:
From a terminal send the ASCII command :014701B7
Where;
01 is the station address
47 is the function code in hex
01 is the command for the function code
B7 is the message checksum
To turn off digital output 00001:
From a terminal send the ASCII command :014700B8
Where;
01 is the station address
47 is the function code in hex
00 is the command for the function code
B8 is the message checksum
-------------------------------------------- */
#include
static unsigned
unsigned
unsigned
unsigned
unsigned
)
{
unsigned
unsigned
myModbusHandler(
char * message,
messageLength,
char * response,
* responseLength
char * pMessage;
char * pResponse;
pMessage = message;
if (*pMessage == 71)
{
/* Action for command data */
pMessage++;
if (*pMessage == 0)
{
request_resource(IO_SYSTEM);
setdbase(MODBUS, 1, 0);
release_resource(IO_SYSTEM);
pResponse = response;
*pResponse
pResponse++;
*pResponse
pResponse++;
*pResponse
pResponse++;
*pResponse
pResponse++;
= 71;
= 'O';
= 'F';
= 'F';
*responseLength = 4;
return NORMAL;
}
if (*pMessage == 1)
{
TelePACE C Tools User and Reference Manual
May 9, 2007
234
request_resource(IO_SYSTEM);
setdbase(MODBUS, 1, 1);
release_resource(IO_SYSTEM);
pResponse = response;
*pResponse
= 71;
pResponse++;
*pResponse
= 'O';
pResponse++;
*pResponse
= 'N';
pResponse++;
*responseLength = 3;
return NORMAL;
}
}
}
static void shutdown(void)
{
installModbusHandler(NULL);
}
/* ----------------------------------------------main
This routine is the modbus slave application.
Serial port com2 is configured for Modbus ASCII
Register Assignment is configured.
The modbus handler is installed.
The exit handler is installed.
-------------------------------------------- */
void main(void)
{
TASKINFO taskStatus;
protocol.
struct pconfig portSettings;
struct prot_settings protSettings;
portSettings.baud
= BAUD9600;
portSettings.duplex
= FULL;
portSettings.parity
= NONE;
portSettings.data_bits = DATA7;
portSettings.stop_bits = STOP1;
portSettings.flow_rx
= DISABLE;
portSettings.flow_tx
= DISABLE;
portSettings.type
= RS232;
portSettings.timeout
= 600;
set_port(com2, &portSettings);
get_protocol(com2, &protSettings);
protSettings.station
= 1;
protSettings.type
= MODBUS_ASCII;
set_protocol(com2, &protSettings);
/* Configure Register Assignment */
clearRegAssignment();
addRegAssignment(DIN_generic8, 0, 10017, 0, 0, 0);
addRegAssignment(SCADAPack_lowerIO,0, 1, 10001, 30001, 0);
addRegAssignment(DIAG_protocolStatus,1,31000, 0, 0, 0);
/* Install Modbus Handler */
request_resource(IO_SYSTEM);
installModbusHandler(myModbusHandler);
release_resource(IO_SYSTEM);
TelePACE C Tools User and Reference Manual
May 9, 2007
235
/* Install Exit Handler */
taskStatus = getTaskInfo(0);
installExitHandler(taskStatus.taskID, shutdown);
while(TRUE)
{
release_processor();
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
236
installRTCHandler
Install User Defined Real-Time-Clock Handler
Syntax
#include
void installRTCHandler(
void (* rtchandler)(TIME *now,
TIME *new)
);
Description
The installRTCHandler function allows an application program to override Modbus protocol
and DNP protocol commands to set the real time clock. This function specifies a function to
be called when a Modbus or DNP message is received for the station. The installed handler
function is called only if the message is intended to set the real time clock.
The function has one parameter: a pointer to a function to handle the messages. See the
section RTCHandler Function for a full description of the function and its parameters. If the
pointer is NULL, no function is called for set the real time clock commands, and the default
method is used set the real time clock.
The function has no return value.
Notes
Call this function with the NULL pointer to disable processing of Set Real Time Clock
messages. This must be done when the application program is ended with an exit handler.
Use the installExitHandler function to install the exit handler.
If the RTC handler is not disabled within an exit handler, it will remain installed and continue
to operate until the controller power is cycled. Changing the protocol type or Erasing the C
Program from the TelePACE Initialize dialog will not remove the handler. If the handler is
located in a RAM-based application and left enabled while a different C application is
downloaded, the original handler will be corrupted and the system will likely crash.
See Also
RTCHandler Function, installExitHandler
TelePACE C Tools User and Reference Manual
May 9, 2007
237
RTCHandler Function
User Specified Real Time Clock Handler Function
The handler function is a user-specified function that handles processing of Modbus
messages or DNP messages for setting the real time clock. The function can have any
name; rtchandler is used in the description below.
Syntax
#include
void rtchandler(
TIME *now,
TIME *new
);
Description
This function rtchandler is a user-defined handler for processing Modbus messages or DNP
messages. The function is called only for messages that set the real time clock.
The rtchandler function should set the real time clock to the requested time. If there is a
delay before this can be done, the time when the message was received is provided so that
a correction to the requested time can be made.
The function has two parameters.
•
The now parameter is a pointer to the structure containing the time when the message
was received.
•
The new parameter is a pointer to the structure containing the requested time.
The function does not return a value.
Notes
The IO_SYSTEM resource has already been requested before calling this function. If this
function calls other functions that require the IO_SYSTEM resource (e.g. setclock), there is
no need to request or release the resource.
This function must not request or release the IO_SYSTEM resource.
See Also
installRTCHandler
TelePACE C Tools User and Reference Manual
May 9, 2007
238
interruptCounter
Read Interrupt Input Counter
Syntax
#include
unsigned long interruptCounter(unsigned clear);
Description
The interruptCounter routine reads the interrupt input as a counter. If clear is TRUE the
counter is cleared after reading; otherwise if it is FALSE the counter continues to
accumulate.
Notes
The interrupt input is located on the 5203 or 5204 controller board. Refer to the System
Hardware Manual for more information on the hardware.
The counter increments on the rising edge of the input signal.
The maximum input frequency that can be counted by the interrupt input is 200 Hz.
See Also
interruptInput, readCounter
TelePACE C Tools User and Reference Manual
May 9, 2007
239
interruptInput
Read State of Interrupt Digital Input
Syntax
#include
unsigned interruptInput(void);
Description
The interruptInput function reads the status of the interrupt input point on the controller. It
returns TRUE if the input is energized and FALSE if it is not.
Notes
The interrupt input can be used as wake up source for the controller or as an additional a
digital input. Refer to the System Hardware Manual for wiring details.
See Also
installRTCHandler
Install User Defined Real-Time-Clock Handler
Syntax
#include
void installRTCHandler(
void (* rtchandler)(TIME *now,
TIME *new)
);
Description
The installRTCHandler function allows an application program to override Modbus protocol
and DNP protocol commands to set the real time clock. This function specifies a function to
be called when a Modbus or DNP message is received for the station. The installed handler
function is called only if the message is intended to set the real time clock.
The function has one parameter: a pointer to a function to handle the messages. See the
section RTCHandler Function for a full description of the function and its parameters. If the
pointer is NULL, no function is called for set the real time clock commands, and the default
method is used set the real time clock.
The function has no return value.
Notes
Call this function with the NULL pointer to disable processing of Set Real Time Clock
messages. This must be done when the application program is ended with an exit handler.
Use the installExitHandler function to install the exit handler.
If the RTC handler is not disabled within an exit handler, it will remain installed and continue
to operate until the controller power is cycled. Changing the protocol type or Erasing the C
Program from the TelePACE Initialize dialog will not remove the handler. If the handler is
located in a RAM-based application and left enabled while a different C application is
downloaded, the original handler will be corrupted and the system will likely crash.
TelePACE C Tools User and Reference Manual
May 9, 2007
240
See Also
RTCHandler Function, installExitHandler
TelePACE C Tools User and Reference Manual
May 9, 2007
241
RTCHandler Function
User Specified Real Time Clock Handler Function
The handler function is a user-specified function that handles processing of Modbus
messages or DNP messages for setting the real time clock. The function can have any
name; rtchandler is used in the description below.
Syntax
#include
void rtchandler(
TIME *now,
TIME *new
);
Description
This function rtchandler is a user-defined handler for processing Modbus messages or DNP
messages. The function is called only for messages that set the real time clock.
The rtchandler function should set the real time clock to the requested time. If there is a
delay before this can be done, the time when the message was received is provided so that
a correction to the requested time can be made.
The function has two parameters.
•
The now parameter is a pointer to the structure containing the time when the message
was received.
•
The new parameter is a pointer to the structure containing the requested time.
The function does not return a value.
Notes
The IO_SYSTEM resource has already been requested before calling this function. If this
function calls other functions that require the IO_SYSTEM resource (e.g. setclock), there is
no need to request or release the resource.
This function must not request or release the IO_SYSTEM resource.
See Also
installRTCHandler
interruptCounter
TelePACE C Tools User and Reference Manual
May 9, 2007
242
interrupt_signal_event
Signal Event in Interrupt Handler
Syntax
#include
void interrupt_signal_event(unsigned event_number);
Description
The interrupt_signal_event function is used in an interrupt handler to signal events. The
function signals that the event_number event has occurred.
If there are tasks waiting for the event, the highest priority task is made ready to execute.
Otherwise the event flag is incremented. Up to 255 occurrences of an event will be
recorded. The current task is blocked of there is a higher priority task waiting for the event.
Notes
Refer to the Real Time Operating System section for more information on events.
This function must only be used within an interrupt handler.
Valid events are numbered 0 to RTOS_EVENTS - 1. Any events defined in ctools.h. are not
valid events for use in an application program.
See Also
signal_event, startTimedEvent, installClockHandler
TelePACE C Tools User and Reference Manual
May 9, 2007
243
interval
Set Timer Tick Interval
Syntax
#include
void interval(unsigned timer, unsigned value);
Description
The interval function sets the tick interval for timer to value. Tick intervals are measured in
multiples of 0.1 second.
If the timer number is invalid, the task's error code is set to TIMER_BADTIMER.
Notes
The default timer tick interval is 1/10 second.
See Also
settimer, read_timer_info, check_error
Example
Set timer 5 to count 12 seconds using 1.0 s ticks.
interval(5, 10);
settimer(5, 12);
/* 1.0 s ticks */
/* time = 12 seconds */
Set timer 5 to count 12 seconds using 0.1 s ticks.
interval(5, 1);
settimer(5, 120);
/* 0.1 s ticks */
/* time = 12 seconds */
TelePACE C Tools User and Reference Manual
May 9, 2007
244
ioBusReadByte
Read One Byte from I2C Slave Device
Syntax
#include
unsigned char ioBusReadByte(void);
Description
The ioBusReadByte function returns one byte read from an I2C slave device. The byte is
acknowledged by the master receiver. This function can be used multiple times in sequence
to read data from a slave device. The last byte read from the slave must be read with the
ioBusReadLastByte function.
If only one byte is to be read from a device, the ioBusReadLastByte function must be used
instead of this function.
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStart, ioBusStop, ioBusReadLastByte, ioBusReadMessage, ioBusSelectForRead
ioBusSelectForWrite, ioBusWriteByte, ioBusWriteMessage
Example
#include
void main(void)
{
unsigned char data[3];
unsigned char ioBusAddress = 114;
request_resource(IO_SYSTEM);
ioBusStart();
if (ioBusSelectForRead(ioBusAddress))
{
data[0] = ioBusReadByte();
data[1] = ioBusReadByte();
/* reading the last byte terminates read */
data[2] = ioBusReadLastByte();
}
ioBusStop();
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
245
ioBusReadLastByte
Read Last Byte from I2C Slave Device
Syntax
#include
unsigned char ioBusReadLastByte(void);
Description
The ioBusReadLastByte function returns one byte read from an I2C slave device and
terminates reading from the slave. The byte is not acknowledged by the master receiver.
This signals to the slave device that the read is complete. This function must be used once
at the end of a read.
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStart, ioBusStop, ioBusReadByte, ioBusReadMessage, ioBusSelectForRead
ioBusSelectForWrite, ioBusWriteByte, ioBusWriteMessage
Example
See example for ioBusReadByte.
TelePACE C Tools User and Reference Manual
May 9, 2007
246
ioBusReadMessage
Read Message from I2C Slave Device
Syntax
#include
READSTATUS ioBusReadMessage(unsigned address, unsigned numberBytes, unsigned
char *message);
Description
The ioBusReadMessage function reads a specified number of bytes from an I2C slave
device.
The function issues a START condition, selects the device for reading, reads the specified
number of bytes, and issues a STOP condition. It detects if the device cannot be selected
and, if so, aborts the read.
The function has three parameters: the address of the device; the number of bytes to read,
numberBytes; and a pointer to a buffer, message, capable of holding the data read.
The function returns the status of the read:
Value
RS_success
RS_selectFailed
Description
read was successful
slave device could not be selected
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusWriteMessage, ioBusStart, ioBusStop, ioBusReadByte ioBusReadLastByte,
ioBusSelectForRead ioBusSelectForWrite, ioBusWriteByte, ioBusWriteMessage
Example
#include
void main(void)
{
unsigned char message[10];
unsigned char ioBusAddress = 114;
READSTATUS
status;
request_resource(IO_SYSTEM);
/* Read a 10 byte message from I2C device */
status = ioBusReadMessage(ioBusAddress, 10,
message);
release_resource(IO_SYSTEM);
if (status != RS_success)
{
fprintf(com1, "I/O error = %d\n\r", status);
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
247
ioBusSelectForRead
Select I2C Slave Device for Reading
Syntax
#include
unsigned ioBusSelectForRead(unsigned char address);
Description
The ioBusSelectForRead function selects an I2C slave device for reading. It writes the
slave device address with the read/write bit set to the read state. The function handles the
formatting of the address byte.
The function has one parameter, the address of the device. It returns TRUE if the write
succeeded, that is the byte was acknowledged by the slave. It returns FALSE if the write
failed, that is the byte was not acknowledged by the slave.
Notes
This function can only be used immediately after a START condition, e.g. ioBusStart.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStart, ioBusStop, ioBusReadByte, ioBusReadLastByte, ioBusReadMessage,
ioBusSelectForWrite, ioBusWriteByte, ioBusWriteMessage
Example
See example for ioBusReadByte.
TelePACE C Tools User and Reference Manual
May 9, 2007
248
ioBusSelectForWrite
Select I2C Slave Device for Writing
Syntax
#include
unsigned ioBusSelectForWrite(unsigned char address);
Description
The ioBusSelectForWrite function selects an I2C slave device for writing. It writes the slave
device address with the read/write bit set to the write state. The function handles the
formatting of the address byte.
The function has one parameter, the address of the device. It returns TRUE if the write
succeeded, that is the byte was acknowledged by the slave. It returns FALSE if the write
failed, that is the byte was not acknowledged by the slave.
Notes
This function can only be used immediately after a START condition, e.g. ioBusStart.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStart, ioBusStop, ioBusReadByte, ioBusReadLastByte, ioBusReadMessage,
ioBusSelectForRead, ioBusWriteByte, ioBusWriteMessage
Example
See example for ioBusWriteByte.
TelePACE C Tools User and Reference Manual
May 9, 2007
249
ioBusStart
Issue an I2C Bus START Condition
Syntax
#include
void ioBusStart(void);
Description
The ioBusStart function issues an I2C bus START condition.
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStop, ioBusReadByte, ioBusReadLastByte, ioBusReadMessage,
ioBusSelectForRead ioBusSelectForWrite, ioBusWriteByte, ioBusWriteMessage
Example
See example for ioBusReadByte.
TelePACE C Tools User and Reference Manual
May 9, 2007
250
ioBusStop
Issue an I2C Bus STOP Condition
Syntax
#include
void ioBusStop(void);
Description
The ioBusStop function issues an I2C bus STOP condition.
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStart, ioBusReadByte, ioBusReadLastByte, ioBusReadMessage,
ioBusSelectForRead ioBusSelectForWrite, ioBusWriteByte, ioBusWriteMessage
Example
See example for ioBusReadByte.
TelePACE C Tools User and Reference Manual
May 9, 2007
251
ioBusWriteByte
Write One Byte to I2C Slave Device
Syntax
#include
unsigned ioBusWriteByte(unsigned char byte);
Description
The ioBusWriteByte function writes one byte to an I2C slave device and returns the
acknowledge signal from the slave. It returns TRUE if the write succeeded, that is the byte
was acknowledged by the slave. It returns FALSE if the write failed, that is the byte was not
acknowledged by the slave.
This function can be used multiple times in sequence to write data to a device.
Notes
ioBusWriteByte can be used to write the address selection byte at the start of an I2C
message; however, the ioBusSelectForRead and ioBusSelectForWrite functions provide
a more convenient interface for doing this.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStart, ioBusStop, ioBusReadByte, ioBusReadLastByte, ioBusReadMessage,
ioBusSelectForRead ioBusSelectForWrite, ioBusWriteMessage
Example
#include
void main(void)
{
unsigned char data[2];
unsigned char ioBusAddress = 114;
request_resource(IO_SYSTEM);
ioBusStart();
if (ioBusSelectForWrite(ioBusAddress))
{
ioBusWriteByte(data[0]);
ioBusWriteByte(data[1]);
}
ioBusStop();
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
252
ioBusWriteMessage
Write Message to I2C Slave Device
Syntax
#include
WRITESTATUS ioBusWriteMessage(unsigned address, unsigned numberBytes,
unsigned char *message);
Description
The ioBusWriteMessage function writes a specified number of bytes to an I2C slave device.
The function issues the START condition, selects the device for writing, writes the specified
number of bytes, and issues a STOP condition. If the slave fails to acknowledge the
selection or any data written to it, the write is aborted immediately.
The function has three parameters: the address of the device; the number of bytes to write,
numberBytes; and a pointer to the buffer, message, containing the data.
The function returns the status of the write:
Value
WS_success
WS_selectFailed
WS_noAcknowledge
Description
write was successful
slave could not be selected
slave failed to acknowledge data
Notes
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioBusStart, ioBusStop, ioBusReadByte, ioBusReadLastByte, ioBusReadMessage,
ioBusSelectForRead ioBusSelectForWrite, ioBusWriteByte
Example
#include
void main(void)
{
unsigned char
unsigned char
WRITESTATUS
message[10];
ioBusAddress = 114;
status;
request_resource(IO_SYSTEM);
/* Write a 10 byte message to I2C device */
status = ioBusWriteMessage(ioBusAddress, 10,
message);
release_resource(IO_SYSTEM);
if (status != WS_success)
{
fprintf(com1, "I/O error = %d\n\r", status);
}
}
TelePACE C Tools User and Reference Manual
May 9, 2007
253
ioClear
Turn Off all Outputs
Syntax
#include
void ioClear(void);
Description
The ioClear function turns off all outputs in the current Register Assignment as follows.
•
analog outputs are set to 0;
•
digital outputs are turned set to 0 (turned off).
If the Register Assignment is empty, all outputs are turned off for all possible I/O modules
that exist under the fixed I/O hardware mapping of firmware versions 1.22 or older.
Also, all delayed digital I/O actions started by the pulse, pulse_train and timeout functions
are always canceled.
Notes
Timers referenced by the pulse, pulse_train and timeout functions are set to 0. All other
timers are not affected.
The IO_SYSTEM resource must be requested before calling this function.
TelePACE C Tools User and Reference Manual
May 9, 2007
254
ioDatabaseReset
Initialize I/O Database with Default Values
Syntax
#include
void ioDatabaseReset(void);
Description
The ioDatabaseReset function resets all I/O database values to their defaults:
•
•
•
•
•
•
•
•
•
•
•
•
•
Configuration parameters are reset to default values. All registers assigned to
configuration parameters through the Register Assignment are also reset to default
values.
All other registers are set to zero. I/O hardware assigned to these registers through the
Register Assignment are also set to zero.
All forcing is removed.
Locked variables are unlocked.
Set all database locations to zero
Clear real time clock alarm settings
Clear serial port event counters
Clear store and forward configuration
Enable LED power by default and return to default state after 5 minutes
Set Outputs on Stop settings to Hold
Set 5904 HART modem configuration for all modems
Set Modbus/TCP default configuration
Write new default data to Flash
Notes
This function can be used to restore the controller to its default state. ioDatabaseReset has
the same effect as selecting the Initialize Controller option from the Initialize command in
the TelePACE program.
Use this function carefully as it erases any data stored in the I/O database.
The IO_SYSTEM resource must be requested before calling this function.
Example
#include
void main(void)
{
/* Power Up Initialization */
request_resource(IO_SYSTEM);
ioDatabaseReset();
release_resource(IO_SYSTEM);
/* ... the rest of the program */
}
TelePACE C Tools User and Reference Manual
May 9, 2007
255
ioRead16Din
Read 16 Digital Inputs into I/O Database
Syntax
#include
unsigned ioRead16Din(unsigned moduleAddress, unsigned startStatusRegister);
Description
The ioRead16Din function reads any 16 point Digital Input Module at the specified
moduleAddress. Data is read from all 16 digital inputs and copied to 16 consecutive status
registers beginning at startStatusRegister.
The function returns FALSE if the moduleAddress or startStatusRegister is invalid or if an
I/O error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startStatusRegister is any valid Modbus status
register between 10001 and (10000 + NUMSTATUS - 15).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead8Din
Example
This program displays the values of the 16 digital inputs read from a 16 point Digital Input
Module at module address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from digital input module and write it to I/O database
*/
ioRead16Din(0, 10001);
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10016; reg++)
{
fprintf(com1, "\n\r%d ", reg);
putchar( dbase(MODBUS, reg) ? '1' :'0');
}
TelePACE C Tools User and Reference Manual
May 9, 2007
256
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
257
ioRead32Din
Read 32 Digital Inputs into I/O Database
Syntax
#include
unsigned ioRead32Din(
UINT16 moduleAddress,
UINT16 startStatusRegister);
Description
The ioRead32Din function reads any 32 point Digital Input Module at the specified
moduleAddress. Data is read from all 32 digital inputs and copied to 32 consecutive status
registers beginning at startStatusRegister.
The function returns FALSE if the moduleAddress or startStatusRegister is invalid or
if an I/O error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startStatusRegister is any valid
Modbus status register between 10001 and (10001 + NUMSTATUS - 32).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker
command (.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead8Din, ioRead16Din
Example
This program displays the values of the 32 digital inputs read from a 32 point Digital Input
Module at module address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from module and write to I/O database */
ioRead32Din(0, 10001);
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10032; reg++)
{
TelePACE C Tools User and Reference Manual
May 9, 2007
258
fprintf(com1, "\n\r%d
", reg);
putchar( dbase(MODBUS, reg) ? '1' :'0');
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
259
ioRead4Ain
Read 4 Analog Inputs into I/O Database
Syntax
#include
unsigned ioRead4Ain(unsigned moduleAddress, unsigned startInputRegister);
Description
The ioRead4Ain function reads any 4 point Analog Input Module at the specified
moduleAddress. Data is read from all 4 analog inputs and copied to 4 consecutive input
registers beginning at startInputRegister.
The function returns FALSE if the moduleAddress or startInputRegister is invalid or if an I/O
error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startInputRegister is any valid Modbus input
register between 30001 and (30000 + NUMINPUT - 3).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead8Ain
Example
This program displays the values of the 4 analog inputs read from a 4 point Analog Input
Module at module address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from digital input module and write it to I/O database
*/
ioRead4Ain(0, 30001);
/* Print data from I/O database */
fprintf(com1, "Register
Value\n\r");
for(reg = 30001; reg <= 30004; reg++)
{
fprintf(com1, "%d
%d\n\r", reg,
}
dbase(MODBUS, reg));
release_resource(IO_SYSTEM);
TelePACE C Tools User and Reference Manual
May 9, 2007
260
}
TelePACE C Tools User and Reference Manual
May 9, 2007
261
ioRead4Counter
Read 4 Counter Inputs into I/O Database
Syntax
#include
unsigned ioRead4Counter(unsigned moduleAddress, unsigned
startInputRegister);
Description
The ioRead4Counter function reads any 4 point Counter Input Module at the specified
moduleAddress. Data is read from all 4 counter inputs and copied to 8 consecutive input
registers beginning at startInputRegister.
Each counter is a 32 bit number, stored in two input registers. The first register holds the
least significant 16 bits of the counter. The second register holds the most significant 16 bits
of the counter.
The maximum count is 4,294,967,295. Counters roll back to 0 when the maximum count is
exceeded.
The function returns FALSE if the moduleAddress or startInputRegister is invalid or if an I/O
error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startInputRegister is any valid Modbus input
register between 30001 and (30000 + NUMINPUT - 7).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section Overview of Functions for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
Example
This program displays the values of the 4 counter inputs read from a 4 point Counter Input
Module at module address 0.
#include
void main(void)
{
unsigned counter, reg;
unsigned long
value;
request_resource(IO_SYSTEM);
/* Read data from counter input module and
write it to I/O database */
ioRead4Counter(0, 30001);
/* Print data from I/O database */
fprintf(com1, "Counter Value\n\r");
counter = 0;
TelePACE C Tools User and Reference Manual
May 9, 2007
262
for(reg = 30001; reg <= 30008; reg+=2)
{
value = dbase(MODBUS, reg) +
((long) dbase(MODBUS, reg+1)<<16);
fprintf(com1, "%d
%ld\n\r", counter++,
value);
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
263
ioRead4202Inputs
Read SCADASense 4202 DR Inputs into I/O Database
Syntax
#include
unsigned ioRead4202Inputs(
unsigned startStatusRegister,
unsigned startInputRegister
);
Description
The ioRead4202Inputs function reads the digital, counter, and analog inputs from the
SCADASense 4202 DR I/O. Data are read from 1 digital input and copied to 1 consecutive
status registers beginning at startStatusRegister. Data is read from the analog input
and copied to 1 input register beginning at startInputRegister. Data are read from the
counter inputs and copied to 4 consecutive input registers beginning at
startInputRegister + 1.
startStatusRegister is any valid Modbus status register between 10001 and (10000
+ NUMSTATUS - 1). startInputRegister is any valid Modbus input register between
30001 and (30000 + NUMINPUT - 4).
The function returns FALSE if startStatusRegister or startInputRegister is invalid
or if an I/O error has occurred; otherwise TRUE is returned.
Notes
When this function reads data from the transnmitter (controller), it also processes the
receiver buffer for the com3 serial port. The com3 serial port is also continuously processed
automatically. The additional service to the com3 receiver caused by this function does not
affect the normal automatic operation of com3.
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
Digital inputs can also be read with the readCounterInput function.
Counters can also be read with the readCounter function.
Analog inputs can also be read with the readInternalAD function.
See Also
ioWrite4202Outputs, readCounter, readCounterInput
Example
This program displays the values of the 1 digital input, 2 counter inputs and 1 analog input
read from SCADASense 4202 DR I/O.
#include
void main(void)
{
TelePACE C Tools User and Reference Manual
May 9, 2007
264
request_resource(IO_SYSTEM);
/* Read 4202 DR inputs and write to I/O database */
ioRead4202Inputs (10001, 30001);
/* Print digital inputy */
fprintf(com2, "Register
Value");
fprintf(com2, "\n\r%d
", 10001);
putchar( dbase(MODBUS, 10001) ? '1' :'0');
/* print analog input */
fprintf(com2, "\n\r%d
%d", reg, dbase(MODBUS, 30001));
/* print counter inputs */
fprintf(com2, "Counter Value\n\r");
counter = 0;
for(reg = 30002; reg <= 30005; reg+=2)
{
value = dbase(MODBUS, reg) +
((long) dbase(MODBUS, reg+1)<<16);
fprintf(com2, "%d %ld\n\r", counter++, value);
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
265
ioRead4202DSInputs
Read SCADASense 4202 DS Inputs into I/O Database
Syntax
#include
unsigned ioRead4202DSInputs(
unsigned startStatusRegister,
unsigned startInputRegister
);
Description
The ioRead4202DSInputs function reads the digital, counter, and analog inputs from the
SCADASense 4202 DS I/O. Data are read from 1 digital input and copied to 1 consecutive
status registers beginning at startStatusRegister. Data is read from three analog
inputs and copied to 3 input register beginning at startInputRegister. Data are read
from the counter inputs and copied to 4 consecutive input registers beginning at
startInputRegister + 4.
startStatusRegister is any valid Modbus status register between 10001 and (10000
+ NUMSTATUS).
startInputRegister is any valid Modbus input register between 30001 and (30000 +
NUMINPUT - 6).
The function returns FALSE if startStatusRegister or startInputRegister is invalid
or if an I/O error has occurred; otherwise TRUE is returned.
Notes
When this function reads data from the SCADASense 4202 DS I/O it also processes the
receiver buffer for the com3 serial port. The com3 serial port is also continuously processed
automatically. The additional service to the com3 receiver caused by this function does not
affect the normal automatic operation of com3.
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
The digital input can also be read with the readCounterInput function.
Counters can also be read with the readCounter function.
Analog inputs can also be read with the readInternalAD function.
See Also
ioWrite4202DSOutputs, readCounter, readCounterInput, readInternalAD
Example
This program displays the values of the digital input, 2 counter inputs and 3 analog inputs
read from the SCADASense 4202 DS I/O.
#include
TelePACE C Tools User and Reference Manual
May 9, 2007
266
void main(void)
{
request_resource(IO_SYSTEM);
/* Read 4202 DS inputs and write to I/O database */
ioRead4202DSInputs (10001, 30001);
/* Print digital input */
fprintf(com2, "Register
Value");
fprintf(com2, "\n\r%d
", 10001);
putchar( dbase(MODBUS, 10001) ? '1' :'0');
/* print analog inputs */
fprintf(com2, "\n\r%d
%d",30001,dbase(MODBUS, 30001));
fprintf(com2, "\n\r%d
%d",30002,dbase(MODBUS, 30002));
fprintf(com2, "\n\r%d
%d",30003,dbase(MODBUS, 30003));
/* print counter inputs */
fprintf(com12 "Counter Value\n\r");
counter = 0;
for(reg = 30004; reg <= 30007; reg+=2)
{
value = dbase(MODBUS, reg) +
((long) dbase(MODBUS, reg+1)<<16);
fprintf(com2, "%d %ld\n\r", counter++, value);
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
267
ioRead5505Inputs
Read 5505 Inputs into I/O Database
Syntax
#include
UINT16 ioRead5505Inputs(
UINT16 moduleAddress,
UINT16 startStatusRegister,
UINT16 startInputRegister);
Description
The ioRead5505Inputs function reads the digital and analog inputs from the 5505 I/O. Data
is read from all 16 digital inputs and copied to 16 consecutive status registers beginning at
startStatusRegister. Data is read from all 4 analog inputs and copied to 8 consecutive
input registers in floating point format beginning at startInputRegister.
The function of the 16 digital inputs is described in the table below.
Point
Offset
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Function
OFF = channel 0 RTD is good
ON = channel 0 RTD is open or PWR input is off
OFF = channel 0 data in range
ON = channel 0 data is out of range
OFF = channel 0 RTD is using 3-wire measurement
ON = channel 0 RTD is using 4-wire measurement
reserved for future use
OFF = channel 1 RTD is good
ON = channel 1 RTD is open or PWR input is off
OFF = channel 1 data in range
ON = channel 1 data is out of range
OFF = channel 1 RTD is using 3-wire measurement
ON = channel 1 RTD is using 4-wire measurement
reserved for future use
OFF = channel 2 RTD is good
ON = channel 2 RTD is open or PWR input is off
OFF = channel 2 data in range
ON = channel 2 data is out of range
OFF = channel 2 RTD is using 3-wire measurement
ON = channel 2 RTD is using 4-wire measurement
reserved for future use
OFF = channel 3 RTD is good
ON = channel 3 RTD is open or PWR input is off
OFF = channel 3 data in range
ON = channel 3 data is out of range
OFF = channel 3 RTD is using 3-wire measurement
ON = channel 3 RTD is using 4-wire measurement
reserved for future use
The function returns FALSE if the moduleAddress, startStatusRegister or
startInputRegister is invalid or if an I/O error has occurred; otherwise TRUE is
returned.
TelePACE C Tools User and Reference Manual
May 9, 2007
268
moduleAddress is the address of the 5505 module. Valid values are 0 to 15.
startStatusRegister is any valid Modbus status register between 10001 and (10001 +
NUMSTATUS - 15).
startInputRegister is any valid Modbus input register between 30001 and (30001 +
NUMINPUT - 7).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
Example
This program displays the values of the 16 digital inputs and 4 analog inputs read from 5505
I/O at module address 3.
#include
void main(void)
{
UINT16 reg;
typedef union
{
UINT16 intValue[2];
float floatValue;
} UF_UNION;
UF_UNION value;
request_resource(IO_SYSTEM);
/* Read data from 5505 I/O into I/O database */
ioRead5505Inputs(3, 10001, 30001);
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10016; reg++)
{
fprintf(com1, "\n\r%d
", reg);
putchar(dbase(MODBUS, reg) ? '1' :'0');
}
for(reg = 30001; reg <= 30008; reg+2)
{
value.intValue[1] = dbase(MODBUS, reg);
value.intValue[0] = dbase(MODBUS, reg + 1);
fprintf(com1, "\n\r%d
%d", reg, value.floatValue);
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
269
ioRead5506Inputs
Read 5506 Inputs into I/O Database
Syntax
#include
UINT16 ioRead5506Inputs(
UINT16 moduleAddress,
UINT16 startStatusRegister,
UINT16 startInputRegister);
Description
The ioRead5506Inputs function reads the digital and analog inputs from the 5506 I/O. Data
is read from all 8 digital inputs and copied to 8 consecutive status registers beginning at
startStatusRegister. Data is read from all 8 analog inputs and copied to 8 consecutive
input registers beginning at startInputRegister.
The function returns FALSE if the moduleAddress, startStatusRegister or
startInputRegister is invalid or if an I/O error has occurred; otherwise TRUE is
returned.
moduleAddress is the address of the 5506 module. Valid values are 0 to 15.
startStatusRegister is any valid Modbus status register between 10001 and (10001 +
NUMSTATUS - 7).
startInputRegister is any valid Modbus input register between 30001 and (30001 +
NUMINPUT - 7).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite5606Outputs
Example
This program displays the values of the 8 digital inputs and 8 analog inputs read from 5506
I/O at module address 3.
#include
void main(void)
{
UINT16 reg;
request_resource(IO_SYSTEM);
/* Read data from 5506 I/O into I/O database */
ioRead5506Inputs(3, 10001, 30001);
TelePACE C Tools User and Reference Manual
May 9, 2007
270
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10008; reg++)
{
fprintf(com1, "\n\r%d
", reg);
putchar(dbase(MODBUS, reg) ? '1' :'0');
}
for(reg = 30001; reg <= 30008; reg++)
{
fprintf(com1, "\n\r%d
%d", reg,
dbase(MODBUS, reg));
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
271
ioRead5601Inputs
Read 5601 Inputs into I/O Database
Syntax
#include
unsigned ioRead5601Inputs(unsigned startStatusRegister, unsigned
startInputRegister);
Description
The ioRead5601Inputs function reads the digital and analog inputs from a 5601 I/O Module.
Data is read from all 16 digital inputs and copied to 16 consecutive status registers
beginning at startStatusRegister. Data is read from all 8 analog inputs and copied to 8
consecutive input registers beginning at startInputRegister.
The function returns FALSE if startStatusRegister or startInputRegister is invalid or if an I/O
error has occurred; otherwise TRUE is returned.
startStatusRegister is any valid Modbus status register between 10001 and (10000 +
NUMSTATUS - 15). startInputRegister is any valid Modbus input register between 30001
and (30000 + NUMINPUT - 7).
Notes
Note that when this function reads data from the 5601 it also processes the receiver buffer
for the com3 serial port. If the controller type is a SCADAPack or SCADAPack PLUS, the
com3 serial port is also continuously processed automatically.
The additional service to the com3 receiver caused by this function does not affect the
normal automatic operation of com3.
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite5601Outputs
Example
This program displays the values of the 16 digital inputs and 8 analog inputs read from a
5601 I/O Module.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from 5601 I/O module and write it
TelePACE C Tools User and Reference Manual
May 9, 2007
272
to I/O database */
ioRead5601Inputs(10001, 30001);
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10016; reg++)
{
fprintf(com1, "\n\r%d ", reg);
putchar( dbase(MODBUS, reg) ? '1' :'0');
}
for(reg = 30001; reg <= 30008; reg++)
{
fprintf(com1, "\n\r%d %d", reg,
dbase(MODBUS, reg));
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
273
ioRead5602Inputs
Read 5602 Inputs into I/O Database
Syntax
#include
unsigned ioRead5602Inputs(unsigned startStatusRegister, unsigned
startInputRegister);
Description
The ioRead5602Inputs function reads the inputs from a 5602 I/O Module as digital or
analog inputs. Data is read from all 5 analog inputs and copied to 5 consecutive input
registers beginning at startInputRegister. The same 5 analog inputs are also read as 5
digital inputs and copied to 5 consecutive status registers beginning at startStatusRegister.
A digital input is ON if the corresponding filtered analog input value is greater than or equal
to 20% of its full scale value, otherwise it is OFF. Analog input 0 to 4 correspond to digital
inputs 0 to 4.
The function returns FALSE if startStatusRegister or startInputRegister is invalid or if an I/O
error has occurred; otherwise TRUE is returned.
startStatusRegister is any valid Modbus status register between 10001 and (10000 +
NUMSTATUS - 4). startInputRegister is any valid Modbus input register between 30001 and
(30000 + NUMINPUT - 4).
Notes
Note that when this function reads data from the 5602 it also processes the receiver buffer
for the com4 serial port. If the controller type is a SCADAPack LIGHT or SCADAPack PLUS,
the com4 serial port is also continuously processed automatically.
The additional service to the com4 receiver caused by this function does not affect the
normal automatic operation of com4.
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite5602Outputs
Example
This program displays the values of the 5 inputs read from a 5602 I/O Module as both digital
and analog inputs.
#include
void main(void)
{
unsigned reg;
TelePACE C Tools User and Reference Manual
May 9, 2007
274
request_resource(IO_SYSTEM);
/* Read data from 5602 I/O module and write it
to I/O database */
ioRead5602Inputs(10001, 30001);
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10005; reg++)
{
fprintf(com1, "\n\r%d ", reg);
putchar( dbase(MODBUS, reg) ? '1' :'0');
}
for(reg = 30001; reg <= 30005; reg++)
{
fprintf(com1, "\n\r%d %d", reg,
dbase(MODBUS, reg));
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
275
ioRead5604Inputs
Read 5604 Inputs into I/O Database
Syntax
#include
unsigned ioRead5604Inputs(
unsigned startStatusRegister,
unsigned startInputRegister);
Description
The ioRead5604Inputs function reads the digital and analog inputs from the 5604 I/O.
Data is read from all 35 digital inputs and copied to 35 consecutive status registers
beginning at startStatusRegister. Data is read from all 10 analog inputs and copied to
10 consecutive input registers beginning at startInputRegister.
The function returns FALSE if startStatusRegister or startInputRegister is invalid
or if an I/O error has occurred; otherwise TRUE is returned.
startStatusRegister is any valid Modbus status register between 10001 and (10001 +
NUMSTATUS - 35).
startInputRegister is any valid Modbus input register between 30001 and (30001 +
NUMINPUT - 10).
Notes
When this function reads data from the 5604 I/O it also processes the receiver buffer for the
com3 serial port. The com3 serial port is also continuously processed automatically. The
additional service to the com3 receiver caused by this function does not affect the normal
automatic operation of com3.
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite5604Outputs
Example
This program displays the values of the 35 digital inputs and 10 analog inputs read from
5604 I/O.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from 5604 I/O into I/O database */
ioRead5604Inputs(10001, 30001);
TelePACE C Tools User and Reference Manual
May 9, 2007
276
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10035; reg++)
{
fprintf(com1, "\n\r%d
", reg);
putchar(dbase(MODBUS, reg) ? '1' :'0');
}
for(reg = 30001; reg <= 30010; reg++)
{
fprintf(com1, "\n\r%d
%d", reg,
dbase(MODBUS, reg));
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
277
ioRead5606Inputs
Read 5606 Inputs into I/O Database
Syntax
#include
UINT16 ioRead5606Inputs(
UINT16 moduleAddress,
UINT16 startStatusRegister,
UINT16 startInputRegister);
Description
The ioRead5606Inputs function reads the digital and analog inputs from the 5606 I/O. Data
is read from all 40 digital inputs and copied to 40 consecutive status registers beginning at
startStatusRegister. Data is read from all 8 analog inputs and copied to 8 consecutive
input registers beginning at startInputRegister.
The function returns FALSE if the moduleAddress, startStatusRegister or
startInputRegister is invalid or if an I/O error has occurred; otherwise TRUE is
returned.
moduleAddress is the address of the 5606 module. Valid values are 0 to 7.
startStatusRegister is any valid Modbus status register between 10001 and (10001 +
NUMSTATUS - 39).
startInputRegister is any valid Modbus input register between 30001 and (30001 +
NUMINPUT - 7).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite5606Outputs
Example
This program displays the values of the 40 digital inputs and 8 analog inputs read from 5606
I/O at module address 3.
#include
void main(void)
{
UINT16 reg;
request_resource(IO_SYSTEM);
/* Read data from 5606 I/O into I/O database */
ioRead5606Inputs(3, 10001, 30001);
TelePACE C Tools User and Reference Manual
May 9, 2007
278
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10040; reg++)
{
fprintf(com1, "\n\r%d
", reg);
putchar(dbase(MODBUS, reg) ? '1' :'0');
}
for(reg = 30001; reg <= 30008; reg++)
{
fprintf(com1, "\n\r%d
%d", reg,
dbase(MODBUS, reg));
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
279
ioRead8Ain
Read 8 Analog Inputs into I/O Database
Syntax
#include
unsigned ioRead8Ain(unsigned moduleAddress, unsigned startInputRegister);
Description
The ioRead8Ain function reads any 8 point Analog Input Module at the specified
moduleAddress. Data is read from all 8 analog inputs and copied to 8 consecutive input
registers beginning at startInputRegister.
The function returns FALSE if the moduleAddress or startInputRegister is invalid or if an I/O
error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startInputRegister is any valid Modbus input
register between 30001 and (30000 + NUMINPUT - 7).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead4Ain
Example
This program displays the values of the 8 analog inputs read from an 8 point Analog Input
Module at module address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from digital input module and write it to I/O database
*/
ioRead8Ain(0, 30001);
/* Print data from I/O database */
fprintf(com1, "Register
Value\n\r");
for(reg = 30001; reg <= 30008; reg++)
{
fprintf(com1, "%d
%d\n\r", reg,
}
dbase(MODBUS, reg));
release_resource(IO_SYSTEM);
TelePACE C Tools User and Reference Manual
May 9, 2007
280
}
TelePACE C Tools User and Reference Manual
May 9, 2007
281
ioRead8Din
Read 8 Digital Inputs into I/O Database
Syntax
#include
unsigned ioRead8Din(unsigned moduleAddress, unsigned startStatusRegister);
Description
The ioRead8Din function reads any 8 point Digital Input Module at the specified
moduleAddress. Data is read from all 8 digital inputs and copied to 8 consecutive status
registers beginning at startStatusRegister.
The function returns FALSE if the moduleAddress or startStatusRegister is invalid or if an
I/O error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startStatusRegister is any valid Modbus status
register between 10001 and (10000 + NUMSTATUS - 7).
Notes
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead16Din
Example
This program displays the values of the 8 digital inputs read from an 8 point Digital Input
Module at module address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from digital input module and write it to I/O database
*/
ioRead8Din(0, 10001);
/* For each digital input on the module */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10008; reg++)
{
fprintf(com1, "\n\r%d ", reg);
putchar( dbase(MODBUS, reg) ? '1' :'0');
}
TelePACE C Tools User and Reference Manual
May 9, 2007
282
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
283
ioReadLPInputs
Read SCADAPack LP Inputs into I/O Database
Syntax
#include
unsigned ioReadLPInputs (unsigned startStatusRegister, unsigned
startInputRegister);
Description
The ioReadLPInputs function reads the digital and analog inputs from the SCADAPack
LP I/O. Data is read from all 16 digital inputs and copied to 16 consecutive status registers
beginning at startStatusRegister. Data is read from all 8 analog inputs and copied to 8
consecutive input registers beginning at startInputRegister.
The function returns FALSE if startStatusRegister or startInputRegister is invalid
or if an I/O error has occurred; otherwise TRUE is returned.
startStatusRegister is any valid Modbus status register between 10001 and (10000 +
NUMSTATUS - 15). startInputRegister is any valid Modbus input register between
30001 and (30000 + NUMINPUT - 7).
Notes
When this function reads data from the SCADAPack LP I/O it also processes the receiver
buffer for the com3 serial port. The com3 serial port is also continuously processed
automatically. The additional service to the com3 receiver caused by this function does not
affect the normal automatic operation of com3.
Data is not copied to the I/O database for registers that are currently forced.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
Example
This program displays the values of the 16 digital inputs and 8 analog inputs read from
SCADAPack LP I/O.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Read data from LP I/O and write it to I/O database */
ioReadLPInputs (10001, 30001);
/* Print data from I/O database */
fprintf(com1, "Register
Value");
for (reg = 10001; reg <= 10016; reg++)
{
fprintf(com1, "\n\r%d
", reg);
putchar( dbase(MODBUS, reg) ? '1' :'0');
TelePACE C Tools User and Reference Manual
May 9, 2007
284
}
for(reg = 30001; reg <= 30008; reg++)
{
fprintf(com1, "\n\r%d
%d", reg,
dbase(MODBUS, reg));
}
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
285
ioReadSP100Inputs
Read SCADAPack 100 Inputs into I/O Database
Syntax
#include
unsigned ioReadSP100Inputs(unsigned startStatusRegister, unsigned
startInputRegister);
Description
The ioReadSP100Inputs function reads the digital and analog inputs from the
SCADAPack 100 I/O. Data is read from all 6 digital inputs and copied to 6 consecutive
status registers beginning at startStatusRegister. Data is read from all 6 analog inputs
and one counter input, and copied to 8 consecutive input registers beginning at
startInputRegister.
The function returns FALSE if startStatusRegister or startInputRegister is invalid
or if an I/O error has occurred; otherwise TRUE is returned.
startStatusRegister is any valid Modbus status register between 10001 and (10000 +
NUMSTATUS - 5). startInputRegister is any valid Modbus input register between 30001
and (30000 + NUMINPUT - 7).
Notes
Data is not copied to the I/O database for registers that are currently forced.
Data from the four external analog inputs is copied to the first four input registers.
Data from the temperature sensor is copied to the fifth input register.
Data from the battery voltage sensor is copied to the sixth input register.
Data from the counter input is copied to the seventh and eighth input registers.
To read data from an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWriteSP100Outputs
Example
This program displays the values of the 6 digital inputs, 6 analog inputs, and the counter
input read from SCADAPack 100 I/O.
#include
void main(void)
{
unsigned reg;
unsigned long count;
request_resource(IO_SYSTEM);
/* Read data from I/O and write it to I/O database */
TelePACE C Tools User and Reference Manual
May 9, 2007
286
ioReadSP100Inputs(10001, 30001);
/* Print digital data from I/O database */
for (reg = 10001; reg <= 10006; reg++)
{
fprintf(com1, "Register %d = %d\r\n", reg,
dbase(MODBUS, reg));
}
fprintf(com1, "\r\n");
/* Print analog data from I/O database */
for(reg = 30001; reg <= 30006; reg++)
{
fprintf(com1, "Regsiter %d = %d\n\r", reg,
dbase(MODBUS, reg));
}
fprintf(com1, "\r\n");
/* Print counter data from I/O database */
count = dbase(MODBUS, 30006);
count += ((unsigned long) dbase(MODBUS, reg)) << 16;
fprintf(com1, "Registers 30006 & 30007 = %ul\r\n", reg,
count);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
287
ioRefresh
Update Outputs with Internal Data
Syntax
#include
void ioRefresh(void);
Description
The ioRefresh function resets devices on the 5000 series I/O bus. Input channels are
scanned to update their values from the I/O hardware. Output channels are scanned to write
their values from output tables in memory.
Notes
This function is normally only used by the sleep function to restore output states when the
controller wakes.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioClear, ioReset
TelePACE C Tools User and Reference Manual
May 9, 2007
288
ioReset
Reset 5000 Series I/O Modules
Syntax
#include
void ioReset(unsigned state);
Description
The ioReset function sets the state of the 5000 Series I/O bus reset signal. state may be
TRUE or FALSE.
The reset signal restarts all devices on the 5000 Series I/O bus. Output modules clear all
their output points. Input modules restart their input scanning. All modules remain in the
reset state until the reset signal is set to FALSE.
Notes
Do not leave the reset signal in the TRUE state. This will disable I/O.
The ioClear function provides a more effective method of resetting the I/O system.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioClear
TelePACE C Tools User and Reference Manual
May 9, 2007
289
ioWrite16Dout
Write to 16 Digital Outputs from I/O Database
Syntax
#include
unsigned ioWrite16Dout(unsigned moduleAddress, unsigned startCoilRegister);
Description
The ioWrite16Dout function writes data to any 16 point Digital Output Module at the
specified moduleAddress. Data is read from 16 consecutive coil registers beginning at
startCoilRegister, and written to the 16 digital outputs.
The function returns FALSE if the moduleAddress or startCoilRegister is invalid or if an I/O
error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startCoilRegister is any valid Modbus coil
register between 00001 and (NUMCOIL - 15).
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
Refer to the section Overview of Functions for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite8Dout
Example
This program turns ON all 16 digital outputs of a 16 point Digital Output Module at module
address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Write data to I/O database */
for (reg = 1; reg <= 16; reg++)
{
setdbase(MODBUS, reg, 1);
}
/* Write data from I/O database to digital
output module */
ioWrite16Dout(0, 1);
release_resource(IO_SYSTEM);
TelePACE C Tools User and Reference Manual
May 9, 2007
290
}
TelePACE C Tools User and Reference Manual
May 9, 2007
291
ioWrite32Dout
Write to 32 Digital Outputs from I/O Database
Syntax
#include
unsigned ioWrite32Dout(
UINT16 moduleAddress,
UINT16 startCoilRegister);
Description
The ioWrite32Dout function writes data to any 32-point Digital Output Module at the
specified moduleAddress. Data is read from 32 consecutive coil registers beginning at
startCoilRegister, and written to the 32 digital outputs.
The function returns FALSE if the moduleAddress or startCoilRegister is invalid or if
an I/O error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startCoilRegister is any valid Modbus
coil register between 00001 and (NUMCOIL - 31).
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
This function is contained in the ctools.lib library. Load this library in you linker
command (.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite8Dout, ioWrite16Dout
Example
This program turns ON all 32 digital outputs of a 32 point Digital Output Module at module
address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Write data to I/O database */
for (reg = 1; reg <= 32; reg++)
{
setdbase(MODBUS, reg, 1);
}
/* Write data from I/O database to digital
output module */
ioWrite32Dout(0, 1);
TelePACE C Tools User and Reference Manual
May 9, 2007
292
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
293
ioWrite8Dout
Write to 8 Digital Outputs from I/O Database
Syntax
#include
unsigned ioWrite8Dout(unsigned moduleAddress, unsigned startCoilRegister);
Description
The ioWrite8Dout function writes data to any 8 point Digital Output Module at the specified
moduleAddress. Data is read from 8 consecutive coil registers beginning at
startCoilRegister, and written to the 8 digital outputs.
The function returns FALSE if the moduleAddress or startCoilRegister is invalid or if an I/O
error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startCoilRegister is any valid Modbus coil
register between 00001 and (NUMCOIL - 7).
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
Refer to the section Overview of Functions for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite16Dout
Example
This program turns ON all 8 digital outputs of an 8 point Digital Output Module at module
address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Write data to I/O database */
for (reg = 1; reg <= 8; reg++)
{
setdbase(MODBUS, reg, 1);
}
/* Write data from I/O database to digital
output module */
ioWrite8Dout(0, 1);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
294
ioWrite2Aout
Write to 2 Analog Outputs from I/O Database
Syntax
#include
unsigned ioWrite2Aout(unsigned moduleAddress, unsigned
startHoldingRegister);
Description
The ioWrite2Aout function writes data to any 2 point Analog Output Module at the specified
moduleAddress. Data is read from 2 consecutive holding registers beginning at
startHoldingRegister, and written to the 2 analog outputs.
The function returns FALSE if the moduleAddress or startHoldingRegister is invalid or if an
I/O error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startHoldingRegister is any valid Modbus
holding register between 40001 and (40000 + NUMHOLDING - 1).
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
Refer to the section Overview of Functions for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite4Aout, ioWrite5303Aout
Example
This program sets both analog outputs to half scale on a 2 point Analog Output Module at
module address 0.
#include
void main(void)
{
request_resource(IO_SYSTEM);
/* Write data to I/O database */
setdbase(MODBUS, 40001, 16384);
setdbase(MODBUS, 40002, 16384);
/* Write data from I/O database to analog
output module */
ioWrite2Aout(0, 40001);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
295
ioWrite4Aout
Write to 4 Analog Outputs from I/O Database
Syntax
#include
unsigned ioWrite4Aout(unsigned moduleAddress, unsigned
startHoldingRegister);
Description
The ioWrite4Aout function writes data to any 4 point Analog Output Module at the specified
moduleAddress. Data is read from 4 consecutive holding registers beginning at
startHoldingRegister, and written to the 4 analog outputs.
The function returns FALSE if the moduleAddress or startHoldingRegister is invalid or if an
I/O error has occurred; otherwise TRUE is returned.
The valid range for moduleAddress is 0 to 15. startHoldingRegister is any valid Modbus
holding register between 40001 and (40000 + NUMHOLDING - 3).
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
Refer to the section Overview of Functions for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite2Aout, ioWrite5303Aout
Example
This program sets all 4 analog outputs to half scale on a 4 point Analog Output Module at
module address 0.
#include
void main(void)
{
unsigned reg;
request_resource(IO_SYSTEM);
/* Write data to I/O database */
for (reg = 40001; reg <= 40004; reg++)
{
setdbase(MODBUS, reg, 16384);
}
/* Write data from I/O database to analog
output module */
ioWrite4Aout(0, 40001);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
296
ioWrite4AoutChecksum
Write to 4 Point Analog Output Module with Checksum
Syntax
#include
UINT16 ioWrite4AoutChecksum(
UINT16 moduleAddress,
UINT16 startHoldingRegister
)
Description
The ioWrite4AoutChecksum function writes data to a 4-point analog output module with
checksum support. Output data comes from the I/O database. The function can be used with
5304 analog output modules. Use the isaWrite4Aout function for all other analog output
modules.
The function has two parameters.
•
moduleAddress is the address of the module. The valid range is 0 to 15.
•
Data are read from 4 consecutive holding registers and written to 4 analog outputs.
startHoldingRegister is any valid Modbus holding register between 40001 and
(40001 + NUMHOLDING - 4).
The function returns FALSE if the moduleAddress or startHoldingRegister is invalid,
or if an I/O error occurs; otherwise TRUE is returned.
Notes
The IO_SYSTEM resource must be requested before calling this function.
This function is contained in the ctools.lib library. Load this library in you linker
command (.cmd) file as shown in the sample file appram.cmd in your ctools directory.
To write data to an I/O Module continuously, add the module to the Register Assignment.
See Also
ioWrite2Aout, ioWrite4Aout, ioWrite5303Aout
Example
This program sets all 4 analog outputs to half scale on a 5304 Analog Output Module at
module at address 0.
#include
void main(void)
{
UINT16 reg;
request_resource(IO_SYSTEM);
/* Write data to I/O database */
for (reg = 40001; reg <= 40004; reg++)
{
setdbase(MODBUS, reg, 16384);
TelePACE C Tools User and Reference Manual
May 9, 2007
297
}
/* Write I/O database to 5304 analog output module */
ioWrite4AoutChecksum(0, 40001);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
298
ioWrite4202Outputs
Write to SCADASense 4202 DR Outputs from I/O Database
Syntax
#include
unsigned ioWrite4202Outputs(
unsigned startHoldingRegister
);
Description
The ioWrite4202Outputs function writes data to the analog output of the SCADASense
4202 DR I/O. Analog data is read from 1 holding register beginning at
startHoldingRegister and written to the analog output.
startHoldingRegister is any valid Modbus holding register between 40001 and (4000 +
NUMHOLDING).
The function returns FALSE if startHoldingRegister is invalid, or if an I/O error has
occurred; otherwise TRUE is returned.
Notes
When this function writes data to the SCADASense 4202 DR I/O it also processes the
transmit buffer for the com3 serial port. The com3 serial port is also continuously processed
automatically. The additional service to the com3 receiver caused by this function does not
affect the normal automatic operation of com3.
To write data to an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead4202Inputs, ioWrite4202OutputsEx
Example
This program sets the analog output to full scale.
#include
void main(void)
{
request_resource(IO_SYSTEM);
/* Write analog data to I/O database */
setdbase(MODBUS, 40001, 32767);
/* Write data from I/O database to 4202 DR output */
ioWrite4202Outputs(40001);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
299
ioWrite4202OutputsEx
Write to SCADASense 4202 DR with Extended Outputs, from I/O Database
Syntax
#include
unsigned ioWrite4202OutputsEx(
unsigned startCoilRegister,
unsigned startHoldingRegister
);
Description
The ioWrite4202OutputsEx function writes data to the outputs of the SCADASense
4202 DR with Extended I/O (digital output). Digital data is read from one coil register starting
at startCoilRegister and written to the digital output. Analog data is read from 1 holding
register beginning at startHoldingRegister and written to the analog output.
startCoilRegister is any valid Modbus coil register between 1 and (NUMCOIL).
startHoldingRegister is any valid Modbus holding register between 40001 and (4000 +
NUMHOLDING).
The function returns FALSE if startCoilRegister or startHoldingRegister are
invalid, or if an I/O error has occurred; otherwise TRUE is returned.
Notes
When this function writes data to the SCADASense 4202 DR I/O it also processes the
transmit buffer for the com3 serial port. The com3 serial port is also continuously processed
automatically. The additional service to the com3 receiver caused by this function does not
affect the normal automatic operation of com3.
To write data to an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead4202Inputs
Example
This program sets the analog output to full scale and turns on the digital output.
#include
void main(void)
{
request_resource(IO_SYSTEM);
/* Write output data to I/O database */
setdbase(MODBUS, 1, 1);
setdbase(MODBUS, 40001, 32767);
/* Write data from I/O database to 4202 DR outputs */
ioWrite4202OutputsEx(1, 40001);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
300
ioWrite4202DSOutputs
Write to SCADASense 4202 DS Outputs from I/O Database
Syntax
#include
unsigned ioWrite4202DSOutputs(
unsigned startCoilRegister
);
Description
The ioWrite4202DSOutputs function writes data to the outputs of the SCADASense 4202 DS
I/O module. Digital data is read from two coil registers starting at startCoilRegister and
written to the digital outputs.
startCoilRegister is any valid Modbus coil register between 1 and (NUMCOIL - 1).
The function returns FALSE if startCoilRegister is invalid, or if an I/O error has
occurred; otherwise TRUE is returned.
Notes
When this function writes data to the SCADASense 4202 DS I/O it also processes the
transmit buffer for the com3 serial port. The com3 serial port is also continuously processed
automatically. The additional service to the com3 receiver caused by this function does not
affect the normal automatic operation of com3.
To write data to an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead4202DSInputs
Example
This program turns on the digital outputs.
#include
void main(void)
{
request_resource(IO_SYSTEM);
/* Write output data to I/O database */
setdbase(MODBUS, 1, 1);
setdbase(MODBUS, 2, 1);
/* Write data from I/O database to 4202 DS outputs */
ioWrite4202DSOutputs(1);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
301
ioWrite5303Aout
Write to 5303 Analog Outputs from I/O Database
Syntax
#include
unsigned ioWrite5303Aout(unsigned startHoldingRegister);
Description
The ioWrite5303Aout function writes data to the 2 points on a 5303 SCADAPack Analog
Output Module. Data is read from 2 consecutive holding registers beginning at
startHoldingRegister, and written to the 2 analog outputs.
The function returns FALSE if startHoldingRegister is invalid or if an I/O error has occurred;
otherwise TRUE is returned.
startHoldingRegister is any valid Modbus holding register between 40001 and (40000 +
NUMHOLDING - 1).
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
Refer to the section I/O Database and Register Assignment for details.
This function is contained in the ctools.lib library. Load this library in you linker command
(.cmd) file as shown in the sample file appram.cmd in your ctools directory.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioWrite2Aout, ioWrite5303Aout
Example
This program sets both analog outputs to half scale on a 5303 Analog Output Module.
#include
void main(void)
{
request_resource(IO_SYSTEM);
/* Write data to I/O database */
setdbase(MODBUS, 40001, 16384);
setdbase(MODBUS, 40002, 16384);
/* Write data from I/O database to analog
output module */
ioWrite5303Aout(40001);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
302
ioWrite5505Outputs
Write to 5505 Configuration from I/O Database
Syntax
#include
UINT16 ioWrite5505Outputs(
UINT16 moduleAddress,
UINT16 inputType[4],
UINT16 inputFilter
);
Description
The ioWrite5505Outputs function writes configuration data to the 5505 I/O module.
The function returns FALSE if moduleAddress is invalid, or if an I/O error has occurred;
otherwise TRUE is returned.
moduleAddress is the address of the 5505 module. Valid values are 0 to 15.
inputType is an array of 4 values indicating the input range for the corresponding analog
input. Valid values are
•
•
•
•
0 = RTD in deg Celsius
1 = RTD in deg Fahrenheit
2 = RTD in deg Kelvin
3 = resistance measurement in ohms.
inputFilter is the analog input filter setting. Valid values are.
•
•
•
•
0 = 0.5 s
1=1s
2=2s
3=4s
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
Example
This program writes configuration data to a 5505 I/O module at module address 5.
#include
void main(void)
{
UINT16 index;
UINT16 inputType[4];
UINT16 inputFilter;
request_resource(IO_SYSTEM);
/* set the input types */
for (index = 0; index < 4; index++)
TelePACE C Tools User and Reference Manual
May 9, 2007
303
{
inputType[index] = 1; // RTD in deg F
}
/* set filter */
inputFilter = 3;
// maximum filter
/* Write configuration data to 5505 I/O module */
ioWrite5505Outputs(5, inputType, inputFilter);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
304
ioWrite5506Outputs
Write to 5506 Configuration from I/O Database
Syntax
#include
UINT16 ioWrite5506Outputs(
UINT16 moduleAddress,
UINT16 inputType[8],
UINT16 inputFilter,
UINT16 scanFrequency
);
Description
The ioWrite5506Outputs function writes configuration data to the 5506 I/O module.
The function returns FALSE if moduleAddress is invalid, or if an I/O error has occurred;
otherwise TRUE is returned.
moduleAddress is the address of the 5506 module. Valid values are 0 to 15.
inputType is an array of 8 values indicating the input range for the corresponding analog
input. Valid values are
•
0 = 0 to 5 V
•
1 = 1 to 5 V
•
2 = 0 to 20 mA
•
3 = 4 to 20 mA.
inputFilter is the analog input filter setting. Valid values are.
•
0 = 3 Hz
•
1 = 6 Hz
•
2 = 11 Hz
•
3 = 30 Hz
scanFrequency is the scan frequency setting. Valid values are.
•
0 = 60 Hz
•
1 = 50 Hz
Notes
To write data to an I/O Module continuously, add the module to the Register Assignment.
The IO_SYSTEM resource must be requested before calling this function.
See Also
ioRead5606Inputs
TelePACE C Tools User and Reference Manual
May 9, 2007
305
Example
This program writes configuration data to a 5506 I/O module at module address 5.
#include
void main(void)
{
UINT16 index;
UINT16 inputType[8];
UINT16 inputFilter;
UINT16 scanFrequency;
request_resource(IO_SYSTEM);
/* set the input types */
for (index = 0; index < 8; index++)
{
inputType[index] = 1; // 1 to 5 V
}
/* set filter and frequency */
inputFilter = 3;
// minimum filter
scanFrequency = 0;
// 60 Hz
/* Write configuration data to 5506 I/O module */
ioWrite5506Outputs(5, inputType, inputFilter, scanFrequency);
release_resource(IO_SYSTEM);
}
TelePACE C Tools User and Reference Manual
May 9, 2007
306
ioWrite5601Outputs
Write to 5601 Outputs from I/O Database
Syntax
#include