APROL Engineering Basics

TM801
 Prerequisites

Training modules: TM800 – APROL System Concept

Software: APROL 2.2 or higher

Automation Runtime 2.66 or higher

SuSE LINUX 8.2 or higher

Hardware: 1 Control Computer, 1x Controller

2 TM801 APROL Engineering Basics

Table of contents

1. INTRODUCTION 4
1.1 Seminar objective 5

2. THE CAEMANAGER 6
2.1 General functions of the CaeManagers 6
2.2 General information for operating the CaeManager 7

3. CAEMANAGER HELP 10

4. CAEMANAGER WORKING AREAS 11

5. DESIGNER MANAGEMENT IN APROL 12

5.1 Designer profiles (general user profiles) 13
5.2 Creating designer profiles 13
5.3 Creating an account 19
5.4 Assigning a profile 21
5.5 Project profiles 22

6. THE IDENTIFICATION SYSTEM IN APROL 27

6.1 Naming conventions 28
6.2 Managing identification systems 31

7. SUMMARY 36

8. APPENDIX 37
8.1 Objectives checklist (a few on-topic questions) 37
8.2 Solutions to the objectives checklist 37

APROL Engineering Basics TM801 3

Introduction

1. INTRODUCTION
APROL engineering can be divided into general and project-specific
sections. The general part is known as basic engineering. In the best cases,
basic engineering only has to be carried out once and is used to configured
the following.

• The design management system determines which company

employees can work with APROL and which rights they have to
work with the applications.
• An identification system is used to determine the manner in which
the system components are named. These should match the names
of the electro-technical documentation. Because of this background,
every company usually uses an identification system tailored to their
needs.

Fig. 1 Project planning

4 TM801 APROL Engineering Basics

 Introduction

1.1 Objectives
After this seminar, you will be able to manage a project correctly. This
refers to the distribution of responsibilities for the project engineering as
well as structuring the system. System administration can now be handled
as needed.

Fig. 2 Overview

APROL Engineering Basics TM801 5

The CaeManager

2. THE CAEMANAGER

2.1 General functions of the CaeManager

The CaeManager is the central program of the Engineering System. It can
be used to perform almost all engineering and configuration tasks
necessary for creating a process control system. The CaeManager makes it
possible for a team to work with a process control system.

It is a structured configuration system for concurrent engineering based

on function block language conforming to IEC 1131-3.

We will now take a look at the terms above:

Concurrent engineering Engineering teams work simultaneously on

the same project without impeding each
other and without having to resort to
complicated data exchange between one
another.
All data are stored in a single database.
Access to this data is managed centrally by a
database server which prevents competing
access to the same data (read-only access to
the "competitor").
Only commissioning functions like Compile,
Generate, and Download may not overlap.

Structured configuration Configuration data is divided into project-

specific reusable parts.
Function blocks in the Standard library,
identification systems, and information for
user management can be reused.
Project-specific parts are stored locally in the
projects (specifically for each respective task).
Project-specific data include the hardware
configuration, function charts, process
diagrams, etc.

6 TM801 APROL Engineering Basics

 The CaeManager

Function block language conforming to IEC 1131-3

Knowledge of specific programming

languages is not necessary to configure the
process control system.
Interconnecting function blocks with a
graphics editor is sufficient to configure both
the logic of the control level and the control
system components (alarm system, graphic
display of plant data, etc.).

2.2 General information for operating the CaeManager

After starting the CaeManager and logging in as a valid user, the following
standard window appears on the desktop:

Menu area

Configuration and
engineering area

Information area
Fig. 3 CaeManager

APROL Engineering Basics TM801 7

The CaeManager

Menu area
All engineering and configuration work can be done using these menus. In
addition, a few menu items are present for file operations and editing
buttons. The icons are from the Windows world and should be self-evident.

Navigation area
The structure of engineering data you create is displayed here in the form
of a directory structure. You're able to navigate inside of your engineering
data while editing it and work with the various elements presented here.

Configuration area
This work area is used to generate and edit objects necessary when you
are creating your process control system. These include function plans,
process diagrams, function blocks, etc.

If you haven't clicked on a particular process control system object to edit it,
then this area will contain the contents of the directory selected on the left.
Double-clicking on the object opens it to be edited.

8 TM801 APROL Engineering Basics

 The CaeManager

The following objects can be created and edited in the configuration area.

Symbol Object type Description

Directory for an additional level in the project
Directory
tree.
The hardware systems of the Controller such as
Controller
terminal stations, remote I/O devices, etc.
The hardware systems of the process control
Control computer level such as the runtime server, operating
station, gateway server, etc.
Function plans for the controller as well as the
runtime system or control computer

Function chart CYCLIC

INIT
EXIT
Text information can be saved simultaneously in
the accompanying comment pages for every
Commentary page
object (control computer, controller, function
plan, etc.)
Process diagrams for the operating station or
Process diagram
operating systems
Equipment Equipment such as motors, pumps, valves, etc.
Parameter set Parameter templates for the equipment listed in
template this template
Process diagrams for the operator station or
Static process diagram
operator systems

Information area
This area shows information about the object name (version), editing mode,
current user, date, and time.

APROL Engineering Basics TM801 9

CaeManager Help

3. CAEMANAGER HELP
All manuals that are currently available are installed as HTML files on the
control computers. These documents can be accessed at any time with the
"Help / Product Documentation" menu item or using KDE menus.

A starting index page branches off to the individual manuals.

Fig. 4 Help index page

10 TM801 APROL Engineering Basics

 CaeManager Working areas

4. CAEMANAGER WORKING AREAS

The CaeManager is modularly divided according to working areas. The
Designer Management and Identification System working areas are
components of basic engineering. The Project design working area is
subdivided into the Libraries and Projects areas and belongs to project
engineering. The different work areas can be selected with the "Working
area" menu item.

Fig. 5 Designer Management in the Working area menu

APROL Engineering Basics TM801 11

Designer Management in APROL

5. DESIGNER MANAGEMENT IN APROL

Designers include every person who works with APROL, regardless of
what they are doing. For example, these can be planners (engineers),
service technicians, or system operators. Designer Management is used to
create user profiles for different areas of responsibility and qualifications.
These user profiles are then assigned to different people.

Note:

Changes only need to be made here if new employees are hired by the
company, employees leave the company, or employees should receive
different rights due to the tasks they need to fulfill.

Note:

The advantage of this procedure is that employees can be quickly

assigned to one or more user profiles, without having to assign every
single user right at a time.

The integrated Designer Management system is used to coordinate and

divide the planned work while supporting the make-up of the project team.

Note:

In the Engineering System, each designer should "know everything"

(have read access). However, many tasks can only be taken care of by
employees that are actually qualified to do so. These employees then
receive write authorization in their areas of responsibility. Other
employees are responsible for the editing of the project or individual
parts of it and are granted administrative rights as a result.

12 TM801 APROL Engineering Basics

 Designer Management in APROL

5.1 Designer profiles (general user profiles)

Designer profiles affect every project since they determine the
authorization levels for using Engineering System applications in APROL,
therefore also affecting the engineering of each individual project.

A designer profile defines certain access rights for the Engineering

System's work areas. APROL can manage many of these designer
profiles.

Note:

It would be pointless to create a separate profile for every subsequent

user (designer) since this would virtually eliminate the advantage of the
profile creation mechanism. Designer profiles should be created
skillfully so that planners (designers) are assigned to individual profiles
in such a way that they receive the rights they need to carry out their
work.

5.2 Creating designer profiles

The following describes the procedure for creating a designer profile in the
Designer Management system.

Fig. 6 Designer / Edit profile menu item

First, select the "Designer / Edit profile" menu item.

APROL Engineering Basics TM801 13

Designer Management in APROL

This opens up the "Edit designer profile" window.

Click on the "Create" button.

Fig. 7 Edit designer profile

Fig. 8 New designer profile

The following dialog box then appears requesting the name of the designer
profile. This name should be unique and have something to do with the
profiles and qualifications in order to avoid confusion when engineering
the project.

Note:

Names should/must be as clear and unique as possible in a system.

After a unique name has been entered, another dialog box opens where
the actual designer profile is defined.

14 TM801 APROL Engineering Basics

 Designer Management in APROL

Appropriate authorization can now be assigned to the work areas provided.

Access Right Abb. Description

Only provides read access to a working area / object
Read R
(read).
Only provides write access to a working area / project part
Write W
(write).
In some working areas, object or project part version can
be validated by confirmation.

Confirm C This right allows versions of functioning objects to be

highlighted/identified. The version management system
can be used to enable whether confirmed versions can be
deleted or not!
In all working areas, a created version of a project part
must be activated in order for it to be compiled and used
Activate A in a project at runtime.
This right allows the designer to supply a project part
version to the entire project (activate).
This right allows the designer to load libraries to the
Download D controller or to load the project or parts of it to the process
control system in the engineering project (download).

APROL Engineering Basics TM801 15

Designer Management in APROL

The rights are assigned by clicking on the respective field. Double-clicking

opens a list of possible rights combinations and the desired combination
can be selected.

Fig. 9 Defining the designer profile

Importance of the working areas

Engineering library: Creating and editing libraries and the

function blocks contained therein.
(Libraries work area)

Note:

Although creating these types of libraries is not a part of this training,

you might make a note that libraries created by users can be password-
protected if desired. Library objects can then be used, but how they are
programmed cannot be viewed. In this way, particular know-how can
be protected.

16 TM801 APROL Engineering Basics

 Designer Management in APROL

Database administration: Database editing. The designer who

wants to update the Engineering
System must have R and W access.
(Libraries work area)

Note:

As an innovative product, APROL depends on constant improvement

and updates. New functions are constantly being added and provided to
customers in the form of updates. These versions are downward-
compatible and can be implemented without much effort.

Database translation Database translation. (Libraries work

area)

Designer Management Creating and editing the Designer

Management system. Designer
Management working area

Engineering Identification System

Users with rights in this work area can

view / configure identification systems.
(Identification System work area)

APROL Engineering Basics TM801 17

Designer Management in APROL

Operator management Creating and editing the Operator

Management system for a project on
the runtime server. (Libraries work area)

Note:

At the beginning of the User Management section it was stated that an

advantage of the profile system is that users who didn't engineer the
project can expand the category of online users (operators). These
users must have rights in this work area (OnlineUserManager).

Project engineering Creating and editing projects and the

parts contained therein. (Libraries work
area)

5.2.1 Editing a designer profile

First, select the "Designer / Edit profile" menu item. This opens up the
"Edit designer profile" window. Select the desired designer profile with the
mouse. Click on the "Open" button.

Editing takes place as explained above. Changes to user rights are applied
once the dialog box is closed.

18 TM801 APROL Engineering Basics

 Designer Management in APROL

5.2.2 Deleting a designer profile

First, select the "Designer / Edit profile" menu item. This opens up the
"Edit designer profile" window. Select the desired desinger profile with the
mouse. Click on the "Delete" button.

Note:

In general, objects with references cannot be deleted before all of the

references are deleted.

Important:

Designer profiles which have already been assigned to designers or

operators cannot be deleted.

5.3 Creating an account

This menu makes it possible to create designers and users.

Note:

It makes sense to enter all employees that will work with APROL as
designers. The users entered can be assigned a user profile or the
assignment can be changed at any time.

APROL Engineering Basics TM801 19

Designer Management in APROL

Creating a designer

The "Designer account" window opens up when you select the "Designer /
Create account" menu item.

Fig. 10 Designer account

Appropriate information should be entered into the Name, First name,

Login, and Password fields. This information is then entered into the
engineering database by clicking on the "Accept" button. The newly
created user then appears in the display box on the left.

Note:

In the dialog box for the LoginServer, you can log in by entering your
user name.

Deleting a designer

Planners appearing in the display box on the left in the "Designer Account"
dialog box can be deleted by selecting the respective name and then
clicking [Delete].

20 TM801 APROL Engineering Basics

 Designer Management in APROL

5.4 Assigning a profile

This menu item can be selected to assign configured designer profiles to
the designers you have created. This gives the designers the access rights
granted to the designer profiles. A designer can be assigned to any
number of profiles, and in some cases every configured profile. The access
rights build on one another.

Note:

Assigning a designer several designer profiles should be avoided by

configuring the designer profile in a sensible manner and should be
done in exceptional situations.

The "Assign designer profile" window opens up when you select the
"Designer / Assign profile" menu item. This dialog box allows you to select
a designer profile to which designers should then be assigned. Assignment
it done by selecting a designer profile in the "Open designer profile:<name
of designer profile>" dialog box.

Fig. 11 Assign designer profile

Once you have finished assigning profiles, the window can be closed with
"OK" or "Cancel" ("Cancel" discards any changes you have made).

APROL Engineering Basics TM801 21

Designer Management in APROL

5.5 Project profiles

The project profiles created using the "Project / Edit profile" govern access
to the tools used in the "Project" working area This allows a refined
structuring of access rights to individual functionalities in the CaeManager.
Creating a new project profile is done in the same way as creating a
designer profile.

A unique name is entered for the new project profile in the "Edit project
profile" dialog box.

Fig. 12 New project profile

Note:

The assignment can be changed at any time by a designer with the

respective rights. Within a group of designers, only one person and one
substitute should have administration rights for the designer profile and
designers if possible.

22 TM801 APROL Engineering Basics

 Designer Management in APROL

Access rights for the user profile to use the following tools can be assigned
in the "Definition of project profile: <name of designer profile>" dialog
box shown below.

Equipment: Creating and editing equipment (for

parameters – handling and recipes)

Function charts: Creating and editing function charts based on

function block language conforming to IEC
1131-3

Hardware configuration: Creating or arranging and processing the

process control system's hardware
configuration

Comment pages: Creating and editing comment pages for other

objects in the engineering system

Physical views: Creating and editing physical views (of a

physical view tree)

Note:

The physical view tree represents the configurator for a system. The
individual control system components are clearly identified in the
system, based on the rules defined for the identification system.

Operator management: Assignment of operators to the project-

specific user profiles created in the project

Note:

In the APROL runtime system and the corresponding user interfaces,

tools and buttons are provided that are not permitted to be used by any
user. The operating philosophy differs from one system to another,
therefore the required user profile is created specifically for the project.

APROL Engineering Basics TM801 23

Designer Management in APROL

Project profiles: Assigning designers to the project team

Note:

A designer with write rights in the project profiles is similar to an

administrator for the project. This task should only be given to the
project manager. This guarantees that only the work assigned to a
designer can be done by that designer.

Background pictures: Creating and editing operator templates,

dynamic image macros, and static process
diagrams

Master data: Defining and editing the project's master data

Plant parts: Creating and editing plant parts (for

parameters – handling and recipes)

Task management: This management refers to the CaeLoader

(distributing or downloading the engineering)
and the ControllerManager (special access to
the controller).

Process diagrams: Placing dynamic diagram elements on static

process diagrams.

24 TM801 APROL Engineering Basics

 Designer Management in APROL

The same access rights we learned with designer profiles are used here –
rights for reading, writing, confirming, activating, and downloading the
application.

Fig. 13 Configuring a project group

Important:

Project profiles are only used in specific projects. Consequently, they

can only be assigned inside of a project which has already been opened
for editing.

Note:

Even though the Design Management system may seem complicated, it

has many powerful features. Think carefully about how to define
profiles sensibly, especially for data used throughout multiple projects.
The more you work with the system, the more you will learn to
appreciate the advantages of this type of user management.

Important:

Without a feasibly configured Designer Management system, you

cannot work with the CaeManager!

APROL Engineering Basics TM801 25

Designer Management in APROL

Exercise 1:

Create a new designer profile.

Exercise 2:

Now create a designer using your first name and your last name as the
login (user name). Please use "aprol" as your password.
Assign this planner to the designer profile you have created.

Exercise 3:

Then create a project profile under "Project / Edit Profile" and assign all
access rights to it.

26 TM801 APROL Engineering Basics

 The Identification System in APROL

6. THE IDENTIFICATION SYSTEM IN APROL

This section will deal with naming conventions for defining the creation of
a project-specific physical view definition. Typically, hierarchical
identification systems are created which allow the system to be structured
according to geographic location. In addition, the identification system is
important in guaranteeing a fast and structured configuration process.

Note:

APROL consequently strives for reusability. In the identification

system working area, only naming conventions are created that can be
assigned to any projects.

The identification system working area is opened using the "Working area /
Identification system" menu item.

Fig. 14 Start identification system

In the identification system working area, the user is able to implement

any identification system used in a company for the physical view. A
hierarchical template is created where the individual levels can be defined
using regular expressions.

APROL Engineering Basics TM801 27

The Identification System in APROL

6.1 Naming conventions

The rules for "regular expressions" are used when creating the
identification system. A detailed description of these "regular expressions"
can also be found in the configuration manual. The identification system
itself is standardized according to DIN 6779.

This allows a defined interface between electrical engineering and process

control engineering.

6.1.1 Regular expressions

A regular expression describes character patterns using metalanguage.
The characters in this meta-language are a subset of the ASCII character
set. There are basic regular expressions and extended regular expressions,
which have an advanced range of functions.

We will only cover the most common expressions here to gain more
understanding of the examples.

! Description / Meaning
[] A character class. It consists of all of the characters inside the
brackets.
Special features: A hyphen, "-", represents a range of characters,
e.g. [A-Z] for all capital letters, [0-9] for all digits, etc.
{} Iteration operator:
Contains a number with an optional comma (before of after the
number) or two numbers separated by a comma. It applies to the
regular expression before it:
One number without comma {n} = previous expression occurs
exactly n times
One number with a preceding comma {,n} = same as {0,n}
One number with a comma following the number {n,} = same as
{n, }
Two numbers separated by a comma {n,m} = previous
expression occurs at least n times and a maximum of m times
Examples:
A{1,3} means that the letter "A" must appear between 1 and 3
times.
A{4} means that the letter "A" must appear exactly 4 times.
| Exclusive OR:
This allows very many different entries to be made.

28 TM801 APROL Engineering Basics

 The Identification System in APROL

! Description / Meaning
Example: Cow|Pig|Sheep is fulfilled if either the "Cow" expression,
the "Pig" expression, or the "Sheep" expression occurs.
() Grouping:
Regular expressions are grouped together to a new regular
expression (explicit parentheses).
Examples: (ab|cd)?ef is fulfilled by "abef", "cdef ", and "ef".
(ab)+ is fulfilled by "ab", "abab", "ababab", etc.
[: :] Named character classes:
[:alnum:], [:alpha:], [:cntrl:], [:digit:], [:graph:], [:lower:], [:print:],
[:punct:], [:space:], [:upper:], [:xdigit:]
Brackets are a part of the symbolic name of the named character
class.
Example:
[[:alnum:]] is the same as "[0-9A-Za-z]".

APROL Engineering Basics TM801 29

The Identification System in APROL

Level Description Formulation Separator

with regular for the
expression next level
Plant This level should record elements [A-Z] {3,} /
whose names should be coded with
at least three capital letters.
Example: REC, MARL
Buildin This level should record elements [A-Z] /
g whose name begins with a capital [[:alpha:]]
letter, followed by at least one more {1,} [0-9]
letter (small or capital), and ending {2,}
with at least a two-digit number
combination.
Example: G07, Building251
Room This level should record elements [A-Z] /
whose name begins with a capital [[:alpha:]]
letter, followed by at most three {0,3}[0-9]{3}
more letters (small or capital), and
ending with a three-digit number
combination.
Example: R125, Room007
Cabine This level should record elements [A-Z] [0-9] /
t whose name begins with a capital {3}
letter and ends with a 3-digit number
combination.
Example: P007
Rack This level should accept elements (PCC|PLC|P /
with names that begin with PCC, PLC CS) [0-9] {2}
or PCS and end with a 2-digit
character sequence. Example:
PCC10, PLC05
CPU This level should record elements (CPU) [0-9]
whose name begins with "CPU" and
ends with a single digit.
Example: CPU2

30 TM801 APROL Engineering Basics

 The Identification System in APROL

Note:

Correctly structuring an identification system and the corresponding

project-specific physical view is elementary for APROL functionality.
For this reason, the universal identification system shown above is part
of the standard delivery of APROL.

6.2 Managing identification systems

The existing identification systems are sorted into groups in an explorer
format in the Identification System working area. This makes it possible
e.g. to order the identification system by project or other criteria.

Fig. 15 Identification system working area

APROL Engineering Basics TM801 31

The Identification System in APROL

6.2.1 Creating an identification group

To create a new group, select the root item of the tree ("Identification
system") on the left side and then either use the "File / New" menu item or
right-click in the right-hand window and select "New". If the dialog box
which appears, you must enter a name and a description for the new
identification system group.

Fig. 16 Creating an identification system group

6.2.2 Creating a new identification system

To create a new identification system, select the group where this should
take place. Then choose either the "File / New" menu item or right-click in
the right-hand window and select "New". In a project, this identification
system can be selected under this name to create a physical view.

Fig. 17 Creating an identification system

32 TM801 APROL Engineering Basics

 The Identification System in APROL

6.2.3 New level in the identification system

Open up the identification system you have created. In the same way as
listed above ("File / New" menu), you can now define the levels of the
identification system.

First the new "level" needs a number. In the example shown previously,
"Company" has Level 1, "Building" has Level 2 and so on up to "CPU" on
Level 6. APROL offers the next unused level. If you change the level
numbers and use a level that has already been assigned, the level will be
overwritten with the new definition after confirming a message box.

"Name" is the designation that is needed to describe the new level in the
project. This name is always specified in the physical view tree along with
the actual expression.

A "regular expression" definition is given under "Expression".

The "Separator" is used to separate the identifiers of the individual layers

from one another. The last level is created without a separator.

To change an identification level, select it (by double-clicking, for example)

and change the desired parameters. The right-mouse button can be used
for functions like "Delete", "Copy", and "Paste".

APROL Engineering Basics TM801 33

The Identification System in APROL

6.2.4 Testing an expression

A label which is used later in the project should be entered underneath the
entry for the separator and checked for correctness with the "Test" button.

Fig. 18 Define and test level

Note:

If new levels should be added to an identification system, all other

levels that are above numerically / hierarchically must be offset
accordingly.
If an identification system is assigned to a project, then it can no longer
be changed. If names are defined for instances in a physical view tree,
then they most likely no longer match the definition after the changes
are made.

34 TM801 APROL Engineering Basics

 The Identification System in APROL

Important:

An identification system is absolutely necessary to create a process

control system project!

Exercise 4:

Create a new identification system or expand an existing one.

APROL Engineering Basics TM801 35

Summary

7. SUMMARY
What have we achieved so far?

The CaeManager, as the central engineering tool, is the core of the

engineering environment. Therefore, it's important to be knowledgeable of
the structure. The APROL help system should always be the first place
you look if problems occur.

The working areas are clearly defined, but you will mostly need the project
engineering area in the future. Ideally, the engineering user management
and identification system only need to be configured correctly one time to
allow simple and intuitive engineering.

Fig. 19 Project structuring

36 TM801 APROL Engineering Basics

 Appendix

8. APPENDIX

8.1 Objectives checklist (a few on-topic questions)

What working areas are included in the CaeManager?

What combinations are useful and logical for user management?

Why is an identification system needed?

Are the regular expressions clear and understandable?

8.2 Solutions to the objectives checklist

Please take note of the necessary additional information.

APROL Engineering Basics TM801 37

Appendix

Notes

38 TM801 APROL Engineering Basics

 Appendix

Overview of training modules

TM200 – B&R Company Presentation ** TM600 – The Basics of Visualization

TM201 – B&R Product Spectrum ** TM610 – The Basics of ASiV
TM210 – The Basics of Automation Studio TM630 – Visualization Programming Guide
TM211 – Automation Studio Online Communication TM640 – ASiV Alarm System
TM212 – Automation Target ** TM650 – ASiV Internationalization
TM213 – Automation Runtime TM660 – ASiV Remote
TM220 – The Service Technician on the Job * TM670 – ASiV Advanced
TM221 – Automation Components and Sources of Errors *
TM223 – Automation Studio Diagnostics TM700 - Automation Net PVI
TM230 – Structured Software Generation TM710 - PVI Communication
TM240 – Ladder Diagram (LAD) TM711 - PVI DLL Programming
TM243 – Sequential Function Chart (SFC) * TM712 - PVIServices
TM245 – Instruction List (IL) * TM730 - PVI OPC
TM246 – Structured Text (ST)
TM247 – Automation Basic (AB) * TM800 – APROL System Concept
TM248 – ANSI C TM801 – APROL Engineering Basics
TM250 – Memory Management and Data Storage TM810 – APROL Setup, Configuration and Recovery
TM260 – Automation Studio Libraries I TM811 – APROL Runtime System
TM812 – APROL Operator Management
TM400 – The Basics of Motion Control TM813 – APROL XML Queries and Audit Trail
TM402 – Dimensioning Motion Control Systems * TM830 – APROL Project Engineering
TM410 – The Basics of ASiM TM840 – APROL Parameter Management and Recipes
TM440 – ASiM Basic Functions TM850 – APROL Controller Configuration and INA
TM441 – ASiM Multi-Axis Functions TM860 – APROL Library Engineering
TM445 – ACOPOS ACP10 Software TM865 – APROL Library Guide Book
TM450 – ACOPOS Control Concept and Adjustment TM870 – APROL Python Programming *
TM460 – Starting up Motors * TM880 – APROL Report *

*) upon request
**) see Product Catalog

APROL Engineering Basics TM801 39

40
Appendix

TM801
Weblink

Internationalität
Kontakt (Headquarter)

Copyright – Bestellnummer

APROL Engineering Basics

Hinteres Deckblatt (auf durch 4 Teilbarer Seitenzahl)

TM801TRE.30-ENG
©06/2006 by B&R. All rights reserved.
All registered trademarks presented are the property of their respective
company. We reserve the right to make technical changes.