LL984 to Unity Converter User manual

33003538 04/2009

3300

3538

.05

www.schneider-electric.com

Unity ProLL984 to Unity ConverterUser manual

04/2009

Schneider Electric assumes no responsibility for any errors that may appear in this document. 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.

© 2009 Schneider Electric. All rights reserved.

2 33003538 04/2009

Table of Contents

Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Part I Functional Description . . . . . . . . . . . . . . . . . . . . . . . 9Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Overview of the Converter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Installation and Authorization of the Converter . . . . . . . . . . . . . . . . . . . . . 13Conversion with the Conversion Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 Converting Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Process of Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 Converting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Converting a File in Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Trouble Shooting after Converting a File. . . . . . . . . . . . . . . . . . . . . . . . . . 21

Part II Converted Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Chapter 4 Converted Data in General. . . . . . . . . . . . . . . . . . . . . . . . 25

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Network Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Constants, Symbols, Networks, Segments and Comments . . . . . . . . . . . 30State RAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Network Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Equation Networks ProWORX32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Not Converted Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 5 Data Relation and Comment/Symbol Generation . . . . . 37Data Relation in ProWORX32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Data Relation in Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Comment and Symbol Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 6 Converted Coils, Contacts, Links and Function Blocks 43Converting Rules and Conversion Settings. . . . . . . . . . . . . . . . . . . . . . . . 44Converted Coils, Contacts and Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Converted Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Not Converted Function Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

33003538 04/2009 3

Part III Execution Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Chapter 7 Differences in the Execution Order . . . . . . . . . . . . . . . . . 55

Specific Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Example: Include 984 Execution Corrections, not set . . . . . . . . . . . . . 58Example: Include 984 Execution Corrections, set . . . . . . . . . . . . . . . . 60

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Appendix A Conversion of Compact and Momentum to Unity Pro . . 65

Compact Modules to Unity Pro Premium Modules . . . . . . . . . . . . . . . . . 66Compact Modules to Unity Pro Modicon M340 Modules. . . . . . . . . . . . . 70Momentum Modules to Unity Pro Modicon M340 Modules . . . . . . . . . . . 74

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4 33003538 04/2009

§
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.

33003538 04/2009 5

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 the installation, and has received safety training to recognize and avoid the hazards involved.

6 33003538 04/2009

About the Book

At a Glance

Document Scope

This document describes the functionality and performance scope of the LL984 to Unity Converter.

Validity Note

This document is valid for Unity Pro starting from Version 4.1.

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 [email protected].

Title of Documentation Reference Number

Unity Pro Enhanced LL984 Block Library 33003745

Unity Pro Software Reference Manual -

Unity Pro Software Operating Modes Manual -

33003538 04/2009 7

8 33003538 04/2009

33003538 04/2009

I

Functional Description

33003538 04/2009


General

This part comprises an overview of the installation and the functional range of the converter.

What's in this Part?

This part contains the following chapters:

Chapter Chapter Name Page

1 Introduction 11

2 Converting Process 17

3 Converting Procedure 19

9


10 33003538 04/2009

33003538 04/2009

1

Introduction

33003538 04/2009

Introduction

General

If installed, this converter component is an integrated part of Unity Pro.

It is used to convert ProWORX32 projects to Unity Pro.

Modsoft and Concept (also mixed IEC LL984) projects can be converted, too, but restrictions may apply. In such a case convert to a ProWORX32 project first.

What's in this Chapter?

This chapter contains the following topics:

Topic Page

Overview of the Converter 12

Installation and Authorization of the Converter 13

Conversion with the Conversion Wizard 15

11

Introduction

Overview of the Converter

General

The converter is used to convert ProWORX32 projects to Unity Pro.

Coils, contacts, links and function blocks are replaced by the respective objects provided by Unity Pro. Subsequently Unity Pro source code is generated according to the IEC LD format.

Versions

The converter will work with the following versions:ProWORX32 V1.11, V1.1, V2.xModsoft 2.61 (conversion may be limited)Concept V2.6 (conversion may be limited)

Starting the Converter

Unity Pro automatically launches the converter after the file to be converted has been selected.

To handle the special formats of Modsoft, ProWORX32 and Concept the converter is embedded in an appropriate framework of the Unity Pro architecture.

By opening the respective project files (*.env, *.pwx, *.asc) the converter is launched out of this framework.

The converter checks whether the project files are valid and show the suitable file formats.

Error Handling

If it is not possible to convert certain objects they will be replaced by dummy EFBs with comments which include detailed error messages.

Error messages will be logged on the report file and will be displayed on the message window during the analysis time. The user is able to go to the error spot of the network by double clicking the error message line in the message window.

Conversion Wizard

Please refer to Conversion with the Conversion Wizard, page 15.

12 33003538 04/2009

Introduction

Installation and Authorization of the Converter

General

The converter has to be installed as an additional software component of Unity Pro.

After the installation the converter is an integrated part of Unity Pro.

For additional information please refer to the LL984 to Unity Converter install document delivered with the converter software.

Uninstallation

In case you previously installed an earlier version of the converter on your PC, you have to remove the existing installation first, before you install the LL984 to Unity Converter.

NOTE: Do not uninstall the Enhanced LL984 Block Library.

Installation

Step Action

1 Verify that you are logged on to your PC with administrator access rights.

2 Close Unity Pro.

3 Via Start → Control Panel → Add or Remove Programs search for LL984 to Unity Converters and remove them.

4 Close Add or Remove Programs and Control Panel.

5 Start 984_Clean.exe, which is delivered with the converter.

Step Action

1 Start the setup.exe.

2 Enter Name and Company.Result:The converter software is installed.

33003538 04/2009 13

Introduction

Authorization

It is not possible to use the converter in demo mode.

Before using the converter has to be authorized. Each new version of the converter has to be authorized again.

For instructions how to authorize, please refer to the separately provided install document.

Unity Pro Service Pack

After installation of a Unity Pro service pack you must reinstall the converter.

If there is... Then ...

no authorization on your PC yet. during installation you are asked to request an authorization from Schneider Electric. You can leave the authorization wizard with Cancel.each time you try to start the converter, you will be asked for authorization. If you do not authorize, the conversion is canceled.

already an authorization (of the same converter version) on your PC.

there is no need to authorize again.

already an authorization on another PC.

you are allowed to transfer the license from the other PC.

14 33003538 04/2009

Introduction

Conversion with the Conversion Wizard

Application Conversion as a Whole

To convert an application as a whole, while keeping the same PLC family, and selection of application parts or remapping of I/O objects is not needed, use the LL984 to Unity Converter directly via the Unity Pro menu File → Open.

Partial Application Conversion

To convert an application partially and/or the PLC family must be changed or remapping of I/O objects is needed, use the conversion wizard via the Unity Pro menu Tools → Convert Partially.

For detailed information, please refer to the Operating Modes Manual -> Conversion Wizard.

Conversion Wizard

The conversion wizard is an integrated part of Unity Pro.

You can use it toconvert applications, exported out of legacy applications (ProWORX, Concept, Modsoft) 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 concurrently the hardware configuration of the new application in Unity Pro.modify the amount of used memory in the CPU.

The conversion wizard is available if you have chosen to install a converter (e.g. LL984 to Unity Converter) during the setup of Unity Pro.

33003538 04/2009 15

Introduction

General Procedure

General procedure to convert a legacy application to Unit Pro

Conversion Wizard Documentation

For detailed information on the conversion wizard, please refer to the Operating Modes Manual -> Conversion Wizard.

Step Action

1 Export your application out of your legacy programming system (e.g. as an ASC file out of Concept).

2 Create a new application in Unity Pro selecting a CPU with enough memory and the I/O access capabilities needed.Optionally you can configure the I/O modules expected to be needed but you can modify the hardware configuration even later (see step 6).

3 Launch the conversion wizard in Unity Pro via Tools → Convert Partially.Result: The conversion wizard asks you to select the exported legacy source file.

4 Select the exported legacy source file.Result: The converter analyzes the source file and displays the result in the 3 tabs of the conversion wizard.

5 Select the parts of the application (or the complete application) to be converted in the Structure tab.

6 Remap the I/O objects for getting them compliant with the new hardware configuration.Concurrently you can modify the hardware configuration of the new application in Unity Pro.Note: To save a backup file of your intermediate I/O mapping you can use the Save button. With Load you can reload your latest saved intermediate I/O mapping.

7 After finishing all your selections and manual modifications click OK.Result: The converter applies the defined remapping to the selected parts of the source file and imports the results into the opened Unity Pro Application.

8 Continue working on the opened application, save it or export as an XEF file.

16 33003538 04/2009

33003538 04/2009

2

Converting Process

33003538 04/2009

Converting Process

Process of Conversion

General


The converter checks the selected file for validity and suitable formats.

Subsequently Unity Pro source code is generated according to the IEC LD format.

Presentation

Presentation of the converting process:

17

Converting Process

Stages of the conversion:

Dummy DFBs

Further information you will find under Dummy DFBs, page 52.

Stage Description

1 In Unity Pro the file to be converted (ProWORX32, Modsoft, Concept) is selected. Through this the converter is launched automatically.

2 The selected file is checked for validity and suitable formats by the converter.

3 Coils, contacts, links and function blocks are replaced by the respective objects provided by Unity Pro.

4 If it is not possible to convert certain objects they will be replaced by dummy DFBs with comments which include detailed error messages.Error messages will be logged on the report file and will be displayed on the message window during the analysis time. The user is able to jump to the error spot of the network by double clicking the error message line in the message window.

5 Subsequently Unity Pro source code is generated according to the IEC LD format and is shown in the Unity Pro main window.

18 33003538 04/2009

33003538 04/2009

3

Converting Procedure

33003538 04/2009


Overview

This chapter comprises information on the procedure of conversion.



Topic Page

Converting a File in Unity Pro 20

Trouble Shooting after Converting a File 21

19


Converting a File in Unity Pro

General


The file to be converted can be selected by the menu File → Open.

Export of a Concept Project

Concept projects have to be exported into a text file (*.asc).

After that it is possible to open this file in Unity Pro. The converter will be launched automatically.

Modsoft (*.env) and ProWORX32 (*.pwx) projects can be opened directly.

Converting a File

Proceed as follows to convert a file to Unity Pro:

Cancel the Conversion

The conversion can be canceled by clicking the Cancel button in the progress dialog box.

Step Action

1 Open the dialog box for selecting a file by clicking File → Open.

2 Select the respective file type.

3 Select the source file that should be converted.

4 Confirm with the Open button.

5 The converting process will be started and a progress bar is showing the proceeding of the conversion.

20 33003538 04/2009


Trouble Shooting after Converting a File

General

If it is not possible to convert certain objects the converter will replaced them by dummy DFBs with comments which include detailed error messages.

Trouble Shooting

Error messages will be logged on the report file and will be displayed on the message window during the analysis time.

By double clicking the error message line in the message window the user is able to jump to the error spot of the network and correct the errors step by step.

Analyze Project

To ensure that the project contains no more errors after trouble shooting, select the menu command Build → Analyze Project.

33003538 04/2009 21


22 33003538 04/2009

33003538 04/2009

II

Converted Data

33003538 04/2009

Converted Data

General

This part comprises information on the data that is converted out of ProWORX32, Modsoft and Concept projects to Unity Pro.

What's in this Part?

This part contains the following chapters:

Chapter Chapter Name Page

4 Converted Data in General 25

5 Data Relation and Comment/Symbol Generation 37

6 Converted Coils, Contacts, Links and Function Blocks 43

23

Converted Data

24 33003538 04/2009

33003538 04/2009

4

Converted Data in General

33003538 04/2009


General

This chapter comprises information on the data that is converted out of ProWORX32, Modsoft and Concept projects to Unity Pro and on objects that can not be converted or will be replaced by the respective objects provided by Unity Pro.



Topic Page

Configuration 26

Network Structure 29

Constants, Symbols, Networks, Segments and Comments 30

State RAM 32

Network Dimensions 34

Equation Networks ProWORX32 35

Not Converted Objects 36

25


Configuration

Modsoft Configuration Section

Modsoft is a DOS-based PLC programming tool using the LL984 language.

The Modsoft configuration section comprises the following elements:

PLC nameModel name (PLC type)System memory sizeExtended memory sizeASCII message tableI/O port informationDrop headsSegment schedulesSpecial functionsLoadable instructionsComments

26 33003538 04/2009


ProWORX32 Configuration

ProWORX32 is unlike Modsoft a Microsoft Windows-based PLC programming tool using the LL984 language.

The ProWORX32 configuration comprises the following:

PLC configurationQuantum984 -785E (converted to Quantum)Compact (converted to Modicon M340 or Premium)Momentum (converted to Modicon M340)

For the conversion of Compact and Momentum modules to Unity Pro please refer to the Appendix Conversion of Compact and Momentum to Unity Pro, page 65.Traffic Cop

800 series I/O200 series I/ODCP series (not converted)Momentum I/O

CommunicationConfiguration Extensions

Data Protect (not converted)Peer CopS980 Addresses (not converted)Quantum Hot Standby (not converted)Profibus (not converted)TCP/IPSY/MAXI/O ScannerQuantum Security (not converted)

NOTE: Please observe that the list items above highlighted as (not converted) will not be converted from ProWORX32 to Unity Pro.

33003538 04/2009 27


Concept Projects

A Concept project first has to be exported into a text file (ASCII file).

If such a Concept file contains LL984 sections and the user tries to open that file in Unity Pro, the converter will be launched automatically.

All error messages will be logged on the report file and will be displayed on the message window during the analysis time. By double clicking the error message line in the message window the user is able to jump to the error spot of the network and correct the errors step by step.

Example of a LL984 section in an ASCII file:

CP_SEC "_ 1" SECTK_F_SECTION LANG_LL SVB: FALSE ID: 1 CODE_IND: 1 TEXT:

LL_NET 1 NAME: " " SONDAT: 0 TEXT:

LL_NOD COL,ROW:1,1 OPCOD: 8 VERT:1 REF: 219:_100012 TEXT:




LL_NOD COL,ROW:2,1 OPCOD: 16 VERT:0 REF: 9:15 TEXT:



LL_NOD COL,ROW:2,5 OPCOD: 16 VERT:0 REF: 9:10 TEXT:



LL_NET 2 NAME:"SHUTDOWN ALARM CONTROL" SONDAT:0 TEXT:




LL_REG 0:148 NID:11 COL,ROW: 1,3 LNG: 1 TRUE "OPEN" EC_UNKNOWN_DT_ID

LL_INS "BLKM" NID: 12 COL,ROW: 1,3




LL_INS "CLSD" NID: 1 COL,ROW: 1,5



28 33003538 04/2009


Network Structure

General

ProWORX32, Modsoft and Concept use the same network structure.

Presentation

Presentation of the network structure:

33003538 04/2009 29


Constants, Symbols, Networks, Segments and Comments

General

ProWORX32, Modsoft and Concept define constants, symbols, networks, segments and comments.

Formats in Unity Pro

The ProWORX32, Modsoft and Concept formats are converted into Unity Pro formats as follows:

NOTE: For each segment (functional module), the first network (section) is associated to segment oriented I/O-transfer (segment scheduling) and the segment comment.

Networks per Section

This option serves for separation of ProWORX32, Modsoft and Concept LL984 segments into smaller units.

The separation of segments into smaller units does not take place, if a jump is present in the segment and its target has not yet been reached. Please refer to Ignore Jumps when splitting (see page 31).

In this case separation becomes active again after the jump target.

Before starting the converting process in Unity Pro the Networks per Section option can be set via Tools → Options → Converters.

You can select a value of 1..10 networks per section.

NOTE: To put only 1 network into one section improves the performance of the respective project when editing.

Modsoft Format Unity Pro Format

constant symbol (e.g. #00002) constant

symbol variable name

symbol descriptor variable comment

1 or 10 networks section

network comment section comment

segment functional module

segment comment functional module comment

30 33003538 04/2009


Ignore Jumps When Splitting

Before starting the converting process in Unity Pro the Ignore Jumps when splitting option can be set via Tools → Options → Converters.

A section may contain jumps to labels. A jump is located inside the section.

The converter takes jumps inside the section into account since it is not allowed to have a jump from one section to another. Depending on how the jump is validated inside the section (active or not), the automatic splitting at network bounds is inhibited (active).

The feature of recognizing jump scopes can be suppressed by the Ignore Jumps when splitting checkbox. When this checkbox is enabled, automatic section splitting always takes place at all jumps. Therefore many error messages concerning jump targets will be generated at analyze time that have to be resolved manually.

See also Networks per Section (see page 30).

Paging Between Sections

According to the network mapping to sections in Unity Pro, an easy navigation function between sections is established, to provide similar behavior as in ProWORX32 with its network paging commands.

Ctrl + Alt + PgUp = display previous networkCtrl + Alt + PgDown = display following network

Symbols Instead of Direct Address

This option applies to contacts and coils that have a state RAM address in LL984, which no symbol is defined for.

Before starting the converting process in Unity Pro the Symbols Instead of Direct Address option can be set via Tools → Options → Converters.

If it is set, the converter replaces the direct address, which is derived from the state RAM address, by a generated symbol.

ProWORX32 LL984 allows to define non-unique descriptors and short comments to document contact and coil meaning.

The converter constructs unique symbols (Unity Pro variable names) as defined in the Symbol Generation Rule.

For detailed information on how symbols (variable names) are invented see Comment and Symbol Generation (see page 40).

Please also refer to Max. Symbol Length (see page 46).

33003538 04/2009 31


State RAM

General

The organization of data memory in the Quantum family is not changed in Unity Pro.

For the Compact and the Momentum families topological addresses are generated.

In order to provide a unified view of data memory, the state RAM areas are mapped using the notation used in IEC 61131. As a second step the data in these areas that correspond to data from I/O modules have an additional, topological address that can be used to access the data.

Notation

The new notation for state RAM maps directly onto the traditional state RAM notation:

Example:

Forced Outputs (%M)

Traditional New Data Storage

0xxxx %M or %Q output coils (bit output)

1xxxx %I input coils (bit input)

3xxxx %IW input words

4xxxx %MW or %QW output words

Traditional notation of the first output coil: 00001

New notation: %M1

WARNINGRISK OF UNINTENDED EQUIPMENT OPERATION

Do not rely on memory protect switch.

The behavior of forced outputs (%M) between ProWORX32/Modsoft/Concept and Unity Pro has changed.

With ProWORX32/Modsoft/Concept you cannot force outputs with the Quantum CPU memory protect switch in position "On".With Unity Pro you can force outputs with the Quantum CPU memory protect switch in position "On".

Failure to follow these instructions can result in death, serious injury, or equipment damage.

32 33003538 04/2009



Reforce outputs after a cold start.

The behavior of forced outputs (%M) between ProWORX32/Modsoft/Concept and Unity Pro has changed.

With ProWORX32/Modsoft/Concept forced outputs keep their state after a cold start.With Unity Pro forced outputs lose their state after a cold start.


33003538 04/2009 33


Network Dimensions

LL984 format

The LL984 network dimensions are 11 columns by 7 rows.

IEC LD format

While converting a LL984 network into an IEC LD network columns and rows are added. Amongst others this is done to create extra space for variables that are shown in additional rows of the function blocks.

34 33003538 04/2009


Equation Networks ProWORX32

ProWORX32 Equation Network

Example of an equation network in ProWORX32:

Network Converted to Unity Pro

The converted network is shown in Unity Pro as follows:

33003538 04/2009 35


Not Converted Objects

Loadables

Loadables will be replaced by dummy DFBs with comments which include detailed error messages.

Loadables are e.g. EUCA, MBUS, PEER etc.

EXE Loadables

ULEX and XMIT are EXE loadables. They will not be converted, but will be supported as part of the new high end PLC Unity Executive Runtime.

ULEX is required for Quantum expert I/O modules and is implemented in Unity firmware.XMIT function block will be supported as an IEC-EFB named XXMIT.

If an XMIT loadable instruction was used in the ProWORX32 project, an empty DFB will be created in the converted Unity Pro project called OPC_31_XMIT_EUCA_ETC.

This empty DFB is connected inside the hosting Unity Pro network as the XMIT instruction was in ProWORX.

The user now has to place the IEC XXMIT function block in this DFB and connect and configure it accordingly.

Please also refer to Not Converted Function Blocks (see page 52).

ASCII Messages

ASCII messages will not be converted.

6x Range

6x range (register in expanded memory) will not be converted.

Multiple Use of Segments

If a segment is called several times in the segment scheduler (multiple use), it will be converted and executed in Unity Pro only once.

In this case you have to identify the segment calls in the source program by yourself and you have to reorganize the scheduling in the Unity Pro program with help of subroutines.

Modsoft SFC

Modsoft SFC will not be converted.

36 33003538 04/2009

33003538 04/2009

5

Data Relation and Comment/Symbol Generation

33003538 04/2009


General

This chapter comprises information on data relation in ProWORX32 and Unity Pro and information on comment and symbol generation.



Topic Page

Data Relation in ProWORX32 38

Data Relation in Unity Pro 39

Comment and Symbol Generation 40

37


Data Relation in ProWORX32

General

The ProWORX32 user interface shows several relations between references and text.

State RAM Reference tonon-unique Descriptorsa Short Commenta Long Commenta unique Symbol

Example

38 33003538 04/2009


Data Relation in Unity Pro

General

Unity Pro relates in its Data Editor direct addresses, unique symbols with a restricted character set, comments and data types.

Direct Addresses

Direct addresses have a default data type. Type checking is strongly done in programs.

If a variable with a direct address needs to have a data type different from the default type, a declaration must be given at minimum with symbol, direct address, and data type.

Data Types

The data types in converted LL984 programs are determined by the block library and the requirement to clearly show overlaps of memory areas, and to avoid access to non- declared memory areas.

The blocks work with unsigned-integer arrays of different sizes or with derived data structures, as predefined by the 984 ladder logic blocks.

33003538 04/2009 39


Comment and Symbol Generation

General

A variable in ProWORX32 can have different properties:Reference (flat address)SymbolDescription (concatenation of Descriptors)Short CommentLong Comment

How comments and symbols are generated during conversion depends on the option settings in Unity Pro (Tools → Options → Converters).

Flat or Topological Addresses

Depending on the target platform and the respective option set under Tools → Options → Converters a flat or a topological address is generated during conversion.

Correction of Symbols (Variable Names)

Symbols (variable names) are corrected during conversion to conform with Unity Pro rules.

Not allowed characters ("#", "$", "&", " ", ...) are replaced by underscore (_).If 2 underscores result in sequence only 1 underscore is inserted instead.An underscore at the end is eliminated.

Therefore it can occur that symbols (variable names) are no more unique. They must be corrected by the user. For further information please refer to Trouble Shooting after Converting a File (see page 21).

Max.Symbol Length

Before starting the converting process in Unity Pro the Max.Symbol Length can be set via Tools → Options → Converters → LL984.

40 33003538 04/2009


Comment Generation Rule

The Comment Generation Rule can be set via Tools → Options → Converters → LL984.

With help of this option it is possible to composite a variable comment from different source strings.

Possible parameters for comment generation are:Sx = short comment (x could be 1 to 4)Dx = descriptors (x could be 1 to 9)L = long comment

Syntax for the Comment Generation Rule

The syntax must be entered without blanks.

Between all different source strings a blank character will be generated for the new comment in Unity Pro.

General Symbol Generation Rules

General rules:If a Symbol is defined for state RAM data, this symbol will be used as variable name.Only if no symbols are defined, a variable name will be generated with help of Symbol Generation Rule.

Variable name source priority (1 = highest):1. state RAM symbol2. concatenated string with help of Symbol Generation Rule

Example Result

D1-5 ProWORX32 descriptors 1 to 5 will be concatenated to 1 comment string

S.1.5.8 S.1 = ProWORX32 short comment 1.5 = begin on character 5.8 = length = 8 characters

S1.5.8D4D9D1 String from short comment 1, beginning on character 5 with length 8, then descriptor 4, then descriptor 9, then descriptor 1 will be concatenated to the new variable comment.

33003538 04/2009 41


Symbol Generation Rule

The Symbol Generation Rule can be set via Tools → Options → Converters → LL984.

With help of this option it is possible to composite a variable name (symbol) from different source strings.

Possible parameters for symbol generation are:Sx = short comment (x could be 1 to 4)Dx = descriptors (x could be 1 to 9)L = long commentF = flat address (string without % character e.g. MW150)

Syntax for the Symbol Generation Rule

The syntax must be entered without blanks.

Between all different source strings an underline (_) will be generated for the new symbol in Unity Pro.

If a source string is empty, it will be omitted.

If Max.Symbol Length is exceeded, the variable name (symbol) will be shortened.

Example Result

FD1 F = first part of the symbol will be the flat address without % character (e.g. MW150)D1 = content of descriptor 1 (e.g. DescriptorONEThe new symbol will be MW150_DescriptorONE)

42 33003538 04/2009

33003538 04/2009

6

Converted Coils, Contacts, Links and Function blocks

33003538 04/2009

Converted Coils, Contacts, Links and Function Blocks

General

This chapter comprises information on the coils, contacts, links and function blocks that are converted out of ProWORX32, Modsoft and Concept projects to Unity Pro and on objects that can not be converted or will be replaced by the respective objects provided by Unity Pro.



Topic Page

Converting Rules and Conversion Settings 44

Converted Coils, Contacts and Links 50

Converted Function Blocks 51

Not Converted Function Blocks 52

43


Converting Rules and Conversion Settings

Placing Objects and Links

To achieve a proper presentation of the converted LL984 sections in Unity Pro, the following rules are applied.

Rules for object placing:The distance between two objects must be at least one cell.When two function blocks are connected, the minimum distance must equal the number of cells of the first function block’s width.The cells in Unity are smaller. If an function block partially occupies another cell, an additional cell is required for the function block.If an object (contact or coils) has a vertical link (OR Link), this vertical link will be located at the end of the cell of the object.An additional cell is required if:

a vertical link (OR Link) with an INPUT function block existsthe source function block has output variablesthe target function block has input variables

A coil may not be directly connected to the left bus bar.

Rules for the conversion of function block links:Function block links between variables/constants and function blocks will be ignored. In these cases, Unity will automatically create a link.Purely horizontal function block links between objects that are not function blocks will be replaced with horizontal links with multiple segments.When two OR objects are connected, a horizontal link is first connected to the right side of the source OR object. An function block link will then be created between this horizontal link and the target object. This occurs because the two OR objects would otherwise be combined during the import into Unity.Each point of the left bus bar can only be occupied by one link.

Suppress Schedule

Sometimes the schedules of ProWORX32, Modsoft and Concept I/O drops can not be converted without errors (Invalid RIO drop).

Before starting the converting process in Unity Pro the check box Suppress Schedule can be set via Tools → Options → Converters → LL984 to suppress the association of I/O drops (Remote I/O) to sections.

This can be done to avoid analyze errors in Unity Pro.

44 33003538 04/2009


Suppress Graphs

With ProWORX32, Modsoft and Concept comment networks can be edited using links to compose large characters in a graphical way.

Unity Pro does not accept such networks, which contain only links.

Before starting the converting process in Unity Pro the check box Suppress Graphs can be set via Tools → Options → Converters → LL984 to erase all these networks during conversion.

This can be done to avoid analyze errors in Unity Pro.

Attach Coils to Open Ends

Using LL984 programming it is not mandatory to terminate a contact network with a coil.

In Unity Pro it is mandatory to terminate a contact network with a coil.

Before starting the converting process in Unity Pro the check box Attach Coils to Open Ends can be set via Tools → Options → Converters → LL984.

If this check box is set coils without assigned variables will be positioned at the open ends automatically. This is done to avoid analyze errors in Unity Pro.

Include 984 Execution Corrections

For this option please refer to chapter Differences in the Execution Order (see page 55).

Unpowered LD Objects to Left Power

Using LL984 programming it is allowed to position LD objects (contacts, links) freely in the networks (not connected to the left power rail).

In Unity Pro this would cause analyze errors.

Before starting the converting process in Unity Pro the check box Unpowered LD Objects to Left Power Rail can be set via Tools → Options → Converters → LL984.

If this check box is set unpowered LD objects will be connected to the left power rail automatically.

Comment Generation Rule

The Comment Generation Rule can be set via Tools → Options → Converters → LL984.

With help of this option it is possible to composite a variable comment from different source strings. Please refer to Comment and Symbol Generation (see page 40).

33003538 04/2009 45


Symbol Generation Rule

The Symbol Generation Rule can be set via Tools → Options → Converters → LL984.

With help of this option it is possible to composite a variable name (symbol) from different source strings. Please refer to Comment and Symbol Generation (see page 40).

Max. Symbol Length

In Unity Pro the maximum variable name length is 32 characters.

In case symbols are generated by the converter, long variable names might occur, which will then interfere with the display of the logic elements.

To enable a proper logic display, the max symbol length can be limited via an option setting in Unity Pro.

Set the Max. Symbol Length via Tools → Options → Converters → LL984 before starting the conversion process.

If Max. Symbol Length is exceeded, the variable name (symbol) will be shortened at the end.

Please also refer to Symbols Instead of Direct Address (see page 31).

Further Conversion Settings

For further conversion settings please refer to Constants, Symbols, Networks, Segments and Comments (see page 30).

Objects to Recognize Transitions

The different ways of handling ladder diagram (LD) objects in Concept (calling an function block) and in Unity Pro (system call) makes the use of State RAM variables (0x/1x register) necessary.

Because of the requirement that several write accesses to the 0x/1x register are possible during a cyclical sweep, there can be differing Online behavior between Concept and Unity Pro.

The objects affected are:Positive transition-sensing contactNegative transition-sensing contact

In Concept the "Old Value" to recognize a transition will only be updated once per cycle.

In Unity Pro the "Old Value" will be updated during every write access.

46 33003538 04/2009


Example:

Concept: Switch %QX1 from 0 -> 1 and the value of %MW1 and %MW2 increase.

Unity Pro: Switch %QX1 from 0 -> 1 and only the value of %MW1 increases.

NOTE: Use objects to recognize transitions with a certain variable only once per cycle.

Forcing Transition-Sensing Contacts

Unity Pro shows a different behavior from ProWORX32 when forcing a transition-sensing contact.

In ProWORX32, when the force value creates a trigger transition, there will be a high signal for 1 cycle at the output of the contact.In Unity Pro the output will show a static signal and transition-sensing is lost.

When positive transition contacts are forced they behave like a normally open contact showing continuously the force value at its output.When negative transition contacts are forced they behave like a normally closed contact showing the reverse of its forced status value at its output.

This behavior only occurs when transition-sensing contacts are forced directly.


Do not directly force variables connected to transition-sensing contacts.

Your application may not behave as intended.


33003538 04/2009 47


If it is planned to force a variable and sense its transition by a transition-sensing contact, decouple the logic by adding a new contact followed by a coil on top of the previous logic.

In example 1, a positive transition of variable A is supposed to be recognized and B should therefore be set for a cycle. This is true as long as variable A is not forced.

In case variable A is forced to 1, in Unity Pro the transition-sensing is lost and variable B will be set to a constant 1 value.

Example 1

To be able to force variable A and also to recognize the positive transition, the logic has to be extended by a normally open contact followed by a coil on top of the previous logic.

In example 2, variable A is assigned to the normally open contact. Variable C is first assigned to the coil and then to the link to recognize positive transitions.

When A is forced to 1, variable C will be set to 1. The positive transition of C is then recognized by the positive transition contact and B is set for 1 cycle.

Example 2

For further information refer to Unity Pro documentation Edge Recognition.

48 33003538 04/2009


Enhanced Graphics (Hidden Option)

To take advantage of optimized graphics without deviations, a hidden option EnhanceGraphics=”1” can be used.

However, in some cases unwanted connections are generated.

If you use this hidden option, check the whole application carefully.

Step Action

1 To activate this hidden option, close Unity Pro.

2 With Notepad open the file _ll984conv.xml in the Unity Pro installation directory.

3 Add the attribute in the second enclosure starting with <Conversion...>.

4 Edit EnhanceGraphics=”1” directly after the word Conversion.

5 Save the file.

6 Close Notepad.

7 Start Unity Pro again,

33003538 04/2009 49


Converted Coils, Contacts and Links

General

All coils, contacts and links are converted to Unity Pro technically one-to-one.

NOTE: Please note the different execution order of transition-sensing objects in Concept and Unity Pro as described under Objects to Recognize Transitions, page 46.

Converted Coils, Contacts and Links

The following coils, contacts and links are converted to Unity Pro:

Normal coilNormally open contactNormally closed contactPositive transition-sensing contactNegative transition-sensing contactHorizontal shortVertical short

NOTE: Retentive coils are converted to normal coils.

Behavior of Coils after Power-on

The behavior of coils after power-on has changed between 984 PLCs and Unity Pro PLCs.

With 984 PLCs, if a retentive (latched) coil is re-energized after PLC lost power, the retentive coil will keep its state for 1 scan when the PLC’s power is restored.Normal coils will be set to 0 when the PLC's power is restored.With Unity Pro PLCs all coils keep their state after power is restored.That means all coils in Unity Pro will behave like retentive (latched) coils in 984 PLCs.


Do not rely on power-on behavior of 984 PLC coils in Unity Pro.

Check the usage of coils and if necessary reset the coils in the first scan with help of additional logic.


50 33003538 04/2009


Converted Function Blocks

General

All function blocks listed in the Unity Pro Enhanced LL984 Block Library are converted to Unity Pro one-to-one.

Information on function blocks that can not be converted you will find under Not Converted Function Blocks, page 52.

Suffixes

The converter automatically translates the LL984 register types (0x, 4x) to suffixes attached to the original block names.

Example for the BLKM block:LL_BLKM_BBLL_BLKM_BILL_BLKM_IBLL_BLKM_II

Meaning of the suffixes:

For further information please refer to the respective block description in the Unity Pro Enhanced LL984 Block Library manual.

Suffix First Parameter Second Parameter

_BB 0x 0x

_IB 4x 0x

_BI 0x 4x

_II 4x 4x

_B constant or register 0x

_I constant or register 4x

33003538 04/2009 51


Not Converted Function Blocks

General

All function blocks listed in the Unity Pro Enhanced LL984 Block Library are converted to Unity Pro one-to-one.

Function blocks that can not be converted will be replaced by dummy DFBs with comments which include detailed error messages.

Error messages will be logged on the report file and will be displayed on the message window during the analysis time. By double clicking the error message line in the message window the user is able to jump to the error spot of the network and correct the errors step by step.

Dummy DFBs

A dummy DFB provides the following informations:The name of a dummy DFB is composed out of "LL_OP_" and the "xx”.“xx” is the decimal representation of the Op-Code.For example an Op-Code 255 that can not be allocated to an LL984 instruction will be converted to a dummy DFB named LL_OP_255.

NOTE: As an exception the Op-Code 31 will be converted to a dummy DFB named OPC_31_XMIT_EUCA_ETC.

All original parameters are listed.An error message is displayed in the section: ConvError(Empty DFB to be filled by user)

Please also refer to Not Converted Objects (see page 36).

Examples

The following table lists function blocks that are not provided by Unity Pro.

LL984 Function Blocks (LOADABLE)

CHS

EUCA

MBUS

PEER

MAP3

MRTM

HLTH

52 33003538 04/2009

33003538 04/2009

III

Execution Order

33003538 04/2009

Execution Order

53

Execution Order

54 33003538 04/2009

33003538 04/2009

7

Differences in the Execution Order

33003538 04/2009


General

This chapter comprises information on the problem that the IEC LD execution order in Unity Pro may differ from the execution order of the original LL984 section in ProWORX32, Modsoft or Concept.

This fact has to be taken into account while converting a ProWORX32, Modsoft or Concept project to Unity Pro.



Topic Page

Specific Characteristics 56

Example: Include 984 Execution Corrections, not set 58

Example: Include 984 Execution Corrections, set 60

55


Specific Characteristics

General

The LL984 execution order is different from the execution order in IEC LD.The execution order in LL984 is column-by-column.Example of execution order in LL984.

The execution order in IEC LD is row-by-row but with the qualification that no element of a network will be evaluated until the states of all of its inputs have been evaluated (according to IEC 61131).Example of execution order in IEC LD

Execution Corrections

Before starting the converting process in Unity Pro the check box Include 984 Execution Corrections can be set via Tools → Options → Converters → LL984.

If this is done the converter modifies the section so that the result in Unity Pro is the same as in ProWORX32, Modsoft or Concept. See Example: Include 984 Execution Corrections, set, page 60.If the check box is not set there may be differences in the result of the respective sections. See Example: Include 984 Execution Corrections, not set, page 58.

56 33003538 04/2009


Error Message

If the check box Include 984 Execution Corrections is not set, an error message will be logged on the report file and will be displayed on the message window during the analysis time.

This error message reminds the user that the execution order may be changed.

Function Blocks, Execution Order

If the check box Include 984 Execution Corrections is set, the converter modifies the section so that the execution order of function blocks in Unity Pro will be the same as in the original LL984 section.

This is done by linking the EN and ENO parameters of the single function blocks.

Scanning Time

It can not be guaranteed that the scanning time of the converted section is the same as of the original section. Maybe there will be a longer scanning time.

33003538 04/2009 57


Example: Include 984 Execution Corrections, not set

Different Execution Order

If the check box Include 984 Execution Corrections is not set before starting the converting process in Unity Pro via Tools → Options, there may be differences in the result of the respective sections.

It may happen that references (coils/contact) are evaluated only when they have changed their state.

LL984 Network

Example network from a LL984 project:

LL984 Execution Order

The execution order in LL984 is column-by column:

The normal coil (#000144) is referenced by the normal open contacts in the 2nd and the 5th row and the normal coil (#000144) gets executed at the end. This is the correct order in LL984.

58 33003538 04/2009


IEC LD Execution Order

The execution order in IEC LD is row by row but with the qualification that no element of a network will be evaluated until the states of all of its inputs have been evaluated:

The normal coil (#000144) gets executed before the referenced normal open contact in the 5th row is evaluated.

NOTE: The execution order has been changed and the result of the converted IEC LD section will be different from the result of the original LL984 section.

33003538 04/2009 59


Example: Include 984 Execution Corrections, set

Set the Check Box

If the check box Include 984 Execution Corrections is set before starting the converting process in Unity Pro via Tools → Options, the converter modifies the section so that the result in Unity Pro is the same as in ProWORX32, Modsoft or Concept.

LL984 Network

Example network from a LL984 project:

LL984 Execution Order

The execution order in LL984 is column-by column:

The normal coil (#000144) is referenced by the normal open contacts in the 2nd and the 5th row and the normal coil (#000144) gets executed at the end. This is the correct order in LL984.

60 33003538 04/2009


Modified Network

The converter modifies the section by adding auxiliary coils and contacts with the prefix _d_:

IEC LD Execution Order

The execution order in IEC LD is now:

So the contact _d_M144 receives the value of the previous execution cycle as it is with the LL984 execution order.

NOTE: The execution order is maintained but the result of the converted section will be the same as the result of the original LL984 section.

33003538 04/2009 61


62 33003538 04/2009

33003538 04/2009

Appendices

33003538 04/2009 63

64 33003538 04/2009

33003538 04/2009

A

Conversion of Compact and Momentum to Unity Pro

33003538 04/2009


Overview

This chapter includes information on the conversion of Compact and Momentum modules to Unity Pro supported modules.



Topic Page

Compact Modules to Unity Pro Premium Modules 66

Compact Modules to Unity Pro Modicon M340 Modules 70

Momentum Modules to Unity Pro Modicon M340 Modules 74

65


Compact Modules to Unity Pro Premium Modules

Overview

Compact modules can either be converted to Unity Pro Premium or Modicon M340 modules depending on the conversion settings.

To define that Compact applications will be converted to Unity Pro Premium applications, open the Conversion Settings tab via Tools → Options in Unity Pro and activate the Map Compact to Premium check box before converting.

If you select conversion to Unity Pro Premium modules, the Compact modules are converted as listed in the table below.

If the check box is not activated, Concept Compact applications are converted to Modicon M340 applications (see Compact Modules to Unity Pro Modicon M340 Modules, page 70).

Manual Corrections

NOTE: The LL984 to Unity Converter converts as far as possible the modules when equivalencies are existing. It is mandatory to check the result according to the process needs. The settings of the hardware modules (parameters) are not converted but set to default values and must be entered for each module in Unity Pro. Channel objects are converted as far as possible. Nevertheless, the program may have to be adapted according to the different behavior with the original module.

Modules

For modules not listed below, no equivalence in Unity Pro is available and there will be an empty slot in the rack.

Compact Module Name Comment Converted to Premium

ADU 204 4 Channel Register Input AEY420

AS-BADU204/254 4 Channel Register Input AEY420


AS-BADU205 4 Channel Register Input AEY420


AS-BADU206/256 4 Channel Register Input AEY414

ADU 210 4 Channel Voltage/Current Input AEY414

AS-BADU210 4 Channel Voltage/Current Input AEY414

ADU 211 16I ANA. THERMO. AEY1614

AS-BADU211/212 16I ANA. THERMO. AEY1614

ADU 212 8 Channel Analog Input Module AEY1614

66 33003538 04/2009


ADU 214 4 Channel Multi Range A/D Input AEY414

AS-BADU214 4 Channel Multi Range A/D Input AEY414

ADU 216 8 Channel Thermocouple AEY1614

AS-BADU216 8 Channel Thermocouple AEY1614

ADU 257 8 Channel Thermocouple AEY1614

AS-BADU257 8 Channel Thermocouple AEY1614

BKF 202 INTERBUS S Slave IBY100

BKF201-16 16 Word INTERBUS S Master IBY100

BKF201-64 64 Word INTERBUS S Master IBY100

CM900 Auto Interface empty slot

DAO 216 24 VDC 16 Point Output Module DSY16T2

AS-BDAO216 24 VDC 16 Point Output Module DSY16T2

DAP 204 24 VDC 4 Point Relay (NO) Module DSY08R5

AS-BDAP2x4 24 VDC 4 Point Relay (NO) Module DSY08R5

DAP 208 24 VDC 8 Point Relay (NO) Module DSY08R5

AS-BDAP208/258 24 VDC 8 Point Relay (NO) Module DSY08R5

DAP 209 120 VAC 8 Point Output Module DSY16S4

AS-BDAP209 120 VAC 8 Point Output Module DSY16S4

DAP 210 24-230 VAC 8 Point Output Module DSY16S4

AS-BDAP210 24-230 VAC 8 Point Output Module DSY16S4

DAP 211 120 VAC Press and Stamp Module DMY28FK

AS-BDAP211 120 VAC Press and Stamp Module DMY28FK

DAP 212 24 VDC 8 Point Input/4 Point Output DMY28FK

DAP 216 24 VDC 16 Point Output Module DSY16T2

AS-BDAP216 (O/N) 24 VDC 16 Point Output Module DMY28FK

DAP 217 5-24 VDC 16 Point Output Module DSY16R5

AS-BDAP217 5-24 VDC 16 Point Output Module DSY16R5

DAP 218 24-240 VAC 16 Point Output Module DSY16S5

AS-BDAP218 24-240 VAC 16 Point Output Module DSY16S5

DAP 220 24 VDC 8 Point Input/Output Module DMY28FK

AS-BDAP220/250 24 VDC 8 Point Input/Output Module DMY28FK

DAP 250 24 VDC 8 Point Input/Output Module DMY28FK

DAP 252 24 VDC 8In 4Out DMY28FK



33003538 04/2009 67


DAP 253 110VDC 8In 4Out DMY28FK

AS-BDAP2x2/253 110VDC 8In 4Out DMY28FK


DAP 253 110VDC 8In 4Out DMY28FK

DAU 202 2 Channel Register Output ASY410

AS-BDAU2x2 2 Channel Register Output ASY410

DAU 204 4 Channel Analog Output, Opto-Isol. ASY410

AS-BDAU204 4 Channel Analog Output, Opto-Isol. ASY410

DAU 208 8 Channel Register Output ASY800

AS-BDAU208 8 Channel Register Output ASY800

DEO 216 24 VDC 16 Point Input Module DEY16D2

AS-BDE0216 24 VDC 16 Point Input Module DEY16D2

AS-BDEP2x6/2x7 24 VDC 16 Point Input Module DEY16D2

DEP 208 230 VAC 8 Point Input Module DEY16A5

AS-BDEP208 230 VAC 8 Point Input Module DEY16A5







DEP 214 12-60 VDC 16 Point Input Module DEY16D3

AS-BDEP214/254 12-60 VDC 16 Point Input Module DEY16D3

DEP 215 5 VDC TTL 16 Pt Input Module DEY16D2

AS-BDEP215 5 VDC TTL 16 Pt Input Module DEY16D2

DEP 216 24 VDC 16 Point Input Module DEY16D2

AS-BDE0216 24 VDC 16 Point Input Module DEY16D2

DEP 217 24 VDC 16 Point Input Module DEY16D2

AS-BDEP217 24 VDC 16 Point Input Module DEY16D2



DEP 220 Fast 24 VDC 16 Point Input Module DEY16FK

AS-BDEP220 Fast 24 VDC 16 Point Input Module DEY16FK

DEP 296 60 VDC 16 In DEY16D3


68 33003538 04/2009


DEP 297 48 VDC 16 In DEY16D3

DEP 257 110 VDC 16 In DEY16A4

FRQ 204 Frequency Module CTY2C

AS-BFRQ204/254 Frequency Module CTY2C

KOS260-64 64 Word Universal Comm CAY33

M7251 Programmable Limit Switch CAY33

M7350 Resolver Decoder CAY41

MOT 201 Axis Motion Control Module Encoder CAY21

MOT 202 Axis Motion Control Module Resolver & Encoder CAY22

VIC 200 4 High Speed Pulse or 4 VRC Inputs CFY11

VIC205 4 High Speed Pulse or 4 5V TTL Inputs CFY21

VIC212 4 High Speed Pulse or 12 VDC Inputs CSY84

VIC224 4 High Speed Pulse or 24 VDC Inputs CAY42

ZAE 201 High speed Counter/Positioner (2 Relay) CTY2A

AS-BZAE201 High speed Counter/Positioner (2 Relay) CTY2A

ZAE 204 4 Channel High speed Counter/Positioner CTY4A

AS-BZAE204 4 Channel High speed Counter/Positioner CTY4A

984-A145 ProWORX32 P575634M

984-0145 ProWORX32 P575634M

984-E275 ProWORX32 P575634M

984-E285 ProWORX32 P575634M

984-E258 ProWORX32 P575634M

984-E265 ProWORX32 P575634M

A145 ProWORX32 P575634M

0145 ProWORX32 P575634M

PC-984-A145 ProWORX CPU, 8 K, 1xMB, 1xMB+ P574634M

PC-E984-258 Concept IEC CPU, 512 K, 2xMB, ET P574634M

PC-E984-265 Concept IEC CPU, 512 K, 2xMB, 1xMB+ P574634M

PC-E984-275 Concept IEC CPU, 512 K, 2xMB, 1xMB+, PC Type II P574634M

PC-E984-285 Concept IEC CPU, 1 M, 2xMB, 1xMB+, PC Type II, ET P574634M

P120 000 in 100..240 VAC, sensors 24V 0.5A PSY2600M

170 ADI 340 00 for FipIO 170ADI34000

170 ADI 350 00 for FipIO 170ADI35000

170 FNT 110 01 for FipIO 170FNT11001


33003538 04/2009 69


Compact Modules to Unity Pro Modicon M340 Modules

Overview

Compact modules can either be converted to Modicon M340 or Unity Pro Premium modules depending on the conversion settings.

To define that Compact applications will be converted to Unity Pro Premium applications, open the Conversion Settings tab via Tools → Options in Unity Pro and activate the Map Compact to Premium check box before converting (see Compact Modules to Unity Pro Premium Modules, page 66).

If the check box is not activated, Concept Compact applications are converted to Modicon M340 applications as listed in the table below.

Manual Corrections


Modules


Compact Module Name Comment Converted to Modicon M340

ADU 204 4 Channel Register Input BMXAMI0410

AS-BADU204/254 4 Channel Register Input BMXAMI0410


AS-BADU205 4 Channel Register Input BMXAMI0410


AS-BADU206/256 4 Channel Register Input BMXAMI0410

ADU 210 4 Channel Voltage/Current Input BMXAMI0410

AS-BADU210 4 Channel Voltage/Current Input BMXAMI0410

ADU 211 8 Channel Analog Input Module BMXART0814

AS-BADU211 8 Channel Analog Input Module BMXART0814

ADU 212 8 Channel Analog Input Module BMXART0814

AS-BADU211/212 8 Channel Analog Input Module BMXART0814

ADU 214 4 Channel Multi Range A/D Input BMXART0414

70 33003538 04/2009


AS-BADU214 4 Channel Multi Range A/D Input BMXART0414

ADU 216 8 Channel Thermocouple BMXART0814

AS-BADU216 8 Channel Thermocouple BMXART0814

ADU 257 8 Channel Thermocouple BMXART0814

AS-BADU257 8 Channel Thermocouple BMXART0814

BKF 202 INTERBUS S Slave InterBus-S MODULE empty slot

BKF201-16 16 Word INTERBUS S Master InterBus-S MODULE empty slot

BKF201-64 64 Word INTERBUS S Master InterBus-S MODULE empty slot

CM900 Auto Interface empty slot

DAO 216 24 VDC 16 Point Output Module BMXDDO1602

AS-BDAO216 24 VDC 16 Point Output Module BMXDDO1602

DAP 204 24 VDC 4 Point Relay (NO) Module BMXDRA0805

AS-BDAP2x4 24 VDC 4 Point Relay (NO) Module BMXDRA0805

DAP 208 24 VDC 8 Point Relay (NO) Module BMXDRA0805

AS-BDAP208/258 24 VDC 8 Point Relay (NO) Module BMXDRA0805

DAP 209 120 VAC 8 Point Output Module BMXDAO1605

AS-BDAP209 120 VAC 8 Point Output Module BMXDAO1605

DAP 210 24-230 VAC 8 Point Output Module BMXDAO1605

AS-BDAP210 24-230 VAC 8 Point Output Module BMXDAO1605

DAP 211 120 VAC Press and Stamp Module BMXDDM16022

AS-BDAP211 120 VAC Press and Stamp Module BMXDDM16022

DAP 212 24 VDC 8 Point Input/4 Point Output BMXDDM16022

DAP 216 24 VDC 16 Point Output Module BMXDDO1602

AS-BDAP216 (O/N) 24 VDC 16 Point Output Module BMXDDO1602

DAP 217 5-24 VDC 16 Point Output Module BMXDDO1612

AS-BDAP217 5-24 VDC 16 Point Output Module BMXDDO1612

DAP 218 24-240 VAC 16 Point Output Module BMXDAO1605

AS-BDAP218 24-240 VAC 16 Point Output Module BMXDAO1605

DAP 220 24 VDC 8 Point Input/Output Module BMXDDM16022

AS-BDAP220/250 24 VDC 8 Point Input/Output Module BMXDDM16022

DAP 250 24 VDC 8 Point Input/Output Module BMXDDM16022

DAP 252 24 VDC 8In 4Out BMXDDM16022

DAP 253 110VDC 8In 4Out BMXDDM16022

AS-BDAP2x2/253 110VDC 8In 4Out BMXDDM16022


33003538 04/2009 71


DAP 292 60 VDC 8In 4Out BMXDDM16022

DAU 202 2 Channel Register Output BMXAMO0210

AS-BDAU2x2 2 Channel Register Output BMXAMO0210

DAU 204 4 Channel Analog Output,Opto-Isol. BMXAMOI0210

AS-BDAU204 4 Channel Analog Output,Opto-Isol. BMXAMO0210

DAU 208 8 Channel Register Output BMXAMO0210

AS-BDAU208 8 Channel Register Output BMXAMO0210

DEO 216 24 VDC 16 Point Input Module BMXDDI1602

AS-BDE0216 24 VDC 16 Point Input Module BMXDDI1602

DEP 208 230 VAC 8 Point Input Module BMXDAI1604

AS-BDEP208 230 VAC 8 Point Input Module BMXDAI1604







DEP 214 12-60 VDC 16 Point Input Module BMXDDI1603

AS-BDEP214/254 12-60 VDC 16 Point Input Module BMXDDI1603

DEP 215 5 VDC TTL 16 Pt Input Module BMXDDI1602

AS-BDEP215 5 VDC TTL 16 Pt Input Module BMXDDI1602

DEP 216 24 VDC 16 Point Input Module BMXDDI1602

AS-BDEP216 24 VDC 16 Point Input Module BMXDDI1602

DEP 217 24 VDC 16 Point Input Module BMXDDI1602

AS-BDEP217 24 VDC 16 Point Input Module BMXDDI1602



DEP 220 Fast 24 VDC 16 Point Input Module BMXDDI1602

AS-BDEP220 Fast 24 VDC 16 Point Input Module BMXDDI1602

DEP 257 110 VDC 16 In BMXDAI1604

DEP 296 60 VDC 16 In BMXDDI1603

DEP 297 48 VDC 16 In BMXDDI1603

DEP 257 110 VDC 16 In BMXDAI1604

AS-BDEP2x6/2x7 110 VDC 16 In BMXDAI1604


72 33003538 04/2009


FRQ 204 Frequency Module BMXEHC0800

AS-BFRQ204/254 Frequency Module BMXEHC0800

KOS260-24 24 Word Universal Comm empty slot

KOS260-64 64 Word Universal Comm empty slot

M7251 Programmable Limit Switch empty slot

M7350 Resolver Decoder empty slot

MOT 201 Axis Motion Control Module Encoder empty slot

MOT 202 Axis Motion Control Module Resolver & Encoder empty slot

VIC 200 4 High Speed Pulse or 4 VRC Inputs empty slot

VIC205 4 High Speed Pulse or 4 5V TTL Inputs empty slot

VIC212 4 High Speed Pulse or 12 VDC Inputs empty slot

VIC224 4 High Speed Pulse or 24 VDC Inputs empty slot

ZAE 201 High speed Counter/Positioner (2 Relay) BMXEHC0200

AS-BZAE201 High speed Counter/Positioner (2 Relay) BMXEHC0200

ZAE 204 4 Channel High speed Counter/Positioner BMXEHC0800

AS-BZAE204 4 Channel High speed Counter/Positioner BMXEHC0800

984-A145 - BMXP342020

984-0145 - BMXP342020

984-E275 - BMXP342020

984-E258 - BMXP342020

984-E265 - BMXP342020

984-E275 - BMXP342020

984-E285 - BMXP342020

A145 ProWORX32 BMXP342020

0145 ProWORX32 BMXP342020

PC-984-A145 Concept BMXP342020

PC-984-0145 Concept BMXP342020

PC-E984-275 - BMXP342020

PC-E984-285 - BMXP342020

PC-E984-258 - BMXP342020

PC-E984-265 - BMXP342020

P120 000 , in 100..240 VAC, sensors 24V 0.5A BMXCPS2000


33003538 04/2009 73


Momentum Modules to Unity Pro Modicon M340 Modules

Overview

Momentum modules are converted to Unity Pro Modicon M340 modules.

The Momentum modules are converted as listed in the table below.

Manual Corrections


Modules


Momentum Module Name

Comment Converted to Modicon M340

Comment

171 CBB 970 30-IEC Processor, 1M Flash, Ethernet, I/O Bus BMXP342020 -

171 CCC 760 10-984 Processor Adapter, 512K, RS232, I/O Bus BMXP342020 -

171 CCC 760 10-IEC Processor Adapter, 512K, RS232, I/O Bus BMXP342020 -

171 CCC 780 10-984 Processor Adapter, 512K, RS232, RS485 BMXP342020 -

171 CCC 780 10-IEC Processor Adapter, 512K, RS232, RS485 BMXP342020 -

171 CCC 960 20-984 Proc. Adapter, 512K, Ethernet, I/O Bus BMXP342020 -

171 CCC 960 30-984 Processor, 1M Flash, Ethernet, I/O Bus BMXP342020 -

171 CCC 960 30-IEC Processor, 1M Flash, Ethernet, I/O Bus BMXP342020 -

171 CCC 960 91 Processor, 1M Flash, Ethernet, I/O Bus BMXP342020 -

171 CCC 980 20-984 Proc. Adapter, 512K, Ethernet, RS485 BMXP342020 -

171 CCC 980 30-984 Processor, 1M Flash, Ethernet, RS485 BMXP342020 -

171 CCC 980 30-IEC Processor, 1M Flash, Ethernet, RS485 BMXP342020 -

171 CCC 980 91 Processor, 1M Flash, Ethernet, RS485 BMXP342020 -

171 CCS 700 10 Processor Adapter, FAST CPU, 64K, RS232 BMXP342020 -

171 CCS 700/780 00 Processor Adapter, 64K, RS232/RS232+RS485 BMXP342020 -

171 CCS 760 00-984 Processor Adapter, 256K, RS232, I/O Bus BMXP342020 -

171 CCS 760 00-IEC Processor Adapter, 256K, RS232, I/O Bus BMXP342020 -

74 33003538 04/2009


17A-ADO-340-00 24V DC-16 Pt Output BMXDDO1602 -

17A-ADI-340-00 24V DC-16 Pt Input BMXDDI1602 -

17A-ADI-540-50 120V AC-16 Pt Input BMXDAI1604 -

17A-ADI-740-50 230V AC-16 Pt Input BMXDAI1604 -

17A-ADM-350-1X 24V DC-16 Pt Input, 16 Pt Output BMXDDM16022 -

17A-ADM-370-10 24V DC-16 Pt Input, 8 Pt @ 2A Output BMXDDM16022 -

17A-ADM-390-30 24V DC-16 Pt Input, 8 Pt Relay Output BMXDDM16022 -

17A-ADO-350-00 24V DC-32 Pt Output BMXDDO1602 -

17A-ADI-350-00 24V DC-32 Pt Input BMXDDI1602 -

17A-AAI-520-40 Analog-4 Ch RTD, Thermo Input BMXAMI0410 no thermocouple input

17A-AAO-120-00 Analog-4 Ch 0-20mA Output BMXAMO0210 too few channels

17A-AAI-030-00 Analog-8 Ch differential Input BMXAMI0410 no differential input

170-ADI-350-00 24V DC-32 Pt Input BMXDDI3202K -

170-ADI-340-00 24V DC-16 Pt Input BMXDDI1602 sink inputs

170-ADI-540-50 120V AC-16 Pt Input BMXDAI1604 -

170-ADO-350-00 24V DC-32 Pt Output BMXDDO3202K -

170-ADO-340-00 24V DC-16 Pt Output BMXDDO1602 -

170-ADM-350-1X 24V DC-16 Pt Input, 16 Pt Output BMXDDM16022 -

170-ADM-370-10 24V DC-16 Pt Input, 8 Pt @ 2A Output BMXDDM16022 too few channels

170-ADM-390-10 24V DC-16 Pt Input, 12 Pt Out 2/DIAG BMXDDM16022 too few channels

170-ADI-740-50 230V AC-16 Pt Input BMXDAI1604 only 120VAC range

170-AAI-520-40 Analog-4 Ch RTD, Thermo Input BMXAMI 0410 no thermocouple input

17A-BNO-6x1-00 BRANCH INTERFACE MODULE empty slot -

17A-ADO-530-50 120V AC-8 Pt @ 2A Output empty slot -

17A-ADO-540-50 120V AC-16 Pt Output empty slot -

17A-ADO-730-50 230V AC-8 Pt @ 2A Output empty slot -

230V AC-16 Pt Output empty slot -

17A-ADO-740-50 DFT 1 Word DG Output empty slot -

17A-IOBUS-0102 DFT 1 Word DG Input empty slot -

17A-ADM-690-5x 20V AC-10 Pt Input,8 Pt Output empty slot -

17A-ARM-370-30 24VDC 10 In/8 Out empty slot -

17A-IOBUS-0103 DFT 1 Word DG Bidirectional empty slot -



Comment

33003538 04/2009 75


17A-IOBUS-0201 DFT 2 Word DG Output empty slot -



17A-IOBUS-0231 DFT 2 Word Analog Output empty slot -

17A-IOBUS-0232 DFT 2 Word Analog Input empty slot -

17A-IOBUS-0233 DFT 2 Word Analog Bidirectional empty slot -



17A-ADM-390-10 24V DC-16 Pt Input, 12 Pt Out 2/DIAG empty slot -














17A-AAO-921-00 Analog-4 Ch 4-20mA Output empty slot -



17A-AMM-090-00 Analog 4 Ch 4-20mA Output empty slot -


17A-AEC-920-00 High-Speed Counter empty slot -


17A-AAI-140-00 Analog-16 Ch SINGLE-ENDED Input empty slot -

17A-ADM-540-80 MCC MODBUS Base empty slot -


17A-ANM-050-10 SERIPLEX INTERFACE empty slot -

17A-ANR-120-9X I/0 Base, 6I/4O Analog 8I/8O digital empty slot -



Comment

76 33003538 04/2009


17A-IOBUS-1633 DFT 12 Word Bidirectional empty slot -

170-ADM-690-5x 120V AC-10 Pt Input, 8Pt Output empty slot -

170-ADM-390-30 24V DC-10 Pt Input, 8 Pt Relay Output empty slot -

170-ADO-540-50 120V AC-16 Pt Output empty slot -

170-ADO-740-50 230V AC-16 Pt Output empty slot -

170-ADO-530-50 120V AC-8 Pt @ 2A Output empty slot -

170-ADO-730-50 230V AC-8 Pt @ 2A Output empty slot -

170-ARM-370-30 24VDC 10 In/8 Out empty slot -

170-ANM-050-10 SERIPLEX INTERFACE empty slot -

170-AAO-120-00 Analog-4 Ch 0-20mA Output empty slot -

170-AAO-921-00 Analog-4 Ch 4-20mA Output empty slot -

170-AAI-030-00 Analog-8 Ch differential Input empty slot -

170-AMM-090-00 Analog-4 Ch 4-20mA Output empty slot -

170-AEC-920-00 high-speed Counter empty slot -

170-AAI-140-00 Analog-16 Ch SINGLE-ENDED Input empty slot -

170-ADM-540-80 MCC MODBUS Base empty slot -

170-ANR-120-90 6I/4O Analog 8I/8O digital empty slot -

170-ANR-120-91 6I/4O Analog 8I/8O digital empty slot -



Comment

33003538 04/2009 77


78 33003538 04/2009

Index

33003538 04/2009

CBA
Index
Aanalyze project, 21ASCII messages, 36attach coils to open ends, 45authorization, 13

Ccoils

converted, 43, 50coils to open ends

attaching, 45cold start, 32comment and symbol generation, 40comment generation rule, 45comment/symbol generation, 37Concept

configuration, 26configuration

Concept, 26Modsoft, 26ProWORX32, 26

constants, symbols, networks, segments, comments

LL984 sections, 30Modsoft, 30ProWORX32, 30

33003538 04/2009

contactsconverted, 43, 50

conversion settings, 44, 46conversion wizard for LL984), 15converted

coils, 43, 50contacts, 43, 50function blocks, 43, 51links, 43, 50

converted data, 23general, 25

converteroverview, 12starting, 12

converting a file in Unity Pro, 20converting procedure, 19converting process, 17

presentation, 17converting rules, 44

edge recognition, 46placing objects and links, 44recognizing transitions, 46transition-sensing, 46

79

Index

Ddata converted, 23data relation

ProWORX32, 38Unity Pro, 39

data relation and comment/symbol genera-tion, 37DFB

dummy, 52differences in the execution order, 55direct address

symbols instead of, 31dummy DFBs, 52

Eenhanced graphics

hidden option, 49equation networks

ProWORX32, 35error handling, 12, 21execution order, 53

differences, 55function blocks, 56, 57specific characteristics, 56

expanded memory register, 36export of a LL984 section out of Concept, 20

Fforced outputs (%M), 32forcing

transition-sensing contacts, 47function blocks

converted, 43, 51execution order, 56, 57not converted, 52

functional description, 9

Ggeneral

converted data, 25

80

graphics enhancedhidden option, 49

IIgnore jumps when splitting, 31include 984 execution corrections, 56, 58, 60installation, 13

Llaunch the converter, 17left power

unpowered LD objects linking, 45links

converted, 43, 50LL984

conversion wizard, 15LL984 section

export out of Concept, 20LL984 sections

constants, symbols, networks, seg-ments, comments, 30network dimensions, 34network structure, 29not converted objects, 36state RAM, 32

loadables, 36EXE, 36

Mmax. symbol length, 46Modsoft

configuration, 26constants, symbols, networks, seg-ments, comments, 30network dimensions, 34network structure, 29not converted objects, 36state RAM, 32

Modsoft SFC, 36multiple use of segments, 36

33003538 04/2009

Index

Nnetwork dimensions

IEC LD format, 34LL984 format, 34LL984 sections, 34Modsoft, 34ProWORX, 34

network paging, 31network structure

LL984 sections, 29Modsoft, 29presentation, 29ProWORX32, 29

Networks per Section1..10, 30

not convertedfunction blocks, 52

not converted objectsLL984 sections, 36Modsoft, 36ProWORX, 36

notationstate RAM, 32

Oorder

of execution, 53outputs (%M) forced, 32overview of the converter, 12

Ppaging between networks, 31paging between sections, 31placing objects and links

converting rules, 44presentation

network structure, 29presentation of the converting process, 17procedure of conversion, 19process of conversion, 17protect switch, 32

33003538 04/2009

ProWORXnetwork dimensions, 34not converted objects, 36

ProWORX32configuration, 26constants, symbols, networks, seg-ments, comments, 30data relation, 38equation networks, 35network structure, 29state RAM, 32

Rrange 6x, 36register in expanded memory, 36registration, 13rules for conversion, 44

Ssections paging, 31segment scheduler

multiple use, 36segments

multiple use, 36SFC

Modsoft, 36specific characteristics

execution order, 56starting the converter, 12state RAM

LL984 sections, 32Modsoft, 32notation, 32ProWORX32, 32

Suffixes, 51suppress graphs, 45suppress schedule, 44symbol and comment generation, 40symbol generation rule, 46symbol length, 46symbol/comment generation, 37symbols instead of direct address, 31

81

Index

Ttransition-sensing contacts

forcing, 47trouble shooting, 21

UUnity Pro

data relation, 39unpowered LD objects to left power, 45

82
33003538 04/2009