Beruflich Dokumente
Kultur Dokumente
Table of contents
1 Introduction........................................................................................................................................... 5
1.1 Learning objectives................................................................................................................. 5
1.2 Safety notices and symbols....................................................................................................6
2 Installation and registration.................................................................................................................. 7
2.1 Installation wizard....................................................................................................................7
2.2 Automation Studio licensing................................................................................................... 9
3 Your first project................................................................................................................................. 10
4 Automation Studio.............................................................................................................................. 11
4.1 Basic concept of Automation Studio.....................................................................................11
4.2 "Coffee machine" sample project..........................................................................................12
4.3 Automation Studio help system............................................................................................ 14
4.4 The workspace......................................................................................................................16
5 Software, hardware and configurations............................................................................................. 22
5.1 Software management in the Logical View.......................................................................... 22
5.2 Hardware organization - Physical View and System Designer.............................................22
5.3 Organizing configurations in the Configuration View............................................................ 23
5.4 Assignment of programs - Software configuration................................................................24
6 Configuring the hardware...................................................................................................................27
6.1 Testing in simulation mode...................................................................................................29
6.2 Adding I/O modules from the Hardware Catalog..................................................................31
6.3 Mapping process variables to I/O channels......................................................................... 32
6.4 Editing an I/O configuration.................................................................................................. 33
6.5 Configuring network interfaces............................................................................................. 34
6.6 Build the project.................................................................................................................... 35
7 Initial installation of the controller...................................................................................................... 36
7.1 Connecting to the target system...........................................................................................37
7.2 Transfer Automation Runtime............................................................................................... 40
7.3 Project installation................................................................................................................. 42
7.4 Offline installation via data storage device........................................................................... 44
8 Programming...................................................................................................................................... 48
8.1 Programming languages....................................................................................................... 48
8.2 Initialization and cyclic subroutines.......................................................................................48
8.3 Variables and data types...................................................................................................... 49
8.4 Creating an application......................................................................................................... 51
8.5 Import, export and team functions........................................................................................52
9 Updates and licenses.........................................................................................................................54
9.1 Hardware and software upgrade.......................................................................................... 54
9.2 Technology Guarding............................................................................................................55
10 Summary.......................................................................................................................................... 56
1 Introduction........................................................................................................................................... 5
1.1 Learning objectives................................................................................................................. 5
1.2 Safety notices and symbols....................................................................................................6
2 Installation and registration.................................................................................................................. 7
2.1 Installation wizard....................................................................................................................7
2.2 Automation Studio licensing................................................................................................... 9
3 Your first project................................................................................................................................. 10
4 Automation Studio.............................................................................................................................. 11
4.1 Basic concept of Automation Studio.....................................................................................11
4.2 "Coffee machine" sample project..........................................................................................12
4.3 Automation Studio help system............................................................................................ 14
4.4 The workspace......................................................................................................................16
5 Software, hardware and configurations............................................................................................. 22
5.1 Software management in the Logical View.......................................................................... 22
5.2 Hardware organization - Physical View and System Designer.............................................22
5.3 Organizing configurations in the Configuration View............................................................ 23
5.4 Assignment of programs - Software configuration................................................................24
6 Configuring the hardware...................................................................................................................27
6.1 Testing in simulation mode...................................................................................................29
6.2 Adding I/O modules from the Hardware Catalog..................................................................31
6.3 Mapping process variables to I/O channels......................................................................... 32
6.4 Editing an I/O configuration.................................................................................................. 33
6.5 Configuring network interfaces............................................................................................. 34
6.6 Build the project.................................................................................................................... 35
7 Initial installation of the controller...................................................................................................... 36
7.1 Connecting to the target system...........................................................................................37
7.2 Transfer Automation Runtime............................................................................................... 40
7.3 Project installation................................................................................................................. 42
7.4 Offline installation via data storage device........................................................................... 44
8 Programming...................................................................................................................................... 48
8.1 Programming languages....................................................................................................... 48
8.2 Initialization and cyclic subroutines.......................................................................................48
8.3 Variables and data types...................................................................................................... 49
8.4 Creating an application......................................................................................................... 51
8.5 Import, export and team functions........................................................................................52
9 Updates and licenses.........................................................................................................................54
9.1 Hardware and software upgrade.......................................................................................... 54
9.2 Technology Guarding............................................................................................................55
10 Summary.......................................................................................................................................... 56
1 Introduction
Automation Studio is the project development environment used specifically for B&R automation com-
ponents. This includes controllers, motion control components, safety modules and HMI applications.
Clearly organized project structuring options and the ability to manage multiple configurations ensure
that teams can work together efficiently and all machine variants can be represented in a single project.
Users are able to choose from a wide range of programming languages, diagnostic tools and editors
to assist them at every stage of engineering. Standard libraries provided by B&R and the integrated
IEC programming languages allow for a highly efficient workflow. Extensive simulation options enable
applications to be configured and tested independently of the hardware.
Figure 1: Automation Studio: one engineering tool for the machine's entire lifecycle
This training module uses simple exercises to demonstrate the wide range of tools available in Automa-
tion Studio. In addition, it will frequently refer to the extensive Automation Studio help system, an invalu-
able reference for completing the exercises in this training module.
You will learn how to create and configure projects in Automation Studio.
You will learn how to develop small programs and declare process variables.
You will learn how to navigate the Automation Studio help system.
You will learn how to set up hardware configurations and use the simulation features in Au-
tomation Studio.
You will learn the steps to follow in order to commission a B&R controller.
You will learn how to use the Automation Studio user interface and the various editors avail-
able.
You will learn about the options for configuring modules with Automation Studio's hardware
management features.
Danger: Disregarding these safety guidelines and notices can result in severe injury, death or
substantial damage to equipment.
Warning: Disregarding these safety guidelines and notices can result in severe injury or sub-
stantial damage to equipment.
Caution: Disregarding these safety guidelines and notices can result in injury or damage to
equipment. This information is important for preventing errors.
Help: References additional documentation (help system, data sheets, user's manuals)
Automation Studio is installed automatically when the Automation Studio DVD is inserted into the com-
puter's DVD drive. It is also possible to start the installation manually by running the Install.exe file. Once
Automation Studio has been installed, it needs to be registered.
The installation wizard guides the user through the installation process. After selecting the language for
installation, a number of installation options are available. These include viewing version information,
calling system requirements, etc.
Figure 2: Automation Studio installation: Selecting the Figure 3: Automation Studio installation: Installation options
installation language and version information
When Automation Studio is started for the first time, the Automation Studio start page is displayed.
From the start page, you can create a new project or open an existing one.
It also includes the "Getting started" section for users to learn more about working with Automation
Studio. The start page can be opened at any time by selecting <Help> / <Show start page> from the
main menu; it is also displayed after a project is closed.
The full range of functions are available in Automation Studio for 30 business days after instal-
lation. After this time, the program is locked until the software is registered.
The licensing window also appears when you open SafeDESIGNER. Here you should enter
the serial number from the Automation Studio license agreement.
In this section you will use the Automation Studio help system as a reference to create a new project,
transfer it to Automation Runtime Simulation and test it using Automation Studio.
1) Click on the How do I create a control project? link on the start page.
The help system is a useful aid for creating a new project, designing a program and then trans-
ferring the project to the Automation Runtime Simulation where it can be tested. Some of the el-
ements of Automation Studio have already been introduced during the course of this first project.
The next few sections will provide additional information about the structure of an Automation
Studio project with the help of an sample project.
The language of the help system can be set by selecting <Tools> / <Options> from the main
menu (English or German).
4 Automation Studio
This section will use an sample project to explain a bit more about Automation Studio and the structure
of projects.
In an Automation Studio project, the software is structured in the Logical View. The machine structure
and machine functions determine what the structure looks like. This direct relationship between the
application and the machine makes the structure of the software intuitive and easy to navigate.
Completed software components are assigned to their respective configurations in the Configuration
View. For each configuration, there is a corresponding hardware configuration that is managed in the
Physical View.
Automation Studio allows automation projects to be structured modularly to support distributed develop-
ment approaches and make working in project teams more efficient.
Automation Studio comes with a number of sample projects. This training module will use the "CoffeeMa-
chine" sample project to explain the Automation Studio environment and some of the many different
functions available. The "CoffeeMachine" sample project can be used to illustrate the path from an initial
design concept to a full representation of the software and hardware components in Automation Studio.
1) Open the Automation Studio sample project from the start page.
After following these steps, the "CoffeeMachine" sample project will be unzipped and opened
in Automation Studio.
The software structure is structured according to the coffee preparation process. Each individual function
is represented in Automation Studio by clearly structuring the design and programming aspects of the
project.
This image shows the Logical
View. Each folder (called a pack-
age in Automation Studio) repre-
sents a logical section of the soft-
ware structure.
The Automation Studio help system is an invaluable resource throughout the development, configura-
tion and commissioning of a project. It serves as a reference guide for using Automation Studio and
its editors, creating programs or HMI applications, configuring drives and much more. In addition, the
Automation Studio help system contains access to all B&R hardware documentation. When you install
new hardware and software upgrades, the Automation Studio help system is expanded to include the
necessary documentation (see"Hardware and software upgrade" on page 54)
"Help favorites" make it possible to manage and store helpful pages within an personalized structure.
You can save the help favorites to a separate file. In this way, help favorites can be managed as needed
and even passed on to other people.
Managing favorites
1) Saving and opening
Help favorites can be saved to a file by se-
lecting "Save" or "Save as" from the File
menu. Any newly added entires are saved
automatically.
2) List of help favorites
The help favorites are managed in a tree
structure. Entries can be moved and re-
named. Clicking on one of the entries will
open the corresponding help page.
3) Toolbar
Figure 17: Managing help favorites The "Help contents" and "Help favorites"
buttons in the toolbar switch between the
Favorites view and the navigation tree in
the Automation Studio help system. The
navigation tree remains synchronized if a
favorite is selected in the Favorites view.
Automation Studio is divided into several different areas, each with a specific function.
When a project is opened in Automation Studio, the various section windows are all docked to the main
program window. Clicking on a window's title bar and dragging it away from the main window will undock
it so that it can be moved to another location.
To create more space on the screen, for example when working with
visual programming editors, the Project Explorer and all other dock-
able windows can be hidden automatically. Clicking on the pin icon Figure 20: Use the pin symbol to dock or
in the title bar of the Project Explorer or any of the other dockable hide windows
windows will toggle the auto-hide function.
The default window layout in Automation Studio can be restored by selecting <Window / Reset
window layout> from the main menu.
4.4.3 Workbooks
Workbook mode presents a clear way of displaying open windows and a convenient way to switch be-
tween them. Windows can be overlapping or arranged above or next to one another.
If several editors are open at the same time, each one is displayed in a separate workbook. For an
overview of all open workbooks, click on the drop-down symbol on the right side of the title bar.
Toolbox window
The Toolbox window provides access to program and configuration elements, programming functions
or hardware modules depending on the editor that is selected.
Figure 24: Toolbox - Ladder Diagram: Figure 25: Toolbox - Hardware Catalog: Figure 26: Toolbox - Object Catalog:
Programming functions, commands, Hardware modules and infrastructure Programs and configuration files
functions and function blocks components
The SmartEdit feature combines a range of intelligent functions that provide additional support in Au-
tomation Studio editors.
Auto-complete
Pressing <CTRL> + <SPACE> will automatically complete the
entry of some terms. Characters already entered serve as a filter.
This feature is supported by the following elements:
Figure 27: SmartEdit - Code completion Variable names, structure elements, constants and enu-
merators
Function names and function blocks
Automatic declaration
Depending on preference, automatic declaration of new variables
can be helpful. In SmartEdit settings, you can make numerous cus-
tom adjustments to the editors. Open the configuration window by
selecting <Tools> / <Options> from the menu. On the "SmartEdit"
tab, activate the setting for automatically declaring variables.
Code snippets
The <CTRL> + <q>, <k> keyboard shortcut can be
used to insert code snippets into a program. Code
snippets are ready-made bits of source code that
can be managed by the user in the code snippet
manager.
Programming \ Editors
General operation \ SmartEdit
General operation \ SmartEdit \ Code snippets
Text editors
Table editors
General operation \ Dialog boxes for input support \ Automatic declaration of vari-
ables
The Project Explorer is a central element of the Automation Studio interface. The Project Explorer con-
tains the Logical View for organizing software, the Physical View for organizing hardware and the Con-
figuration View for managing configurations to represent multiple machine variants in a single project.
The hardware required for the machine can be managed either in a hierarchical view or in a graphical
view.
Automation Studio's hardware management features are used to perform the following
tasks:
Insert and configure hardware modules
Map variables to I/O data points
Configure fieldbus modules and interfaces
Physical View
The Physical View is a hierarchical topology overview of the config-
ured hardware.
When you create a project or a new system configuration you se-
lect a CPU. Then the required hardware modules are added into the
topology from the Toolbox.
The configuration of individual hardware components and interfaces is opened in Physical View via the
shortcut menu. This allows you to make module-specific settings, network configurations and configu-
ration settings for system behavior.
System Designer
System Designer provides a visual representation of the Physical View. In System Designer, the control
components can be arranged just as they would be used in the actual machine. I/O modules are added
and removed in the same way as in the Physical View (see 6.2 "Adding I/O modules from the Hardware
Catalog"). The two views are synchronized with each other.
Figure 32: Open System Designer via the toolbar of the Physical View. Add hardware modules from the Toolbox.
The System Designer editor allows objects to be laid out automatically. The ability to add text
boxes makes it possible to group hardware components and assign them to a control cabinet,
for example.
When you double-click on a configuration to activate it, the corresponding hardware assigned is dis-
played in the Physical View as well as in the System Designer. Only one configuration can be [Active]
at a time.
The following configuration elements are managed, among others, in the Configuration View.
The software elements to be transferred to the target system for the active configuration are assigned
in the software configuration.
There are several different ways to assign software to the software configuration:
"Automatic assignment when creating a program" on page 25
"Adding existing programs manually" on page 25
Figure 34: Open the software configuration from the controller's shortcut menu.
The execution order and priority of programs can be changed by moving the corresponding
objects as necessary directly in the software configuration.
If a new hardware configuration is added to the Configuration View, the software elements must be
manually assigned to the software configuration.
Open the software configuration, then select the Logical View in Project Explorer. An object can then be
assigned by moving it from the Logical View to the desired position in the software configuration.
This procedure makes it easy to assign individually selected programs to a particular configuration.
Entire packages from the Logical View can be added to the software configuration, even if they
contain a mixture of programs and other object types. To do this, drag the selected package to
the highest position in the software configuration.
Double-click on an entry in the software configuration to open the Logical View with the corre-
sponding entry automatically selected.
The ability to manage multiple configurations in one project allows you to work with the different variants
of a given machine type all in the same project. The may differ in terms of software scope and/or the
exact hardware used.
The Logical View is shown in the image on the left. This view is used to manage libraries and programs.
The image on the right shows a schematic representation of the different variants of a machine. In
Automation Studio, each variant is represented by a corresponding configuration. The configurations
differ from each other in terms of the hardware used and the software packages that are assigned to
them.
Table 2: Different machine variants can be created by assigning software packages to them.
Project management
Als Basis fr dieses Kapitel dient das in Kapitel 3 "Your first project" on page 10 erstellte Projekt.
This project already contains a configuration based on the "Automation Runtime Simulation" and a Lad-
der Diagram program with two variables.
This task consists of multiple subtasks that will be explained in detail in the next few sections.
Add a new configuration using the toolbox. To do this, open the Configuration View and insert a new
configuration via drag-and-drop or by double-clicking. Then select the desired controller in the wizard.
Figure 39: Select the desired controller using the filter in the
wizard.
We have already created the "LampTest" program using the Getting Started section in the Automation
Studio help system.
The Automation Studio status bar indicates when a CPU simulation is running.
After the configuration has been transferred to ARsim, all the diagnostics tools1 become avail-
able. Program sequences can be tested and further developed without having to connect to the
machine. To transfer a project to the real controller, simulation mode is ended via the menu.
You can tell whether the configuration in is running in simulation mode using the traffic light
icon in the status bar.
Figure 44: Automation Studio status bar - Connection to the real hardware
1 Further information on the topic of diagnostics can be found in the training module "TM223 - Automation
Studio Diagnostics" and in the Automation Studio help system.
When using an X20 system, I/O modules can be added directly to the X2X Link interface.
I/O modules can be added either in the Physical View or in the System Designer. I/O modules can be
dragged and dropped from the Hardware Catalog to the desired position.
Selecting an interface (X2X, POWERLINK, etc.) in the control system filters the Hardware Cat-
alog to show only the ones that match this interface. The results list can be filtered by setting
further filter categories.
It is also possible to search for a particular module by entering all or part of its model number.
Communication \ X2X
Communication \ POWERLINK
I/O mapping is another way of referring to the assignment of variables being used in the control program
to a module's I/O channels.
Variables are allocated to an I/O channel by selecting <Open> / <I/O Mapping> in the I/O mapping editor
that is opened using the shortcut menu in the relevant module, or by double-clicking on the relevant I/
O module.
All B&R I/O modules have configuration options. The I/O configuration can be used to configure I/O
modules without having to do any programming.
The I/O configuration can only be opened by selecting <Open> / <I/O configuration> from the main
menu or <I/O configuration> from the respective I/O module's shortcut menu.
The data sheet for the selected I/O module can be accessed directly from the Physical View. To
do this, select the I/O module in the Physical View. Press the <F1> key to open the Automation
Studio help system. The data sheet for the selected module appears. The data sheet contains
technical information, configuration options, connection examples and details of the LED status
indicators.
Automation Studio requires a network connection in order to communicate with the controller. PC and
controller must therefore be on the same subnet.
If the PC is already running on a network, the settings should be noted before changing them.
Please contact your network administrator for detailed information about the integration
of devices into an existing network.
The network properties can be opened using the shortcut menu for the desired Ethernet interface for the
controller. It is then possible to configure the parameters for the network interface as needed.
Automation software \ Getting started \ Creating programs in Automation Studio \ X20 CPU
example project
Configuring Ethernet settings on the target system
Configuring Ethernet settings on the PC
Configuring the online connection
Programming \ Building and transferring projects \ Establishing a connection to the target system
Communication \ Ethernet \ AR configuration \ Interface configuration
Once a program has been completed, it must first be built before it can be transferred to the target system.
Rebuild a configuration
When you recompile (rebuild) a configuration (by pressing <CTRL>+<F7>), all the software objects in
the active configuration are created again, even if their source files have not changed since the last time
they were compiled.
To install the controller, it is necessary to transfer Automation Runtime (operating system), the system
components and the application project. Whether installation is performed online or offline depends on
the target system. Systems with integrated flash memory are delivered with preinstalled default Automa-
tion Runtime. This guarantees that a connection with Automation Studio is established and online instal-
lation can be carried out. Offline installation is available for systems with CompactFlash and CFast cards.
Instructions on installation and commissioning can be found in the data sheet of the respective
controller in section "System Flash programming".
Online installation
In BOOT mode, first the Automation Runtime version configured in the project is installed and then the
Automation Studio project is transferred in its entirety.
The following steps are necessary:
"Connection using "Browse for target systems"" on page 38
"Transfer Automation Runtime" on page 40
"Project installation" on page 42
Offline installation
For offline installation, Automation Runtime, system components and the application project are copied
to the CompactFlash or CFast card. A USB card reader is required for this procedure.
The following steps are necessary:
"Offline installation" on page 45
"Connection using "Browse for target systems"" on page 38
"Project installation" on page 42
If an operating system was already installed, then the step "Transfer Automation Runtime" is
not necessary. The transfer of the project can be begun immediately once connection has been
established.
Programming \ Building and transferring projects \ Establishing a connection to the target sys-
tem \ Ethernet connections
Project management \ Project installation
The previous section explained how to configure the network interface settings for the network controller.
These settings only have to be configured once before a connection can be made. The "Browse for
target systems" function allows you to assign temporary IP parameters for the controller.
There are two ways to establish a connection:
"Connection using "Browse for target systems"" on page 38
"Establish connection via manual configuration" on page 39
The configuration dialog box for online connection is opened by selecting <Online / Settings> from the
main menu.
Clicking on one of the texts in the overview image will open a description of the relevant settings
for the Automation Studio project and the PC.
Additional information can also be found in the following sections of the help system:
Programming \ Building and transferring projects \ Establishing a connection to the target sys-
tem
Communication \ Ethernet \ Network settings
Communication \ Ethernet \ Online communication
Communication \ Ethernet \ FAQ
Clicking on the "Browse" icon in the toolbar activates the search function for the network. This will open
up a second pane in the main window. The results of the network search will then appear a few seconds
later. If the CPU could be identified on the network, it will be shown in the list of results. The connection
is then established by right-clicking on the CPU and selecting "Connect" from its shortcut menu.
Programming \ Building and transferring projects \ Establishing a connection to the target sys-
tem \ Ethernet connections
Browse for targets
Target system search \ Temporary IP configuration
Target systems can be distinguished between based on the MAC address, node numbers, host-
names and serial numbers.
Manual configuration
If it is not possible to browse the network, for example if SNMP broadcasts are blocked, it is possible
to set up an online connection manually.
Programming \ Building and transferring projects \ Establishing a connection to the target sys-
tem \ Ethernet connections
As soon as a connection exists between the PC and the controller, its status will be shown in
the Automation Studio status bar.
In BOOT mode, Automation Runtime can then be transferred to the controller.
Figure 54: An online connection to the controller has been established. The controller is in BOOT mode.
In RUN or SERVICE mode, the entire project can be transfered to the controller. Au-
tomation Studio diagnostic tools are available when there is an active online connec-
tion.
Figure 55: An online connection to the controller has been established. The controller is in RUN mode.
There is a wizard to assist you through the process of transferring Automation Runtime. It is recommend-
ed to select the option "Modules from the project scheme". This option includes the system settings from
the project in addition to Automation Runtime. As a requirement for this, the project must be compiled
in advance.
Figure 57: Transferring Automation Runtime: Transfer modules Figure 58: Transferring Automation Runtime: Progress
from the project scheme indicator
All target systems have the option of deliberately starting in BOOT mode. Depending on the
target system, this is done using a reset button, the mode selector switch or node number se-
lector switch. The reset button can be used to restart the system and change the operating
mode. The mode selected with a mode selector switch is applied after restarting. Further infor-
mation about the possible operating modes and actions can be found in the data sheet of the
respective target system.
Starting from default Runtime2 Browsing for target systems via SNMP3 is also supported for
SG4 systems with V3.06 and later.
1) Establish a connection to the controller via "Browse for target systems" function.
2) [optional] Put the target system into BOOT mode via the reset button, the mode selector switch or
node number selector switch.
3) Start Automation Runtime transfer via <Online> / <Services> / <Transfer Automation Runtime>
After Automation Runtime has been transferred, the controller is in RUN mode. Now, the entire
project can be transferred to the controller.
Figure 59: Automation Runtime transferred successfully. Connection established. The controller is in RUN mode.
2 The default Automation Runtime is a reduced variant of Automation Runtime which is preinstalled on all
controllers.For example, the default Automation Runtime boots from flash memory.
3 The Simple Network Management Protocol is a network protocol used to monitor and control devices on a
network from a central location (e.g. routers, servers, switches, printers, computers, etc.).
Initial transfer
An initial transfer is performed the first time a project is installed. During this, the target system is com-
pletely initialized. All data from any previous projects is removed. With an initial transfer, the entire project
including Automation Runtime is always transferred to the target system. The memory is partitioned,
formatted and the target system is restarted. RETAIN and permanent variables are deleted during an
initial transfer.
An initial transfer is performed under the following conditions:
The configuration ID of the the target system differs from the one defined in the project.
The configuration ID is established in the system configuration of the controller.
The partitioning of the target system doesn't match the partitioning required for the project.
The transfer takes place to a data storage device (see "Offline installation via data storage de-
vice" on page 44).
The user forces an initial transfer in the transfer settings.
4 With Automation Runtime C4.25 and later, the Automation Runtime version is transferred with the project,
included in the transfer module and automatically installed.
Update transfer
Automation Studio will generally first attempt an update transfer on the target system. If an update trans-
fer is not possible (the configuration ID has changed, for example), then an initial transfer is performed
instead. During an update transfer, only data that has been changed is transferred to the target system.
Depending on the transfer settings, the Init and Exit programs are executed or values are received from
process variables.
Figure 63: Transfer dialog box: Project differences require a Figure 64: Transfer dialog box: no differences were identified
restart between the project and the target system.
In addition to the textual notes, notification icons are shown in the transfer dialog box. These
can be used to open tooltips with detailed information about the differences between the project
and the target system configuration.
Figure 65: Additional information from notification icons in the transfer dialog box
The target system is now up-to-date. The function of the program "LampTest" can now be tested
directly on the target system.
Figure 66: Ladder Diagram program "LampTest" in monitor mode with powerflow
3) Compare the states in Automation Studio with the LED status indicators
Figure 67:
CompactFlash
Project management \ Project installation \ Operation \Transfer dialog box \ Offline installation
The USB flash drive can be selected in the configuration dialog box. It is also possible to decide if
Automation Runtime should be updated along with the application. A version check prevents the target
system from being updated unintentionally.
Pressing the "Start" button copies the remote install structure to the USB flash drive. The system can
now be updated using the newly set-up USB flash drive.
Diagnostics and service \ Service tool \ Runtime Utility Center \ Creating a list / data medium
\ Remote install structure creation
8 Programming
A program is a POU (program organization unit, as defined in the IEC 61131 standard) that possesses
the ability to directly access all global variables, functions and function blocks.
A variety of different programming languages are available in Automation Studio for creating programs.
It is also possible to combine multiple programming languages within a single project.
All text-based programming languages in Automation Studio use the same editor. As a result, diagnostic
tools always have the same features and are always operated in the same way. This high degree of
uniformity simplifies workflows and increases productivity.
Function blocks included in B&R standard libraries can be called and used in all of the pro-
gramming languages.
Programming \ Programs
Task initialization
When the cyclic system is started, each task executes its initialization subroutine. This Init program can
contain program code which calculates and describes variable values.
Cyclic subroutine
The program's cyclic subroutine starts once the task's initialization subroutine has completed. Variables
which are described there retain their values until they are overwritten or until the system is restarted.
Exit subroutine
A task's exit program is only called when the task is uninstalled (deleted). If resources (e.g. memory,
interfaces, etc.) were requested in the initialization or cyclic subroutine, then these resources must be
freed up properly.
It is also possible for the user to create user-defined data types that
are based on basic data types. In Automation Studio, these user-
defined data types (or derived data types) are declared in a file with
the extension .typ.
Figure 77: Data type declaration file
In the Logical View, you can structure the software as required using packages. This facilitates the simple
encapsulation of data and functionality.
This structure determines the scope and visibility of the declared variables and data types. This allows
you to define variables the appropriate "logical" place in the project.
Automation Studio controls the scope of variables using the position of the .var file.
6 Program organization units are defined in the IEC 61131-3 standard and referred to as POUs. POUs corre-
spond to programs functions and function blocks into which the control project is divided.
A variable always has a data type as one of its properties. The variable declaration can contain additional
properties for the variable.
Constants are variables whose values cannot be changed while a program is being executed. A constant
is assigned its initial value when the software is created (Value column).
RETAIN variables are protected in buffered memory so that they can be reloaded after a system restart
(warm restart). Unlike RETAIN variables, permanent variables are also protected against a cold restart.
In order for variables to be stored in the permanent memory area, they have to be defined as RETAIN
and Global in the variable declaration window.
Depending on the target system used, a buffer battery is used in the CPU to retain the data. More detailed
information is listed in the data sheet of the respective device.
The standard libraries delivered with Automation Studio make it possible for users to access many dif-
ferent system functions. They allow, for example, physical interfaces to be freely programmed, reports
to be used in a targeted manner and hardware to be configured with a high level of flexibility.
It is also possible to import numerous sample programs, which demonstrate how the libraries can be
used. These encompass executable program code for the controller or the simulation.
With solutions that are installed via the Automation Studio upgrade dialog box, you receive complete
project templates with process control, simulation and visualization. These are imported into the project
by the user and adjusted as required.
Programming
Libraries
Examples
mapp Technology unites configuration and programming. Functionality is implemented in the application
program using standard libraries. In addition, mapp provides configuration interfaces that allow the func-
tionality of mapp components to be influenced independently of where they are used in the application
software.
Working in a team means that the various responsibilities have to be divided up between team members.
Automation Studio includes functions designed to help teams work more efficiently:
Passing on project data via export with small file sizes
Applying project data via import
Working with source control systems
Project management
Automation Studio project \ Project import/export
Distributed development
Using source control systems
Completed software components can be exported and imported so that they can be shared or reused in
other projects. Exports are performed individually for each package in the Logical View.
If a package includes dependencies to libraries, they can be entered in the properties of the package.
These properties are checked when importing a package so that any required libraries are added au-
tomatically.
Programming \ Examples
Figure 82: Adding samples from the
toolbox
In addition to the offline installation function and opening System Diagnostics Manager, Automation
Studio's "Tools" menu offers other functions as well. This section briefly explains the function of the
Upgrades dialog box as well as Technology Guarding.
The ability to upgrade components makes it possible to update hardware and motion libraries as well as
upgrade to newer versions of Visual Components or Automation Runtime.
Upgrading components online is handled directly in Automation Studio.
The upgrade process is started by selecting <Tools> / <Upgrades> from the menu. A dialog box opens,
showing available upgrades.
10 Summary
Automation Studio is more than just a programming tool. It provides support for the user throughout the
entire lifecycle of a machine from the initial concept all the way to the finished project.
Whether it's being able to clearly structure software to match the physical parts of the machine, working
with different configurations to design multiple variants of the same machine or working together concur-
rently in a team on the same project Automation Studio always has the right tools for the job at hand.
Figure 85: Automation Studio: one engineering tool for the machine's entire lifecycle
Automation Studio is an invaluable resource for programmers, service technicians and maintenance
engineers for every stage of a machine's lifecycle.
At the Automation Academy, you'll develop the skills you need in no time!
Our seminars make it possible for you to improve your knowledge in the field of automation engineering.
SEM410 Integrated motion control* If you don't happen to find a seminar on our website that suits your
SEM441 Motion control: Electronic gears and cams** needs, keep in mind that we also offer customized seminars that we
SEM480 Hydraulics** can set up in coordination with your sales representatives:
SEM1110 Axis groups and path-controlled movements** SEM099 Individual training day