Maestro

Freelance 2000
Coupling Freelance 2000 - Maestro UX
Version 4/5
Notice
Information provided in this manual is subject to change without prior notice and
represents no obligation on the part of ABB Automation Products.
The industrial standards and regulations (e.g. DIN, VDE, VDI, etc.) applicable in the
Federal Republic of Germany are used. Outside the Federal Republic of Germany, the
relevant national specifications, standards and regulations must be observed.
ABB Automation Products reserves all rights, especially those arising out of BGB, UWG,
UrhG as well as out of industrial property rights (patents, utility models, trademarks,
service trademarks and flavour samples).
The designations used and the products shown/mentioned in this manual have not been
specifically marked regarding existing industrial property rights.
No part of this manual may be reproduced without prior written permission from ABB
Automation Products.
Should you find any mistakes in this manual, please make a copy of the appropriate
page(s) and send it/them to us with your comments. Any suggestions which may help to
improve comprehension or clarity will also be gratefully accepted.
Please send your suggestions to:
Product Management Dept., DEAPR/LMS-Hannover, Fax: +49 (0)511 6782 701

Contents
1 Coupling Freelance 2000 - Maestro UX.................................................................. 7

1.1 Hardware.................................................................................................................... 7
1.1.1 Structure of a network with DCP 02 as the gateway.................................................. 8
1.1.2 Structure of a network with DCP 10 as the gateway.................................................. 9
1.1.3 Structure of a network with two DCP 10 as the redundant gateway........................ 10
1.1.4 Hardware versions ................................................................................................... 12
1.2 Installing the Ethernet connections .......................................................................... 12
1.2.1 Installing the CPU module address via the encoder ................................................ 13
1.2.2 Free configuration of Ethernet interfaces ................................................................. 14
1.2.3 DCP 10 gateway with DigiNet S and O net not separated....................................... 15
1.2.4 DCP 10 gateway with DigiNet S and O net separated............................................. 16
1.2.5 Redundant DCP 10 gateway with DigiNet S and O net not separated.................... 17
1.2.6 Redundant DCP 10 gateway with DigiNet S and O net separated .......................... 19
1.3 Data throughput........................................................................................................ 20
1.3.1 Reading values ........................................................................................................ 20
1.3.2 Writing values........................................................................................................... 22
1.3.3 Messages to Maestro UX......................................................................................... 22
1.4 Software packages................................................................................................... 22
1.5 Configuration ............................................................................................................ 23
1.5.1 Creating the gateway station in the project tree....................................................... 23
1.5.2 Configuration of a gateway station........................................................................... 24
1.5.3 Gateway station in the hardware structure .............................................................. 27
1.5.4 Configuration of the process stations....................................................................... 28
1.5.5 Names of tags and variables.................................................................................... 29
1.5.6 Specification of the data available via the gateway ................................................. 30
1.5.7 Commissioning......................................................................................................... 32
1.5.8 Preparing project data for transfer to an external system ........................................ 33
1.5.9 Transfer of the PLCOpen file to the Maestro UX system......................................... 33
1.5.10 Conversion of the PLCOpen file into Maestro UX data............................................ 33
1.5.10.1 Project data of the DigiVis station ............................................................................ 34
1.5.10.2 Conversion of texts by the converter........................................................................ 35
1.5.11 Display of Freelance 2000 data on Maestro UX ...................................................... 35
1.5.12 Reconfiguration of data relevant to Maestro UX ...................................................... 36
1.5.13 Loading to the gateway from Maestro UX................................................................ 37
1.5.14 Time synchronization ............................................................................................... 37
1.5.15 Subsequent project changes.................................................................................... 38
1.6 Application redundancy ............................................................................................ 39
2 Display of Freelance 2000 data on Maestro UX................................................... 40

2.1 Mapping of Freelance 2000 function blocks and variables on Maestro UX ............. 40
2.2 Faceplates on Maestro UX and DigiVis ................................................................... 40
2.2.1 Fundamental differences.......................................................................................... 40
2.2.1.1 Size of the faceplates............................................................................................... 40
2.2.1.2 Display of messages in the faceplate ...................................................................... 40
2.2.1.3 Layout of the faceplates ........................................................................................... 41
3
2.2.1.4 Operator panel ......................................................................................................... 41

2.2.1.5 Operation ................................................................................................................. 41
2.2.2 Class-specific differences ........................................................................................ 41
2.2.2.1 String data type........................................................................................................ 41
2.2.2.2 Date&Time data type ............................................................................................... 41
2.2.2.3 PackedBool data type (BYTE, WORD, DWORD).................................................... 41
2.2.2.4 Structured Data Types ............................................................................................. 42
2.2.2.5 Global variables ....................................................................................................... 42
2.2.2.6 Signals of I/O modules............................................................................................. 43
2.2.2.7 BYTE, WORD, DWORD / CSDPB constant function blocks ................................... 43
2.2.2.8 DINT / CSDINT constant function block .................................................................. 43
2.2.2.9 Communication function blocks ............................................................................... 43
2.3 Sequential function chart (SFC)............................................................................... 43
2.3.1 Steps of an SFC....................................................................................................... 43
2.3.2 Tip mode .................................................................................................................. 44
2.3.3 Action windows ........................................................................................................ 44
2.3.4 Transitions ............................................................................................................... 44
2.4 Graphic displays ...................................................................................................... 45
2.5 Group displays ......................................................................................................... 45
2.6 Overview display...................................................................................................... 45
2.7 Messages................................................................................................................. 45
2.7.1 Display of priorities .................................................................................................. 45
2.7.2 Filtering messages without configuration information.............................................. 46
2.7.3 Substitute names for messages .............................................................................. 47
2.7.4 Messages in connection with Maestro UX application redundancy......................... 47
2.7.5 Display of messages................................................................................................ 47
2.7.6 Acknowledgement of messages .............................................................................. 47
2.7.7 Hints......................................................................................................................... 48
2.8 Archiving .................................................................................................................. 48
2.9 DigiBatch.................................................................................................................. 48
2.10 User-defined function blocks.................................................................................... 48
2.11 Horn function............................................................................................................ 49
3 Time synchronization ............................................................................................ 50

3.1 Time synchronization within a Freelance 2000 system ........................................... 50
3.2 Time synchronization of several Maestro UX .......................................................... 50
3.3 Time synchronization via a gateway ........................................................................ 50
3.4 System time, local time, summertime ...................................................................... 51
3.5 Time synchronization with DCP 02 gateway ........................................................... 51
3.5.1 Maestro UX workstation (WS), 1 Freelance 2000 system....................................... 52
3.5.2 Application redundancy ........................................................................................... 53
3.5.3 Maestro UX, 2 Freelance 2000 systems.................................................................. 54
3.5.4 Maestro UX, 1 Freelance 2000 system and CSC.................................................... 55
3.6 Time synchronization with DCP 10 gateway ........................................................... 56
3.6.1 Maestro workstation (WS), one Freelance 2000 system......................................... 56
3.6.2 Application redundancy ........................................................................................... 57
3.6.3 Maestro UX workstation (WS), two Freelance 2000 systems ................................. 58
4
3.6.4 Maestro UX workstation (WS), one Freelance 2000 system and CSC ................... 59
3.7 Commissioning the time synchronization................................................................. 60
4 Redundancy behavior of the gateway.................................................................. 61

4.1 Redundancy toggle, error detection ......................................................................... 61
4.2 Redundancy state .................................................................................................... 62
4.3 System messages from the gateway to Maestro UX ............................................... 64
5 Appendix: Mapping of Freelance 2000 function block classes ......................... 68
6 Appendix: Examples for project changes ........................................................... 70

6.1 Add or delete a tag or a variable .............................................................................. 70
6.2 Reconfiguration of a tag ........................................................................................... 71
6.3 Changing gateway data............................................................................................ 73
5
1 Coupling Freelance 2000 - Maestro UX
In addition to the DigiVis software package, a Maestro UX system can also be used to operate
and observe a Freelance 2000 system. The Freelance 2000 system is linked to Maestro UX
with a gateway station. The data which are to be available on Maestro UX are specified in the
project configuration on DigiTool. The appropriate parts of the project are transferred from
DigiTool to Maestro UX.
1.1 Hardware
To link Freelance 2000 to a Maestro UX system, an additional CPU module is to be inserted as

a gateway in any free slot in an existing rack. Both DCP 02 and DCP 10 can be used as the
gateway.
Use two CPU modules type DCP 10 to implement a redundant gateway. The two CPU modules
need not be placed side by side in one rack, they can be inserted in any rack.
Whether a CPU module is used as a process station or a gateway station is not specified until
the corresponding operating system is loaded during commissioning. A boot EPROM download
must first be carried out for all CPU modules, both for the process stations and for the gateway
stations, during setup procedure or using the DigiTool Configure tool.
For better clarity, in each of the following examples only one process station, one Maestro UX
workstation and one DigiVis station will be illustrated. The process station is shown with one
CPU; it may, however, have two CPU modules as a redundant station. Also the Maestro UX
workstation can be realized redundant.
The IP addresses indicated are not fixed default values; they are intended only to clarify the
system.
7
1.1.1 Structure of a network with DCP 02 as the gateway

This CPU module has one Ethernet connection; all system stations are linked in the same net-
work. For implementation, this means that the base IP addresses and the subnet masks of all
stations must be identical (e.g.: IP address = 172.16.x.y (with x=0..15 and y=0..255) and subnet
mask = 255.255.255.0).
gw_1net.bmp
All data traffic, in both the Freelance 2000 and the Maestro UX system, takes place in this net-
work. Load separation must be implemented with a bridge.
8
1.1.2 Structure of a network with DCP 10 as the gateway

This CPU module has two Ethernet connections; it is still possible to network the stations as
with the use of DCP 02 - all stations in one network. In this case, one Ethernet connection of
the module is not used or is just fitted with terminating resistors.
DigiNet S and O net are separated into two networks. To separate DigiNet S and O net into two
networks, both Ethernet connections are used and configured with different IP addresses. In
addition to its original functional capabilities, the gateway assumes certain tasks of a router.
Complex networks should always be implemented with ‘real’ routers.
gw_2net.bmp
In this network, all the data traffic in the Freelance 2000 system runs completely in DigiNet S,
separated from the O net of the Maestro UX system. The gateway is addressed via the first
Ethernet connection by DigiTool to load the configuration and via the second connection by
Maestro UX to read and write the Freelance 2000 data.
9
1.1.3 Structure of a network with two DCP 10 as the redundant gateway

Using two DCP 10 modules, the gateway can be structured as a redundant gateway. Analogue
to the non redundant gateway, either all stations can be operated in one network or the two
networks are separated.
The two CPU modules need not be placed side by side in one rack, they may be inserted in
any free slot in the Freelance 2000 rack. It is also possible to insert them in racks of another
Freelance 2000 system, the sole condition being that DigiTool can reach both gateway partners
via the Ethernet.
Both network connections are supervised cyclically; data adjustment of both redundancy part-
ners is carried out via the first Ethernet connections, i.e. the DigiNet S.
The connections between the two redundant CPU modules must be realized directly. It is not
allowed to install a router within the redundancy link.
a) Redundant gateway with DigiNet S and O net not separated
gwr_1net.bmp
Always the first Ethernet connection is linked with DigiNet S. Analogue to a redundant process
station, the second Ethernet connections are linked separately.
10
b) Redundant gateway with DigiNet S and O net separated
gwr_2net.bmp
The first Ethernet connection is linked with DigiNet S, the second with the O net. Both networks
are supervised cyclically.
11
1.1.4 Hardware versions

A gateway CPU module can be inserted in a module rack or removed during current operation
of a process station. It is therefore possible to link a Freelance 2000 system during current op-
eration to Maestro UX.
With an older hardware version inserting of a gateway CPU in a module rack may trigger a pro-
cess station warm start. The reason for this is a problem with the battery voltage of the mod-
ules. This problem has been eliminated for DCP 02 as from version with hardware index
12.3, for DCP 10 as from hardware index 1.0, for DCO 01 as from index 2.02.
A gateway CPU module can be inserted without any problems in a module rack, if all
DCP 02, DCP 10 and DCO 01 modules in this rack at least feature one of the hardware
indices indicated above.
1.2 Installing the Ethernet connections
As described in the Mounting and Installation Manual, the IP addresses and subnet masks of a
CPU module can be set either with the hardware or with the software. IP addresses 172.16.1.x
with x = 1...15 and subnet mask 255.255.240.0 can be set with the coding switch on the CPU
module, all other addresses are assigned via the diagnostic interface.
When setting the coding switch to a fixed value (unequal 0), the second Ethernet interface of a
DCP 10 module is configured as a redundancy link to Cheapernet.
These standard addresses cannot be used for Maestro UX workstations with version 2.
The operating system HP-UX 10.2 used for Maestro UX does not allow this combination
of IP address and subnet mask.
The configuration of the gateway Ethernet connections have to be carried out via the diagnos-
tic interface in the system menu. The remaining system parameters which do not concern the
Ethernet interfaces are not dealed with; for their installation, see the Mounting and Installa-
tion Manual.
Access to the system menu is obtained if the Run/Stop switch of the module is set to Stop dur-
ing booting.
12
1.2.1 Installing the CPU module address via the encoder

The system menu of the boot loader first displays the up - to - date configuration of the CPU
module.
sysmen01.bmp
The IP address is defined by the coding switch, the second Ethernet connection is preset as a
redundancy link, implemented with Cheapernet.
Select <C>hange to change the displayed parameters. In this case, only the type of connection
of the first Ethernet interface can be modified.
sysmen02.bmp
13
1.2.2 Free configuration of Ethernet interfaces

When setting the encoder to the value 0, both Ethernet interfaces are freely configurable using
the system menu. At first, the up to date configuration is displayed:
sysmen03.bmp
In the submenu <C>hange the system parameters can be modified. The entries required de-
pend upon the structure of the networks:
14
1.2.3 DCP 10 gateway with DigiNet S and O net not separated

The type of connection, the IP address, the subnet mask and the network type can be entered
for the first interface. The second Ethernet interface is not used, therefore enter <0> for Dis-
abled.
sysmen05.bmp
15
1.2.4 DCP 10 gateway with DigiNet S and O net separated

The first Ethernet interface is linked to DigiNet S, the second to the O net; enter <2> to config-
ure the second interface as Gateway.
As in the above given example, at first the type of connection, the IP address, the subnet mask
and the network type to be changed are displayed for the first interface. Then the correspond-
ing entries for the second Ethernet interface are required - enter the IP address and the subnet
mask for the O net.
sysmen06.bmp
It is not necessary to enter a default router in the gateway; default router configuration =
0.0.0.0.
For a FTP export, a link from DigiTool-PC to the Maestro UX-Workstation must be installed;
therefore, the gateway is entered as router for both computers.
16
DigiTool-PC
Select the network protocol TCP/IP protocol in Control panel / Network / Protocols. Enter the IP
address of the gateway station in DigiNet S in dialog Properties in the field Default gateway.
Maestro UX-Workstation
In an Unix environment, change the directory /etc and enter:
route add <ip-adr1> <ip-adr2> 1
with <ip-adr1> = IP address of the tool-PC in DigiNet S and
<ip-adr2> = IP address of the gateway in the O net
This command is necessary after each reboot of the workstation.
1.2.5 Redundant DCP 10 gateway with DigiNet S and O net not separated
The second Ethernet interface is used as redundancy link, therefore enter <1> to configure the
second interface as RedLink.
As in the above given example, at first the type of connection, the IP address, the subnet mask
and the network type to be changed are displayed for the first interface.
For the second Ethernet connection, only the type of connection - AUI or Cheapernet - need to
be configured; the IP address and the subnet mask are not required in this case and are not
offered.
17
sysmen07.bmp
Carry out these settings for both redundancy partners.
For communication via the redundancy link, IP addresses are composed using the numbers of
the module rack and the slot. In other words, two modules in different process stations in iden-
tical slots (e.g. the 5th slot of the 3rd I/O unit) are allocated the same IP address. Two network
stations with identical addresses may not be operated in one network. For such a structure, the
redundancy link needs to be configured as individual network, see Section 1.2.6, redundant
DCP 10 gateway with DigiNet S and O net separated.
This redundancy network has to be configured as an individual network separated from
DigiNet S.
If the two gateway redundancy partners are located in different process stations in iden-
tical slots, the redundancy link needs to be configured as an individual network and not
as a redundancy link.
18
1.2.6 Redundant DCP 10 gateway with DigiNet S and O net separated

The 2nd Ethernet interface is linked to the O net, enter <2> for Gateway.
The connected networks are used for the redundancy link, configuration as RedLink is not pos-
sible in this case.
The first interface is always connected to DigiNet S, the second to the O net. For both inter-
faces, the type of connection, the IP address, the subnet mask and the network type need to be
determined.
sysmen08.bmp
It is not necessary to define a default router in the gateway;

default router configuration = 0.0.0.0.
For a FTP export there must be a link from DigiTool-PC to the Maestro UX-Workstation; there-
fore, the gateway is entered as router on both computers.
19
DigiTool-PC
Select the network protocol TCP/IP protocol in Control panel / Network / Protocols. Enter the IP
address of the gateway station in DigiNet S in dialog Properties in the field >Default Gateway.
Maestro UX-Workstation
In an Unix environment, change the directory /etc and enter:
route add <ip-adr1> <ip-adr2> 1
with <ip-adr1> = IP address of the Tool-PC in DigiNet S and
<ip-adr2> = IP address of the gateway in the O net.
This command is necessary after each reboot of the workstation.
1.3 Data throughput
1.3.1 Reading values

When loading the configuration from DigiTool, all the variables and function block data which
are announced to the gateway can be read and written from Maestro UX. In the gateway the
configured variables are arranged in a table with their names and tolerance ranges. The maxi-
mum number of variables depends only on the size of the memory available on the gateway
(memory = 8MB).
At any time a selection of these data can be read by a Maestro station. To this end, Maestro
UX logs the variables which are to be read for updating on through the gateway as soon as
their values are required (for archiving, for display in a faceplate, in a free graphic display, etc.)
and logs them off again when updating is no longer required. After an update inquiry, lists are
set up in the gateway for reading the values from the process stations. From this time on, the
updated values from the D-PS are buffered in the gateway with an update cycle of 1000 ms.
Each gateway can process a maximum of 10,000 updates at any one time. (Each update
represents a point to point connection: if the same process value is requested from two Maes-
tro UX workstations, two updates are required in the gateway).
The data from a Freelance 2000 process station are communicated via lists. Depending on the
data types of the variables and provided that no values of string data types are communicated,
an average of 250 values can be transported in a list.
A maximum of 10 lists are available for communication between a process station and a gate-
way. Therefore, approximately 2500 variables from each process station can be read via a
gateway at any one time. At another time, other variables, i.e. from other addresses, can be
read as a result of changed Maestro UX inquiries.
The values read from the process stations are checked in the gateway to see whether data
changes have been made. A tolerance range is used to specify which minimum data changes
are signaled to Maestro UX. The fastest update cycle between gateway and Maestro UX is
1000 ms. Regardless the data change, however, each value is send from the Freelance 2000
gateway to Maestro UX within 10 seconds.
20
In a Maestro UX workstation a maximum of 20,000 values can be managed for update simulta-
neously at any one time. Approximately 1000 value changes can be processed per second.
Assuming a value change on average every 20 seconds, one Maestro UX can process for up-
dating a maximum of 20 000 signals..
In steady state, a gateway can read a maximum of 2500 values from a process station at any
one time. More than 5000 values per second can be sent to Maestro UX.
‘Steady state’ means that no new requests are coming from Maestro UX. For every change in
request, triggered, for example, by calling up a new graphic display, more extensive processing
is necessary in the gateway so that in this case the 5000 value changes per second cannot be
guaranteed.
Overview of the data throughput when reading values
0DHVWUR8; 1000 values/s
20000 inquiries at any one time
> 5000 values/s
*DWHZD\
10000 updates at any one time
2500 values/s per D-PS
3URFHVVVWDWLRQV'36
21
1.3.2 Writing values

The writing of a value in the Freelance 2000 process station is generally triggered by an op-
erator action. Up to 300 write jobs per second can be processed in the gateway.
The writing of values has no influence on the efficiency of the read services in the gateway, i.e.
in addition to the 5000 changes to values to be read per second, these 300 write jobs per sec-
ond can be processed in the gateway.
1.3.3 Messages to Maestro UX

All messages generated in the process stations are sent to the gateway; the messages are fil-
tered in the gateway and routed to Maestro UX. All system messages are sent to the con-
nected workstation; process messages are only routed if a gateway access has been config-
ured for the tag which has generated this message. All the other process messages are re-
jected in the gateway.
A buffer for 3000 messages (V 3.2 = 2000 messages, V 2.3 = 1000 messages) is reserved in
the Freelance 2000 gateway. These 3000 (or 2000 or 1000) messages can be buffered within
one second. The buffer is enabled by Maestro UX for 5 messages per second, subsequently
again 5 messages per second can be buffered.
In a Maestro UX system there is just one message server for each coupling, i.e. all messages
from a gateway are sent to one workstation; the other workstations collect the messages from
this station with the message server. A message link is implemented from the Freelance 2000
gateway to the configured message server. For a Maestro UX system with application redun-
dancy, the Freelance 2000 gateway sets up a message link to each of the two message serv-
ers as from version V 3.2; when using the gateway software version 2.3, two gateways have to
be set up for the application redundancy.
1.4 Software packages
The add-on package DigiCSO is necessary for the Freelance 2000 system. This package
contains the gateway operating systems. During commissioning in DigiTool the operating sys-
tem matching the CPU module is loaded onto the gateway station.
In the Maestro UX system, the add-on package for Freelance 2000 must have been installed.
Both the Dig2CSO.x conversion program for converting DigiTool data and the descriptions of
the Freelance 2000 function blocks for Maestro UX as well as the associated faceplates are
contained in this package.
The transfer of project data from DigiTool to Maestro UX is carried out using the FTP software.
22
1.5 Configuration
1.5.1 Creating the gateway station in the project tree

In the project element Configuration CONF the number of gateway stations must be set to a
value greater than 0. For optimal usage of the system possibilities, the maximum numbers en-
tered here should not be greater than the number of operator and gateway stations actually re-
quired for the project.
In order to link a Freelance 2000 system with Maestro UX, a Gateway station D-GS or a redun-
dant Gateway station D-GS/RED must be entered in DigiTool in the project tree.
A change in the configuration of the numbers of stations influences the memory mapping
in the process stations. If the number of possible stations is subsequently changed, a
cold start of all process stations (Initialize or Load / Whole station) is necessary.
23
1.5.2 Configuration of a gateway station

The configuration of the gateway station consists in allocating a name, which must be a maxi-
mum of 4 characters long, and specifying the gateway type. In order to link a Freelance 2000
system with Maestro UX, the type DCP-Gateway must be entered.
kopp1us.bmp
This dialog is displayed directly in connection with the creation of a new gateway resource or
via the menu selection Project / Header... for a gateway.
Name any gateway name, max. 4 characters

Version date and time of object creation
Type DCP-Gateway
Ext. time server Loading the gateway station the function to synchronize other stations is
activated.
Enable Time synchronization can be switched on and off.
IP Address 1..3 Up to 3 stations can be synchronized by one gateway resource. Ad-
dresses from Maestro UX workstations or other DCP gateway stations
can be configured.
Drawing header / Drawing footer
see DigiTool Manual 1
24
After selection of ACCESS RIGHTS... the following dialog is displayed:
kopp2us.bmp
In this dialog, the access methods of the gateway are configured. The settings in this dialog are
given priority treatment over the settings in the subordinate objects.
Read only No write commands are ever relayed from the Maestro UX system to
the process stations.
Access For each process station in the project it is configured whether the gate-
way only has a read permission or a read and write permission.
In case only a read permission has been configured for a process station,
all write permissions related to a variable or a tag in this process station
are rejected in the gateway.
The entry Read only for the complete gateway overwrites the write per-
mission which has been configured.
For each process station which has been subsequently entered in the
project tree, the standard setting read permission by the gateway is en-
tered.
The configuration write permission is only effective if the checkbox Read

only is not selected.
Default access for new variables / tags
All newly created variables and tags are provided with the access rights
for gateways which have been configured here as default setting.
25
After selecting BOOT PARAMS... the boot parameters of the gateway are configured.
kopp7us.bmp
Memory These figures affect the memory mapping in the gateway.

Max. no. of objects The max. number of objects which can be loaded to the gateway.
PRAM size Memory area reserved for the configuration data. This memory area is
cold start resistant.
The value should be set to 1200.
Max. no. of connections

Gives the number of Maestro UX-Workstations which can be linked to this
gateway ( max = 10).
Reset on fatal error In case an internal error is detected in the resource during processing the
CPU module stops the processing. This entry permits the setting that the
CPU module leaves such an error state after 10 seconds by means of a
cold start.
A maximum of 10 Maestro UX-Workstations can be linked to a gateway.
26
1.5.3 Gateway station in the hardware structure

Each gateway station reduces the maximum possible number of operator stations by
one. In the structure display of the hardware editor one operator control station must be se-
lected and assigned to the gateway resource previously created in the project tree.
kopp10us.bmp
For documentation purposes it is possible to establish the correlation between resource and
equipment: first select a free slot in a process station and insert a gateway CPU in this slot. For
a non redundant gateway station select one DCP 02GWY or DCP 10GWY, according to the
hardware used; for a redundant gateway, two DCP 10GWY must be fitted. Each module is al-
located a name by the system; this name can be changed at any time.
The gateway CPU modules can be fitted in any one of the process stations, either in the central
unit or in an I/O unit.
27
After selection of a gateway resource in the structure display the fitted CPU module can be al-
located to the gateway. Select the name of the CPU module which is to be used as the gate-
way station. For a redundant gateway, two CPU modules are entered.
kopp9us.bmp
Example for the equipment allocation to a redundant gateway. If the hardware is allocated to a
non redundant gateway, the second entry CPU 2 is disabled.
The IP address of the gateway must be entered in the Network configuration. Regardless of
which CPU module - DCP 02 or DCP 10 - is used as the gateway, the gateway address in the
DigiNet S is always entered here. Thus it is guaranteed that the gateway station can always be
reached from DigiTool. For a redundant gateway, enter the IP addresses of both gateway
modules in the DigiNet S.
1.5.4 Configuration of the process stations

With very few exceptions, configuration of the process stations does not depend upon the cou-
pling with Maestro UX. In order to link a Freelance 2000 system to Maestro, the DigiTool proj-
ect data are transferred to the Maestro UX system and converted with the Dig2CSO.x conver-
sion program. When creating the project in DigiTool, a few matters concerning the Maestro UX
connection must be taken into consideration.
28
1.5.5 Names of tags and variables

For each linked tag and variable, an object with the appropriate name is stored in the Maestro
UX system in the central object list (COL). In the gateway station, the names of tags and/or
variables are converted into process station addresses. The name allocation must meet the
conventions of all three systems.
In DigiTool all texts with Unicode characters are stored, no Unicode characters are processed
in the gateway station. When loading the names in the gateway, the Unicode characters are
converted.
Names of tags and variables which are to be linked via the gateway may only contain
ASCII characters (highest byte = 0).
The names of Freelance 2000 variables begin with a letter and continue with numerals, letters
or underscore. It is forbidden to have an underscore at the start. The standard conventions on
the energy market that variable names may begin with numerals is not implemented in Free-
lance 2000 at the moment.
Tag names in Freelance 2000 are composed freely from any visible characters. The following
names are forbidden for the coupling:
• Names beginning with ‘_’ or ‘.’ or ‘=‘
• Names containing ‘$’, ‘/’, ‘~’, ‘%’, '.'
It is recommended not to use special characters in the names of tags and variables
which are to be linked via the gateway.
Up to version 3.3 it was possible to use the same name for a tag and a variable in a Free-
lance 2000 project. On Maestro UX a name may occur only once; the same name for two ob-
jects is forbidden. Also when loading different Freelance 2000 projects, same names must be
avoided. If two objects having the same name belong to one class, they overwrite each other
when stored in the COL - the last save wins.
Reconfiguration of a project and a new upload can have similar effects as when loading from
different projects - Maestro UX cannot distinguish between the two.
In Freelance 2000 names can be used which differ only in that they are in upper and lower
case letters. If these two objects (tags or variables) are linked via a gateway, a warning of a
possible name collision is generated by the plausibility check. This warning must be heeded for
a data link via a DDE gateway, for a Maestro link this message can be ignored (as under
Maestro UX a distinction is also made between upper and lower case letters).
(For the identification of non conforming names, see Section 1.5.10, Conversion of the
PLCOpen file into Maestro UX data).
29
1.5.6 Specification of the data available via the gateway

In connection with project configuration, it is necessary to define which data from the process
stations are to be available in the Maestro UX system via the gateway. For every tag and every
variable of the project, it is necessary to configure whether the data from the process station
can be read and/or written via the gateway.
In the station view (Tag list or Variable list Å Station view) the permitted access methods
through a gateway can be configured for every list entry.
The configured station access rights are visualized in the tag list and in the variable list by indi-
vidual letters:
kopp6us.bmp
R Read
W Write
After double-clicking on the left mouse button in a gateway column or positioning the cursor in
a line and making the menu selection Edit / Station access..., the dialog for configuring the ac-
cess options is displayed. The station access can be changed jointly for several list entries by
marking several entries with SHIFT + ARROW KEYS before calling up the menu (Station ac-
cess...).
30
kopp5us.bmp
Station List of the configured gateway stations; in the tag list, the operator sta-
tions are also listed;
Access Only for DigiVis stations; insignificant for gateway linking
Read The data of the previously selected variable(s) or tag(s) can be read
from the process station via the gateway.
Write The data of the previously selected variable(s) or tag(s) can be modi-
fied in the process station via the gateway (only user-defined variables
can be written, predefined variables of the process station can only be
read).
No access via the process image should be configured for variables which can be written
via a task or via the gateway. The write command can be lost during implementation of
the process image.
If these variables are to be used in a redundant task they should be mapped on other
variables.
31
1.5.7 Commissioning
During commissioning a gateway resource is treated similarly to a process resource. Via the
dialog (select project tree element Å Project Å Header...) the functions BOOTSTRAP, INITIALIZE
ALL, INITIALIZE and COLD START are possible. The configured station ACCESS RIGHTS can be visu-
alized. In connection with a redundant gateway it is possible to trigger a redundancy toggle with
PRIM/SEC.
kopp8us.bmp
kopp8aus.bmp
In connection with the first commissioning of a gateway Load Å Whole station is necessary;
changes in configuration are transferred to the gateway station via Load Å Changed objects.
With the load process from DigiTool all variables and tags for which the access through this
gateway has been configured are announced to the gateway station. Data of these variables
and tags can later be displayed and possibly modified on a Maestro UX system.
32
1.5.8 Preparing project data for transfer to an external system

A special file format, the PLCOpen file, is used to transfer project data to external systems, for
example Maestro UX. This file is first stored on the hard disk of the DigiTool PC. The project
data are stored in the PLCOpen format on the hard disk by selecting Project Å Export.. from
the main menu, selecting the file type PLCOpen file (*.plc) and indicating a file name.
The PLCOpen file should always be created out of a project which has undergone a
plausibility check.
1.5.9 Transfer of the PLCOpen file to the Maestro UX system

Using the FTP software the PLCOpen file exported from DigiTool is transferred to the Maestro
UX system. The transfer can be initiated either on the PC or on the workstation. When the FTP
software is started, the IP address of the other station (DigiTool PC or Maestro UX workstation)
must be stated. In case that DigiNet S and the O net are separated into two networks via a
DCP 10, the gateway has to be entered as a router in the DigiTool-PC and in the workstation
(see Section 1.2.4, DCP 10 gateway with DigiNet S and O net separated and/or Section
1.2.6, redundant DCP 10 gateway with DigiNet S and O net separated). Once a connection
has been established between the DigiTool-PC and the Maestro UX-Workstation, the PLCO-
pen file can be transferred (see description in Operating Instructions 42/72-3822).
/usr/contronic/appl/dgw/upload must always be used as the target directory when transfer-

ring the PLCOpen file to the workstation.
In order to transfer a PLCOpen file using FTP, the installed DigiNet S and O net connections
are used. If two separate networks are used, the file is routed by the gateway; if one network is
used for DigiNet S and O net, the file is transported ‘past’ the gateway to Maestro UX.
When a router function is carried out on the DCP 10 gateway, a previously installed link contin-
ues to function, i.e. the data continue to be updated on Maestro UX.
1.5.10 Conversion of the PLCOpen file into Maestro UX data

A PLCOpen file contains all relevant project data. Via the system dialog on Maestro UX, func-
tions are called up with which the data of the PLCOpen file are converted into Maestro UX data
and are stored in the database of the Maestro UX system, the central object list (COL) (de-
scription in operating instructions 42/72-3822). The Freelance 2000 function blocks are
mapped in Maestro UX with their faceplates, and accordingly the data required for the face-
plates are transferred to the workstation.
Firstly, all gateways which are present in both the PLCOpen file and in the configuration data of
the Maestro UX system are determined with the Dig2CSO.x data conversion program. To this
end, the IP addresses of the gateways are compared in the Maestro UX version 1.2x. As from
33
the Maestro UX version 2.0, the gateway names are compared. If no identical names are found
in the PLCOpen file and in the Maestro UX configuration, a consistency check of the IP ad-
dresses is carried out in the same way as in the earlier versions.
For all tags and variables of the gateways known in both systems, objects are created for the
COL. Each of these objects contains a COMI selector in which the name of the ‘provider’ of the
data is entered. The Maestro UX name of this gateway is entered in all objects created by the
Dig2CSO.x converter.
The Dig2CSO.x conversion program recognizes most of the existing names which meet the
convention and the corresponding entities are filtered, i.e. the objects are not created in the
Maestro UX system (for the names which meet the convention, see Section 1.5.5, Names of
tags and variables).
After the conversion, error messages should be traced using

grep Error /usr/contronic/tmp/Dig2CSO.log
Upon this command, all the lines of the log file containing the text 'Error' are displayed.
Another log file is created when the data are stored in the central object list (COL):
ErrTrace.log. Error numbers 13405 and 13406 describe the tags and variables for which no
object could be stored in the central object list because an object from another class already
exists under this name.
It is possible to show a describing text to the error number:

errlits <error number>
The non conforming objects and names need to be corrected in DigiTool. After this, the PLCO-
pen file has to be newly created, transferred to Maestro UX and reconverted.
1.5.10.1 Project data of the DigiVis station

The project configuration of the DigiVis stations is not transferred to Maestro UX, only the con-
figuration of the process stations. There is thus no transfer from Freelance 2000 to Maestro UX
of
• Graphic displays,
• Group displays,
• Trend displays,
• Archives,
• Display accesses.
All settings concerning these items must be reconfigured on Maestro UX.
34
1.5.10.2 Conversion of texts by the converter

A text is stored with a standard specified by the operating system. As Freelance 2000 and
Maestro UX run under different operating systems, Windows and Unix, all Freelance 2000
characters must be converted into the equivalent Maestro UX characters when project data are
transferred.
The names of tags and variables are also used in the gateway as well as in DigiTool, DigiVis
and Maestro UX. The name table is loaded by DigiTool and update requests are made by
Maestro UX to the gateway concerning the names. Therefore, these identifiers may only con-
tain characters which are identical on all systems (see above, the chapter on Names of tags
and variables). The other texts - short text, long text, comments - are generally correctly con-
verted in the German and English versions, including the special characters used.
In the Freelance 2000 version 2.3, for a Russian project the converter with the option ‘-k’ (for
Cyrillic) must be called up. This is only possible on UNIX level in a terminal window (shell).
In the Freelance 2000 version 3.2, Russian characters are stored by DigiTool as Unicode
characters (2 byte-coded); these characters are not processed by the conversion program of
the Maestro UX version 1.2. Only 1 byte-codable characters are permitted for all texts.
As from Maestro UX version 2.0 the converter processes Unicode characters. Characters
from the ISO tables 1, 2 and 5 are converted; it is thus possible to use Western European,
Eastern European and Cyrillic characters. Before calling up the converter, the software pack-
age with the related language needs to be installed in Maestro UX.
1.5.11 Display of Freelance 2000 data on Maestro UX

As soon as the objects for the Freelance 2000 tags and variables have been created and
stored in the COL, all the necessary data of the Freelance 2000 project are in the Maestro UX
system. Tag and variable faceplates can be called up and values from tags and variables can
be used in graphic displays and logs. The operation of parameters and variables is also directly
possible.
In the same way, the messages from the Freelance 2000 process stations are immediately re-
ceived from the gateway in the Maestro UX system.
35
1.5.12 Reconfiguration of data relevant to Maestro UX

In order to implement Freelance 2000 projects on Maestro UX, a Maestro UX object is created
for every function block and every variable. To this end, there is a mapping rule for every
Freelance 2000 function block and variable type which is available on Maestro UX via a gate-
way. The values configured in Freelance 2000 are accepted in the Maestro UX objects and all
parameters which are not available in Freelance 2000 are allocated suitable default values at
the initial configuration.
Special Maestro UX functional capabilities such as archiving, display access, etc. must be con-
figured with online configuration. Most of the other data can also be modified again in the
Maestro UX configuration dialog. However, you should consider that if the project is reloaded,
for example after a project change in DigiTool, all the values configured in DigiTool will be
overwritten.
The source for the Freelance 2000 function blocks on Maestro UX is DigiTool. All con-
figurations which DigiTool makes possible are to be carried out on DigiTool. Only Maes-
tro UX-specific configurations are to be carried out on Maestro UX.
Example: The operator access of a value is part of the function block information, it originates
in Freelance 2000 and is thus overwritten with the current project data in connection with each
upload. The display format of a function block parameter is pure Maestro UX information and is
not configured on Freelance 2000. When an object is created, a default format is entered; any
change in format for this entity is retained with a new upload of the object.
The selectors which are overwritten by a new upload on Maestro UX are not marked in the ob-
ject editor. If several objects of one type are to be modified in the same way, you should there-
fore test with one individual entity whether the modifications are retained when the project is
loaded again. You can proceed as follows:
1. After creating the OBL file,

grep tagname OBLfile > tagname.obl
can be used to create a file which contains only the entity with the name tagname.obl.
2. This file can be stored in the central object list (COL) using
Exchange -p . -lf tagname.obl -ak
and can be viewed in the object editor.
This procedure is also recommended in connection with modifying individual entities in large
projects as it results in the load times being much shorter and the effects (overwriting reconfig-
ured values) remaining low.
36
1.5.13 Loading to the gateway from Maestro UX

After a Freelance 2000 object is modified with Maestro UX online configuration, a link object
(FTYP = DGW_Obj) is automatically created for the modified object. If a modification affects the
method of operation of the gateway, this functional capability must be loaded to the gateway by
a download from Maestro UX:
Select Configure / Digimatik / Gateway / Download in the system dialog and select gateway. All
link objects in the Maestro UX system will be loaded to this gateway.
The creation of gateway objects in Maestro UX and the loading to the gateway from Maestro
UX is only necessary if tolerance ranges have been modified. After the project data are loaded
from DigiTool, all signals are already linked with the standard tolerance range (the tolerance
range indicates which changes in values are to be sent to Maestro UX; this evaluation takes
place only for values of data type REAL or FLOAT).
1.5.14 Time synchronization

A gateway station can be used as time master for a Maestro UX workstation. Two configuration
steps are necessary: The gateway resource must be enabled to send the time synchronization
message to the workstation. The workstation has to be configured to read and process this
message.
The IbnTool of the Maestro UX system must be used to configure the gateway as time master.
With this configuration step the workstation is able to read the time synch message.
In the gateway resource the function for sending the time synch message has to be switched
on. Therefore a load process must also be carried out from Maestro UX to the gateway.
Maestro UX version 1.2x and 2.0: in order to load the time master functional capability from
Maestro UX to the gateway, at first at least one link object must be created. The time master
functional capability cannot be loaded individually to the gateway.
With Freelance 2000 version 4.1 it is possible to enable the time master function with Digi-
Tool. During the gateway resource configuration the Ext. time server function can be enabled.
Up to 3 stations can be configured with their IP addresses. Loading the gateway station the
time master function is enabled.
Entering the IP address of the Maestro UX workstation in this dialog, the download from Digi-
Tool to the gateway will start the time synchronization process. The gateway has to be config-
ured in the Maestro UX system as time master, but a download from Maestro UX to the gate-
way is not necessary.
37
kopp11us.bmp
1.5.15 Subsequent project changes

After a change of configuration in DigiTool and Load / Changed objects to the process station,
at first no more operation is possible from Maestro UX via the gateway. Only after Load /
Changed objects to the gateway can the Freelance 2000 function blocks be operated again.
After each load process to a process station it is necessary to load to the gateway via
DigiTool - regardless of the extent of the change.
There is no version monitoring between Freelance 2000 and Maestro UX. This means that the
balancing of the project data must be ensured by the user. After a project change in DigiTool,
repeated creation, transfer and loading of the PLCOpen file to Maestro UX is only necessary if
data and parameters have been modified which are relevant for the display on Maestro UX. For
example, if a function block was added to the project, the adaptation of the workstation configu-
ration is only necessary if this function block is also to be available via the gateway.
With the repeated loading of a project, new entities are added and old entities (apart from some
protected selectors in the class) are overwritten. Old entities from earlier load processes are
not deleted if their tag names are no longer used. The central object list (COL) of Maestro UX
must be tidied up ‘manually’.
38
Load time reduction

After a reconfiguration of the Freelance 2000 project with a change of configuration of a proc-
ess station, there is a version conflict with the gateway after the Load / Changed objects of the
process station. In this state, operator access to Maestro UX is no longer possible. The inter-
ruption time can be minimized as follows:
1. Adapt and check the Freelance 2000 project but do not yet load it on the PS.
2. Create the PLCOpen file of the project.
3. Transfer it to Maestro UX (by ftp).
4. Convert project data (PLC to OBL file).
5. Store objects in the central object list (COL) (caution: entities may be overwritten which are
required for current operation).
6. If tolerance ranges are changed, link objects are automatically created when the objects
are saved.
7. Load to the process station from DigiTool.
8. Load to the gateway from DigiTool.
9. Load to the gateway from Maestro UX if tolerance ranges have been changed.
Point 5 changes the Maestro UX configuration to the new state and most (unchanged) entities
can still be accessed by the operator. Only a few minutes are required for points 7-9 in large
projects.
1.6 Application redundancy
For a system with application redundancy and subordinate Freelance 2000, there should be a
gateway for every Maestro UX system. In DigiTool these two gateways must be configured
identically.
39
2 Display of Freelance 2000 data on Maestro UX
2.1 Mapping of Freelance 2000 function blocks and variables on Maestro UX
Function block classes which are available on DigiVis are displayed on Maestro UX (for the as-
signment of class identifiers, see the appendix). Not all selectors of the Freelance 2000 func-
tion blocks are available on Maestro UX. Those selectors are displayed which are required for
display in the faceplate.
In connection with the coupling of a communication function block (Modbus, Send and Receive,
telecontrol protocol) the messages of this function block are transferred to Maestro UX.
2.2 Faceplates on Maestro UX and DigiVis
Displays on DigiVis and Maestro UX have been aligned. Some differences arise out of the dif-
ferent properties of the two systems.
2.2.1 Fundamental differences

2.2.1.1 Size of the faceplates
On Maestro UX all faceplates have the same size (1/6 of the display area or group display).
2.2.1.2 Display of messages in the faceplate

Messages from a tag are visualized on the two systems in different ways:
DigiVis: The message information is read from the message management of the DigiVis sta-
tion. The header of the faceplate is displayed in the priority color of the highest-value message
of the tag.
Maestro UX: The text in the faceplate header (tag name and short text) is displayed in red if
there is at least one message from this tag. The background of the faceplate header is high-
lighted in red if an error status is present at the function block. The ERR output of the function
blocks is used for this.
Message-relevant data cannot be configured in the signal box for Freelance 2000 objects (for
example message priority). They are delivered with the message via the gateway.
40
2.2.1.3 Layout of the faceplates

On Maestro UX a status field is additionally displayed between the value display and the op-
erator panel.
2.2.1.4 Operator panel

In Freelance 2000 keys which cannot be operated are displayed in gray, in Maestro UX there is
no optical identification. A message comes only after operation if writing, for example by the
configuration, was not permitted.
2.2.1.5 Operation
DigiVis has language-specific names for the selectors operated, on Maestro UX the selector
names are displayed.
2.2.2 Class-specific differences

2.2.2.1 String data type
String data types are not currently supported.
2.2.2.2 Date&Time data type

Each value of the Date&Time data type is interpreted on Maestro UX as GMT (Greenwich
Mean Time) and converted into the current time with the current time zone and the summertime
table.
The value of a constant function block is displayed on DigiVis without further calculation; for the
display of variables in a graphic display, the configuration specifies whether conversion is to
take place.
2.2.2.3 PackedBool data type (BYTE, WORD, DWORD)

Maestro UX cannot write PackedBool data type values.
41
2.2.2.4 Structured Data Types

There is no representation of variables of structured data types, even the components are not
accessible on Maestro UX.
2.2.2.5 Global variables

Maestro UX features faceplates for global variables. Freelance 2000 variables cannot be oper-
ated after the first upload. The operability can be changed in Maestro UX online configuration.
It is not changed by a repeated upload.
Operation of variables is only possible if the operator access on Maestro UX is reconfig-

ured.
Variables in Maestro UX can be scaled. At the first upload of a variable, the selectors are set to
the following values and these values can be changed in the Maestro UX on-line configuration;
they are not changed by a new upload:
Real Variables (REAL)

Scale start SKL/SKA 0.0
Scale end SKL/SKE 100.0
Dimension SKL/DIMT/HREF % TLIST/DIM/PERCENT
Integer Variables (INT, DINT, UDINT, UINT)

Scale start SKL/SKS 0
Scale end SKL/SKE 10000
Bitstring Variables (BYTE, WORD, DWORD)

Scale start SKL/SKA 0
Time Variables
Scale end SKL/SKE 01:00:00 (1 hour)
In Freelance 2000 global variables can be provided with comments (33 characters). These
comments or their start are displayed both on the long text (30 characters) and the short text
(12 characters) of the variable object on Maestro UX.
42
2.2.2.6 Signals of I/O modules

With Freelance 2000 version 4.1 signals of the I/O modules can be used directly within the dif-
ferent editors. An allocation to global variables is not necessary .
It is not possible to connect these signals directly over the gateway. For coupling to Maestro
UX the signals of I/O modules have to be allocated to global variables.
2.2.2.7 BYTE, WORD, DWORD / CSDPB constant function blocks

Like the bitstring variables, bitstring constants also feature a scaling. At the first upload, the
selectors are set to the following values:
2.2.2.8 DINT / CSDINT constant function block

The faceplate of the DINT constant function block displays the bargraph for positive values in
the color of the negative values.
For operator interventions on Maestro UX (Operating Window) on a DINT constant function

block, figures in the area of the maximum values are relayed incorrectly to Freelance 2000, for
example the Maestro UX value 123456789 is sent as 123456792 to Freelance 2000.
2.2.2.9 Communication function blocks

There is no faceplate for the communication function blocks (Modbus, Send and Receive,
Telecontrol). If these function blocks are linked via the gateway, the messages are transferred
from Freelance 2000 to Maestro UX.
2.3 Sequential function chart (SFC)
2.3.1 Steps of an SFC

In DigiTool comments can be allocated to every step of an SFC. These comments (max. 20
characters) are displayed on step texts 1 and 2 by Maestro UX. A new line is started preferably
at blank characters, after special characters ‘,’, ‘.’, ‘-‘, ‘/’ or at a change from lower case to upper
case. Step texts 1 and 2 are displayed in the standard display on Maestro UX.
From Maestro UX the step delays of an SFC are not operable. The same applies to Permanent
On/Off.
43
2.3.2 Tip mode

In Maestro UX tipping is only possible for user with names ‘TT...’. Tipping backwards is not
supported.
2.3.3 Action windows

Only variables of data type BOOL can be written from action windows on Maestro UX. The op-
erability of the variables must be reconfigured on Maestro UX and is retained even after re-
peated upload. The action window corresponds to the criteria window of a step on DigiVis.
2.3.4 Transitions
For the variables displayed in the transition window, transition-specific comments can be allo-
cated in Freelance 2000. For the display in Maestro UX, the general comments of the variables
are accepted.
The criteria window on Maestro UX can be displayed either in table form or in the form of gate
logic. If gate logic is selected as the display form, an AND and an OR gate are displayed. The
output of the AND gate is an additional input of the OR gate. The output of the OR gate dis-
plays the transition result. The inputs of the two gates correspond to the variables in the AND
or OR section of the criteria window on DigiVis. When the transition is computed, the signal
lines are highlighted. Criteria which have been met are displayed in green and criteria which
have not been met are displayed in red.
In the table display only the criteria which have not been met are ever displayed. The criteria
which have not been met are highlighted in red when the transition is computed. Thus it is easy
to see why a transition has not yet switched. In both display forms of the criteria window an
autoscroll mode can be activated. In this case, the criteria window of the currently active transi-
tion is always displayed. On account of the screen layout, however, only two criteria windows
can be displayed simultaneously.
In a Freelance 2000 system it is possible to configure an SFC program with 8 * 16 = 128 si-
multaneously "active" transitions. On a Maestro UX workstation a maximum of 16 transition
statuses can be displayed.
44
2.4 Graphic displays
In DigiVis only variables can be used to animate graphic displays. On Maestro UX access is
possible to all - linked - selectors.
2.5 Group displays
The configuration of the group displays on Freelance 2000 is not transferred to Maestro UX.
One important reason for this is the different faceplate formats.
2.6 Overview display
For the display of group displays, there is, for every function block for which a faceplate exists,
an additional ‘small’ faceplate for display in the overview display. In general, these displays cor-
respond to those in Freelance 2000. The following deviations occur:
• All ‘small’ faceplates have full display height like the standard faceplates.
• For the individual drive functions, the run direction arrows are not displayed.
2.7 Messages
All system messages of the Freelance 2000 system are transferred to Maestro UX.
Of the messages which are caused by function blocks, only those messages for the function
block of which write or read access via the gateway has been configured are relayed to Maes-
tro UX.
2.7.1 Display of priorities

In Freelance 2000 there are message priorities 0 to 5. Message types are linked to these pri-
orities.
From version 3.1, the system error messages in the Freelance 2000 system are also subdi-
vided into system message groups S1, S2, and S3. These groups are visible at the operator
interface (message page, Signal Sequence Log SSL) and can be used for filtering (for example
in the message page) and for initiating actions (horn, entries in SSL).
45
The division of the 3 system message groups (with examples):
S1: Internal system errors / process and GWY CPU internal.

System messages concerning process CPU hardware and software (cold/warm start of the
Freelance 2000 process station), GWY CPU hardware and software (lost DigiNet S or O net
link, messages lost from process station xxxx), CPU and GWY redundancy (Prim/Sec Tog-
gle), execution system (task unrunnable, start/stop of the resource), power failure
S2: Internal periphery errors, operations:

Internal I/O system messages, self-test of the I/O modules, lateral communication, task op-
erations
S3: External periphery errors, (“others”):

No power supply, line break or short circuit at I/O terminal
The Freelance 2000 messages are displayed as follows on Maestro UX:
Freelance 2000 Maestro UX

Prio Type Prio Type
0 System S1 1 SY control system
0 System S2 2 PI process interface
0 System S3 3 PI process interface
1 Fault 1 Fault
2 Fault 2 Fault
3 Fault 3 Fault
4 Switch 4 Switch
5 Hint 9 Switch
A special feature exists for the EVENT function block. In Freelance 2000 this function block is
used, for example, to start logs and archives. On Maestro UX this functional capability cannot
be used. An event initiated by this function block is displayed with priority 10 in the message
page.
2.7.2 Filtering messages without configuration information

All messages from the Freelance 2000 system are sent to the gateway. In the gateway only
those objects are known for which a read or write access has been configured via the gateway.
In version V2.3 messages from objects not known in the gateway are provided with a substitute
name and signaled to Maestro UX. From version 3.2 these messages are filtered in the gate-
way, i.e. are no longer communicated to Maestro UX.
System messages are always communicated to Maestro UX.
46
2.7.3 Substitute names for messages

For messages from the Freelance 2000 objects resource and task, substitute names are gen-
erated in the gateway:
Resource: DIGI_RSC_Sn_Om/Ai
with n=Freelance 2000 PS station number, m=object number, i=alarm index
Task: DIGI_TSK_Sn_Om/Ai
with n= Freelance 2000 PS station number, m=object number, i=alarm index
As from Freelance 2000 version 3.3 messages from a task are displayed with the task name.
Only messages from a resource are generated with the substitute name.
2.7.4 Messages in connection with Maestro UX application redundancy

As from version V 3.2, the gateway supports two message links; thus, for messages, applica-
tion redundancy can be implemented with one gateway.
2.7.5 Display of messages

Display of the texts in the message page:
Long text = <alarm type> : <message text> / <long text of the function>
For analog monitors only the selector (L1…L4) is displayed in the message page instead of the
alarm type unlike in Freelance 2000.
For information on the system message groups of Freelance 2000, the text “S1“, “S2“ or “S3“ is
displayed as the start of an error text on Maestro UX.
2.7.6 Acknowledgement of messages

According to the Maestro UX system, messages are acknowledged locally within the worksta-
tion. If a message is acknowledged on a workstation, this is not signaled to the process station.
Accordingly, an acknowledgement made in DigiVis is not relayed to Maestro UX.
47
2.7.7 Hints
The Freelance 2000 hint texts are collected from all limit values and displayed in the help page
of the function block on Maestro UX. The associated selector is placed before each text.
All hints are consecutive. If no hint texts have been configured, the Maestro UX help text only
contains the selectors (example for a controller block: "L1:L2:L3:L4"). Until Maestro UX version
1.2 the help text in the Maestro UX system has a maximum 248 characters; as a result, the
hints can be truncated for function blocks with several messages.
2.8 Archiving
Only the Freelance 2000 signals with the Maestro UX data types FKH_... can be archived. For
the Maestro UX data types BTY_... archiving can be configured, but these signals with BTY_
data types are not stored in the archive files.
In the configuration dialogs it is not possible to see which Maestro UX data type the individual
selectors have. The data types BTY_... are mainly used for binary and discrete signals; most
analog values have data type FKH_... and can be archived.
2.9 DigiBatch
There is no display of the PLI function block on Maestro UX.
2.10 User-defined function blocks
The instances of the inner function blocks of a user function block can be operated and ob-
served. Emulation of the user FB on Maestro UX is possible by creating a new class (create a
class, possibly expand text lists and CTYPE lists, create a faceplate, expand Maestro UX sys-
tem objects by the new class). This should be left to the experts.
48
2.11 Horn function
Acknowledgement of the control-room horn in Maestro UX can be linked to the Freelance 2000
horn. Proceed as follows:
In Freelance 2000 a horn function block is configured, the inputs of which are described by
variables.
In order to control a horn from Maestro UX, a horn object must be configured in every worksta-
tion. The name of the horn object is <hostname>_HORN.
In the configuration of this horn object, the link to the Freelance 2000 horn is established under
[HORN I/O] by the global variables of the process station being assigned to the inputs and out-
puts of this object.
By assigning the variable which describes the set input of the horn function block to the output
‘HORN IS ACTIVE’, the Freelance 2000 horn is activated when the Maestro UX horn is activated
(syntax: <Var.Name>/DigVal/SIG/WERT).
By assigning the variable which describes the reset input of the horn function block to the out-
put ‘HORN ACKNOWLEDGEMENT’, the acknowledgement of the Maestro UX horn is relayed to the
Freelance 2000 horn.
49
3 Time synchronization
3.1 Time synchronization within a Freelance 2000 system
All CPU modules within a Freelance 2000 system (process stations and gateway stations) have
equal rights regarding time synchronization. In general, the module with the lowest station
number assumes the time master function for the CPU modules among themselves.
If a radio clock is connected to a CPU module, this CPU becomes time master in the Freelance
2000 system.
All PCs within a Freelance 2000 system (DigiTool, DigiVis, DigiDDE) can be synchronized by
this process station (setting during setup procedure). Without time synchronization of a Free-
lance 2000 PC, the curve and trend display does not function correctly.
3.2 Time synchronization of several Maestro UX
In a Maestro UX network, one of the workstations is configured as the time master. Only this
workstation monitors the input of a time synchronization message; the other workstations read
the time from this workstation and synchronize themselves with it.
In the ‘time master workstation’ a gateway is configured as the time supplier. On reception of a
time synchronization message, a check is carried out in the Maestro system as to whether the
message comes from the configured time supplier. Only these messages are accepted and
processed.
3.3 Time synchronization via a gateway
Within a Freelance 2000 system, the time synchronization is sent as a broadcast. Even if a
Maestro UX workstation is in the same network, this time message is not interpreted by the
workstation. If a DCP-Gateway is configured as the time master for a Maestro UX workstation,
the gateway sends the time information specifically to the IP address of this workstation.
If a CCO is configured as the time master, it also sends the time information as a broadcast but
in a format that is used by the 'time master' workstation.
This time synchronization message is also received and interpreted by all Freelance 2000
gateways. In this way, the Freelance 2000 systems are synchronized by one CCO.
50
3.4 System time, local time, summertime
In the process stations the system time (Greenwich Mean Time GMT) is used for all time
stamps.
The local time is calculated from the system time and the time zone. The time zone is uniform
throughout the project and is transferred to all stations during bootstrap loading and initializa-
tion (from V3.3). Within the process station, the system time is used and local time is available
to the user (for example for regular, daily events).
All timed data are transferred to DigiVis with the system time. For display on DigiVis the system
time is converted into the current time with the time zone and the summertime table of the
DigiVis PC.
If time stamps are expected by the Maestro UX workstation, which do not exist within the
Freelance 2000 system, the corresponding data are expanded by this time stamp within the
gateway.
In the Maestro world the system time is also used for all time stamps of data. Each value of
data type Date&Time is converted in the workstation with the current time zone and summer-
time.
Time synchronization always takes place with the system time.
3.5 Time synchronization with DCP 02 gateway
In the following examples a Freelance 2000 system is generally represented by one D-PS, one
DigiVis PC and the DigiTool PC. In the O net one workstation is the time master for the other
workstations; this master clock is synchronized by a CCO or a gateway. For this reason, in the
following examples only one workstation is shown in each case; all other workstations are of no
significance for the time synchronization.
51
3.5.1 Maestro UX workstation (WS), 1 Freelance 2000 system
n_1f2k.bmp
All stations, workstation, gateway and all process stations, are in a network, i.e. the base IP
addresses and subnet masks of all stations must be configured identically. One of the Free-
lance 2000 CPU modules assumes the time master functional capability for the other process
stations and the gateway.
In WS1, GWY is configured as the time master for the Maestro UX. The gateway sends the
message for synchronization to the workstation.
52
3.5.2 Application redundancy
n_apred.bmp
For the implementation of application redundancy, it makes sense to double the gateway (GWY
and GWY’) as well as doubling the workstation (WS1 and WS1’).
All stations, workstations, gateways and all process stations, are in a network, i.e. the base IP
lance 2000 CPU modules is the time master for the other process stations and the gateways.
In DigiTool both gateways are configured completely identically.
For each Maestro UX workstation the associated gateway is configured as the time master, i.e.
GWY for WS1 and GWY’ for WS1’.
53
3.5.3 Maestro UX, 2 Freelance 2000 systems
n_2f2k.bmp
All stations, workstation, gateways and all process stations, are in one network, i.e. the base IP
lance 2000 CPU modules assumes the time master functional capability for the other process
and gateway stations.
The data from Freelance 2000 system 1 are delivered to Maestro UX via GWY1, the data from
system 2 via GWY2. One of the two gateways is defined as the time master for Maestro UX. If
this GWY fails or is taken out of the network, there is no time master for Maestro UX.
The two Freelance 2000 systems are in the same network, there is therefore only one time
master for both systems. The time synchronization for the Freelance 2000 systems is sent as a
broadcast, but is not received by the workstation as the message is sent to a port which is not
monitored by Maestro UX. Configuring a gateway as the time master for Maestro UX results in
the gateway creating an additional time synchronization for Maestro UX.
54
3.5.4 Maestro UX, 1 Freelance 2000 system and CSC
n_f2cco.bmp
The workstation, gateway and all process stations are in one network.
The time synchronization message from a Freelance 2000 gateway is not understood by the
CCO; however, the gateway understands a message from a CCO. On account of these prop-
erties, the CCO must be defined as the time master. After receiving a time message from a
CCO, the gateway becomes the time master in the DigiNet S; as a result, the Freelance 2000
modules are synchronized by the CCO.
If there are several CCOs in the system, it is necessary to ensure that only one station sends
time synchronization messages or that all synchronization messages run with identical times,
as otherwise the gateway accepts the new time with each synchronization message and
‘jumps’ accordingly.
The problem can be avoided by using a router in order to separate the Freelance 2000 system
from the rest of the network. A radio clock should be used to ensure that both subnets run with
identical times.
If the above example is expanded by another Freelance 2000 system, both gateways become
time masters in the DigiNet S. As the two time masters run with identical times, no problems
arise as a result; however, to reduce the network load, separate networks should be con-
structed for the two systems with a router.
55
3.6 Time synchronization with DCP 10 gateway
In the following examples a Freelance 2000 system is generally represented by one D-PS, one
DigiVis PC and the DigiTool PC. In the O net one workstation is the time master for the other
workstations; this master clock is synchronized by a CCO or a gateway. For this reason, in the
following examples only one workstation is shown in each case; all other workstations are of no
significance for the time synchronization.
For the time synchronization it makes no difference whether a redundant or a non redundant
gateway is used. In a redundant gateway the functional capacity ’time master’ is assumed by
the redundancy partner of the gateway in case of a redundancy.
3.6.1 Maestro workstation (WS), one Freelance 2000 system
nn_1f2k.bmp
DigiNet S: The time in the process stations is set by DigiTool. All stations in the
DigiNet S - including the gateway - synchronize themselves with each
other.
O net: In WS1, GWY is entered as the time master.
56
3.6.2 Application redundancy
nn_apred.bmp
For the implementation of application redundancy, it is sensible to double the gateway (GWY
and GWY’) as well as doubling the workstation (WS1 and WS1’). In DigiTool the two gateways
are configured completely identically.
DigiNet S - including the two gateways - synchronize themselves with
each other.
O net and O net’: The two networks are independent of one another. For each Maestro UX
workstation the associated gateway is configured as the time master, i.e.
GWY for WS1 and GWY’ for WS1’.
Application redundancy can also be implemented with just one gateway. For the time synchro-
nization this gateway must be configured as the time master in both workstations (WS1 and
WS1’).
57
3.6.3 Maestro UX workstation (WS), two Freelance 2000 systems
nn_2f2k.bmp
DigiNet S1: The time in the process stations is set by DigiTool1. All stations in the
DigiNet S1 - including GWY1 - synchronize themselves with each other.
DigiNet S2: The time in the process stations is set by DigiTool2. All stations in the
DigiNet S2 - including GWY2 - synchronize themselves with each other.
O net: One of the gateways - GWY1 or GWY2 - is the time master for the work-
station.
The synchronization message sent by the time master gateway is not understood by the other
gateway. Therefore, the two Freelance 2000 systems are not synchronized with each other.
Uniform times for all stations involved must be implemented using a radio clock.
58
3.6.4 Maestro UX workstation (WS), one Freelance 2000 system and CSC
nn_f2cco.bmp
DigNet S - including GWY1 - synchronize themselves with each other.
C net: The stations within the C net synchronize themselves with each other.
O net: The time synchronization message from a Freelance 2000 gateway is not
understood by the CCO; however, the gateway understands a message
from a CCO. On account of these properties, the CCO must be defined as
the time master.
The time message is accepted by both the workstation and the gateway. The gateway be-
comes the time master in the DigiNet S; the Freelance 2000 system is therefore time-
synchronized by the CCO.
If there are several CCOs in the system, it is necessary to ensure that only one station sends
time synchronization messages or that all synchronization messages run with identical times,
as otherwise the gateway accepts the new time with each synchronization message and
‘jumps’ accordingly.
59
3.7 Commissioning the time synchronization
Time zone and summertime
In all PCs in the Freelance 2000 system, select the correct time zone and check the Automati-
cally adjust clock for daylight saving changes checkbox in Windows NT Control panel under
Date/Time. The summertime table of Windows NT is used for all displays on the PCs.
Up to version 3.2:
However, the summertime table must also be entered on the DigiTool PC using the ‘DigiTool
Configure’ tool. The Use Daylight Saving Time checkbox must also be checked in this dialog.
This summertime table is loaded on the process station and used by the function blocks for lo-
cal time-summertime conversion. It is loaded only in connection with the Load / Whole station
load process.
On the DigiVis PCs, the use of summertime must be activated using the DigiVis Configure tool;
check the Use Daylight Saving Time checkbox under Daylight Saving Time.
As from version 3.3:
The setting of the time zone and the use of summertime is carried out for the whole project at
the project tree node CONF. The Windows NT summertime table is used for all displays.
Time synchronization on the PCs
Time synchronization must be activated on all Freelance 2000 PCs. This is set either in con-
nection with setup or using the ‘DigiTool Configure’ or DigiVis Configure tool. Under Time Syn-
chronization, set Enable Time Synchronization.
Time synchronization within a Freelance 2000 system
To active time synchronization within a Freelance 2000 system, the time must have been set at
least once. In the commissioning of DigiTool, select Options / Set system time... in the project
tree. The Use Daylight Saving Time checkbox must also be checked in this dialog.
60
4 Redundancy behavior of the gateway
4.1 Redundancy toggle, error detection
During undisturbed operation, both network connections of both redundancy partners are cycli-
cally monitored. For data exchange between primary and secondary the DigiNet S link is used.
If the gateway is reconfigured with DigiTool or Maestro UX, data are also adjusted via the
DigiNet S connection.
A complete failure of a CPU is detected within 1 s. In other terms, failure of the primary triggers
the redundancy toggle within 1 s and the message Prim/Sec-Toggle by primary failure is
sent to Maestro UX; in case of a failure of the secondary, the message Secondary failure is
sent to Maestro UX within this same period of time.
The period it takes to detect a power fail depends upon the network check. Network check is
carried out every 15 seconds, i.e. a defective network can be detected within 30 seconds.
As long as at least one network connection works between primary and secondary, detected
errors are communicated to the redundancy partner. Redundancy toggle is carried out if an im-
provement of the overall state can be expected.
Redundancy adjustment between primary and secondary is carried out via the DigiNet S con-
nection, i.e. if the DigiNet S connection is disturbed there is no redundancy. If the redundancy
between primary and secondary has been reestablished, the secondary will be newly booted
by the primary and adjusted to the updated data.
As long as a gateway CPU is not booted, the information whether this CPU has been last used
as primary or secondary of the gateway will be retained. As far as possible, always the initial
primary should therefore be first repaired in order to avoid the redundancy toggle. The later re-
paired secondary then can be booted and adjusted by the primary, if required.
An error detected on the secondary is transferred to the primary; the primary then generates a
message to Maestro UX concerning the error state.
A primary error is at first transferred to the secondary. The secondary checks whether the
overall state can be improved by a redundancy toggle. The primary (the "old" or - in case a
toggle took place, the "new" primary) sends an error message and an eventually implemented
redundancy toggle to Maestro UX.
Once the error state has been remedied, the initially generated message to Maestro UX will be
signaled as being inactive.
61
4.2 Redundancy state
The gateway state is displayed during commissioning in DigiTool in the project tree and the pa-
rameter mask of the gateway resource (gateway variable xxx.RedState).
sync Variable value = 3

Correct operation of primary and secondary, data are adjusted.
The O net link may be disturbed as this connection does not influence the
redundancy state.
A disturbed O net connection is visualized by a message on Maestro UX.
not sync Variable value = 2

Primary and secondary present, data are not adjusted.
Occurs only as transition state during booting and adjusting of the
secondary.
no secondary
Variable value = 1
Primary cannot reach secondary via DigiNet S, i.e. no redundancy any
more.
As soon as the secondary can be again addressed by the primary, the
secondary is booted and data are adjusted.
Depending upon the earlier state of the redundancy, the primary will gen-
erate a message to Maestro UX:
Secondary not found (secondary was never found, booting and adjust-
ing not possible),
Secondary not reachable after boot (secondary was not found any
more after booting) or
Secondary failure (redundancy was established but secondary then
failed).
62
no redundancy
Variable value = 0
A redundant gateway was configured in the project tree. During commis-
sioning mode of DigiTool a connection to the IP address of this gateway
station is established. There a gateway with a non redundant configura-
tion is found.
This state only exists the time the station is not loaded, i.e. as long as the
configuration in DigiTool and in the gateway station do not match.
The inverse case - a non redundant gateway station was configured in the
project tree, a redundant resource exists - cannot be seen in the project
tree.
The link DigiTool and gateway is established if with the configured IP ad-
dress the primary CPU is found. With Load / Whole station the secondary
passes to the boot loader, i.e. the CPU exists but does not impair the rest
of the system. In the system display or in the hardware manager this
module can be seen as being present but not configured.
If the configured IP address points to a secondary CPU no connection
can be established. In this case it is not possible to load a redundant con-
figuration with a not redundant configuration. (If necessary a redundancy
toggle must be done before.)
Redundancy error
Variable value = 128
With this error message a redundant process station signals that, for ex-
ample, redundancy adjustment is not possible because of an overload.
This message should not occur for the gateway. In case such a state oc-
curs for the gateway, the service personnel has to be informed.
63
4.3 System messages from the gateway to Maestro UX
As from version 3.3, messages are generated from a gateway resource and displayed on
Maestro UX. These messages are not available in DigiVis.
Message text Msg. Cause for the message Remedy

Prio.
GWY Messages lost S1 More messages have been gener- Eliminate the cause for the
from process station ated in the process station than can big volume of arising mes-
„xxx“ be buffered in the gateway. The sages. After a disconnec-
stated process station ("xxx"= tion, an overview over the
PS<Resld> could not store all mes- outstanding messages is
sages. reestablished.
GWY Connection S1 Communication with a process sta- Check network connection

lost to process station has been interrupted. „xxx“ = between gateway and pro-
tion „xxx“ PS<ResId>„ cess station..
GWY boot cause: S1 The CPU module watchdog has trig- Contact your competent
Watchdog gered a cold start. service personnel.
GWY boot cause: S1 The reset switch has triggered a cold Not required, normal op-
Cold start by reset start of the CPU module. eration.
switch
Reset switch pressed for more than
5 s.
GWY boot cause: S1 A fatal software error occurred on Contact your competent
Software error the CPU module. service personnel.
GWY boot cause: S1 An operation (in DigiTool) has trig- Not required, normal op-
Bootstrap by opera- gered a bootstrap on the CPU mod- eration.
tor ule.
Initialization by op- gered an initialization on the gate- eration.
erator way station.
Cold start by opera- gered a cold start on the CPU mod- eration.
tor ule.
GWY boot cause: S1 A warm start has been triggered by Not required, normal op-
Warm start by reset the reset switch on the CPU module. eration.
switch
Reset switch pressed for less than
5s.
64

Prio.
GWY boot cause: S1 A warm start has been triggered on Not required, normal op-
Warm start by op- the CPU module by an operation. eration
erator Not possible with V 3.3 as Digi-
Tool does not feature a warm start
button.
GWY boot cause: S1 A critical software error has triggered Contact your competent
Warm start/critical a warm start on the CPU module. service personnel.
error
GWY boot cause: S1 A fatal software error occurred on Contact your competent
CPU fault detected the CPU module. service personnel.
GWY cold start / S1 The safety functions in case of a Reestablish the power
Power fail power fail could not be implemented. supply.
Sys.time set at S1 The system time of the gateway has Not required, normal op-
"xxxx" been altered by an operation (in eration.
DigiTool), "xxxx" states the initial (lo-
cal) time.
GWY software error S1 A fatal error occurred on the CPU Contact your competent
"xxxx" module, "xxxx"states the error iden- service personnel.
tification.
GWY warm start S1 The CPU module was restarted after Normal operation, eventu-
down time "xxxx" a power fail and a warm start was ally check the power sup-
carried out. "xxxx" states the time of ply.
power fail.
GWY Red: No S1 The DigiNet S connection of a re- Check the DigiNet S con-
DigiNet S connection dundancy partner is disturbed. If the nections of the two gate-
primary was concerned, the mes- way CPU modules.
sage "Prim/Sec-Toggle by network
error" appears. Subsequently to the
error in DigiNet S the message
"Secondary not found" is output.
GWY Red: No O net S1 The O net connection of a redun- Check the O net connec-
connection dancy partner is disturbed. If the tions of the two gateway
primary was concerned, the mes- CPU modules.
sage ‘Prim/Sec-Toggle by network
error' appears.
GWY radio clock S1 A radio clock connected to the gate- Check the radio clock
failed way failed. and/or the connection.
65

Prio.
Battery low of CPU S2 The battery of the CPU module is Replace or insert a battery.
module low or not inserted.
Battery low of link S2 The battery of the link module is low Replace or insert a bat-
module or not inserted. tery.
CPU module of high S2 The temperature of the CPU module Reduce the ambient tem-
temperature is over 70 °C. perature.
The ambient temperature is higher

than 50 °C.
Secondary not found S1 The redundancy partner was not Check whether the secon-
found. No redundancy possible. dary CPU exists and the
redundancy link is correct.
Secondary not S1 The redundancy partner has been Check whether the secon-
reachable after boot booted but cannot be reached after- dary CPU could not termi-
wards. No redundancy possible. nate starting of the operat-
ing system.
Secondary failure S1 Redundancy was present. The re- Check the functional capa-
dundancy partner failed. bilities of the CPU module.
This message also ap-
pears in case of a defective
redundancy link..
Prim/Sec toggle by S1 Redundancy toggle caused by pri- Replace defective CPU or

primary failure mary CPU failure. search for other causes.
Prim/Sec toggle by S1 Redundancy toggle by activation of Not required, normal op-

toggle switch the toggle switch on the primary eration.
CPU.
Prim/Sec toggle by S1 Redundancy toggle by activation of Not required, normal op-

toggle button the toggle button in DigiTool. eration.
Prim/Sec toggle by S1 Redundancy toggle by operation in Not required, normal op-

test menu the test menu via the diagnostic in- eration.
terface.
Prim/Sec toggle by S1 Redundancy toggle by identification Check the network con-

network error of an error in the network connec- nection of the CPU mod-
tion. Acc. to a previous message, an ule, especially the connec-
error occurred in the DigiNet S or in tion of the actual secon-
the O net. dary CPU..
66

Prio.
First adjustment not S1 During data adjustment on the CPU Contact your competent
finished modules an internal error occurred service personnel.
on the secondary CPU.
Object error, first S1 The user program could not be com- Do not load the user pro-
adjustment not pos- pletely loaded. gram with ’Load selected
sible objects’. Update project
data using ’Load whole
station’ or at least using
’Load changed objects’.
67
5 Appendix: Mapping of Freelance 2000 function block classes
In part, several Freelance 2000 function block classes are mapped to one Maestro UX class for
data type reduction in Maestro UX.
Maestro UX Assigned Remarks

class Freelance 2000 class
CSDPB CSTBY, CSTWO, Constant function blocks for bit-string data types BYTE,
CSTDW WORD, DWORD)
CSDDT CSTDT Constant function block for DT
CSDTIME CSTTI Constant function block for TIME
CSDCBOOL CSTBO Constant function block for BOOL
CSDREAL CSTRE Constant function block for REAL
CSDINT CSTIN, CSTUI, CSTDI, Constant function blocks for integer data types INT, UINT,
CSTUD DINT, UDINT
CSDTOUCH TOUCH Touch button
CSDFAC FAC_D Frequency analog converter
CSDBOOL M_BOUT Binary output
CSDCTP CT_P Pulse counter
CSDCTUD CTUD Up/down counter
CSDCTT CTT Time counter
CSDCTLT CT_LT Time - meter
CSDMONOF MONO_F Monoflop
CSDTON TON Timer, switch-on delay
CSDTOF TOF Timer, switch-off delay
CSDTONOF TONOF Timer, switch-on/off delay
CSDTIMER TIMER Timer with external time input
CSDCR C_CR Continuous ratio controller
CSDSR C_SR Ratio step controller
CSDCS C_CS Continuous standard controller
CSDCU C_CU Continuous universal controller
CSDSS C_SS Standard step controller
CSDSU C_SU Universal step controller
CSDOS C_OS Standard two-position controller
CSDOU C_OU Universal two-position controller
CSDPS C_PS Standard three-position controller
CSDPU C_PU Universal three-position controller
CSDCTANA CT_ANA Counter with analog input
CSDCANA C_ANA Set point controller
SCDAITR AI_TR Analog input transformation
SCDAITRT AI_TRT Analog input transformation, transient
SCDAOTR AO_TR Analog output transformation
CSDTS TS Time scheduler
CSDDOS DOS, DOS_A Dosing circuit
CSDIDF1 IDF_1 Individual drive function for unidirectional units
68
Maestro UX Assigned Remarks

class Freelance 2000 class
CSDIDF2 IDF_2 Individual drive function for bi-directional units
CSDIDFA IDF_A Individual drive function for actuators
CSDDOSE DOS_E Extended dosing circuit
CSDMANA M_ANA Analog monitoring
CSDMBOOL M_BIN Binary monitoring
CSDMBAV M_BAV Binary monitoring of antivalency
CSDMOD MODM_R8C, Messages for Modbus master function blocks
MODM_R16C, Messages for Send and Receive function blocks
MODM_W1C, Messages for telecontrol function blocks
MODM_W8C,
MODM_W16C,
MODM_R1R,
MODM_R8R,
MODM_R16R,
MODM_W1R,
MODM_W8R,
MODM_W16R,
MODM_LBT,
SR_USEND,
SR_URECV,
FWK_S_MELD,
FWK_S_MWERT,
FWK_S_ZWERT,
FWK_S_SWERT,
FWK_S_BEFEHL
CSDTASK Task of the Freelance 2000 process station
CSDVBOOL Freelance 2000 variables of data type BOOL
CSDVINT Freelance 2000 variables of integer data types INT, UINT,
DINT, UDINT
CSDVREAL Freelance 2000 variables of data type REAL
CSDVTIME Freelance 2000 variables of data type TIME
CSDVDT Freelance 2000 variables of data type DT
CSDVPB Freelance 2000 variables of bit-string data types BYTE,
WORD, DWORD
CSDVSTRING Freelance 2000 variables of data types STR8, STR16,
STR32, STR64, STR128, STR256
CSDGWY Visualization of data from the Freelance 2000 gateway
69
6 Appendix: Examples for project changes
6.1 Add or delete a tag or a variable
Configuration in DigiTool
Enter a new function block or a new variable to the project configuration and define access
rights for this function block or variable via the gateway station in the tag or variable list
or
delete a function block or a variable in the project configuration
or
change access rights for a function block or a variable via the gateway station in the tag or
variable list
or
move a program in the project tree containing a function block or a variable linked via a gate-
way station.
Check the project
Commissioning in DigiTool
→ Load changed objects to the process station.

Effect on Maestro UX:
There is a version conflict between process station and gateway station. All data are still
updated in Maestro UX; all operator actions from Maestro UX are rejected in the gateway
station.
→ Load changed objects to the gateway station.
During load process the connection between the gateway station and Maestro UX is in-
terrupted. Once the data structure has been recreated in the gateway station, the con-
nection is reestablished and all data are updated in Maestro UX. The version conflict
between process and gateway station no longer exists, all operator actions are again
possible.
The time of interruption depends upon the number of tags and variables known to the
gateway. If 1000 tags and variables are linked via the gateway station, reconfiguration in
the gateway takes some 5 seconds, i.e. the connection to Maestro UX is interrupted for
approx. 5 seconds.
70
Maestro UX
The new object needs to be configured in the COL (central object list).
Alternative A:
I) recreate the PLCOpen file from DigiTool
II) transfer the PLCOpen file to Maestro UX
III) convert the PLCOpen file into an OBL file
IV) reload the OBL file to the COL using the system dialog
or
load the tag in question to the COL via entries in a terminal window (see Section 1.5.12,
Reconfiguration of data relevant to Maestro UX )
Alternative B:
I) create the object via the on-line configuration dialog in Maestro UX.
If a function block was deleted or the gateway access rights of a function block were deleted,
the object in question has to be deleted "manually" in the COL.
6.2 Reconfiguration of a tag
Change a parameter of an existing tag provided by the gateway station. Check the project.
→ Load changed objects to the process station.

There is a version conflict between process station and gateway station. All data are still
updated in Maestro UX; all operator actions from Maestro UX are rejected in the gateway
station.
→ Load changed objects to the gateway station.
The version conflict between process and gateway station no longer exists, all operator
actions are again possible.
71
Maestro UX:
All following actions depend upon the changed parameter:

a) the parameter only exists in the process station, e.g. controller parameter Kp:
→ no further workstation operations are required.
b) the parameter exists in the workstation, e.g. operability of an alarm

→ the object in question has to be updated in the COL (central object list):
Alternative A:
I) recreate the PLCOpen file from DigiTool
II) transfer the PLCOpen file to Maestro UX
III) convert the PLCOpen file in an OBL file
IV) reload the OBL file using the system dialog to the COL
or
Reload the tag in question to the COL via entries in a terminal window (see Section
1.5.12, Reconfiguration of data relevant to Maestro UX )
Alternative B:
reconfigure the object in question in Maestro UX using the on-line configuration dialog.
72
6.3 Changing gateway data
Change name, resource-Id or IP address of a gateway station.

Check the project .
→ Load changed objects to the gateway station

During the load process all gateway station connections with Maestro UX and with the process
stations are interrupted. Once the data structure of the gateway station has been recreated, the
connections are again established.
Maestro UX
The effects on Maestro UX depend upon the changes made.
If DigiNet S and O net are operated in one network, the DigiNet S IP address is identical to the
O net IP address; configuration modification has to be carried out in the same way for Maestro
UX. If the two networks are separated, the DigiNet S address is without significance for Maes-
tro UX.
The gateway name is without significance for data communication. In order to convert a
PLCOpen file, the gateway name and the IP address are evaluated. Any adjustment depends
upon the Maestro UX version and the gateway hardware.
Maestro UX does not know the resource-ID; after a change, no adjustment in the workstation
is required.
73
Index
A
Archiving 53
C
Commissioning 36
Configuration of a gateway 25
Conversion program 37
D
DCP 02 gateway 8
DCP 10 gateway 9
DigiBatch 53
F
Faceplate
Display of Messages 45
Layout 46
Operation 46
Operator panel 46
Size 45
Faceplates 45
Function block classes
available on Maestro UX 45
G
Gateway
Configuration 25
DCP 02 8
DCP 10 9
Project tree 25
Graphic display 49
Group display 49
H
Hints 52
Horn 53
L
Loading gateway from Maestro UX 41
Loading times 43
75
M
Messages 50
O
Objects in COL 37
Overview display 50
P
PLCOpen file 37
Project change 43
Project data of the DigiVis station 38
R
Read/Write access 34
Reading values 21
Reconfiguration on Maestro UX 40
S
Sequential function chart 48
Software packages 24
T
Tag names 32
Text conversion 39
Time synchronization via gateway 54
Time synchronization with DCP 02 55
Time synchronization with DCP 10 60
Time synchronization within Freelance 2000 54
Time synchronization within O net 54
Transferring project data 37
U
User-defined function blocks 53
V
Variable names 32
W
Writing values 23
76
42/37-4451 US 01.00 Subject to technical changes without notice.
ABB Automation Products GmbH ABB Automation Products ABB Automation Products
Regional Center Germany Regional Center Sweden Regional Center Americas
Industriestr. 28 Finnslätten 29801 Euclid Avenue
D-65760 Eschborn, S-721 67 Västerås, Sweden Wickliffe, Ohio, USA 440 92
Tel: +49 (0) 6196 800-0 Phone: +46 (0) 21 34 20 00 Phone: +1 (440) 585-8500
Fax: +49 (0) 6196 800-1119 Fax: +46 (0) 21 13 78 45 Fax: +1 (440) 585-8756
http://www.abb.de/automation http://www.abb.com/se http://www.abb.com

Maestro

Uploaded by

Document Information

Original Title

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

Maestro

Uploaded by

Copyright:

Available Formats

Freelance 2000

Coupling Freelance 2000 - Maestro UX

Please send your suggestions to:

Product Management Dept., DEAPR/LMS-Hannover, Fax: +49 (0)511 6782 701

1 Coupling Freelance 2000 - Maestro UX.................................................................. 7

2 Display of Freelance 2000 data on Maestro UX................................................... 40

2.2.1.4 Operator panel ......................................................................................................... 41

3 Time synchronization ............................................................................................ 50

4 Redundancy behavior of the gateway.................................................................. 61

5 Appendix: Mapping of Freelance 2000 function block classes ......................... 68

6 Appendix: Examples for project changes ........................................................... 70

1 Coupling Freelance 2000 - Maestro UX

To link Freelance 2000 to a Maestro UX system, an additional CPU module is to be inserted as

1.1.1 Structure of a network with DCP 02 as the gateway

1.1.2 Structure of a network with DCP 10 as the gateway

1.1.3 Structure of a network with two DCP 10 as the redundant gateway

a) Redundant gateway with DigiNet S and O net not separated

b) Redundant gateway with DigiNet S and O net separated

1.1.4 Hardware versions

1.2 Installing the Ethernet connections

1.2.1 Installing the CPU module address via the encoder

1.2.2 Free configuration of Ethernet interfaces

1.2.3 DCP 10 gateway with DigiNet S and O net not separated

1.2.4 DCP 10 gateway with DigiNet S and O net separated

This command is necessary after each reboot of the workstation.

Carry out these settings for both redundancy partners.

1.2.6 Redundant DCP 10 gateway with DigiNet S and O net separated

It is not necessary to define a default router in the gateway;

This command is necessary after each reboot of the workstation.

1.3 Data throughput

1.3.1 Reading values

Overview of the data throughput when reading values

0DHVWUR8; 1000 values/s

20000 inquiries at any one time

> 5000 values/s

10000 updates at any one time

2500 values/s per D-PS

1.3.2 Writing values

1.3.3 Messages to Maestro UX

1.4 Software packages

1.5.1 Creating the gateway station in the project tree

1.5.2 Configuration of a gateway station

Name any gateway name, max. 4 characters

After selection of ACCESS RIGHTS... the following dialog is displayed:

The configuration write permission is only effective if the checkbox Read

Memory These figures affect the memory mapping in the gateway.

Max. no. of connections

A maximum of 10 Maestro UX-Workstations can be linked to a gateway.

1.5.3 Gateway station in the hardware structure

1.5.4 Configuration of the process stations

1.5.5 Names of tags and variables

1.5.6 Specification of the data available via the gateway

1.5.8 Preparing project data for transfer to an external system

1.5.9 Transfer of the PLCOpen file to the Maestro UX system

/usr/contronic/appl/dgw/upload must always be used as the target directory when transfer-

1.5.10 Conversion of the PLCOpen file into Maestro UX data

After the conversion, error messages should be traced using

It is possible to show a describing text to the error number:

1.5.10.1 Project data of the DigiVis station

All settings concerning these items must be reconfigured on Maestro UX.

1.5.10.2 Conversion of texts by the converter

1.5.11 Display of Freelance 2000 data on Maestro UX

1.5.12 Reconfiguration of data relevant to Maestro UX