2.2.1.2 Readme PDF

Information about B&R AutomationSoftware
Contents
1 Information about B&R Automation Software............................................................................................1
1.1 B&R Automation Software Service Release 2.2.1.2.......................................................................1
1.2 New Functions are documented for the following versions.............................................................2
1.2.1 New functions in Service Release 2.2.1.2.............................................................................2
1.2.2 New Functions in AS V2.2.....................................................................................................6
1.2.3 Neue Funktionalitten in AS V2.1.5.0..................................................................................16
1.2.4 New Functions for AS V2.1..................................................................................................17
1.2.5 New Functions for AS V2.0..................................................................................................22
1.3 Error Corrections are documented for the following versions.......................................................24
1.3.1 Error corrections in Service Release 2.2.1.2.......................................................................25
1.3.2 Error Corrections AS V2.2 Service Packs and Service Release.........................................31
1.3.3 Error Corrections − AS V2.1 to AS V2.2..............................................................................32
1.3.4 Error Corrections − AS V2.1 to AS V2.1.5.0........................................................................39
1.3.5 Error Corrections AS V2.1...................................................................................................42
1.4 Known Problems and Deficiencies are documented for the following versions............................44
1.4.1 Known problems in Service Release 2.2.1.2.......................................................................44
1.4.2 Known Problems and Deficiencies in AS V2.2....................................................................45
1.4.3 Known Problems and Deficiencies in AS V2.1....................................................................46
i
ii
1 Information about B&R Automation Software
1.1 B&R Automation Software Service Release 2.2.1.2

This Service Release Version includes Service Pack 1 and 2
This file contains current Information of B&R Automation Software. We recommend that you read the entire
file before installing and using the B&R Automation Software.
B&R Industrie Elektronik GmbH has the Copyright ((C) 1999−2002) for all in the following table with * signed
components.
Software Components on the Service Release CD Version

Automation Net / PVI
PVI 2.2.0.3002
PVI Runtime (only binaries, no help) 2.2.0.3103
PVI Transfer Tool 2.2.0.2203
PVI Controls + Alarm 2.2.0.2110
Automation Studio *
Automation Desktop 2.2.1.0001
Motion Components 2.2.1.0001
Visual Components 2.2.1.0001
Automation Runtime
Automation Runtime V2.61 (i386) 2.2.1.0001
Automation Runtime V2.30 (m68k) 2.2.1.0001
AR102 InstallKit 2.2.0.4201
AR105 InstallKit 2.2.0.4301
1
NC Software ACP10 for CAN V0.502

ACP10 for PowerLink V1.002
NC150 V1.22
DM455 V1.80
NC154 V5.420
NC156 V5.420
NC157 V5.420
NC158 V5.420
Panel Studio 2.2.0.5201
Version changer 2.2.0.7003
The installation of the following Service Release 2.2.1.0001 software components can be done separately via
the installation menu "BrMenu.exe" (only the selected component will be updated):
♦ Automation Runtime V2.61 (i386) 2.2.0.1306

♦ Automation Runtime V2.30 (m68k) 2.2.0.1402
1.2 New Functions are documented for the following versions

New functions in Service Release 2.2.1.2
New Functions for AS V2.2
New Functions for AS V2.1.5.0
1.2.1 New functions in Service Release 2.2.1.2
Automation Runtime, Automation Studio, Automation Net, Version Changer
1.2.1.1 Automation Runtime
AR102, AR105, CP360, i386 Base, Libraries (i386), Libraries (m68k) + m68k Baes
1.2.1.1.1 AR102
♦ If there are several assignments for interfaces

on the AR102, then RS485 mode on COM3 is also supported. The RS485 interface
can be accessed via IF6. Parallel operation of CAN and RS485 is not possible.
♦ Multiple assignments for interfaces
On the AR102, RS485 mode is now also supported on COM3. The RS485 interface
can be operated using IF6. Simultaneous operation of CAN and RS485 is not
possible.
1.2.1.1.2 AR105
♦ Support for 5LS189.6

♦ Multiple assignments for interfaces
On the AR102, RS485 mode is now also supported on COM3. The RS485 interface
2
can be operated using IF6. Simultaneous operation of CAN and RS485 is not
possible.
♦ UPS support (ID#55120)
Communication can now take place with a B&R UPS using the AsUPS library. If a
power failure is detected on the UPS, Automation Runtime shuts down and is
brought to a secure state. Automation Runtime is restarted by a power on.
♦ SMTP support
Email can now be sent using functions in the Ethernet library.
♦ 'spooler' library created for i386 (ID#38400)
To operate intelligent modules (DM455, NC352), the application program must be
spooled to these modules by Automation Runtime.
♦ 'if661' library created for i386
Functions from this library are used to operate the 3IF661.9 module.
♦ New 'FileCopy' function in the FileIO library (ID# 47490).
♦ Access monitoring with the SRAM200x library
With the new SRAM200x library, read and write access to the SRAM area can be
monitored.
1.2.1.1.3 CP360
♦ New FTP server

The FTP server is now the same as the FTP server on the AR10x.
1.2.1.1.4 i386 Base
♦ The number of parallel connections has been increased to 128.

♦ FTP access update
It is now possible to access all Automation Runtime partitions using FTP
♦ Access to partitions C, D, E, and F
Partitions C, D, E, and F can now be operated using functions from the FileIO
library. However, these partitions must be on the first Compact Flash (CF) or hard
drive (HDD). If a second CF or HDD is used, it has to be addressed as Drive G.
1.2.1.1.5 Libraries (i386)
♦ INA reinstall (ID#54885)

INA communication can be activated or deactivated using the functions
INADevOpen() and INADevClose() in the commserv library. If the interface was
previously used by other protocols (Net2000, frame driver), it can now be used again
as an INA interface
♦ INA client updates (ID#55115)
− Correct formatting when transferring structures and structure arrays between
different target system types
− Data exchange using event variables
− Expansion of target memory for uploading and downloading
− Expansion of link objects from 1,000 to 16,000
♦ UPS support (ID#55120)
Communication can now take place with a B&R UPS using the AsUPS library. If a
power failure is detected on the UPS, Automation Runtime shuts down and is
brought to a secure state. Automation Runtime is restarted by a power on.
♦ SMTP support
♦ 'spooler' library created for i386 (ID#38400)
To operate intelligent modules (DM455, NC352), the application program must be
spooled to these modules by Automation Runtime.
♦ 'if661' library created for i386
Functions from this library are used to operate the 3IF661.9 module.
♦ New 'FileCopy' function in the FileIO library (ID# 47490).
♦ Access monitoring with the SRAM200x library
With the new SRAM200x library, read and write access to the SRAM area can be
monitored.
3
1.2.1.1.6 Libraries (m68k) + m68k Base
♦ INA Client updates (ID# 55115)

− Correct formatting when transferring structures and structure arrays between
different target system types
(AR V2.30 + AR V2.61)
− Data exchange using event variables
(AR V2.30 + inaclient V1.12.7)
♦ SMTP support
♦ New 'LoopConR' library
Controller library which calculates REAL variables internally
♦ 'LoopCont' library update
−LCPID(): New function 'inactive in selector loop control':
If (fbk_mode == LCPID_FBK_MODE_EXT_SELECTOR (new mode!!)) and (Y_fbk !=

Y_old)
are true in LCPID_OUT_MODE_AUTO, AND the control deviation changes
the sign, then Yi= (Y_fbk − Yp_old − Yd_old − A_old) is set.
New warning LC_WARN_LCPID_YFBK_LIMIT if Y_fbk stays under Y_min or

exceeds Y_max here.
♦ New 'Spooler' library created
1.2.1.2 Automation Studio
Automation Desktop, Motion Components, Visual Components
1.2.1.2.1 Automation Desktop
♦ Loading project lists

Project lists can now be loaded back again, similar to saved schemas.
♦ Overwriting module parameters can now be deactivated when importing
If modules (tasks) were shifted into a different task class of the target memory was
changed, these changes were overwritten again after a new import. Overwriting
module parameters can now be deactivated.
♦ Update of Sysconf settings
New settings options for the size of the Supervisor Stack for the root task
new settings options for the number of timers
♦ Update for online connections
Read Timeout (RT) parameter for online modem connections
direct IP specification (DAIP) for Ethernet online connection
♦ Declariation of FBKs when inserting
If an FBK call is inserted using a dialog box, the declaration editor is shown after
selecting the FBK type, whereby the correct data type is already entered.
♦ Implicit variables can now be hidden
Variables which are automatically created (intermediate variable in the ladder
diagram, SFC step variables, ...) can now be hidden in the variable declaration.
♦ Extension of Update Memcard Wizard
The permanent Flag area can now be ereased by uploading the Automation
Runtime via Update Memcard
♦ Additional support of LS187 and LS189
1.2.1.2.2 Motion Components
♦ During a test, a warning is given before executing a command. The user can
supress the warning for a certain command by marking the respective CheckBox in
the Warning dialog box. After each restart of AS, all warnings are shown again, even
4
if the user supressed a warning text the last time AS was run.
Currently, only the warning " Danger! You can cause a dangerous movement.
Please observe the safety regulations in the manual." is output for the command
"ncREL_MOVE, ncSTART" .
♦ During a test, it is now possible to execute the command "ncMOVE, ncSTOP" by
pressing the F3 key in addition to pressing the "STOP" button.
1.2.1.2.3 Visual Components
1.2.1.2.3.1 General Information
◊ Several levels can now also be configured on control keys.

◊ Picture number index can be configured.
◊ Operating the "Load Bitmap from File" dialog box was simplified.
(ID#53050, ID#18028, ID#19428)
◊ Copying and inserting objects is possible at the current mouse
position. This has to be set in the VC Options menu.
◊ Alarm data module can be generated steplessly up to 1000. Alarm
module can also be disabled.
1.2.1.2.3.2 Visapi Functions
◊ VA_GetDiplay Info: Reads display resolution (i386).

◊ VA_GetActAlarmList : Reads the alarm list.
◊ VA_GetTextByTextgroup: Displays texts which are assigned to a
text group.
1.2.1.3 Automation Net
PVI Control, PVI−Alarm System, PVI−Trend System, PVI Configurator, PVI Transfer, PVI
Manager
1.2.1.3.1 PVI Control
♦ new function "Format" added

with this function internal values can be converted in a Resource editor format and
be displayed.
♦ Handling of several versions
With an new setup the PVI control are copied into a version dependend directory.
Thus several versions of PVI Control can be stored. With the B&R Version Changer
(AS_VersionChanger_0xx.exe) the different versions can be selected.
1.2.1.3.2 PVI Alarm System
♦ With the PVI Alarm System Bit and value alarms van be monitored. With the PVI
Alarm Configurator the alarms can be configured, to evaluate and record the alarms
the Alarm server is used. With the PVI Alarm Control the alarms can be displayed.
With the additional API interface the indication of the alarms can be realised by the
user. Also a historical clipbord is included.
1.2.1.3.3 PVI Trend System
♦ With the PVI Trend System process variables can be pictured graphical. With the
PVI Trend Configurator the alarms can be configured, to evaluate and record the
trend the Trend server is used. With the PVI Trend Control the trend can be
displayed. Also a historical clipbord is included.
1.2.1.3.4 PVI Configurator
♦ Support of MTC Line
5
1.2.1.3.5 PVI Transfer
♦ Two additional commands for error handling have been introduced:

"OnErrorResume" and "OnErrorBreak" (ID#51855)
It is now possible to resume or cancel the procedure after an error.
♦ The command "Connection" has been expanded:
− It is possible to make multiple connection settings in sequence, and the functioning
connection can be used further (ID#51850).
− A remote PVI online connection is now possible.
♦ Automatic CD creation implemented:
A directory structure can be created using this function, which contains the entire
project including operating system and necessary PVI files. The directory structure
can then be burned 1:1 on a CD. If you insert the CD, the PVITransfer is
automatically started and the project is transferred onto the RPS (ID#51860).
♦ Compact Flash creation installed:
Using this function it is possible, to create a Compact Flash directly from a laptop,
which contains the entire project including operating system. This is especially useful
for larger projects, because a serial transfer takes up a lot of time (ID#55375).
♦ When reading the error logbook ("ReadErrorLogbook" command) a language
distinction is made (German or English) (ID#56360).
♦ PVITransfer can be repeatedly started and can communicate simultaneously with
several controllers (ID#53950).
♦ The data types TIME and DATE_AND_TIME are possible, when reading and writing
variables.
1.2.1.3.6 PVI Manager
♦ Default values for process variables (ID#923)

Preset values for variables can now be set using the DV parameter
♦ Updates for CAST functions
CAST functions (CM=xx) were expanded. More detailed information can be found in
the PVI user documentation.
1.2.1.4 Version Changer
♦ Switching of PVITransfer or PVIControl versions now possible, without having AS

installed.
♦ Command line calls updated.
♦ Version Changer now in french language available
1.2.2 New Functions in AS V2.2
1.2.2.1 Automation Software V2.2
Automation Studio, NC Software, AutomationNet (PVI), AutomationRuntime, WindowsCE
1.2.2.1.1 Automation Studio
Automation Desktop, Motion Components, Visual Components, Automation Runtime Version

und Libraries
1.2.2.1.1.1 Automation Desktop
♦ Library debugging
equivalent to task debugging; now allows library functions to also be tested in the
6
debugger
♦ Profiler
measures CPU and stack loads on runtime targets
♦ Configuration dialog box
for simple configuration of interface parameters, memory allocation, IP addresses,
and much more
♦ ANSI/ASCII string formats
tasks and FBKs from the PG2000 in which umlauts are used can be imported into
Automation Studio without reworking.
strings in data modules, tasks, and libraries can now be optionally compiled in ANSI
or ASCII formats.
♦ Library dependencies
dependencies of other libraries are automatically entered, but can now be edited by
the user.
in addition, dependencies can be version or date dependent.
♦ Project printing
the entire contents of a project can now be printed with only one command (source
text, software objects, configuration settings, IO module assignment, hardware
structure)
♦ Repeated installations and switching versions
several versions of Automation Studio can now be installed. The active version can
be selected using the version switcher (only one version can be active, all other
versions cannot be started during this time)
♦ "Generate Transfer List"
produces download lists for PVI Transfer Tool
♦ Integrated error logbook help
help for the error message is displayed in the error logbook
♦ Hardware help reorganized
hardware module help is started by pressing F1. The description tab on the right
side has been removed.
♦ Project lists
project lists can be created in Automation Studio and externally. These lists can be
used for transferring and export Automation Studio projects.
♦ tasks can be exported without library information (export files are smaller)
♦ project name and scheme name are shown in the title bar
♦ scheme files can be deleted
♦ already saved scheme files are displayed when saved again
♦ additional menu option "Window / Close Ctrl−F4"
♦ permanent variable size setting in the Sysconf editor once more
♦ searching for software objects in the GDM
♦ standard target memory for data modules and tasks
♦ Ethernet as an online connection
unique configuration dialog box in Automation Studio for Ethernet online
communication
♦ Local PP boot
if a project is now transferred to the PP (parallel processor) a warm restart and cold
restart are executed directly on the main processor.
♦ expansion to 8 task classes for Automation Runtime projects (CP360, AR10x)
♦ IO driven task class for Automation Runtime projects (CP360)
♦ multiple lined function call in ST
♦ output parameters when calling memcpy, strcpy, memset, and strcat in IEC
languages are configured for i386 to m68k (they also return the next address and
not the start address)
♦ CP476 hardware support updated
ME0x0 modules can be inserted and used further (IO connections, Visual
Components).
7
1.2.2.1.1.2 Motion Components
• Standardization of trace displays in McTrace, Cam Editor and Automation Studio Trace
• Custom binary saving format .mch implemented in the Trace display object
• Deactivation of ACOPOS modules in the HW configuration
• NC configuration structure is now suited for several networks of many different types
• Operating ACOPOS modules on the Powerlink network is now possible
• 8Vxxxx.00−2 hardware accepted (HWC files, calling the help)
• Network command trace (as successor to the CAN command trace)
• ASCII Export Version 2.0 for network trace (with column for network[IF−Index], z.B. CAN[0],
CAN[1], PLK[0], VIRT[0], etc. )
• CAN Trace and Network Trace binary data is stored in the Motion Temp directory after each
load procedure, before the interpretation of the data begins − the _trc.bin files which are
automatically created ca be loaded in the Network Trace − an example for the name of a file
generated in this manner is: m68k_manid128_manver0.992_net_trc.bin
1.2.2.1.1.3 Visual Components
♦ Touch configuration
As an update for using touch displays with IPC 2000 and 5000 systems, now any
free serial interface can be used and configured for the touch screen. Interfaces
used by other devices (i.e. C100) are automatically not available.
♦ Variable numbering of text groups
Up to now, text numbers (indices) of texts could only be increased beginning with
the number 0. Now the text numbers of each text can optionally be set individually.
In this way, error numbers can be more easily assigned an appropriate error text, for
example.
♦ Variables in text group texts
Texts in a text group no longer have to contain only static texts; instead, dynamic
texts can be put together at runtime using the contents of PLC process variables. In
this way, error messages can be extended to include additional information, for
example, or high performance status displays can be easily implemented.
♦ Saving variables in the alarm list
In addition to the information stored previously in the alarm list, now up to four
pieces of numeric information from PLC process variables can also be stored with
the alarm text. In this way, alarms can be written with additional information such as
the error number of errors pertaining to intelligent IO components or the item which
caused the error to occur. Configuration takes place in the same way as text group
variables.
♦ Standardized scaling
Scaling of numeric data types was extremely simplified since all numeric data types
(except UDINT and FLOAT) will be able to be scaled to the entire DINT range in the
future. This removes the previous restriction which only allowed process variables to
be scaled within the value range of its own data type.
♦ Compressed bitmaps
Color bitmaps can be saved in compressed format with Visual Components 2.2
which allows them to be displayed very quickly. Compression is optimized for
graphics with large, monochrome surfaces like those which are very frequently used
for system images and schematic representations. Optimal compression is enabled
in this way.
Bitmaps are managed and used as previously; compression takes place
automatically with all supported controllers the next time the project is Built.
♦ New controller
In addition to the previously supported CAN operator panels, now serial operator
panels can be connected to the RS232 interface(s) and configured with Visual
Components. All display units which could be used previously with the C130 CAN
controller can be connected to the C100 controller.
♦ PS/2 AT keyboard support for IPC systems
8
With AT keyboard support, a lot of time can be saved by the simplified input of texts
and numbers, especially during the startup phase. In this way, the operator panel
can be designed even more to the operation of the machine while an AT keyboard
can be used during startup. By default, Visual Components supports German and
English (US) keyboard formats. Other formats can be defined as needed.
♦ Importing and exporting projects and parts of a project
Visual Components now supports importing and exporting of projects and parts of
projects; work invested can be more easily reused than previously in new projects.
All components from the Visual Components tree view can be individually or
collectively exported and imported. Dependencies are considered automatically so
that exporting can never be incomplete. Exporting and importing take place in XML
format; naturally, exporting and importing text in ASCII format is available.
1.2.2.1.2 NC Software
ACP10, Nc15x
1.2.2.1.2.1 ACP10
NC software ACP10_Powerlink V1.002 (corresponds to ACP10 V0.502 updated with Powerlink

functions) is contained in AS V2.2.
V0.501, V0.500, V0.495, V0.494, V0.493, V0.491, V0.490, V0.478, V0.475, V0.474
V0.501
♦ Drum Sequencer:
The number of tracks was increased to six.
♦ Extrapolation Filter:
The actual position filter for encoder 1/2/3 has been expanded to include
extrapolation. Activation and configuration are carried out with
ENCOD1/2/3_S_FILTER_TE.
V0.500
• The NC action "ncGLOBAL,ncINIT" is NO LONGER automatically activated, if there is

an INIT parameter module on the PLC.
• Cyclic Drive Operation (user data to the drive):

All parameters for CYCLIC_TODRV_PARID can now be used, which contain the Write
Attribute and are not occupied by "special functions" (e.g. data block transfer).
• Cyclic Monitor Data:
The data type limits DINT/UDINT for CYCL_MON_REQU1 and REAL32 for
CYCL_MON_REQU2 have been removed.
• NC Object "ncACP10USCOB":
New component "if_name" (CAN interface name for CAN open functions).
V0.495
• Return Power Limit PGEN_LIM:

The power dissipation in the motor winding is now considered for the return limits. The limits
have therefore been enlarged. By limiting the isq quadrature current, the warning 64506:
Return Power Limit (delay too long) is actively sent if the warning is enabled.
Enabling the warning:

PARID_MSG_CONF_ERROR_NUMBER = 64506
PARID_MSG_CONF_ACTIVATE_ERROR = ncEIN
A stop of movement is not triggered due to the limit. With longer limitation, movement can be
9
aborted if the lag error is exceeded.
The limits can be read on the following parameters:
ISQ_MAX_UDC (REAL) DC bus voltage controller: Upper current limit

ISQ_MIN_UDC (REAL) DC bus voltage controller: Lower Current Limit
A possibility which allows greater return power for mains supply of Un = 400V has been
developed for applications already sent out, which drive return power in the DC bus network
and are larger than the maximum brake power.
• E−stop for encoder signal failure of an asynchronous motor:

As of now, the stator is supplied with power in a way that the maximum motor torque is
created at the pull−out speed. If generator torque limits are used, then the power is supplied
in a way that the maximum generator torque limit occurs at the pull−out speed.
• Cam Profile Automat:

The monitoring function AUT_POLY_CHECK has been implemented for cam profile
polynomials.
V0.494
• Torque Limiter TLIM:

Torque limitation is now possible on asynchronous machines.
• Under voltage controller UVCTRL:
In the event of a power failure in standstill, a position change could occur in the external load
torque (e.g. by a vertical axis).
• Current monitoring when opening the brakes:
During the open phase, the brake monitors the stator current. An error occurs and the
controller is shut off if this is larger than the motor nominal current. For greater loads,
shut−off was prevented due to transient operations. Therefore, the monitor interval has been
increased on the maximum motor current.
Now, the parameter AUT_ST_COUNT_INIT for the ncANZAHL event can also be
consistently changed (with AUT_ONL_PAR_LOCK).
New Parameter for the Compensation Gears:
AUT_COMP_SL_V_MAX, AUT_COMP_SL_A1_MAX, AUT_COMP_SL_A2_MAX.
V0.493
• Analog Signal Monitoring AC122:

If an error occurs, the current position is rejected and replaced by one of the last speed
extrapolated positions.
• Drum Sequencer:
Consistent online change of the ON and OFF positions is now possible using the parameter
DRUMSEQ_ONL_PAR_LOCK.

Simultaneous consistent online change for drum sequencer and cam profile automat is
possible using the group parameter ONL_PAR_LOCK.
• Incremental Encoder Emulation:
Incremental encoder emulation is supported on the AC130 in slots 3 and 4.
• Speed Controller (SCTRL):
Speed limits can be configured on the speed controller input.
• Enable/Disable Warning Message:
Warnings in the error number range 64500 to 64999 only serve diagnostic / information
10
purposes and are therefore not displayed as default setting. They can be selectively enabled
and disabled:
PARID_MSG_CONF_ERROR_NUMBER = fehler_nr
PARID_MSG_CONF_ACTIVATE_ERROR = ncEIN and ncAUS
E.g.: "Diagnostic Message" for enabling the speed limit:
• Return Power Monitoring:
At DC bus voltage > 770V, the limiter is activated. An E−Stop is executed and an error
message is sent.
• Current Regulator (IREG):
Anti−Windup has been built into the current regulators.
• Over−temperature Monitoring Braking Resistor (Bleeder):
When the braking resistor reaches over−temperature, an E−Stop is executed.
• DC Bus Voltage Monitoring:
The software limit which causes an E−Stop has been removed.
V0.491
• Drive Synchronization:
The manipulated variable for drive synchronization can be configured.
• Analog Signal Monitoring AC122:
The plausibility check was removed and therefore open connection monitoring enabled
(preparation for hardware change on AC122).
• Stop of Movement:
A configuration can be made to cause an E−Stop when over−current occurs. The number of
over−current E−Stops is saved.
• Data block transfer now has a higher priority in the NC manager idle time task than Trace
parameter transfer or Trace data upload. Both of these functions are now interrupted when a
data block transfer is requested, and for the duration of the data block transfer.
V0.490
• Watchdog:
The watchdog is only enabled when the controller is active.
• Brake chopper:
The brake chopper is only enabled when the controller is on.
• DC Bus Voltage Monitoring of Enable Input:

Since V0.340 the loading relay was opened by setting the enable input. The loading
procedure which follows could last up to 200ms.
Now, the loading relay remains closed and the limit value is set to 90% of the nominal DC
bus voltage.
• On ACOPOS 1180 to 128M phase failure recognition has been implemented.
• DC Bus:
An under voltage limit for power failure has been implemented.
• Parameter Sequences:
Up to 10 parameter sequences can be loaded by downloading to the ACOPOS. With receipt
of the initialization command, a parameter of the corresponding sequence is initialized every
400us.
• New Function Parameter SCALE_R4_TO_I2:
The INT parameter SCALE_R4_TO_I2 is calculated by an "arbitrary" REAL parameter
11
(SCALE_R4_PARID) with an offset (Parameter SCALE_R4_OFFSET) and a multiplication

factor (Parameter SCALE_R4_ FACTOR).
Example for SCALE_R4_TO_I2 = air column torque in [NM]*10000:
SCALE_R4_PARID = TORQUE_ACT
SCALE_R4_OFFSET = 0.0
SCALE_R4_FACTOR = 10000.0
• External Cyclic Set Value Entry Mode 2:
The parameter SCALE_R4_TO_I2 is now included in the actual value telegram on bytes 2
and 3.
• Drum Sequencer:
The following parameters can now be set when the drum sequencer is active for online
changes to the switching edges and the dead time compensation setting:
DRUMSEQ_TRACK_INDEX
DRUMSEQ_CAM_INDEX
DRUMSEQ_S_DO_ON
DRUMSEQ_S_DO_OFF
DRUMSEQ_DO_DELAY
Switching positions larger than the interval are now allowed for cams which overlap intervals.
The cam end code has been changed to DRUMSEQ_S_DO_OFF equal to zero:
Cams can now be activated/deactivated online.
When the drum sequencer is starting, no default off edge is generated any more after the
start position is reached.
Master speed filtering for switching time compensation has been optimized.

The master axis AUT_COMP_MA_S for the compensation path can now also be configured
with zero.
The minimum compensation path of the master axis AUT_COMP_MA_S_MIN is now
checked for all compensation variations and is always in relation to the "effective"
compensation path.
• Labeling Cam Automat:

Restart, new parameter IDs implemented.
• Labeling Cam Automat:
New maximum FIFO size: 100.
• Simulation Mode:
The simulation model dynamic has been changed. (the amount of inertia and maximum
motor current has been reduced).
• Name change of the parameter ID 525 to EXTSET_CYC_STAT_BITS.
The parameter AUT_MA_V_MAX (maximum master speed) can now be changed online and
consistently for an active automat.
New parameter PCTRL_SYS_TIME for coupling.
• The message queue for the NC manager task is now made with variable size for the I386
platform (depending on the amount of drives). The previous constant size of 2000 bytes is
sometimes not enough when many drives are used in an application. Until recently, this was
not a problem in applications.
• A timeout time of 64ms is now used for CAN request telegrams (previously 32ms), to
improve the chance that a send timeout error is not falsely displayed even when the CAN
12
bus overloads. Until recently, this was not a problem in applications.
V0.478
• Controlling the brake chopper:

The precision of control functions was improved.
• Actual Position Filter for Motor Encoder (encoder on slot 2):
The filtered position is now available on ENCOD1_S_ACT_FILTER for coupling. Activation
and configuration with ENCOD1_S_FILTER_T10.
V0.475
• A check is now made before downloading NC system modules (BsLoader, operating system)
to make sure they are compatible with the ACOPOS NC HW version. Otherwise, the
download is cancelled and a corresponding error message is given.
Using ACP10−SW before this version it is possible to transfer a (non−operational)

BsLoader with the wrong NC HW version to an ACOPOS and burn it there in the
FPROM. As a result, ACOPOS cannot be operated.
• The timeout time for burning NC system modules (BsLoader, operating system) on the
ACOPOS servo drive for NC system module download has been increased, since the
burning process for 8Vxxxx.00−2 can take longer than the previously set time.
If an earlier version of ACP10 SW is used with 8Vxxxx.00−2, the error 32033: "timeout
burning the system module after download" can occur.

As of now, online switching of the master axis is possible using AUT_MA_AXIS.
• A second external encoder can now be used on slot 4.
• AC123 Incremental SSI Encoder:
Multiturn rotational encoders are now supported.
V0.474
• Online Change of the Lag Error Limits:

The parameters AXLIM_DS_STOP, AXLIM_DS_WARNING and AXLIM_DS_STOP2 can
now also be changed during active movement.
The event "ncZ_ENDE+ncNEGATIV" for reverse and the new parameters
AUT_START_ST_INDEX and AUT_CAM_MA_S_REL for a "direct start" in a cam of "any"
state have been implemented.
1.2.2.1.2.2 NC15x
V5.420, V5.413, V5.412
V5.420
♦ NC157:
◊ CAN communication is automatically received after a network error.

◊ Simulation mode is now also possible without ACOPOS being connected.
◊ Simultaneous referencing of multiple axes is now possible.
◊ Referencing is now cancelled when a power failure occurs.
◊ Telegram for reading the collective status bits is now entered in the CAN
trace.
13
◊ ACP10 operating system 0.502 integrated
♦ NC157:
A new response record type "ACOPOS reset" has been implemented. The following
states are set by the NC manager in the user data after this type is received:
◊ NC Object Type "ncAXIS":

encoder_if.status.init = ncFALSE;
move.go_home.valid = ncFALSE;
move.status.complete = ncFALSE;
◊ NC Object Type "ncEXTENCOD":
encoder_if.status.init = ncFALSE;
move.go_home.valid = ncFALSE;
♦ NC157:
◊ Status "netwerk.status.phase" has been implemented

◊ Option "+ncQUICKSTOP" for "dig_e.level..." has been implemented:
If "+ncQUICKSTOP" is set for a digital HW input when "dig_e.pegel...", then
the defined level for this input triggers the quick stop function.
V5.413
• CNC:
Restart now also functions for NC programs which use more than one trigger function (G200
/ G201). If only one trigger function is used per path section, an NC program can contain a
maximum of 31 such path sections without losing restart capability.
V5.412
• ACP10 operating system V0472 integrated
1.2.2.1.3
1.2.2.1.4 AutomationNet (PVI)
PVI, PVI Controls
1.2.2.1.4.1 PVI
♦ Support of LS172 in Windows NT 4.0, Windows 2000 and Windows XP with

configuration dialog box in the Windows Control Panel
The LS172 is a DUAL CAN card (PCI or ISA).
♦ Support of LS251 in Windows 2000 and Windows XP
♦ Expansion of INA node numbers to 255 for TCPIP, on the targets CP360 and AR10x
the INA node numbers can be set to values greater than 99.
1.2.2.1.4.2 PVI Controls
♦ PVIButton Control
♦ PVITouchpad Control
for entering values using a touch display
♦ Method for reading connection parameters of a PVI object
♦ Notification when all form links are valid
♦ Mouse operation of the PVI Listbox
♦ Alignment for PVI Textbox
14
1.2.2.1.5 Automation Runtime
AR V2.60, AR V2.28
1.2.2.1.5.1 AR V2.60
♦ AR Base (i386)
◊ A task class can be configured from which it and all higher task classes
(task class numbers) can be influenced by the task class idle time window.
All lower TCs remain unimpaired by the idle time window.
◊ Secure B&R module system
mirrors partitions for AR10x, therefore the AR systems must also be
reinstalled (Important: HDD must be repartitioned and reformatted)
◊ Update of the base system for profiling functions
◊ 8 cyclic task classes are now available
◊ Library debugging
♦ CP360
◊ Reading the node switch for INA station numbers
◊ Support of IF787, IF786 and IF789
♦ AR102
◊ AT keyboard support for Visual Components.
◊ PnP support for 5LS172.4
◊ Support of slot number switch (5LS127.4, etc)
♦ AR105
◊ PnP support of 5LS172.6 und 5LS172.61
◊ AT keyboard support for Visual Components.
◊ PnP support for 5LS172.4
◊ Support of slot number switch (5LS172.6, etc)
1.2.2.1.5.2 AR V2.29
♦ PP41 (m68k)
◊ PowerLink task class update
HSTC#2 can be configured as a PowerLink task class
♦ CP476 (m68k)
◊ PowerLink task class update
HSTC#2 can be configured as a PowerLink task class
1.2.2.1.5.3 AR V2.28
♦ AR Base (m68k)
◊ Can2000: RTR frames with varying data lengths − CAN_LIB V2.02
◊ Arouter: transmit queue per device instead of only one transmit queue
◊ FBase PP: Communication no longer via IRQs in case the CPU needs them
1.2.2.1.6 Windows CE
1.2.2.1.6.1 B3.0 20020118
♦ WinCE Runtime V3.0

Support of more than 32 MB RAM
Provit 5000C/5600C up to 256 MB RAM
Provit 200x up to 64 MB RAM
♦ Install kits are provided together
there is only one install kit manager for the different runtime systems
♦ Support of LS172 in Windows CE 3.0 with a configuration dialog box in Windows
Control Panel
the LS172 is a DUAL CAN card (PCI or ISA)
♦ PVI components update (PVI manager, INA2000 line)
15
1.2.3 Neue Funktionalitten in AS V2.1.5.0
1.2.3.1 Automation Software V2.1.5.0
(entspricht AS V2.1 + SR (1 bis 4))
Automation Studio, Automation Runtime
Automation Desktop, NC Software
♦ Libraries with source text are no longer overwritten when changing the operating
system. The library upgrade dialog box is shown. (ID#48880)
1.2.3.1.1.2 New NC−SW−version:
♦ 1.2.3.1.1.3 ACP10 V0.492

♦ 1.2.3.1.1.4 NC150 V1.210 (instead of V1.200)
♦ 1.2.3.1.1.5 NC154 V5.414
♦ 1.2.3.1.1.6 NC156 V5.414
♦ 1.2.3.1.1.7 NC157 V5.414
♦ 1.2.3.1.1.8 NC158 V5.414
♦ Documentation:
− The WinWord documents for ACP10−SW are installed again
♦ V2.28
♦ Y1.55
1.2.3.2
Allgemeine Informationen
1.2.3.2.1 Vorgangsweise bei der Installation des Service Pack (von B&R Downloadarchiv):
• ALLE B&R Automation Software Programme BEENDEN

• Starten der Selbstextrahierenden Datei "AS210SPx_Ger.exe" (Service Pack) bzw.
"AS210SRx_Ger.exe" (Service Release). Geben Sie den Pfad bekannt, in dem die Dateien
entpackt und gespeichert werden.
• Es wird automatisch die Datei "ServPack.exe" gestartet
Stimmt die zu erneuernde B&R Automation Software−Version und die Sprache berein, kann im
eingeblendeten Dialog mit dem Schaltfeld "Start Service Pack" die Installation gestartet werden.
Stimmt die Sprache des Service Pack mit der des installierten B&R Automation Studios nicht
berein, oder ist keine B&R Automation Studios Version V2.1 installiert, wird das Schaltfeld nicht
aktiviert.
• Nach dem Start der Installation werden die Daten auf dem Datentrger ausgetauscht.
16
1.2.3.2.2 Anmerkungen zur Service Pack Installation:
• Abhngig von den installierten Komponenten knnen beim bertragen der Dateien teilweise auch
englische Texte angezeigt werden.
1.2.3.2.3 Enthaltene Dateien
1.2.3.2.3.1 im Wurzelverzeichnis:
Liesmich.pdf (diese Datei)

Data.z
Disk1.id
ServPack.cfg
ServPack.exe
ServPack.ins
Setup.ini
Setup.pkg
1.2.4 New Functions for AS V2.1
Automation Studio, Panel Studio, AutomationNet (PVI), AutomationRuntime, WindowsCE
Automation Desktop, Motion Components, Visual Components, Automation Runtime version

and libraries
♦ Source Code Protection

All source files can now be assigned a password and stored safely. The user can
only open the protected files with the assigned password; when compiled, file
protection is temporarily removed.
♦ Setting font and colors for the editors
The font and color settings for the editors can now be defined using the
Extras\Options menu choices.
♦ Generate Transfer List (to simulate a download)
♦ Download in service mode
If the PLC is in service mode when the download is started, the PLC is set back to
service mode after resetting the target (cold restart, warm restart) during the
download.
♦ Display the scope of the variable in Watch
♦ Display the address of the dynamic variables
♦ Software tree view saved
When a project is closed or the software register is exited, the current software tree
view is saved and will be displayed the next time the project is opened.
♦ Permanent variables for m68k defined directly in variable declaration
Process variables can now be created directly in Automation Studio (Register
Permanent) in the permanent memory area on the PLC. The memory area must be
managed by the user. No automatic shifting of the variables or offsets when
changing a data type or the variable.
17
♦ C Debugger now shows which lines are not removed during optimization
There were often problems in line coverage or when setting breakpoints in a C task
because the C compiler removed certain instructions during optimization. In online
mode, the lines which are still available after optimization are now shown.
♦ Import/Export of data types
Data types can now be imported and exported using the data type editor
♦ Support of the IF370 in B&R Automation Studio
♦ Checking variable assignments in the IEC languages
Now, the data type is monitored for assignments. If e.g.: a UDINT variable is
assigned to a USINT, an error message in now given because the entire range of
the UDINT variable cannot be saved in the USINT. Explicit type conversion (cast)
allows this error message to be corrected.
♦ Checking the input parameters (data types) for function calls in Automation Basic
and structured text
The input parameters for FBK calls is now also checked. If e.g.: a UDINT is given for
a function input instead of a USINT variable as expected, an error message occurs.
Explicit type conversion (cast) allows this error message to be corrected. For
outputs, the check takes place in the other direction.
♦ Instructions with multiple lines in Automation Basic
It is now possible to create instructions with multiple lines in Automation Basic. The
character " \ " marks a line break.
e.g.:
ab01var = \
ab02var + ab03var
♦ Range monitoring for field variables in the IEC languages
A function is available that now allows the user to carry out range monitoring for field
variables. This function delivers a field variable to the current index with each
access, the minimum and maximum index. The user can now decide in a function if
the index it to be limited or if an error (CPU in Service) should be entered.
♦ Project global setting for back end of a C task
− under Project/Settings/Compile & Transfer, the back end option can now be
selected for all C tasks to overwrite variables and the data type declaration.
♦ With Build All, there is now a division for which variables and constants are to be
deleted.
♦ Curve calculations in Trace and in the Cam Editor

− Execution of mathematical operations with curves as variables (e.g.: subtraction or
multiplication of 2 curves).
− digital Butterworth high and low pass filter 2nd degree
− Fourier Transformation
− Differentiation of curves
♦ CSV format for saving and loading curves in Trace and in the Cam Editor (replaces
Excel format)
♦ ACOPOS Documentation is part of the online help
♦ New Functions in Visual Components 2.1

♦ The major updates for Version 2.1 have been made in the following areas:
♦ Project creation with color display
♦ Process images shown using color possibilities available on the target system.
Possibility to use a variable to control the colors (16 bit value − high byte foreground,
low byte background color). This allows visibility to be controlled during runtime and
18
blink effects can be created.

♦ Expanded Font Possibilities
♦ "True Type Fonts" are supported on the graphic target system. Any fonts and
symbols from Windows can be added to a project. The fonts are always shown with
fixed character widths on the visualization device − proportional fonts are converted
respectively. Please note that some fonts are copyrighted.
♦ Status Variables
♦ With the help of the status variables, displaying objects can be switched on and off
(bit 0). Entry can also be disabled during runtime (bit 1). For INA Client
communication, an "Edit" bit has been added (bit 15 − set or reset by the Interpreter,
while an entry field is being edited).
♦ Screen Saver
♦ Any process image can be defined as screen saver and is automatically shown after
a set delay.
♦ Uniform Input and Output Fields
♦ Assigning explicit data types is no longer necessary when configuring input and
output fields. There are only numeric and alphanumeric input and output fields. The
scaling size is automatically set.
♦ Variable Scaling
♦ Scaling and value limitation for fields can also take place using variables.
♦ SVGA / XGA
♦ In addition to the existing VGA panels (640*480), SVGA (800*600) and XGA
(1024*768) panels can also be configured with up to 256 colors.
♦ Editor − Grid Functions
♦ The editor can arrange static objects such as lines, rectangles and ellipses in levels
using the shortcut menu. Pressing the "CTRL" key allows horizontal or vertical lines
as well as squares and circles to be drawn. The settings for the grid can be defined
directly using the grid icon menu in the toolbar. The objects can be positioned with
pixel precision or using the defined grid.
♦ Button and Hotspot
♦ These new elements are only for Touch displays. Buttons can be configured as
desired (size, with and without bitmap and/or text, color and function). Blink effects
are possible using color variables.
♦ Hotspots are invisible switches (touch sensitive areas). This allows invisible
switching functions to be placed at certain locations. The representation can be
configured using bitmaps or line graphics.
♦ List Boxes
♦ With this output field, a list of texts can be shown on the display, the texts can be
output from a text group or a process variable. A text can be shown highlighted.
Selecting the highlighted text takes place using a process variable.
♦ Key Levels
♦ With shift keys, panel keys can be used to enter up to 4 different characters per key.
Other key functions can only be configured on the first level.
♦ Split Download
♦ The project is divided over multiple modules. Bitmaps and fonts, which make up the
majority of a project, are packed in a module. This module only has to be transferred
again if bitmaps or fonts have been added or changed. This greatly reduces the
download time during the development phase.
♦ Multiple Projects
♦ Multiple CAN panels can be operated on a CPU. A CAN panel can also be operated
parallel to a VGA visualization device. Each panel is configured in a separate
project.
♦ API Expansions
♦ The API interface was changed because of the possibility to execute multiple
projects on the target system. New functions include possibilities to read the Touch
coordinates, set contrast and brightness and read alarms.
♦ Necessary changes in existing projects can be found under Upgrade of Visual
Components 2.0 Projects.
19
♦ Data Point List

♦ All variables used in the individual pictures can be saved in a text file. This list can
be used to further process INA CLIENT FBKs.
♦ Decimal Point Representation
♦ Fields with decimal representation can also be entered without without the decimal
point key.
♦ Alarm System
♦ Saving the historical alarm list takes place in a data module. Printing the alarms on
IPC based devices is possible using the parallel interface.
♦ Increment/Decrement
♦ With the help of a button, a variable can be incremented or decremented in steps.
Optionally, a repeat function and upper/lower limits can be configured.
♦ Jog Keys
♦ Using an API function, jog key functions (key matrix) can be programmed based on
the task classes. This allows priorities to be set for reading keys.
♦ Variable Color Palette
♦ The color palette of 256 colors can be adjusted in a project specific manner. If
multiple shades of a color are required, the palette can be defined in the editor.
♦ Color palette settings can also be changed during runtime via API. This is helpful
when creating fade−in and fade−out effects. (Only valid for I386 systems with VGA
controller)
1.2.4.1.1.4 Automation Runtime version and libraries
♦ i386 Targets Beta Version Y1.51

♦ m68k Targets Version V2.27
♦ SRAM Lib for AR102
AutomationRuntime Library to access SRAM on the IPC2001/2002
♦ Ethernet ( UDP / TCPIP ) and Eth_Sock (BSD Socket) for m68k and i386
Communication libraries with UDP/TCPIP or BSD sockets
♦ Modbus for m68k and i386 (RTU Slave and Master, ASCII Master)
Communication library for Modbus protocol
♦ DRV_3964 for i386
Communication library for 3964R protocol
♦ FileIO for i386 (starting with Y1.39)
Library for data access
♦ DataObj for m68k and i386 (starting with V2.26 or Y1.39)
Library for accessing data objects (data modules, etc.)
♦ IOCtrl for m68k (starting with V2.25 and only for System2003)
Library to control the System 2003 IO cycle
♦ Dvframe for i386
Library for serial communication
♦ AsMath for i386
Library for mathematics functions
♦ LoopCont for i386
Library for closed loop controller
♦ PPDpr for i386
Library for memory access on parallel processors
♦ AR000 contained in setup
Demo PLC as Windows task
♦ WebServer for i386
For our AutomationRuntime targets (AR10x and CP360) there is only one
WebServer. With this module, ASP documents (home pages) can be created on the
target which can be viewed in a browser. These ASP documents can show variable
values and writing to variables is also possible. An ftp server is direct integrated in
the operating system.
Error Corrections
20
1.2.4.1.2 Panel Studio
1.2.4.1.3 V 1.3.4
♦ PVI is enabled by Panel Studio.

♦ Resource texts are output correctly.
♦ A&P32700:
Copying fields, changing variables works without Assign.
♦ A&P40275:
Crash when changing pictures and with input order switched switched on has been
corrected.
♦ A&P38015:
In multilingual projects, the text was output incorrectly after being moved in the
picture.
PVI, PVI Control, PVI Tools
1.2.4.1.4.1 PVI
♦ PVI Manager can be operated in Windows NT / 2000 as NT service (program

arguments: /Install, /Deinstall). Service operation is signaled with a different icon.
♦ Support of the LS172 in Windows NT 4.0 and Windows 2000
the LS172 is a DUAL CAN card (PCI or ISA)
♦ CAN support for Windows 9x (InaCAN and DCAN)
♦ DCAN line manages dynamic data lengths
the DCAN line now delivers the length of a received CAN frame
♦ DCAN line supports extended frames (29 bit identifier)
♦ Support of multiple modems (INA2000 and NET2000)
multiple modems can now be operated on a computer at the same time
/IF=modem(1..9)
♦ INA2000 CAN: max. number of nodes 255
♦ VarAccess Control
Control for transparent access of variable values
♦ PVIListBox Control
Control for entry of values using selection from a list
♦ UniCode Support
respective VB Controls (Microsoft Forms 2.0 Object Library, PVIListbox,
PVITextbox) can now use UniCode texts
♦ Export/Import of resource files as CSV, UniCode Txt
♦ Alignment for PVITextboxControl
alignment in PVITextboxControl can now be specified
♦ Max / Min value monitoring in PVI Textbox Control
♦ Switch the Connection Description for Logical Tags
using the methods Get and SetConnection, the connection parameters for PVI
Objects can now be read or edited. (switch from COM1 to COM2, change the station
number in the network, etc.)
♦ Support of multiple configuration files in an application (a separate configuration file
for each form)
♦ Support of AR010 and AR000 (Shared Memory)
♦ Support of MiniNet
♦ Read and write arrays with Read and WriteTag
♦ Read and write structures with Read and Writebuffer
21
1.2.4.1.4.3 PVI Tools
♦ PviTransfer Tool (Service Tool)

Setting up controller, reading and setting variables, deleting memory, upload of
modules to the PLC
♦ PviLogView Tool
for simple display of PVI log files
1.2.4.1.5.1 AR Y1.51
♦ Installation Kit / Setup

◊ When creating the installation diskettes for AR10x, a bootable image is now
copied to the first diskette. The user no longer needs a bootable diskette.
◊ Setup for the AR010 now gives a warning that this is the setup for the
AR010 and not the setup for an installation kit
◊ The setup for the AR010 now checks if this is an NT4.0 computer
♦ AR Basis (i386)
◊ Overload handling implemented in CAN_xopen (Y1.40)
◊ New "DefaultGateway" parameter for Ethernet in Sysconf (Y1.46)
♦ CP360
◊ PP boot implemented (Y1.41)
♦ AR102
◊ Error handling for transmit error from the LS172 implemented (Y1.40)
◊ Timestamp for CAN frames taken from the LS172 (Y1.40)
♦ AR105
◊ Support for new VGA chip in Provit 5000C and 5600C (Chips & Tech 69030)
(Y1.48)
1.2.4.1.6 WindowsCE
1.2.4.1.7 B2.0.0.7
♦ WinCE Runtime V3.0

◊ PVI and PVI Controls are integrated in image
◊ Supported protocols and interfaces
− Ina2000 serial and CAN
− Net200 serial
1.2.5 New Functions for AS V2.0
Automation Studio, AutomationNet (PVI), Panel Studio,
Automation Desktop,
♦ Visual Components,
which can be used to create visualization application (integrated in the B&R
Automation Studio user interface).
22
♦ MEMCARD Update Assistant,

which can be used to save individual projects on a MEMCARD and loaded to the
CPU using a MEMCARD insert.
♦ New Functions
◊ Save project as
◊ Double−clicking on the address error or bus error in the logbook opens the
C−source at the respective position.
◊ Error logbook can be saved as file
♦ Support of Automation Runtime for i386 target systems
◊ Remanent Variables
◊ Default initialization value for variables is 0
♦ Support of the product family B&R Power Panel (PP21, PP41)
♦ New and updated libraries:
◊ AsTime V1.00
◊ BrSystem V1.10
◊ IF361 V2.01
◊ IF661 V2.03
◊ IOConfig V1.01
◊ IO_lib V2.30
◊ LoopCont V1.01
◊ SYS_lib V1.36
♦ New and updated system modules
◊ Burtrap V1.36
♦ New PLC Software V 2.25 (m68k)
♦ New AR Software Y1.35
♦ New and updated help:
◊ Help files for dynamic TPU libraries (CP474, CP478, CP774, IP151, IP152,
IP161, IP350)
◊ Help files for system object SPSIOMAN and PBIXMAN
♦ Software Licensing
♦ Help files for dynamic TPU libraries (CP474, CP478, CP774, IP151, IP152, IP161,
IP350)
♦ Motion Components
◊ Cam profiles for ACOPOS servo drives
◊ Control of ACOPOS servo drives using multiple CAN interfaces
♦ PVI Core (PviMan.exe 1.60, PviCom.dll 1.60):

− Along with bit addressing (variable addressing), now all data types
permitted in the process object can be output in the link object (up to now,
this was only possible with BOOLEAN).
− When converting types with type STRING, all bytes from the string end to
the buffer end are filled with binary 0's.
− Access type CONNECT in mode "path name": When writing, the output of
".." is no longer required (in "single name" mode, the syntax remains as
previously) − Updated Cast.Mode: With CM=2, the string value is always
interpreted as a decimal number when converting data from string to integer.
− A ReadRequest DATA on an internal process variable object without valid
data returned error 12013 instead of 0−data (can be switched off with
PviMan VersionStyle < 1.54)
−Variable addressing update.
−Optimization: (declaration of event variables)
− Variable addressing update.
♦ PVI Monitor (PviMon.exe 1.60):

− New input dialog box for log components.
23
− Updated input dialog box for manager parameters (parameters: Auto−Exit,

Priority).
− Automatic connect in "Remote" operating mode after program starts ("/remote"
argument).
− New function for displaying the PLC operating system version (Menu: Help −>
PCC System Versions).
♦ PVI Data Logger (PviLog.dll 1.55):
− If the date/time stamp is turned off, then an ascending log number is output.
− Backup function ("LogBackup"), see online documentation.
− Break functions ("BreakStr" and "BreakTime"), see online documentation.
♦ PVI Communication Library (PviCom.dll 1.56.2):
− New initialization parameter "AS" for Autostart mode: AS=0 −> PVI manager is not
automatically started
♦ INA2000 Line (BrBase.dll):
−Optimization: Variable values were no longer updated after downloading the task if
the task was already on the PLC.
− new file BrBase.dll
♦ NET2000 Line (LnNet2.dll 1.53, Net2000.dll 1.51):
− CANCEL error (or object release) from Read/Write jobs between NET2000 frame
request/response. Response frame was incorrectly evaluated.
− Station management − if the station object is in an error state, frame retry is shut
off.
− The /SR (Suppress Ident Retry) parameter default was changed from SR=0 to
SR=1.
♦ B&R Security Check:
− Display licenses (license module and all connected B&R Security Keys).
♦ Configuration DLL (PviCfg.dll 1.50):
− New functions "PviCfgGetProgress" and "PviCfgGetLineText".
♦ OPC Server (2.08):
− New
♦ Devices (InaFrm.dll 1.55):
− Optimization ("Application hangs on CLOSE" is changed)
− New device "AR010" added (only WindowsNT)
− Driver change on LS251 (correction of crash and performance problems, "Loss of
Frames" is corrected)
− Optimization − TCP/IP Device
♦ Help files in the global help directory relocated
♦ Configuration DLL (PviCfg.dll 1.50):
− New functions: "PviCfgGetProgress" and "PviCfgGetLineText" (use new OPC
server)
Configuration DLL optimization (OPC server error display)
♦ Addition of FAQs in the help system (PVIDLLInterface and PVIControl)
♦ new module "NC INITPARAMETER" to generate InitParameter modules from an
ASCII file.
♦ Default value for the Windows socket port number has been changed from 2048 to
20000.
1.2.5.1.3 Panel Studio
1.2.5.1.3.1 V 1.3.3
Reference version for modification descriptions
1.3 Error Corrections are documented for the following versions

Error corrections in Service Release 2.2.1.2
Error Corrections in AS V2.2 Service Packs and Service Releases
24
Error Corrections in AS V2.1 −> AS V2.2
Error Corrections in AS V2.1 −> AS V2.1.5.0
Error Corrections in AS V2.0 −> AS V2.1
1.3.1 Error corrections in Service Release 2.2.1.2
Automation Runtime, Automation Studio, Automation Net, Versions Changer, Panel Studio
AR102, AR105, CP360, i386−Based, Libraries (i386), m68k−Based, Libraries & System
Modules (m68k), PPx1
1.3.1.1.1 AR102
♦ The system clock's time leap (after a cold restart) has been corrected (ID#11731)
♦ Online communication breakdown has been corrected (ID#12551)
If several online connections were routed via an AR102, it was possible that one of
the routed connections failed after a period of time
1.3.1.1.2 AR105
♦ Cycle time violation when accessing the hard drive has been corrected (ID#8423).
♦ Crash when erasing non−existent permanent internal variable areas has been
corrected (ID#12361).
1.3.1.1.3 CP360
♦ Problems with RS485 communication on IF6xx modules have been corrected

(ID#11096, 54325).
♦ Time delay when booting the CP360 without Ethernet has been minimized
(ID#12706).
1.3.1.1.4 i386−Based
♦ Changes made to the cycle time tolerance for task class 8 (ID#54620).
Default values were adjusted to task class 4 by m68k target systems.
♦ Problems when debugging libraries corrected.
♦ CAN Bus Off handling implemented.
1.3.1.1.5 Libraries (i386)
♦ Support of the "Time" data type when reading variables using INA
An error message appeared if an attempt was made to read a variable of data type
"Time". These variables can now be read.
♦ Conversion of FileIO to asynchronous functions (ID#55050)
Problems accessing defective data mediums were fixed with this conversion.
♦ FlexIQ
− I/O data module was limited to 64k
− If variables whose names were longer than 32 characters were entered into the I/O
data module, and they were not present on the AR,
then memory was overwritten when the error message was entered.
1.3.1.1.6 m68k−Based
♦ Crash when uploading synchronously and simultaneously deleting the same module
(ID#55860)
♦ Configuring timer devices possible in Sysconf (ID#50520)
If Error# 75 is entered in the logbook after the CPU was restarted, then the number
of timer devices was too small. Beginning with V2.30 (X5.53), this number can be
configured.
25
♦ Problems with the Applader corrected (ID#12921)

♦ If a power failure occurs during downloading, then memory which has already been
reserved is no longer freed up (ID#13176)
This problem affects CPUs with DRAM (2010 CPUs, CP260, LS251)
1.3.1.1.7 Libraries & System Modules (m68k)
♦ Support of the "Time" data type when reading variables using INA
An error message appeared if an attempt was made to read a variable of data type
"Time". These variables can now be read.
♦ Memory leaks in the CANIO library corrected (ID#14210)
♦ Support of ME020 and EX101 for CAN I/Os (ID#40660, 36880)
♦ Access monitoring for IOConfig
IOAlloc and IOFree now check status 0x0bdb −−> semaphore busy
♦ System module: fbtcpip
Stack was increased and problems with deinstallation corrected
♦ System module: tcpipdrv
Adjustments carried out for V2.30
1.3.1.1.8 PPx1
♦ Error corrections in the I/O Manager for PPx1
♦ If the data type of global variables was changed, then sometimes not all tasks were
recompiled (ID#55690).
♦ Crash when browsing in the Ladder Diagram corrected (ID#56265)
A crash occurred if a variable was copied and then ESC and PageDown were
pressed.
♦ Crash when closing the IEC editor with the Window/Close menu entry corrected.
♦ If tasks were imported with library constants, then, during compilation, the library
was also recompiled (ID#54915).
♦ Target memory was entered incorrectly (ID#53390)
If a data module from a PG2000 project was imported and then transferred with a
project list, then the module was transferred into the incorrect target memory.
♦ Faulty entry for timer device in the sysconf (ID#53075)
If a further parameter in the sysconf was changed after modifying the timer device,
the timer device settings were overwritten.
♦ Function block interface cleared (ID#54900, ID#54810)
If older projects were opened and/or compiled with old libraries, the FBK interfaces
could be cleared.
♦ Structure definition for i386 could not be translated (ID#50135)
♦ Crashes when debugging in Windows XP corrected (ID#54565)
♦ Shortcut menu in the tracer was not displayed in Windows 98 (ID#53275)
♦ Source texts for C Libraries were no longer found when double clicking on function
names, if the project was located in a path with empty spaces (ID#49920)
♦ Faulty IL generation corrected (ID#53620)
♦ Problems when copying FBK calls and renaming the instance variable corrected
(ID#53210)
♦ Description for the receive timeout changed from ms to character delay (character
time)
♦ Slaves for local expansion were no longer detected at hardware upload (ID#53590)
26
♦ Analog CAN IO's for CM211 and CM411 modules could not be imported (ID#53235)
♦ Crashes during printing (if no printer had been installed) were corrected (ID#52985)
♦ Profiler crash for Windows 98 corrected (ID#54415)
♦ Profiler crash after aborting the booting process was corrected (ID#53485)
♦ Profiler restart after aborting the booting process was not possible (ID#53320)
♦ Incorrect Profiler module transferred (ID#52275)
Evaluation of the hardware type is made using project hardware. If there was an
online connection to another hardware type, an incorrect Profiler module could have
been transferred to the Target.
♦ The shortcut menu was not displayed using Shift−F10 in the Profiler (ID#12266)
♦ Problems when transferring data in function blocks corrected (ID#48750)
If several FBKs are called in a nested manner, a problem could occur when
transferring BOOL variables
♦ modified error message if CAN IOs are used in task class 5−8 (ID#11666)
♦ Problem of SFC Task import an export with large ladder diagramm network fixed
(ID#55210)
♦ wrong warning of IEC Code generator removed (ID#54235)
If an integer number is compared with a calculated integer number in an IF
statement, a warning is given by the code generator. (i.e. if var = konst1 /1 then)
♦ Select statement was not processed correctly if state, select or endselect were used
as variable names (ID#52035)
♦ The list of Automation Basic keywords and operators are updated (ID#51870)
♦ If recursive pointers was used in structure definitions, the entry of the data types into
the project database was wrong(ID#53240)
♦ Debugging of SFC Task >= 64k caused a crash of the Automation Runtime
(ID#56235)
♦ LineCoverage and Debugging was not working anymore in some C Tasks
(ID#54540)
If the name of the C file in the software tree did not correspond (case sensitive) to
the names of the C files on the hard drive, then the corresponding debug information
was not found.
♦ Problem of debugging libraries on i386 targets fixed (ID#52785, 52765, 52720,
52665, 52660, 52380, 49315, 12186, 12166, 12161, 10791, 10726, 10716)
♦ Shortcuts in menu "Debug" updated (ID# 52705)
♦ Crash after opening the serial Interface configuartion dialog in a C221 project fixed
(ID#54185)
♦ if String areas are used as function lock interface, they were wrong entered into the
header file (ID#55150)
♦ Crash after starting debugger for a C Task under WXP fixed (ID#54565)
♦ Memcard Update Manager transfers all system modules, before the Update
Memcard will be created (ID#55865)
♦ Memory Leaks removed (ID#54930, 56075, 56105)
1.3.1.2.2 Motion Components
♦ The user can supress the warnings "Warning: the record with index '.....' has ParID
zero."and "Warning: The value of parameter '....' in the record with index '....' could
not be retrieved." (which can occur relatively often for each trace data buffer) after
the first error is shown.
If ParID zero is recognized during interpretation of network trace data, the evaluation
of the data was previously aborted with the message "Failed to evaluate a record.
Error while evaluating the network trace buffer !".
Now a warning is shown in this case, and the evaluation will be continued after
acknowledge of the warning.
♦ If an new INIT parameter module for the NC157 was created with AS V2.2 and
assigned to an NC object on an NC157 module, during the compilation of the NC
objects from the second NC157 module on a network interface index not equal to
27
zero was entered into the INIT parameter module . This caused the following error
message to be shown when opening NC watch, NC test and NC trace for such INIT
parameter modules:
"Object '..............' is not on target! Function is not possible!"

♦ If projects, in which INIT parameter modules for NC objects after the second NC157
module were created with AS versions before V2.2, have been opened with AS
V2.2, the following behavior occured:
The INIT parameter module was not shown in the hardware configuration for the
respective NC object, but NC watch, NC test and NC trace could be operated in the
software tree.
♦ In the "Trace Options" property page, times larger than 1000.0 seconds can now be
entered (e.g. for continuous load measurements).
♦ If the NC−Manager version was changed after inserting an NC157 and then an
ACOPOS servo drive was added to the hardware configuration for the NC157, the
NC−Manager was overwritten (with the latest version of the NC−Manager).
♦ If the "Trace Options" property page was closed and opened again, a ParID
previously entered manually as trigger parameter was deleted.
♦ The motor parameters "motor_type and encoder_type" for an OEM motor were not
updated if the encoder type was changed for the AC123 encoder card in the
hardware configuration.
♦ If the address of the general NC configuration list on the PLC had the value zero
(e.g. because no NC manager was existing on the PLC), then an address error
occurred on the PLC when using NC watch, NC test and NC trace.
Now a corresponding error message is displayed.
♦ If an NC−Manager version is overwritten with itself, all tasks that use the
NC−Manager are recompiled even if the header files and archive files have not
changed.
Now the tasks are only recompiled if the change date for the header files and
archive files for the NC−Manager have changed.
♦ The settings (e.g.the type of memory on the PLC (User Rom, MemCard, etc.) the
NC−Manager is loaded to) are lost when the NC−Manager version was changed.
Now the setting are kept when changing versions.
♦ When Trace Data was loaded from a floppy disk and this floppy disk was removed
from the drive afterwards, it was not possible to print out the Trace data.
♦ OEM motors with EnDat encoder:
The parameters of an OEM motor connected to an AC120 can be edited in
Automation Studio as well as in the corresponding .mpd file.
During compilation the parameters were not written to the *cfg.br file (e.g.
acp10cfg.br) and therefore not transferred to the controller.
♦ Saving a trace without charts:
After opening a trace that was closed after deleting all charts, the message box
"Internal Application Error" was shown.
♦ Cam editor:
An error message was shown if an ACOPOS cam was defined with too many
segments or polynomials (more than 63).
From now on it is possible to define 64 segmets or polynomials; the error message
has been modified.
♦ Network command trace:
If ACP10 software was used with more than one network interface and several
requests for the same node number were sent on different network interfaces before
the response to the first request has been received, then the responses could not be
assigned to a unique request.
♦ Cam editor:
When closing the cam editor the user was reminded to save the cam even if no
changes were made.
♦ Inserting ACOPOS drives::
If during insert dialogue the name of a not existing INIT parameter module was
28
entered by the user, then the INIT parameter module was created even then, after
inserting of ACOPOS was rejected because of an error.
1.3.1.2.3.1
Visual Components editor
◊ Crash when exchanging hardware if the VC editor was open.

(ID#19928)
◊ Crash when opening an existing project − only in specific projects.
(ID#19928, ID#54730)
◊ Crash when compiling specific projects. (ID#20328)
◊ When an error message appears in the output window, a
double−click on it will now jump to the corresponding page where
the object is marked. (ID#16128)
◊ Handling improved when inserting text groups. (ID#53060)
◊ Type filter was adapted for bar graphs. (ID#53150)
◊ Project was compiled even if there weren't any changes. (ID#53260)
◊ Changes in the color palette were not applied during compilation.
◊ Negative values could not be displayed in Simulation Mode.
◊ The key matrix index was calculated incorrectly when an AT
keyboard was used. (ID#20628)
◊ Variable cannot be connected (internal data bank is now updated).
(ID#20028)
◊ Correction for password input field in Locked Mode. (ID#20528)
◊ Touch button configuration, behavior when inputting incorrect values
was adjusted. (ID#20728)
◊ Internal data type structure adjusted. (ID#20928)
◊ Empty text groups could not be edited after they were imported.
(ID#21028)
◊ Keys which were not used were also compiled; memory consumed
on the target system. (ID#21128)
◊ Input behavior adjusted for all dialog boxes. (ID#21528)
◊ Bitmap was not updated in the editor after being edited. (ID#53145)
◊ Warning that no alarm printer is connected was removed.
(ID#19528)
◊ Text group texts assigned to a touch button could not be edited.
(ID#54800)
◊ The AlphaPad and NumPad bitmaps could be used as background
bitmaps. (ID#53480)
◊ Corrections in the online help. (ID#53340, ID#53600, ID#53920,
ID#53915, ID#54855, ID#54295, ID#53915, ID#53845, ID#53165)
1.3.1.2.3.2
Visual Components Runtime
◊ Touch button hung if two keys were pressed at the same time.
(ID#84895)
◊ Refresh response was corrected for the active focus.
Visible/Invisible switching didn't work for the active focus.
(ID#53085)
◊ The first touch action after changing pages was ignored. (ID#53395)
◊ Font height for NumPad and AlphaNumPad input was not checked.
Font height is now checked and the next smaller font is used if it
cannot be displayed in the NumPad. (ID#53450)
◊ Visualization application was not started correctly if the alarm
system was used on m68k target systems. (ID#20228)
◊ Ends of fields were not cleared for advanced text output fields when
switching texts. (ID#54645)
29
1.3.1.3 Automation Net
PVI Control, PVI Configurator, PVI Transfer, INA2000, PVI Manager
1.3.1.3.1 PVI Control
♦ PVI Control methode "ReadResource" doesn't work, if spaces are included in the
resource name(ID#54230)
♦ Memory Leaks using PVI Textboxes fixed (ID#57405)
1.3.1.3.2 PVI Configurator
♦ Addresses of process variables can be longer than 255 characters.

♦ Tag names can now be longer than 80 characters.
♦ Sub groups with identical names have not been possible (ID#50330).
1.3.1.3.3 PVI Transfer
♦ Printing of multiple pages does not work properly (ID#12366).

♦ Using a relative path for the log file in some cases caused a crash (ID#54715).
♦ If the PVI manager was in "LOCKED" mode, the procedure could not be started
(ID#12076).
♦ Problem when deleting a nonexistent module.
♦ Opening a PIL file larger than 64 KB, caused a crash.
♦ If the option "Stop PVI Manager automatically" in the PVI monitor was selected, a
connection to the target system could not be made (ID#54795).
♦ Editing the command Read or WriteVariable the selected data type get lost
(ID#57400).
1.3.1.3.4 INA2000
♦ /DAIP parameter was not evaluated correctly (ID#54965)

If several Automation Runtime targets with the same node number but different IP
addresses were addressed, then the same target was always reached. The
evaluation of the IP address (/DAIP) was left out.
♦ Connection disruptions via Ethernet were corrected (ID#57450)
If small amounts of data (1 byte reference data) were transferred via an existing
Ethernet connection, then the connection was interrupted.
1.3.1.3.5 PVI Manager
♦ Problems with the hysteresis function corrected (ID#54245)

♦ Default values for process variables (ID#923)
Preset values for variables can now be set using the DV parameter
♦ Updates for CAST functions
CAST functions (CM=xx) were expanded. More detailed information can be found in
the PVI user documentation.
1.3.1.4 Panel Studio
♦ communication problems are fixed

Problems with an incompatible communication library are fixed
♦ System close button deactivated while switching.

♦ CR/LF ID removed in the registration entries.
♦ PVITransfer or PVIControl entries recognized.
♦ List entries in the status field cleared when switched several times.
30
1.3.2 Error Corrections AS V2.2 Service Packs and Service Release
1.3.2.1 Automation Software V2.2.0.18 − SP
(contains error corrections from SP1)
Automation Studio
Automation Desktop
♦ The contents of SFC tasks (ladder diagram steps) were not printed correctly
(ID#37195)
♦ Long variable names in ladder diagram tasks were shortened when printed
(ID#12446)
♦ Crash occurred when importing an SFC task with more than 2 nested SFC levels
(ID#53175)
♦ If a variable named step was used in an SFC task, then importing the task was
cancelled without an error message (ID#11901 and ID#51995)
♦ The PLC crashed if a new step was inserted with a breakpoint in an SFC task and
the task was then transferred to the PLC (ID#51475)
♦ Step names, qualifiers, or action names could be overwritten by tooltips (ID#51430)
♦ Changes in SFC tasks could only be saved in the uppermost level. Changes could
not be saved when in a subeditor (ST, LAD, IL). (ID#51390, ID#51405)
1.3.2.2
1.3.2.3 Automation Software V2.2 SP1
Automation Studio
Automation Desktop, Motion Components
♦ Crash when starting the MemCard Update Wizard corrected (ID#52975)

♦ CAN IO master was no longer found after changing over to V2.29 (ID#52790, 53015,
53205)
♦ On the PPx1, the screw−in modules were inserted twice or were deleted for slots 1 −
3. (ID#53020)
♦ Profiler crash for Windows 98 corrected (ID#52395)
♦ Default Sysconf for AR010 V2.60 missing in Setup (ID#53005)
♦ If modem support was activated for i386 targets, then an error was output during a
Build
♦ SS1.IF2 was entered as an interface string in the NC CFG module when an

ACOPOS device was inserted to a CAN interface of a 3IF787.9. SS1.IF1 would be
correct.
♦ Information entered manually was overwritten by the default values when the NC
Manager CFG module version was automatically upgraded.
31
♦ A crash occurred if an IF module was exchanged with a second IF module

connected to an ACOPOS device in the hardware configuration and then it was
deleted. This error has been corrected by updating the internal data structures.
1.3.2.4 General information
1.3.2.4.1 Installation Procedures for the Service Pack (from B&R Download Archive):
• Close ALL B&R Automation Software programs.

• Run the self−extracting file "AS220SPx_Eng.exe"(Service Pack) or "AS220SRx_Eng.exe"(Service
Release). Specify the path in which the files are to be decompressed and saved.
• The "ServPack.exe" file automatically starts.
If the correct B&R Automation Studio version and language are selected, a dialog box appears. Click
on the "Start Service Pack" button to start the installation. If the language of the Service Pack does
not match the installed B&R Automation Studio program, or if B&R Automation Studio V2.2 is not
already installed, this button will not be activated.
• After installation begins, data will be copied to the data medium.
1.3.2.4.2 Service Pack Installation Notes:
• Depending on the installed components, English texts may sometimes be displayed when
transferring files.
1.3.2.4.3 Included Files
1.3.2.4.3.1 In the root directory:
ReadMe.pdf (this file)

Data.z
Disk1.id
ServPack.cfg
ServPack.exe
ServPack.ins
Setup.ini
Setup.pkg
1.3.3 Error Corrections − AS V2.1 to AS V2.2
Automation Studio, NC Software, Automation Net (PVI), Automation Runtime, PG2000
32
♦ "LN" function (AB) could not be called (ID#48530)

♦ After Monitor mode starting/ending, the position in the IEC editor remains the same
(ID#47080)
♦ When importing C libraries with source code, now all source text files located in the
project path are entered relatively in the data bank. This way, the project can also be
edited in a different directory.
♦ Different data module sizes corrected between V2.0 SP5 and V2.1
did not terminate binary numbers in the data module with a "," ; a larger data type
was recognized by the data module compiler (ID#49790)
♦ LAD crash corrected for branched LAD lines (ID#49680)
♦ LAD problems with the "Search in File" function corrected (ID#49630)
♦ Upper/Lower case problems when searching in LAD corrected (ID#49635)
♦ LAD problems when deleting networks corrected (ID#50755,50775)
♦ LAD FBK copying without having to declare the new FBK again (ID#49855)
♦ SFC − if a non−declared variable is used in a transaction, the variable declaration
area now opens up. (ID#49690) (ID#49690)
♦ ST − "MOD" function could not be called (ID#48625)
♦ Software tree was not updated correctly when a module was deleted in the runtime
system
♦ Crash when saving C files larger than 600 kB corrected (ID#46885)
♦ The "library information not transferred to the target system" switch was not
considered for the Update Memcard Wizard (ID#45705)
♦ Warnings in the Update Memcard wizard are now output at the start of the transfer,
not just at the end (ID#47745)
♦ AB − after opening a project, the current line display works once again (ID#47025)
♦ AB − a long search string (over 80 characters) caused a crash (ID#46330)
♦ AB − key combination Ctrl + F (search function) did not work in online mode
(ID#45920)
♦ LAD − problems with nested LAD networks corrected (ID#46940)
♦ LAD − after copying networks from V2.0, the task could no longer be opened
(ID#47270)
♦ A negative value was not allowed at the end of a line in a data module (ID#46215)
♦ Problems with permanent variables corrected (performance with W2k ID#46000)
(memory clearing ID#46725)
♦ If changes are made in the global declaration without saving, compilation is not
carried out (ID#5890) (if something is changed in the variable, data type, etc.
declarations, and the line is still active (hasn't been left), these changes were not
saved)
♦ The IEC task was no longer recompiled after modifying a data type in a C task
(ID#45280)
♦ Error corrections when importing m68k projects... (AS could crash when importing
Sysconf) (ID#45355, ID#9996)
♦ The directory for permanent variables is not entered in the HWC file on 2010 CPUs
(ID#46790)
♦ User library *.a files are only created when first called (ID#45885)
♦ If a library is needed by a system module, AS tries to import it even though it already
exists in the project (ID#45680)
♦ Task description clears out umlauts (ID#46830) − software tree is not constructed
completely (ID#46795)
♦ start number of a task without source is not changed (ID#45350)
♦ individual bytes in the byte array can no longer be entered in string. Input now
possible again (ID#46550)
♦ A data bank error could have occurred if a library error message was displayed in
the output window and a double−click was used to return to the source text file
(ID48145)
33
♦ C libraries with constants were compiled an additional time after a Build All
(ID#48440)
♦ When adding C libraries with source text, the source files paths were always entered
as absolute (ID#47610)
♦ LAD − if a function block output of type ANY was connected with a function block
input of type ANY, than an intermediate variable of type BOOL was used (ID#48135)
♦ LAD − if a single line network was created with a normally opened contact as an
input contact and a pos./neg. transition coil as an output, the editor crashed
(ID#49025)
♦ LAD − comments are incorrectly displayed when the comment box is reopened after
inserting comments during ladder diagrams and using "Shift + Enter" for line breaks.
This problem mainly occurs with Microsoft XML libraries (msxml.dll). This problem
has now been fixed (ID#49195)
♦ LAD − if function blocks were used without an output, the ladder diagram task could
no longer be opened (#ID49330)
♦ LAD − double−clicking on error messages in the LAD output window did not lead to
the error location (ID#11116)
♦ PVI manager crash caused by incorrect input parameters was corrected (ID#49400)
♦ AB and ST compiler errors corrected (ID#48085)
♦ Division functions which could return an incorrect result now produce a warning
when compiling
(i.e.: USINT divided by SINT and SINT is negative => incorrect result) (ID#49105)
♦ Data module could not be opened in online mode (ID#49640)
♦ Data module was switched to online mode when "Find in Files" was selected
(ID#11446)
♦ LAD variables from the previous network were overwritten if a function without an
input was used in the LAD (ID#48895)
♦ Structures could not be attached onto the "address" FBK (ID#48885)
♦ SFC crash when importing a task corrected (ID#49605)
♦ ST − "len" was recognized as a function in the ST editor and therefore was written in
capital letters. Problem when using function parameter names which were written in
lowercase in the function (ID#43215)
♦ "Generate Transfer List" no longer deletes modules on the PLC. In addition, the
memory monitor is now skipped when the transfer is simulated (ID#50145)
♦ "Insert Library" dialog box was enlarged. Libraries paths are now visible. (ID#49620)
♦ Problems selecting colors in McTrace and in the Cam Editor corrected

♦ .mpd files with more than 12 characters in the file name now function again (OEM
motors with long names)
♦ Importing a real axis into a project with CP360 − swapping was incorrect
♦ Tracing more than 4681 CAN records DWORD instead of WORD for CanDataSize
♦ Improved behavior when repeating a trace
♦ Automation Studio could crash when printing axis structures
♦ ACOPOS cam profiles were not translated back in Automation Studio
1.3.3.1.1.3
♦ Activation of alphanumeric levels if switching to an alphanumeric input field

(ID#52445)
♦ Input behavior corrected when "Shift Decimal Point" function is activated (ID#52355)
♦ Crashes corrected in the editor (ID#52200,52130,49875,49245,14828,13928)
♦ Up/Down corrections (ID#51750,49410)
♦ Input behavior corrected when AlphaPad is used (ID#50955)
♦ Key functions were incorrectly compiled when more than 255 pictures were used
(ID#50950)
♦ Visapi samples located in Help corrected (ID#50600)
♦ The cursor hung when controlled by Goto Input if input fields overlapped (ID#50575)
34
♦ LED status was not accepted by the C130 during the booting phase (ID#50565)
♦ Bitmaps could not be placed over the background bitmap defined in the global
picture (ID#50340)
♦ Boolean variable as status variable when VC objects used (ID#49950)
♦ Crash corrected for variable scaling of input fields (ID#49935)
♦ Corrections and updates in Help (ID#49925,49785,49665,48800,48795)
♦ Error behavior of "Momentary Byte Hot Spots" and "Touch Buttons"
♦ Incorrect scaling of input fields (ID#49320)
♦ Output error when maximum bargraph amplitude used (left/right) (ID#48920)
♦ Variable search logic improved in variable dialog box (ID#48820)
♦ LED failure when hiding a VC object − error corrected (ID#48715)
♦ Scaled UINT variables were output in a position too far to the left ID#48105)
♦ 16 bit bitmaps are automatically converted into 256 color bitmaps (ID#47510)
♦ Alarm system filter did not function on m68k targets (ID#14728)
♦ Text import correction (ID#14028)
ACP10, NC15x
1.3.3.1.2.1 ACP10
V0.502, V0.500, V0.495, V0.494, V0.493, V0.492, V0.491, V0.490, V0.478, V0.477, V0.475,
V0.474, V0.473
V0.502
♦ Because of an error in the basic FPGA, it is possible that the operating system no
longer works correctly after the system is started. Only the ERROR LED or the
ERROR LED and RUN LED are lit. The LEDs on the plug−in modules AC112 or
AC110 are not lit. Network communication was not possible.
This error only occurred in 8Vxxxx.00−2.
V0.500
• AC130 Incremental Encoder Emulation:

Drive synchronization failed when activating incremental encoder emulation.
• Message FIFO:
With cyclic error messages, it is possible that the error FIFO was empty, even though the
bits for "Warning" and "Error" were set in the cyclic status.
V0.495
• AC130 Incremental Encoder Emulation or AC123 SSI Encoder:

A hardware reset occurred if the drive controller was switched on when changing to one of
these encoder types. The controller can no longer be switched on during the change.
• Command "Delete System Modules":
System modules (BsLoader, operating system) were not deleted. This error was present
since V0.490.
V0.494
• Torque Calculation for Asynchronous Motors:

The calculated torque was too low.
• Current Offset Measurement:
Measuring the current offset took place when the inverter was switched on, therefore false
offset values occurred depending on the switching frequency and the cable length. Now the
current offset measurement takes place with the inverter switched off.
35
• When downloading a data block, errors were not entered into the user data (neither in the
message record, nor in the data block user structure). This error was present since V0.491.
V0.493
• CAN Objects for Cyclic External Set Value Entry Mode 2:

The CAN ID "Write Response Channel 3" and "Cyclic User Data to the Drive" was assigned
the same CAN object. Therefore, only read−write channel 3 or cyclic user data functioned
depending on the order that the parameters were set.
• CAN Objects for Cyclic External Set Value Entry Mode 2:
A read response for a broadcast command was sent on channel 3. This caused errors 6015
and 6016 or an error during trace upload.
• Over−current Emergency Stop:
In V0.492 and V0.491, over−current monitoring was deactivated. Therefore an emergency
stop was not triggered if an over−current occurred.
• Simulation Mode:
If the DC bus was loaded before starting simulation mode, a lag error then occurred during
an active movement in simulation mode.
V0.492
• AC120 EnDat Encoder:

If disturbances occurred during SSI transfer to the EnDat encoder, the ACOPOS device
could not initialize the encoder. In this case, the transfer is now reinitialized.
If the EnDat encoder is not connected, the software reset takes too long. The NC Manager
could be interrupted with the error message "Incorrect boot status after software reset".
• Power Limitation for Over−voltages:
If the DC bus voltage increases over 770 V and the brake current reaches the maximum
value (returned power limiting active), the following error occurs:
The motor accelerates for the duration of the emergency stop with the brake current listed
above from power limiting.
Error Scenarios:
Over−voltage occurs when all servo drives have a brake resistor over−temperature, delay
limit parameters are set too high or over−voltages are measured because of DC bus voltage
disturbances.
• The CAN controller for 8Vxxxx.00−2 is not able to accept CAN telegrams with CAN bus
acknowledge when booting following a software reset or NC system start. Therefore the NC
Manager interrupts the initialization of an ACOPOS device with a response timeout error (for
the read request after "Read Boot Status"), if only ACOPOS 8Vxxxx.00−2 devices are
connected to the CAN bus.
• The option "+ncINIT" for the NC action
"ncSERVICE+ncPAR_SEQU,ncDOWNLOAD+ncINIT" was ignored. This error was only
present in V0.491.
V0.490

Incorrect absolute positions could occur with inductive multi−turn encoders. This error was
present since V0.475.
• Encoder in Slot 4 (Encoder 3):
If an encoder error occurred, the "Reference position valid" status was not cleared. This error
was present since V0.475.
• Movement Interrupted and Emergency Stop:
The movement interruption and the position controlled emergency stop were always
initialized with acceleration 0. Therefore the target position could be exceeded because the
acceleration had to be built up.
36
• AC130 Digital IO Cards:

An encoder connected to the AC130 was not initialized.
• Simulation Mode for AC120 EnDat Encoder:
After switching off simulation mode, an EnDat motor encoder was not initialized. This error
was present since V0.475.
• Encoders in Slot 3 and 4 (Encoder 2 and 3):
When coupling to the external actual position ENCOD2_S_ACT or ENCOD3_S_ACT, the
filtered position ENCOD2_S_ACT_FILTER or ENCOD3_S_ACT_FILTER was used (should
not have been used).
• External Cyclic Set Value Entry Mode 2:
Protection against sending the actual value too soon if there is a lot of jitter for the sync time
stamp.
V0.478
• If the NC Manager idle time task for trace data upload is interrupted for a long time between
the last test to determine if the telegram was already sent and the timeout check (e.g. by a
higher priority user idle time task), then a request timeout error (number 32061) could occur
even though the request telegram was sent correctly.
• Controlling the Power Supplies for the Plug−in Modules:
If an ACOPOS servo drive was equipped with several plug−in modules with high power
consumption, the operating system start failed. The error mainly occurred when using the
AC123 with ACOPOS 1640 and 128M.
V0.477
• With BsLoader V0.480−0.484, the download of system modules (BsLoader, operating

system) was interrupted because of an error when reading the the NC hardware version.
This error was present since V0.475.
V0.475
• AC130 Digital IO Cards:

In the AC130 error records, the wrong number was shown as additional information.
V0.474
♦ Software Reset:
The response telegram on a software reset was not sent if the bus was heavily loaded.
V0.473
• Emergency Stop, Movement Interrupted:

The motor spins out during an emergency stop or when a movement is interrupted in speed
control mode.
• AC120 Endat Encoder, Determining the Position:
Endat encoders with a resolution higher than 2^14 analog increments were not supported.
1.3.3.1.2.2 NC15x
V5.420, V5.415, V5.414
V5.420
♦ If the NC action "ncCNC_SPS/ncINIT" was carried out in the MotionComponents

test, then the internal data of the function nccnccom() was not initialized (because
the INIT handshake for the "normal" NC object was checked instead of the test NC
object).
37
♦ In "bewegung.ncprogramm.start_pos" in the NC object (type "ncCNCSYS"),

"ncHAUPTPRG" is now entered as INIT value. Then this value does not have to be
selected in the NC object test before starting an NC program.
V5.415
• NC157:
The positions for external encoders are now only calculated when using an external encoder.
V5.414
• CNC:
The new restart for G200 now also functions for G201.
The programmed zero point offset (G92) was shown in the zero point monitor for tangential
and linear axes even after they were deselected.
PVI, PVI Controls
1.3.3.1.3.1 PVI
♦ Data changes with event variables could be lost (ID#46760)

♦ WebServer demo functions once again (ID#46625)
♦ Problems corrected when connecting a text resource to a UserControl (ID#49210)

♦ Scaling with the scroll bar didn't work (ID#48070)
♦ Problems with the comma and period in the PVI text box corrected (ID#46685)
♦ BOOL variables are incorrectly represented in the PVI text box (ID#46395)
♦ A crash could occur in PVI AddIn if the VB project was located on the network
(ID#50975)
♦ Crash corrected when double tag names were present (ID#47880)
♦ Memory was no longer cleared when switching languages (ID#50205)
♦ If the format of a value was changed in the PVI Textbox, then this value was
transferred to the PLC again
(i.e. PLC value 123 => after formatting shown = 12 => then was reverse formatted
and the value 120 was transferred to the PLC) (ID#50915)
♦ Relative path specification with .\Path\*.svr was not supported for the resource file
(ID#49485)
♦ AddIn runtime error 70 corrected when ending the application, if form as MDIChild =
TRUE (ID#51930)
♦ Configurator crash − if the group name was not closed with the Enter key is
corrected (ID#47285)
♦ If a tag name was input a second time with copy/paste, then an endless loop
occurred in the PVI configurator (ID#47885)
♦ The position in the Properties dialog box was not displayed correctly if several
controls were placed on the form (cursor position was not in the visible range)
(ID#51925)
AR V2.60, AR V2.29 ,AR V2.28
1.3.3.1.4.1 AR V2.60
♦ AR Base (i386)
◊ Problems with tNetTask (Ethernet driver) corrected
This module requires some of the 60ms computing time
◊ Problem with time adjustment corrected
38
◊ Problem with lost files corrected (ID10381, 10021)

1.3.3.1.4.2 AR V2.29
♦ AR Base (m68k)
◊ INA CAN connection breaks off with error entry "14827" and "8840 −
INA2000 CAN: No Rx buffer free" in the error log (ID#50780)
◊ INA Ethernet connection breaks off with error entry "14918 − WARNING:
Routing: assignment error of sent frame" in error log (ID#50380)
◊ Free USERRAM space became smaller when frequently downloading the
same project in USERRAM without booting in−between (ID#49255)
♦ PP41
◊ Communication error when using a interface module IF6xx serial interface in
the PP41 expansion slot (EX101) (ID#49395)
1.3.3.1.4.3
1.3.3.1.4.4 AR V2.28
♦ AR Base (m68k)
◊ Reserved memory was not freed up when connection interrupted during an
online connection
◊ Error corrected when quick switching of physical connection (RS232
switching box) (ID#44635)
◊ When installing modules, the priority of called tasks was lowered only during
cyclic operation, not during booting (ID#45335, 45345)
♦ CP260
◊ Problems with Flash components corrected
♦ CP476
◊ Analog IOs did not function on the CP476 anymore if HSTC1 was present
(ID#47010)
1.3.3.1.5
1.3.3.1.6 PG2000
V2.44
♦ With larger ladder diagrams (approx. 300 lines), sometimes lines at the end of the
diagram were removed when the ladder diagram editor was opened (ID#47170,
46710)
1.3.4 Error Corrections − AS V2.1 to AS V2.1.5.0
1.3.4.1 Automation Software V2.1.5.0
(AS V2.1 + SR (1 to 4))
Automation Studio, Automation Runtime
Automation Desktop, Visual Components
♦ If a library error message was shown in the output window and the user double
clicked in the source text file, a data bank error could result (ID#48145)
♦ C libraries with constants were compiled again after a Build All (ID#48440)
♦ When adding C libraries with source text, the path of the source files was always
39
entered as absolute (ID#47610)

♦ if a function block output of type ANY was connected with a function block input of
type ANY, an intermediate variable of type BOOL was used (ID#48135)
♦ if a single line network was created with a normally opened contact as an input
contact and a pos./neg. transition coil as an output contact, the editor crashed
(ID#49025)
♦ when inserting comments in the ladder diagram and using "Shift + Enter" for line
breaks, comments are incorrectly displayed when the comment box is
reopened. This problem occurs mainly with Microsoft XML libraries (msxml.dll). This
problem has been fixed. (ID#49195)
♦ if function blocks were used without an output, the ladder diagram task could no
longer be opened (ID#49330)
♦ double clicking on error messages in the output window did not lead to the error
location (ID#11116)
♦ Find in Files... did not function in ladder diagrams with intermediate variables
(ID#49630)
♦ Case was not taken into account while searching (ID#49635)
♦ A crash occurred in the editor if the graphic information of an individual network was
deleted along with the comment (ID#50755)
♦ A crash occurred in the editor if several networks were deleted (ID#50775)
♦ Network was not completed correctly (ID#51645)
♦ Network was not completed correctly (ID#53620)
♦ Status LEDs were incorrectly controlled (ID#49750): After loading the program to the
PLC, the status LEDs (Run, Error, Mode and Ready) were lit although the target was
in Run Mode.
♦ Project update with visual components objects.
Because the text data format in SR1 has already been changed, it is absolutely
required to carry out an update. Runtime versions < 1.12.2 (SR1) are no longer
compatible for compiled Visual Component projects. The problems which occurred
on SR1 with the update of V2.1 were repaired. Compiling the VC project is still
necessary so that the runtime components version corresponds to those of the VC
project.
♦ status variable was updated: On images with several input fields, the input field with
the current focus (active) can be queried using a status variable. This presumes that
each input field is assigned a different status variable. Bit 14 is placed in the status
word of the input field which is currently active.
♦ Changing the KeyLevel using the control program: Previously, the KeyLevel could
only be evaluated by the control
program (level 0−3). Starting with SR2, the level can also be set by the control
program (Value > 3 = KeyLevel 0).
♦ Scaling: If an input/output field activated scaling directly after assignment of a
variable of data type > USINT, then no PLC value > −128 to 127 could be input. The
dialog box must be closed without scaling and reopened so that the data type limit
can be reset.
♦ Field length: The field length could not be changed before assigning a variable. Now
the field length automatically sets to the character length of the appropriate data type
(i.e. UDINT − 10) and can later be changed.
♦ Triggering the LED with the PLC: A variable assigned a key LED was not displayed
in the Visual Components variable overview.
♦ Copying a static text: The color and status variable are now used.
♦ Increment / Decrement function: In order to assign a decrement function, a negative
increment (i.e. −1) must be used. This was not accepted correctly (error number
65535).
♦ Background Bitmap: Assigning a status variable to a background bitmap was not
accepted.
40
♦ AS crash: When deleting a picture or when closing / compiling, a crash was fixed in
3 projects.
♦ C130 – Lines: In SR1, slanted lines were supported in the editor on the C130.
However, since this function is not supported by the C130, these were converted to
pixel positions by the CAN driver and specified in individual CAN frames. This
caused a very slow picture generation. This function was kept out of the editor in
SR2 – only horizontal and vertical lines are able to be drawn.
♦ Text groups without names: If a text group was created without a name and a text
for this text group was inserted right away, AS crashed.
♦ Scaling: When using scaling for UINT values with decimal places and the lower limit
was > 0, then when a limit violation occurred, "*****" were displayed.
♦ C130 – Locking input fields using status variables: If an input field was locked by a
status variable and not by a password in a C130 project, the input field was switched
to invisible but could still allow input but it could not be closed.
♦ C130 – Several C130s on one PLC: After a warm restart, there were problems
controlling LEDs on 2 different C130 displays.
♦ C130 with character displays: The key matrix reset itself when a key was pressed for
a long time.
1.3.4.1.2.1 AR Basis (m68k)
♦ Reserved memory was not freed up when connection interrupted during an online
connection
♦ Error corrected when quick switching of physical connection (RS232 switching box)
(ID#44635)
♦ When installing modules, the priority of called tasks was lowered only during cyclic
operation, not during booting (ID#45335, 45345)
1.3.4.1.2.2 CP260
♦ Problems with Flash components corrected

1.3.4.1.2.3 CP476
♦ Analog IOs did not function on the CP476 anymore if HSTC1 was present
(ID#47010)
1.3.4.2
1.3.4.3 General information
1.3.4.3.1 Installation Procedures for the Service Pack (from B&R Download Archive):
• Close ALL B&R Automation Software programs.

• Run the self−extracting file "AS210SPx_Eng.exe" (Service Pack) or "AS210SRx_Eng.exe"
(Service Release). Specify the path in which the files are to be decompressed and saved.
• The "ServPack.exe" file automatically starts.
If the correct B&R Automation Studio version and language are selected, a dialog box appears. Click
on the "Start Service Pack" button to start the installation. If the language of the Service Pack does
not match the installed B&R Automation Studio program, or if B&R Automation Studio V2.1 is not
already installed, this button will not be activated.
41
• After installation begins, data will be copied to the data medium.
1.3.4.3.2 Service Pack Installation Notes:
• Depending on the installed components, English texts may sometimes be displayed when
transferring files.
1.3.4.3.3 Included Files
1.3.4.3.3.1 In the root directory:
ReadMe.pdf (this file)

Data.z
Disk1.id
ServPack.cfg
ServPack.exe
ServPack.ins
Setup.ini
Setup.pkg
1.3.5 Error Corrections AS V2.1
Automation Studio, AutomationNet (PVI), AutomationRuntime
Automation Desktop, Motion Components
♦ Revision of the LAD editor

(A&P
45840,44365,44360,44070,43185,43085,42920,42865,42665,40325,40155,38925,
38880,38875,37595,37295,36865)
♦ Error correction in UpdateMemCard Wizard
(A&P 44310,40905,40675,40890)
♦ Performance problems in Windows 2000 and Windows XP solved (problem caused
by a Windows API function)
♦ All source files (C task) in the *.pgp folder are now saved relatively (A&P 39595)
♦ Indication of if this is a relative or absolute shown in the status bar (A&P23890)
♦ When adding software objects (C task) which are in the *.pgp folder, you are no
longer asked if the file should be copied to the CPU directory
♦ Error message when saving or compiling if source or BR files are write protected
(A&P44665)
♦ Error correction for LineCoverage in AB and ST
♦ Error correction for nested IF instructions in AB
♦ Debug file for C task is now created in XML format
a. Debugging large C tasks now also possible in W9x
b. Performance improvements for large C tasks
♦ Error corrections in SFC Editor
♦ tcpipdrv, Ethernet now also for PP41 and PP21 (A&P40655)
♦ IF361 Lib performance improvements
♦ LoopCont software dependencies entered correctly (A&P41830)
42
♦ Net2000 Slave on i386 now delivers same structure as on m68k

♦ Management of multiple RIO masters
♦ DA_ Functions are removed form sys_lib for i386, function could not be guaranteed
on i386. dataobj should be used as replacement
♦ for pv_xgetadr with dynamic PVs, it is now possible to determine if you want the
values for the pointer or the contents of the pointer (A&P42985)
♦ if a FBK is changed in the LibManager from upper to lower case or from lower to
upper case, the *.a file is now created correctly again (A&P44105, 43625, 34010)
♦ Managing the RIO_slaves on the LS251 / representation was incomplete (A&P
43375,43675,43670)
♦ Curve calculations in Trace and in the Cam Editor

− Execution of mathematical operations with curves as variables (e.g.: subtraction or
multiplication of 2 curves).
− digital Butterworth high and low pass filter 2nd degree
− Fourier Transformation
− Differentiation of curves
♦ CSV format for saving and loading curves in Trace and in the Cam Editor (replaces
Excel format)
♦ Acopos Documentation is part of the online help
1.3.5.2
PVI, PVI Control
1.3.5.2.2 PVI
♦ in the INA2000 line, all resources used are released after canceling the connection
♦ CAN driver: the controller is automatically reinitialized when the BusOff state occurs
♦ Error correction for an incoming call in W9x (W9x crashed if PVI recognized an
incoming call)
♦ Error correction for Read/WriteRequest after connection interruption (if a
ReadRequest or WriteRequest occurred on the connection immediately after the
connection was interrupted, the request could be held up)
♦ MININET Line (LnMini.dll 2.00):
− Crash when ending with a broken connection was corrected.
− Crash if VT parameter is not given was corrected
1.3.5.2.3 PVI Controls
♦ PVI Configurator switch for cast to string, so that no octal values are written if there
is a preceding zero
♦ PVI Control method ReadResource now also supports UniCode strings
♦ dynamic variables can now also be imported
1.3.5.2.4.1 AR Y1.51
♦ AR Basis (i386)
◊ crash of InaClient FBKs (Y1.51)
◊ AVT entry for CANIO FBKs also in service mode (Y1.48)
◊ optimization (approx. −25%) of the CANIRQ Handler (Y1.48)
43
◊ zero pointer inquiry when deleting CAN objects (1.47)

◊ remanent local PV data was not deleted during a cold restart (Y1.46)
◊ correction VxWorks Ethernet Configuration (PING) (Y1.45)
◊ DBTRACER: crash in LineCoverage corrected (Y1.42)
◊ incorrect data or time in error logbook (Y1.42)
◊ CAN task priorities taken from the registry
◊ ExitSP (_EXIT) not called in Service Mode
♦ CP360
◊ new PLD file (error accessing PCI interface) (Y1.50)
◊ Correction in basic address calculation for IF060/IF6xx on CP360 system
bus (Y1.49)
◊ new CP360 bus FPGA file (bit handling, error correction for XP152 DPR
access) (Y1.41)
♦ m68k
◊ CM471 Manager functions with CP474 again starting with V2.27
1.4 Known Problems and Deficiencies are documented for the

following versions
Known problems in Service Release 2.2.1.2
Known Problems and Deficiencies in AS V2.2
Known Problems and Deficiencies in AS V2.1
1.4.1 Known problems in Service Release 2.2.1.2
Automation Runtime, Automation Studio, Versions Changer
CP360, AR102 InstallKit, AR105 InstallKit
1.4.1.1.1 CP360
♦ If the CP360 boots without a network connection, then Ethernet communication can
no longer be started while it is running.
♦ After an operation system update the Powerlink IO nodes 3EX282.6 of series 2005
must be restarted.
♦ the functons of library FileIO can not be used anymore for the InitUp routine.
1.4.1.1.2 AR102 InstallKit
♦ After these setup files are installed, only installation diskettes for operating system
V2.61 can be created. However, if operating system V2.60 is required, then the
current installation kit must be uninstalled before installing the V2.60 installation kit.
1.4.1.1.3 AR105 InstallKit
♦ After these setup files are installed, only installation diskettes for operating system
V2.61 can be created. However, if operating system V2.60 is required, then the
current installation kit must be uninstalled before installing the V2.60 installation kit.
44
♦ Crash occurs when overwriting large source blocks with paste in the C Editor (MS
Control problem)
♦ Beginning with AS V2.2, only AR V2.60 and higher can be used for i386 target
systems
Existing i386 projects must be reconfigured and Sysconf (Syedit) settings are
rejected (task class time, IP addresses, interface parameters for CAN and serial,
memory allocation, CAN IO parameters)
♦ Data type monitoring in the Ladder Diagram editor relaxed; no direct monitoring of
data types when input
♦ The Automation Studio Tracer can only be used if Motion Components was installed.
The Trace recording object requires Motion Software program libraries.
♦ If Office XP is installed on the machine, then Automation Studio could crash if the
Online Info dialog box is opened. When Office XP is installed, the registration for the
MS Calendar control is destroyed. Other applications which use this object can also
no longer be used (VB applications, VC applications). To remedy this, the MS
Calendar control has to be reregistered in the Windows 'System' or 'System32' path.
♦ Setting key matrix priority

This option only works ith the "Lower TC#4" setting (used as the default setting).
♦ Problems can occur during object registration in Windows 9x.

Error Message: Out of environment space.
Solution: Expand memory area.
1.4.2 Known Problems and Deficiencies in AS V2.2
Automation Studio, NC Software, AutomationRuntime
♦ a crash occurs when overwriting large source blocks with copy and paste in the C
Editor (problem from MS Control)
♦ only AR V2.60 can be used with AS V2.2 in i386 projects
♦ existing i386 projects must be reconfigured and Sysconf (Syedit) settings are
rejected (task class time, IP addresses, interface parameters for CAN and serial,
memory allocation, CAN IO parameters)
♦ data type monitoring in the ladder plan editor relaxed, no direct monitoring of data
types when input
♦ the Automation Studio Trace only can be used, if Motion Components are installed.
The Trace Object needs some program librarys from Motion software.
45
♦ 'Values' are not adapted in Chart Properties (#11646).

♦ The Status Bar is not updated ( or the Automation Studio crashes) when a message
of a PVI status change occurs during the Trace Options Property Sheet is open.
♦ When a cam profile ist printed, the first derivation is also printed although not
selected and shown in Properties/Display (#52165).
♦ The "Formulas"−Tab is not shown correctly when the Properties dialog is opened
during zooming (#11746).
1.4.2.1.1.3 Visual Components / Automation Studio Setup
♦ the Microsoft XML 3.0 setup program needs the Microsoft Installer. This system
upgrade could be installed with Microsoft Internet Explorer or is part of the Windows
operatingsystem (Windows ME, 2000, XP). If it is not installed on your computer,
you can find it on Automation Software CD in the directory
\WindowsAddOns\Msi\InstMsiA.exe for Windows 9x

\WindowsAddOns\Msi\InstMsiW.exe for Windows NT
NC15x
1.4.2.1.2.1 NC15x
♦ CNC axes settings are not initiallized correctly for axes , which are declared in the
INIT parameter module of a CNC object in the CNC axes settings (components
"achse[i].cncax.obj") that are a part of another NC154 (or NC157) module (so−called
"module external axes").
1.4.2.1.3
1.4.2.1.5 V2.60
♦ AR targets (except for CP360) cannot be updated from Y1.5x to V2.60 using
Automation Studio.
AR10x must be repartitioned and reformatted (necessary for secure B&R module
system; application data is now located in Partition2 and mirrored inPartition3 −−
System is located on Partition1)
♦ The new WebServer (webserv.br) must be used. The BR module is now located in
(...\Br_AS_220\As\System\V0260\i386\webserv.br)
1.4.3 Known Problems and Deficiencies in AS V2.1
Automation Studio, AutomationNet, Automation Runtime
46
♦ "Library information not sent to target system" not carried out by Update Wizard
(Strip Library Info)
♦ a crash occurs when overwriting large source blocks with copy and paste in the C
Editor (problem from MS Control)
♦ when importing a task, libraries in the project could be deleted (brsystem, etc)
♦ when transferring the operating system of Motion Components, the associated
manager must first be transferred to the PLC. Because a false download sequence
can occur in Automation Studio, the operating system (nc157sys, etc.) should be
deactivated during the first download. Transferring the operating system can be
started directly after downloading the associated manager and after the subsequent
cold restart.
♦ System requirements for new Visual Components Firmware

a. m68k starting with V2.26 and higher
b. i386 starting with Y1.50 and higher
♦ When updating VC Firmware, all modules may not be exchanged, please check
version V1.xx
1.4.3.2
1.4.3.2.1.1 PVI
♦ LS251 driver (PCI Bus) does not function in W2k (WXP)
1.4.3.2.2.1 AR Y1.51
♦ AR Basis (i386)
◊ No exception task on i386
◊ with AR000, a connection cannot be established for SharedMemory if the
PVI Manager is running as an NT Service
◊ CAN_open ignores baud rate from the FBK call if INA communication is
started in Syedit
♦ m68k
◊ Hardware upload of a PP21 does not function
47
48

2.2.1.2 Readme PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2.2.1.2 Readme PDF

Uploaded by

Copyright:

Available Formats

Information about B&R AutomationSoftware

Information about B&R AutomationSoftware

1.1 B&R Automation Software Service Release 2.2.1.2

Software Components on the Service Release CD Version

NC Software ACP10 for CAN V0.502

♦ Automation Runtime V2.61 (i386) 2.2.0.1306

1.2 New Functions are documented for the following versions

New Functions for AS V2.2

New Functions for AS V2.1.5.0

New Functions for AS V2.1

New Functions for AS V2.0

1.2.1 New functions in Service Release 2.2.1.2

Automation Runtime, Automation Studio, Automation Net, Version Changer

1.2.1.1 Automation Runtime

♦ If there are several assignments for interfaces

♦ Support for 5LS189.6

♦ New FTP server

♦ The number of parallel connections has been increased to 128.

♦ INA reinstall (ID#54885)

1.2.1.1.6 Libraries (m68k) + m68k Base

♦ INA Client updates (ID# 55115)

If (fbk_mode == LCPID_FBK_MODE_EXT_SELECTOR (new mode!!)) and (Y_fbk !=

New warning LC_WARN_LCPID_YFBK_LIMIT if Y_fbk stays under Y_min or

1.2.1.2 Automation Studio

Automation Desktop, Motion Components, Visual Components

1.2.1.2.1 Automation Desktop

♦ Loading project lists

1.2.1.2.3.1 General Information

◊ Several levels can now also be configured on control keys.

◊ VA_GetDiplay Info: Reads display resolution (i386).

1.2.1.3 Automation Net

1.2.1.3.1 PVI Control

♦ new function "Format" added

1.2.1.3.3 PVI Trend System

1.2.1.3.4 PVI Configurator

♦ Support of MTC Line

1.2.1.3.5 PVI Transfer

♦ Two additional commands for error handling have been introduced:

1.2.1.3.6 PVI Manager

♦ Default values for process variables (ID#923)

1.2.1.4 Version Changer

♦ Switching of PVITransfer or PVIControl versions now possible, without having AS

1.2.2 New Functions in AS V2.2

1.2.2.1 Automation Software V2.2

Automation Studio, NC Software, AutomationNet (PVI), AutomationRuntime, WindowsCE

1.2.2.1.1 Automation Studio

Automation Desktop, Motion Components, Visual Components, Automation Runtime Version

1.2.2.1.1.1 Automation Desktop

1.2.2.1.1.3 Visual Components

NC software ACP10_Powerlink V1.002 (corresponds to ACP10 V0.502 updated with Powerlink

• The NC action "ncGLOBAL,ncINIT" is NO LONGER automatically activated, if there is

• Cyclic Drive Operation (user data to the drive):

• Return Power Limit PGEN_LIM:

Enabling the warning:

aborted if the lag error is exceeded.

The limits can be read on the following parameters:

ISQ_MAX_UDC (REAL) DC bus voltage controller: Upper current limit

• E−stop for encoder signal failure of an asynchronous motor:

• Cam Profile Automat:

• Torque Limiter TLIM:

• Analog Signal Monitoring AC122:

• Cam Profile Automat:

E.g.: "Diagnostic Message" for enabling the speed limit: