ACESYS UNITY Reference Manual v7.0.4

ACESYS UNITY - Introduction 1
ACESYS UNITY - Group 2

ACESYS UNITY - Route 3
ACESYS UNITY – Uni Motor 4
ACESYS UNITY – Bi Motor 5
ACESYS UNITY – Motor Gate 6
ACESYS UNITY – Positioner 7
ACESYS UNITY – Valve 8
ACESYS UNITY - Select 9
ACESYS UNITY - Alarm 10
ACESYS UNITY - Analog 11
ACESYS UNITY – PID Controller 12
13
ACESYS UNITY v7.0.4
ACESYS UNITY – PLC Communication 14
15
Volume 1/1 ACESYS UNITY – Extended Motor 16
ACESYS UNITY – Extended Gate 17
ACESYS UNITY – Extended Valve 18
19
20
21
22
23
24
25
26
FLSmidth Automation 27
Hoffdingsvej 34 28
DK-2500 Valby 29
Copenhagen 30
Denmark 31
32
33
34
35
36
37
Phone: +45 36 18 27 00 38
Telefax: +45 36 18 27 99 39
TAB
TAB
ACESYS program
Unity Reference Manual
Introduction
F.L.Smidth A/S - Automation
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:
Version AceV7.0.4 $Revision:: 0 $

Last modified $Modtime:: 01-09-05 12:00 $
Author Finn Kousgaard Poulsen
Last modified by $Author:: Fkp $
Name of Word File $Workfile:: Unity 01 Introduction.doc $
Index Range 0-1000
Disclaimer:
The information in this document is subject to change without notice and should not be construed, as a commitment
by F.L.Smidth A/S. F.L.Smidth assumes no responsibility for any errors that may appear in this document.
In no event shall F.L.Smidth be liable for direct, indirect, special, incidental or consequential damages of any
nature or kind arising from the use of this document, nor shall F.L.Smidth be liable for incidental or consequential
damages arising from use of any software or hardware described in this document.
Options specified and described in the F.L.Smidth documentation as part of the general description - but initially
neither ordered by the customer nor confirmed by the seller - will not commit the supplier to any further and future
supply and/or installation.
The software described in this document is furnished under a license and may be used, copied, or disclosed only in
accordance with the terms of such license.
Copyright © F.L.Smidth A/S.

All rights reserved.
Contents
Introduction (Unity) ..................................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
Hardware Requirements ....................................................................................................... 4
Software Requirements ........................................................................................................ 4
General Configuration ................................................................................................................. 5
Memory Allocation............................................................................................................... 5
General Elementary Variables.............................................................................................. 7
Watchdog .................................................................................................................................... 7
ECS_CMD.................................................................................................................................. 7
MSW_GROUPS ........................................................................................................................ 8
MSW_ROUTES......................................................................................................................... 8
MSW_UNITS............................................................................................................................. 9
MSW_SELECT.......................................................................................................................... 9
MSW_ALARMS....................................................................................................................... 10
ANALOG_ALARMS ............................................................................................................. 10
MSW_PID ................................................................................................................................ 11
ACESYS Installation................................................................................................................. 12
ACESYS Implementation ......................................................................................................... 15
Program Organizing ........................................................................................................... 15
Master Block ...................................................................................................................... 17
Watchdog .................................................................................................................................. 17
Scan Time ................................................................................................................................. 17
Enable Device Simulation....................................................................................................... 17
Master Link............................................................................................................................... 18
PLC Clock................................................................................................................................. 18
Department Block............................................................................................................... 19
Manipulating with Group/Route Command....................................................................... 20
ACESYS Library................................................................................................................ 21
Function Blocks ....................................................................................................................... 21
Data Types................................................................................................................................ 22
ECS Configuration .................................................................................................................... 23
Common Configuration...................................................................................................... 23
General Configuration ........................................................................................................ 24
Link Configuration ............................................................................................................. 26
Status.................................................................................................................................. 27
Department Configuration.................................................................................................. 28
PLC Configuration .................................................................................................................... 29
Project Settings................................................................................................................... 29
Connecting to the PLC ....................................................................................................... 30
Ethernet Configuration ....................................................................................................... 32
Memory Consumption........................................................................................................ 35
Device Simulation ..................................................................................................................... 36
Copyright © FLSmidth Automation. All rights reserved. Contents  i

Introduction (Unity)
General
Purpose
This manual contains a PLC specific description of ACESYS for the Schneider
Electric Unity controllers. This version of ACESYS for Unity is designed for the HMI
system ECS.
This manual has to be seen in consecutive with the generic ACESYS manual.
This manual will not cover information included in the Unity documentation from
Schneider Electric or ECS documentation. On the other hand some essential
information will be mentioned even they are part of the Unity/ECS documentation.
Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  3

Hardware Requirements
Developing, test and examples shown in this manual are based on the following
hardware components. Newer versions will probably be suitable, but are not tested:
140 CPU 651 60 Pentium controller
Software Requirements
The following software is used during developing and test of the ACESYS package for
Unity. Newer versions will probably be suitable, but are not tested:
Unity Pro XL V2.1.0
ECS Major Version 7.0.5
SdrModiconSvr30.exe Version 7.0.5.4
SdrModiconCfgUi30.exe Version 7.5.0.3
SdrModiconAcfgUi30.exe Version 7.5.0.3
4  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

General Configuration
Memory Allocation
The Unity PLC operates with two different types of memory:
Located Memory
Unlocated Memory
Variables of the located memory type are linked to a fixed memory address by the
PLC-programmer. Variables linked to an unlocated memory location are automatically
assigned to an internal address when the PLC program is compiled.
The size of the located memory is limited to 64.000 words. Since it is mandatory to use
located memory for data exchange with ECS it is necessary to manage the layout of
this memory area. In addition located memory has to be used for field I/O signals.
The following configuration of the Unity controller illustrates a suggested
configuration:
Figure 1 Unity Memory Configuration
The above configuration allocates the following addresses:
Digital Output (0x): %M1 – 2048

Digital Input (1x): %I1 – 2048
Analog Input (3x): %IW1 -512
Other purposes (3x): %IW513 - 1024
Analog Output (4x): %MW1 - 512
Other purposes (4x): %MW513 – 1994
ECS Data exchange (4x): %MW2000 – 63200

The data area allocated for data exchange with ECS is divided as shown below:
TYPE NO. OF SIZE IN NO. OF START END

UNITS WORDS WORDS ADDR ADDR
PLC set time 1 5 5 1995 1999
Watch Dog Address 1 1 1 2000 2000
ECS Commands 100 3 300 2001 2300
MSW Group 50 2 100 2301 2400
MSW Route 50 2 100 2401 2500
MSW Units 300 2 700 2501 3100
Spare 3101 3200
MSW Select 100 2 200 3201 3400
MSW Alarm 300 2 600 3401 4000
MSW Analog 300 4 1200 4001 5200
MSW PID 50 2 100 5201 5300
Interlock 400 0,0625 25 5301 5325
Indication 400 0,0625 25 5326 5350
Operator Set Point 100 2 200 5351 5550
Totalizer 100 2 200 5551 5750
PID SPA+SPM 50 4 200 5751 5950
Faceplate Group 50 15 750 5951 6700
Faceplate Route 50 10 500 6701 7200
Faceplate Select 100 5 500 7201 7700
Faceplate Alarm 300 15 4500 7701 12200
Faceplate Analog 300 60 18000 12201 30200
Faceplate PID 50 60 3000 30201 33200
Faceplate Units 300 100 30000 33201 63200
Figure 2 ACESYS Memory Layout
The above memory allocation can be changed but the following part of the
documentation will refer to this layout.

General Elementary Variables
A number of elementary variables have to be created for general use. Create the
following variables:
Figure 3 Elementary Variables
Watchdog
The purpose of this variable is to monitor the communication between the PLC and
ECS. For further information see “Master Block” on page 17 and “General
Configuration” on page 24.
ECS_CMD
The purpose of this array is to receive department commands from ECS. For
information about the PLC program for the department see “Department Block” on
page 19 and for the ECS configuration see “Department Configuration” on page 28.
The data array contains the information shown below:
Figure 4 Department Variables in PLC

MSW_GROUPS
This array contains the Machine Status Word (MSW) and timestamp for all group
objects for monitoring actual state on ECS. For further information about groups see
chapter “Group”.
Figure 5 Group MSW array
MSW_ROUTES
This array contains the Machine Status Word (MSW) and timestamp for all route
objects for monitoring actual state on ECS. For further information about routes see
chapter “Route”.
Figure 6 Route MSW array

MSW_UNITS
This array contains the Machine Status Word (MSW) and timestamp for all unit
objects (unimotor, bimotor, motorgate, valve, positioner, extended motor, extended
gate and extended valve) for monitoring actual state on ECS. For further information
about units see the appropriate chapter for the unit type.
Figure 7 Unit MSW array
MSW_SELECT
This array contains the Machine Status Word (MSW) and timestamp for all select
chapter “Select”.
Figure 8 Select MSW array

MSW_ALARMS
This array contains the Machine Status Word (MSW) and timestamp for all digital
alarm objects for monitoring actual state on ECS. For further information about routes
see chapter “Alarm”.
Figure 9 Alarm MSW array
ANALOG_ALARMS
This array contains the actual analog value, Machine Status Word (MSW) and
timestamp for all analog measuring objects for monitoring actual state on ECS. For
further information about routes see chapter “Alarm”.
Figure 10 Analog MSW array

MSW_PID
This array contains the Machine Status Word (MSW) and timestamp for all PID
chapter “PID”.
Figure 11 PID MSW array

ACESYS Installation
After installation of the CD “ACESYS V7.04 for Unity” two libraries have to be
installed. By default the ACESYS installation will copy files to “C:\ACESYS\v7.0.4”:
Figure 12 ACESYS Installation Destination
After installation of the ACESYS CD two folders containing libraries exist:
Libraries to
be installed
The “PLC Library” contains the ACESYS standard function block library and data
types, and the “SIM Library” contains functions for writing to physical input for
Device Simulation purpose.

Install the libraries using the program from the Unity software package “Types Library
Update”:
Figure 13 Unity Types Library Update
Please note that the “Unity Pro XL” software must not be started during the library
installation.
Browse to the PLC Library (default stored in “C:\ACESYS\v7.0.4\Unity\PLC
Library”) pick select the FAMILY.DSC and select open:
Figure 14 PLC Library Locations
Select Install Family:
Figure 15 PLC Library Installations

A successful installation will give the following message:
Figure 16 Installation Succeeded
Afterward browse to the SIM Library (default stored in

“C:\ACESYS\v7.0.4\Unity\SIM Library”) pick select the FAMILY.DSC and select
open:
Figure 17 SIM Library Locations
Install this library the same way as the PLC Library.
If the library to be installed already exists on the system a message similar to the
following message will be shown:
Figure 18 Library Update Message

ACESYS Implementation
The following section describes how the ACESYS standard has been implemented in
the Unity Controller, in respect to the controller functionality.
Program Organizing
The program structure can be displayed in Functional or Structural view
The structural view is shown below:
Figure 19 Structural View
The execution order of the program is equal to the section order in the structural view.
The functional view is shown below:
Figure 20 Functional View

Swapping between the two views is done by clicking the two icons shown below:
Right-clicking on a section allows linking to a functional section:
Figure 21 Linking Sections to Functional Module

Master Block
The first block to be inserted in the PLC-program is the Master Block:
To Department
FBs
The purpose of the master block is:

 Monitor the communication with ECS
 Launch Master Stop when communication with ECS fails
 Make flash slow/fast pulses
 Enable Device Simulation
 Show actual PLC scan time
 Adjust PLC clock from ECS
Watchdog
If the input “WatchDog_Enable” is set to high, the master block will monitor the
communication with ECS. If a high signal is not received on the in-/output
“WatchDog_ECS” within the time defined on the input “WatchDog_Time” a master
stop command will be launched. The master block will automatically clear the in-
/output “WatchDog_ECS” after receiving a high signal.
The remaining time before a master stop is launched can be monitored on the output
“WatchDog_Elap”.
See “General Elementary Variables” on page 7 for declaring of the variable
“WATCHDOG”.
Scan Time
The actual scan time for the PLC can be monitored on the output “ScanTime_ms” in
milliseconds.
Enable Device Simulation

The Device Simulation can be enabled for the PLC by setting the input
“SIM_Enabled” to high.

Master Link
The output “MASTER_Link” is of the type “ACESYS_MASTER_LINK” and has the
following structure:
Figure 22 Master Link Structure
This output is linked to all department objects.
PLC Clock
The in-/output “Time_Set” is used to adjust the PLC system date and time from ECS.
The actual time will be send from ECS in the format DT (Data & time). After the PLC
has adjusted the PLC clock the in-/output “Time_Set” will be reset to “DT#2000-01-
01-12:00:00”. Any new values will trig a new adjusting of the PLC system date and
time.

Department Block
For each department represented in the PLC a department object has to be assigned:
From Master FB
To Group FBs
See “General Elementary Variables“ on page 7 for declaring of the variable

“ECS_CMD[x]”.
The department FB will reset the commands launched from ECS after launching the
command on the output “DEPT_CMD”.

Manipulating with Group/Route Command
Normally the command from the parent object (group/route) is linked directly to the
unit:
Figure 23 Direct link of parent command
Some time it can be necessary to manipulate with this command for a single unit.
Since the CMD is a structure a new variable can be created of the type
“ACESYS_CMD”:
In the PLC-program the originally is copied to this new variable. Now it is possible to
make logic for each item in the structure, and link the new variable to the unit:
Figure 24 Manipulated Commands to Unit
In the above the Group Select command is not passed to the unit, but all other
commands are passed.

ACESYS Library
The ACESYS library contains a number of function blocks and data types.
Function Blocks
The following Derived FB Types are included in the ACESYS standard:
Figure 25 ACESYS FB Library

Data Types
The following Derived Data Types are included in the ACESYS standard:
Figure 26 ACESYS Data Types

ECS Configuration
The following sections describes configuration of the ECS system for proper
communication with the Unity. The examples will use the memory layout shown in
Figure 2 ACESYS Memory Layout page 6, and are based on Ethernet communication.
Parameters to pay special attention are marked with a circle.
Common Configuration
The Common configuration is valid for all PLCs configured. Two parameters have to
be configured different from the default value:
Max. Holding Register: 64000
Max Input Register: 64000
These figures have to match to the memory allocation shown Figure 2 ACESYS
Memory Layout page 6.
Furthermore server to synchronize system clocks in the PLCs has to be selected. The
possible options are No, From Server 1, From Server 2 or From Both:
Figure 27 Unity Server Common Configuration

General Configuration
In the following example a redundant Ethernet configuration is configured on a Unity
PLC.
The watchdog addresses and T.O.D. Register have to match to the memory allocation
shown Figure 2 ACESYS Memory Layout page 6. The watchdog period has to be
smaller than the time configured in the PLC-program for automatic execution of
master stop when communication timeout.
Figure 28 Unity Server General Configuration
Please note the length of the T.O.D. Register doesn’t matter when Unity PLC is
selected because the time and date is always send in the PLC format DT which
allocate 5 words.

The actual communication status can be monitored for the PLC and each network. For
this purpose create B-point tags using the algorithm 13 and the Interface type
Modicon.
Figure 29 Point Configuration Status Points
The addresses configuration for these status points using algorithm 13 has to be left
blank:
Figure 30 Address Configuration Status Points

Link Configuration
Each of the links has to be configured with the appropriate net address:
Figure 31 Unity Server Link Configurations

Status
For each of the configured link the status can be monitored:

Department Configuration
The department commands addresses have to match to the memory allocation shown
Figure 2 ACESYS Memory Layout page 6.
Figure 32 Department Configuration
In the above example department 1 is configured, using MW2001-2003.
Department commands: Department 1 MW2001-2003

Department 2 MW2004-2006
….
Department 100 MW2298-2300
The bit addresses are always as shown in the example.

PLC Configuration
The following sections describe basic configurations for settings up a Unity PLC-
project.
Project Settings
Select Tools  Project Settings in the menu:
Figure 33 Unity Project Settings
Set the parameter “Variables not used” in the Warning during analyses. This will
ensure that you get a warning if you have defined variables which are not used.
Select the parameter Include Upload Information. This makes it possible to make an
upload a complete PLC-program without having an offline program. It is
recommended to use the option to ensure the possibility to upload the complete
program, including variables adjusted from the faceplates. Using the option will
require more memory in the PLC

Connecting to the PLC
Configure the IP-address on the PLC by using the push buttons on the CPU.
To establish the communication to the PLC from the Unity Pro XL software package
select PLC  Select Address from the menu:
Figure 34 Unity Set Address
Select TCPIP and the correct IP-address.

Afterwards select PLC  Connect from the menu.
When the connection is established it is possible to transfer the project to the PLC:
Figure 35 Unity PLC menu
Transferring requires a stop of the PLC.

Another option is to compare the project with the PLC:
Figure 36 Unity PLC comparison
The project can be transferred to the PLC or the PLC can be transferred to the project.

Ethernet Configuration
In the communication create a net network by right-click at the Networks folder:
Figure 37 Unity Network definition
Select Ethernet and choose a proper name:
Figure 38 Unity Add Network

Afterwards double-click at the new created network to configure the network:
Figure 39 Unity Net Configurations
Enter the correct IP address and sub network mask.
The parameter Model Family is very important to configure correct.
If the connection is the on board port on the PLC it is has to be “TCP/IP 10/100
Extended connection”. A normal 140 NOE 771 01 Ethernet 10/100 module has to be
configured as a “TCP/IP 10/100 Regular connection”.
After the network has been configured the network has to be linked to the Ethernet
card or on-board Ethernet port on the CPU. Select the Ethernet port in the hardware
configuration:
Figure 40 Unity Select of Ethernet Port

Double-click at the Ethernet port and select the network:
Figure 41 Unity Assigning Network to Ethernet Port

Memory Consumption
The actual use of memory in the PLC can be monitored by selecting PLC  Memory
Consumption in the Menu.
The memory usage screen of a PLC with memory card and data storage is shown
below. If the PLC does not have a memory card, only the information relating to the
internal memory is displayed:
Figure 42 Unity Memory Consumptions
During program editing (online or offline) it is a good idea to bring this menu up from
time to time and press the push button “Pack”. This function will make a memory re-
organization.

Device Simulation
An optional package to the ACESYS standard library offers a set of function blocks
for simulation of I/O signal is supported.
Implementation of the individual simulation functions will be documented in the
following chapters for the specific functions.
The following characteristics are covered by the PLC I/O simulation:
 The simulation can be en/disabled by manipulating with an input on the
ACESYS_MASTER block (see Enable Device Simulation on page 17).
 By keeping the simulation for all units in one program it is easy to delete
the internal PLC I/O simulation.
 The simulation code is not infiltrated in the basic PLC-code, but kept in
separate function blocks.
It is recommended to gather the simulation code in one section:
Figure 43 Device Simulation Program Section
It the above example the device simulation is programmed in Structured Text (ST).

TAB
TAB
ACESYS program
Group
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 02 Group.doc $
Index Range 0-1000
Disclaimer:

Contents
Group (Unity)................................................................................................ 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
Main Program Structure .............................................................................................................. 4
PLC Program Group.................................................................................................................... 6
Variable Definitions ............................................................................................................. 6
PLC Program........................................................................................................................ 7
ECS Group Configuration ........................................................................................................... 8
Group B-point Algorithms ................................................................................................... 8
Group B-point Addresses ..................................................................................................... 9
Interlock B-point Algorithms ............................................................................................. 10
Interlock B-point Addresses ............................................................................................... 11
Info Faceplate ............................................................................................................................ 12

Group (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Group (Unity)  3

Main Program Structure
It is recommended to create one section for each group object in the Structural View:
Group
Section
Figure 1 Group Object- Structural View
Afterwards switch to the Functional View and create a Functional Module with the
same tag code:
Figure 2 Group Object - Functional View
Switch back to the Structural View and attached the section to the Functional Section:
4  Group (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Localization of Group Object
The created section will now appears in the Functional View:
Figure 4 Group Object Linked to Functional View

PLC Program Group
Variable Definitions
For each group object one tag of the type “ACESYS_Token” has to be created to
carry miscellaneous information to/from child objects:
Figure 5 Group Token Tag
As indicated above the variable contains actual output status for the group module,
and token information to/from child objects. Please that Address definition is not
required.
Furthermore one tag of the type “ACESYS_GROUP_FACEPLATE” has to be created

for each group object:
Figure 6 Group Faceplate Tag
This tag contains information to/from ECS. Address definition is required for data
exchange with ECS. For further information about address see chapter Introduction
section Memory Allocation.

PLC Program
Below is shown programming example for one group:
4 5
Figure 7 PLC Program Examples
The following steps have to be done after inserting of the ACESYS_GROUP function
block and basic input pins are linked:
1. Interlocking information is gathered. For appropriate memory addresses for
interlocking point for monitoring on ECS see chapter Introduction section
Memory Allocation.
2. Link the DEPT_CMD from the parent department object
3. Link the variable for faceplate parameters
4. Link the token variable
5. Link the Machine Status Word (MSW) variable. The index has to be unique
for each group function block. For declaration of the MSW array see chapter
“Introduction”.

ECS Group Configuration
Group B-point Algorithms

Create a B-point using the following Interface type, Conversion Algorithm and Block
algorithm:
Click at the icon to setup the Modicon Addresses.

Group B-point Addresses
The following snapshots illustrate the Modicon address configuration in ECS. The
addresses refer to the memory layout suggested in chapter Introduction section
Memory Allocation:
Unit = 1:
Register = 2299 + Unit * 2
Figure 8 Group Address Configuration Unit no. 1
Unit = 2:

Interlock B-point Algorithms
Create a B-point using the following Interface Type, Conversion Algorithm and Block
Algorithm:

Interlock B-point Addresses
Memory Allocation:
Unit = 1:
Unit 2:

Info Faceplate
The following faceplate can be called up from the group faceplate:
Figure 12 Group Info Faceplate
ACESYS Version and Build Number indicate the version of the PLC function block.
Program State expresses the current state of the function for debugging purposes.

TAB
TAB
ACESYS program
Route
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 03 Route.doc $
Index Range 0-1000
Disclaimer:

Contents
Route (Unity) ................................................................................................ 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Route..................................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Route Configuration............................................................................................................ 8
Route B-point Algorithms .................................................................................................... 8
Route B-point Addresses...................................................................................................... 9
Interlock B-point Algorithms ............................................................................................. 10
Interlock B-point Addresses ............................................................................................... 11
Info Faceplate ............................................................................................................................ 12

Route (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Route (Unity)  3

It is recommended to create one section for each Route object in the Structural View:
Route
Section
Figure 1 Route Object- Structural View
Afterwards switch to the Functional View and create a Functional Module with the
same tag code as a child to the parent group:
Figure 2 Route Object - Functional View
4  Route (Unity) Copyright © FLSmidth Automation. All rights reserved.

Switch back to the Structural View and attached the section to the Functional Section:
Figure 3 Localization of Route Object
Figure 4 Route Object Linked to Functional View

PLC Program Route
For each Route object one tag of the type “ACESYS_Token” has to be created to
carry miscellaneous information to/from child objects:
Figure 5 Route Token Tag
As indicated above the variable contains actual output status for the Route module,
and token information to/from child objects. Please that Address definition is not
required.
Furthermore one tag of the type “ACESYS_ROUTE_FACEPLATE” has to be created

for each Route object:
Figure 6 Route Faceplate Tag

PLC Program
Below is shown programming example for one Route:
6
4 5
The following steps have to be done after inserting of the ACESYS_ROUTE function
1. Interlocking information is gathered. For appropriate memory addresses for
interlocking point for monitoring on ECS see chapter Introduction section
Memory Allocation.
4. Link the token variable from the parent group object
5. Link the token for the route object
for each Route function block. For declaration of the MSW array see chapter
“Introduction”.

ECS Route Configuration
Route B-point Algorithms

algorithm:

Route B-point Addresses
Memory Allocation:
Unit = 1:
Figure 8 Route Address Configuration Unit no. 1
Unit = 2:

Interlock B-point Algorithms
Create a B-point using the following Interface Type, Conversion Algorithm and Block
Algorithm:

Interlock B-point Addresses
Memory Allocation:
Interlock Point 7:
Interlock Point 8:

Info Faceplate
The following faceplate can be called up from the Route faceplate:
Figure 12 Route Info Faceplate

TAB
TAB
ACESYS program
Unimotor
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 04 Unimotor.doc $
Index Range 0-1000
Disclaimer:

Contents
Unimotor (Unity) .......................................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Unimotor............................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Unimotor Configuration ...................................................................................................... 8
Unimotor B-point Algorithms .............................................................................................. 8
Unimotor B-point Addresses................................................................................................ 9
PLC-program Device Simulation ....................................................................................... 10
Info Faceplate ............................................................................................................................ 11

Unimotor (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Unimotor (Unity)  3

It is recommended to create one section for each Unimotor object in the Structural
View:
Unimotor
Section
Figure 1 Unimotor Object- Structural View
Afterwards attached the section to the Functional Section parent section (group or
route):
Figure 2 Localization of Unimotor Object
4  Unimotor (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Unimotor Object Linked to Functional View

PLC Program Unimotor
One tag of the type “ACESYS_UNIMOTOR_FACEPLATE” has to be created for
each Unimotor object:
Figure 4 Unimotor Faceplate Tag

PLC Program
Below is shown programming example for one Unimotor:
4
3
The following steps have to be done after inserting of the ACESYS_UNIMOTOR

function block and basic input pins are linked:
1. Link the parent object command (from group or route object)
3. Link the token variable from parent object (group or route)
for each unit function block

ECS Unimotor Configuration
Unimotor B-point Algorithms

algorithm:

Unimotor B-point Addresses
Memory Allocation:
Unit = 4:
Figure 6 Unimotor Address Configurations Unit no. 4
Unit = 5:
Figure 7 Unimotor Address Configurations unit no. 5

Device Simulation
for simulation of I/O signal.
For enabling of internal PLC I/O test see chapter 1 “Introduction”
PLC-program Device Simulation

In the following example simulation for one unimotor is shown, programmed in FDB:
1 3
4
5
2
Figure 8 Device Simulation Program FDB
1. Link to unit faceplate tag

2. Link to unit output command
3. Insert a ACESYS_SIM_I function for each signal to be simulated
4. Make connection between simulation block and ACESYS_SIM_I blocks
5. Define %I address to be simulated
The above example can also be programmed in ST (recommended), and will appear as
shown below:
Figure 9 Device Simulation Program ST

Info Faceplate
The following faceplate can be called up from the Unimotor faceplate:
Figure 10 Unimotor Info Faceplate

TAB
TAB
ACESYS program
Bimotor
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 05 Bimotor.doc $
Index Range 0-1000
Disclaimer:

Contents
Bimotor (Unity) ............................................................................................ 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Bimotor................................................................................................................. 6
PLC Program........................................................................................................................ 7
ECS Bimotor Configuration ........................................................................................................ 8
Bimotor B-point Algorithms ................................................................................................ 8
Bimotor B-point Addresses .................................................................................................. 9
Info Faceplate ............................................................................................................................ 11

Bimotor (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Bimotor (Unity)  3

It is recommended to create one section for each Bimotor object in the Structural View:
Bimotor
Section
Figure 1 Bimotor Object- Structural View
route):
Figure 2 Localization of Bimotor Object
4  Bimotor (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Bimotor Object Linked to Functional View

PLC Program Bimotor
One tag of the type “ACESYS_BIMOTOR_FACEPLATE” has to be created for each
Bimotor object:
Figure 4 Bimotor Faceplate Tag

PLC Program
Below is shown programming example for one Bimotor:
4
2
The following steps have to be done after inserting of the ACESYS_BIMOTOR


ECS Bimotor Configuration
Bimotor B-point Algorithms

algorithm:
Figure 6 B-point Configuration Bimotor

Bimotor B-point Addresses
Memory Allocation:
Unit = 1:
Figure 7 Bimotor Address Configurations Unit no. 1
Unit = 31:
Figure 8 Bimotor Address Configurations unit no. 31

Device Simulation

3
1
4
2 5

2. Link to unit output commands
shown below:

Info Faceplate
The following faceplate can be called up from the Bimotor faceplate:
Figure 11 Bimotor Info Faceplate

ACESYS program
Motorgate
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 06 Motorgate.doc $
Index Range 0-1000
Disclaimer:

Contents
Motorgate (Unity)......................................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Motorgate.............................................................................................................. 6
PLC Program........................................................................................................................ 7
ECS Motorgate Configuration..................................................................................................... 8
Motorgate B-point Algorithms ............................................................................................. 8
Motorgate B-point Addresses............................................................................................... 9
Info Faceplate ............................................................................................................................ 12

Motorgate (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Motorgate (Unity)  3

It is recommended to create one section for each Motorgate object in the Structural
View:
Motorgate
Section
Figure 1 Motorgate Object- Structural View
route):
Figure 2 Localization of Motorgate Object
4  Motorgate (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Motorgate Object Linked to Functional View

PLC Program Motorgate
One tag of the type “ACESYS_MOTORGATE_FACEPLATE” has to be created for
each Motorgate object:
Figure 4 Motorgate Faceplate Tag

PLC Program
Below is shown programming example for one Motorgate:
4
2
The following steps have to be done after inserting of the ACESYS_MOTORGATE


ECS Motorgate Configuration
Motorgate B-point Algorithms

algorithm:
Figure 6 B-point Configuration Motorgate

Motorgate B-point Addresses
Memory Allocation:
Unit = 2:
Figure 7 Motorgate Address Configurations unit no. 2
Unit = 45:
Figure 8 Motorgate Address Configurations unit no. 45

Device Simulation

3
1
4
2 5


shown below:

Info Faceplate
The following faceplate can be called up from the Motorgate faceplate:
Figure 11 Motorgate Info Faceplate

ACESYS program
Positioner
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 07 Positioner.doc $
Index Range 0-1000
Disclaimer:

Contents
Positioner (Unity)......................................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Positioner .............................................................................................................. 6
PLC Program........................................................................................................................ 7
ECS Positioner Configuration ..................................................................................................... 8
Positioner B-point Algorithms.............................................................................................. 8
Positioner B-point addresses ................................................................................................ 9
Info Faceplate ............................................................................................................................ 10

Positioner (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Positioner (Unity)  3

It is recommended to create one section for each Positioner object in the Structural
View:
Positioner
Section
Figure 1 Positioner Object- Structural View
route):
Figure 2 Localization of Positioner Object
4  Positioner (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Positioner Object Linked to Functional View

PLC Program Positioner
One tag of the type “ACESYS_POSITIONER_FACEPLATE” has to be created for
each Positioner object:
Figure 4 Positioner Faceplate Tag

PLC Program
Below is shown programming example for one Positioner:
The following steps have to be done after inserting of the ACESYS_POSITIONER


ECS Positioner Configuration
Positioner B-point Algorithms

algorithm:

Positioner B-point addresses
Memory Allocation:
Unit = 14:
Figure 6 Positioner Address Configuration unit no. 14
Unit = 47:
Figure 7 Positioner Address Configuration unit no. 47

Info Faceplate
The following faceplate can be called up from the Positioner faceplate:
Figure 8 Positioner Info Faceplate

ACESYS program
Valve
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 08 Valve.doc $
Index Range 0-1000
Disclaimer:

Contents
Valve (Unity)................................................................................................. 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Valve..................................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Valve Configuration............................................................................................................ 8
Valve B-point Algorithms .................................................................................................... 8
Valve B-point Addresses...................................................................................................... 9
Info Faceplate ............................................................................................................................ 10

Valve (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Valve (Unity)  3

It is recommended to create one section for each Valve object in the Structural View:
Valve
Section
Figure 1 Valve Object- Structural View
route):
Figure 2 Localization of Valve Object
4  Valve (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Valve Object Linked to Functional View

PLC Program Valve
One tag of the type “ACESYS_VALVE_FACEPLATE” has to be created for each
Valve object:
Figure 4 Valve Faceplate Tag

PLC Program
Below is shown programming example for one Valve:
4
2
The following steps have to be done after inserting of the ACESYS_VALVE function

ECS Valve Configuration
Valve B-point Algorithms

algorithm:

Valve B-point Addresses
Memory Allocation:
Unit = 9:
Figure 6 Valve Address Configuration unit no. 9
Unit = 51:
Figure 7 Valve Address Configuration unit no. 51

Info Faceplate
The following faceplate can be called up from the Valve faceplate:
Figure 8 Valve Info Faceplate

ACESYS program
Select
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 09 Select.doc $
Index Range 0-1000
Disclaimer:

Contents
Select (Unity)................................................................................................ 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Select .................................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Select Configuration............................................................................................................ 8
Select B-point Algorithms .................................................................................................... 8
Select B-point Addresses...................................................................................................... 9
Info Faceplate ............................................................................................................................ 10

Select (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Select (Unity)  3

It is recommended to create one section for each Select object in the Structural View:
Select
Section
Figure 1 Select Object- Structural View
route):
Figure 2 Localization of Select Object
4  Select (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Select Object Linked to Functional View

PLC Program Select
One tag of the type “ACESYS_SELECT_FACEPLATE” has to be created for each
Select object:
Figure 4 Select Faceplate Tag

PLC Program
Below is shown programming example for one Select:
3
1
The following steps have to be done after inserting of the ACESYS_SELECT function
for each select function block

ECS Select Configuration
Select B-point Algorithms

algorithm:

Select B-point Addresses
Memory Allocation:
Unit = 1:
Figure 6 Select Address Configuration Unit no. 1
Unit = 4:
Figure 7 Select Address Configuration Unit no. 4

Info Faceplate
The following faceplate can be called up from the Select faceplate:
Figure 8 Select Info Faceplate

ACESYS program
Alarm
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 10 Alarm.doc $
Index Range 0-1000
Disclaimer:

Contents
Alarm (Unity) ................................................................................................ 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Alarm.................................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Alarm Configuration ........................................................................................................... 8
Alarm B-point Algorithms ................................................................................................... 8
Alarm B-point Addresses ..................................................................................................... 9
Info Faceplate ............................................................................................................................ 10

Alarm (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Alarm (Unity)  3

It is recommended to create one section for each Alarm object in the Structural View:
Alarm
Section
Figure 1 Alarm Object- Structural View
route):
Figure 2 Localization of Alarm Object
4  Alarm (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Alarm Object Linked to Functional View

PLC Program Alarm
One tag of the type “ACESYS_ALARM_FACEPLATE” has to be created for each
Alarm object:
Figure 4 Alarm Faceplate Tag

PLC Program
Below is shown programming example for one Alarm:
3
1
The following steps have to be done after inserting of the ACESYS_ALARM function
for each Alarm function block

ECS Alarm Configuration
Alarm B-point Algorithms

algorithm:

Alarm B-point Addresses
Memory Allocation:
Unit = 1:
Figure 6 Alarm Address Configuration Unit no. 1
Unit = 6:
Figure 7 Alarm Address Configuration Unit no. 6

Info Faceplate
The following faceplate can be called up from the Alarm faceplate:
Figure 8 Alarm Info Faceplate

ACESYS program
Analog Measuring
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 11 Analog Measuring.doc $
Index Range 0-1000
Disclaimer:

Contents
Analog Measuring (Unity)........................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Analog Measuring ................................................................................................ 6
PLC Program........................................................................................................................ 7
ECS Analog Measuring Configuration........................................................................................ 8
Analog A-point Algorithms ................................................................................................. 8
Analog A-point Addresses ................................................................................................... 9
Info Faceplate ............................................................................................................................ 10

Analog Measuring (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Analog Measuring (Unity)  3

It is recommended to create one section for each Analog Measuring object in the
Structural View:
Analog
Section
Figure 1 Analog Object- Structural View
route):
Figure 2 Localization of Analog Object
4  Analog Measuring (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Analog Object Linked to Functional View

PLC Program Analog Measuring
One tag of the type “ACESYS_ANALOG_FACEPLATE” has to be created for each
Analog Measuring object:
Figure 4 Analog Faceplate Tag

PLC Program
Below is shown programming example for one Analog measuring unit:
1
2
3
7
5
4
The following steps have to be done after inserting of the ACESYS_ANALOG

2. Link the raw analog input in Real format to the input PIW for indication on
faceplate
3. Link the analog input normalized to 0.0-100.0 in real format to the input
PIW_NORM
4. Assign U_RANGE, O_RANGE and SIG_FAULT to healthy default values
(“1”) if no error check is possible. Another possibility is to link status from
I/O-card or insert compare instructions to trig fault states above/below a
certain analog value.
for each Analog function block

ECS Analog Measuring Configuration
Analog A-point Algorithms

Create an A-Point using the following Interface type, Conversion Algorithm and Block
algorithm:
Conversion Algorithm: 1 – Linear input

p= C1*aiv + C2
C1 = Gain
C2 = Offset
For further information about Reference points see the ECS document
“ApointAlgorithms30_English.doc”.

Analog A-point Addresses
Memory Allocation:
Unit = 1:
Figure 6 Analog Address Configuration Unit no. 1
Unit = 4:
Figure 7 Analog Address Configuration Unit no. 4

Info Faceplate
The following faceplate can be called up from the Analog faceplate:
Figure 8 Analog Info Faceplate

ACESYS program
PID Controller
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 12 PID.doc $
Index Range 0-1000
Disclaimer:

Contents
PID Controller (Unity).................................................................................. 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program PID Controller ...................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS PID Controller Configuration.............................................................................................. 8
PID Controller B-point: Mode.............................................................................................. 8
PID Controller B-point Addresses: Mode ............................................................................ 9
PID Controller A-point: SPA ............................................................................................... 9
PID Controller A-point Addresses: SPA............................................................................ 11
PID Controller A-point: SPM............................................................................................. 11
PID Controller A-point Addresses: SPM ........................................................................... 13
Info Faceplate ............................................................................................................................ 14

PID Controller (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. PID Controller (Unity)  3

It is recommended to create one section for each PID Controller object in the Structural
View:
PID Section
Figure 1 PID Object- Structural View
route):
Figure 2 Localization of PID Object
4  PID Controller (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 PID Object Linked to Functional View

PLC Program PID Controller
One tag of the type “ACESYS_PID_FACEPLATE” has to be created for each PID
Controller object:
Figure 4 PID Faceplate Tag
Furthermore two tags SPA (set point auto) and SPM (set point manual) has to be
created for each PID Controller object:
Figure 5 PID Set point Tags

PLC Program
Below is shown programming example for one PID Controller:
7
5
The following steps have to be done after inserting of the ACESYS_PID function
1. Link the set point auto tag
2. Link the set point manual tag
4. Link the process value to the input PV. The value has to be normalized to 0.0-
100.0 in real format. Link the analog signal status to the PV_OK input,
indication that the input signal is healthy (“1” = ok).
for each PID function block

ECS PID Controller Configuration
Normally three ECS points have to be configured for a PID Controller:

<Tagcode>_SPM Manual Set point
<Tagcode>_SPA Auto Set point
<Tagcode>_MODE PID mode
PID Controller B-point: Mode

Create a B-Point using the following Interface type, Conversion Algorithm and Block
algorithm:
Figure 7 B-point Configuration PID Mode
P1 = Process Value (PV) - controlled variable

P2 = Controller output Manual Setpoint (A-point with algorithm 4)
P4 = Controller Mode B-point. (B-point with appropriate algorithm, eg 33)

PID Controller B-point Addresses: Mode
Memory Allocation:
Unit = 1:
Figure 8 PID Mode Address Configurations Unit no. 1
Unit = 3:
Figure 9 PID Mode Address Configurations Unit no. 3
PID Controller A-point: SPA

algorithm:

Figure 10 Point configuration PID SPA

P2 = Controller output Manual Setpoint (A-point with algorithm 4)
P4 = Controller Mode B-point. (B-point with appropriate algorithm, eg 33)
P7 = Optional A-point that holds the actual position of the controlled device (damper
or valve).
C1 = Gain (Same as PV Gain)
C2 = Offset (Same as PV Offset)
C9 and C10 = Limits for setpoint output. C9 is the low limit and C10 the high limit.
So if C9 = 0 and C10 = 100 and an attempt is made to set the setpoint to 50 then this
will be accepted. However a value of 101 will be rejected. C9 and C10 are also used as
low and high range for PID faceplate sliders.

PID Controller A-point Addresses: SPA
Memory Allocation:
Unit = 1:
Figure 11 PID SPA Address Configurations Unit no. 1
Unit = 3:
Figure 12 PID SPA Address Configurations Unit no. 3
PID Controller A-point: SPM

algorithm:

Figure 13 Point configuration PID SPM
P1 = Automatic Setpoint (A-point with algorithm 3)

P4 = Controller Mode B-point (B-point with appropriate algorithm, eg 33)
C1 = Gain (Same as PV Gain)
C2 = Offset (Same as PV Offset)
C9 and C10 = Limits for output. C9 is the low limit and C10 the high limit. So if C9
= 0 and C10 = 100 and an attempt is made to set the setpoint to 50 then this will be
accepted. However a value of 101 will be rejected. C9 and C10 are also used as low
and high range for PID faceplate sliders.

PID Controller A-point Addresses: SPM
Memory Allocation:
Unit = 1:
Figure 14 PID SPM Address Configurations Unit no. 1
Unit = 3:
Figure 15 PID SPM Address Configurations Unit no. 3

Info Faceplate
The following faceplate can be called up from the PID faceplate:
Figure 16 PID Info Faceplate

ACESYS program
PLC Communication
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 14 PLC Communication.doc $
Index Range 0-1000
Disclaimer:

Contents
PLC Communication (Unity) ...................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
Communication principle ............................................................................................................ 4
Sending Data ........................................................................................................................ 4
Receiving Data ..................................................................................................................... 4
Hardware Configuration .............................................................................................................. 6
PLC Program............................................................................................................................... 8
Main Program Structure....................................................................................................... 8
PLC Program...................................................................................................................... 10
Sending Data ............................................................................................................................ 10
Receiving Data ......................................................................................................................... 11

PLC Communication (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. PLC Communication (Unity)  3

Communication principle
The ACESYS implementation of PLC to PLC communication is based on global data

configuration.
Global data service is a real time Publisher/Subscriber mechanism providing an
efficient data exchange for PLC application coordination.
Ethernet cards supporting Global Data are arranged in a distribution group for the
purpose of application variable exchange and synchronization.
The ACESYS implementation is prepared to handle redundant network. Therefore two
distribution groups are defined named Primary and Secondary. To ensure redundancy
the variables are broadcasted twice via both distribution groups.
Sending Data
The variables to be send are defined as Publish in the data editor.
Primary
Ethernet
PLCxx_Primary
Card
PLCxx_Data
Secondary
Ethernet
PLCxx_Secondary
Card
The variable PLCxx_Data are copied to PLCxx_Primary and PLCxx_Secondary. These

two variables are broadcasted to all nodes on the network via the distribution groups
defined on the networks.
Receiving Data
The variables to be received are defined as Subscribe in the data editor
Primary
Ethernet PLCxx_Primary
Card
PLCxx_Data
Secondary
Ethernet PLCxx_Secondary
Card
The variables PLCxx_Primary and PLCxx_Secondary are received via the networks.
When new data are received the data are copied to PLCxx_Data.
4  PLC Communication (Unity) Copyright © FLSmidth Automation. All rights reserved.

Using the global data exchange requires configuration in the network configuration as
well as the data editor.
In the following table planning of variables to the communicated are shown:
Variable Group Symbol PLC Number

ID Name
1 2 3 … 16
1 Primary PLC01_Primary PUB SUB SUB SUB

1 Secondary PLC01_Secondary PUB SUB SUB SUB
2 Primary PLC02_Primary SUB PUB SUB SUB
2 Secondary PLC02_Secondary SUB PUB SUB SUB
3 Primary PLC03_Primary SUB SUB PUB SUB
3 Secondary PLC04_Secondary SUB SUB PUB SUB
… …
16 Primary PLC16_Primary SUB SUB SUB PUB
16 Secondary PLC16_Secondary SUB SUB SUB PUB
Figure 1 Publish/Subscribe planning
The above table can be extended to handle up to 64 PLC nodes.

Hardware Configuration
The global data has to be configured on the network. Configure the primary and
secondary connections networks as shown below:
Figure 2 Global Data Primary Ethernet Card
Figure 3 Global Data Secondary Ethernet Card

Parameter Description
Health timeout After this time period has run out, the data
received becomes invalid. Set this value to
e.g. 10.000 ms. Supervision of receiving of
data is carried out by the ACESYS receive
block
Group address Class D Multicast IP address. All nodes in
the global data procedure use the same
Multicast address for distributing or
receiving data. The address range is:
224.0.0.0 to 239.255.255.255.
Distribution time Number of scan between publishing data.
Set the value to 1.
Group name Logical name. Defines the variable

allocation to different communication
configurations in the variable editor. Use
the names Primary and Secondary.
Status bit block Address for retrieving the status
information of the global data procedure.
Ensure that the variable is not used for
other purposes.
Multicast filtering Activates an Ethernet switch on
connection that supports Multicast
filtering.
Figure 4 Ethernet Card Parameters

PLC Program

It is recommended to create one section for each PLC Communication object in the
Structural View:
PLC
Communication
Section
Figure 5 PLC Communication Object- Structural View

Create three tags for each PLC in the network of the type
“ACESYS_PLCtoPLC_DATA”:
Figure 6 PLC Communication Tags
In the above variable definition window tags for 10 nodes are shown. The PLC to PLC
implementation can handle up to 64 nodes.
Note that the above shown variable definitions are for PLC no. 1 (the variable
PLC01_Primary and PLC01_Secondary are defined as PUB.
As indicated above the data type “ACESYS_PLCtoPLC_DATA” contains of the
following variables:
Figure 7 Data Type ACESYS_PLCtoPLC_Data
The variable Watchdog is used to monitor communication timeout. Every time a new
message is broadcasted a new value is written to the Watchdog variable. The receiving
PLC will check that the value has changed before elapse of watchdog time.
For data exchange arrays of 32 Boolean, 10 words, and 10 real are also transmitted are
defined.

PLC Program
Below is shown programming example for PLC Communication:
Sending Data
The following snapshot shows the ACESYS_PLC_SEND:
1 2 3
Figure 9 PLC Program Send Data
The following connections have to be made to the send block:

1. Working variable structure to be broadcasted
2. Variable structure to be broadcasted via primary network
3. Variable structure to be broadcasted via secondary network
Create logic to move internal variable to the data structure to be broadcasted:
Figure 10 Moving data to be Send

Receiving Data
The following snapshot shows the ACESYS_PLC_RECEIVE:
1 5
2 6
3
Figure 11 PLC Program Receive Data
The following connections have to be made to the receive block:

1. Define action to be carried out when watchdog time has elapsed. If the
Clear_Bool is set to true all Boolean variables in the received data structure
will be reset. The same functionality is implemented for Clear_Word and
Clear_Real, where word and real variables will be set to zero.
2. Watchdog time. When this time has elapsed without receiving new data the
data will reset in accordance to settings made
3. Variable structure received via primary network
4. Variable structure received via secondary network
5. The output status can be used to monitor the communication status, e.g. by
creating a digital alarm object to monitor the status.
6. Working variable
Create logic to move the received data to the internal variables:
Figure 12 Moving Received Data

ACESYS program
Extended Motor
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 16 Extended Motor.doc $
Index Range 0-1000
Disclaimer:

Contents
Extended Motor (Unity)............................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Extended Motor .................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Extended Motor Configuration............................................................................................ 9
Extended Unimotor B-point Algorithms .............................................................................. 9
Extended Bimotor B-point Algorithms............................................................................... 10
Extended Motor B-point Addresses.................................................................................... 11
Info Faceplate ............................................................................................................................ 14

Extended Motor (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Extended Motor (Unity)  3

It is recommended to create one section for each Extended Motor object in the
Structural View:
Extended
Motor
Section
Figure 1 Extended Motor Object- Structural View
4  Extended Motor (Unity) Copyright © FLSmidth Automation. All rights reserved.

route):
Figure 2 Localization of Extended Motor Object
Figure 3 Extended Motor Object Linked to Functional View

PLC Program Extended Motor
One tag of the type “ACESYS_EXTMOTOR_FACEPLATE” has to be created for
each Extended Motor object:
Figure 4 Extended Motor Faceplate Tag

PLC Program
Below is shown programming example for one Extended Motor:
4
2 3
The following steps have to be done after inserting of the ACESYS_EXTMOTOR

5. Insert the function block ACESYS_EXTMOTOR_PARMETER and link
input signals and link to input EXT_PARM on main block.
The use of the function block ACESYS_EXTMOTOR_PARM is implemented caused

to the limitation of maximum of 32 input pins on a function block in Unity. Therefore
it is not possible to add all signals from an intelligent device as single signals.

The output EXT_PARM on the ACESYS_EXTMOTOR_PARMETER function block
and the input EXT_PARM on the ACESYS_EXTMOTOR is a structure with the
following layout:
Figure 6 ACESYS_EXTMOTOR_PARAMETER Data Type

ECS Extended Motor Configuration
The extended motor can be used for unimotor and bimotors. The conversion algorithm
differs depending of the selected type, but the block algorithm is identical.
Extended Unimotor B-point Algorithms

algorithm:
Figure 7 Extended Unimotor Algorithms

Extended Bimotor B-point Algorithms
algorithm:
Figure 8 Extended Bimotor Algorithms

Extended Motor B-point Addresses
Memory Allocation:
Unit = 19:
Figure 9 Extended Motor Address Configuration Unit 19
Unit = 21:
Figure 10 Extended Motor Address Configuration Unit 21

Device Simulation

In the following example simulation for one extended unimotor is shown, programmed
in FDB:
1 3
4
5
2
Figure 11 Device Simulation Program FDB Unimotor

2. Link to unit output command (For a extended unimotor only one command
will exist)

The PLC program simulating an extended bimotor can appears as the following
example:
The above examples can also be programmed in ST (recommended), and will appear
as shown below. The following example shows simulation of a unimotor:
Figure 12Device Simulation Program ST Unimotor
Below an example of simulating a bimotor is shown:
Figure 13 Device Simulation Program ST Bimotor

Info Faceplate
The following faceplate can be called up from the Extended Motor faceplate:
Figure 14 Extended Motor Info Faceplate

ACESYS program
Extended Gate
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 17 Extended Gate.doc $
Index Range 0-1000
Disclaimer:

Contents
Extended Gate (Unity)................................................................................. 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Extended Gate....................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Extended Gate Configuration .............................................................................................. 9
Extended Motorgate B-point Algorithms ............................................................................. 9
Extended Positioner B-point Algorithms............................................................................ 10
Extended Gate B-point Addresses ...................................................................................... 11
Info Faceplate ............................................................................................................................ 14

Extended Gate (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Extended Gate (Unity)  3

It is recommended to create one section for each Extended Gate object in the Structural
View:
Extended
Gate
Section
Figure 1 Extended Gate Object- Structural View
route):
Figure 2 Localization of Extended Gate Object
4  Extended Gate (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Extended Gate Object Linked to Functional View

PLC Program Extended Gate
One tag of the type “ACESYS_EXTGATE_FACEPLATE” has to be created for each
Extended Gate object:
Figure 4 Extended Gate Faceplate Tag

PLC Program
Below is shown programming example for one Extended Gate:
4
2 3
The following steps have to be done after inserting of the ACESYS_EXTGATE

5. Insert the function block ACESYS_EXTGATE_PARMETER and link input
signals and link to input EXT_PARM on main block.
The use of the function block ACESYS_EXTGATE_PARM is implemented caused to

the limitation of maximum of 32 input pins on a function block in Unity. Therefore it
is not possible to add all signals from an intelligent device as single signals.

The output EXT_PARM on the ACESYS_EXTGATE_PARMETER function block
and the input EXT_PARM on the ACESYS_EXTGATE is a structure with the
following layout:
Figure 6 ACESYS_EXTGATE_PARAMETER Data Type

ECS Extended Gate Configuration
The extended Gate can be used for Motorgate and Positioner. The conversion
algorithm differs depending of the selected type, but the block algorithm is identical.
Extended Motorgate B-point Algorithms

algorithm:
Figure 7 Extended Motorgate Algorithms
Two conversion algorithms can be used depending of the wanted status text:
Algorithm 84: Pos 1/Pos 2
Algorithm 85: Open/Closed

Extended Positioner B-point Algorithms
algorithm:
Figure 8 Extended Positioner Algorithms

Extended Gate B-point Addresses
Memory Allocation:
Unit = 27:
Figure 9 Extended Gate Address Configuration Unit no. 27
Unit = 29:
Figure 10 Extended Gate Address Configuration Unit no. 29

Device Simulation

In the following example simulation for one extended Motorgate is shown,
programmed in FDB:
3
1
4
5
2
Figure 11 Device Simulation Program FDB Motorgate


The PLC program simulating an extended Positioner can appears as the following
example:
as shown below. The following example shows simulation of a Motorgate:
Figure 12Device Simulation Program ST Motorgate
Below an example of simulating a Positioner is shown:
Figure 13 Device Simulation Program ST Positioner

Info Faceplate
The following faceplate can be called up from the Extended Gate faceplate:
Figure 14 Extended Gate Info Faceplate

ACESYS program
Extended Valve
Høffdingsvej 34
DK-2500 Valby
Copenhagen
Denmark
+45 36 18 27 00
Fax: +45 36 18 27 99
Printing History:

Name of Word File $Workfile:: Unity 18 Extended Valve.doc $
Index Range 0-1000
Disclaimer:

Contents
Extended Valve (Unity) ............................................................................... 3
General ........................................................................................................................................ 3
Purpose................................................................................................................................. 3
PLC Program Extended Valve..................................................................................................... 6
PLC Program........................................................................................................................ 7
ECS Extended Valve Configuration ............................................................................................ 9
Extended Valve 2 positions B-point Algorithms .................................................................. 9
Extended Valve 3 positions B-point Algorithms ................................................................ 10
Extended Valve B-point Addresses .................................................................................... 11
Info Faceplate ............................................................................................................................ 14

Extended Valve (Unity)
General
Purpose
system ECS.
Copyright © FLSmidth Automation. All rights reserved. Extended Valve (Unity)  3

It is recommended to create one section for each Extended Valve object in the
Structural View:
Extended
Valve
Section
Figure 1 Extended Valve Object- Structural View
route):
Figure 2 Localization of Extended Valve Object
4  Extended Valve (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Extended Valve Object Linked to Functional View

PLC Program Extended Valve
One tag of the type “ACESYS_EXTVALVE_FACEPLATE” has to be created for
each Extended Valve object:
Figure 4 Extended Valve Faceplate Tag

PLC Program
Below is shown programming example for one Extended Valve:
4
2 3
Figure 5 PLC Program Example
The following steps have to be done after inserting of the ACESYS_EXTVALVE

5. Insert the function block ACESYS_EXTVALVE_PARMETER and link
input signals and link to input EXT_PARM on main block.
The use of the function block ACESYS_EXTVALVE_PARM is implemented caused

to the limitation of maximum of 32 input pins on a function block in Unity. Therefore
it is not possible to add all signals from an intelligent device as single signals.

The output EXT_PARM on the ACESYS_EXTVALVE_PARMETER function block
and the input EXT_PARM on the ACESYS_EXTVALVE is a structure with the
following layout:
Figure 6 ACESYS_EXTVALVE_PARAMETER Data Type

ECS Extended Valve Configuration
The extended Valve can be used for Valve 2 positions and Valve 3 positions. The
conversion algorithm differs depending of the selected type, but the block algorithm is
identical.
Extended Valve 2 positions B-point Algorithms

algorithm:
Figure 7 Extended Valve 2 positions Algorithms

Extended Valve 3 positions B-point Algorithms
algorithm:
Figure 8 Extended Valve 3 positions Algorithms
Algorithm 92: Pos 1/Pos 2/Pos 3
Algorithm 95: Open/Closed/10%

Extended Valve B-point Addresses
Memory Allocation:
Unit = 23:
Figure 9 Extended Valve Address Configuration Unit 23
Unit = 25:
Figure 10 Extended Valve Address Configuration Unit 25

Device Simulation

In the following example simulation for one extended Valve 2 positions is shown,
programmed in FDB:
3
1
4
5
2
Figure 11 Device Simulation Program FDB Valve 2 positions


The PLC program simulating a extended Valve 3 positions can appears as the
following example:
as shown below. The following example shows simulation of a Valve 2 positions:
Figure 12 Device Simulation Program ST Valve 2 positions
Below is a example of simulating a Valve 3 positions shown.
Figure 13 Device Simulation Program ST Valve 3 positions

Info Faceplate
The following faceplate can be called up from the Extended Valve faceplate:
Figure 14 Extended Valve Info Faceplate

ACESYS UNITY Reference Manual v7.0.4

Uploaded by

Copyright:

Available Formats

You might also like

ACESYS UNITY Reference Manual v7.0.4

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ACESYS UNITY Reference Manual v7.0.4

Uploaded by

Copyright:

Available Formats

ACESYS UNITY - Introduction 1

ACESYS UNITY - Group 2

Unity Reference Manual

Version AceV7.0.4 $Revision:: 0 $

Copyright © F.L.Smidth A/S.

Copyright © FLSmidth Automation. All rights reserved. Contents  i

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  3

4  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 1 Unity Memory Configuration

The above configuration allocates the following addresses:

Digital Output (0x): %M1 – 2048

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  5

TYPE NO. OF SIZE IN NO. OF START END

6  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 3 Elementary Variables

Figure 4 Department Variables in PLC

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  7

Figure 5 Group MSW array

Figure 6 Route MSW array

8  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 7 Unit MSW array

Figure 8 Select MSW array

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  9

Figure 9 Alarm MSW array

Figure 10 Analog MSW array

10  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 11 PID MSW array

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  11

Figure 12 ACESYS Installation Destination

After installation of the ACESYS CD two folders containing libraries exist:

12  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 13 Unity Types Library Update

Figure 14 PLC Library Locations

Select Install Family:

Figure 15 PLC Library Installations

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  13

Figure 16 Installation Succeeded

Afterward browse to the SIM Library (default stored in

Figure 17 SIM Library Locations

Install this library the same way as the PLC Library.

Figure 18 Library Update Message

14  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

Figure 19 Structural View

The functional view is shown below:

Figure 20 Functional View

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  15

Right-clicking on a section allows linking to a functional section:

Figure 21 Linking Sections to Functional Module

16  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

The purpose of the master block is:

Enable Device Simulation

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  17

Figure 22 Master Link Structure

This output is linked to all department objects.

18  Introduction (Unity) Copyright © FLSmidth Automation. All rights reserved.

See “General Elementary Variables“ on page 7 for declaring of the variable

Copyright © FLSmidth Automation. All rights reserved. Introduction (Unity)  19

Figure 23 Direct link of parent command

Figure 24 Manipulated Commands to Unit