Install PDF
Install PDF
Install PDF
Software installation
Inhaltsverzeichnis (31.5.2011)
1 Software installation..........................................................................................................................................1
1.1 Automation Net - PVI............................................................................................................................1
1.1.1 System requirements - PVI.........................................................................................................1
1.1.1.1 System requirement - PVI Runtime...................................................................................2
1.1.1.2 System requirement - PVI Development...........................................................................2
1.1.2 Installing B&R Automation Net (PVI Runtime)............................................................................2
1.1.2.1 PVI Runtime......................................................................................................................2
1.1.2.2 PVI Development setup.....................................................................................................3
1.1.3 Adding PVI software components...............................................................................................3
1.1.4 Uninstalling PVI..........................................................................................................................4
1.1.4.1 PVI Runtime......................................................................................................................4
1.1.4.2 PVI Development..............................................................................................................4
1.1.5 PVI setup info.............................................................................................................................4
1.1.5.1 PVI Runtime / Developer - Setup......................................................................................4
1.2 Automation Studio................................................................................................................................8
1.2.1 Automation Studio system requirements....................................................................................8
1.2.2 Installing Automation Studio.....................................................................................................10
1.2.3 Adding software components in Automation Studio.................................................................12
1.2.4 Licensing...................................................................................................................................13
1.2.4.1 Automation Studio...........................................................................................................13
1.2.4.2 License automatically (online).........................................................................................14
1.2.4.3 License manually (offline)................................................................................................14
1.2.4.4 Option license..................................................................................................................15
1.2.5 Uninstalling Automation Studio.................................................................................................16
1.2.5.1 Applies to multiple installations (only Version AS2.x):.....................................................16
1.2.6 Automation Studio setup info....................................................................................................16
1.2.6.1 Automation Studio Help - Setup......................................................................................16
1.2.6.2 Automation Runtime - Setup...........................................................................................18
1.2.6.3 Automation Studio - Setup..............................................................................................20
1.3 Automation Studio Target for Simulink®............................................................................................21
1.3.1 Automation Studio Target for Simulink® - System requirements.............................................21
1.3.2 Automation Studio Target for Simulink® - Installation..............................................................22
1.3.3 Automation Studio Target for Simulink® - Uninstallation..........................................................22
1.3.4 Automation Studio Target for Simulink® - Documentation.......................................................22
1.4 FAQ....................................................................................................................................................22
1.4.1 Installing a USB dongle............................................................................................................22
1.4.1.1 Installation procedures....................................................................................................23
i
Software installation
ii
1 Software installation
1.1 Automation Net - PVI
1.1.1 System requirements - PVI
The computer on which PVI is to be installed must meet the following requirements:
The computer also has to have an open online interface for the connection between the programming device
(computer) and the target system (controller).
An open interface (COM1 - COM4), a serial/USB adapter, or an Ethernet interface can be used.
1 Software installation 1
Software installation
Windows Windows
Windows XP Windows NT 4.0 Windows 95/98/ME
Vista / 7 2000
32 Bit 64 Bit 32 Bit 64 Bit
Operating 1) 2) 1) 1) 2)
5) 3) 6) 7) 4) 6)
system
Software SP3 for OPC Server Windows Socket
DA 2.0 (WinSock) version 2.2
needed
PVI Components
• PVIControl.NET applications can only be created with Visual Studio 2003.
• PVIServices applications can be operated with any .NET framework.
Processor At least Pentium III 650 MHz (recommended Pentium IV 850 MHz)
RAM At least 256 MB (depending on the number of process objects)
Hard disk space At least 20 MB free
1) No CAN communication.
2) No USB Dongle support on 64 Bit operating systems. On B&R targets (IPC, APC, PPC) no PVI dongle
required.
3) PVI services applications not possible.
4) No support for OPC server and PVIServices applications.
5) Limited USB support for CF creation, PVI Transfer.
6) No USB support for CF creation, PVI Transfer.
7) ARCNET OS9 line only up to SP5
Windows Windows
Windows XP Windows NT 4.0 Windows 95/98/ME
Vista / 7 2000
32 Bit 64 Bit 32 Bit 64 Bit
Operating 1) 2) 1) 1) 2)
3) 4)
system
Software SP3 for OPC Server Windows Socket
DA 2.0 (WinSock) Version 2.2
required
PVI Components
• PVIControl.NET applications can only be created with Visual Studio 2003.
• PVIServices applications can be run with any .NET Framework.
Processor At least Pentium III 650 MHz (recommended Pentium IV 850 MHz)
RAM At least 256 MB (depending on the number of process objects)
Hard disk space At least 100 MB free
1) No CAN communication.
2) No USB Dongle support on 64 Bit operating systems. On B&R targets (IPC, APC, PPC) no PVI dongle
required.
3) PVI services applications not possible.
4) No support for OPC server and PVIServices applications.
You need administrator rights to install software with the Windows NT/2000/XP operating system! Contact your
network administrator if necessary.
1. Insert the language-specific or multi-language (if applicable) installation CD in the computer's CD-ROM
drive.
2. If the "AutoPlay" option is activated on your computer, then the B&R Automation Software window
appears. If "AutoPlay" is not enabled, run the Install.exe file from the root directory of your installation
CD.
If a more current Automation Net version is already installed on your system, the PVI installation
is aborted.
The installation process begins after clicking on the "Start installation" button.
If one of the components listed below should be installed, the "PVI Development setup" must be installed.
Components included:
Components can be deselected or selected for installation by clicking on the selection tree in the component
selection dialog box.
Every time Automation Net is installed, the components selected for installation are shown. Therefore, the only
components in the selection tree that can be selected are ones that have been added or those that have not yet
been installed.
If components should be removed, the entire Automation Net must be removed and then reinstalled without the
respective components (these can then not be selected in the selection tree).
PVI Runtime can be removed from the system in the Start menu under All Programs / B&R Automation /
PVI%Version% / Uninstall PVI Runtime.
PVI Development can be removed from the system in the Start menu under All Programs / B&R Automation /
PVI%Version% / Developer / Uninstall PVI Developer.
This setup was created using the scripting language NSIS. This makes it possible for B&R to implement logic
completely independent of the system.
1.1.5.1.2 Overview of the available transfer parameters for the PVI Runtime / Developer setup
Transfer parameters can be used to influence, control or configure preset values for all B&R setups. The
following section describes the transfer parameters recognized by the Automation Studio setup.
The names are case sensitive. The preceding characters for each of the parameters (e.g. - or /) must also be
entered correctly.
/RC Program Like the /R option, the user can select the /RC
mode components to be installed, despite working in
(reduced reduced mode.
mode with
component This option only has an effect in PVI Runtime
selection) Setup, and not in PVI Developer Setup.
However, PVI Developer Setup applies this
option in PVI Runtime Setup if it calls it.
/RP Program Like the /R option, however, user input is /RP
mode needed to close the installation dialog box. This
(reduced mode is mostly used in order to check the
mode with installation process in the details window.
pause)
This option only has an effect in PVI Runtime
Setup, and not in PVI Developer Setup.
However, PVI Developer Setup applies this
option in PVI Runtime Setup if it calls it.
/ARS AR setup This parameter can be used to specify the file /ARS=PVIRuntime.exe
file name name for the Automation Runtime setup. If the
parameter is not specified, the developer setup
uses the default file name for the runtime setup.
/Log File name Here you must always enter the complete path, /Log=C:\Temp\InstallationProcess.log
for the log including the file name. The file is not generated
until the end of the installation. While the setup or
is running this file doesn't yet exist.
/Log
The /Log parameter can also be entered alone
(without = and the file path). In this case, the
setup chooses a name for the log file
automatically. The file is stored in the
INSTALLDIR.
All PVI setups can be installed without user input, e.g. from a batch file.
1.1.5.1.4 ExitCode
A Windows program can return an ExitCode (or return code). This is normally 0 and doesn't affect a user
installation. However, there are certain circumstances (e.g silent installation), in which it can be helpful for the
ExitCode to have a different value. The following values are possible:
Transfer parameters for the setup (e.g. /D or /Log) are not validated explicitly. An invalid parameter must
therefore not necessarily result in an error or in an ExitCode <> 0.
1.1.5.1.5 pvi.ini
The /O option lets you to provide the PVI Developer and PVI Runtime Setups with a file that allows them to
control the individual components of the setup. The options are entered in the form of an identifier. The identifier
is shown in the setup's options window under "description" when you move the mouse over the components.
If in the INI file, which here in the Help is always named pvi.ini, there is no component specified explicitly, the
Setup uses the default value. However, the value is different for each component. It is therefore advisable to
always specify all components explicitly in such an INI file.
[PVI260]
S0101=1
S0102=1
S0200=1
S0201=1
S0202=1
S0301=1
S0401=1
S0500=1
S0501=1
S0502=1
[PVI260_DEV]
S0100=1
S0110=1
S0120=1
S0130=1
S0131=1
S0132=1
S0140=1
S0150=1
S0160=1
S0161=1
S0161a=1
S0161b=1
S0162=1
S0163=1
S0164=1
S0170=1
S0190=1
S01A0=1
Meaning:
S0132=0 The value 0 means that this component should not be installed.
S0132=1 The value 1 means that this component should be installed.
The PVI Runtime Setup and the PVI Developer Setup use separate "INI sections". The name "INI section"
should not be confused with the name "Section", in the sense of an NSIS Setup. An "INI section" refers to a
group of values within an INI file. The name of an "INI section" is written in brackets. For example [PVI260]. An
NSIS "Section" refers to a encapsulated area within the NSIS Setup. In NSIS terminology, this is called a
component. A component can be selected in the component list with a checkmark.
Currently the PVI Runtime Setup always uses the name [PVI260] as the INI section. The PVI Developer Setup
user [PVI260_DEV]. This makes it possible for both setups to use a common INI file. It is also possible to move
both INI sections to separate INI files. The file name pvi.ini is only an example. The transfer parameter /O only
looks for a file name, and not the entire path for pvi.ini.
The computer on which Automation Studio is to be installed must meet the following requirements:
Minimum Recommended
Processor Pentium IV 2 GHz or higher Dual Core
RAM 1 GB 2 GB or higher
Hard disk space At least 5 GB At least 10 GB
Graphics XGA (1024 x 768) SXGA (1280 x 1024) or higher
Internet Explorer 6.0 7.0 or higher
http://www.microsoft.com/windows/virtual-pc/download.aspx
The computer also has to have an open online interface for the connection between the programming device
(computer) and the target system (controller).
An open interface (COM1 - COM4), a serial/USB adapter, or an Ethernet interface can be used.
You need administrator rights to install software with the Windows NT/2000/XP operating system! Contact your
network administrator if necessary.
1. Insert the language-specific or multi-language (if applicable) installation CD in the computer's CD-ROM drive.
2. If the "AutoPlay" option is activated on your computer, then the B&R Automation Installation window appears. If "AutoPlay" is not enabled, run the
Install.exe file from the root directory of your installation CD.
5. In the next window, start the installation by pressing the "Start installation" button.
If a current Framework or PVI version is not present on the target computer, they will be
installed during setup.
After confirming the license agreement and entering the user data, the installation dialog box for
selecting components is displayed.
If a component should not be installed, it can be deselected in the selection tree before
continuing the installation by clicking on Next>.
In the dialog box shown below, the installation directory can be changed by clicking the
Browse...button.
Components can be deselected or selected for installation by clicking on the selection tree in the component
selection dialog box.
1.2.4 Licensing
The following dialog box is displayed as long as Automation Studio has not yet been registered:
Enter the B&R serial number (included on the CD insert) into the first input field.
1.2.4 Licensing 13
Software installation
Pressing the License automatically (online) button automatically licenses the B&R Automation Studio™
Version online if there is an existing Internet connection.
Pressing the License manually (offline) button opens up a licensing dialog box. You can use the system code
(Sys-ID) shown here to apply for the actual activation code from the B&R Homepage Services site.
Entering the system code (Sys-ID) and pressing the Register button displays the activation code, which must
then be entered into the lower input field in the Automation Studio licensing window (License code (Sec-ID)).
If the correct code has been entered, then the licensing procedure can be completed with the OK button.
If a valid B&R serial number is not input, the dialog box can still be closed with License later, which starts the
30 day evaluation period.
The time left in the evaluation period is shown each time Automation Studio™ is started. Operation is possible
during this period without limitations.
If the evaluation period expires, then the software must be licensed to be able to continue using it.
In the information dialog box in Automation Studios pressing the "Option license" button while the option "B&R
AS C++ Option" has not yet been enabled, the following appears:
Enter the B&R serial number in the first input field. Once a valid serial number has been entered, the enabled
option is displayed in the Automation Studio information dialog box.
If a valid license number has already been entered and the "Option license" button is pressed, then the existing
license can be deleted.
If there are several version of B&R Automation Studio being used on your computer simultaneously, only the
active version can be uninstalled.
If no versions are active, the Version Changer can be used to activate the one you want to uninstall (see Version
Changer help).
Automation Studio can be removed from the system in the Start menu under All Programs / B&R Automation /
Automation Studio %Version% %Language% / Uninstall Automation Studio.
Once the uninstall wizard is started, the uninstall process is carried out automatically.
If there is still a B&R Automation Studio version present on your computer after one has been uninstalled, it has
to be activated using the Version Changer.
The Automation Studio Help setup installs both the English and the German Help for Automation Studio.
1.2.6.1.2 Available transfer parameters for the Automation Studio Help setup
Transfer parameters can be used to influence, control or configure preset values for all Automation Studio 3.x
setups. The following section describes the transfer parameters recognized by the Automation Studio setup.
The names are case sensitive. The preceding characters for each of the parameters (e.g. - or /) must also be
entered correctly.
/Log File name for the log Here you must always /Log=C:\Temp\InstallationProcess.log
enter the complete
path, including the file or
name. The file is not
generated until the /Log
end of the installation.
While the setup is
running this file
doesn't yet exist.
This function is
available starting with
Automation Studio
V3.0.72.
/D Target directory The target directory for /D=C:\Program Files\BrAutomation
the installation is set
using the option /D.
The /D option must
always be the last
parameter entered.
1.2.6.1.3 ExitCode
A Windows program can return an ExitCode (or return code). This is normally 0 and doesn't affect a user
installation. However, there are certain circumstances (e.g silent installation), in which it can be helpful for the
ExitCode to have a different value. The following values are possible:
Transfer parameters for the setup (e.g. /D or /Log) are not validated explicitly. An invalid parameter must
therefore not necessarily result in an error or in an ExitCode <> 0.
This setup was created using the scripting language NSIS. This makes it possible for B&R to implement logic
completely independent of the system. The Automation Runtime setup consists of multiple subordinate setups.
Depending on the selected components, the individual setups are started in the background of the superordinate
Automation Runtime setup.
Transfer parameters can be used to influence, control or configure preset values for all Automation Runtime
setups. The following section describes the transfer parameters recognized by the Automation Runtime setup.
The names are case sensitive. The preceding characters for each of the parameters (e.g. - or /) must also be
entered correctly.
The -R parameter
must not also be
entered.
/Log File name for the log Here you must always /Log=C:\Temp\InstallationProcess.log
enter the complete
path, including the file or
name. The file is not
generated until the /Log
end of the installation.
While the setup is
running this file
doesn't yet exist.
1.2.6.2.3 ExitCode
A Windows program can return an ExitCode (or return code). This is normally 0 and doesn't affect a user
installation. However, there are certain circumstances (e.g silent installation), in which it can be helpful for the
ExitCode to have a different value. The following values are possible:
Transfer parameters for the setup (e.g. /D or /Log) are not validated explicitly. An invalid parameter must
therefore not necessarily result in an error or in an ExitCode <> 0.
This setup was created using the scripting language NSIS. This makes it possible for B&R to implement logic
completely independent of the system.
Transfer parameters can be used to influence, control or configure preset values for all Automation Studio 3.x
setups. The following section describes the transfer parameters recognized by the Automation Studio setup.
The names are case sensitive. The preceding characters for each of the parameters (e.g. - or /) must also be
entered correctly.
/Log File name for the log You must always enter /Log=C:\Temp\InstallationProcess.log
the complete path,
including the file or
name. The file is not
generated until the /Log
end of the installation.
While the setup is
running this file
doesn't yet exist.
1.2.6.3.3 ExitCode
A Windows program can return an ExitCode (or return code). This is normally 0 and doesn't affect a user
installation.
Transfer parameters for the setup (e.g. /D or /Log) are not validated explicitly. An invalid parameter must
therefore not necessarily result in an error or in an ExitCode <> 0.
The following components are required for automatic code generation with B&R Automation Studio Target for
Simulink®:
Optional (for source code that is more efficient and easier to read):
Nearly all toolboxes from The MathWorks are fully compatible with B&R Automation Studio Target for Simulink®.
B&R Automation Studio Target for Simulink® is installed under MATLAB® by running the file install.p, which is
located in the installation directory after Automation Studio is installed
"%AS_Installationsverzeichnis%\BrAutomation\Simulink Target Setup".
The components for automatic code generation are copied to a user-specific directory (e.g. C:\Program
Files\BrAutomation\B&R Automation Studio Target for Simulink® - the name "B&R Automation Studio Target for
Simulink®" is automatically added to the selected directory names) and then registered in MATLAB®.
To remove B&R Automation Studio Target for Simulink® from the system, run uninstall.p under MATLAB®.
Documentation for B&R Automation Studio Target for Simulink® can be found as a PDF file in the following
directory:
1.4 FAQ
1.4.1 Installing a USB dongle
• ARwin
If the dongle was already connected during the installation of Automation Studio or Automation Net, it had to be
removed and reconnected to the interface once before installing the driver.
The first time a USB dongle is used, its driver must be installed. This is done as follows:
• Insert the USB dongle in the USB port. The operating system will detect the new hardware and display
the following dialog box
• In the next dialog box, select Install the software automatically and continue with Next>.
• If the driver cannot be found, the path shown in the dialog box must be entered in order to continue the
installation.
Component Description
ARwin For the ARwin, use the directory described above "C:\Windows\system32\Drivers", since
a different dongle driver is used than for PVI.
The dongle driver for the ARwin can only be used in Windows XP, since the ARwin is only
released for this operating system.
PVI For PVI, use the dongle drivers in the directory
"%InstallDir%\BrAutomation\PVI\V3.00.00\PVI\WinUSB".
The dongle driver for PVI can also be used in Windows Vista and Windows 7 (both only
the 32-bit version).