Eio0000000549 PDF

E
I
O
0
0
0
0
0
0
0
5
4
9
.
0
4
www.schneider-electric.com
LL984 Editor
EIO0000000549 07/2012
LL984 Editor
Reference Manual
LL984 Specifics
07/2012
2 EIO0000000549 07/2012

The information provided in this documentation contains general descriptions and/or
technical characteristics of the performance of the products contained herein. This
documentation is not intended as a substitute for and is not to be used for
determining suitability or reliability of these products for specific user applications. It
is the duty of any such user or integrator to perform the appropriate and complete
risk analysis, evaluation and testing of the products with respect to the relevant
specific application or use thereof. Neither Schneider Electric nor any of its affiliates
or subsidiaries shall be responsible or liable for misuse of the information that is
contained herein. If you have any suggestions for improvements or amendments or
have found errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic
or mechanical, including photocopying, without express written permission of
Schneider Electric.
All pertinent state, regional, and local safety regulations must be observed when
installing and using this product. For reasons of safety and to help ensure
compliance with documented system data, only the manufacturer should perform
repairs to components.
When devices are used for applications with technical safety requirements, the
relevant instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware
products may result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
2012 Schneider Electric. All rights reserved.
EIO0000000549 07/2012 3
Table of Contents
Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About the Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Part I Data Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 1 General Functions of the Data Editor . . . . . . . . . . . . . . . 13
Configuring the Data Editor columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part II Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2 General Functions of the LL984 Editor. . . . . . . . . . . . . . 19
General Functions and Layout of the LL984 Editor. . . . . . . . . . . . . . . . . . 20
Toolbar of the LL984 Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
General Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 3 Accessing Tasks and Sections . . . . . . . . . . . . . . . . . . . . 31
Creating LL984 Segments and Networks . . . . . . . . . . . . . . . . . . . . . . . . . 32
Modifying LL984 Segment Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Modifying LL984 Network Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Scheduling LL984 Segments and Network . . . . . . . . . . . . . . . . . . . . . . . . 40
Deleting, Cutting, Copying and Pasting LL984 Segments and Network . . 41
Chapter 4 Unity Pro Software Options. . . . . . . . . . . . . . . . . . . . . . . 43
4.1 Project Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.2 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Data and Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 5 Common Functions for Graphical Languages. . . . . . . . 51
Using Bookmarks in Graphical Languages Sections . . . . . . . . . . . . . . . . 51
Chapter 6 LL984 Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.1 Creating a Program with LL984 Programming Language. . . . . . . . . . . . . 58
Project Settings for LL984 Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Creating an LL984 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Syntax and Semantics Check During Programming . . . . . . . . . . . . . . . . . 63
Network Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Navigating with the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4 EIO0000000549 07/2012
Selecting Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Deleting, Cutting, Copying, Pasting and Moving Objects . . . . . . . . . . . . 71
Displaying the Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Inserting and Deleting Rows/Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2 Editing Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Selecting Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Placing Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Properties Dialog for Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.3 Editing Coils. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Selecting Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Placing Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Property Dialog for Coils . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.4 Editing Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Editing Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Using Mnemonics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.5 Editing Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Selecting Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Combining Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Placing Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Editing Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.6 Editing Equation Network Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Editing Equation Network Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Editing the ST Assignment Expression . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.7 Assigning Variables to LL984 Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Assigning Variables to LL984 Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6.8 Calling Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Calling Subroutines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
6.9 Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 7 Programming Languages Data Selection Dialog . . . . . . 121
Data Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Chapter 8 Search/Replace Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Overview of the Search / Replace tool. . . . . . . . . . . . . . . . . . . . . . . . . . . 126
General Features for Search/Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Searching for Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Replacing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Search Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Data Search Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Cross-References (Search Results) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Cross-References (Replace) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Tracing Variables / Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
EIO0000000549 07/2012 5
Part III Debugging and Adjustment . . . . . . . . . . . . . . . . . . . 139
Chapter 9 Viewing and Adjusting Variables . . . . . . . . . . . . . . . . . . 141
Force Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Instruction Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Part IV Import / Export of LL984 Applications . . . . . . . . . . . 151
Chapter 10 Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Importing an LL984 Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Importing PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Importing Specific CPU Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Importing Hot Standby Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Importing I/O Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Importing Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Importing Descriptors and Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Import Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Importing Application Parts with the Conversion Wizard. . . . . . . . . . . . . . 191
Chapter 11 Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Exporting/Importing LL984 Segments/Networks. . . . . . . . . . . . . . . . . . . . 193
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Appendix A Supported / Not Supported I/O Modules . . . . . . . . . . . . 197
Quantum Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Series 800 Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Series 200/500 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
SY/MAX Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Compact Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Appendix B Special Conversion for Compact I/O Modules. . . . . . . . 223
B.1 Digital Input Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Digital Input Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
B.2 Digital Output Modules Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Digital Output Modules Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
B.3 Digital Mixed Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Digital Mixed Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
B.4 Analog Input Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Analog Input Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
ADU 206/256. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
ADU 205 Voltage and Current. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
ADU 210 Voltage and Current. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
ADU 204/ADU 254 Thermocouple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
ADU 214 Mixed Voltage, Current, Thermocouple and Resistors . . . . . . . 241
ADU 257 One and Two Channel Thermocouple with 32 bit . . . . . . . . . . . 245
ADU 211/212, ADU 216 Hardware Switch Configured Modules. . . . . . . . 246
FRQ xxx, ZAE xxx, MOT_xxx, VIC_xxx, Counting and Positioning
Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
6 EIO0000000549 07/2012
B.5 Analog Output Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Analog Output Modules Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
DAU 204 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
DAU 208 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
DAU 2x2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
EIO0000000549 07/2012 7
Safety Information
Important Information
NOTICE
Read these instructions carefully, and look at the equipment to become familiar with
the device before trying to install, operate, or maintain it. The following special
messages may appear throughout this documentation or on the equipment to warn
of potential hazards or to call attention to information that clarifies or simplifies a
procedure.
8 EIO0000000549 07/2012
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by
qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction
and operation of electrical equipment and its installation, and has received safety
training to recognize and avoid the hazards involved.
EIO0000000549 07/2012 9
About the Book
At a Glance
Document Scope
This documentation describes the specifics of Unity Pro with LL984 Editor.
Validity Note
This documentation is valid from Unity Pro 7.0.
For standard features please refer to the Unity Pro, Operating Modes Manual.
NOTE: With Unity Pro 6.0 the LL984 language is supported for Quantum PLCs (but
not for Quantum Safety PLCs).
With Unity Pro 6.1 the LL984 language is supported for Modicon M340 PLCs with
Modicon M340 firmware 2.4 or later.
Related Documents
You can download these technical publications and other technical information from
our website at www.schneider-electric.com.
User Comments
We welcome your comments about this document. You can reach us by e-mail at
techcomm@schneider-electric.com.
Title of Documentation Reference Number
Unity Pro Original LL984 Block Library EIO0000000550
Unity Pro Operating Modes Manual 33003101
Unity Pro Languages and Program Structure, Reference Manual EN 35006144
10 EIO0000000549 07/2012
EIO0000000549 07/2012 11
I
LL984 Editor
Data Editor
EIO0000000549 07/2012
Data Editor
Data Editor
12 EIO0000000549 07/2012
EIO0000000549 07/2012 13
1
LL984 Editor
General Functions of the Data Editor
EIO0000000549 07/2012
General Functions of the Data
Editor
Configuring the Data Editor columns
Introduction
In every Data Editor tab you can configure the column display (a default
configuration is suggested). This lets you:
define the columns you want to display,
define the sequence for the columns shown.
Columns Available
The following table showns the different columns available in the Data Editor under
various tabs.
Column Name Description
Name name of the instance or data type
Type data type
Address address in the controller for referencing the variables
984 Address LL984 address of the variable (%Mx = 00000x, %Ix = 10000x, %IWx =
30000x, %MWx = 40000x)
This column is only available for Quantum PLCs (but not for Quantum
Safety PLCs).
Value initial value for the variables
Comment comment for the variables
Custom free text for use of an external tool or for special user requirements
Global data Shows if the variable is a variable that was swapped between different
stations via the network.
Global data
- Group
number of the group (the variables) in which the variable is transported
Global data
- ID
number for the unique display of a variable in the group (the variables)
14 EIO0000000549 07/2012
Alias name selected by the user which makes it possible to change an IODDT,
DDT or an Array element to a name defined by the manufacturer or the
user
Alias of complete path of the variable sub-field on which user sets Alias attribute
Save Shows if the variable accepts the mechanism for updating initial values
with current values.
Used number of times the variables are used in the program and in other parts
of the project (animation tables, user windows)
RW program Shows if the variable can or can not be written by the program.
Constant Shows if the variable is a constant or not.
Descriptor descriptors (1 to 9) of variables
Descriptor 1 is displayed after selecting this column in the Column
Configuration dialog. Descriptors 2 to 9 can be displayed using the +
sign in the Descriptor column header.
No. order number of a function block
Version type version
HMI When General Project Settings Data Dictionnary Only HMI
variables is checked, this reduces memory usage.
Column Name Description
EIO0000000549 07/2012 15
Defining Columns
NOTE: The Name and Type columns are required.
Step Action
1 Select the desired tab in the Data Editor.
2 Via the context menu open the Column Configuration dialog using Customize Columns.
The following dialog appears.
3 Check the check boxes that correspond to the columns you wish to display.
4 Confirm the changes using the command OK.
16 EIO0000000549 07/2012
Description of the buttons
Changing the Columns Sequence
NOTE: The first column must always correspond with the attribute Name.
Button Description
OK confirms the configuration and exits the dialog
Cancel discards the changes and exits the dialog
Default restores the default configuration
Help opens the Help of the Column Configuration dialog
Step Action
1 Select the desired tab in the Data Editor.
2 Via the context menu open the Column Configuration dialog using Customize
Columns.
3 Place the cursor on the chosen attribute and move it to the desired location by
clicking on the two buttons to the right of the window.
4 Confirm by clicking OK.
EIO0000000549 07/2012 17
II
LL984 Editor
Programming
EIO0000000549 07/2012
Programming
Overview
This part describes the specifics of the LL984 Editor.
For standard features please refer to Programming (see Unity Pro, Operating
Modes).
What Is in This Part?
This part contains the following chapters:
Chapter Chapter Name Page
2 General Functions of the LL984 Editor 19
3 Accessing Tasks and Sections 31
4 Unity Pro Software Options 43
5 Common Functions for Graphical Languages 51
6 LL984 Editor 57
7 Programming Languages Data Selection Dialog 121
8 Search/Replace Tool 125
Programming
18 EIO0000000549 07/2012
EIO0000000549 07/2012 19
2
LL984 Editor
General Functions of the LL984 Editor
EIO0000000549 07/2012
General Functions of the LL984
Editor
Overview
This chapter describes the general functions of the LL984 Editor.
What Is in This Chapter?
This chapter contains the following topics:
Topic Page
General Functions and Layout of the LL984 Editor 20
Toolbar of the LL984 Editor 23
General Restrictions 26
20 EIO0000000549 07/2012
General Functions and Layout of the LL984 Editor
Introduction
Each LL984 network displayed in the LL984 Editor contains a matrix of 7 rows and
11 columns, where you can place contacts, coils, function blocks etc.
Launching the LL984 Editor
Double-click a LL984 network in the Program section of the Structural View of the
Project Browser.
A new LL984 Editor window is opened and the network is displayed there.
LL984 Editor windows can be maximized, so that only one editor window is visible
at a time.
Displaying the Network Name
If the editor window is minimized, the name of an LL984 network is displayed in the
title bar of the editor.
If the editor window is maximized, the name of an LL984 network is displayed in the
title bar of the Unity Pro main window.
Switching Between Networks
Using Ctrl+Alt+Page Down / Ctrl+Alt+Page Up you can switch to the next/previous
section, which is then displayed in the same editor window.
This does not modify the current selection in Project Browser, where still the first
section is highlighted which was opened by double-click.
If the last/first row of a network is already visible, simple Page Down/Page Up
displays the next/previous network.
Using Page Down in the last network of a segment, if the last row is already visible,
will display a message box asking you to create a new network.
Please also refer to Navigating with the Keyboard (see page 67).
EIO0000000549 07/2012 21
Only 1 Window for Open Commands
Under Tools Options Data and Languages Languages LL984 you can
activate/deactivate the Reuse 984 editor window when network is opened
option.
If this check box is checked only 1 window is used for Open commands on LL984
networks.
If this check box is not checked, for each Open command on an LL984 network, a
new window is opened.
Please refer to Options (see page 48).
Zoom
Use the buttons Zoom In, Zoom Out and Zoom to Fit from the Unity Pro menu bar
or the commands under View Zoom.
Displaying the Function Blocks
Example AND
The function blocks of the Original LL984 Block Library are displayed
1 cell wide and 1 to 3 cells high
with boolean pins (inputs/outputs) on the left and the right side of the function
block
with parameters (nodes) in the middle of the block (top, middle and bottom node)
Not assigned nodes are displayed as ?????.
with block type name at the bottom of the block without prefix (for example
L9_AND is displayed as AND)
In other tools and editors (like Type Library Browser, Data Editor etc.) the blocks
are displayed with their prefix (L9_AND).
no pin names are shown
the left and the right side of DFBs are displayed as double lines
function blocks with detected analyze errors are displayed in blue
22 EIO0000000549 07/2012
If the cursor is placed over a not assigned pin, a tooltip is displayed with pin name
and comment. If a pin is assigned, information about the assigned variable is
displayed (refer to Network Display (see page 66)).
For detailed information please refer to the function block descriptions (see Unity
Pro, Original LL984, Block Library).
Using the Toolbar
Please refer to Toolbar of the LL984 Editor (see page 23).
EIO0000000549 07/2012 23
Toolbar of the LL984 Editor
Introduction
The LL984 Editor provides a toolbar at the top of the editor window which contains
an arrow button (Select Mode), the most frequent LL984 objects, buttons to open
special function editor tools, function bocks for subroutines and an assortment of
frequently used functions blocks for LL984 networks.
Additionally the toolbar provides a button to open the LL984 Instruction Bar.
NOTE: The last selected toolbar button remains selected until the Esc key is
pressed or the arrow button is selected.
Representation
Elements of the Toolbar
Number Description
1 Select Mode (Esc) (see page 69)
2 Normally open contact (F3) (see page 78)
3 Normally closed contact (Shift+F3) (see page 78)
4 Positive transition-sensing contact (Ctrl+F3) (see page 78)
5 Negative transition-sensing contact (Ctrl+Shift+F3) (see page 78)
6 Coil (F5) (see page 87)
7 Latched coil (Shift+F5) (see page 87)
8 Boolean Connection (F7) (see page 100)
9 Vertical Connection (Shift+F7) (see page 100)
10 Boolean Link (Alt+F6) (see page 100)
11 Data Selection (Ctrl+D) (see Unity Pro, Operating Modes)
12 FFB Input Assistant (Ctrl+I) (see Unity Pro, Operating Modes)
13 Type Library Browser (Alt+3) (see Unity Pro, Operating Modes)
14 Equation Network block (see page 106)
15 Comment (F8) (see page 119)
16 Inspect Window (F9) (see Unity Pro, Operating Modes)
24 EIO0000000549 07/2012
Customizing the Toolbar
To customize the toolbar open the Customize dialog via Tools Customize
Toolbars and for example drag a function block button from the LL984 Instruction
Bar to the toolbar.
The customized toolbar is saved with the project.
Please also refer to the general toolbar features (see Unity Pro, Operating Modes).
LL984 Instruction Bar
The LL984 Instruction Bar provides the LL984 function blocks.
Use the LL984 Instruction Bar button in the toolbar to show/hide the instruction
bar.
To display the function blocks of the EMTH and PCFL families, click the respective
button with an arrow in the lower right corner.
Clicking such a button opens a sub-toolbar containing the function blocks of the
family.
You can drag and dock the instruction bar anywhere you like.
The position of the instruction bar is saved with the project, which means next time
opening the project will restore the toolbar position.
17 Subroutine buttons (JSR, LAB, RET) (see page 117)
JSR (Jump Subroutine)
LAB (Label the starting point of a Subroutine)
RET (Return from Subroutine)
18 ADD, SUB, MUL, DIV
Here you can directly select frequently used function blocks L9_ADD, L9_SUB,
L9_MUL, L9_DI V.
19 Change View Mode (Ctrl+W) (see page 66)
20 LL984 Instruction Bar (see section below.
Number Description
EIO0000000549 07/2012 25
Using Menus or Context Menu
You can activate the features provided by the toolbar also via the Edit menu or using
the context menu of the LL984 Editor (right-click with the mouse).
26 EIO0000000549 07/2012
General Restrictions
Introduction
For Unity Pro with LL984 Editor compared to legacy LL984 applications the
restrictions described below apply.
Memory Addresses
The following memory address are used in Unity Pro:
No Debugging Support
The Unity Pro LL984 Editor does not provide debugging support. Only the IEC
languages (FBD, LD, SFC, ST, IL) provide debugging features.
Segment Scheduling
Segment scheduling is managed by the order of sections programmed in the MAST
task.
Unity Pro with LL984 Editor does not support executing 1 segment several times
during a PLC scan, which was possible with legacy LL984 applications.
The Cont r ol contact state can only be an On state to solve. Legacy LL984
applications allowed an option of On or Of f to solve the segment.
Unity Pro does not support the Reset WDT setting.
Unity Pro does not support inverted condition variables neither for segments nor
for networks.
If an I/O drop is associated with a logic segment without any logic programmed the
segment is not created and therefore the associated I/O is not solved. Drops without
logic must be explicitly set to scan associated I/Os.
Review the segment scheduler and logic segmentation and after the conversion add
sections to the MAST task with the proper Remote I/O drop added that needs to be
solved for the application.
For Modicon M340 target applications I/O scheduling is not possible from the
segment. The MAST task updates the I/O modules.
Unity Pro Legacy LL984 Application
%M (memory bit) 0x
%I (discrete input) 1x
%IW (input word) 3x
%MW (memory word) 4x
EIO0000000549 07/2012 27
Segments not in the right order after import of a ProWORX application
In case there is one or more segments, which are not marked for execution in the
LL984 segment scheduler, the import will place the first of these segments as first
LL984 segment in Mast Task segment tree.
The segments/sections are scanned in the order displayed in the Project Browser.
As this wrong placed segment has a condition LL984_Segment _Not Sol ved, this
segment will not be scanned.
If the segment condition is removed, the segment must also be placed in the correct
place in the Mast Task segment tree, to get correct execution order.
Segments/networks programmed but not listed in the segment scheduler are
not imported.
All Segments which are disabled in LL984 segment scheduler are not scanned
in Unity Pro.
Such segments are connected to a common variable, initialized at 0 named
LL984_Segment _Not Sol ved.
To enable one or several segments, condition variable in the segment properties
window must be deleted.
Import log file has an incorrect message - Negative segment conditions are
not supported....
A wrong message may appear in the import log file after an import of a Concept *.asc
file: Negat i ve segment condi t i ons ar e not suppor t ed. Segment
condi t i on must be adapt ed i n Segment xx.
This happens in case where a previously conditionally executed segment, was set
to continuously before the Concept project was exported into a *.asc file.
As the import of the continuously state is correct, there is no more action necessary.
Interrupt Handling
Unity Pro does not support interrupt handling with LL984 subroutines.
That means applications with the I TMR function and those that use the HLI 340
interrupt module with the I MOD instruction will need to be modified so that they make
use of standard Unity Pro interrupt handling with I/O events.
If the original LL984 application contains an I MOD FFB programmed to service
interrupts for the HLI input module, the LL984 subroutine sections will be imported
into the Unity Pro application in the SR section of the MAST task. But they will not
be operational with interrupt handling. In Unity Pro, the HLI I/O points that are
configured as interrupts are linked to I/O events in the Events section. The LL984
subroutine program will have to be programmed (in one of the IEC languages) in the
appropriate I/O EVT section.
28 EIO0000000549 07/2012
Once completed, the SR sections that were imported into the MAST task need to be
deleted.
Please also refer to Calling Subroutines (see page 117).
Online Changes
Online changes in Unity Pro is not unlimited.
A message will be generated, if a certain percentage (e.g. 75%) of the available
Build Build Changes memory is already used.
The LL984 Editor of Unity Pro does not allow "direct" changes of code like in legacy
LL984 systems.
A change performed online in an LL984 network will lead to a modification of the
network and needs to be confirmed and downloaded by Build Build Changes.
Forcing
In legacy LL984 applications forced bits remain in their state after a cold start.
In Unity Pro forced bits are reset on cold start.
Non-latched/Latched Coil Restrictions
For non-latched/latched coil restrictions please refer to Selecting Coils
(see page 87).
State Flow / Power Flow
Legacy LL984 applications provide switching between State Flow and Power Flow
view.
Unity Pro only provides 1 view (Power Flow). Therefore no switching to State Flow
is available.
Extended Memory
Unity Pro Quantum PLCs do not support SCADA packages that use Quantum
extended memory reads and writes (Modbus FC0x14 and FC0x15).
Extended memory data from a legacy Quantum LL984 application will be moved to
a Unity Pro defined variable location.
MMF (Modicon Motion Framework)
Unity Pro does not support the MMF (library of motion function blocks, loadable).
EIO0000000549 07/2012 29
Modsoft SFC
Modsoft SFC and Modsoft macros will neither be converted to nor supported by
Unity Pro.
Not Supported Legacy LL984 Instructions
For legacy LL984 instructions that are not supported by Unity Pro please refer to Not
Implemented Function Blocks (see Unity Pro, Original LL984, Block Library).
If the imported LL984 Ladder Logic application contains unsupported LL984 logic
instructions or user loadables, proceed as described under Not Supported Legacy
LL984 Instructions and User Loadables (see page 188).
Function Blocks
L9_IMIO, No error code 16#2003 in case of IOFUN=3
When using the immediate I/O function block (L9_I MI O) with parameter I OFUN=3
(combined input and output operation) with a none-bidirectional I/O module there is
no error-code 16#2003 reported.
EMTH FFBs: Results and error-code different between legacy LL984 and
Unity Pro LL984
When using EMTH FFBs (L9E_. . . ) with very small floating point values or with
val ue=NAN/ I NF the result of the operation or the error code retrieved by the EMTH
L9E_ERLOG FFB may differ between legacy LL984 and Unity Pro LL984.
Examples:
If the input value of L9E_SI NE is 1. 363573E- 36, the L9E_ERLOG FFB in
ProWORX32 reports the error code 1A01 (FP Under f l ow), while in Unity Pro
LL984 there is no error code reported. In Unity Pro LL984 the Under f l ow
er r or is reported if the input value is 1. 175E- 38.
If you compare the FP values 9. 18E- 41 and 0. 0 using the L9E_CMPFP function
block, the result in legacy LL984 is Equal and in Unity Pro LL984 the result is
Gr eat er .
If the input value of the L9E_SQRFP (square root) FFB is +NAN, the error code
retrieved by the EMTH L9E_ERLOG FFB in Unity Pro is 16#1704 (FP val ue
i nval i d), while in legacy LL984 the error code is 16#1702 (FP Over f l ow).
30 EIO0000000549 07/2012
PCFL FFBs: Different results between legacy LL984 and Unity Pro LL984
The calculation of the formula ( A*B*C) / D in the L9P_CALC FFB delivers different
results in legacy LL984 and in Unity Pro LL984 in case of A=1. 0 and
B=C=D=9. 18E- 41. In Unity Pro LL984 the result is 0. 0 and in legacy LL984 the
result is 9. 18E- 41.
XMIT, Not pr esent i n Li br ar y error. Opcode must be changed to 1F
L9_XMI T now is offered as an EFB always available, while legacy LL984 projects
know it as a loadable. Opcode is no more needed and must be set to 1F before
importing application to Unity Pro.
L9_ID and L9_IE function blocks do not disable/ enable the ITCNTRL when set
in Mode 3
With the L9_I D/L9_I E function block you can mask/unmask interrupts. The
parameter I NT_TYPE specifies the type of operation:
I NT_TYPE=1
A global interrupt masking is performed, that means all I/O and timer interrupts
are masked (L9_I D) or unmasked (L9_I E). Masking of interrupts can be done
for a series of PLC scans. The masking starts when the L9_I D block is executed
and it ends when the L9_I E block is executed. The L9_I D/L9_I E block with
I NT_TYPE=1 has the same effect as the IEC function block
MASKEVT/ UNMASKEVT.
I NT_TYPE=2
Not supported in Unity Pro LL984.
I NT_TYPE=3
Only timer interrupts are masked/unmasked. This mode can be used to protect a
short sequence of code in your application from being interrupted by a timer
event. You cannot disable timer interrupts for several PLC scans. The
L9_I D/L9_I E function block with I NT_TYPE=3 has the same effect as the IEC
function block I TCNTRL with parameter ENABLE=Fal se (L9_I D) or
Enabl e=Tr ue (L9_I E) and EVENT=1. . 32.
EIO0000000549 07/2012 31
3
LL984 Editor
Accessing Tasks and Sections
EIO0000000549 07/2012
Overview
Accessing Sections
This chapter describes the specifics added in Project Browser in order to support
LL984 segments and networks.
For standard features please refer to Accessing Sections (see Unity Pro, Operating
Modes).
Accessing Tasks
For information on how to create and modify program tasks please refer to Access
to Tasks (see Unity Pro, Operating Modes).
Topic Page
Creating LL984 Segments and Networks 32
Modifying LL984 Segment Properties 36
Modifying LL984 Network Properties 38
Scheduling LL984 Segments and Network 40
Deleting, Cutting, Copying and Pasting LL984 Segments and Network 41
32 EIO0000000549 07/2012
Creating LL984 Segments and Networks
Introduction
The logic of LL984 is programmed in networks.
Several networks are grouped in segments.
Each network contains a matrix of 7 rows and 11 columns, where you can place
contacts, coils, function blocks etc.
At the beginning of each segments code execution the inputs of a RIO drop can be
read and at the end the outputs of the same or another RIO drop can be written.
Recommendations
It is recommended not to use more than 64 segments and 5,000 networks in an
application.
Restrictions
For creating LL984 segments and networks the following rules apply:
LL984 segments can only be created when the Ladder Logic 984 (LL984)
project setting is activated via Tools Project Settings Program
Languages.
LL984 segments can only be created in the MAST task of the application, they
are not allowed in the FAST and AUX tasks.
Only one LL984 segment can be created inside the subroutine (SR Sections)
node of the MAST task.
LL984 segments can not be created under Timer Events or I/O Events nodes.
LL984 segments can not be created in DFBs.
For action and transition sections in SFC, LL984 is not allowed as language.
Only ST, IL, FBD and LD are allowed as language.
LL984 segments and sections with Unity Pro IEC languages can be mixed inside
the Sections node of the MAST task. The same is valid inside the subroutine (SR
Sections) node of the MAST task.
LL984 networks can only be created as children of LL984 segments.
Only LL984 networks are allowed as children of LL984 segments, no sections
with IEC languages can be created there.
EIO0000000549 07/2012 33
Creating a Segment
Creating a Network
Step Action
1 Left-click the Sections directory of the MAST task, or place the cursor using the
arrow keys on this directory.
2 Click the right mouse button or use Shift+F10 to select New Section in the context
menu.
Result: The properties dialog for the segment is opened.
3 Enter the section (segment) name.
The section (segment) name must be unique in the entire project and conform to the
general naming conventions of Unity Pro.
4 Select LL984 Segment as programming Language of the segment.
5 Select the functional module to which the segment is attached from the
Localization tab if necessary.
Also refer to Functional modules (see Unity Pro, Operating Modes).
6 Define a boolean variable in the Condition tab with which the segment can be
activated/deactivated (segment active when variable=1) if required.
You have the following options to select variables:
Enter the name of the variable/address directly or copy it from the clipboard.
Use the ... button to open a Data Selection dialog.
7 Only applies to Quantum projects:
Assign a read RIO drop and a write RIO drop to the segment in the Remote IO tab
if required.
8 Enter a comment in the Comment tab if desired (max. 1024 characters).
9 If you wish to create additional segments, confirm the entries with Apply. In this
case, the dialog will remain open and you can generate additional segments.
If you do not wish to create additional segments, confirm the entries with OK. In this
case, the dialog will close and the generated segment is displayed as the last
element in the Sections directory.
NOTE: The position of sections and segments inside the Structural view matches
exactly the execution sequence and can be changed via drag-and-drop.
Step Action
1 Left-click an LL984 Segment in the Sections directory of the MAST task, or place
the cursor using the arrow keys on this directory.
2 Click the right mouse button or use Shift+F10 to select New 984 Network in the
context menu.
Result: The properties dialog for the network is opened.
3 Enter the network name.
The network name must be unique in the entire project and conform to the general
naming conventions of Unity Pro.
34 EIO0000000549 07/2012
A new network is normally inserted as the last element in the LL984 Segment
directory.
To insert a new network directly before a selected network use Insert Network
from the context menu.
Creating a Network for Subroutines
4 LL984 Network is preselected for the Language of the network and can not be
changed.
5 Define a boolean variable in the Condition tab with which the segment can be
activated/deactivated (segment active when variable=1) if required.
You have the following options to select variables:
Enter the name of the variable/address directly or copy it from the clipboard.
Use the command button ...to open a Data Selection dialog.
6 Enter a comment in the Comment tab if desired.
7 Confirm the entries with OK. The dialog will close and the generated network is
displayed as the last element in the LL984 Segment directory.
NOTE: The position of networks inside the Structural view matches exactly the
execution sequence and can be changed via drag-and-drop.
Step Action
Step Action
1 Left-click the SR Sections directory of the MAST task, or place the cursor using the
arrow keys on this directory.
2 Click the right mouse button or use Shift+F10 to select New SR Section in the
context menu.
Result: The properties dialog for the SR section (LL984 Segment) is opened.
3 Enter the SR section (LL984 segment) name.
The SR section (LL984 Segment) name must be unique in the entire project and
conform to the general naming conventions of Unity Pro.
4 Select LL984 Segment as programming Language of the segment.
NOTE: There can be only 1 LL984 SR segment in a project. So when there is
already 1 existing you can no longer select LL984 Segment as programming
Language for a new SR section.
5 Enter a comment in the Comment tab if desired (max. 1024 characters).
6 Confirm the entries with OK. The dialog will close and the generated LL984
segment is displayed in the SR Section directory.
7 Left-click the LL984 Segment in the SR Sections directory of the MAST task, or
place the cursor using the arrow keys on this directory.
8 Click the right mouse button or use Shift+F10 to select New 984 Network in the
context menu.
Result: The properties dialog for the network is opened.
EIO0000000549 07/2012 35
Displaying or Modifying Segment/Network Properties
Exporting/Importing Segments/Networks
Please refer to Exporting/Importing LL984 Segments/Networks (see page 193).
9 Enter the network name.
The network name must be unique in the entire project and conform to the general
naming conventions of Unity Pro.
10 LL984 Network is preselected for the Language of the network and can not be
changed.
11 Enter a comment in the Comment tab if desired.
12 Confirm the entries with OK. Tthe dialog will close and the generated network is
displayed as the last element in the LL984 Segment directory.
NOTE: The position of networks inside the Structural view matches exactly the
execution sequence and can be changed via drag-and-drop.
Step Action
Step Action
1 Left-click on the desired segment/network, or place the cursor on this
section/network with the arrow keys.
2 Click the right mouse button or use Shift+F10 to select Properties in the context
menu.
Result: The Properties dialog for is opened.
3 Implement the desired changes.
4 Confirm all entries with OK.
36 EIO0000000549 07/2012
Modifying LL984 Segment Properties
Introduction
This section describes the specifics of the LL984 Editor referring to modifying LL984
segment properties.
Modes).
Protection
The Protection property is not available at the moment.
Localization
You can only attach LL984 segments to a functional module and not LL984
networks. The networks of a segment are implicitly attached to the functional module
of their segment.
You can attach an LL984 segment to a functional module either in the Localization
tab of its properties dialog or in the Project Browser via drag-and-drop from the
Structural View to the Functional View.
You can detach an LL984 segment from a functional module either in the
Localization tab of its properties dialog or by selecting Detach from the segments
context menu.
Condition
You can modify the Condition of an LL984 segment in the Condition tab of its
properties dialog.
When you configure a boolean variable in this tab, the state of this variable is
checked at the beginning of the LL984 segments code execution.
When the variables state is 0, the segment and all its networks are not executed.
When the variables state is 1 or when no condition variable is defined for the
segment, it depends on the condition variables of the networks whether the
networks are executed or not.
EIO0000000549 07/2012 37
Remote I/O
You can synchronize the Remote I/Os of an LL984 segment in the Remote I/O tab
of its properties dialog.
Here you can configure which Remote Quantum drop is read before and which one
is written after execution of the LL984 segment.
Drops which are not yet configured are displayed in red inside the list box.
Not configured drops can be selected here, but when they are not configured before
next Build, the build will not be successful and a diagnostic message will be
displayed.
NOTE: This property is only available for Quantum projects.
Comment
You can enter a comment to an LL984 segment in the Comment tab of its properties
dialog.
The maximum size of a comment is 1024 characters.
The LL984 Subroutine Segment
You can only have 1 LL984 segment under the SR sections node of the MAST task.
The properties dialog of this LL984 subroutine segment only provides the General
and the Comments tabs.
The Is called check book in the General tab is greyed and not checked.
This is done because in LL984, subroutines can be called via a memory word and
so you only know at run time whether a subroutine is called or not.
You can not define a condition variable for the LL984 subroutine segment.
38 EIO0000000549 07/2012
Modifying LL984 Network Properties
Introduction
This section describes the specifics of the LL984 Editor referring to modifying LL984
network properties.
Modes).
Protection
The Protection property is not available at the moment.
Localization
You can only attach an LL984 segment to a functional modules. The networks of a
segment are implicitly attached to the functional module of their segment.
Condition
You can modify the Condition of an LL984 network in the Condition tab of its
properties dialog.
When you configure a boolean variable in this tab, the state of this variable is
checked at the beginning of the LL984 networks code execution.
When the variables state is 0, the variable and its networks are not executed.
When the variables state is 1 or when no condition variable is defined for the
network, it depends on the condition variables of the networks whether the networks
are executed or not.
You can define a condition variable for each network.
NOTE: Condition variables do not have influence on the execution of an L9_SKP
block, that means when you have a skip over 4 networks, you skip the remainder of
the current network and the next 3 networks independent of their condition variables.
Remote I/O
You can synchronize the Remote I/Os only for LL984 segments and not for LL984
networks.
Comment
You can enter a comment to an LL984 network in the Comment tab of its properties
dialog.
The maximum size of a comment is 1024 characters.
EIO0000000549 07/2012 39
User Directory/Hyperlink
For LL984 networks you can add hyperlinks by selecting Add Hyperlink from the
networks context menu.
For details please refer to chapter Hyperlinks (see Unity Pro, Operating Modes).
You can not add user directories to LL984 networks.
LL984 Networks in Subroutine Segments
The properties dialog of an LL984 network in a subroutine (SR) segment only
provides the General and the Comments tabs.
The Is called check box in the General tab is greyed and not checked, because in
LL984 subroutines can be called via a memory word and so you only know at run
time whether a subroutine is called or not.
You can not define a condition variable for an LL984 network in a subroutine (SR)
segment.
40 EIO0000000549 07/2012
Scheduling LL984 Segments and Network
Introduction
Sections and LL984 segments (and also LL984 networks inside segments) are
executed in the sequence in which they are displayed in the Structural View of the
Project Browser.
To change this sequence, you can drag-and-drop sections, LL984 segments or
LL984 networks inside the Structural View.
Restrictions
For dragging-and-dropping LL984 segments and networks the following rules apply:
Sections (ST, LD, ) can not be dropped into LL984 segments.
LL984 segments can not be dropped into other LL984 segments.
LL984 networks can only be dropped into LL984 segments.
LL984 networks can be dropped into the LL984 subroutine segment under the SR
Sections) node of the MAST task.
After dropping the networks, they are re-analyzed latest during next Build,
because e.g. L9_LAB function blocks are only allowed in networks of the LL984
segment in the SR Sections node.
When an LL984 network has an activation condition and is dragged-and-dropped
into the LL984 subroutine segment, the LL984 network loses its activation
condition because subroutine networks do not have activation conditions.
Drag-and Drop Between Applications
You can not drag-and drop LL984 segments and networks from one Unity Pro
application to another.
To copy sections between applications you have to use the import/export feature of
Unity Pro.
EIO0000000549 07/2012 41
Deleting, Cutting, Copying and Pasting LL984 Segments and Network
Deleting LL984 Segments and Networks
You can delete LL984 segments and networks in the Structural View of the Project
Browser.
To delete an LL984 segment or network either select Delete from its context menu
or press the DEL key.
If you want to delete an LL984 segment, a message is displayed that all its networks
will be deleted, too.
You have to confirm this message to delete the LL984 segment.
Cutting, Copying and Pasting
You can not cut, copy and paste LL984 segments and networks in a Unity Pro
application.
Alternatively you can use the import/export feature on segment or network level.
42 EIO0000000549 07/2012
EIO0000000549 07/2012 43
4
LL984 Editor
Unity Pro Software Options
EIO0000000549 07/2012
Overview
This chapter describes the specifics of the LL984 Editor referring to Unity Pro
software options.
For standard features please refer to Unity Pro Software Options (see Unity Pro,
Operating Modes).
This chapter contains the following sections:
Section Topic Page
4.1 Project Settings 44
4.2 Options 48
44 EIO0000000549 07/2012
4.1 Project Settings
Program
Overview
This chapter describes the specifics of the LL984 Editor referring to Unity Pro project
settings (Tools Project Settings).
For standard features please refer to Project Settings (see Unity Pro, Operating
Modes).
Introduction
This projects configuration settings can be accessed via Tools Project Settings
Program. It contains FBD, LD, SFC, ST and LL984 settings.
As with other Unity Pro project settings, the LL984 specific project settings are also
stored as part of the application.
Representation
Appearance of the Languages settings
EIO0000000549 07/2012 45
Items of the Languages Settings
NOTE:
For modifying the Ladder Logic (LL984) setting the following restrictions apply:
This setting is disabled for applications using Quantum Safety PLCs, as LL984
segments and networks can only be created for non-safety applications.
To modify this setting you have to go offline.
Item of the LL984 Setting
This LL984 setting is enabled only, if the LL984 library setup was installed.
NOTE: Modifying this setting causes a re-analysis of the LL984 networks. This is
also possible in the online mode.
Items of the Network Display Settings
NOTE: Modifying the Column Width setting does not cause a new Build.
Item Description
Function Block Diagram
(FBD)
When these check boxes are checked, the respective
languages can be used in your project.
Ladder (LD)
Sequential Function Chart
(SFC)
List (IL)
Structured Text (ST)
Ladder Logic (LL984) When this check box is checked, the LL984 language can
be used in your project.
Item Description
SKP enabled When this check box is checked, the L9_SKP function block
can be used in your project.
Item Description
Printing View Using this list you select view1 to view4 defined under items View 1 to
View 4 (see below).
The default view is view4.
The view you select for the Printing View setting is used for printing the
LL984 networks.
Column Width Using this field you can enter the column width as a floating point value (1.0
to 3.0).
For example a value of 3.0 means a 3 times larger column width.
The default width is 1.0.
46 EIO0000000549 07/2012
Items of the View 1 to View 4 Settings
The LL984 Editor can display various information concerning variables attached to
coils, contacts and function block nodes.
According to the settings for View 1 to View 4 the LL984 Editor displays the
following information:
address (e.g., %M100)
984-address (e.g., 400100)
variable name
variable comment
descriptors 1 to 9
topological address
You can switch between the different views defined using CTRL+W or using the
Change View Mode button.
Default settings for View 1 to View 4
Item Description
Line 1
...
Line 7
For each line, you can select which information should be shown:
blank
address
984-address
variable
comment
descriptor 1 to descriptor 9
topological address
Max characters per cell
width
Defines the maximum number of characters visible in one cell (5
to 32). Increasing this value leads to a smaller font size and vice
versa.
The default is 10 characters.
NOTE: A high values (for example 32) may lead to a very small
(unreadable) font size, but such a value makes sense when used
in conjunction with a larger Column Width setting (like 2.0 or
3.0).
Setting View 1 View 2 View 3 View 4
Line 1 blank blank blank blank
Line 5 blank blank blank comment
Line 6 blank variable 984-address variable
EIO0000000549 07/2012 47
NOTE:
For the View 1 to View 4 settings the following restrictions apply:
If the value variable is selected in consecutive lines (for example Line 1 and
Line 2) the variable name is broken into n lines, if it is longer than the cell width.
If the value variable is selected, for example, for Line 1 and Line 3 and if for
Line 2 any other value is selected, the variable name is truncated at the end of
Line 1 and is not broken into Line 3.
Line 3 starts with the first character of the variable name again.
If the value comment is selected in consecutive lines (for example Line 1 -
Line 3) the variable comment is broken into n lines, if it is longer than the cell
width.
If the value comment is selected, for example, for Line 1 and Line 3 and if for
Line 2 any other value is selected, the variable comment is truncated at the end
of Line 1 and is not broken into Line 3.
Line 3 starts with the first character of the variable comment again.
If all 7 lines are configured as blank, the LL984 Editor displays the variable name
in Line 7 automatically.
Max characters per cell width
The calculated font height is applied for all kinds of displayed information
(address, variable, comment etc.).
Blank lines at the top are not displayed. Blank lines in the middle or at the bottom
are displayed as empty lines.
Line 7 address address address address
Max characters per cell width 10 10 10 10
Setting View 1 View 2 View 3 View 4
48 EIO0000000549 07/2012
4.2 Options
Data and Languages
Overview
This chapter describes the specifics of the LL984 Editor referring to Unity Pro
options (Tools Options).
For standard features please refer to Options (see Unity Pro, Operating Modes).
Introduction
This configuration section can be accessed via Tools Options Data and
Languages. It contains settings for entering data.
For standard features please refer to Data and Languages (see Unity Pro,
Operating Modes).
Representation
LL984 options
EIO0000000549 07/2012 49
Items of the LL984 Options
NOTE: For modifying the settings mentioned above, the following restrictions apply:
Modifying the Show latched coils as setting will lead to a refresh of the editor
window of the opened LL984 networks.
Modifying the Reuse 984 editor window when network is opened setting will
only take effect next time an LL984 editor is opened.
Item of the Mnemonics Options
Under LL984 Mnemonics the Property label column lists the contacts and coils
and an assortment of functions blocks available for LL984 networks.
In the Property value column you can enter a mnemonic for each listed element.
A mnemonic can consist of up to 4 alphanumeric signs.
Using Mnemonics
As you start typing text, while the current cell marker is on an empty cell in the
LL9894 editor, a small edit box opens in the editor.
Entering a mnemonic (first key typed will be taken over into the edit box) and
pressing the ENTER key will insert the corresponding LL984 element at the current
cell.
If the cells needed to insert the element are already occupied, a message box will
inform you and the element will not be inserted.
Item Description
Show latched coil as Using this list you can select which letter (L or M) will be
displayed inside a latched coil.
The default letter that will be displayed is an L.
Reuse 984 editor window
when network is opened
If this check box is checked only 1 window is used for Open
commands on LL984 networks.
If this check box is not checked, for each Open command on an
LL984 network, a new window is opened.
50 EIO0000000549 07/2012
EIO0000000549 07/2012 51
5
LL984 Editor
Common Functions for Graphical Languages
EIO0000000549 07/2012
Common Functions for Graphical
Languages
Using Bookmarks in Graphical Languages Sections
Introduction
Bookmarks are used to mark positions in the margin (gray column on the left edge
of the section/network) and allow the marked positions to be easily found in different
language sections/networks.
You can navigate through a list of bookmarks, displayed in the Tools Bookmarks
dialog.
An example of a bookmark in SFC:
The current bookmark is indicated using a horizontal arrow ( ).
Bookmark are displayed in different colors.
Created Enabled/Disabled Color
manually enabled blue
manually disabled light gray
automatically enabled gray
automatically disabled light gray
52 EIO0000000549 07/2012
Setting Bookmarks
You have the following options to set a bookmark:
Execute the command Edit Bookmarks > Toggle Bookmark. (There must
not be any current bookmark in the selected area).
The bookmark is inserted in the margin (gray column on the left edge of the
section/network) and is marked as the current bookmark.
Press the Ctrl+F2 key combination. (There must not be any current bookmark in
the selected area).
The bookmark is inserted in the margin (gray column on the left edge of the
section/network) and is marked as the current bookmark.
or
Place the mouse pointer in the margin (gray column on the left edge of the
section/network) at the position to be marked and use Toggle Bookmark from
the context menu for the margin (right mouse click).
The bookmark is inserted at the mouse pointer and marked as the current
bookmark.
Removing Single Bookmarks
You have the following options to remove a bookmark:
Select the bookmark to be deleted as the current bookmark (e.g. with Next
Bookmark) and use the Edit Bookmark > Toggle Bookmark command.
Select the bookmark to be deleted as the current bookmark (e.g. with Next
Bookmark) and press the Ctrl+F2 key combination.
or
Place the mouse pointer on the bookmark to be removed and use Toggle
Bookmark from the context menu of the bookmark (right mouse click).
You can also remove a bookmark using the context menu of the Bookmarks
dialog.
Removing All bookmarks
You have the following options to remove all bookmarks in the current
section/network:
Use the Edit Bookmark> Clear all Bookmarks menu command.
or
Press the Ctrl+Shift+F2 key combination.
You can also remove all bookmarks using the context menu of the Bookmarks
dialog.
EIO0000000549 07/2012 53
Searching for Bookmarks (Search Down)
You have the following options to search for bookmarks (search down):
Use the Edit Bookmark> Next Bookmark menu command.
Use the Edit Go to Bookmark Next menu command.
or
Press the F2 key.
If a current bookmark is selected, a jump is made to the next one and it is marked
as the current bookmark.
The bookmarks are traversed according to their order of appearance in the
Bookmarks dialog.
Searching for Bookmarks (Search Up)
You have the following options to search for bookmarks (search up):
Use the Edit Bookmark> Previous Bookmark menu command.
Use the Edit Go to Bookmark Previous menu command.
or
Press the Shift+F2 key combination.
If a current bookmark is selected, a jump is made to the previous one and it is
marked as the current bookmark.
The bookmarks are traversed according to their order of appearance in the
Bookmarks dialog.
Bookmarks Dialog
To open the bookmarks dialog use Tools Bookmarks.
A list of the projects bookmarks is displayed in the Bookmarks dialog.
54 EIO0000000549 07/2012
Creating bookmarks is done in the language editors.
Deleting and renaming bookmarks can be done in the Bookmarks dialog, too.
NOTE: Renaming of bookmarks can only be done with created bookmarks.
Automatically created bookmarks can not be renamed.
Bookmark Commands in Language Editors
The bookmark commands in language editors affect the Bookmarks dialog as
follows:
Toggle Bookmark creates a bookmark, visible also in the Bookmarks dialog.
It will be appended to the list of bookmarks.
Next Bookmark jumps to the next bookmark in the list of bookmarks
Previous Bookmark jumps to the previous bookmark in the list of bookmarks.
Delete Bookmark deletes the selected bookmark.
Delete all Bookmarks deletes only the bookmarks inside the current
section/network.
NOTE: The Bookmark tab of the Edit Go To dialog only displays the bookmarks
of the current section.
Naming Bookmarks
Created bookmarks are named as Bookmark1, Bookmark2 and so on.
In the Bookmarks dialog you can rename the bookmarks.
Element Description
Bookmark column List of the projects bookmarks. Automatically created bookmarks
(see below) are displayed in gray and can not be renamed.
Location column Location of the bookmark (section, network or DFB) referring to the
Project Browser.
Line column Line in the section/network where the bookmark is located.
check boxes in the
Bookmark column
Activate this check box to be able to jump to this bookmark by
means of Next Bookmark/Previous Bookmark.
By default for newly created bookmarks the check box is activated.
Delete/Delete all Right click in the dialog and select from the context menu:
Delete: to delete the selected bookmark
Delete all: to delete all bookmarks in the project
EIO0000000549 07/2012 55
Automatically Created Bookmarks
Automatically created bookmarks are named as Search<Search String>.
Automatically created bookmarks are displayed in gray and can not be renamed.
The maximum number of automatically created bookmarks is 30.
Automatic creation of another bookmark will insert the new bookmark as the first one
in the bookmark list and will delete the bookmark at the end.
For automatically created bookmarks please refer to Tracing Variables / Addresses
(see page 138).
Navigating to Bookmarks
In the Bookmarks dialog double-click a line in the list of bookmarks to open the
respective section/network with the selected bookmark.
If the check box in front of a bookmark line is not activated, you can not jump to this
bookmark by means of Next Bookmark/Previous Bookmark.
Saving Bookmarks
Bookmarks are saved with your application.
Deleting Bookmarked Lines
If you delete a section/network or a bookmarked line in a section/network, the
corresponding bookmarks are deleted, too.
Undo will not restore the bookmarks.
56 EIO0000000549 07/2012
EIO0000000549 07/2012 57
6
LL984 Editor
LL984 Editor
EIO0000000549 07/2012
LL984 Editor
Overview
This chapter describes the specifics of the LL984 Editor.
Section Topic Page
6.1 Creating a Program with LL984 Programming Language 58
6.2 Editing Contacts 77
6.3 Editing Coils 86
6.4 Editing Function Blocks 95
6.5 Editing Links 99
6.6 Editing Equation Network Blocks 105
6.7 Assigning Variables to LL984 Objects 113
6.8 Calling Subroutines 117
6.9 Entering Comments 119
LL984 Editor
58 EIO0000000549 07/2012
6.1 Creating a Program with LL984 Programming
Language
Overview
This section describes the basics for creating a program in the LL984 programming
language.
What Is in This Section?
This section contains the following topics:
Topic Page
Project Settings for LL984 Programs 59
Creating an LL984 Program 60
Syntax and Semantics Check During Programming 63
Network Display 66
Navigating with the Keyboard 67
Selecting Objects 69
Deleting, Cutting, Copying, Pasting and Moving Objects 71
Displaying the Properties 74
Inserting and Deleting Rows/Columns 75
LL984 Editor
EIO0000000549 07/2012 59
Project Settings for LL984 Programs
Introduction
Before creating an LL984 program, you should activate the following project
settings:
Ladder Logic 984 (LL984)
(Project Settings Program Languages)
To be able to create LL984 sections and networks.
Allow dynamic arrays (ANY_ARRAY_XXX)
(Project Settings Variables)
To be able to use dynamic arrays with the LL984 function blocks.
LL984 Editor
60 EIO0000000549 07/2012
Creating an LL984 Program
Introduction
The LL984 Editor window is made up of cells and 1 object can be placed in each
one. The cells are separated visually using a grid which can be switched off (View
Grid).
Creating an LL984 Program with the Mouse
Process the following steps to create an LL984 program with the mouse:
Step Action
1 Create an LL984 network. (see page 32)
2 Select the desired object using:
the menu commands in the Edit New <Object> menu
or
the symbols for the objects in the toolbar
Result: The mouse pointer indicates the selected object (placement mode).
3 Click the target cells in the LL984 section.
Result: The selected object is inserted and the selection mode is active again.
Example:
Return to selection mode by clicking the symbol or pressing the ESC key.
4 To enter the respective actual parameters (variable/address), double-click the
object.
Result: The properties dialog box for the object is opened.
Example:
LL984 Editor
EIO0000000549 07/2012 61
Creating an LL984 Program with the Keyboard
Process the following steps to create an LL984 program with the keyboard:
5 Enter the desired actual parameter and a comment (if required) and confirm the
entries with OK.
Result: The names of the associated variables are displayed above the object.
NOTE: Entering a binary address opens the Create variable dialog. By this you
can create a variable associated with the entered address.
6 Repeat these steps until all objects are entered.
Step Action
Step Action
1 Create an LL984 network. (see page 32)
2 Using the keyboard, place the field with the gray background on the cell where the
object should be inserted.
3 Select the desired object using the function keys for the objects.
Result: The cursor symbol indicates the selected object.
4 Confirm the selection using the ENTER key.
Result: The selected object is inserted into the cell with the gray background and
the gray field is automatically shifted to the next cell.
Example:
To return to selection mode, press the ESC key.
5 To enter the respective actual parameters (variable/address), use the Properties
menu command from the shortcut menu.
Result: The properties dialog box for the object is opened.
Example:
LL984 Editor
62 EIO0000000549 07/2012
6 Enter the desired actual parameter and a comment (if required) and confirm the
entries with OK.
Result: The names of the associated variables are displayed above the object.
NOTE: Entering a binary address opens the Create variable dialog. By this you
can create a variable associated with the entered address.
7 Repeat these steps until all objects are entered.
Step Action
LL984 Editor
EIO0000000549 07/2012 63
Syntax and Semantics Check During Programming
Introduction
Syntax and semantics check is performed directly when creating the program.
The result of this check is displayed in 3 formats:
Directly in the program section with colored objects or texts.
As tooltip if the cursor is placed on an incorrect object.
In the output window, if Build Analyze is selected.
NOTE: Warnings are not visualized in the program section.
Colors of Objects/Texts
Tooltips
If the cursor is placed over an incorrect object, a tooltip is displayed with a brief
description of the cause of the error/warning.
Messages in the Output Window
Error and warning messages are displayed in the output window after Build
Analyze.
Double-click an error or a warning message in the output window to navigate to the
affected object in the LL984 Editor.
Errors messages in contrast to warning messages must be fixed, because they
inhibit a successful Build.
Color Description
black Syntax and semantics are correct.
blue Possible causes:
Associated variable is not declared.
Data type of the variable does not match the data type of the pin.
Input or output pin not connected.
red wavy line
below text
invalid text. For example, variables which are not declared, variables with
an incorrect data type, etc.
LL984 Editor
64 EIO0000000549 07/2012
Error Messages
The following is a list of example error messages that Analyze will display (E).
Error Message
illegal link
variable %1 must be located
only coils allowed in last column
only one coil per row
FFB type %1 isnt supported
last object in row must be coil
maximum column number allowed is 11
maximum row number allowed is 7
parameter %1 expects constant value
illegal constant value %1: %2
parameter %1 expects variable
unsupported object
dimension of %1 is too small, must be at least %2
dimension of %1 must be %2
variable %1 must be writable
parameter of %1 must be a multiple of %2
parameter of %1 must be a multiple of %2
usage of LL984 language is disabled
usage of SKP instruction is disabled
%1 only allowed in subroutine network
%1 must be in row1/column1
label %1 isnt unique
label %1 doesnt exist
subroutine segment doesnt exist
file %1 is missing
IMC template %1 doesnt exist
Non-latched usage of %1 detected, which is used also as latched
LL984 Editor
EIO0000000549 07/2012 65
Warning Messages
The following is a list of example warning messages that Analyze will display (W).
Tolerated Problems
Analyze will tolerate the following problems.
Warning Message
expression expected (if no actual parameter is assigned to a contact)
variable expected (if no actual parameter is assigned to a coil)
Problem
missing connections (to power rails or other logic elements)
skipping from a subroutine network to a network of another subroutine in the LL984
subroutine segment, if the project setting "SKP enabled" is checked
LL984 Editor
66 EIO0000000549 07/2012
Network Display
Introduction
coils, contacts and function blocks.
This information is displayed above the respective coil, contact or function block
node and can be displayed by tooltip, too.
4 Different Views
You can define 4 different views (View 1 to View 4) via Tools Project Settings
Program LL984 Network Display.
According to the settings for View 1 to View 4 the LL984 Editor will show the
following information:
address (e.g. %M100)
984-address (e.g. 400100)
variable name
variable comment
descriptors 1 to 9
topological address
For detailed information on how to define the different views, please refer to Project
Settings, section Program (see page 44).
View Switching
You can switch between the different views defined, using CTRL+W or using the
Change View Mode button ( ).
The buttons tooltip shows the current view (View 1, 2, 3 or 4.
LL984 Editor
EIO0000000549 07/2012 67
Navigating with the Keyboard
Using the Keyboard
The following keys and key combinations are provided for navigation:
Key combinations Motion
Left arrow Moves the gray field in a cell to the left by one cell and selects the
contents of that cell.
If the first line is reached, the previous line is automatically selected.
Right arrow Moves the gray field in a cell to the right by one cell and selects the
If the last line is reached, the next line is automatically selected.
Up arrow Moves the gray field in a cell to the up by one cell and selects the
Down arrow Moves the gray field in a cell to the down by one cell and selects the
Shift+Left arrow Moves the selected object and the gray field to the left by one cell.
This also applies to several selected objects, the gray field must be
behind one of the selected objects.
Shift+Right arrow Moves the selected object and the gray field to the right by one cell.
Shift+Up arrow Moves the selected object and the gray field up by one cell.
Shift+Down arrow Moves the selected object and the gray field down one cell.
Home Positions the gray field in the first column and shows this new location.
End Positions the gray field in the last column and shows this new location.
Ctrl+Home Positions the gray field in the upper left hand cell in this network and
shows this new location.
Ctrl+End Positions the gray field in the upper right hand cell in this network and
shows this new location.
Page Up Scrolls the position of the gray field one page up and shows this new
position, as long as the first row is not visible.
Displays the previous network/segment, if the first row is already
visible. You can also display the previous segment/network via View
GoTo Previous Section.
LL984 Editor
68 EIO0000000549 07/2012
NOTE: You can also display a segment/network by double-clicking the respective
segment/network in the Structural View of the Project Browser.
Page Down Scrolls the position of the gray field one page down and shows this new
position, as long as the last row is not visible.
Displays the next network/section, if the last row is already visible. You
can also display the next section/network via View GoTo Next
Section.
Using Page Down in the last network of a segment, if the last row is
already visible, will display a message box asking you to create a new
network.
Click Yes to open the New Network dialog.
Click No to open the next segment/network.
Space bar Selects or deselects the object in the cells highlighted in gray.
Shift + Space bar The position of the gray field is moved one cell to the right.
Enter In Insert mode: Inserts the selected object into the currently selected
cells highlighted in gray and moves the position of the gray field one
cell to the right.
Alt+Enter Opens the properties dialog box for the selected object/pin.
Tab Select the next pin in an FFB if the FFB or an FFB pin is selected.
Esc Activates the Select mode.
Key combinations Motion
LL984 Editor
EIO0000000549 07/2012 69
Selecting Objects
Select Mode
Objects are selected in select mode.
Select mode can be activated using:
the Edit Select Mode menu command
the symbol,
or
the Esc key
The cursor symbol indicates that select mode is active
Selecting an Object
Selecting Several Objects
Using the Mouse Using the Keyboard
Left-click the object you want to select. Move the gray field to the cell with the object to be
selected, see also Navigating with the Keyboard
(see page 67).
1. Click the left mouse button and keep it
pressed.
2. Drag the mouse across the objects you
want to select.
or
1. Left-click the first object you want to select.
2. Press the Ctrl key and keep it pressed.
3. Left-click the next object you want to
select.
4. Repeat these steps until all desired objects
are selected.
Selecting several objects:
1. Move the gray field to the cell with the first
object to be selected, see also
Navigating with the Keyboard
(see page 67).
2. Press the Shift+Space bar key
combination.
Result: The object is added to the
current selection and the gray field is
shifted one cell to the right.
3. Repeat these steps until all desired
objects are selected.
LL984 Editor
70 EIO0000000549 07/2012
Selecting by Rows
Selecting by Columns
Selecting All
Deselecting Objects
Selecting the contents of a row:
1. Left-click the number of the row you want
to select in the vertical ruler.
Selecting the contents of several lines:
1. Left-click the number of the first line you
want to select in the vertical ruler.
2. Press the Shift key and keep it pressed.
3. Left-click the number of the last line you
want to select in the vertical ruler.
-
Selecting the contents of a column:
1. Left-click the number of the column you
want to select in the horizontal ruler.
Selecting the contents of several columns:
1. Left-click the number of the first column
you want to select in the horizontal ruler.
3. Left-click the number of the last column
you want to select in the horizontal ruler.
-
Use the Edit Select All menu command. Press the Ctrl+A key combination.
Left-click an empty space in the section. Move the gray field.
LL984 Editor
EIO0000000549 07/2012 71
Deleting, Cutting, Copying, Pasting and Moving Objects
Deleting Objects
Cutting Objects
The cut object can be inserted in any other position (also in another LL984 network).
Copying Objects to the Clipboard
The cut object can be inserted in any other position (also in another LL984 network).
1. Select (see page 69) the object to be
deleted.
2. Use the Edit Delete menu command.
Deleting the selected object:
1. Select (see page 69) the object to be
deleted.
2. Press the Del key.
Deleting the object left of the gray field:
1. Press the Backspace key.
Result: The selected object is deleted. The actual parameters are deleted together with the
object, even if they were not selected explicitly. Boolean links are only deleted if they are
selected explicitly.
1. Select the object to be cut.
2. Use the Edit Cut menu command.
or
Use Cut from the context menu (right-
click).
1. Select the object to be cut.
2. Press the Ctrl+X key combination.
Result: The selected object is cut from the section and copied to the clipboard. This is also
the case for the actual parameters.
1. Select the object to be copied.
2. Use the Edit Copy menu command.
or
Use Copy from the context menu (right-
click).
2. Press the Ctrl+C key combination.
Result: The selected object is copied to the clipboard. This is also the case for the actual
parameters.
LL984 Editor
72 EIO0000000549 07/2012
Pasting Objects from the Clipboard
Moving Objects
1. Use the menu command Edit Insert.
or
Use Paste from the context menu (right-
click).
2. Left-click the target position.
1. Move the cursor to the target position
pressing Ctrl and using the arrow keys.
2. Press the Ctrl+V key combination.
3. Press Enter.
NOTE: (for pasting contacts and coils) If the target position already contains a contact or
coil, the existing object is overwritten by the new object.
NOTE: The following is the behavior of the Copy, Cut and Paste on a function block
instance. It only applies to graphical languages as FBD, LD and LL984.
Using the Paste function after a Copy of an object:
As a result of a Copy, a new function block instance (FBI name) is used. The Paste
function creates a new FBI whenever it is repeated. Accordingly, the FBI name is
incremented.
Using the Paste function after a Cut of an object:
As a result of a Cut, the same instance of the function is used. The Paste function uses
the same FBI whenever it is repeated. Accordingly, the FBI is identical.
1. Select the object to be moved.
2. Position the mouse pointer on the
selected object. (On one of the selected
objects if several are selected).
Result: The mouse pointer changes its
symbol to .
3. Click the left mouse button and keep it
pressed.
Result: The mouse pointer changes its
symbol to .
4. Drag the object to the new position and
release the mouse button.
1. Position the gray field on the object to be
moved.
2. Press the Space bar.
4. Move the object to the target position
using the arrow keys.
LL984 Editor
EIO0000000549 07/2012 73
Copying Objects via Drag-and-Drop
Result: The selected object is moved from its original position to the target position. The
objects actual parameters are moved together with the object. Boolean links are only kept
for horizontal movement operations.
NOTE: A moving of FFBs to cells that are already occupied (e.g. by contact, coil, other FFB,
boolean link), is not possible.
NOTE: The move operation is also possible across sections between different opened LL984
networks.
NOTE: When objects are moved beyond the visible area of the editor window, automatic
scrolling of the window will not begin until you reach the edge of the window with the mouse
pointer, not as soon as the objects are moved beyond the edge.
Using the Mouse Using the
Keyboard
2. Position the mouse pointer on the selected object.
Result: The mouse pointer changes its symbol to .
3. Click the left mouse button and keep it pressed.
4. Press the Ctrl key and keep it pressed.
Result: The mouse pointer changes its symbol to .
5. Drag the object to the new position.
NOTE: This is also possible across sections between different opened
LL984 networks.
6. Release the mouse button.
Result: A copy of the selected object is pasted at the target position. The
objects actual parameters (variable/address) are copied together with
the object. A new instance is automatically created for FFBs.
-
LL984 Editor
74 EIO0000000549 07/2012
Displaying the Properties
Displaying the Object Properties
You have the following options to display the object properties dialog:
Double-click the object.
Select (see page 69) the object and use the Edit Properties... dialog.
Select the object and use Properties from the context menu (right-click).
Select the object and then press the Alt+Enter key combination.
When the properties dialog is called without an object being selected, the Network
Properties (see page 38) dialog is opened.
If several objects are selected, the commands do not work.
Displaying the Data Properties
You have the following options to display the Data Properties dialog
(see page 121):
Via the LL984 network:
Select an object and use Data Properties from the context menu or press the
Ctrl+Enter key combination.
Via the Data Editor
Select the line of the respective object in the Data Editor and use Data
Properties from the context menu or press the Ctrl+Enter key combination or
use the Edit Data Properties dialog.
LL984 Editor
EIO0000000549 07/2012 75
Inserting and Deleting Rows/Columns
Introduction
Each network contains a matrix of 7 rows and 11 columns.
But via Insert/Delete row and Insert/Delete column you can shift rows
downwards/upwards and shift columns to the right/left.
Rules for Inserting Rows/Columns
The following rules apply when inserting rows/columns.
The new row is inserted above the first selected row.
The content of the following rows will be shifted to the bottom.
The new column is inserted left of the first selected column.
The content of the following columns will be shifted to the right.
If there are no free rows/columns at the bottom/right of the network, the menu
items will be disabled.
If the new row would intersect a middle or a bottom node of an FFB, the menu
items will be disabled.
Rules for Deleting Rows/Columns
The following rules apply when deleting rows/columns.
You can not delete a row/column containing any object.
If there are no free rows/columns at the current position, the menu items will be
disabled.
Inserting Rows
Inserting Columns
Step Action
1 Select the desired row in the vertical ruler (click the row number).
2 Use the Insert row menu command from the context menu of the vertical ruler or use
the Edit Insert row menu command.
Result: A row is inserted above the selected row.
Step Action
1 Select the desired column in the horizontal ruler (click the column number).
2 Use the Insert column menu command from the context menu of the horizontal ruler
or use the Edit Insert column menu command.
Result: A column is inserted left of the selected column.
LL984 Editor
76 EIO0000000549 07/2012
Deleting Rows
Deleting Columns
Step Action
1 Select the desired row in the vertical ruler (click the row number).
2 Use the Delete row menu command from the context menu of the vertical ruler
or use the Edit Delete row menu command.
Result: The row is deleted. The rows below are shifted on row up. At the bottom
an empty row is inserted.
Step Action
1 Select the desired column in the horizontal ruler (click the column number).
2 Use the Delete column menu command from the context menu of the horizontal
ruler or use the Edit Delete column menu command.
Result: The column is deleted. The columns from the right are shifted one
column to the left. At the right side of the grid an empty column is inserted.
LL984 Editor
EIO0000000549 07/2012 77
6.2 Editing Contacts
Overview
This section describes how to edit contacts in the LL984 programming language.
Topic Page
Selecting Contacts 78
Placing Contacts 80
Properties Dialog for Contacts 83
LL984 Editor
78 EIO0000000549 07/2012
Selecting Contacts
Introduction
A contact is an LL984 element that transfers a status on the horizontal link to its right
side. This status comes from the Boolean AND link of the status of the horizontal link
on the left side with the status of the relevant Boolean current parameter.
Information Concerning Variables
This information can be displayed by tooltip, too.
For further information on how the variables attached to contacts are displayed,
please refer to Network Display (see page 66).
Contact Types
Contact Type Description Call via Menu Command Call via
Icon
Call via Key
Normally open
contact
For normally open contacts, the status
of the left link is copied to the right link,
if the status of the relevant Boolean
actual parameter is 1. Otherwise, the
status of the right link is 0.
Edit New Normally
open contact
or
Normally open contact from
the context menu
F3
Normally
closed contact
For normally closed contacts, the status
of the left link is copied to the right link,
if the status of the relevant Boolean
actual parameter is 0. Otherwise, the
status of the right link is 0.
Edit New Normally
closed contact
or
Normally closed contact
from the context menu
Shift+F3
Positive
transition-
sensing
contact
With contacts for detection of positive
transitions, the right link for a program
cycle is 1 if a transfer of the relevant
actual parameter goes from 0 to 1 and
the status of the left link is 1 at the same
time. Otherwise, the status of the right
link is 0.
Also see Edge Recognition (see Unity
Pro, Program Languages and Structure,
Reference Manual ).
Edit New Positive
transition-sensing contact
or
Positive transition-sensing
contact from the context
menu
Ctrl+F3
LL984 Editor
EIO0000000549 07/2012 79
Negative
transition-
sensing
contact
With contacts for detection of negative
transitions, the right link for a program
cycle is 1 if a transfer of the relevant
actual parameter goes from 1 to 0 and
the status of the left link is 1 at the same
time. Otherwise, the status of the right
link is 0.
Also see Edge Recognition (see Unity
Pro, Program Languages and Structure,
Reference Manual ).
Edit New Negative
transition-sensing contact
or
Negative transition-sensing
contact from the context
menu
Ctrl + Shift +
F3
Contact Type Description Call via Menu Command Call via
Icon
Call via Key
LL984 Editor
80 EIO0000000549 07/2012
Placing Contacts
Introduction
Contacts can be placed in any free cell except cells directly on the right power rail.
If a contact is placed in a cell that was previously occupied by a contact, coil, a
Boolean link or a label, the cell contents are replaced by the new contact.
If a contact is placed in a cell that is already occupied by another object (e.g. FFBs),
an error message is returned.
The following are permitted as actual parameters for contacts:
Boolean variables
Boolean literals (0, 1, FALSE, TRUE)
Boolean addresses (topological addresses or symbolic addresses)
ST expressions that return a Boolean result (e.g. Var A > Var B)
ST expressions as formal parameters on contacts are an extension of IEC 61131-
3 and must be explicitly enabled via the Tools Project Settings Program
Languages Common by activating the Usage of ST expressions check
box.
Automatically Assign a Variable
If via Tools Options Data and Languages Languages the Automatically
assign a variable to a new graphical object check box is activated, then the
corresponding properties dialog is automatically opened when an object is placed.
The procedures explained here are used when the check box is deactivated.
Placing Contacts
Step Action
1 Select the desired contact, see also Selecting Contacts (see page 78).
2 Click the target cell in the LL984 section.
or
Use the Arrow keys to move the gray field to the target position, and press Enter.
Result: The selected contact is inserted.
3 To place further contacts of the same type:
Click the target cell in the LL984 section.
or
Use the Arrow keys to move the gray field to the target position and press Enter.
To return to selection mode:
Press the Esc key.
To insert other objects:
Select the object you wish to insert.
LL984 Editor
EIO0000000549 07/2012 81
Assigning Actual Parameters
Step Action
1 Open the properties dialog (see page 74) for the contact.
Result: The contacts properties dialog is opened.
Example:
2 You have the following options to enter the actual parameters:
You can enter %Mx (%Ix) and confirm using Enter.
You can enter the actual parameter and confirm using Enter.
You can select the actual parameter from the list of recently used names using
the symbol and confirm using Enter.
or
Using the button ... you can open a Data Selection dialog and confirm the
selected variables there with OK.
3 Confirm the selected variable with OK.
Result:
If the selected variable is declared, it is enabled in the section. A syntax and
semantics check (see page 63) is performed and the procedure ends here.
If the variable is not declared, a Create variable? dialog opens. In this case,
continue with the following steps of this procedure.
NOTE: If you wish to declare the variable later, close the dialog using the
symbol. In this case, the variable name is enabled in the section, but not declared.
NOTE: Entering a binary address (%M1 / %I1) opens the Create variable dialog
proposing a variable name (_000001 / _100001) that can be modified. If there is
already a variable associated to %M1 / %I1 it will be reused as proposal.
LL984 Editor
82 EIO0000000549 07/2012
Usage of ST Expressions
To enter ST expressions for contacts the same rules apply as for entering ST
expressions for FFB pins (see Unity Pro, Operating Modes).
4 If you do not want to assign the variable an address or comment, confirm using
Enter or the symbol.
Result: The variable is declared and enabled in the section. A syntax and
semantics check is performed and the procedure ends here.
Example:
5
If you do want to assign the variable an address and/or comment, use the
symbol for obtaining an advanced dialog and enter the address and/or comment.
6
Confirm with Enter or the symbol.
semantics check is performed immediately after the statement is entered.
Example:
Step Action
LL984 Editor
EIO0000000549 07/2012 83
Properties Dialog for Contacts
Calling the Properties Dialog
See Displaying the Properties (see page 74).
Structure of the Properties Dialog
The contact properties dialog consists of 2 tabs:
General
In this tab, you can enter the actual parameter (see page 81) of the contact.
Comment
In this tab, you can enter a comment about the contact.
General Tab
Representation of the General tab
LL984 Editor
84 EIO0000000549 07/2012
Elements of the General tab
NOTE: Entering a binary address (%M1 / %I1) opens the Create variable? dialog
proposing a variable name (_000001 / _100001) that can be modified. If there is
already a variable associated to %M1 / %I1 it will be reused as proposed.
Comment Tab
Representation of the Comment tab
Element Description
BOOLEAN
Expression
Enter the name of the actual parameter in this text box.
You have the following options:
You can directly enter the name of the variable/address or paste it from the
clipboard.
You can select the name of the variable from the list of recently used names
using the symbol.
or
Use the command button ...to open a Data Selection dialog (see Unity
Pro, Operating Modes).
The actual parameters which are permitted are:
Boolean variables
Boolean constants
ST expression delivering a Boolean result (e.g. Bool Var 1 OR Bool Var 1)
Literal (1 or 0 or. TRUE or FALSE)
OK Use this command button to accept the entries and close the dialog.
Apply Use this command button to accept the entries without closing the properties
dialog.
LL984 Editor
EIO0000000549 07/2012 85
Elements of the Comment tab
Element Description
Text box Enter a comment about the contact.
This comment is displayed as a tooltip when the cursor is placed over
the contact. It is independent from the variable comment that can be
assigned to the variable in the Data Editor.
OK Use this command button to accept the entries and close the dialog.
Apply Use this command button to accept the entries without closing the
properties dialog.
LL984 Editor
86 EIO0000000549 07/2012
6.3 Editing Coils
Overview
This section describes how to edit coils in the LL984 programming language.
Topic Page
Selecting Coils 87
Placing Coils 90
Property Dialog for Coils 93
LL984 Editor
EIO0000000549 07/2012 87
Selecting Coils
Introduction
A coil is an LL984 element which transfers the status of the horizontal link on the left
side, unchanged, to the horizontal link on the right side. The status is saved in the
respective Boolean actual parameter. Coils normally follow contacts or FFBs,
(functions and function blocks), but they can also be followed by contacts.
Information Concerning Variables
This information can be displayed by tooltip, too.
For further information on how the variables attached to coils are displayed, please
refer to Network Display (see page 66).
Coil Types
CAUTION
UNINTENDED EQUIPMENT OPERATION
Be sure of the output states after a PLC start when using latched and non-latched
coils.
Before using non-latched or latched coils, make sure that you completely
understand the different behavior of non-latched/latched coils.
Non-latched Coils
A reset of the coil will be performed during warm-start and after STOP/RUN of
the PLC. Reset during warm-start works for %M addresses and %M-located-
variables attached only.
Latched Coils
In the first scan latched coils have the status of last scan before warm-start.
Failure to follow these instructions can result in injury or equipment damage.
LL984 Editor
88 EIO0000000549 07/2012
PLC Start Behavior of Coils
Non-latched Coils
A reset of the coil will be performed during warm-start and after STOP/RUN of the
PLC. Reset during warm-start works for %M addresses and %M-located-
variables attached only.
Latched Coils
Latched coils will maintain their state after a Stop/Start of the PLC and on warm-
start. In the first scan latched coils have the status of last scan before warm-start.
This is the same behavior as normal coils show in IEC Ladder Diagram language.
Coil Type Description Call via Menu Command Call via
Icon
Call via
Keyboard
Coil (non-
latched)
With coils, the status of the left link is copied to
the relevant Boolean actual parameter and the
right link.
For further information see below.
Edit New Coil
or
Coil from the context menu
F5
Latched
coil
With latched coils, the status of the left link is
copied to the relevant Boolean actual
parameter and the right link.
For further information see below.
Edit New Latched coil
or
Latched coil from the context
menu
Shift+F5
LL984 Editor
EIO0000000549 07/2012 89
Detailed information:
For details when a warm-start is performed please see Processing of Power
Outage and Restoral for Premium/Quantum PLCs (see Unity Pro, Program
Languages and Structure, Reference Manual ).
Especially for the case of a Power Cycle this depends on the position of the PLCs
key switch (MemPrt/Start/Stop).
For firmware version 2.8:
Latched coils are not maintained if the key switch is in the Start position.
For firmware version 2.6:
Latched coils are maintained regardless of the key switch position.
For details regarding the PLCs key switch refer to Key Switches (see Quantum
with Unity Pro, Hardware, Reference Manual).
For details regarding Cold Start and warm-start processing refer to Processing on
Cold Start for Premium/Quantum PLCs (see Unity Pro, Program Languages and
Structure, Reference Manual ) and Processing on Warm Restart for
Premium/Quantum PLCs (see Unity Pro, Program Languages and Structure,
Reference Manual ).
Non-latched Coil Restriction
The following restriction applies for non-latched coils:
If an address (or a variable located on this address) is attached to a normal LL984
coil (non-latched) and this address has other (latched) write usages somewhere
else in the program (for example an assignment in ST/FBD/LD or a latched coil
in an LL984 network), this will lead to the following analyze message:
Non- l at ched usage of %1 det ect ed, whi ch i s used al so as
l at ched.
This message will be reported for the non-latched coil(s) usage in LL984
networks only.
To help avoid this restriction, start a search for getting the occurrences of this
conflicting address.
Latched Coil Representation
A latched coil is represented by a circle with an L or an M in the middle.
Whether an L or an M will be displayed inside a latched coil can be define via Tools
Options Data and Languages LL984 Show latched coil as. Please
refer to Data and Languages (see page 48).
LL984 Editor
90 EIO0000000549 07/2012
Placing Coils
Introduction
For placing coils the following restrictions apply:
Only 1 coil can be placed per row.
No other object can be placed to the right of a coil. The coil is always the last
object in a row.
If a coil is placed in a cell that is already occupied by another object (e.g. FFBs),
an error message is returned.
A placed coil automatically creates a connection with its neighboring objects on the
left if they are of the BOOL data type, even if free cells are between them.
The following are permitted as actual parameters for coils:
Boolean variables
Show Coils in Last Column
Using the main menu View you can activate the Show coil in last column setting.
If this setting is activated, each coil will be displayed in the last column with a dotted
line between its "real" location cell and the last column.
Otherwise each coil will be displayed at its "real" location cell.
NOTE: Activating this setting will switch the LL984 Editor to Read only mode. No
modifications are allowed inside the LL984 Editor. To leave the Read only mode,
just deactivate this setting.
Automatically Assign a Variable
If via Tools Options Data and Languages Languages the Automatically
assign a variable to a new graphical object check box is activated, then the
corresponding properties dialog is automatically opened when an object is placed.
The procedures explained here are used when the check box is deactivated.
LL984 Editor
EIO0000000549 07/2012 91
Placing Coils
Assigning Actual Parameters
Step Action
1 Select the desired coil. See also Selecting Coils (see page 87).
or
Use the Arrow keys to move the gray field to the target position, and press Enter.
Result: The selected coil is inserted.
3 To place further coils of the same type:
or
Press the Esc key.
Step Action
1 Open the properties dialog (see page 74) for the coil.
Result: The coils properties dialog is opened.
Example:
2 You have the following options to enter the actual parameters:
You can enter %Mx (%Ix) and confirm using Enter.
You can enter the variable/address name and confirm using Enter.
You can select the variable name from the list of recently used names using
the symbol and confirm using Enter.
or
Using the button ... you can open a Data Selection dialog and confirm the
selected variables there with OK.
LL984 Editor
92 EIO0000000549 07/2012
3 Confirm the selected variable with OK.
Result:
If the selected variable is declared, it is enabled in the section. A syntax and
semantics check (see page 63) is performed and the procedure ends here.
If the variable is not declared, a Create variable? dialog opens. In this case,
continue with the following steps of this procedure.
NOTE: If you wish to declare the variable later, close the dialog using the
symbol. In this case, the variable name is enabled in the section, but not
declared.
NOTE: Entering a binary address (%M1 / %I1) opens the Create variable?
dialog proposing a variable name (_000001 / _100001) that can be modified. If
there is already a variable associated to %M1 / %I1 it will be reused as proposal.
4 If you do not want to assign the variable an address or comment, confirm using
Enter or the symbol.
semantics check is performed and the procedure ends here.
5
If you do want to assign the variable an address and/or comment, use the
symbol for obtaining an advanced dialog and enter the address and/or comment.
6
Confirm with Enter or the symbol.
semantics check is performed.
Step Action
LL984 Editor
EIO0000000549 07/2012 93
Property Dialog for Coils
Calling the Properties Dialog
See Displaying the Properties (see page 74).
Structure of the Properties Dialog
The coil properties dialog consists of 2 tabs:
General
In this tab, you can enter the actual parameter (see page 91) of the coil.
Comment
In this tab, you can enter a comment about the coil.
General Tab
Representation of the General tab
Elements of the General tab
Element Description
BOOLEAN
Expression
Enter the name of the actual parameter in this text box.
You have the following options:
You can directly enter the name of the variable/address or paste it from
the clipboard.
You can select the name of the variable from the list of recently used
names using the symbol.
or
Use the command button ... to open a Data Selection dialog (see Unity
The actual parameters which are permitted are:
Boolean variables
LL984 Editor
94 EIO0000000549 07/2012
Comment Tab
Representation of the Comment tab
Elements of the Comment tab
OK Use this command button to accept the entries and close the dialog box.
dialog box.
Element Description
Element Description
Text box Enter a comment about the coil.
This comment is displayed as a tooltip when the cursor is placed over the coil.
It is independent from the variable comment that can be assigned to the
variable in the Data Editor.
OK Use this command button to accept the entries and close the dialog box.
dialog box.
LL984 Editor
EIO0000000549 07/2012 95
6.4 Editing Function Blocks
Topic Page
Editing Function Blocks 96
Using Mnemonics 98
LL984 Editor
96 EIO0000000549 07/2012
Editing Function Blocks
Introduction
You can insert function blocks using one of the following features:
Mnemonics
Data Selection
FFB Input Assistant.
Types Library Browser,
Copy/Paste
Inserting a Function Block
Step Action
1 In the LL984 Editor right-click and select from the context menu either
Data Selection (Ctrl+D) or
FFB Input Assistant (Ctrl+I).
You can also insert a function block using:
drag-and-drop from the Types Library Browser (Alt+3), .
copy/paste
Mnemonics
2 Enter the complete name of the function block (e.g. L9_SUB).
3 Confirm with Enter.
4 Click the cell where you want to insert the function block.
Result:
The function block is inserted (if allowed at this position).
LL984 Editor
EIO0000000549 07/2012 97
Representation of the FFB Input Assistant
You can also see the Comments displayed in the dialog above as a tooltip when the
cursor is placed over the respective pin of the function block.
Editing Values
To open the FFB Input Assistant for an already inserted function block, right-click
the function block and select FFB Input Assistant from the context menu.
Click the Entry Field and enter a value.
You are only allowed to edit the Entry fields displayed in black. Only the nodes (top,
middle, bottom) of a function block can be edited.
You can not edit the Entry fields displayed in grey (disabled).
Restrictions
For inserting function blocks the following restrictions apply:
Only LL984 library function blocks can be inserted in LL984 networks. If you try
to insert a function block of another library a message will inform you, that this is
not possible.
You can not insert self-programmed DFBs in LL984 networks.
LL984 library function blocks can not be inserted in IEC languages sections
(FBD, LD, ST, IL). SFC does not use function blocks.
FBD and LD editors will refuse insertion and will display a message that
insertion is not possible.
For textual languages (ST, IL) the call of an LL984 library function block will be
detected during Analyze.
LL984 Editor
98 EIO0000000549 07/2012
Using Mnemonics
Introduction
Instead of inserting LL984 objects via toolbar, FFB Input Assistant, Data Selection
or drag-and-drop, you can use so called Mnemonics.
Mnemonics Option
Open the Tools Options dialog.
Under Data and Languages Languages LL984 Mnemonics the Property
label column lists the contacts and coils and an assortment of frequently used
functions blocks available for LL984 networks.
In the Property value column you can enter a mnemonic for each listed element.
A mnemonic can consist of up to 4 alphanumeric signs.
Using Mnemonics
As you start typing text, while the current cell marker is on an empty cell in the
LL9894 Editor, a small edit box opens in the editor.
Entering a mnemonic (first key typed will be taken over into the edit box) and
pressing the Enter key will insert the corresponding LL984 element at the current
cell.
If the cells needed to insert the element are already occupied, a message box will
inform you and the element will not be inserted.
LL984 Editor
EIO0000000549 07/2012 99
6.5 Editing Links
Overview
This section describes how to edit links in the LL984 programming language.
Topic Page
Selecting Links 100
Combining Links 101
Placing Links 102
Editing Links 104
LL984 Editor
100 EIO0000000549 07/2012
Selecting Links
Introduction
Links are connections between LL984 objects (contacts, coils, FFBs etc.).
Boolean connections comprise one or more cell-segments that connect Boolean
objects (contacts, coils) with one another.
Boolean Connection (horizontal connection)
This horizontal connection enables series switching of contacts and coils.
The cell-segments of this connection can be created individually or as a complex
connection comprising several cell-segments.
Boolean Link (horizontal link)
This horizontal link automatically creates a connection between neighboring
Boolean objects to the left and right or between an object and the power rail.
Vertical Connection
This vertical connection enables parallel switching of contacts and coils.
Link Types
Link Type Description Call via Menu Command Call via
Icon
Call via Key
Horizontal
connection
horizontal connection, 1 cell wide Edit New Boolean
Connection
or
Boolean Connection from the
context menu
F7
Horizontal link A horizontal link creates a connection
between neighboring Boolean objects to
the left and right.
If there are no neighboring Boolean
objects available, a connection to the
power rail is made.
Edit New Boolean Link
or
Boolean Link from the context
menu
Alt+F6
Vertical
connection
vertical connection, 1 cell high Edit New Vertical
Connection
or
Vertical Connection from the
context menu
Shift+F7
LL984 Editor
EIO0000000549 07/2012 101
Combining Links
Boolean Links
Horizontal and vertical Boolean links can be combined in any way.
Example:
Contacts and Coils
Contacts and coils link automatically to existing horizontal or vertical links if no free
cells are found between them.
Example:
Crossing Boolean Links
If 2 Boolean links cross each other they are automatically connected. Since Boolean
links may not cross each other there is no special label for them.
Example:
LL984 Editor
102 EIO0000000549 07/2012
Placing Links
Placing Horizontal Connections
Process the following steps to place a horizontal link.
Placing Horizontal Links
Process the following steps to place a horizontal link.
Step Action
1 Select the horizontal connection (Boolean Connection). See also Selecting Links
(see page 100).
or
Result: The link is inserted.
3 To place further links of the same type:
or
Press the Esc key.
Step Action
1 Select the horizontal link (Boolean Link). See also Selecting Links (see page 100).
or
Result: The link is inserted and a connection is created to the neighboring Boolean
objects to the left and right.
If there are no neighboring Boolean objects available, a connection to the power
rail is made.
or
Use the Arrow keys to move the gray field to the target position and press
Enter.
Press the Esc key.
LL984 Editor
EIO0000000549 07/2012 103
Placing Vertical Connections
On the right side of the cells, there is space to create a vertical connection to the cell
below or above. Process the following steps to place a vertical connection.
Step Action
1 Select the vertical connection (Vertical Connection). See also Selecting Links
(see page 100).
2 Click the object which should be connected with the cell below.
or
Result: The link is inserted.
or
Press the Esc key.
LL984 Editor
104 EIO0000000549 07/2012
Editing Links
Introduction
If you combine several horizontal links this will result in 1 horizontal link.
If you combine several vertical links this will result in 1 vertical link.
If you combine a horizontal and a vertical link this will result in a link made of 2
objects, a horizontal and a vertical link, that can be selected independent from each
other.
Deleting, Cutting, Copying, Pasting and Moving Links
You can delete, cut, copy, paste and move links.
For further information please refer to Deleting, Cutting, Copying, Pasting and
Moving Objects (see page 71).
Modifying the Size of Links
Step Action
1 Select a link.
Result: Size handles are displayed at the beginning and at the end of the link.
2 Click a size handle with the left mouse button and keep it pressed.
3 Drag the size handle to the desired new end position of the link and release the
mouse button.
LL984 Editor
EIO0000000549 07/2012 105
6.6 Editing Equation Network Blocks
Overview
This section describes how to edit Equation Network Blocks in the LL984
programming language.
Topic Page
Editing Equation Network Blocks 106
Editing the ST Assignment Expression 108
LL984 Editor
106 EIO0000000549 07/2012
Editing Equation Network Blocks
Introduction
Equation networks in the LL984 Editor are provided as Equation Network Blocks.
Equation network blocks offer an opportunity to program complex mathematical
functions, with values stored in memory words.
An Equation Network Block contains an assignment expression written in ST
language.
In general you can use the features provided by ST language as long as it is a valid
ST assignment expression.
Please refer to the Structured Text (ST) chapter (see Unity Pro, Program Languages
and Structure, Reference Manual ) and the ST Editor chapter (see Unity Pro,
Operating Modes).
Using the Equation Network Block
You can insert an Equation Network Block using the respective toolbar button, via
menu (Edit New Equation Network block) or via the editors context menu
(right mouse click).
An Equation Network Block can only be inserted in an LL984 network at row 1,
column 2. The block is 7 rows high and 9 columns wide.
On the left side of an equation network block there is an Enable input pin, where you
can connect a contact or a boolean connection.
On the right side there are 5 output pins (OK, Lower, Equal, Greater,Error), where
you can connect 5 normally open coils. After inserting these coils are displayed with
symbols inside according to the pin names (O, <, =, >, E).
LL984 Editor
EIO0000000549 07/2012 107
Representation
Representation of the Equation Network Block
Items of the Equation Network Block
Problems During Solving
Item Description
input pin Enable you can connect a contact or a boolean connection to
enable the block
equation network block expression written in ST language
output pins OK (O): set when the equation is solved without problems
Lower (<): set when the equation result is less than zero
Equal (=)set when the equation result is equal to zero
Greater (>)set when the equation result is greater than zero
Error (E): set when a problem occurred during solving the
equation (see table below)
Problem Description
invalid operation An internal message generated by the math coprocessor.
overflow A value is too large to be represented in its specified data type.
underflow A number is too small to be represented in FP format (for floating
point data only).
divided by 0 The variable, constant, or result of a function directly to the right of
a / operator has a value of zero.
LL984 Editor
108 EIO0000000549 07/2012
Editing the ST Assignment Expression
Introduction
After inserting an Equation Network Block double-click the displayed question
marks (?????) to enter the ST assignment expression.
Confirming with Enter will start an analysis and the found detected problems will be
displayed in a tooltip.
Animation of the memory words used inside the ST assignment expression can be
seen in a Variable Window. Please refer to Variable Display Window (see Unity
Memory Addresses
A memory address entered in the ST assignment expression must start with one of
the following symbols, specifying the address type:
%M (memory bit)
%I (discrete input)
%IW (input word)
%MW (memory word)
The address type must be followed by an address number (no leading zeros
required).
Creating Variables Automatically
After confirming the ST assignment expression with Enter, for every entered
address a variable will be created automatically, which is used in the equation
network.
Examples
Address Variable
%M1 _000001
%I1 _100001
%IW1 _300001
%MW1 _400001
LL984 Editor
EIO0000000549 07/2012 109
The variable type is derived from its address suffix.
The variable is mapped to the associated internal located memory.
For example: %IW1DI becomes the variable _300001_DI : DI NT@%I W1.
Constants
Constants in equation networks have the same syntax as in other IEC editors (that
is without a leading # character).
Operators
Operators and their precedence
Suffix Variable Type
no suffix %Mx, %Ix EBOOL
%IWx, %MWx UINT
I INT
DI DINT
UD UDINT
R REAL
W WORD
Operation Symbol Precedence
Parentheses (expression) HIGHEST
Function evaluation identifier (argument list) -
Negation - -
Complement ~ -
Exponentiation ** -
Multiply * -
Divide / -
Add + -
Subtract - -
Comparison < , > , <= , >= -
Equality = -
Inequality <> -
Boolean AND & -
LL984 Editor
110 EIO0000000549 07/2012
The operators **, *, /, +, -, <<, >>, <, >, <=, >=, =, <>, &, ^ and | are supported as
they are implemented now in Unity Pro ST syntax. That is not all data type
combinations for operand types and the result type are supported.
NOTE: Unity Pro only supports a floating point value for the ** operator (EXPT-
functions).
NOTE: Bitwise logical AND, OR or XOR operations work like in ST syntax.
Ternary Conditional
Ternary conditional (C?t:f ), in contrast to legacy LL984, is not available in Unity Pro
ST syntax.
The already existing SEL function block provides this functionality and has to be
used instead.
Example:
Legacy syntax:
400010 : = 300010 < 300020 ? 300004 : 300005
Unity Pro syntax:
%MW10 : = SEL( %I W10 < %I W20, %I W4, %I W50) ;
With the following, automatically created by the editor:
_400010 : = SEL( _300010 < _300020, _300004, _300005) ;
Bitwise Shift
Bitwise shift (<<, >>), in contrast to legacy LL984, is not available in Unity Pro ST
syntax.
The already existing SHL and SHR function blocks provide this functionality and have
to be used instead.
Example:
Legacy syntax:
400010 = 300010U << 3
Unity Pro syntax:
%MW100W: = SHL( %I W10W, 3) ;
_400100_W: = SHL( _300010_W, 3) ;
Boolean Exclusive OR ^ -
Boolean OR | -
Assignment := LOWEST
Operation Symbol Precedence
LL984 Editor
EIO0000000549 07/2012 111
Function Blocks
In general you can use the function blocks provided for ST language.
In particular the following Unity Pro function blocks replace the legacy function
blocks listed below.
Legacy Function
Name
Unity Pro
Function Name
Argument
Type*
Return Type* Meaning
ABS ABS S,U,L,UL,F S,U,L,UL,F absolute value
ARCCOS ACOS F F arc cosine
ARCSIN ASIN F F arc sine
ARCTAN ATAN F F arc tangent
COS COS F F cosine
COSD COSD F F cosine of degrees
EXP EXP F F exponent function (power of e)
(does not need to be a whole number)
FIX REAL_TO F L convert floating point to integer
(presumes an FP argument)
FLOAT INT_TO S, U, L, UL F converts integer to floating point
(presumes an integer argument)
LN LN F F natural logarithm (base e)
LOG LOG F F common logarithm (base 10)
SIN SIN F F sine of radians
SIND SIND F F sine of degrees
SQRT SQRT F F square root
TAN TAN F F tangent of radians
TAND TAND F F tangent of degrees
*: S=INT, U=UINT, L=DINT, UL=UDINT, F=REAL
LL984 Editor
112 EIO0000000549 07/2012
Example of an LL984 Expression
Legacy syntax:
40701 = 40702U + COS( 40703UL) * #8. 00135F + SI N( 40704) ;
Unity Pro syntax:
%MW701 : = REAL_TO_UI NT( WORD_TO_REAL( %MW702W) +
COS( WORD_AS_REAL( %MW703W, %MW704W) ) * 8. 00135 +
SI N( WORD_TO_REAL( %MW704W) ) ) ;
_400701 : = REAL_TO_UI NT( WORD_TO_REAL( _400702_W) +
COS( WORD_AS_REAL( _400703_W, _400704_W) ) * 8. 00135 +
SI N( WORD_TO_REAL( _400704_W) ) ) ;
LL984 Editor
EIO0000000549 07/2012 113
6.7 Assigning Variables to LL984 Objects
Assigning Variables to LL984 Objects
Introduction
In the LL984 Editor you can assign a variable (like _400001 or sym1) or an address
(like %M1) to an FFB pin or to a contact/coil.
If the variable is not declared, the Create variable? dialog opens.
If the variable or address assigned is not compatible with the pin or contact/coil, a
message will be displayed in the output window after Build Analyze.
Automatic Variable Naming
If you, for example, assign an address (e.g. %MW1) to a pin, the Create variable?
dialog opens proposing a variable name (e.g. _400001) and a data type (e.g. UINT).
The following rules apply to this automatic proposal, depending on the address of
the actual parameter, the pin type and dimension (n) in case of an array type:
NOTE: For the most used pin types UINT and EBOOL no type suffix are appended
to the proposed variable name.
Address Pin Type Dimension (for array types) Variable Name
%MW1 UINT 1 (n) _400001 (_400001_n)
INT _400001_I (_400001_In)
WORD _400001_W (_400001_Wn)
%IW1 UINT 1 (n) _300001 (_300001_n)
INT _300001_I (_300001_In)
WORD _300001_W (_300001_Wn)
%I1 EBOOL 1 (n) _100001 (_100001_n)
%M1 EBOOL 1 (n) _000001 (_000001_n)
LL984 Editor
114 EIO0000000549 07/2012
Use Case 1
Assignment to a pin of type UINT
NOTE: As the pin type was UINT no type suffix was appended to the variable name.
Use Case 2
Assignment to a pin of type ARRAY[1...n] of UINT
Use Case 3
Assignment to a pin of type ANY or ANY_ARRAY_UINT or ANY_ARRAY_BOOL
(dynamic array)
The dimension (n) of a dynamic array will be provided by another dimension pin (e.g.
LENGTH) of the function block.
This dimension pin will be initialized during block insertion.
The dimension of the array will be calculated based on the dimension pin value
entered as actual parameter of the dimension pin.
If the resulting type is a UINT array:
dimension = dimension pin value.
If the resulting type is a Boolean array:
dimension = dimension pin value * 16.
User-Assigned
Address
Variable Variable Created
and Assigned
Variable Type
%MW1 not existing yet _400001 UINT
User-Assigned
Address
and Assigned
Variable Type
%MW1 not existing yet _400001_n ARRAY[1...n] of UINT
User-Assigned
Address
and Assigned
Variable Type
%MW1 not existing yet _400001_n ARRAY[1...n] of UINT
LL984 Editor
EIO0000000549 07/2012 115
If you modify n on the dimension pin to n2:
Use Case 4
Assignment to a pin of type DDT1
Memory Consumption
If you create any kind of located variables (elementary type, array or DDT) this will
not increase memory consumption on the PLC (except for Upload information).
New Variable Creation
If you assign a different address or modify a dimension pin, a new variable will be
created.
The old attributes (except the address) will be overtaken and the old variable will be
deleted, if it is not used anywhere else in the program.
Invalid Variables
If you create a located variable with an address range which exceeds the address
range defined under State RAM of the CPUs Configuration tab, the following
message will be displayed after Build Analyze:
Topol ogi cal addr ess i ndex i s not val i d.
User-Assigned
Address
Variable Variable Created and
Assigned
Variable Type
%MW1 not existing yet _400001_n2 ARRAY[1...n2] of UINT
%MW1 already existing _400001_n2
attributes (like descriptors,
comments etc.) are taken
over
ARRAY[1...n2] of UINT
User-Assigned
Address
and Assigned
Variable Type
%MW1 not existing yet _400001_DDT1 DDT1
LL984 Editor
116 EIO0000000549 07/2012
There are different ways to solve this issue:
Click the message displayed in the output window to open the Data Editor and
adapt the address of the variable.
Click the message displayed in the output window to open the Data Editor and
delete the variable and create a new variable with an applicable address range.
Adapt the address range defined under State RAM of the CPUs Configuration
tab.
NOTE: If you just create a new variable at the pin of the function block without
deleting the previously created, invalid variable the message mentioned above will
be displayed again after next Build Analyze.
Example:
Under State RAM of the CPUs Configuration tab you entered a value 10000 for
%MW.
In your program you have an L_BLKMfunction block with LENGTH = 10.
At the SOURCE pin of the function block you enter following value: %MW9999.
This results in creation of the following variable:
_409999: ARRAY[ 1. . 10] OF UI NT@%MW9999
As the start address is %MW9999 and the length is 10, the end address will be
%MW10009.
This exceeds the address range (10000) defined under State RAM of the CPUs
Configuration tab.
Therefore the message mentioned above will be displayed after Build Analyze.
LL984 Editor
EIO0000000549 07/2012 117
6.8 Calling Subroutines
Calling Subroutines
Introduction
Calling subroutines is managed by 3 function blocks:
L9_J SR
L9_LAB
L9_RET
For detailed information please refer to the function block descriptions (see Unity
Pro, Original LL984, Block Library).
Up to 1023 subroutines can be established.
Unity Pro does not support interrupt handling with LL984 subroutines.
Restrictions
For the calling subroutines feature the following restrictions apply:
Only one LL984 segment can be created inside the subroutine (SR Section)
node of the MAST task.
L9_LAB and L9_RET function blocks can only be placed in an LL984 subroutine
network in the SR Sections.
An L9_LAB function block can only be placed in row 1, column 1 of an LL984
subroutine network.
Subroutine Structure
A subroutine is identified by a number (1.. 1023).
Subroutines are called by the L9_J SR function block within an LL984 network
(normal or subroutine network).
Two additional function blocks, which are only available in subroutine networks,
mark the starting point (L9_LAB function block) and ending point (L9_RET function
block) of a subroutine.
A subroutine may span multiple networks.
The L9_RET function block is optional and this explicit ending point of a subroutine
can be omitted,
if the last subroutine network is the last network of the subroutine segment or
if a new subroutine network (L9_LAB) would entered.
The L9_RET function block or the implicit forms, return from the current subroutine
network to the calling L9_J SR function block with an OK status.
LL984 Editor
118 EIO0000000549 07/2012
Nesting
A subroutine may call other subroutines or recursively call itself up to 100 times.
If the maximum nesting level is reached, an implicit return is performed and the ERR
output of the L9_J SR function block is set.
A nesting level problem message is propagated to the (99) cascaded L9_J SR
function blocks.
Further cascaded L9_J SR function blocks, which are being executed after a nesting
level problem, do not succeed to call a subroutine and the ERR output is being set
until the nesting level stack has been unwound.
NOTE: The message is only visible at those L9_J SR function blocks, contributing to
the problem. A dedicated problem treatment is possible on each calling level.
Subsequent L9_J SR function blocks of a segment are not influenced by this
problem.
Please also refer to the L9_J SR function block description (see Unity Pro, Original
LL984, Block Library).
LL984 Editor
EIO0000000549 07/2012 119
6.9 Entering Comments
Entering Comments
Introduction
Comments can be placed in LL984 sections in the form of text objects.
Text objects can overlap other objects.
The size of the object, depending on the size of the text, can be extended vertically
and horizontally to fill further grid units.
The same rules apply for entering text and navigating within text objects as for
editing ASCII text in standard text editors. (To create a line break in text objects you
must press the Ctrl+Enter key combination).
NOTE: Keep in mind that each change to a comment (e.g. change to a comment
text, change to the size of the text object) makes it necessary to recreate the section
involved (Build Build Changes).
Selecting the Text Object
You have the following options to select text objects:
Use the Edit New Comment menu command.
Use the Comment menu from the context menu.
Press the F8 key.
or
Select the symbol.
The active placement mode for text objects is indicated by the cursor symbol.
Placing Text Objects
Step Action
1 Select the text object.
or
Result: The text object is inserted.
Example:
LL984 Editor
120 EIO0000000549 07/2012
3 Enter the comment.
4 Confirm the text entered with:
Clicking with the mouse outside of the text object
or
Pressing the Enter key.
5 To insert further text objects:
or
Use the Arrow keys to move the gray field to the target position and press
Enter.
Press the Esc key.
Step Action
EIO0000000549 07/2012 121
7
LL984 Editor
Programming Languages Data Selection Dialog
EIO0000000549 07/2012
Programming Languages Data
Selection Dialog
Data Properties
Introduction
The anchored window (see Unity Pro, Operating Modes) Data Properties is used
to display and modify the variables and FFB properties.
The Data Properties window can be called up
using the Data Editor (see Unity Pro, Operating Modes).
a. Select one or several lines in the Data Editor.
b. Select Properties from the context menu.
the programming language sections
a. Select one or several element(s) in the programming language section.
b. Select Data Properties from the context menu or press CTRL+Enter.
the tab I/O Objects of a module
a. Select one or several lines in the Address/Name/Type table.
b. Select Data Properties from the context menu.
How the window behaves and the options in the Data Properties window depend
on whether the window was opened using the Data Editor or the Programming
Languages section.
NOTE: If more than one object is selected, only the common data for all the selected
objects is displayed. If this data is modified, the modification applies to all the
selected objects. In this way it is possible to assign the same comment to different
variables or assign the same initial value, see also: Unity Pro, Operating Modes
CAUTION
LOSS OF DATA
Before changing a data in the Data Properties window, ensure that the change is
appropriate not only to the selected instance of this data, but also to all other
instances of this data.
Failure to follow these instructions can result in injury or equipment damage.
122 EIO0000000549 07/2012
Structure of the Window
The contents of the window depend on the selected object:
Window Data Properties for elementary variables:
Window Data Properties for function blocks:
EIO0000000549 07/2012 123
Columns Available
The following table shows the different columns available in the Data Editor under
various tabs.
Name Description
Name name of the instance or data type
Comment comment for the variables/function blocks
Via the context menu, the comment can be linked to a Hyperlink (see Unity
Address address in the controller for referencing the variables
984 Address LL984 address of the variable (%Mx = 00000x, %Ix = 10000x, %IWx =
30000x, %MWx = 400001)
This column is only available for Quantum PLCs (but not for Quantum
Safety PLCs).
RW program Shows if the variable can or can not be written by the program.
Value initial value for the variables
Alias name selected by the user which makes it possible to change an IODDT,
DDT or an Array element to a name defined by the manufacturer or the user
See also: Unity Pro, Operating Modes.
Alias of complete path of the variable sub-field on which user sets Alias attribute
Save Shows if the variable accepts the mechanism for updating initial values with
current values.
Constant Shows if the variable is a constant or not.
Global data Shows if the variable is a variable that was swapped between different
stations via the network.
Global data
- Group
number of the group (the variables) in which the variable is transported
Global data
- ID
number for the unique display of a variable in the group (the variables)
Descriptor descriptors (1 to 9) of variables
Descriptor 1 is displayed after selecting this column in the Column
Configuration dialog. Descriptors 2 to 9 can be displayed using the +
sign in the Descriptor column header.
Type data type
Category EDT, DDT or IODDT
Size memory size
Used number of times the variable/function block is used in the program and in
other parts of the project (animation tables, user windows)
Custom free text for use of an external tool or for special user requirements
No. order number of a function block
Version type version
124 EIO0000000549 07/2012
EIO0000000549 07/2012 125
8
LL984 Editor
Search/Replace
EIO0000000549 07/2012
Search/Replace Tool
Subject of this Chapter
This chapter presents the Search / Replace tool and how to use its main functions:
the Search function is used to look for data,
the Replace function is used to replace data.
Topic Page
Overview of the Search / Replace tool 126
General Features for Search/Replace 128
Searching for Data 129
Replacing Data 130
Search Toolbar 131
Data Search Dialog 132
Cross-References (Search Results) 134
Cross-References (Replace) 137
Tracing Variables / Addresses 138
Search/Replace
126 EIO0000000549 07/2012
Overview of the Search / Replace tool
Introduction
The Search / Replace tool provides you with the following functions:
the Search function,
the Replace function.
Search Function
This function lets you look for objects such as:
instances of elementary data types (EDT),
instances and types of derived data (DDT / IODDT),
instances and types of function block data (EFB / DFB),
instances and types of data relating to Sequential Function Charts (SFC),
topological addresses (%M100).
The search is carried out in the following areas of the project:
sections that make up the application program,
animation tables,
operator screens,
configuration.
Replace Function
This function lets you replace objects such as:
instances of elementary data types (EDT),
instances of derived data types (DDT / IODDT),
instances of function block data (EFB / DFB),
topological addresses (%M100).
The replacement objects must be declared, except for direct addressing data (%M,
%MW, etc.) and their type must correspond to that of the objects being replaced.
The replacement can done on the search results and initiated at the result window.
Accessing the Data Search Dialog
To open the Data Search dialog
click the Data Search button in the toolbar or
use the Tools Search / Replace menu (Alt+5).
Search/Replace
EIO0000000549 07/2012 127
Predefined Search
To start a predefined search
from the Data Editor or
from a language editor window,
select the object whose references you want to see and use Initialize Search from
the context menu.
Another way is to select a variable in a language editor window. Doing so, the list
box of the search toolbar (see page 131) contains the variable name. Press Enter
to start searching. You can also use 2 special buttons from the toolbar to search for
reading/writing references (see page 131).
Search/Replace
128 EIO0000000549 07/2012
General Features for Search/Replace
Copy / Paste
You can use copy and paste in the following instances:
copying a data item from any given editor in the programming software and
pasting it into an entry field in the window,
copying a data item from the window and pasting it into any given editor in the
programming software,
copying / pasting a data item within a window.
Drag-and-Drop
You can use drag-and-drop for search.
Drag a data item from any given editor in the programming software and drop it at
the end of the list of displayed references; the corresponding tree is created.
Protection
The Search function is always available. Protection applies to:
the references in the protected sections of the program, which are not displayed,
the references in the protected sections of the DFBs, which are not displayed.
The Replace function complies with the protection applied to the different areas of
the project:
if the application field is in read-only, the Replace button is not available,
if certain references are protected, they can not be selected for replacement.
Online Mode
The use and behavior of Search / Replace in online mode are identical to the use
and behavior in offline mode.
Save Context
When you close the Search / Replace window, the following data is saved:
the position and size of the window,
the selection of search parameters,
the 10 most recent entries in the drop-down menu,
the current view (structural/functional and full/shortened/flat),
the contents of the Unity Pro Search / Replace output window.
Search/Replace
EIO0000000549 07/2012 129
Searching for Data
Searching via Data Search Dialog
To search data using the Data Search dialog, you must perform the following
actions:
Predefined Search
To start a predefined search
from the Data Editor or
from a language editor window,
select the object whose references you want to see and use Initialize Search from
the context menu.
Another way is to select a variable in a language editor window. Doing so, the list
box of the search toolbar (see page 131) contains the variable name. Press Enter
to start searching. You can also use 2 special buttons from the toolbar to search for
reading/writing references (see page 131).
Step Action
1 Open the Data Search dialog
by clicking the Data Search button in the toolbar or
by using the Tools Search / Replace menu (Alt+5) and pressing the Data
Search button in the Cross-References window (see page 134).
Result:
The Data Search Dialog is displayed.
2 Specify the search options in the Data Search Dialog (see page 132).
3 Click the Search button.
Result:
The search results are displayed in the Cross-References window
(see page 134).
Search/Replace
130 EIO0000000549 07/2012
Replacing Data

To access the data replace function, you must perform the following actions:
Step Action
1 After searching for data (see page 129) the search results are displayed in the
Cross-References dialog (see page 134).
2
In the Cross-References dialog click the button to display the Replace with
area of the dialog.
3 Enable the check boxes for those references of the search results which should be
replaced.
4 Enter the replacement data (only data compatible with the data being searched
for is tolerated)
or click the Down arrow to select the replacement data out of a list providing the
last 10 entries
or click the ... button to open a Data Selection dialog to select the instance or
data to be replaced (only the instances compatible with the instance being
searched for are displayed)
5 Click the Replace button to start the replacement operation in the preselected
Scope. Please refer to Data Search dialog (see page 132).
Search/Replace
EIO0000000549 07/2012 131
Search Toolbar
Introduction
The main toolbar of Unity Pro provides a Data Search button with a list box beside
it to select or to enter a search string.
Start Searching
To start searching the selected or entered search string press Enter.
The default search options are used.
The options can be changed by pressing the Data Search button left to the list box
instead of pressing Enter.
The search results are displayed in the Cross-References dialog (see page 134)
and a jump to the first occurrence of the searched data is done.
Data Search Dialog
To open the Data Search dialog (see page 132) click the binoculars symbol.
Searching for Reading/Writing References
To search for reading/writing references only, you can use
the Data Search dialog (see page 132) or
two special buttons from the toolbar (see below).
Using one of these 2 buttons initiates a direct jump to the first found occurrence of
the reading/writing reference (for example, into the containing network).
If instead of a direct jump to the first found occurrence of the reading/writing
reference the Data Editor is opened, either deactivate the Overlapping
(see page 132) option or click the Go to next reference button (see page 134).
Button Description
Click this button to start searching for reading references only.
The current search options, defined in the Data Search dialog, are used but the
Write option is ignored.
Click this button to start searching for writing references only.
The current search options, defined in the Data Search dialog, are used but the
Read option is ignored.
Search/Replace
132 EIO0000000549 07/2012
Data Search Dialog
Representation
Description
Elements of the Search tab
Element Description
Find what Enter the complete variable name you want to search for.
Click the Down arrow to display a list providing the last 10 search
strings.
Click the ... button to open a Data Selection dialog to select the object
you want to search for.
Scope Select the scope where you want to search.
The different scopes are:
application
a specific DFB of the project
all scopes (application + all DFBs)
Search button Starts the search and opens search results window (Cross-
References).
Close button Closes the dialog.
Help button Opens the Help for this dialog.
Read Limits the search to reading references.
Write Limits the search to writing references.
Overlapping Activate this check box to search for all complete and partial references.
Search/Replace
EIO0000000549 07/2012 133
Indirect Activate this check box to search for sub-elements and direct parents of
structured variables and arrays.
Max level of
indirection
Defines the maximum level of indirect elements (sub-elements/parents)
to be displayed.
Context Limits the search to a specific context.
Any: no contextual search
FFB: variable passed to an FFB
Coil: variable attached to a LD/LL984 coil
Contact: variable attached to a contact
SFC Object: variable used with an SFC object
ST/IL Statement: variable used with an ST/IL statement
The context is displayed as an optional column in the search results.
Keep previous
results
Activate this check box to keep the previous search results. Otherwise,
the search results window (Cross-References) is cleared before the
new search results are displayed.
Output to pane 2 Deactivate this check box to display the search results in the Find
Result 1 tab of the search results window (Cross-References).
Activate this check box to display the search results in the Find Result
2 tab of the search results window (Cross-References).
Element Description
Search/Replace
134 EIO0000000549 07/2012
Cross-References (Search Results)
Introduction
The Cross-References search results dialog displays the results of a search.
Representation
Description
Elements of the Cross-References dialog
Element Description
Find Result 1
tab
Find Result 2
tab
Depending on the respective check box activated in the Data Search dialog
(see page 132), the search results are displayed in one of the 2 tabs.
Displays the search results in a similar manner to the structural view in the
Project Browser.
Displays the search results in a similar manner to the functional view in the
Project Browser.
Displays the search results in Full form.
Data declaration
Path
Data usage
Displays the search results in Shortened form.
Data declaration
Data usage
Displays the search results in Flat form.
Data usage
Search/Replace
EIO0000000549 07/2012 135
Selects the previous reference of the search results.
Selects the next reference of the search results.
Jumps directly to the currently selected found occurrence of the reference.
Jumps directly to the previous found occurrence of the reference (for
example into the containing network).
Jumps directly to the next found occurrence of the reference.
Opens the Data Search dialog.
Displays/hides the Replace with area of the dialog (see page 137).
Reference This column displays the name of the instance or type
(DDT/IODDT/EFB/DFB) of the data searched for. The details displayed
depend on the display settings described above (Full, Shortened, Flat).
Type This column displays
type and reference of the data searched for,
programming language used in the sections, subroutines, events, etc.
that contain references to the data searched for.
Usage This column displays
the nature of the references to the data searched for (read only, write
only, read / write),
the data search area.
Context Specific context as defined in the Data Search Dialog (see page 132).
Unit This column displays the unit of the Location.
Location This column displays the location of the data searched for in a short form.
Element Description
Search/Replace
136 EIO0000000549 07/2012
Sorting Order
When the search results are displayed in Full or Shortened form sorting can only
be done by Reference or Type.
When the search results are displayed in Flat form sorting can also be done by
reference related columns (Usage, Context, Unit and Location).
The search results are first sorted by their path (Program, Task, Segment,
Section/Network).
The search results of sections/networks are sorted by a second key, depending on
the kind of the section/network.
References within IEC language sections (FBD, LD, SFC, ST, IL) are sorted by
row and column.
References within LL984 networks are sorted by column and row.
You can re-sort the search results by clicking on a specific column.
Re-sorting by multiple keys is not supported.
Search/Replace
EIO0000000549 07/2012 137
Cross-References (Replace)
Introduction
The Cross-References (Search Results) dialog (see page 134) displays the results
of a search.
To display the Replace with area of the dialog use the button.
Representation
Description
Elements of the Replace with area of the dialog
Element Description
Replace with
To display this area of the dialog use the button.
Enable the check boxes for those references of the search results
which should be replaced.
Enter the replacement data (only data compatible with the data being
searched for is tolerated),
or click the Down arrow to display a list providing the last 10 entries,
or click the ... button to open a Data Selection dialog to select the
instance or data to be replaced (only the instances compatible with the
instance being searched for are displayed).
Replace button Starts the replacement operation in the preselected Scope. Please refer to
Data Search dialog (see page 132).
Search/Replace
138 EIO0000000549 07/2012
Tracing Variables / Addresses
Introduction
Using the tracing feature, you can locate the occurrences of a variable/address in
an application.
Tracing
Step Action
1 Select an object in a language editor window.
Result:
The address attached to the object is displayed in the edit field of the Search Toolbar
(see page 131).
2 Start a search either
by pressing the Enter key or
by means of one of the 2 special buttons next to the edit field of the Search
Toolbar (Searching for Reading/Writing References (see page 131)).
Result:
The search results are displayed in the Cross-References dialog
(see page 134).
A direct jump is initiated to the first found occurrence of the reading/writing
reference (for example into the containing network).
A new automatic Search_<Search String> bookmark is created (to be able to
jump back later on). This bookmark is inserted into the bookmarks list like any
other manually created bookmark. Automatically created bookmarks
(see page 55) are displayed in gray and can not be renamed.
3 Double-click a search result, displayed in the Cross-References dialog, to jump to
the respective read/write location.
4 With the bookmarks feature you can mark one or more of the shown locations in the
language editor. These bookmarks can be used later on to jump to from the
bookmarks window.
5 From the bookmarks window you can also select the automatic Start of Search
bookmark for going back to the original starting position of the search.
NOTE: You can delete automatically generated bookmarks via the bookmarks
window.
EIO0000000549 07/2012 139
III
LL984 Editor
Debugging and Adjustment
EIO0000000549 07/2012
140 EIO0000000549 07/2012
EIO0000000549 07/2012 141
9
LL984 Editor
Viewing and Adjusting Variables
EIO0000000549 07/2012
Overview
This chapter describes the specifics of the LL984 Editor referring to viewing and
adjusting Variables.
For standard features please refer to Viewing and Adjusting Variables (see Unity
Topic Page
Force Mode 142
Instruction Editor 148
142 EIO0000000549 07/2012
Force Mode
Preset Force Values in Offline Mode
The Modification Values and Force Values for variables can be preset in offline
mode via animation tables. This information can be transferred to PLC later.
Presetting values can also be used for multiple modification and forcing of Boolean
variables (see Unity Pro, Operating Modes).
Preset Force Values in Project Information
The preset force values of variables are included in the
download (Transfer Project to PLC) information of a project
upload (Transfer Project from PLC) information of a project.
The Modification Value/Force Value attribute of a variable is part of the animation
table information.
Include in Upload Information
In the properties dialog of an animation table you can activate/deactivate an
additional property (Include in Upload Information).
As a default this property is activated.
This check box in the property dialog of an animation table is enabled only, if
Animation tables is activated via Project Settings General PLC embedded
data Upload information.
Implementing Forcing Mode
Press the Force button in the Operating Mode area:
EIO0000000549 07/2012 143
This mode is only available for variables responding to these conditions:
the variable must be an EBool type,
it must be a located variable,
the forcing attribute must be validated in the variable editor.
NOTE: Animation table doesnt manage analog I/O variables forcing.(For Modicon
M340 PLCs these variables can be forced in the program)
NOTE: With the animation table, it is not possible to set or reset the bit associated
to step S.x.
Forcing input and output values in a running controller can have serious
consequences to the operation of a machine or process. Only those who understand
the implications in the controlling logic, and who understand the consequences of
forced I/O on the machine or process, should attempt to use this function.
NOTE:
Before forcing outputs, make sure that you exactly understood the different behavior
of forced outputs (%M) with Modsoft/NxT/Concept and Unity Pro.
With Modsoft/NxT/Concept you cannot force outputs when the Memory Protect
switch of the Quantum CPU is set to the "On" position.
With Unity Pro you can force outputs even when the Memory Protect switch of
the Quantum CPU is set to the "On" position.
With Modsoft/NxT/Concept forced outputs maintain their values following a cold
start.
With Unity Pro forced outputs lose their disabled state following a cold start.
WARNING
You must have prior knowledge of the process and the controlled equipment and
the modified behavior in Unity Pro before attempting to force I/O or numeric values
to memory locations.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
144 EIO0000000549 07/2012
Forcing a Variable
To force a localized Boolean variable, carry out the following actions:
When a variable is forced, the letter F is displayed in front of the value:
Step Action
1 Use the mouse to select the Boolean variable.
2
Press one of the buttons corresponding to the desired value, or from
the contextual menu, execute the Force to 0 or Force to 1 commands.
To force several variables simultaneously, see Forcing several located variables
(see Unity Pro, Operating Modes).
WARNING
equipment damage.
EIO0000000549 07/2012 145
NOTE:
start.
Unforcing a Variable
To unforce a located Boolean variable, carry out the following actions:
When a variable is unforced, the letter F no longer appears in front of the value.
Creating an Offline Forcing Animation Table
To create a new animation table of forced bits from scratch, carry out the following
actions:
Step Action
1 Use the mouse to select the Boolean variable.
2
Press the . button or execute the Unforce command from the contextual
menu.
To unforce several variables simultaneously, see Unforcing several located variables
(see Unity Pro, Operating Modes)
Step Action
1 Create a new (permanent) animation table via the Project Browser.
2 Enter the memory bits you want to force either as single bits (like %M1) or as a bit
array (like M1:100).
3 Press the Force button.
4
Press the Swaps to multiple mode button.
5 Enter forcing values 0 or 1 in the Force value column.
146 EIO0000000549 07/2012
To create a new animation table of existing forced bits in the PLC, carry out the
following actions:
Build/Build changes and Save your application.
By building, the values entered in the Force value column will be included in the
upload information which is downloaded into the PLC.
Forcing by Use of an Offline Forcing Animation Table
To force values before starting the PLC, carry out the following actions:
Step Action
1 There are 3 ways to open the Forced bits animation table:
In the status bar click the red F.
In the Project Browser right-click Animations Tables and select Open Forced
Bits Table from the context menu.
Via Tools PLC Screen open the PLCScreen dialog.
In the Information tab under APPLICATION MISCELLANEOUS click the
FORCED BITS line.
2 Since this animation table is temporary only, copy and paste the animation table via
context menu of the Project Browser.
3 Make the copied animation table permanent (using the Temporary table button
).
4 In the copied Forced bits animation table press the Force button.
5
6
Press the Populates multiple values using existing forced bits button.
Result: The Force value column is populated.
Step Action
1 Open an existing application (*.STU, *.STA or an uploaded application).
2 Connect to the PLC.
3 Open the manually created/copied Forced bits animation table (see Creating an
Offline Forcing Animation Table above).
4 Press the Force button to enter forcing mode.
5
EIO0000000549 07/2012 147
NOTE:
start.
6
Press the Execute multiple button to force the bits from the preset Force
value column.
7 Now you can start your application.
WARNING
equipment damage.
Step Action
148 EIO0000000549 07/2012
Instruction Editor
Introduction
For every Unity Pro FFB you can use the Unity Pro animation tables during runtime.
(Select a function block and use Initialize Animation Table from the context menu.
Please refer to Animation Tables (see Unity Pro, Operating Modes).
But since special FFBs of the Original LL984 Block Library have parameters of array
type there will be no detailed information displayed for these parameters.
So for most of the FFBs of the Original LL984 Block Library the LL984 editor
provides another means of animation called Instruction Editor.
NOTE: For the FFBs of the Original LL984 Block Library that are not supported by
the Instruction Editor see table below.
Using the Instruction Editor
To open the Instruction Editor for an FFB during runtime, select the FFB and use
Show instruction from the context menu.
Representation
Representation of the Instruction Editor
EIO0000000549 07/2012 149
Items of the Instruction Editor
Changing the Data Type
If for example an element of the table is defined as of type floating point or 32 bit
integer, the next element is shown as disabled.
For some elements you can change the predefined data type.
For example showing a decimal also as binary.
Changing from floating point to decimal will enable the next decimal row.
Changing back to floating point will disable the next decimal row.
Bit Information
For certain memory words, bit information is also available.
In this case positioning the mouse over the Data column of such a memory word will
show information for the bits, which may be specially useful when Binary is selected
as data type format (Radix).
Item Description
Table Header displays <Pin name>:<Variable name>@<Address>
pin name of the respective function block node
name of the connected variable
Description describes the elements of the array
Address displays the address of the array element in case of located variables
In case of unlocated variables this field is empty.
In either case the corresponding data column field can be
animated/modified.
Data displays the actual value of the array element
The value can be edited by clicking this field.
Radix allows you to select the displayed data type format
Available formats:
Binary
Decimal
Floating Point
HexaDecimal
BCD
ASCII
Signed Integer
32 Bit Integer
150 EIO0000000549 07/2012
FFBs Not Supported by Instruction Editor
The following FFBs are not supported by the Instruction Editor.
Family Not Supported FFBs
CONTL_COMM L9_ID
L9_IE
MISC L9_LAB
L9_RET
EIO0000000549 07/2012 151
IV
LL984 Editor
Import / Export of LL984 Applications
EIO0000000549 07/2012
Import / Export of LL984
Applications
Overview
This part describes the specifics of the LL984 Editor.
For standard features please refer to Import / Export (see Unity Pro, Operating
Modes).
What Is in This Part?
This part contains the following chapters:
10 Import 153
11 Export 193
Import / Export of LL984 Applications
152 EIO0000000549 07/2012
EIO0000000549 07/2012 153
10
LL984 Editor
Import
EIO0000000549 07/2012
Import
Topic Page
Importing an LL984 Application 154
Importing PLCs 162
Importing Specific CPU Configurations 165
Importing Hot Standby Configurations 173
Importing I/O Modules 175
Importing Communication Settings 182
Importing Descriptors and Comments 185
Import Restrictions 187
Importing Application Parts with the Conversion Wizard 191
Import
154 EIO0000000549 07/2012
Importing an LL984 Application
Introduction
When you import an application to Unity Pro from other programming software,
some functions may behave differently.
For example:
Cold start behavior of Unity Pro LL984 applications is different from legacy LL984
applications.
Imported Concept IEC coils behave differently than imported LL984 coils.
Unit Pro MATH functions might not behave the same as legacy LL984 (overflow,
underflow, etc.).
General Message after Import
After the import check the log file (see page 161) for error and warning messages.
You have to Analyze and Build the project.
WARNING
After you imported an application program, edit the result carefully to check that
all the logic elements have been ported completely and are located correctly in
the program.
Test the application before running it to check that it performs as expected.
If necessary, edit the program to add logic elements that are missing, remove
code that is not necessary, and replace logic elements that behave differently
from their intended purpose.
equipment damage.
Import
EIO0000000549 07/2012 155
Import
To import an LL984 application use the File Open menu command.
Please refer to Open dialog (see Unity Pro, Operating Modes).
You can import the following legacy LL984 applications:
Concept Projects (*.ASC)
Modsoft Projects (*.CFG)
ProWORX32 Databases (*.PWX)
ProWORX Nxt (*.DCF)
NOTE: Imported MSTR functions are not designed to work with the Modicon M340
CPUs. After an application is converted to Unity Pro, it must be manually updated.
The MSTR function must be replaced by the READ_VAR and WRITE_VAR
functions.
For further information please refer to Import / Export of LL984 Applications
(see page 151).
Import
156 EIO0000000549 07/2012
LL984 Options Dialog (-> Target PLC Quantum)
After selecting a legacy LL984 application file, the following LL984 Options dialog
is displayed. The following graphic shows an example with a legacy Quantum LL984
source application and a Quantum selected as target PLC family.
Element Description
Application Displays the name of the legacy application to be imported.
Source PLC Family Displays the PLC family of the legacy application to be
imported.
OK Starts the import.
Cancel Displays a message . . . Conver t st ep f ai l ed, no
application is imported, and the following message is generated
in the import log file: Conver si on t er mi nat ed by User .
Symbols
Original Select this option to use the original variable names of the
legacy application in your new Unity Pro application.
Import
EIO0000000549 07/2012 157
_XYYYYY Select this option to automatically convert the legacy variable
names.
The new variable names will be composed according to the
following list:
_: an underscore will be the leading sign of the converted
variables.
X: represents the data type in the memory area.
0: %M (memory bit)
1: %I (discrete input)
3: %IM (input word)
4: %MW (memory word)
YYYYY: represents the address number.
For example _400001 stands for%MW1.
Target PLC Family
Quantum Select this option to use the Quantum as target PLC.
M340 Select this option to use the Modicon M340 as target PLC.
The Modicon M340-specific parameters for full topological
addressing are listed in a separate table below.
Long Comments
1:1 In Project Select this option to convert the long comments of your legacy
application to text that will be displayed in the Custom column
of the Data Editor.
1:n In Hyperlinked Files Select this option to convert the long comments to text files. In
this case the long comments are available as hyperlinks in the
variable Comments column of the Data Editor.
Additionally you can define a path for the created aperient text
files (in the edit field below).
Either define a relative path in the root directory of your
application.
Or use the ... button to select any other path.
The sub-folder of the hyperlink files is displayed below the edit
field.
The path defined will be written to the project settings of your
new application (Tools Project Settings General
Path Hyperlink Root Path).
Label causes SR Select this option to import a segment containing labels as an
SR segment, even if its scheduling does not express this.
Labels are allowed only in SR segments.
For details please refer to Calling Subroutines (see page 117).
Element Description
Import
158 EIO0000000549 07/2012
LL984 Options Dialog (-> Target PLC Modicon M340)
Converting a legacy LL984 application to a Modicon M340 application you can
determine the kind of addressing. By default Mixed topological / State RAM
addressing is used (option Full Topological not selected).
Mixed Topological / State RAM Addressing (-> Modicon M340)
The following graphic shows an example for converting a legacy Compact
application to a Modicon M340 application with Mixed topological / State RAM
addressing (option Full Topological not selected).
NOTE: If you want to import a legacy LL984 Compact application which uses
Modbus request to communicate with an HMI, you have to use State RAM
addressing to preserve the Modbus exchange between PLC and HMI.
Import
EIO0000000549 07/2012 159
Full Topological Addressing (-> Modicon M340)
To convert a legacy LL984 application to a Modicon M340 application with full
topological addressing, the option Full Topological has to be selected.
All word variables get a declaration with a symbol and the topological address in
the data editor, if not already present.
Input Words are copied to a mirror area of memory words, allowing SCADA
access.
Discrete words are directly addressed with topological addresses in the
programs, if no symbols are defined for them, showing in this way directly their
hardware connection to the controller.
If SCADA access is required to discrete inputs, the input bits can be copied as
well to a mirror area of memory bits by checking Copy Input Bits.
SCADA access for inputs with Full Topological checked needs modified
addresses in the SCADA system the offsets in the dialog must be added to the
original offsets and the memory areas must be used instead of the input areas.
The following graphic shows an example for converting a legacy Compact
application to a Modicon M340 application with full topological addressing.
Import
160 EIO0000000549 07/2012
For converting a legacy LL984 application to a Modicon M340 application with full
topological addressing, the following additional parameters are used:
NOTE: With this Full Topological option activated you must manually change the
access to the %I and %I Waddresses in the SCADA components.
Converting a Legacy Compact Application to Modicon M340 with Full Topological Addressing
During conversion of a legacy Compact application to a Modicon M340 application
with full topological addressing, the import automatically creates separate ST code
sections for input and output operations with copying commands to transfer I/O data
to the mirrored memory areas.
Please refer to Module Emulation (see page 178).
Import Behavior
During import of a legacy LL984 application, problems may be detected:
controller family not supported
I/O family not supported
I/O module not supported
rack count exceeded
instruction/function block not supported
non-coil in column 11
Generally such an issue does not stop the import.
Instead a message is displayed for each of these detected problems in the
Import/Export tab of the Output Window at the bottom of the Unity Pro user
interface.
Element Description
Full Topological Activate this option to convert input word addresses (3x) of the legacy
LL984 application to a separate, mirrored area of the %MWareas of the
target Modicon M340 application.
If this option is not activated, the legacy LL984 application is converted
into a State RAM Modicon M340 application.
Input Word Offset Enter the offset for the input word addresses (3x) in the mirrored area
of the %MWarea of the target Modicon M340 application.
Copy Input Bits Activate this option to additionally convert input bit addresses (1x) to
the mirrored area of the %Marea of the target Modicon M340
application.
Input Bit Offset Enter the offset for the input bit addresses (1x) in the mirrored area of
the %Marea of the target Modicon M340 application.
Import
EIO0000000549 07/2012 161
Double-click such a message in the Output Window to access the respective dialog
in your application.
If detected problems occur the following is done during import:
Not supported controllers or I/O families are replaced by a default
Quantum/Modicon M340 configuration.
Not supported I/O modules are ignored in case of Quantum as target PLC family.
Exceeding racks and their modules are ignored.
Not supported instructions are represented by empty DFBs that look identical to
the LL984 instruction. In such a case proceed as described under Not Supported
Legacy LL984 Instructions and User Loadables (see page 188).
Equation networks with questionable conversions (for example implicit type cast)
will contain the imported equation statement and an additional message.
Equation networks which are not compliant with Modicon M340 variable
alignment rules, will cause a build error during Analyze.
For details please refer to Equation Networks (see page 188).
The import of a legacy application that contains duplicated identifiers is aborted.
For details please refer to Duplicated Identifiers (see page 189).
If parts of a legacy application are not imported, after Analyze and Build of the
project an appropriate message is displayed. In this case you have to adapt the
application manually. (For example in case of Modicon M340 by selecting Mixed
topological and State RAM in the Memory Tab (see Unity Pro, Operating Modes)
of the modules and subsequently fixing the related variables).
Import Log File
After import a message informs you that the conversion and import is finished and
reminds you to have a look at the import log file.
The import log file is stored in the root directory of your application.
You have to Analyze and Build the project.
Import
162 EIO0000000549 07/2012
Importing PLCs
Introduction
During import PLCs used in legacy LL984 applications are replaced by PLCs
available in Unity Pro.
In the LL984 Options dialog box you can select either Quantum or Modicon M340
as the target PLC family.
For some legacy PLCs, it is only possible to create an default configuration without
I/Os in the selected target PLC family. This is indicated in the import log file.
The default configuration
for Modicon M340 is a local rack with CPU (BMX P34 2020, firmware V2.4) and
power supply.
for Quantum is a local rack with CPU (140 CPU 534 14A) and power supply.
984 PLCs
A 984 controller can either be:
replaced with a default Modicon M340 configuration without I/Os,
replaced by a Quantum local rack with a CPU, power supply and remote I/O
controller inserted. I/Os having direct equivalents are translated with module
specific parameters.
NOTE: The Legacy LL984 PLCs 984A, 984B and 984X do not have local I/Os.
Importing such a legacy PLC having for example Series 800 I/Os as RIO drops 1-32
will insert the first RIO drop as a Quantum local I/O and the following 2-32 RIO drops
as 1-31 Quantum RIO drops.
You have to adapt your Unity Pro hardware configuration manually.
Legacy LL984 PLC Unity Pro Quantum PLC
984A/S908
984B/S908
140 CPU 534 14A
984A/S901
984B/S901
984X
140 CPU 534 14A, no I/Os
38x48x, 68x78x 140 CPU 534 14A
484Replacement 140 CPU 534 14A, no I/Os
Import
EIO0000000549 07/2012 163
As a workaround it is recommended to adapt your legacy LL984 application by
changing the PLC to a Quantum PLC (with the appropriate I/Os) before importing
the application to Unity Pro.
If the legacy LL984 application which is imported contains a 800 I/O local drop with
more than 2 racks (e.g. 4 racks) it will be translated to a local Quantum drop with the
appropriate number of racks (e.g. 4 racks).
But as in Unity Pro a local Quantum drop can only have a maximum number of 2
racks, this Quantum drop is invalid. This is indicated by a message in the
Import/Export tab of the Output Window.
As a solution you have to drag-and-drop the modules of rack 3 and 4 to racks 1 and
2 and subsequently delete rack 3 and 4. During drag-and-drop Unity Pro will adapt
the logic.
Quantum PLCs
Quantum PLCs used in legacy LL984 applications can either be:
replaced by a default Modicon M340 configuration without I/Os,
replaced/upgraded by the next Quantum Unity Pro equivalent:
140 CPU 311 10
140 CPU 434 12A/U
140 CPU 534 14A/U
140 CPU 671 60
140 CPU 672 60
140 CPU 672 61
Please also refer to Unity Pro Hot Standby (see page 173).
Compact PLCs
If you select the option Modicon M340 as target PLC, Compact PLCs are replaced
by Modicon M340 CPU BMX P34 2020, firmware V2.4.
For Compact 16 Bit PLCs the board behavior is not emulated.
For Compact 32 Bit PLCs the board behavior is emulated as far as possible.
If you select the option Quantum as target PLC, Compact PLCs are replaced by
Quantum 140 CPU 534 14A.
If the legacy LL984 application which is imported contains a Compact drop with
more than 2 racks (e.g. 4 racks) it will be translated to a local Quantum drop with the
appropriate number of racks (e.g. 4 racks).
But as in Unity Pro a local Quantum drop can only have a maximum number of 2
racks, this Quantum drop is invalid. This is indicated by a message in the
Import/Export tab of the Output Window.
As a solution you have to drag-and-drop the modules of rack 3 and 4 to racks 1 and
2 and subsequently delete rack 3 and 4. During drag-and-drop Unity Pro will adapt
the logic.
Import
164 EIO0000000549 07/2012
Micro PLCs
Micro PLCs can either be translated with a default Quantum configuration or with a
default Modicon M340 configuration.
Momentum PLCs
Momentum PLCs can either be translated with a default Quantum configuration or
with a default Modicon M340 configuration.
584 PLCs
Converting a legacy 584 application ends up with NoConf.
ProWORX or Modsoft applications with a Modicon 584 PLC cannot be imported
correctly:
segment order may be changed
Traffic cop may not be imported correctly
Port parameter may not be imported correctly
As a workaround, it is recommended to convert the ProWORX 584 application to a
ProWORX Quantum application before importing the application to Unity Pro.
584 PLC segment order different
If in the source project there is a 584 PLC which does not support a segment
scheduler, after an import the segment order may not be correct. In this case, you
must adjust the segment order in the Project Browser.
Other PLCs
Other PLCs can either be translated with a default Quantum configuration or with a
default Modicon M340 configuration.
Import
EIO0000000549 07/2012 165
Importing Specific CPU Configurations
Introduction
With legacy LL984 applications it was possible to configure some special CPU
properties.
During import of a legacy LL984 application the following CPU properties are
converted:
Battery Coil
Timer Register
Time of Day Clock
Special Unity Pro ST sections are generated with code that reproduces these
properties.
The ST sections generated in your new Unity Pro application are:
LL984_OS_Wrapper in the MAST task
This section provides code to support the Battery Coil, Time of Day Clock and
in parts the Timer Register properties.
Timer0 in the Timer Events task
This section provides additional code to support the Timer Register property.
To provide necessary information before the application gets executed these special
sections will be executed before the application sections are executed.
You can modify or remove the code in these sections.
For the Watch Dog Time property see section below (see page 170).
Using System Bits (%SM) and System Words (%SW)
Information concerning the above mentioned properties can be read from system
bits (%SM) and system words (%SW).
Please refer to System Objects (see Unity Pro, Program Languages and Structure,
Reference Manual ).
You can adapt your application using these system bits and system words and
subsequently delete the automatically generated sections.
Battery Coil
If the battery coil is configured in a legacy LL984 application, the PLC operating
system fills the addressed coil with the battery status every scan.
This battery status provides the same information as the %S68 bit in a Unity Pro
PLC.
Therefore, if a battery coil is configured in the legacy LL984 application, the
LL984_OS_Wrapper section contains code to copy the %S68 content to the
configured battery coil (%M).
Import
166 EIO0000000549 07/2012
The needed code is:
%Mx: =%S68;
where x stands for the number of the configured battery coil in the legacy LL984
application.
Battery Coil with Modicon M340 as Target System
If the battery coil is configured in a legacy LL984 application, but the target system
is a Modicon M340, then no code is generated for the battery coil because the
Modicon M340 is not equipped with a battery.
A message in the import log file indicates that the Modicon M340 is not equipped
with a battery and that the power up behavior may differ from the legacy LL984
application.
Timer Register
The timer register is a 10ms based free running timer.
In the legacy LL984 application the configured timer register gets updated in the
system timer interrupt every 10ms.
To get a similar behavior in Unity Pro the Timer0 event section has the following
properties.
Please also refer to Properties dialog box for Timer Event Sections (see Unity Pro,
Operating Modes).
The corresponding I TCNTRL function block is called in the LL984_OS_Wrapper
section.
The LL984_OS_Wrapper section provides a free running 10 ms counter in the
configured timer %MW.
The cyclic application modifies this value and during the next timer execution, the
modified value will be incremented.
Property Value
Time number 0
Time base 10 ms
Preset 1
Phase 0
Import
EIO0000000549 07/2012 167
The Timer0 event section provides the timer register in Unity Pro.
The needed code in the LL984_OS_Wrapper section is:
I TCNTRL ( ENABLE : = t r ue ( *BOOL*) ,
RESET : = f al se ( *BOOL*) ,
HOLD : = f al se( *BOOL*) ,
EVENT : = 0( *BYTE*) ,
STATUS => TI MER0_STATUS_WORD( *WORD*) ,
VALUE => TI MER0_TI ME_REGI STER( *TI ME*) ) ;
I F( %S21 = t r ue) THEN
%MWx: =0;
END_I F;
The needed code in the Timer0 event section is:
%MWx: =%MWx+1;
where x stands for the number of the configured timer register in the legacy LL984
application.
Time of Day Clock
In some legacy LL984 PLCs it is possible using the Time of Day registers to read
and write data to the Real Time Clock chip.
The legacy LL984 TOD (Time of Day) data have the following (American) format:
In dependence of the required action (read or write) the application has to set a
control bit in the first Time of Day register.
In Unity Pro PLCs the Real Time Clock is handled using the system objects %S50
and %SW49 to %SW53.
Register Control Register Description
4XXXX Discrete 1 (MSB) 1 = set clock values
Discrete 2 1 = read clock values
Discrete 3 1 = done flag
Discrete 4 1 = error flag
4XXXX +1 Day of week (1 - 7) 1 = Sunday
4XXXX +2 Month (1 - 12) -
4XXXX +3 Day (1 - 31) -
4XXXX +4 Year (00 - 99) -
4XXXX +5 Hours (0 - 23) -
4XXXX +6 Minutes (0 - 59) -
4XXXX +7 Seconds (0 - 59) -
Import
168 EIO0000000549 07/2012
The Unity Pro system words %SW49 to %SW53 have the following format:
The LL984_OS_Wrapper section will emulate the legacy LL984 Time of Day
function using the %S50 and %SW49 to %SW53 system objects.
In case a read is required the LL984_OS_Wrapper section will read the content
from %SW49 to %SW53 convert and write this information to the configured Time
of Day word (%MW).
Then the performed read action gets shown in the control word in bit 3.
In case the %S51 shows a Real Time Clock error the bit 4 in the control word will be
set.
In case a write to the Real Time Clock is required the values in the Time of Day word
are validated.
If the values are not correct, the error flag in the control word will be set.
If case the values are valid, the data gets prepared in an unlocated word array and
the FFB WRTC_DT, which writes the PLC internal Real Time Clock, is called.
To show a successfully write the Done flag in the Time of Day Control word is set.
The needed code in the LL984_OS_Wrapper section is:
I F( ( %MWx AND 16#8000) = 16#8000) THEN
( * Wr i t e t he cl ock wi t h hel p of t he WRTC_DT EF *)
%S18 : =FALSE;
( * Val i dat i on f r omt he cl ock par amet er s *)
i f ( ( %MWx+4 > 99) ( * Year > 99 *)
OR ( %MWx+2 > 12) ( * Mont h > 12 *)
OR ( %MWx+3 >31 ) ( *Day > 31 *)
OR ( %MWx+5 >23 ) ( * Hour s > 23 *)
OR ( %MWx+6 >59 ) ( * Mi nut es > 59*)
OR ( %MWx+7 >59 ) ) ( * Seconds > 59*)
System Word Description
%SW49 day of the week
1 = Monday
2 = Tuesday
3 = Wednesday
4 = Thursday
5 = Friday
6 = Saturday
7 = Sunday
%SW50 Seconds (16#SS00)
%SW51 Hours and Minutes (16#HHMM)
%SW52 Month and Day (16#MMDD)
%SW53 Year (16#YYYY)
Import
EIO0000000549 07/2012 169
THEN
( * One or mor e of par amet er cont ai ns wr ong val ues *)
%MW10 : = 16#1000;
ELSE
UNI TY_LL984_I NTARRAY[ 1] : = ( *I NT*) SHL( I NT_TO_BCD( %
MW17 ) , 8) ;
MW15 ) , 8) ;
UNI TY_LL984_I NTARRAY[ 2] : = UNI TY_LL984_I NTARRAY[ 2]
OR ( *I NT*) \ I NT_TO_BCD( %MW16) ;
MW12) , 8) ;
UNI TY_LL984_I NTARRAY[ 3] : = UNI TY_LL984_I NTARRAY[ 3]
OR ( *I NT*) \ I NT_TO_BCD( %MW13) ;
UNI TY_LL984_I NTARRAY[ 4] : = ( *I NT*) I NT_TO_BCD( %MW14
+2000) ;
UNI TY_LL984DT : = ARI NT_TO_DT( UNI TY_LL984_I NTARRAY) ;
WRTC_DT ( UNI TY_LL984DT) ;
i f ( %S18 = TRUE) THEN
%MW10 : = 16#1000;
ELSE
%MW10 : = 16#2000;
END_I F;
END_I F;
ELSE
( *************** Real Ti me Cl ock Read******************)
I F( ( %MWx AND 16#4000) = 16#4000) THEN
( * Read t he cont ent f r omSW49. . %SW53 and conver t t he cont ent
t o a LL984 TOD f or mat *)
I F( %S51 = TRUE) THEN
%MW10 : = 16#1000; ( * Show an er r or because t he %SW
49
t i l l %SW50 ar e not val i d yet *)
ELSE
%MWx+1 : =%SW49; ( * Day of t he week cont ent *)
%MWx+2 : =BCD_TO_I NT( SHR( %SW52, 8) AND 255) ;
( * Mont h f r omt he %SW52 hi gbyt e *)
%MWx+3 : =BCD_TO_I NT( %SW52 AND 255) ;
( *day f r omt he %SW52 Lowbyt e *)
%MWx+4 : =BCD_TO_I NT( %SW53) MOD 100;
( *Year onl y f r om0 t i l l 99*)
%MWx+5 : =BCD_TO_I NT( SHR( %SW51, 8) AND 255) ;
( * Hour s f r omt he %SW51 hi gbyt e *)
Import
170 EIO0000000549 07/2012
%MWx+6 : =BCD_TO_I NT( %SW51 AND 255) ;
( *Mi nut es f r omt he %SW51 l owbyt e *)
%MWx+7 : =BCD_TO_I NT( SHR( %SW50, 8) ) ; ( * Seconds *)
%MWx : =16#6000; ( * Show t he appl i cat i on t hat
t he r ead f r omt he t i me of day cl ock i s done
,
but l et t he r ead command bi t t r ue *)
END_I F;
END_I F; END_I F;
where x stands for the first number of the configured Time of Day register in the
legacy LL984 application.
NOTE: The Day of the Week setting of Time of Day Clock is configurable in legacy
LL984applications. In Unity Pro with LL984 this system setting (%SW49) is derived
from the defined date and is not settable when using the LL984 configured TOD
clock command word Set Time Bit. This can be compensated by modifying the ST
logic in the LL984_OS_Wrapper section.
(For example code %MWx+1 : = ( %SW49 + 1) MOD 7; to get Sunday as 1st
weekday, Monday as 2nd, etc.).
Watch Dog Time
The watchdog time in legacy LL984 applications is used to stop the PLC if an
expected scan time is exceeded.
Since in Unity Pro the imported LL984 sections will run in the MAST task, the MAST
task watchdog time is the Unity Pro equivalent to the legacy LL984 applications
watchdog time.
During import
the watchdog time configured in the legacy LL984 application is converted to the
MAST task watchdog time
When the configured watchdog time is 0 (which in the legacy LL984 application
means 250 ms), the MAST task watchdog time is set to 250 ms.
the MAST task is configured as a cyclic task, since this cyclic mode is very similar
to the cyclic scan of a legacy LL984 application.
If a watchdog overflow occurs the PLC stops immediately (HALT state).
The system bit %S11 indicates a watchdog overflow. It is set to 1 by the system
when the MAST task cycle time becomes greater than the watchdog.
Import
EIO0000000549 07/2012 171
The system word %SW11 provides the watchdog time value in ms. This value can
not be modified by the program.
The maximum value of the MAST task watchdog is 1500 ms.
NOTE: Watch Dog Time settings of imported legacy LL984 applications greater
than 150 (150*10 ms =1500 ms), will cause the MAST task watch dog time to be set
at its maximum limit of 1500 ms.
Please also refer to Displaying and Modifying Task Properties (see Unity Pro,
Operating Modes).
I/O Mapped Status Word
NOTE: Compact I/O mapped status word support is not generated during import. In
case the Compact application was using the information stored in the I/O mapped
status register, you have to modify the application to use the standard Modicon
M340 module status information.
NOTE: This section only provides information for you to be considered.
In Compact legacy LL984 systems the I/O mapped status word is given in the status
table for all modules and refers to the configured slot in the rack.
For Compact PLCs the first word in the dialog I/O map contains the status word of
both the first slots (CPU) at the same time. The 3x-reference for the status
information is freely definable. E.g. if the address begins with 300101 the status
word at 300103 is for the slot 3 in the primary rack.
Partitioning of 3x register I/O mapped status area (PLC input)
3x Word Slot Backplane
3x 1 CPU slot 1. backplane
3x + 1 2 CPU slot
3x + 2 3 1. I/O module
3x + 5 6 4. I/O module 2. backplane
... ... ...
3x + 9 10 8. I/O module
... ... ...
3x + 14 15 13. I/O module
... ... ...
3x + 19 20 18. I/O module
Import
172 EIO0000000549 07/2012
Structure of I/O mapped status word
Sections with Emulation Code
After import these sections contain the instructions which are necessary for example
to copy the BMXAMO0410 status bits to the DAU204 status word, or to copy the
BMXAMI0410 status bits to the ADU206/256 status word.
You can read/write access these sections, but show at the beginning is the remark:
( * Do not change ar bi t r ar i l y *)
Please also refer to Module Emulation (see page 178).
Bit Meaning
0 - 14 module depended, in most cases not used
15 0 = module is healthy
1 = module is not healthy (reports various errors messages which are
viewable on the input status word of the module once identified)
Import
EIO0000000549 07/2012 173
Importing Hot Standby Configurations
Introduction
In legacy LL984 applications the Quantum Hot Standby extension allows you to set
the type of state RAM transfer between 140 CHS 110 00 modules in a redundant
controller system.
An initial command register and the non-transfer area can be defined. It is also
possible to define fragments from the state RAM which should be transferred in each
scan, and some fragments which should transferred with multiple scans.
This extension is only available for Quantum controllers Version 2.x that contain the
CHS loadable in the configuration.
Unity Pro Hot Standby
The Unity Pro Hot Standby control system uses the 140 CPU 671 60,
140 CPU 672 60 or 140 CPU 672 61 PLC providing a CPU with an integrated
coprocessor.
The legacy CPU (1 slot) and the 140 CHS 110 00 extension module (1 slot) are
replaced by the new 140 CPU 671 60, 140 CPU 672 60 or 140 CPU 672 61 PLC (2
slots).
In a Unity Pro Hot Standby control system the state RAM, except the non-transfer
area, becomes transferred each scan.
Therefore the non-transfer area parameter becomes converted to a Unity Pro Hot
Standby setting.
The command register and the status register allow the monitoring and controlling
of Hot Standby operations.
The status register is the third word in the non-transfer area.
Since Unity Pro supports only one non-transfer area in the %MW area, all
configured non-transfer areas in the 0x,1x, 3x references are not imported.
In case the source application uses the reference specific exclusion and additional
state RAM transfer features, the application must be adapted to the Unity Pro Hot
Standby needs.
In general only the settings made in the Quantum Hot Standby configuration
extension will be imported.
For detailed information please refer to the Hot Standby documentation
(see Modicon Quantum, Hot Standby System, User Manual).
Import
174 EIO0000000549 07/2012
Hot Standby Settings by Means of Loadables
Hot Standby settings made in legacy LL984 applications by means of the CHS
loadable, or in older LL984 series by means of the HSBY loadable, are not imported
and must be manually adjusted in the Hot Standby tab of the CPU module dialog.
The following message is displayed:
Hot st andby conf i gur at i on wi t h CHS l oadabl e i s not suppor t ed.
Hot St andby adapt i on must be made manual l y.
In this case the application must be adapted to the Unity Hot Standby needs.
The PLC, automatically inserted during import, must be replaced by the
appropriate Hot Standby PLC 140 CPU 671 60, 140 CPU 672 60 or
140 CPU 672 61.
The Hot Standby parameters have to be adjusted manually.
The HSBY or CHS DFBs, created during import, must be removed to allow a build
of the application.
Import
EIO0000000549 07/2012 175
Importing I/O Modules
Introduction
Legacy LL984 systems associate images of dynamic module data to the State RAM.
This association is expressed in the Traffic Cop dialogs.
Quantum Series
Quantum I/O modules of legacy LL984 applications are replaced by the same
Unity Pro Quantum I/O modules, if available.
Non-available modules are substituted by appropriate modules. Please refer to
Quantum Modules (see page 198).
Non-supported Quantum modules are ignored during import. A message in the
import log file reminds you to replace manually these modules after import.
A legacy LL984 Traffic Cop is converted to Unity Pro for Quantum.
For Quantum systems, Traffic Cop content can be mapped one to one because
Unity Pro provides for Quantum similar dialogs.
Special cases:
Quantum 140 XBE100-00 modules not in the right place
Depending on the application, after an import two 140 XBE 100 00 modules may
be placed in the same rack. Unity Pro displays a message during the Build.
Correct the configuration by putting a 140 XBE 100 00 in seperate racks.
Empty Quantum DIO rack is not converted to Unity Pro
If a configured Quantum DIO drop only contains a 140 CRA 2xx module, this DIO
drop is not imported. If empty drops are needed, create them in Unity Pro with just
a 140 CRA2xx module in each rack.
Modicon Compact / A120 Series I/O (General)
During import the converter tries to find for each Compact I/O module an equivalent
in the Modicon M340 or Quantum family (depending on the selected target PLC
family). Please refer to Compact Modules (see page 217).
Modicon Compact / A120 Series I/O (Modicon M340 as Target PLC Family)
For any unknown or unsupported Compact module that is not converted, a message
is generated in the import log file. The unknown / unsupported modules are replaced
by dummy modules. Any such replacement is indicated by a message in the output
window during Analyze. Double-click a message to navigate to the affected module
in the PLC bus configuration window, substitute the dummy module and adapt the
logic if required.
Import
176 EIO0000000549 07/2012
Some Compact modules are converted to 2 Modicon M340 modules
(For example, DAU208 is converted to two AMO0414 modules using voltage
sensors (see page 217)). These additional modules are integrated in the rack in
consecutive order. The slot numbers of the subsequent modules in the rack are
correspondingly increased.
Reduced Modules
When importing Compact I/O modules with Modicon M340 as target PLC family, for
compatibility reasons and to avoid address overlapping some modules are
configured with a reduced number of I/Os in Unity Pro during import. Please refer to
Reduced Modules (see page 221).
Traffic Cop
For each module the traffic cop data are evaluated and traffic cop parameters like
State RAM address and type (discrete or register/word), are used as configuration
data of the Modicon M340 module.
There are 2 different Compact families, which also have 2 different types of traffic
cop.
32-Bit CPUs: 984-E258 to 984-E285
16-Bit CPUs: 948-0120 to 948-E255
The usage of I/O modules is different between these 2 families:
With 32 Bit Compact CPUs most analog and expert modules get configured with
help of module specific configuration dialogs.
With 16 Bit Compact CPUs, I/O modules are configured at runtime with user
logic.
Emulation of Compact modules (I/O configuration parameters) is limited to projects
which contain a 32-Bit Compact CPU.
Module specific channel I/O blocks
Depending on the different Compact module parameter data the converter will only
set the Modicon M340 module specific channel I/O blocks which contain amongst
others scaling and limit parameters.
When a channel cannot be configured to perform like it has been with the Compact
family a ConvEr r or block is inserted into a converter generated ST section,
informing you that there is an issue to be solved by hardware and/or program logic
changes.
In this case the channel is configured with a default configuration (same
configuration as when manually inserting the module into the PLC bus configuration
window.
During Analyze a ConvEr r or message is displayed in the output window. Double-
click the message to navigate to the ST section which contains the ConvEr r or
block.
Import
EIO0000000549 07/2012 177
In this section the ConvEr r or block appears under a topic comment which contains
the topological address of the channel.
You can retrieve the configuration of the module by opening the module with the
topological address.
You need to configure the module with Modicon M340 possibilities and potentially
change the program logic.
After solving the issue you can acknowledge this by deleting the ConvEr r or block.
No Compact status word emulation
With exception for DAU204 there will be no Compact status word emulation in the
Unity Pro target application.
Therefore you have to check the application and communication, if such status
information was used.
No analog current channel value adaptation
There is no analog current channel value adaptation.
Compact has a special behavior. For some analog modules In cases like a range
limit or a broken wire was detected, the analog current channel value is set to a pre-
defined value. E.g. the ADU205 15 Bit sign value is set to -32768 in case an under
range has occurred.
As in Modicon M340 analog current channel values will not be adapted, you have to
check the application concerning the utilization of the analog current channel values.
Module dependent parameters
The generated Modicon M340 module parameter are module dependent and are
described in chapter Special Conversion for Compact I/O Modules (see page 223).
Specific Configuration Dialogs
If an ST section has been created during import to emulate Compact configuration
behavior, the converter creates a specific I/O module configuration with specific
configuration dialogs (see page 178).
Please also refer to Memory Tab (see Unity Pro, Operating Modes).
The Memory Management area is grayed and the choice is fixed to Mixed
Topological / State RAM.
WARNING
Check if the setting of the analog channel to a predefined value is compatible with
the application.
equipment damage.
Import
178 EIO0000000549 07/2012
In the State RAM area Format and Coding are defined by the import.
You can only delete these modules. Copy and paste of these modules is not
possible.
Module Emulation
When importing a legacy Compact LL984 application into Unity Pro with Modicon
M340 as target PLC family and the configuration of the Compact I/O modules cannot
be converted directly into a Modicon M340 module configuration, then in some
cases ST Sections will be created to emulate Compact configuration behavior.
This paragraph describes the module emulation in case of converting Compact I/O
modules to Modicon M340 modules.
The sequence of LL984 segments in the MAST task is introduced by import with an
ST section ATSTCopIn dedicated for pre-processing of input module data and
terminated with an ST section ATSTCopOut for post-processing of output module
data.
In the header of the configuration dialog of a module with pre- or post-processing,
the original module name is shown after the introduction Emulation module.
For orientation, both ST sections show a list of comments, for each module the
topological position, the generated module name and the original module name.
For example: ( * 0. 0 BMXP342020 ( 984- E258) : *) .
Following the module comment line, module specific processing is implemented.
Emulation Segments Configuration Dialog with Module
Emulation Hint
Import
EIO0000000549 07/2012 179
For example:
ADU256, DAU204: construction of the specific module status word
ConvError notes for module channels which cannot be automatically converted,
e.g. due to manual-only configured original modules (e.g. ADU 216) or non-
available resolution
ADU 204-254: thermocouple scaling
If the address conversion option Full Topological is selected, copying code for the
module data between topological address and mirror areas in %Mor %MWmemory is
placed into these sections as well.
Modicon Compact / A120 Series I/O (Quantum as Target PLC Family)
Compact I/O modules are replaced by Quantum modules.
Please refer to Compact Modules (see page 217).
Since most Quantum I/O modules provide larger data size than the Compact I/O
modules, in many cases an overlap can occur and you may have to adjust the
application.
Not supported Compact modules are ignored during import.
In case there is no equivalent I/O module available in the Quantum family the slot
will be left empty and a hint will be generated in the log file.
A message in the import log file reminds you to replace these modules after import
by yourself.
Special Cases:
EHC10500 parameters may not be correctly set after conversion of a ZAE 20
In this case, after application import you get a message as:
{Devi ce ( 1. 4) 140 EHC 105 00}: Par amet er <DEFAULT TO RELATI VE
SET> out of r ange ( val ue ( 0) not i n [ 1 t o 1] )
To correct this issue you have to delete the module and reconfigure it, with the
proper parameters from the legacy application.
Application containing 140MSB10100 or/and 140EIA92100 ends up with
NoConf
When a legacy Compact project containing a B MOT201 board is imported,
Unity Pro PLC goes in NoConf state after download.
During configuration import the B MOT201 is converted to a 140 MSB101-00
Module. This module is not correctly converted. Unity Pro OS detects a wrong
parameter size and goes in NoConf state.
This issue may also appear using 140 EIA921-00 modules.
As a workaround you have to delete the module from the Unity Pro configuration,
create it again and manually enter the parameters from the legacy application.
Import
180 EIO0000000549 07/2012
Series 800
Available direct equivalents for series 800 are replaced by the same module.
Logically equivalent, but electrically different modules are treated commonly.
Please refer to Series 800 Modules (see page 205).
8 Bit module must be mapped on 16 bit addresses
After import of a legacy LL984 application to Unity Pro, in some cases you get the
message:
S800 8 Bi t modul e must be mapped on a 16( +1) bi t boundar y
In this case you have to map the 8 Bit module on S800 drop to 16 bit addresses.
Unity Pro handles the data mapping on 16 bit boundaries.
Invalid Unity Pro Drop Configuration
If an imported legacy LL984 application contains a drop with more than 2 racks of
Series 800 I/O modules, it is translated to a local Quantum drop with the same
number of racks. This configuration is invalid with Unity Pro as a local Quantum drop
can only have a maximum of 2 racks. This is indicated by a message in the
Import/Export tab of the Output window.
As a solution, for a Quantum drop with 3 racks, drag-and-drop the rack 3 modules
to racks 1 and 2 and then delete rack 3. During drag-and-drop Unity Pro
automatically adapts the logic.
Series 200/500
Series 200/500 I/O modules are generically replaced by two 800 Series I/O
modules.
Unity Pro and legacy LL984 systems support these I/O families generically, so
logically similar modules are treated commonly.
Please refer to Series 200/500 Modules (see page 211).
Series 200 I/Os are not imported properly
During import of a ProWORX or Modsoft application with a Modicon 984B controller,
the Traffic cop may not be imported properly.
The imported project will contain more channels with I/O modules than configured
in the source project.
As a workaround it is recommended to replace the PLC of your legacy LL984
application with a Quantum PLC before importing the application to Unity Pro.
Import
EIO0000000549 07/2012 181
SY/MAX
Available direct equivalents for SY/MAX I/O modules are replaced.
Please refer to SY/MAX Modules (see page 214).
Not supported SY/MAX I/O modules are ignored during import.
A message in the import log file reminds you to replace these modules after import
by yourself.
Series 300, DCP
Series 300 and DCP I/O families are not supported.
Momentum
Momentum I/O families are not supported.
Micro
Micro I/O families are not supported.
Parameter <NOT USED>
After import of a legacy LL984 application to Unity Pro, in some cases you get the
message:
Par amet er <NOT USED> out of r ange [ val ue 0] not i n [ 1 t o 1]
Delete the module configuration and reconfigure it with the correct parameters from
the legacy application.
Import
182 EIO0000000549 07/2012
Importing Communication Settings
Introduction
Communication features are offered in legacy LL984 applications as configuration
extensions.
Only the following extensions are converted during import:
TCP/IP communication
Peer Cop
I/O Scanner
SY/MAX Ethernet
TCP/IP Communication
The TCP/IP extension enables the controller to work with a TCP/IP communication
card.
Controllers support different numbers of TCP/IP communications cards:
Quantum 113, Revision 2 and 213 Revision 2 controllers support 2 cards
Quantum 424, Rev. 2 supports up to 6 cards
M1E Momentum controllers only support 1 card and the head number is fixed to
1.
During import of a legacy LL984 application the following TCP/IP parameters are
converted:
card number (1-6)
slot number (1-16)
IP address (1-255).(1-255).(1-255).(1-255) from the IP Address, Subnet Mask,
and Gateway IP fields.
0.0.0.0 indicates an undefined address.
Framing Type (Ethernet II or IEEE 802.3)
IP Address Selection
Extension: On power up, PLC reads its TCP/IP addressing information from
this extension.
BOOTP: On power up, the PLC requires a BOOTP server to supply TCP/IP
addressing information.
For further information please refer to Quantum TCP/IP Configuration
(see Quantum with Unity Pro, TCP/IP Configuration, User Manual).
Import
EIO0000000549 07/2012 183
Peer Cop
The Peer Cop extension provides data transfer between 2 or more controllers on a
peer-to-peer network, as well as linking multiple networks using the S985
communication card.
Peer Cop configures data blocks to be continuously transferred (once per scan)
between nodes on a Modbus Plus network.
Data can be broadcast to all nodes on a single link (Global I/O) or between specific
Modbus Plus nodes on a link (Specific I/O).
A maximum of 32 data registers or 512 (for example, 32*16) I/O points can be
transferred to or read from a controller at a time.
Peer Cop is supported by the by Compact with A145 and the E-Series CPUs,
Momentum and Quantum controllers equipped with NOK Modbus+ adapters.
Up to three Links of the Peer Cop can be configured and edited.
During import of a legacy LL984 application the Peer Cop parameters are converted
to Unity Pro.
For further information please refer to Peer Cop Configuration (see Quantum with
Unity Pro, Modbus Plus Network Modules, User Manual).
I/O Scanner
During import of a legacy LL984 application (with Quantum as target PLC family) the
following I/O Scanner parameters are converted:
Transaction type
Direct
Creates a single transaction in the local device. Data is transferred regardless
of the programming of the remote device. This option is simpler than Link
Client/Server, as the target device needs no additional program to verify its
operation.
Link Client/Server
Creates a pair of matching transactions, one in each device. The server makes
a request from a client, which then responds to that request. This is a more
complex option than Direct transactions to set up and maintain.
IP address in the local device IP address field in the standard IP format (1-
255).(1-255).(1-255).(1-255).
For Quantum, select the slot that the NOE (or similar Ethernet adapter) card
resides in.
Target PLCs with which to communicate.
These target PLCs are called remote devices. At least one remote device must
be defined before proceeding - IP address of the PLC for the remote device.
If using a Quantum PLC, select the slot that the NOE (or similar Ethernet adapter)
card resides.
Import
184 EIO0000000549 07/2012
Transactions
To transfer data from one device to another a transaction is required.
Up to 128 transactions may be created, except if you are using the M1E PLCs,
then only 64 transactions can be supported.
Function (Read/Write)
From and To (4xxxx addresses)
Length (Number of register fields in the Read from Remote and Write to
Remote device area).
For further information please refer to Configuring the Quantum I/O Scanner
(see Quantum with Unity Pro, TCP/IP Configuration, User Manual).
NOTE: With Unity Pro it is not allowed to set the parameters Health Timeout and/or
Repetitive Rate to zero. (With legacy LL984 application it was possible to set these
parameters to zero).
Device Control Block is not imported for ProWORX projects.
Importing a legacy LL984 application with a configured Ethernet I/O Scanner
configuration, the Device Control Block configuration is not imported.
After the import, reenter the Device Control Block address in the Unity Pro Ethernet
configuration window.
SY/MAX Ethernet
The SY/MAX configuration extension allows you to properly access and configure
up to 6 SY/MAX RIO cards.
This extension is only available when using Quantum controllers, Revision 2 or later.
During import of a legacy LL984 application the following SY/MAX Ethernet
parameters are converted:
card number (1-6)
Module Drop Number (-1 to 99). Set to -1 if the drop is not defined.
Backplane Slot (number of the slot (0 to16) that the RIO card inhabits.
Set to 0 to remove a module.
Retry Count (1 to 255)
Timeout (1 ms to 65535 ms)
For further information please refer to Quantum Ethernet Modules (see Quantum
with Unity Pro, Experts and Communication, Reference Manual).
NOTE: If the content from SY/MAX configuration extension is not imported to the
Unity Pro target application, you have to check and adjust the NOE311/NOE351
configuration parameter in the Unity Pro target application.
Import
EIO0000000549 07/2012 185
Importing Descriptors and Comments
Introduction
During importing an application (see page 154) the following elements of a legacy
LL984 application are imported:
Descriptors
Short comments
Long comments
Page titles
Descriptors
The descriptors (1-9) of variables are imported and can be displayed and edited
using the Data Editor or the Data Properties dialog.
Please refer to Configuring the Data Editor Columns (see page 13).
NOTE: The symbol descriptors in a Modsoft project are converted into short
comments in a Unity LL984 project.
NOTE: Bit-Descriptors from Modsoft or ProWORX are not converted as they do not
have an equivalent in a Unity LL984 project.
Short Comments
The short comment of a variable is imported and displayed as the Comment
property of the variable.
It can be displayed and edited using the Data Editor or the Data Properties dialog.
The Comment can also be displayed in the LL984 Editor. Please refer to Network
Display (see page 66).
A short comment associated to a network is imported as a network comment.
Long Comments
During import of an application you can select on of the 2 options:
1:1 In Project
1:n In Hyperlinked Files
Please refer to Additional LL984 Options Dialog (see page 156).
Import
186 EIO0000000549 07/2012
If you select
1:1 In Project, the long comment of a variable is imported and displayed as the
Custom property of the variable.
A long comment associated to a network is imported as a network comment.
1:n In Hyperlinked Files, the long comments are converted to text files.
If there is a already a comment in the variable Comments column, this
comment will be colored in blue and works as a hyperlink to the text file.
If there is no comment in the variable Comments column, a relative path
colored in blue, is displayed working as a hyperlink to the text file.
A long comment associated to a network is imported as a hyperlink for the
network with User Name equal to the network name and Target Path equal to
the text file, where the long comment is stored.
This hyperlink can be activated via the Project Browser.
The hyperlinks are available in the variable Comments column of the Data Editor
and in the Data Properties dialog.
The Comment can also be displayed in the LL984 Editor. Please refer to Network
Display (see page 66).
NOTE: Long comments will not be included in upload information.
Hyperlink for a Network Long Comment
In case a hyperlink for a network long comment is not created after import you have
to create it manually.
The long comment files are stored at the location which was selected during import.
The name of the long comment files will be _LCx, where x is the long comment
number.
In the hyperlink properties dialog (accessible via the network context menu) it is
possible to browse to the selected long comment folder and select the wanted long
comment file.
Page Titles
The Page Title of a legacy LL984 network will be imported as network name.
The Page Title of a legacy LL984 network can be up to 64 characters long.
As in Unity Pro network names are limited to 32 characters, the network names are
truncated and a numerical suffix is automatically appended to make it unique.
Blank characters are replaced by underscores.
You can edit the network name using its Properties dialog via context menu (right
mouse click) or directly in the Project Browser.
The unchanged Page Title is displayed in the network comment.
Import
EIO0000000549 07/2012 187
Import Restrictions
Macros
ProWORX32, ProWORX Nxt, Modsoft SFC and Modsoft macros are not converted
nor supported.
Data Watch Windows
During import, Data Watch Windows used in legacy LL984 applications, are
converted to animation tables in Unity Pro.
Please refer to Forcing Variables via Animation Tables (see page 142) and
Animation Tables (see Unity Pro, Operating Modes).
Animation Tables
Whether animation tables are imported or not depends on your legacy LL984
application:
Concept
With Concept all animation tables (*.RDE) in the application folder are imported
to Unity Pro, but with no connections to the application you are importing.
Modsoft
Modsoft animation tables (*.RFD) are not imported to Unity Pro.
You have to enter them manually.
ProWORX32
With ProWORX32 only the last opened animation table, which is stored with the
application file, is imported to Unity Pro. External files (*.DWA) are not imported
to Unity Pro.
ProWORX Nxt
ProWORX Nxt animation tables (*.DWW) are not imported to Unity Pro.
You have to enter them manually.
Hot Standby
Import supports only Quantum Hot Standby settings made by means of the Hot
Standby configuration extension.
For more information please refer to Importing Hot Standby Configurations
(see page 173).
Import
188 EIO0000000549 07/2012
Not Supported Legacy LL984 Instructions and User Loadables
If the imported LL984 Ladder Logic application contains unsupported LL984 logic
instructions or user loadables, the following occurs:
1. The import log identifies the unsupported instruction(s) and/or loadable(s) with a
message: An unsuppor t ed i nst r uct i on or l oadabl e f ound.
2. The import places an empty DFB that looks identical to the LL984 instruction in
the same location(s) in logic.
3. The empty DFB contains ST logic:
{ConvEr r or ( Unsuppor t ed i nst r uct i on or l oadabl e f ound.
Pl ease see t he i mpor t l og f or mor e det ai l s) ; }; .
This code is not executable and causes a notification during Analyze of the
project.
If empty DFBs are part of the imported application, proceed as follows:
You can locate the empty DFBs logic instances using one of several methods:
Use the Search icon in the tool bar.
Double-click the DFB in the Project Browser.
Right-click the DFB in DFB Types and select Initialize search from the context
menu.
For legacy LL984 instructions that are not supported by Unity Pro please refer to Not
Implemented Function Blocks (see Unity Pro, Original LL984, Block Library).
Equation Networks
If the imported LL984 Ladder Logic application contains equation networks with
questionable conversions (for example implicit type cast), the following occurs:
The respective Equation Network Block contains the imported equation
statement and an additional message:
Pl ease check t he i nt egr i t y and cor r ect ness of t hi s equat i on
bef or e pr oceedi ng.
This message causes a notification during Analyze of the application.
After verification of the Equation Network Blocks correctness, you must delete
this message to achieve a successful Build.
After import of an equation network, data type suffix of I NT variables S is different
from the suffix created by the LL984 Editor.
Step Action
1 Delete or comment out the empty DFB ST to eliminate these notifications during
the analyzlis of the application.
2 Create replacement DFB logic using available IEC instructions if the
unsupported instruction or user loadable is still required in the application.
3 Contact the local Schneider Electric representative if assistance is necessary.
Import
EIO0000000549 07/2012 189
The generated suffixes are:
Importing Equation Networks to Unity Pro for Modicon M340
Modicon M340 has specific variable alignment rules, which are different from
Quantum.
Depending on the legacy LL984 application, the variable type alignment of the
imported equation network might not match the Modicon M340 alignment rules if
you:
import a legacy LL984 application containing equation networks
select Modicon M340 as target platform
In this case, a build error is created during Analyze of the application.
Modify the equations to match the Modicon M340 alignment rules, to achieve a
successful Build.
Modicon M340 alignment:
BOOL and BYTE types are aligned on either even or uneven bytes.
I NT, WORD and UI NT types are aligned on even bytes.
DI NT, UDI NT, REAL, TI ME, DATE, TOD, DT and DWORD types are aligned on
double words.
Duplicated Identifiers
If the imported LL984 Ladder Logic application contains duplicated identifiers, i.e for
example a network and a segment have the same name, the import is aborted.
The following message is displayed:
Obj ect cr eat i on f ai l ur e. Dupl i cat e i dent i f i er .
You have to open the application with your legacy LL984 software (e.g. Concept,
ProWORX32 etc.) and you have to take care for unique identifiers.
After that you can import your legacy application again.
Data Type Import LL984 Editor
INT S I -
DINT L DI -
UDINT UL UD
REAL F R
WORD W W
DWORD DW DW
Import
190 EIO0000000549 07/2012
Drop Status Word
In case I/O mapped status words are configured for Quantum or Compact I/O drops,
the Concept or ProWORX software prevents a double usage of 3x references from
this I/O mapped status area.
The size of the area depends on the highest configured slot number (E.g.: If in slot
number 8 a module is configured the usage as input words of the first four 3x
references from the module status area is prevented).
In case of Unity Pro with a Quantum PLC, independent of the highest configured
slot, 8 %IW words for the primary rack and additional 8 %IW words for a secondary
rack are reserved and cannot be used as input references.
Because of this, it is possible that after import an I/O module is mapped to a %IW
address which was allowed in the legacy application but which leads to an error
message during Build of the Unity Pro application.
In this case you must remap the I/O modules or the I/O mapped status area, and
adapt the application concerning these changed %IW addresses.
Import
EIO0000000549 07/2012 191
Importing Application Parts with the Conversion Wizard
Introduction
The conversion wizard is an integrated part of Unity Pro.
You can use it to
convert applications, exported out of legacy applications (PL7, Concept, LL984)
to Unity Pro.
convert legacy applications partially or as a whole
remap I/O objects (channels, variables etc.) during conversion by means of the
wizard.
adapt the hardware configuration of the new application concurrently in Unity Pro.
modify the amount of used memory in the CPU.
For detailed information please refer to Conversion Wizard (see Unity Pro,
Operating Modes).
Import
192 EIO0000000549 07/2012
EIO0000000549 07/2012 193
11
LL984 Editor
Export
EIO0000000549 07/2012
Export
Exporting/Importing LL984 Segments/Networks
Introduction
You can export/import LL984 segments and networks from the Structural View of
the Project Browser.
Restrictions
In contrast to the Export dialog for other language sections, the dialog for LL984
segments/networks does not provide the With SR check box, because the
subroutine networks called in the exported networks are not exported.
This is done because the called subroutine number can be given as a parameter at
runtime, so you do not know in advance which subroutines are really called.
If you want to use the called subroutines in another application, you must export and
re-import the whole LL984 subroutine segment.
Files Generated
Files with the following extensions are generated during export:
*.X9S for LL984 segments
*.X9N for LL984 networks
The created files also include the definitions of variables and variable types used
inside the exported segments and networks.
Exporting LL984 Segments/Networks
Step Action
1 Select the element to be exported (LL984 segment/network).
2 Right-click and select Export from the context menu or use the File Export
menu command.
3 Select the destination directory for the export and enter the file name.
4 Select / deselect the With DDT/With DFB options.
Export
194 EIO0000000549 07/2012
Importing LL984 Networks
To import a *.X9N file (LL984 network) you have to select an LL984 segment node
in the Structural View of the Project Browser
Right-click and select Import from the context menu or use the File Import menu
command.
In case of naming conflicts for the network name or the used variables and variable
types an Import Trouble Report dialog will be displayed. Please refer to Managing
Conflicts (see Unity Pro, Operating Modes).
Importing LL984 Segments
To import a *.X9S file (LL984 segment) you have to select Sections or SR Sections
in the Structural View of the Project Browser.
Right-click and select Import from the context menu or use the File Import menu
command.
In case of naming conflicts an Import Trouble Report dialog will be displayed.
Importing a *.X9S file to the SR Sections node can end up in the existence of more
than one LL984 segment under SR Sections.
During Analyze this will be checked and will lead to an analyze error.
In this case move the LL984 subroutine networks needed into one LL984 SR
segment and delete the other LL984 SR segments.
Even if the Ladder Logic (LL984) option under Tools Project Settings
Program Languages is not set, *.X9S files can be imported without error
messages and the corresponding segments and networks will be created. But in this
case later during Analyze an i ncor r ect l anguage message will be raised for
these segments and networks.
In the context menu of segments the menu entry to import networks is disabled in
case the Ladder Logic (LL984) option is not set.
5 Click the Export button.
6 A message in the Import/Export tab of the output window informs you when
export is completed.
Step Action
EIO0000000549 07/2012 195
LL984 Editor
EIO0000000549 07/2012
Appendices
What Is in This Appendix?
The appendix contains the following chapters:
A Supported / Not Supported I/O Modules 197
B Special Conversion for Compact I/O Modules 223
196 EIO0000000549 07/2012
EIO0000000549 07/2012 197
A
LL984 Editor
Supported / Not Supported I/O Modules
EIO0000000549 07/2012
Supported / Not Supported I/O
Modules
Topic Page
Quantum Modules 198
Series 800 Modules 205
Series 200/500 Modules 211
SY/MAX Modules 214
Compact Modules 217
198 EIO0000000549 07/2012
Quantum Modules
Supported Quantum Modules
Analog input
Analog output
Digital input
Legacy Module Description Substituted by Unity Pro
Module
ACI030-00 Analog 8 Channel Unipolar Input available in Unity Pro
ACI040-00 16 CH Analog Current Module available in Unity Pro
AII330-00 I.S. Analog Input available in Unity Pro
AII330-10 I.S. 8CH Analog Input Current available in Unity Pro
ARI030-10 8 Channel RTD available in Unity Pro
ATI030-00 8 Channel Thermocouple available in Unity Pro
AVI030-00 8 Channel Bipolar, Analog Input available in Unity Pro
Module
ACO020-00 4-20 mA Analog Output Module available in Unity Pro
ACO130-00 8 Channel Output Module available in Unity Pro
AIO330-00 I.S. Analog Output available in Unity Pro
AVO020-00 Analog Voltage Output Module available in Unity Pro
Module
DAI340-00 24 VAC ISO 16 Input Module available in Unity Pro
DAI353-00 24/48 VAC 32 Input Module available in Unity Pro
DAI440-00 48 VAC 2x8 Input Module available in Unity Pro
DAI453-00 48 VAC 32 Input Module available in Unity Pro
DAI540-00 115 VAC 16 Input Module Isolated available in Unity Pro
DAI543-00 2x8 115 VAC Input Module available in Unity Pro
DAI753-00 230 VAC 4x8 Input Module available in Unity Pro
DCF077-00 GPS or DTS Time Module available in Unity Pro
DDI153-10 5 VDC 4x8 Input Module available in Unity Pro
EIO0000000549 07/2012 199
Digital output
DDI353-00 24 VDC 32 Input Module 140DDI35310
DDI353-10 24 VDC True Low 32 Input Module available in Unity Pro
DDI364-00 24 VDC 6x12 Fast Input Module available in Unity Pro
DDI673-00 125 VDC 24 Point I/P Module available in Unity Pro
DDI841-00 10-60 VDC 16 Input Module available in Unity Pro
DDI853-00 10-60 VDC 32 Input Module available in Unity Pro
DII330-00 I.S. Digital Input available in Unity Pro
DSI353-00 24 VDC 32 Point Input Module available in Unity Pro
HLI340-00 Hi-Speed/Latch/Interrupt available in Unity Pro
Module
DAO840-00 24-230 VAC 16 Output available in Unity Pro
DAO842-10 100-230 AC 16 Output
Module
available in Unity Pro
DAO853-00 24-230 VAC 4x8 Out available in Unity Pro
DDO153-10 5 VDC 4x8 Output Module available in Unity Pro
DDO353-00 24 VDC 32 Output Module available in Unity Pro
DDO353-01 24 VDC 32 Point Output
Module
DDO353-10 24 VDC True Low 32
Output Module
DDO364-00 24 VDC True High 96
Output Module
DDO843-00 10-60 VDC 16 Output available in Unity Pro
DDO885-00 125 VDC 12 Point O/P
Module
DIO330-00 I.S. Digital Output available in Unity Pro
DRA840-00 16 Output Relay available in Unity Pro
DRC830-00 8 Output ISO Relay available in Unity Pro
DVO853-00 10-30 VDC Verified Output
Module
Module
200 EIO0000000549 07/2012
Generic analog
Mixed
Communication
Module
ACI050-00 32 CH Analog Current In GENANAIO
ACI051-00 32 CH Analog Voltage/Current GENANAIO
ACI052-00 32 CH Analog Voltage/Current GENANAIO
AUI040-00 16 Channel Universal Input Module GENANAIO
AVI050-00 32 CH Analog Voltage In GENANAIO
Module
AMM090-00 Analog In/Out 4Ch/2Ch available in Unity Pro
DAM390-00 16/8 Bidir 24 VAC 140DAM59000
DAM490-00 16/8 Bidir 48 VAC 140DAM59000
DAM590-00 16/8 Bidir 120 VAC available in Unity Pro
DCP Distributed Control Module GENNOM
DDM390-00 16/8 Bidir 24 VDC available in Unity Pro
DDM690-00 125 VDC 4 Input/4 Output HPO Module available in Unity Pro
EHC105-00 High Speed Counter 5 Channel available in Unity Pro
EHC202-00 High Speed Counter available in Unity Pro
EIA921-00 1 Channel AS-I Module Interface available in Unity Pro
ERT854-10 32 Point Smart Digital Input available in Unity Pro
ESI062-10 2 Channel ASCII Interface available in Unity Pro
MSB101-00 Motion Inc Enc available in Unity Pro
MSC101-00 Motion Enc/Res available in Unity Pro
NOA611-00 INTERBUS-S Master Module GENNOM
NOA611-10 INTERBUS-S Master with PCP GENNOM
NOG111-00 Bitbus Master GENNOM
Module
CRA211-10 DIO Drop MB+ available in Unity Pro
EIO0000000549 07/2012 201
Controller
CRA931-00 RIO Drop S908 140CRA93X00
CRA932-00 RIO Drop S908 140CRA93X00
CRP811-00 Profibus DP Interface Module PTQPDPMV1
CRP931-00 RIO Head S908 140CRP93X00
CRP932-00 RIO Head S908 140CRP93X00
NOE211-00 Ethernet TCP/IP Twisted Pair 140NOE77111
NOE251-00 Ethernet TCP/IP Fiber Optic 140NOE77111
NOE311-00 Ethernet SY/MAX Twisted Pair available in Unity Pro
NOE351-00 Ethernet SY/MAX Fiber Optic available in Unity Pro
NOE771-00 Ethernet TCP/IP 10/100 Megabit available in Unity Pro
NOE771-10 Factorycast Web Server 140NOE77111
NOM212-10 MB+ Drop Interface Card 140NOM2XX00
NOM2XX-00 MB+ Drop Interface Card available in Unity Pro
NWM100-00 Factory Cast HMI Web Server available in Unity Pro
P910 - J892/P8XX
Module
140CPU65150 controller available in Unity Pro
434/534 Controller 140CPU53414A/U
CPU-113-2 Controller 140CPU31110
CPU-424-X Controller 140CPU43412A/U
CPU-434 Controller 140CPU43412A/U
CPU-534 Controller 140CPU53414A/U
Module
202 EIO0000000549 07/2012
Rack
Power supply
Backplane expander
Module
XBP-002 - available in Unity Pro
XBP--004 - available in Unity Pro
Module
CPS-111 115/230V AC Power Supply 3A available in Unity Pro
CPS-114 115/230V AC Power Supply 10A available in Unity Pro
CPS114-20 115/230V AC Power Supply 10A available in Unity Pro
CPS-124 115/230V AC Power Supply RED 8A available in Unity Pro
CPS124-20 115/230V AC Power Supply RED 8A available in Unity Pro
CPS-211 24 V DC Power Supply 3A available in Unity Pro
CPS-214 24 V DC Power Supply 8A available in Unity Pro
CPS-224 24 V DC Power Supply RED 8A available in Unity Pro
CPS-414 48 V DC Power Supply SUM 8A available in Unity Pro
CPS-424 48 V DC Power Supply RED 8A available in Unity Pro
CPS-511 125V DC Power Supply 3A available in Unity Pro
CPS-524 125V DC Power Supply 8A available in Unity Pro
CPS524-20 125V DC Power Supply 10A available in Unity Pro
XBE-100 - available in Unity Pro
Legacy Module Description Substituted by Unity Pro Module
XBE100-00 Backplane Expander available in Unity Pro
EIO0000000549 07/2012 203
Not Supported Quantum Modules
Mixed
Communication
Counter
Motion
Legacy Module Description
AMM090-0X Analog-4 Ch 4-20mA Output
DEVNET-08 16 Register Devicenet Scanner
DEVNET-32 64 Register Devicenet Scanner
EHC204-00 High Speed Counter 4 Channel
EHC208-00 High Speed Counter 8 Channel
GPS100-00 IRIG-B Time Sync Interface
I2T010-00 I2T 10 Input / 10 Output
I2T016-00 I2T 16 Input / 16 Output
MPM204-00 4 Channel Meter Proving Module
NOL911-XX LonWorks Interface
NOP911-00 Profibus FMS Interface Module
QSPXM Seriplex Master
SERX53-00 Sequence Of Events Recorder
NOE511-00 Ethernet MMS Twisted Pair
NOE551-00 Ethernet MMS Fiber Optic
MCI186X MultiTurn Resolver Interface
MCI18X1X2 Resolver Interface Module
MCI18X3X4 Single Turn Interface
MMB102-00 Two axis motion with incremental
MMB104-00 Four axis motion with incremental
MMC120-0X 2-Axis Motion Control
MMD102-00 Two axis absolute motion
MMD104-00 Four axis absolute motion
204 EIO0000000549 07/2012
Miscellaneous adapter
CHS110-00 Hot Standby
HRT100-00 HART Serial Communications Card
MDCCRDL-6 Bus Module, Cradle
QUCM-SE NRD Universal Comm
XCP900-00 Battery Backup
EIO0000000549 07/2012 205
Series 800 Modules
Supported Series 800 Modules
Analog input
Analog output
Module
B863-001 4 Channel Register Input B863
B873 4 Channel Analog Input B873
B873-001 4-20mA,1-5V 4 Channel Analog Input B873
B873-002 4-20mA,1-5V 4 Channel Analog Input B873
B873-011 -10 V to 10 V 4 Channel Analog Input B873
B873-200 V/A, Thermo, RTD, Strain Gauge Input B873
B875 8 channel. Analog Input B875
B875-001 4-20mA, 1-5V 8 Channel Analog Input B875
B875-002 4-20mA, 1-5V 8 Channel Analog Input B875
B875-101 Fast selectable 8 chan. Analog Input B875
B875-102 Fast selectable 8 chan. Analog Input B875
B875-111 Select. 8 channel Differential Input B875
B875-200 V/A, Thermo, RTD, Strain Gauge Input B875
B877-111 Select. 16 channel Single Ended Input B877
Legacy Module Description Substituted by Unity
Pro Module
B846 Analog MUX B846
B846-001 Analog MUX B846
B846-002 Analog MUX B846
B862-001 4 Channel Register Output B862
206 EIO0000000549 07/2012
Digital input
B872 Selectable 4 Channel Voltage Output B872
B872-002 4-20 mA,1-5V 4 Channel Analog Output B872
B872-011 Selectable 4 Channel Voltage Output B872
B872-100 4-20mA 4 Channel Current Output Module B872
B872-200 Selectable 4 Channel Voltage Output B872
Module
B803-008 115 VAC 8 Point Input Module B803
B807 32 Point Input Module B807
B817 16 Point Isolated Input Module B817
B817-116 115 VAC 16 Point Isolated Input Module B817
B817-216 230 VAC 16 Point Isolated Input Module B817
B821 8 Point Input B821
B821-008 10-60 VDC 8 Point Input B821
B821-108 10-60 VDC 8 Point Input B821
B825-016 24 VDC 16 Point Input B825
B829-116 5V TTL 16 Input B829
B835 8 Point Input B835
B837-016 24 VAC/DC 16 Point Input B837
B849-016 48 VAC/DC 16 Point Input Module B849
B853-016 115 VAC/125 VDC 16 Input B853
B863-03w 4 Channel Register Input B863
Pro Module
EIO0000000549 07/2012 207
Digital output
B881-001 24 VDC 16 Point Latched Input B881
Pro Module
B802-008 115 VAC 8 Point Output Module B802
B804 115 VAC 16 Point Output Module B804
B806 32 Point Output Module B806
B810-008 115 VAC 8 Isolated Output Module B810
B814-001 NO Power Relay 8 Point Output Module B814
B814-002 NC Power Relay 8 Point Output Module B814
B814-108 NO/NC Power Relay 8 Point Output Module B814
B818-032 24 VDC 32 Point Output B818
B820-008 10-60 VDC 8 Point Output B820
B826-032 24 VDC 32 Point Output -
B828-016 5V TTL 16 Point Output B828
B836-016 12-250 VDC 16 Point Output Module B836
B840-108 NO/NC Reed Relay 8 Point Output Module B840
B842-008 NO/NC Reed Relay 8 Point Output Module B842
B881-108 115 VAC 8 Point Protected Output Module B881
B882-032 24 VDC Diagnostic Output Module B882
Module
208 EIO0000000549 07/2012
Mixed
Communication
Pro Module
B881-508 125 VDC 8 Point True High Output Module B881
B882-239 0-30 kHz 2 High Speed Up-Counter Module B882
B883 10 Point Input Module B883
B883-001 0-50 kHz 2 High Speed UP/Down Counter B883
B883-101 4 kHz CAM ABS Encoder Input,8 Disc Out available in Unity Pro
B883-111 1 kHz CAM with Velocity compensation available in Unity Pro
B883-200 10 Thermocouple Input Module B883
B883-201 8 RTD Input Module B883
B885-100 Motion Module B885
B885-110 Motion Module B885
B886-000 High Speed Logic Solver B886
B887-000 12 Register Bi-directional B887
B888-100 Datalogic CM1000 AutoID interface available in Unity Pro
DCP Distributed Control Module GENNOM
B819 230 VAC 32 Point Input Module B819
B863 4 Channel Register Input B863
B881 8 Point Protected Output Module B881
Module
J890-001 RIO Single P890300
J890-002 RIO Redundant P890300
J892-001 RIO-ASCII Single J892/P8XX
J892-002 RIO-ASCII Redundant J892/P8XX
EIO0000000549 07/2012 209
Rack
Power supply
Not Supported Series 800 Modules
Mixed
H810-100 4 slot secondary available in Unity Pro
H810-208 4 slot alone available in Unity Pro
H810-209 4 slot primary available in Unity Pro
H819-103 7 slot primary AS-H819-209
Module
P800-003 Power Supply 115/230 VAC P890300
P802-001 Power Supply 24VDC P890300
P830-000 Power Supply 115/230 VAC 24VDC P890300
XBE-100 - available in Unity Pro
B884-002 2 Loop, PID Control Module
B885 Motion Module
B885-002 ASCII/BASIC Module
MMC188-40 Motion Module
S985-XXX Modbus Plus Interface
210 EIO0000000549 07/2012
Communication
Controller
D908-110 Distributed Control Single
D908-120 Distributed Control Dual
S908-110 RIO Proc Single
S908-120 RIO Proc Dual
S911-800 Hot Standby
984-380 Controller
984-381 Controller
984-381E Controller
984-385 Controller
984-385E/D Controller
984-480 Controller
984-480E Controller
984-485 Controller
984-485E Controller
984-680 Controller
984-685 Controller
984-685E Controller
984-780 Controller
984-785 Controller
984-785E Controller
984-785EQ Controller
984-785L Controller
B816 -
EIO0000000549 07/2012 211
Series 200/500 Modules
Supported Series 200/500 Modules
Digital input
Digital output
Module
500-IN 500 Series Input B805
B231 115 VAC Input B805
B233 24 VDC Input B805
B237 5 VDC Input for TTL Logic B805
B243 Analog Input B805
B245 230 VAC Isolated Input B805
B247 115 VAC Isolated Input B805
B275 10-60 VDC Input B805
B553 9-56 VDC Universal Input - True High B805
B557 5 VTTL Input B805
B559 9-56 VDC Universal Input - True Low B805
B561 9-160 VDC Input B805
B581 Absolute Encoder B805
B583 Intrinsically Safe Latched Input B805
Pro Module
500-OUT 500 Series Output B804
B230 115 VAC Output B804
B232 24 VDC Output B804
B236 5 VDC Outputs for TTL Logic B804
212 EIO0000000549 07/2012
Mixed
B238 24 VDC High Current Output B804
B239 High Speed Pulse Signals B804
B244 230 VAC Isolated Output B804
B246 115 VAC Isolated Output B804
B248 10-60 VDC Output B804
B260 Analog Voltage Output B804
B262 Analog Current Output B804
B266 Reed Isolated Output B804
B552 9-56 VDC Universal Output - True High B804
B556 5VTTL Output B804
B558 9-56 VDC Universal Output - True Low B804
B560 9-150 VDC Output B804
B592 Reed Relay Output - Normally Open B804
B596 Reed Relay Output - Normally Closed B804
Module
500-IN/OUT 500 Series Mixed B846
B570 5VDC BCD Multiplexer B846
B571 Complement of BCD
Multiplexer
B846
B572 Analog Output B846
B574 4-20 mA Analog Output B846
B575 Stepper Motor Control B846
B579 Dual High Speed Counter B846
Pro Module
EIO0000000549 07/2012 213
Not Supported Series 200/500 Modules
Digital input
Digital output
200-IN 200 Series Input
200-OUT 200 Series Output
214 EIO0000000549 07/2012
SY/MAX Modules
Supported SY/MAX Modules
Analog input
Analog output
Digital input
Module
RIM121 4-Function Analog Input 8030RIM121_125
RIM123 8 Channel High Speed Analog Input 8030RIM123
RIM125 16-Function Analog Input 8030RIM121_125
RIM126 8 Channel Analog/Thermo Input 8030RIM126
RIM127 12 Channel RTD Input Module 8030RIM127
RIM131 High Speed Counter Module 8030RIM131
RIM144 Multiplexed BCD Input Module 8030RIM144
Module
ROM121 4-Function Analog Output 8030ROM121
ROM122 4-Function Isolated Output 8030ROM122
ROM131 Stepper Motor Controller Module 8030ROM131
ROM141 Multiplexed BCD Output Module 8030ROM141
Module
RDI116 16 Channel Input 8030RIM101_361
RDI132 32 Channel Input 8030RIM331
RDI1XX Input Module 8030RIM331
RIM101 16-Function 120V AC/DC Input 8030RIM101_361
RIM301 85-140 VAC 16 Input Module 8030RIM301
RIM331 32-Function 24V DC Input 8030RIM331
RIM361 16-Function 240V AC/DC Input 8030RIM101_361
RIM731 64-Function 24V AC/DC Input 8030RIM731
EIO0000000549 07/2012 215
Digital output
I/O adapter
Rack
Simulator
Module
RDO616 16 Channel Relay Output 8030ROM271
RDO732 32 Channel Relay Output 8030ROM871
RDOXXX Relay Output 8030ROM871
ROM221 16-Function 120V AC Output 8030ROM221_431
ROM271 16-Function 120V AC Relay Output 8030ROM271
ROM421 35-140 VAC 16 Output Module 8030ROM421
ROM431 16-Function 240V AC Output 8030ROM221_431
ROM441 32-Function 24V DC Output 8030ROM441
ROM871 64-Function Relay Output 8030ROM871
Module
CRM931-D1 Digital 2 Slot RIO Adapter 8030CRM931DG1
CRM931-RG Register RIO Adapter Module 8030CRM931DG1
HRK200 Rack 8030-RRK-200
RRK100 Rack 8030-RRK-100
Module
SIM116 16 In Sim 830_SIM_116
216 EIO0000000549 07/2012
Not Supported SY/MAX Modules
Power supply
PS25 -
PS35 -
EIO0000000549 07/2012 217
Compact Modules
Overview
Compact modules can either be converted to Unity Pro Modicon M340 or Quantum
modules depending on the conversion settings.
To define that Compact modules will be converted to Unity Pro Modicon M340
modules, open the LL984 Options dialog box and activate the option M340 in this
dialog box (see page 156).
To convert Compact modules to Unity Pro Quantum modules, activate the option
Quantum.
Please also refer to Special Conversion for Compact I/O Modules (see page 223).
Supported Compact Modules
Analog input
Analog output
Legacy Compact
Module
Description Substituted by Quantum
Module
Substituted by Modicon
M340 Module
ADU 204- ADU 254 4 Channel Register Input GENANAIO BMXART0414
ADU 205 4 Channel Register Input 140ACI03000 BMXAMI0410
ADU 210 4 Channel Voltage/Current Input GENANAIO BMXAMI0410
ADU 211 8 Channel Analog Input Module 140ACI03000 BMXART0814
ADU 212 8 Channel Analog Input Module 140ACI03000 BMXART0814
ADU 214 4 Channel Multi Range A/D Input 140ACI03000 BMXAMI0410,
BMXART0414
ADU 216 8 Channel Thermocouple available in Unity Pro BMXART0814
ADU 257 8 Channel Thermocouple 140ACI03000 BMXART0814
Legacy Compact Module Description Substituted by
Quantum Module
Substituted by
Modicon M340 Module
DAU 202 2 Channel Register Output GENANAIO BMXAMO0210
DAU 204 4 Channel Analog Output, Opto-Isolation GENANAIO BMXAMO0410
DAU 208 8 Channel Register Output 140ACO13000 BMXAMO0410,
BMXAMO0410
218 EIO0000000549 07/2012
Digital input
Digital output
Legacy Compact Module Description Substituted by
Quantum Module
M340 Module
DEO 216 24 VDC 16 Point Input Module 140DDI35300 BMXDDI1602
DEP 208 230 VAC 8 Point Input Module 140DAI74000 BMXDAI0805
See Reduced Modules
(see page 221).
See Reduced Modules
(see page 221).
See Reduced Modules
(see page 221).
DEP 214-254 12-60 VDC 16 Point Input Module 140DDI67300 BMXDDI1603
DEP 215 5 VDC TTL 16 Pt Input Module 140DDI35300 BMXXXXXXX
See Dummy Module
(see page 175).
DEP 216 24 VDC 16 Point Input Module 140DDI35300 BMXDDI1602
DEP 220 Fast 24 VDC 16 Point Input Module 140DDM39000 BMXDDI1602
DEP 257 110 VDC 16 In 140DAI54000 BMXDAI1604
DEP 296 60 VDC 16 In 140DDI67300 BMXXXXXXX
See Dummy Module
(see page 175).
DEP 297 48 VDC 16 In 140DDI67300 BMXDDI1603
Legacy Compact
Module
Module
M340 Module
DAO 216 24 VDC 16 Point Output Module 140DDO35300 BMXDDO1602
DAP 204 24 VDC 4 Point Relay 140DRC83000 BMXDRA0805
DAP 209 120 VAC 8 Point Output Module 140DDO84010 BMXDAO0805
See Reduced Modules
(see page 221).
EIO0000000549 07/2012 219
Mixed
DAP 210 24-230 VAC 8 Point Output Module 140DAO84220 BMXDAO0805
See Reduced Modules
(see page 221).
DAP 216 24 VDC 16 Point Output Module 140DDO35300 BMXDDO1602
DAP 217 5-24 VDC 16 Point Output Module 140DRC83000 BMXDDO1612
DAP 218 24-240 VAC 16 Point Output Module 140DAO84000 BMXDAO1605
Legacy Compact
Module
Module
M340 Module
Legacy
Compact
Module
Description Substituted by
Quantum Module
Substituted by Modicon M340 Module
DAP 211 120 VAC Press and Stamp Module 140DDM39000 BMXXXXXXX
See Dummy Module (see page 175).
DAP 212 24 VDC 8 Point Input/4 Point Output 140DDM39000 BMXDDM16022
DAP 220-250 24 VDC 8 Point Input/Output Module 140DDM39000 BMXDDM16022
DAP 252 24 VDC 8In 4Out 140DDM39000 BMXDDM16022
DAP 253 110VDC 8In 4Out 140DDM39000 BMXDDI1604, BMXDRA0804
See Reduced Modules (see page 221).
DAP 292 60 VDC 8In 4Out 140DDM39000 BMXXXXXXX
FRQ 204 Frequency Module 140EHC10500 BMXXXXXXX
See Dummy Module.
FRQ 254 Frequency Module 140EHC10500 BMXXXXXXX
See Dummy Module.
ZAE 201 High speed Counter/Positioner 140EHC10500 BMXXXXXXX
See Dummy Module.
ZAE 204 4 Channel High speed
Counter/Positioner
140EHC10500 BMXXXXXXX
VRC/CTR2xx High Speed Counter - BMXXXXXXX
See Dummy Module.
VIC 200 4 High Speed Pulse or 4 VRC Inputs - BMXXXXXXX
See Dummy Module.
VIC 205 4 High Speed Pulse or 4 5V TTL Inputs - BMXXXXXXX
See Dummy Module.
220 EIO0000000549 07/2012
Controller
Rack
VIC 212 4 High Speed Pulse or 12 VDC Inputs - BMXXXXXXX
See Dummy Module.
VIC 224 4 High Speed Pulse or 24 VDC Inputs - BMXXXXXXX
Legacy
Compact
Module
Description Substituted by
Quantum Module
Legacy Compact Module Description Substituted by Quantum
Module
M340 Module
984-0120 Controller 16 Bit 140CPU53414A/U BMXP342020
984-A120 Controller 16 Bit 140CPU53414A/U BMXP342020
984-A13x Controller 16 Bit 140CPU53414A/U BMXP342020
984-E241 Controller 16 Bit 140CPU53414A/U BMXP342020
Module
M340 Module
HDTA-200 Rack 140XBP00600 BMXXBP0600
HDTA-201 Rack 140XBP00600 BMXXBP0600
EIO0000000549 07/2012 221
Power supply
Mixed
Motion
Reduced Modules
When importing Compact I/O modules with Modicon M340 as target PLC family, for
compatibility reasons and to avoid address overlapping some modules are
configured with a reduced number of I/Os in Unity Pro during import.
NOTE: These reduced modules can not be selected in the New Device dialog of the
PLC bus editor in Unity Pro.
For the reduced modules you must physically insert the following modules into your
hardware rack.
Module
P120 000 Power Supply 140CPS11420 BMXXXXXXX
P120 125 Power Supply 140CPS11420 BMXXXXXXX
See Dummy Module.
Module
M340 Module
CNOE-211 Ethernet Option module 140NOE77110 BMXNOE0100.2
Module
M340 Module
MOT 201 Axis Motion Control Module
Encoder
140MSC10100 BMXXXXXXX
See Dummy Module
(see page 175).
MOT 202 Axis Motion Control Module
Resolver & Encoder
140MSC10100 BMXXXXXXX
See Dummy Module.
Reduced Module Module to be Physically Inserted
BMXDAI0804 BMXDAI1604
BMXDAO0805 BMXDAO1605
BMXDDI0804 BMXDDI1604
222 EIO0000000549 07/2012
Not Supported Compact Modules
I/O adapter
Legacy Compact Module Description
BKF 202 INTERBUS S Slave
BKF201-16 16 Word INTERBUS S Master
BKF201-64 64 Word INTERBUS S Master
KOS260-24 24 Word Universal Comm
KOS260-64 64 Word Universal Comm
EIO0000000549 07/2012 223
B
LL984 Editor
Special Conversion for Compact I/O Modules
EIO0000000549 07/2012
Special Conversion for Compact
I/O Modules
Section Topic Page
B.1 Digital Input Modules Conversion 224
B.2 Digital Output Modules Conversion 225
B.3 Digital Mixed Modules Conversion 226
B.4 Analog Input Modules Conversion 227
B.5 Analog Output Modules Conversion 249
224 EIO0000000549 07/2012
B.1 Digital Input Modules Conversion
Digital Input Modules Conversion
Binary/BCD Conversion
For Quantum BCD configuration is possible for digital input modules mapped on %I
or %IW.
For Modicon M340 BCD configuration only is possible for digital input modules
mapped on %IW.
In case BCD is configured with discrete references you have to adapt your
application accordingly.
EIO0000000549 07/2012 225
B.2 Digital Output Modules Conversion
Digital Output Modules Conversion
For Quantum BCD configuration is possible for digital output modules mapped on
%M or %MW.
For Modicon M340 BCD configuration only is possible for digital output modules
mapped on %MW.
Timeout Behavior Conversion
Since Modicon M340 modules have a configurable PLC Stop behavior, the legacy
Compact PLC Stop behavior can be converted to a Modicon M340 module specific
PLC Stop behavior.
The legacy setting Last Val ue sel ect ed becomes the fallback mode
Mai nt ai n, and in case a User def i ned Val ue is configured, this value will be
converted to the channel specific fallback values, and the fallback mode is set to
Fal l back.
226 EIO0000000549 07/2012
B.3 Digital Mixed Modules Conversion
Digital Mixed Modules Conversion
For Quantum BCD configuration is possible for digital mixed modules mapped on %I
or %IW (inputs) respectively on %M or %MW (outputs).
For Modicon M340 BCD configuration only is possible for digital mixed modules
mapped on %IW (inputs) respectively on %MW (outputs).
Timeout Behavior Conversion
Since Modicon M340 modules have a configurable PLC Stop behavior, the legacy
Compact PLC Stop behavior can be converted to a Modicon M340 module specific
PLC Stop behavior.
The legacy setting Last Val ue sel ect ed becomes the fallback mode
Mai nt ai n, and in case a User def i ned Val ue is configured, this value will be
converted to the channel specific fallback values, and the fallback mode is set to
Fal l back.
EIO0000000549 07/2012 227
B.4 Analog Input Modules Conversion
Topic Page
Analog Input Modules Conversion 228
ADU 206/256 229
ADU 205 Voltage and Current 234
ADU 210 Voltage and Current 238
ADU 204/ADU 254 Thermocouple 239
ADU 214 Mixed Voltage, Current, Thermocouple and Resistors 241
ADU 257 One and Two Channel Thermocouple with 32 bit 245
ADU 211/212, ADU 216 Hardware Switch Configured Modules 246
FRQ xxx, ZAE xxx, MOT_xxx, VIC_xxx, Counting and Positioning Modules 248
228 EIO0000000549 07/2012
Analog Input Modules Conversion
Introduction
Unity Pro generalizes module configuration by using a similar dialog for all analog
input modules, where the Concept and ProWORX Compact analog input module
dialogs are very different in style and content.
Scale and Overflow Parameters
Scale and Overflow parameters are used by the converter for all analog input
modules to implement the value ranges and limit checks, as they have been in the
Compact system.
The Range column must always be filled, otherwise during Analyze appropriate
messages are generated. The most similar sensor is generated in this case.
Additional parameters are required by the BMXARTxxxx modules. They are also
determined by the converter.
Over/Under-Range Values
The Compact module specific pre-defined Over/Under-Range values are not
supported by the Modicon M340 analog modules.
In case the legacy application uses any of the Compact module specific pre-defined
Over/Under-Range values (for example for range error detection) this part of the
application needs to be reworked manually.
In the following chapters the configuration of the specific Compact analog input
modules is described.
Tables list all value ranges provided by the Compact analog module.
EIO0000000549 07/2012 229
ADU 206/256
Modicon M340 Replacement
The legacy Compact ADU 256 module works just like the ADU 206 module, except
that the ADU 256 module operates at extended temperature.
Therefore, both modules are substituted by Modicon M340 BMXAMI0410 modules.
Supported and Unsupported Modes
Please refer to the following tables to see how conversion is done and to find the
modes for which automatic conversion cannot be provided.
Modes showing scaling values Out of Range cannot be converted automatically,
because
the required values exceed the maximum possible ones. In these cases
additional emulation code for value conversion is necessary.
For an example how to create emulation code please refer to the description of
the ADU 214 module (see page 243).
the mode is not the import default mode (please refer to Conversion Weaknesses
(see page 231)). In this case you have to parameterize the BMXAMI0410
channel manually.
The BMXAMI0410 module does not support a 16 bit conversion mode.
In case a legacy ADU 206 module is configured with a 16 bit resolution a message
in the import log file is generated.
Also for each channel a message is generated in the import log file, and the
BMXAMI0410 channel input/output blocks (IOBs) will contain the default values.
Additionally a ConvEr r or block is inserted into a converter generated ST section.
Please refer to Module specific channel I/O blocks (see page 175).
Unipolar
ADU 206
0..20 mA
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit 02,000 0..20 mA 0 / 2,000
12 bit 04,00 0..20 mA 0 / 4,000
15 bit + sign 032,000 0..20 mA 0 / 32,000
16 bit 064,000 0..20 mA Out of Range
230 EIO0000000549 07/2012
Bipolar
ADU 206
0..1 V
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit 02,000 0..5 V Out of Range
15 bit + sign 032,000 0..5 V Out of Range
ADU 206
0..10 V
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit 02,000 0..10 V 0 / 2,000
12 bit 04,000 0..10 V 0 / 4,000
15 bit + sign 032,000 0..10 V 0 / 32,000
ADU 206
+/-20 mA
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit -2,0002,000 +/-20 mA -2,0002,000
12 bit 484,048 +/-20 mA 484,048
15 bit + sign -32,00032,000 +/-20 mA -32,00032,000
16 bit 76864,768 +/-20 mA Out of Range
ADU 206
+/-1 V
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit -2,0002,000 +/-5 V Out of Range
12 bit 484,048 +/-5 V Out of Range
15 bit + sign -32,00032,000 +/-5 V Out of Range
16 bit 76864,768 +/-5 V Out of Range
ADU 206
+/-10 V
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit -2,0002,000 +/-10 V -2,0002,000
12 bit 484,048 +/-10 V 484,048
15 bit + sign -32,00032,000 +/-10 V -32,00032,000
16 bit 76864,768 +/-10 V Out of Range
EIO0000000549 07/2012 231
Broken Wire
Conversion Weaknesses
The ADU206/ADU256 voltage/current input selection is made using jumpers.
Therefore, the converter selects a default conversion mode and adapts the channel
parameter to this default mode.
The conversion default ranges are:
020 mA
In case the ADU206/ADU256 parameter shows +/-1 V,+/-20 mA.
020 mA
In case the ADU206/ADU256 parameter shows 0..1 V, 020 mA.
420 mA
In case the ADU206/ADU256 parameter shows 0,2..1 V, 420 mA.
ADU 206
4..20 mA
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit 02,000 4..20 mA 0 / 2,000
12 bit 04,000 4..20 mA 0 / 4,000
15 bit + sign 032,000 4..20 mA 0 / 32,000
ADU 206
0.2..1 V
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
15 bit + sign 032,000 0..5 V Out of Range
ADU 206
2..10 V
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
11 bit 02,000 0..10 V -500 / 2,000
12 bit 04,000 0..10 V -1000 / 4,000
15 bit + sign 032,000 0..10 V -8000 / 32,000
232 EIO0000000549 07/2012
Additional Actions for the User
The ADU206/ADU256 voltage/current input selection is made using jumpers.
Since the converter selects a default mode for the BMXAMI0410 channel mode
(please refer to Supported and Unsupported Modes (see page 229)), the channel
ranges and the channel scaling must be checked. In case a non default range
should be used the channel range and the channel parameters must be adapted
to the application needs.
The 2..10 V mode is not directly supported by the BMXAMI0410 module. In case
this mode is emulated with the 0..10 V BMXAMI0410 range, negative values may
appear when the input voltage is lower than 2 V.
For this mode no broken wire bit will be set in the emulated status word.
Therefore, in this case the logic must be adapted to accept negative values, and
the broken wire detection must be realized with additional logic.
Created Emulation Code
There is only automatic creation of emulation code for status information (see
below).
Supported Status Information
The legacy Compact module specific input status bits, are not provided by Modicon
M340 modules directly.
During import ST code is generated, which copies or combines existing
BMXAMI0410 status information to the corresponding ADU 206 status area.
These bits are set and reset according to the BMXAMI0410 status information,
which may differ from the ADU 206 status behavior.
The BMXAMI0410 module provides no information which is similar to the bit 5 and
bit 7 status word meaning.
Therefore, these 2 bits have no equivalent in the Modicon M340 target status word.
The status bits are provided by the Modicon M340 module in the following way:
Bit
1..16
Meaning (Compact) 30xxx
Register)
Equivalent at
BMXAMI0410
Meaning (Modicon M340)
1 1 = channel 1 current error
(overrange or open circuit)
%IWr.m.0.1.5 OR
%IWr.m.0.1.6 *
measurement within lower or
upper tolerance zone
%IWr.m.1.1.5 OR
%IWr.m.1.1.6 *
%IWr.m.2.1.5 OR
%IWr.m.2.1.6 *
%IWr.m.3.1.5 OR
%IWr.m.3.1.6 *
EIO0000000549 07/2012 233
To ease the access to this status information, the converter creates emulation code,
which transfers the bits to concerned input variable. The created code can be
viewed inside the section ATSTCopI n.
Furthermore BMXAMI0410 does not provide a common error for overrun, the
emulation code combines the channel overrun/underrun errors to simulate this
status information. A logical OR is used for doing this.
5 module measures current or
voltage in 12 bit unipolar mode
not available with
Modicon M340
not available with Modicon
M340
6 module measures current or
voltage with an offset over the
restricted range
4-20 mA, 0.2-1 V, 2-10 V
one or more of bit
1-4 is set
measurement of one
channel is within lower or
7 external supply voltage to the
module is not connected
not available with
Modicon M340
not available with Modicon
M340
8 module is not ready yet, or one
or more of bit 1-4 is set, or
processor fault occurs
one or more of bit
1-4 is set or the
module error bit is
set
measurement of one
channel is within lower or
upper tolerance zone or a
module error is shown
9-16 not used not used not used
* r = rack, m = module slot
Bit
1..16
Meaning (Compact) 30xxx
Register)
Equivalent at
BMXAMI0410
Meaning (Modicon M340)
234 EIO0000000549 07/2012
ADU 205 Voltage and Current
The ADU 205 module is substituted by Modicon M340 BMXAMI0410 modules.
because the required values exceed the maximum possible ones. In these cases
For an example how to create emulation code please refer to the description of the
ADU 214 module (see page 243).
The BMXAMI0410 module does not support a 16 bit conversion mode.
In case a legacy ADU 205 module is configured with a 16 bit resolution a message
in the import log file is generated.
Also for each channel with an unsupported mode selected a message is generated
in the import log file, and the BMXAMI0410 channel input/output blocks (IOBs) will
contain the default values.
Additionally a ConvEr r or block is inserted into a converter generated ST section.
Please refer to Module specific channel I/O blocks (see page 175).
The ADU 205 ranges -20 to +20 V, -40 to 40 mA and 0 to 20 V are not supported by
any Modicon M340 module.
ADU 205
Mode
AMI0410
Sensor
-20 to +20 V Not supported
-40 to 40 mA Not supported
-10 to +10 V +/-10 V
+/- 20 mA +/- 5V +/- 20 mA
0 to 20 mA 0..5 V / 0..20 mA
4 to 20 mA 1..5 V / 4..20 mA
0 to 10 V 0..10 V
0 to 20 V Not supported
EIO0000000549 07/2012 235
Scaling Values
Modicon M340 scaling values for the ADU 205 modes supported for the
BMXAMI0410module.
ADU 205
0..20 mA
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
12 bit 04,095 0..20 mA 0 / 4,095
12 bit + sign 04,095 0..20 mA 0 / 4,095
13 bit 08,191 0..20 mA 0 / 8,191
15 bit + sign 032,000 0..20 mA 0 / 32,000
ADU 205
0..10 V
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
12 bit 04,095 0..10 V 0 / 4,095
12 bit + sign 04,095 0..10 V 0 / 4,095
13 bit 08,191 0..10 V 0 / 8,191
15 bit + sign 032,000 0..10 V 0 / 32,000
ADU 205
4..20 mA
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
12 bit 04,095 4..20 mA 0 / 4,095
12 bit + sign 04,095 4..20 mA 0 / 4,095
13 bit 08,191 4..20 mA 0 / 8,191
15 bit + sign 032,000 4..20 mA 0 / 32,000
ADU 205
+/- 20 mA
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
12 bit 04,095 +/- 20 mA 0 / 4,095
12 bit + sign -4,0954,095 +/- 20 mA -4,095 / 4,095
13 bit 08,191 +/- 20 mA 0 / 8,191
15 bit + sign -32,00032,000 +/- 20 mA -32,000 / 32,000
16 bit 065,520 +/- 20 mA Out of Range
236 EIO0000000549 07/2012
The ADU 205 voltage/current inputs support ranges which are not supported by any
Modicon M340 analog module.
In case such an extended range like +/- 20 V, 0-20 V or +/-40 mA was selected an
adaptation must be made manually and may be also an adaptation for the sensors
must be made.
Manually created emulation code is required for applications where a 16 bit
resolutions was used and for applications where a +/- 20 V, 0-20 V or +/-40 mA
range was selected.
There is no automatic creation of emulation code for this module during import.
There is no automatic emulation of status information for the ADU 205 module
during import.
The described Compact module specific input status bits below are not provided by
Modicon M340 modules directly. In case the application references to ADU 205
status information, application needs to be adapted manually, and should use the
available Modicon M340 module status Information.
Compact ADU 205 module specific I/O mapped status word
ADU 205
+/- 10 v
Origin Value
Range
Adequate
BMXAMI0410 Mode
Scaling values
0% / 100%
12 bit 04,095 +/- 10 V 0 / 4,095
12 bit + sign -4,0954,095 +/- 10 V -4,095 / 4,095
13 bit 08,191 +/- 10 V 0 / 8,191
15 bit + sign -32,00032,000 +/- 10 V -32,000 / 32,000
16 bit 065,520 +/- 10 V Out of Range
Bit Meaning
0 Channel 1 - exceed/fall below measuring range
EIO0000000549 07/2012 237
3 Channel 4 - exceed/fall below measuring range or open circuit
4 Channel 1 - open circuit
8-14 reserved
15 0 = module is healthy
1 = module is not healthy (multiple error: reports various errors which are
viewable on the input status word of the module once identified.)
Bit Meaning
238 EIO0000000549 07/2012
ADU 210 Voltage and Current
The legacy Compact ADU 210 module is substituted by a Modicon M340
BMXAMI0410 module.
The conversion is performed by setting special scaling values inside the
configuration of the BMXAMI0410 module.
For ADU 210 conversion this mechanism is sufficient to support every mode of
ADU 210 module.
Limit checks are different for the BMXAMI0410 module.
Therefore, additional user actions are required in case l i mi t <> 0 was activated
for ADU 210 channel.
There is no automatic creation of emulation code for the ADU 210 module during
import.
There is no emulation of status information for the ADU 210 module during import.
ADU 210 Mode Origin Value
Range
Adequate BMXAMI0410 Mode Scaling Values
0% / 100%
inactive inactive 10 V default
010 V 032,000 010 V 0 / 32,000
05 V 032,000 05 V 0 / 32,000
210 V 032,000 010 V -8,000 / 32,000
15 V 032,000 15 V 0 / 32,000
5 V -32,00032,000 5V -32,000 / 32,000
10 V -32,00032,000 10 V -32,000 / 32,000
EIO0000000549 07/2012 239
ADU 204/ADU 254 Thermocouple
The legacy Compact ADU 204/ADU 254 is substituted by a Modicon M340
BMXART0414.
With the exception of the 13 bit and 15 bit+sign resolutions in combination with RTD
sensors, the ADU 204/ADU 254 modes are supported by automatic conversion.
If after conversion the resulting temperature ranges do not fit the process
requirements, additional adaptations are necessary. Please refer to Additional
Actions for the User (see page 239).
In opposite to the RTD modes, whereupon the delivered values are in fixed units of
1/10 C or 1/10 F for the resistance measurement mode the converter inserts
special scaling values in the configuration to adapt to the ADU 204/ADU 254
ranges.
For RTD sensor modes the resolutions 13 bit and 15bit+sign are not supported by
automatic conversion. Manual created emulation code is required for these
operation modes.
Furthermore it is possible that the temperature range of the resulting RTD does not
comply with the process requirements. In this case the proposed mode and RTD
sensor must be replaced by other.
ADU 204/ADU 254 RTD
Sensor Mode
Temperature
Range
Adequate
BMXART0414 Mode
Temperature
Range
Pt 100, -200 to 850 C -200...850 C Pt 100 -175825 C
Pt 200, -200 to 250 C -200250 C Pt 100 -175825 C
Ni 100, -60 to 250 C -60...250 C Ni 100 -54174 C
Ni 200, -60 to 150 C -60...150 C Ni 100 -54174 C
APt 100, -200 to 600 C -200...600 C JPt 100 -87437 C
APt 200, -200 to 250 C -200...250 C JPt 100 -87437 C
ADU 204/ADU 254
Resistance Mode
Origin Value
Range
Adequate
BMXART0414 Mode
Scaling Values
0% / 100%
0...400 , 13 bit 08,191 0...400 0 / 8,191
0...400 , 15 bit+sign 032,000 0...400 0 / 32,000
240 EIO0000000549 07/2012
The following table shows the RTD sensors supported by the BMXART0414 module
and the provided temperature ranges.
The converter creates emulation code for the temperature modes 1.0 Celsius and
1.0 Fahrenheit, which divides the 1/10 units of BMXART0414 by 10.
The created ST code for this purpose looks like this example:
%I W177 : = WRI TE_I NPUT_I NT( REAL_TO_I NT( I NT_TO_REAL( %I W177) /
10. 0) ) ;
The automatically created emulation code is stored in the ST section ATSTCopI n.
There is no emulation of status information for the ADU 204/ADU 254 module during
import.
RTD Type Supported Temperature Range
Pt100 IEC 751-1995, JIS C1604-1997 (2/4 wires) -175825 C (-2831517 F)
Pt1000 IEC 751-1995, JIS C1604-1997 (2/4 wires) -175825 C (-2831517 F)
Ni100 DIN43760-1987 (2/4 wires) -54174 C (-66346 F)
Ni1000 DIN43760-1987 (2/4 wires) -54174 C (-66346 F)
Pt100 IEC 751-1995, JIS C1604-1997 (3 wires) -175825 C (-2831517 F)
Pt1000 IEC 751-1995, JIS C1604-1997 (3 wires) -175825 C (-2831517 F)
Ni100 DIN43760-1987 (3 wires) -54174 C (-66346 F)
Ni1000 DIN43760-1987 (3 wires) -54174 C (-66346 F)
JPt100 JIS C1604-1981, JIS C1606-1989 (2/4 wires) -87437 C (-124818 F)
JPt1000 JIS C1604-1981, JIS C1606-1989 (2/4 wires) -87437 C (-124818 F)
JPt100 JIS C1604-1981, JIS C1606-1989 (3 wires) -87437 C (-124818 F)
JPt1000 JIS C1604-1981, JIS C1606-1989 (3 wires) -87437 C (-124818 F)
Cu10 (2/4 wires) -91251 C (-132484 F)
Cu10 (3 wires) -91251 C (-132484 F)
EIO0000000549 07/2012 241
ADU 214 Mixed Voltage, Current, Thermocouple and Resistors
Legacy Compact ADU 214 modules can be configured to Mixed Voltage, Current,
Thermocouple and Resistor inputs on a per channel basis. There is no equivalent
module in the Modicon M340 range and therefore more than one module is needed
to substitute a ADU 214 module.
Inside the configuration the converter places BMXAMI0410 and BMXART0414
module(s) for ADU 214 substitution, by applying the following rules:
A second module is placed if more than 4 channels are needed, either one
BMXAMI0410 or one BMXART0414.
Because conversion of the different ADU 214 modes is done by using the scaling
feature of BMXAMI0410 and BMXART0414, only a few conversions can be
provided automatically. Please refer to the following tables to get an overview.
Modes showing scaling values Out of Range cannot be converted automatically.
In these cases additional emulation code for value conversion is necessary.
Please refer to Additional Actions for the User (see page 243).
First Found Sensor is Replacement
ADU 214 Unipolar Voltage one BMXAMI0410
ADU 214 Bipolar Voltage one BMXAMI0410
ADU 214 Thermocouple one BMXART0414
ADU 214 Resistor one BMXART0414
ADU 214 Unipolar
Voltage
Origin Value Range Adequate
BMXAMI0410 Mode
Scaling values 0% /
100%
0...0.5 V 032,000 0...5 V Out of Range
01 V 032,000 05 V Out of Range
05 V 032,000 05 V 0 / 32,000
010 V 032,000 010 V 0 / 32,000
0.10.5 V 032,000 05 V Out of Range
0.21 V 032,000 05 V Out of Range
15 V 032,000 15 V 0 / 32,000
2...10 V 032,000 010 V -8,000 / 32,000
242 EIO0000000549 07/2012
ADU 214
Bipolar Voltage
Origin Value Range Adequate
BMXAMI0410 Mode
Scaling values 0% /
100%
0.5 V -32,00032,000 5 V Out of Range
1 V -32,00032,000 5 V Out of Range
5 V -32,00032,000 5 V -32,000 / 32,000
10 V -32,00032,000 10 V -32,000 / 32,000
ADU 214
Thermocouple
Origin Value
Range
Adequate
BMXART0414 Mode
Scaling values 0% /
100%
100
-60+160 C Ni
032,000 100
-54+174 C Ni
Out of Range
200
-60+160 C Ni
032,000 none Out of Range
500
-60+160 C Ni
1 k
-60+160 C Ni
032,000 1 k
-54+174 C Ni
Out of Range
100
-160+160 C Pt
032,000 100
-175+825 C Pt
Out of Range
200
-160+160 C Pt
500
-160+160 C Pt
1 k
-160+160 C Pt
032,000 1 k
-175+825 C Pt
Out of Range
100
-200+320 C Pt
032,000 100
-175+825 C Pt
Out of Range
200
-200+320 C Pt
500
-200+320 C Pt
1 k
-200+320 C Pt
032,000 1 k
-175+825 C Pt
Out of Range
100
-200+640 C Pt
032,000 100
-175+825 C Pt
Out of Range
200
-200+640 C Pt
EIO0000000549 07/2012 243
Because of the huge value range of the ADU 214 module most of the resulting
scaling values are exceeding the maximum possible range. Therefore additional
emulation code is needed to convert and emulate the origin range of values.
The ST Section ATSTCopI n has been already created to admit additional emulation
code. Please also refer to Module Emulation (see page 178).
Of course also other types of sections (like FBD, LD etc.) can be used for this
purpose.
Example conversion for Thermocouple -60+160 Range:
Within this temperature range the ADU 214 module delivers values between
032,000 as it is noted in the table above. In the opposite the BMXART0414
module delivers always in units of 1/10 C and therefore results in values between -
6001600 for the same temperature range.
Now you have to perform a linear conversion of these values from one range into
the other. One possibility to do that is the usage of the common equation for a line:
Y = m * X + b
Whereas m is the gradient and b is the intersection with the ordinate of that
searched line.
500
-200+640 C Pt
1 k
-200+640 C Pt
032,000 1 k
-175+825 C Pt
Out of Range
ADU 214 Resistor Origin Value Range Adequate
BMXART0414 Mode
Scaling values 0% /
100%
0...100 032,000 0...400 Out of Range
0...200 032,000 0...400 Out of Range
0...500 032,000 0...4 k Out of Range
0...1 k 032,000 0...4 k Out of Range
0...2 k 032,000 0...4 k Out of Range
ADU 214
Thermocouple
Origin Value
Range
Adequate
BMXART0414 Mode
Scaling values 0% /
100%
Compact Module
Low
Compact Module
High
Modicon M340
Module Low
Modicon M340
Module High
0 32,000 -600 1600
244 EIO0000000549 07/2012
The gradient m can be calculated by:
m = (Compact high - Compact low) / (M340 high - M340 low)
In the example the gradient m results into 14.545.
Now you can calculate the intersection point b using the formula:
b = Compact high - m * M340 high
And this results into 8,727.27 for b.
With both values it is now possible to build your ST code for doing the conversion.
Remember this is based on the equation for a line Y = m * X + b from the beginning,
which looks adapted to your purpose like this:
<Compact value> = m * <M340 value> + b
and expressed in structured text (ST) like this:
%IW999 := WRITE_INPUT_INT(REAL_TO_INT(m * INT_TO_REAL(%IW999) +
b));
and finally with inserted values like this:
%IW999 := WRITE_INPUT_INT(REAL_TO_INT(14.545 * INT_TO_REAL(%IW999)
+ 8727.27));
After this ST code has been added to the application than the received values will
be the same as they were delivered by the ADU 214 module within the temperature
range:
-60160 C.
Creation of emulation code for other modes can be done in the same way.
There is no automatic creation of emulation code for the ADU 214 module during
import.
EIO0000000549 07/2012 245
ADU 257 One and Two Channel Thermocouple with 32 bit
The legacy Compact ADU 257 module is substituted by a Modicon M340
BMXART0814 module.
The BMXART0814 module is equipped with a 16 bit converter for each input and
therefore every ADU 257 resolution can be reached at least.
For this module the way of conversion differs from others, because no scaling value
mechanism has been used, rather the converter creates emulation code to convert
the BMXART0814 values into ADU 257values.
Due to this principle almost every mode of the ADU 257 module is supported. Only
the IEEE754 floating point resolutions must be adapted manually.
Manually created emulation code is required for channels with IEEE754 floating
point resolution.
The converter creates emulation code for almost every ADU 257 mode and every
resolution. Only IEEE754 floating point resolution is not supported.
Automatically created emulation code is stored in the ST section ATSTCopI n.
The basic principle of conversion is the equation for a line ( Y = m* X + b) . For
an example how to create emulation code please refer to the description of the
ADU 214 (see page 243) module.
Example for created ST code:
%I W130 : = WRI TE_I NPUT_I NT( REAL_TO_I NT( 0. 216667 *
I NT_TO_REAL( %I W130) + 710. 666626) ) ;
246 EIO0000000549 07/2012
ADU 211/212, ADU 216 Hardware Switch Configured Modules
The legacy Compact modules ADU 211/212 and ADU 216 are substituted in the
following way:
They are converted with Unity Pro default configuration - as if just entered by
Unity Pro configuration.
The import log file gives a hint to correct the default module choice.
Since this legacy analog module is configured during runtime by the logic, it is not
possible to adjust the BMXART0814 channel settings during import.
For the converter there is no information available, which could be used to adjust the
BMXART0814 parameters.
The BMXART0814 configuration must be adapted to the sensor and application
needs.
Since the application contains logic to configure the Compact module during
runtime, this configuration logic must be removed.
With the legacy ADU211/212/216 modules it was necessary to demultiplex the
input values with help of logic. This logic must be removed.
In case the legacy Compact application used a data format or data type which is
not supported by the BMXART0814 module, the logic must be adapted.
In case the legacy Compact application used status information of these
modules, you have to adapt the logic, and status information, accessible in the
topological area of the BMXART0814 module, has to be used.
In case on the ADU211/212 dip switch settings Vol t age Conver si on is
selected, and the input Vol t age Range is greater than +/-1.28 V the
BMXART0814 must be replaced by two BMXAMI0410 modules.
Legacy Compact
Module
Description Substituted by Modicon
M340 Module
ADU 211 8 Channel Analog Input Module BMXART0814
ADU 212 8 Channel Analog Input Module BMXART0814
ADU 216 8 Channel Thermocouple BMXART0814
EIO0000000549 07/2012 247
In case only for one group (4 channels) Vol t age Conver si on is selected, and
the input Vol t age Range is greater than +/-1.28 V, the BMXART0814 module
must be replaced by one BMXART0414 and one BMXAMI0410 module.
There is no automatic creation of emulation code for these modules during import.
There is no emulation of status information or I/O mapped status word information
for these modules during import.
248 EIO0000000549 07/2012
FRQ xxx, ZAE xxx, MOT_xxx, VIC_xxx, Counting and Positioning Modules
The legacy counting and positioning modules are substituted by dummy modules
(BMXXXXXXX).
There is no configuration conversion nor parameter conversion.
You have to modify the configuration and logic of your application regarding the
counting and positioning modules.
EIO0000000549 07/2012 249
B.5 Analog Output Modules Conversion
Topic Page
Analog Output Modules Conversion 250
DAU 204 251
DAU 208 254
DAU 2x2 255
250 EIO0000000549 07/2012
Analog Output Modules Conversion
Introduction
Analog output modules provide Fallback Values. The Stop behavior of Compact
modules can be taken over in an identical manner.
User Defined Values
If User Defined values are set for Compact modules, these values are moved to
Modicon M340 modules and used for Fallback Values. In such cases you have to
activate the assigned Fallback checkbox in the Modicon M340 target module.
Affected modules are DAU 204, DAU 208 and DAU 2x2.
EIO0000000549 07/2012 251
DAU 204
The legacy Compact DAU 204 module is substituted by a Modicon M340
BMXAMO0410 module.
because the required values exceed the maximum possible ones. In these cases
DAU 204
0..20 mA, 4..20 mA
Origin Value
Range
Adequate
BMXAMO0410 Mode
Scaling Values
0% / 100%
11 bit 02,047 0..20 mA, 4..20m A 0 / 2,048
12 bit 04,095 0..20 mA, 4..20m A 0 / 4,096
15 bit + sign 032,000 0..20 mA, 4..20m A 0 / 32,000
16 bit 065,520 0..20 mA, 4..20m A Out of Range
DAU 204
1 V
Origin Value
Range
Adequate
BMXAMO0410 Mode
Scaling Values
0% / 100%
11 bit 02,047 10 V 9,216 / 11,264
12 bit 04,095 10 V 18,432 / 22,528
15 bit + sign -32,00032,000 10 V Out of Range
16 bit 065,520 10 V Out of Range
DAU 204
5 V
Origin Value
Range
Adequate
BMXAMO0410 Mode
Scaling Values
0% / 100%
11 bit 02,047 10 V -1,024 / 3,072
12 bit 04,095 10 V -2,048 / 6,144
15 bit + sign -32,00032,000 10 V Out of Range
252 EIO0000000549 07/2012
DAU 204
10 V
Origin Value
Range
Adequate
BMXAMO0410
Mode
Scaling Values
0% / 100%
11 bit 02,047 10 V 0 / 2,048
12 bit 04,095 10 V 0 / 4,096
15 bit + sign -32,00032,000 10 V -32,00032,000
DAU 204
0...1 V
Origin Value
Range
Adequate
BMXAMO0410
Mode
Scaling Values
0% / 100%
11 bit 02,047 10 V -20,480 / 20,480
15 bit + sign 032,000 10 V Out of Range
DAU 204
0...5 V
Origin Value
Range
Adequate
BMXAMO0410
Mode
Scaling Values
0% / 100%
11 bit 02,047 10 V -4,096 / 4,096
12 bit 04,095 10 V -8,192 / 8,192
15 bit + sign 032,000 10 V Out of Range
DAU 204
0...10 V
Origin Value
Range
Adequate
BMXAMO0410
Mode
Scaling Values
0% / 100%
11 bit 02,047 10 V -2,048 / 2,048
12 bit 04,095 10 V -4,096 / 4,096
15 bit + sign 032,000 10 V -32,000 / 32,000
EIO0000000549 07/2012 253
Manually created emulation code is required for every mode in which the scaling
values are Out of Range.
There is only automatic creation of emulation code for status information (see
below).
The status bits are provided by the Modicon M340 module in the following way:
To ease the access to this status information, the converter creates emulation code,
which transfers the bits to concerned input variable. The created code can be
viewed inside the section ATSTCopI n.
Furthermore BMXAMO0410 does not provide a common error for current, the
emulation code combines the by-channel errors to simulate this status information;
a logical OR is used for doing this.
Bit (1..16) Meaning (Compact)
Register 30xxx
Equivalent at
BMXAMO0410
Meaning
(Modicon M340)
1 1 = current error OR of Ch.1 Ch.4 -
2 1 = Ch.1 current error [T_ANA_OUT_BMX].ACT_WIRE_FLT actuator wire open or short
6..14 not used - -
15 1 = module memory error not known/available -
16 1 = module error [T_GEN_MOD].MOD_ERROR module detected error bit
254 EIO0000000549 07/2012
DAU 208
The legacy Compact DAU 208 module has 8 output channels and is substituted by
2 Modicon M340 BMXAMO0410 modules.
configuration of the BMXAMO0410 modules.
This conversion mechanism is sufficient to support every mode at every resolution
of DAU 208 modules.
Also the values for Overflow and Underflow and the configured Timeout values are
taken over to the BMXAMO0410 configuration to get an identical behavior in cases
of overflow and timeout.
No additional actions are necessary.
There is no emulation of status information for the DAU 208 module during import.
DAU 208 Mode Origin Value
Range
Adequate
BMXAMO0410
Mode
Scaling Values
0% / 100%
Overflow Values
Below /Above
10 V, 12 bit 484,048 10 V 48 / 4,048 47 / 4,049
10 V, 15 bit+sign -32,00032,000 10 V -32,000 / 32,000 -32,016 / 32,016
EIO0000000549 07/2012 255
DAU 2x2
The legacy Compact DAU 208/DAU 252 module is substituted by a Modicon M340
BMXAMO0210 module.
configuration of the BMXAMO0210 module.
This conversion mechanism is sufficient to support every mode at every resolution
of DAU 2x2 modules.
Also the values for Overflow and Underflow and the configured Timeout values are
taken over to the BMXAMO0210 configuration to get an identical behavior in cases
of overflow and timeout.
No additional actions are necessary.
There is no emulation of status information for the DAU 2x2 module during import.
DAU 2x8 Mode Origin Value
Range
Adequate
BMXAMO0210
Mode
Scaling Values
0% / 100%
Overflow
Values
Below /Above
020 mA, 12 bit 484,048 020 mA 48 / 4,048 47 / 4,049
020 mA,
15-bit+sign
-32,00032,000 020 mA -32,000 / 32,000 -32,016 / 32,016
10 V, 12bit 484,048 10 V 48 / 4,048 47 / 4,049
10 V, 15 bit+sign -32,00032,000 10 V -32,000 / 32,000 -32,016 / 32,016
256 EIO0000000549 07/2012
EIO0000000549 07/2012 257
C
B
A
LL984 Editor
Index
EIO0000000549 07/2012
Index
B
bookmarks
graphical languages, 51
C
coils
LL984 editor, 57
Compact I/O modules
special conversion, 223
contacts
LL984 editor, 57, 77
creating a program
E
equation network blocks
LL984 editor, 57, 105
export/import LL984 segments and networks
LL984 editor, 193
F
FBD editor
search/replace function, 125
function blocks
G
general functions
LL984 editor, 19
general restrictions
LL984 editor, 19
graphical languages
bookmarks, 51
I
I/O modules supported/not supported
LL984 editor, 197
IL editor
import restrictions
LL984 editor, 153
importing an LL984 application
LL984 editor, 153
importing parts of an LL984 application
LL984 editor, 153
instruction editor
LL984 editor, 148
L
layout
LL984 editor, 19
LD editor
links
Index
258 EIO0000000549 07/2012
LL984 editor
assigning variables, 57, 113
coils, 57, 86
contacts, 57, 77
creating a program, 57, 58
creating networks and sections, 31
equation network blocks, 57, 105
export/import LL984 segments and net-
works, 193
function blocks, 57, 95
general functions, 19
general restrictions, 19
I/O modules supported/not supported,
197
import restrictions, 153
importing an LL984 application, 153
importing parts of an LL984 application,
153
instruction editor, 148
layout, 19
links, 57, 99
modifying networks and sections, 31
network display, 57, 66
options, 43
project settings, 43
scheduling networks and sections, 31
subroutines, 57, 117
toolbar, 19
N
network and section creation
LL984 editor, 31
network and section modification
LL984 editor, 31
network display
networks and sections scheduling
LL984 editor, 31
O
options
LL984 editor, 43
P
project settings
LL984 editor, 43
S
SFC editor
special conversion for Compact I/O modules,
223
ST editor
subroutines
LL984 editor, 57, 117
T
toolbar
LL984 editor, 19
V
variables assignment
LL984 editor, 57, 113

Eio0000000549 PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Eio0000000549 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

E

S-ar putea să vă placă și