Software installation

Software installation

1
Software installation

1 Supported operating systems................................................................................. 2

2 Limitations for virtual machines............................................................................. 5

3 Automation Studio.................................................................................................... 5
3.1 System requirements...................................................................................................................................... 5
3.1.1 Automation Studio 4.7............................................................................................................................... 5
3.2 Installation....................................................................................................................................................... 6
3.2.1 Classic....................................................................................................................................................... 6
3.2.2 Adding software components.................................................................................................................... 6
3.3 Licensing......................................................................................................................................................... 7
3.3.1 Automation Studio..................................................................................................................................... 7
3.3.2 Automation Studio (Legacy).................................................................................................................... 11
3.4 Uninstalling.................................................................................................................................................... 13
3.5 Installation notes........................................................................................................................................... 13
3.5.1 Automation Help installer........................................................................................................................ 13
3.5.2 Automation Runtime installer.................................................................................................................. 14
3.5.3 Automation Studio installer......................................................................................................................15

4 PVI.............................................................................................................................17
4.1 System requirements.................................................................................................................................... 17
4.1.1 PVI 4.3 and later..................................................................................................................................... 17
4.2 Installation..................................................................................................................................................... 17
4.2.1 Adding software components.................................................................................................................. 18
4.3 Uninstalling PVI.............................................................................................................................................18
4.4 PVI installer................................................................................................................................................... 18

5 SafeDESIGNER........................................................................................................ 19
5.1 System requirements.................................................................................................................................... 19
5.1.1 SafeDESIGNER 4.3.................................................................................................................................19
5.1.2 SafeDESIGNER 4.2.................................................................................................................................20
5.2 Installation..................................................................................................................................................... 20
5.3 Licensing....................................................................................................................................................... 20
5.4 Uninstalling.................................................................................................................................................... 21
5.5 SafeDESIGNER installer...............................................................................................................................21

6 Automation Studio Target for Simulink................................................................21

6.1 System requirements.................................................................................................................................... 21
6.2 Installation..................................................................................................................................................... 21
6.3 Uninstalling.................................................................................................................................................... 25
6.4 Licensing....................................................................................................................................................... 26

1 Supported operating systems

Automation software components are supported by a wide range of operating systems. The following tables provide
an overview.
For information about using Automation Software on virtual machines, see Limitations for virtual machines.
For detailed information about system requirements and limitations, please click on the version.

2
 Software installation

Automation Studio (AS)

Windows Vista Windows 7
Version Windows XP Windows 8 Windows 10
32-bit 64-bit 32-bit 64-bit

<2.7

2.7

3.0.71

3.0.80

3.0.81

3.0.90

4.0

4.1

4.2

4.3

4.4

4.5

4.6

4.7

Table 1: Automation Studio

Automation Runtime Simulation (ARsim)

Version Windows XP Windows Vista Windows 7 Windows 8 Windows 10

2.93 - 2.95

2.96 - 4.06

4.08 - 4.40

4.41 or later

Table 2: Automation Runtime Simulation (ARsim)

Automation Runtime Windows (ARwin)

Windows 7 Windows 8 Windows 10
Version Windows XP Windows Vista Legacy
UEFI
32-bit 64-bit 32-bit 64-bit (32-bit)
(32-bit) / 64-bit)
/ 64-bit)

2.93 - 3.09

4.00 - 4.01

Table 3: Automation Runtime Windows (ARwin)

3
Software installation
Windows 7 Windows 8 Windows 10
Version Windows XP Windows Vista Legacy
UEFI
32-bit 64-bit 32-bit 64-bit (32-bit)
(32-bit) / 64-bit)
/ 64-bit)
1)

4.02 - 4.06

4.08 - 4.24

4.25 - 4.40

4.41 or later

Table 3: Automation Runtime Windows (ARwin)

1) V4.02 or later

VC Windows Terminal (VCWT)

Version Windows XP Windows Vista Windows 7 Windows 8 Windows 10

3.0.90.x

4.0.x

4.1.x

4.2.x

4.3.x

4.4.x or later

Table 4: VC Windows Terminal (VCWT)

Process Visualization Interface (PVI)

Version Windows XP Windows Vista Windows 7 Windows 8 Windows 10

<2.7

2.7

3.0.0

3.0.2

4.0 - 4.2

4.3 or later

Table 5: Process Visualization Interface (PVI)

SafeDESIGNER
Version Windows XP Windows Vista Windows 7 Windows 8 Windows 10

2.8x

2.9x

3.0.x

3.0.18

Table 6: SafeDESIGNER

4
 Software installation
Version Windows XP Windows Vista Windows 7 Windows 8 Windows 10

3.1.0

3.3.0

3.4.x

4.1.x

4.2.0

4.2.1 or lat-
erSafeDESIGNER 4.2

Table 6: SafeDESIGNER

FieldbusDESIGNER (FD)
Version Windows XP Windows Vista Windows 7 Windows 8 Windows 10

3.0.71

1) 1) 1) 1)

3.0.80

Table 7: FieldbusDESIGNER (FD)

1) 3.0.80.41 or later

2 Limitations for virtual machines

Operating automation software products on virtual machines has not been tested.
The following tables contain product versions tested with Microsoft Windows Virtual PC, however.

Automation Studio
Version Operating system Exceptions
2.x Windows 7 (32-bit and 64-bit) Installation and operation only on Windows Virtual PC in XP mode.
Up to 3.0.71 UP06 Windows 7 (32-bit) Installation and operation only on Windows Virtual PC in XP mode.
3.0.71 Windows 7 (64-bit) Installation and operation only on Windows Virtual PC in XP mode.
3.0.80 Windows 7 (64-bit) Installation and operation only on Windows Virtual PC in XP mode.

Automation Runtime simulation

PC-based Automation Runtime Simulation can be used on Windows Virtual PC in XP mode in Windows 7, but the
timing is not the same as in actual Windows XP.

FieldbusDESIGNER
For FieldbusDESIGNER, the same limitations and functions apply as for Automation Studio V3.0.71 and later.
Version Operating system Exceptions
Up to 3.0.71 UP06 Windows 7 (32-bit) Installation and operation only on Windows Virtual PC in XP mode.
3.0.71 Windows 7 (64-bit) Installation and operation only on Windows Virtual PC in XP mode.
3.0.80 Windows 7 (64-bit) Installation and operation only on Windows Virtual PC in XP mode.

3 Automation Studio
3.1 System requirements

This section contains the system requirements for Automation Studio as well as specifications regarding which
operating systems can be used with which versions. For information about using Automation Software on virtual
machines, see limitations for virtual machines.

3.1.1 Automation Studio 4.7

This section contains the system requirements for Automation Studio 4.7.

5
Software installation

Operating systems
• Windows 10 (32-bit and 64-bit)
• Windows 8 (32-bit and 64-bit)
• Windows 7 SP1 (32-bit and 64-bit)
• Windows Vista SP2 (32-bit and 64-bit)
Processor
• Minimum: Intel Core i3 or comparable
• Recommended: Intel Core i5 or comparable
RAM
• Minimum: 4 GB
• Recommended: 8 GB
Hard drive space
• Minimum: 10 GB
• Recommended: 15 GB
Screen resolution
• Minimum: 1024 x 768
• Recommended: 1920 x 1080
Browser
• Minimum: Windows Internet Explorer® 6.0
• Minimum: Windows Internet Explorer® 9.01)
• Recommended: Windows Internet Explorer® 11.01)
1) Applies to Automation Help.

Interface
• Ethernet, CAN or serial

3.2 Installation

3.2.1 Classic

Administrator rights are needed on Windows operating systems to install new software. If necessary,
contact your network administrator.

Installation steps
1. Insert the installation DVD into the computer's DVD-ROM drive.
2. If option "AutoPlay" is enabled, then the B&R Automation installation window will appear. If AutoPlay was not
enabled, file Install.exe from the root directory of the DVD installation must be started.
3. Select the desired installation language with the mouse.
4. In the window that appears, start the installation with Start installation.

If a current .NET framework or PVI version does not exist on the computer, they will be installed
during the setup process.

5. After confirming the licensing agreement and entering your user data, the installation dialog box for selecting
the type of installation will be displayed.
6. Choosing Classic installation will open the dialog box for selecting components.
If a component should not be installed, it can be deselected in the selection tree.
Clicking on the Next button continues the installation.
7. In the following dialog box, the installation directory can be changed by clicking on Browse.
8. Clicking on the Install button then installs Automation Studio on the computer.

3.2.2 Adding software components

Restart the installer and add individual components. In the selection dialog box, select and install the necessary
components.
6
 Software installation

3.3 Licensing

The following dialog box will be displayed on startup to select the Automation Studio license if Automation Studio
has not yet been licensed. It is possible to choose between Automation Studio and Automation Studio (Legacy).
• Automation Studio
This contains a new, easier procedure for licensing Automation Studio.
• Automation Studio (Legacy)
Existing licenses can continue to be used with this option.

A license must exist on every workstation running Automation Studio. Depending on the license, it is
limited to the workstation or can exist on a Technology Guard (dongle).

3.3.1 Automation Studio

Selecting option Automation Studio opens the product licensing window.

7
Software installation

There are various options for activating Automation Studio.

• Online activation with a valid license key
• Activating an evaluation license
• Licensing from the command line

Online activation
Enter the supplied B&R license key in the input field. Clicking button Activate will automatically license the B&R
Automation Studio version online over an existing Internet connection.

Evaluation license
The link in the dialog box directs to the B&R website. When selecting an evaluation license, an email is sent to the
specified address after the form has been filled out. This email contains a license key that can be activated in the
licensing dialog box. The remaining evaluation period is shown each time Automation Studio is started. After the
evaluation period expires, Automation Studio must be licensed again.

License manually (command line)

It is possible to perform licensing from the command line to avoid having to start Automation Studio. Use the
following command for licensing (uses the default paths for the Automation Studio installation):
C:\BrAutomation\AsTools\Technology Guarding\bin\BR.AS.License.UI.exe /LicenseKey:<License key>

This option requires an Internet connection and cannot be performed offline. Old B&R serial numbers
(11-digit string) are not supported.
For additional information about manual licensing, see the page Known problems.

Limitations when using Automation Studio

Depending on the license, some functions in Automation Studio may be locked or only partially available for use.
For an overview of licenses and their effects, see the B&R website.
Known problems when returning licenses.

3.3.1.1 Offline licensing

For offline licensing, it is necessary to transmit a request file to B&R; Automation Studio is then licensed using
an update file.

8
 Software installation

Licensing Automation Studio

1) Start the CodeMeter Control Center
Open the CodeMeter Control Center under Program / CodeMeter in the Windows Start menu. Alterna-
tively, enter CodeMeter Control Center in the Start menu's search bar.
2) Import the license container
If the license container Bernecker + Rainer Industrie Elektronik is not displayed, import the license
container by dragging and dropping it into the selection window. The license container file (B+R_lif.wbb)
is located in the Automation Studio installation directory under AsTools\Technology Guarding\Lif. (e.g.
C:\BrAutomation\AsTools\Technology Guarding\Lif)
3) Select the license container
Licensing can be handled directly on the PC or using a Technology Guard (B&R dongle).
Depending on the license purchased, select Bernecker + Rainer Industrie Elektronik or CmStick/C (B&R
dongle must be plugged into the PC).

4) Create the request file

Click on License activation to start the wizard. Follow the wizard to create a request file.

9
Software installation

In the next step, enter the location and name of the request file and create the request file with Apply.
End the wizard with Complete.

10
 Software installation

5) Send the request file to B&R

Send the request file and license number to B&R via email. Please contact the nearest B&R subsidiary.
6) Obtain the update file
As soon as the check is performed at B&R, an update file is sent back.
7) Copy the update file to the PC with Automation Studio
Using a removable storage device, copy the update file to the PC where Automation Studio should be
licensed.
8) Complete Automation Studio licensing
Double-clicking on the update file in the file explorer will license Automation Studio so that it can be used.
Alternatively, import the update file into CodeMeter using drag-and-drop. CodeMeter licenses Automation
Studio automatically.

3.3.2 Automation Studio (Legacy)

This licensing is only still available for compatibility reasons.

The following page describes how Automation Studio can be licensed using legacy licenses.
The following dialog box opens after selecting option Automation Studio (Legacy).
The provided B&R serial number must be entered in the first input field. Once a valid serial number is entered, all
of the other buttons will become active.

11
Software installation

License automatically (online)

Clicking on the License automatically (online) button will automatically license the Automation Studio version
online over an existing Internet connection. An error message is displayed if a connection cannot be established
to the B&R server.

License manually (offline)

Clicking button License manually (offline) opens the licensing dialog box. A licensing code can be requested by
selecting menu option Service / Software registration on the B&R website.

After entering the Sys-ID and pressing the Register button, you will receive an activation code that you can then
enter in the License code (Sec-ID) input field in the Automation Studio licensing dialog box.

12
 Software installation

If the correct code has been entered, click OK to complete the licensing process.
If a valid B&R serial number is not entered, close the dialog box with button License later. Automation Studio
remains unlicensed and cannot be used, however.

Limitations
The following licenses are no longer supported with legacy licensing.
• Fieldbus licenses
• Evaluation licenses

The option of licensing with legacy licenses is available for a limited time only and will be removed
from Automation Studio in later versions.

3.4 Uninstalling

If multiple versions of Automation Studio are installed on the same PC simultaneously, only the active
version can be uninstalled. If no versions are active, the Version Changer can be launched to activate
the one that should be uninstalled.
Start Automation Studio deinstallation via Windows Start menu - Programs / B&R Automation / Automation
Studio %Version% %Language% / Uninstall Automation Studio .

Multiple installations (AS 2.x only):

If there is still a B&R Automation Studio version present on the computer after another version has
been uninstalled, it must be enabled with the Version Changer.

3.5 Installation notes

3.5.1 Automation Help installer

Command line parameters can be used to influence, control or define preset values for all Automation Studio
installers.

13
Software installation

Overview of command line parameters for the Automation Help installer

These parameter names are case-sensitive. It is also important to specify the character preceding each
parameter correctly (e.g. - or /).
Parameter Explanation Comment Example
/Log Logger The entire path must be specified for /Log=C:\Temp\InstallationProcess.txt
the installation log file, including the file- or /Log
name. This file is not generated until the
installation is complete. While the in-
staller is running, this file does not exist.
Parameter /Log can be specified with-
out a path. The file is saved in the temp
directory (%temp%).
-RP Installation mode Only "reduced mode" is currently avail- /R=Y
able. It provides a simplified GUI. Dia-
log boxes with user interaction are hid-
den.
/S Installation mode This mode executes installation in the /S
background. A dialog box is not dis-
played.
-L Dialog box language 1033 for English, 1031 for German -L=1031: Dialog boxes in German
-L=1033: Dialog boxes in English
-G Destination path (global) Installation path for global settings -G="C:\BrAutomation"
-V Destination path (version) Installation path for version-specific -V="C:\BrAutomation\AS43"
settings

The following rules also apply:

• Do not use /S and -RP together.
• -G and -V must be used together.

Return value
0 = No error occurred during installation.
1 = Installation was aborted by the user.
2 = An error occurred during installation.

Command line parameters passed to the installer (e.g. /D or /Log) are not explicitly validated. An invalid parameter
therefore does not necessarily have to result in an error or exit code ≠ 0.
Batch file example for evaluating the exit code:
"AS4_AH_V4.3_Help_English.exe" -RP -G="C:\BrAutomation" -V="C:\BrAutomation\AS43"

"AS4_AH_V4.3_Help_German.exe" -RP -G="C:\BrAutomation" -V="C:\BrAutomation\AS43"

Possible reasons for an exit code with value 2:

• A valid installation of Automation Studio could not be found.
• The installation directory is write-protected.

3.5.2 Automation Runtime installer

This setup file was created using the NSIS scripting language. This makes it possible for B&R to implement logic
completely independently of the system where the software is being installed. The Automation Runtime installer
consists of several subordinate installation files. Depending on the selected components, the individual installers
are started in the background of the overarching Automation Runtime installation.

Available command line parameters for the Automation Runtime installer

Command line parameters can be used to influence, control or define preset values for all Automation Runtime
installers.
These parameter names are case-sensitive. It is also important to specify the character preceding each
parameter correctly (e.g. - or /).

14
 Software installation
Parameter Explanation Comment Example
-L GUI language 1033 for English, 1031 for German /L=1031 : Dialog boxes in German /
L=1033 : Dialog boxes in English
-R or /R Program mode Only "reduced mode" is currently avail- -R=Y
able. It provides a simplified GUI. Dia-
log boxes with user interaction are hid-
den. Parameter -RP is not permitted to
be specified at the same time.
-RP or /RP Program mode Parameter "Reduced mode with pause" -RP
works the same way as parameter -R,
with the only difference being a pause
when the installer is finished. The last
dialog box of the installer is therefore
not closed automatically. Parameter -R
is not permitted to be specified at the
same time.
-G Path Global installation path -=C:\Program Files\BrAutomation
-V Path Local installation path -V=C:\Program Files\BrAutoma-
tion\AS43
-h or -? Setup help Opens a message box listing all of the -h
possible command line parameters for
the installer. The installer does not con-
tinue running. As a result, any other pa-
rameters specified are ignored.
/Log Filename of the log file The entire path must be specified for /Log=C:\Temp\InstallationProcess.log
the installation log file, including the file- or /Log
name. This file is not generated until
the installation is complete. While the
installer is running, this file does not ex-
ist. Parameter /Log can also be speci-
fied by itself (i.e. without = and the file
path). In this case, the installer choos-
es a name for the log file automatical-
ly. The file is saved to the installation
directory.
/D Destination path The destination directory for the instal- /D=C:\Program Files\BrAutomation
lation is set with option /D. Option /
D must always be the last parameter
specified. The path must be specified
without quotation marks.

Return value
0 = No error occurred during installation.
1 = Installation was aborted by the user.
2 = An error occurred during installation.

Command line parameters passed to the installer (e.g. /D or /Log) are not explicitly validated. An invalid parameter
therefore does not necessarily have to result in an error or exit code ≠ 0.
Batch file example for evaluating the exit code:
"Automation Runtime 2.6.0.1309_V2.92.exe" /R /L=1031 /D=C:\Programme\BrAutomation
IF %ERRORLEVEL% 0

Possible reasons for an exit code with value 2:

• A valid installation of Automation Studio could not be found.
• The installation directory is write-protected.

3.5.3 Automation Studio installer

This setup file was created using the NSIS scripting language. This makes it possible for B&R to implement logic
completely independently of the system where the software is being installed.

Overview of command line parameters for the Automation Studio installer

Command line parameters can be used to influence, control or define preset values for all installers starting with
Automation Studio 3.
These parameter names are case-sensitive. It is also important to specify the character preceding each
parameter correctly (e.g. - or /).

15
Software installation
Parameter Explanation Comment Example
/L GUI language 1033 for English, 1031 for German /L=1031 : Dialog boxes in German
/L=1033 : Dialog boxes in English
/R=Y Program mode Only "reduced mode" is currently avail- /R=Y
able. It provides a simplified GUI. Dia-
log boxes with user interaction are hid-
den.
/Log Filename of the log file The entire path must be specified for /Log=C:\Temp\InstallationProcess.log
the installation log file, including the file-
name. This file is not generated until or
the installation is complete. While the
installer is running, this file does not ex- /Log
ist.

Parameter /Log can also be specified

by itself (i.e. without = and the file path).
In this case, the installer chooses a
name for the log file automatically. The
file is saved to the installation directory.
/D Destination path The destination directory for the instal- /D=C:\Program Files\BrAutomation
lation is set with option /D. Option /
D must always be the last parameter
specified.
/INSTALL_SUFFIX Expansion of the version label The text set by the parameter is added /INSTALL_SUFFIX=ParallelTest
to the Automation Studio version la-
bel. This makes it possible to install
the same version of Automation Studio
on a computer at the same time. The
specified text is not permitted to contain
spaces or quotation marks.

Return value
0 = No error occurred during installation.
1 = Installation was aborted by the user.
2 = An error occurred during installation.

Command line parameters passed to the installer (e.g. /D or /Log) are not explicitly validated. An invalid parameter
therefore does not necessarily have to result in an error or exit code ≠ 0.
Batch file example for evaluating the exit code:
"Automation Studio V4.5.1.exe" /R=Y /L=1031 /D=C:\Programme\BrAutomation
IF %ERRORLEVEL% 0

Possible reasons for an exit code with value 2:

• The user running the installer is not an administrator.
• The BrAddOn.ini file could not be found.
• A Windows 2000 operating system is being used without SP4.
• A Windows XP operating system is being used without SP2.
• A process named "pviman.exe" is running.
• A process named "pvimon.exe" is running.
• A process named "pvitransfer.exe" is running.
• A process named "pg.exe" is running.
• Automation Studio is already installed and incompatible with the version being installed.
• The installation directory is write-protected.

Installing upgrades from the command line

All upgrades can be installed using a batch file as follows.
• Automation Studio 4.x upgrades
<UpgradeName.exe> -G="<Global AS install path>" -V="<Local AS install path>" -R=Y

Batch file examples

AS4_AR_A0426_X20CP1586.exe -G="C:\BRAutomation" -V="C:\BRAutomation\AS42" -R=Y

AS4_HW_X20DO9322.exe -G="C:\BRAutomation" -V="C:\BRAutomation\AS42" -R=Y

• Automation Studio 3.x upgrades

<UpgradeName.exe> -T=3.0.70 -G="<Global AS install path>" -V="<Local AS install path>" -R=Y

Batch file examples

16
 Software installation

AS3.0_AR_C0310_X20CP3486.exe -T=3.0.70 -G="C:\BRAutomation" -V="C:\BRAutomation\AS30090" -R=Y

AS3.0_HW_X20AI2322.exe -T=3.0.70 -G="C:\BRAutomation" -V="C:\BRAutomation\AS30090" -R=Y

4 PVI
4.1 System requirements

This section contains system requirements for the Process Visualization Interface (PVI) as well as specifications
regarding which operating systems can be used with which versions. For information about using Automation
Software on virtual machines, see limitations for virtual machines.

4.1.1 PVI 4.3 and later

This section contains the system requirements for Process Visualization Interface V4.3 and later.
Operating systems
• Windows 10 (32-bit and 64-bit)
• Windows 8 (32-bit and 64-bit)
• Windows 7 SP1 (32-bit and 64-bit)
• Windows Vista SP2 (32-bit and 64-bit)
Processor
• Recommended: Intel Core i3 or comparable
• Minimum: Dual core or comparable
RAM
• Minimum: 1 GB
• Recommended: 2 GB
Hard drive space
• Minimum: 300 MB
• Recommended: 500 MB

4.2 Installation

Administrator rights are needed on Windows operating systems to install new software. If necessary,
contact your network administrator.

Installation steps
1. Insert the installation DVD into the computer's DVD-ROM drive.
2. If option "AutoPlay" is enabled on the computer, then the B&R automation software window will appear. If
AutoPlay was not enabled, file Install.exe from the root directory of the CD installation must be started.
3. Select Automation Net from the list on the left window border.
4. Then start the install procedure.

Installing PVI Development

If one of the following components is to be installed, PVI Development Setup must be installed.
Components included:
• PVI base system (PVI Runtime installer)
• Runtime Utility Service (PVI Runtime installer)
• PVI development tools
• PVI server
• PVI help documentation - German
• PVI help documentation - English
• PVI PDF documentation
• PVI examples
• PVI tutorial

17
Software installation

4.2.1 Adding software components

The installer must be run again in order to add individual components. Components can be deselected or selected
for installation by clicking on them in the selection tree in the component selection dialog box.
Each time the Automation Net installer is executed, the components selected for installation are record-
ed. As a result, the only components in the selection tree that can be selected are those that are entirely
new or those that have not yet been installed.
If components should be removed, all of Automation Net must first be uninstalled and then reinstalled
without selecting the respective components (i.e. they are not permitted to be selected in the selection
tree).

4.3 Uninstalling PVI

Automation Net PVI can be removed from the system by selecting "All programs / B&R Automation / PVI %Ver-
sion% / Uninstall PVI" from the Windows Start menu.

4.4 PVI installer

Command line parameters can be used to influence, control or define preset values for all B&R installers.
These parameter names are case-sensitive. It is also important to specify the character preceding each
parameter correctly (e.g. - or /).

Available command line parameters for the Process Visualization Interface

Parameter Explanation Comment Example
/Log Logger The entire path must be specified for /Log=C:\Temp\InstallationProcess.txt
the installation log file, including the file- or /Log
name. This file is not generated until the
installation is complete. While the in-
staller is running, this file does not exist.
Parameter /Log can be specified with-
out a path. The file is saved in the temp
directory (%temp%).
/R Installation mode This mode provides a simplified GUI. /R
Dialog boxes with user interaction are
hidden.
-L Dialog box language 1033 for English, 1031 for German /L=1031 : Dialog boxes in German /
L=1033 : Dialog boxes in English
/D Destination path The destination directory for the instal- /D=C:\BrAutomation
lation is set with option /D. Option /
D must always be the last parameter
specified. Specify the path without quo-
tation marks.
-O Options for installation The packages to be installed can be de- -O=C:\Temp\pvi.ini
fined via the specified file.
/S Silent installation No user input is required. /S

"Reduced mode" installation

All PVI installers can be installed without user input.
Batch file example:
"Automation Net PVI Runtime V4.5.exe" -L=1031 /R -O="C:\Temp\pvi.ini" /D=C:\Program Files\BrAutomation

Return value
0 = No error occurred during installation.
1 = Installation was aborted by the user.
2 = An error occurred during installation.
Command line parameters passed to the installer (e.g. /D or /Log) are not explicitly validated. An invalid parameter
therefore does not necessarily have to result in an error or exit code ≠ 0.
• The user executing the installer is not an administrator.
• A process named "pviman.exe" is running.
• A process named "pvimon.exe" is running.
• A process named "pvitransfer.exe" is running.

18
 Software installation

• PVI is already installed and is incompatible with the version being installed.
• The installation directory is write-protected.

pvi.ini
Option -O allows a file to be passed to the installer that controls the individual components of the installer. The
options are specified in the form of an identifier.

The PVI installer currently includes the following components:

Identifier Description
PVIManagerAsService Installs PVI Manager as a Windows service
RUC Runtime Utility Center
TGDongleDriver Dongle driver for Technology Guard (1TG0500.02)
USBDongleDriver Dongle driver for USB dongle (5S0500.02U)
CANDriverCC770 CC770 CAN driver
CANDriverSJA1000 SJA1000 CAN driver
OPCServer PVI OPC DA 3.0 server
PVIAPI PVI C/C++ libraries, PviServices, ANSL Linux API and example code
PVIHelp PVI help documentation

Example of a complete pvi.ini file:

[PVI]
PVIManagerAsService=0
RUC=1
TGDongleDriver=1
USBDongleDriver=0
CANDriverCC770=0
CANDriverSJA1000=0
OPCServer=0
PVIAPI=1
PVIHelp=1

Value 0 means that the component should not be installed.

Value 1 means that this component should be installed.

Overview of command line parameters for the PVI installer for uninstall
Parameter Explanation Comment Example
/S Silent uninstall No user input is required for this. /S

5 SafeDESIGNER
5.1 System requirements

This section contains the system requirements for SafeDESIGNER.

No support for the following installations:
- Standalone installation
When using a virtual machine, make sure that the system behaves the same way as real hardware (e.g.
VMware Workstation).

5.1.1 SafeDESIGNER 4.3

This section contains the system requirements for SafeDESIGNER 4.3.

Operating systems
• Windows 10
• Windows 8
• Windows 7
Processor
• Minimum: See Automation Studio 4.3.
• Recommended: See Automation Studio 4.3.
RAM
• Minimum: See Automation Studio 4.3.
• Recommended: See Automation Studio 4.3.
19
Software installation

Hard drive space

• Minimum: See Automation Studio 4.3.
• Recommended: See Automation Studio 4.3.
Screen resolution
• Minimum: See Automation Studio 4.3.
• Recommended: See Automation Studio 4.3.
Interface
• Ethernet

5.1.2 SafeDESIGNER 4.2

This section contains the system requirements for SafeDESIGNER 4.2.

Operating systems
• Windows 10
• Windows 8
• Windows 7
Processor
• Minimum: See Automation Studio 4.2.
• Recommended: See Automation Studio 4.2.
RAM
• Minimum: See Automation Studio 4.2.
• Recommended: See Automation Studio 4.2.
Hard drive space
• Minimum: See Automation Studio 4.2.
• Recommended: See Automation Studio 4.2.
Screen resolution
• Minimum: See Automation Studio 4.2.
• Recommended: See Automation Studio 4.2.
Interface
• Ethernet

5.2 Installation

Administrator rights are needed on Windows operating systems to install new software. If necessary,
contact your network administrator.

SafeDESIGNER versions are always installed in the same directory as the Automation Studio versions.

Installation steps
1. Insert the installation DVD into the computer's DVD-ROM drive.
2. If option "AutoPlay" is enabled, then the B&R Automation installation window will appear. If AutoPlay was not
enabled, file Install.exe from the root directory of the DVD installation must be started.
3. Select the desired language with the mouse.
4. In the window that appears, start the installation with Start installation.

If a current Framework is not present on the target computer, it will be installed during the setup
process.

5.3 Licensing

Licensing of SafeDESIGNER V4.3.0 and later is handled by a valid Automation Studio license.
For older versions (prior to 4.3.0), licensing is handled in SafeDESIGNER by entering the valid Automation Studio
license.

20
 Software installation

5.4 Uninstalling

A SafeDESIGNER version can be removed by executing the Uninstall.exe file in the version's installation directory.
Versions are always installed to the same directory as Automation Studio versions.
The uninstall wizard carries out the deinstallation process automatically.

5.5 SafeDESIGNER installer

Command line parameters can be used to influence, control or define preset values for all SafeDESIGNER in-
stallers. The following section summarizes the command line parameters that can be used with the SafeDESIGN-
ER installer.
These parameter names are case-sensitive. It is also important to specify the character preceding each
parameter correctly (e.g. - or /).
Parameter Explanation Comment Example
/Log Logger The entire path must be specified for /Log=C:\Temp\InstallationProcess.txt
the installation log file, including the file- or /Log
name. This file is not generated until the
installation is complete. While the in-
staller is running, this file does not exist.
Parameter /Log can be specified with-
out a path. The file is saved in the temp
directory (%temp%).
/R Installation mode This mode provides a simplified GUI. /R
Dialog boxes with user interaction are
hidden.
/L Dialog box language 1033 for English, 1031 for German /L=1031 : Dialog boxes in German /
L=1033 : Dialog boxes in English
/D Destination path The destination directory for the instal- /D=C:\BrAutomation
lation is set with option /D. Option /
D must always be the last parameter
specified. Specify the path without quo-
tation marks.

Return value
0 = No error occurred during installation.
1 = Installation was aborted by the user.
2 = An error occurred during installation.
Command line parameters (e.g. /D or /Log) are not explicitly validated. An invalid parameter therefore does not
necessarily have to result in an error or exit code ≠ 0.
Batch file example for evaluating the exit code:
"SafeDESIGNER V4.2.exe" /R /L=1031 /D=C:\Programme\BrAutomation
IF %ERRORLEVEL% 0

Possible reasons for an exit code with value 2:

- The user running the installer is not an administrator.
- The installation directory is write-protected.

6 Automation Studio Target for Simulink

6.1 System requirements

Automation Studio Target MATLAB/Simulink version Automation Studio Coder from MathWorks
for Simulink version
4.5.0 R2007b or later 3.0.90 or later Simulink Coder
Embedded Coder
5.6.1 R2012b or later 3.0.90 or later Simulink Coder
Embedded Coder
6.0.0 R2016a or later 3.0.90 or later Simulink Coder
Embedded Coder

6.2 Installation

The installer and latest version can be downloaded from the Downloads section of the B&R website.
Link: B&R Downloads section

21
Software installation

Figure 1: Automation Studio Target for Simulink - Welcome screen

Depending on which language is configured on the PC, the wizard is displayed in German or English.

22
 Software installation

Figure 2: Specification of the MATLAB path where matlab.exe is located

All MATLAB versions starting with R2016b up to the latest release are supported. MATLAB must be closed.

23
Software installation

Figure 3: Specification of the Automation Studio Target for Simulink installation path
A folder for B&R Automation Studio Target for Simulink is automatically created in the specified path.
MATLAB will open in the background. Please wait until the licensing dialog box or a licensing message appears.
Uninstall wizard:
The uninstall wizard is located in the installation directory of Automation Studio Target for Simulink. It can also be
launched via "Control Panel → Programs and features".

24
 Software installation

Figure 4: Uninstall wizard - Welcome screen

Figure 5: Successful uninstall

The installation directory of Automation Studio Target for Simulink can now be deleted manually.

6.3 Uninstalling

The file for uninstalling is located in the installation directory of Automation Studio Target for Simulink or can be
launched from Control Panel / Programs and functions.

25
Software installation

6.4 Licensing

Licenses

Automation Studio Target for Simulink Technology Guarding / License name

AS Target for Simulink - Single license 1TGSIMTS.SNG.00-01
AS Target for Simulink - Site license 1TGSIMTS.STE.00-01
AS Target for Simulink - Corporate license 1TGSIMTS.CRP.00-01

Licensing procedure
Once Automation Studio Target for Simulink has been installed, it must be licensed. If Automation Studio Target
for Simulink has not yet been licensed, the licensing dialog box is automatically displayed to enter a license key. If
a Technology Guard dongle containing a license file exists, the license is activated automatically.

Depending on the selected license type, a Technology Guard for storing the license is needed (Technology Guard-
ing) or a licensing key must be entered in the licensing dialog box. Evaluation licenses and student licenses can
be requested directly on the B&R website.
There are various options for activating Automation Studio Target for Simulink.
• Online activation with a valid license key
• Activating an evaluation license
Online activation
Enter the supplied B&R license key in the input field. Clicking button Activate will automatically license the B&R
Automation Studio Target for Simulink version online over an existing Internet connection.
Evaluation license
The link in the dialog box directs to the B&R website. When selecting an evaluation license, an email is sent to the
specified address after the form has been filled out. This email contains a license key that can be activated in the
licensing dialog box. The remaining evaluation period is shown each time Automation Studio Target for Simulink
is started. After the evaluation period expires, Automation Studio Target for Simulink must be licensed again.

26