0% found this document useful (0 votes)
29 views104 pages

Release Notes

Uploaded by

Sebek k
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
29 views104 pages

Release Notes

Uploaded by

Sebek k
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

IndustrialIT

Compact Control Builder AC 800M


Version 5.0.0/1

Release Notes
IndustrialIT
Compact Control Builder AC 800M
Version 5.0.0/1

Release Notes
NOTICE
This document contains information about one or more ABB products and may include a
description of or a reference to one or more standards that may be generally relevant to
the ABB products. The presence of any such description of a standard or reference to a
standard is not a representation that all of the ABB products referenced in this document
support all of the features of the described or referenced standard. In order to determine
the specific features supported by a particular ABB product, the reader should consult the
product specifications for the particular ABB product.

The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.

This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.

The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.

This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.

TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respec-
tive owners.

Copyright © 2003-2007 by ABB.


All rights reserved.

Release: March 2007


Document number: 3BSE033044D5001
Table of Contents

TABLE OF CONTENTS

About This Book


General ..............................................................................................................................9
Document Conventions ...................................................................................................10
Use of Warning, Caution, Information, and Tip Icons ....................................................11
Applicable Specifications ................................................................................................12

Section 1 - Introduction
Executive Summary.........................................................................................................13
Revision Record ..............................................................................................................14
Version Designation.........................................................................................................14
Software .............................................................................................................14
Libraries .............................................................................................................15
Hardware .............................................................................................................18
Product Support ...............................................................................................................18

Section 2 - Functionality Changes


New Functions .................................................................................................................19
General .............................................................................................................19
Engineering Environment.....................................................................................21
Control and I/O ....................................................................................................23
Alarm and Event...................................................................................................30
Standard Libraries ................................................................................................32
OPC Server for AC 800M ....................................................................................36
Discontinued and Replaced Functions and Units ............................................................36
OPC Transfer of Domain Files via MMS no Longer Supported .........................36
Downloading via PPP Makes it Impossible to read Compact Flash ....................36
OPC Server and MMS Server cannot be Launched from System Tray ..............36
Auto Log On from the Setup Wizard is not Possible ...........................................37

3BSE033044D5001 5
Table of Contents

Language Settings from Setup Wizard in Control Builder .................................. 37


Changed Menus in Project Explorer .................................................................... 37
Not Released Functions................................................................................................... 39

Section 3 - Compatibility
Compatible Hardware Modules ...................................................................................... 41
Compatible Firmware...................................................................................................... 44

Section 4 - Fixed Problems


Version 5.0.0/1 ................................................................................................................ 45
Administration ..................................................................................................... 45
Configuration ....................................................................................................... 46
Operational........................................................................................................... 50
Version 5.0.0/0 ................................................................................................................ 56
Administration ..................................................................................................... 57
Configuration ....................................................................................................... 59
Operational........................................................................................................... 69

Section 5 - Known Problems


Administration................................................................................................................. 75
Controller ............................................................................................................ 76
Communication.................................................................................................... 77
I/O Handling ........................................................................................................ 78
Operational ...................................................................................................................... 80
Control Builder .................................................................................................... 80
OPC Server .......................................................................................................... 80
Controller ............................................................................................................ 81
Communication.................................................................................................... 84
I/O Handling ........................................................................................................ 85
PROFIBUS-DP .................................................................................................... 89
Configuration .................................................................................................................. 90
Control Builder .................................................................................................... 90
Communication.................................................................................................... 94

6 3BSE033044D5001
Table of Contents

I/O Handling.........................................................................................................97
PROFIBUS-DP ....................................................................................................99
Instruction Manual Changes..........................................................................................100
Controller ...........................................................................................................100

3BSE033044D5001 7
Table of Contents

8 3BSE033044D5001
About This Book

General
This document provides a brief overview on functionality. It lists the problems that
existed in the previous version or service pack that were fixed and corrected in this
release. It also enumerates known problems encountered in the final testing of this
product release. Where possible the document identifies workarounds that help
overcome the problem. The document contains additional notes that may be
valuable to customers and service personnel working with the product. This
document replaces the existing release notes for the prior release and is included on
the product CD.
This document provides important information and information not contained in the
ordinary manuals, sales information, or other types of product information.
Refer to Compact Control Builder AC 800M when Control Builder is mentioned
in this manual.
Refer to OPC Server for AC 800M when OPC Server is mentioned in this
manual.
The term Modem refers to modems that are configured and controlled by a
controller. It does not refer to modems that are transparent for the controller.

3BSE033044D5001 9
Document Conventions About This Book

Document Conventions
The following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
• Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
• Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
• Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
• Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).
• The names of push and toggle buttons are boldfaced. For example, click OK.
• The names of menus and menu items are boldfaced. For example, the File
menu.
– The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: select File > New > Type.
– The Start menu name always refers to the Start menu on the Windows
Task Bar.
• System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name

10 3BSE033044D5001
About This Book Use of Warning, Caution, Information, and Tip Icons

Use of Warning, Caution, Information, and Tip Icons


This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:

Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.

Warning icon indicates the presence of a hazard which could result in personal
injury.

Caution icon indicates important information or warning related to the concept


discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.

3BSE033044D5001 11
Applicable Specifications About This Book

Applicable Specifications
This product meets the requirements specified in EMC Directive 89/336/EEC and in
Low Voltage Directive 72/23/EEC.
The libraries described in this document conform to the IEC 61131-3 Programming
Languages standard, except for control modules, which are not supported by this
standard.

12 3BSE033044D5001
Section 1 Introduction

This document represents the release notes for Compact Control Builder AC 800M,
Version 5.0.0/1.
This document provides a brief overview on functionality. It lists the problems that
existed in the previous version or service pack that were fixed and corrected in this
release. It also enumerates known problems encountered in the final testing of this
product [Link] possible the document identifies workarounds that help
overcome the problem. The document contains additional notes that may be
valuable to customers and service personnel working with the product. This
document replaces the existing release notes for the prior release and is included on
the product CD.

Executive Summary
This document covers the products listed in Version Designation on page 14.
This release of Compact Control Builder AC 800M (Version 5.0.0/1) is
compatible with Compact Control Builder version 5.0.0/0, 4.1.0/x, 4.0.0/0 and
Control Builder M version 3.2/7 (or later 3.2/x) with some reservations. See
section 3, Compatibility, for further information.
The manual Compact Control Builder AC 800M, Getting Started, Introduction and
Installation (3BSE041584R101) describes how to perform an upgrade.

3BSE033044D5001 13
Revision Record Section 1 Introduction

Revision Record
Table 1. Revisions

Revision Release Date Remarks


Version 5.0.0/0 October 25, 2006
Version 5.0.0/1 March 26, 2007

Version Designation
Software
Compact Control Builder AC 800M Version 5.0.0/1 contains software support for
the following products:

Released Software Version


• Compact Control Builder AC 800M 5.0.0/1
• Firmware for PM851/PM856/PM860 5.0.0/1
• Firmware for PM861(A)/PM864(A) 5.0.0/1
• OPC Server for AC 800M 5.0.0/1
• MMS Server for AC 800M 5.0.0/1
• Base Software for SoftControl 5.0.0/1
• IP Config 1.4.0
• Serial Firmware Upgrade 2.1.3
• RNRP 2.21

14 3BSE033044D5001
Section 1 Introduction Libraries

Libraries
There are two categories of libraries, see Libraries for new Applications on page 15
and Legacy Library Versions on page 18.

Libraries for new Applications


These libraries should be used for new applications.

Library Version
• AlarmEventLib 1.3-5
• BasicGraphicLib 1.0-4
• BasicLib 1.4-9
• BatchLib 1.0-8
• COMLICommLib 1.1-4
• ControlAdvancedLib 1.2-8
• ControlBasicLib 1.0-11
• ControlExtendedLib 1.1-5
• ControlFuzzyLib 1.1-11
• ControlObjectLib 1.0-8
• ControlSimpleLib 1.0-10
• ControlSolutionLib 1.0-6
• ControlStandardLib 1.2-11
• ControlSupportLib 1.1-6
• FFH1CommLib 1.0-6
• GroupStartLib 1.2-7
• IconLib 1.1-6
• INSUMCommLib 1.0-5
• MB300CommLib 1.0-5

3BSE033044D5001 15
Libraries Section 1 Introduction

• MMSCommLib 1.1-5
• ModBusCommLib 1.1-2
• ModemCommLib 1.0-5
• ProcessObjBasicLib 2.2-7
• ProcessObjDriveLib 1.2-9
• ProcessObjExtLib 2.2-9
• ProcessObjInsumLib 1.2-10
• S3964CommLib 1.1-2
• SattBusCommLib 1.1-2
• SerialCommLib 1.1-5
• SignalLib 1.4-7
• SupportLib 1.1-9

• ABBDrvNpbaCI851HwLib 1.0-0
• ABBDrvNpbaCI854HwLib 1.0-2
• ABBDrvRpbaCI851HwLib 1.0-0
• ABBDrvRpbaCI854HwLib 1.0-2
• ABBPnl800CI851HwLib 1.0-0
• ABBPnl800CI854HwLib 1.0-0
• ABBProcPnlCI851HwLib 1.0-0
• ABBProcPnlCI854HwLib 1.0-0
• BasicHwLib 5.0-0
• CI851PROFIBUSHwLib 1.0-0
• CI852FFh1HwLib 1.0-0
• CI853SerialComHwLib 1.0-0
• CI854PROFIBUSHwLib 1.0-20

16 3BSE033044D5001
Section 1 Introduction Libraries

• CI855MB300HwLib 1.1-7
• CI856S100HwLib 1.1-7
• CI857InsumHwLib 1.2-16
• CI858DriveBusHwLib 1.0-3
• CI865SattIOHwLib 1.0-8
• COMLIHwLib 1.0-8
• ModbusHwLib 1.0-7
• ModemHwLib 1.0-0
• PrinterHwLib 1.0-0
• S200IoCI851HwLib 1.0-0
• S200IoCI854HwLib 1.0-0
• S800CI801CI854HwLib 1.0-10
• S800CI830CI851HwLib 1.0-6
• S800CI830CI854HwLib 1.0-6
• S800CI840CI854HwLib 1.0-5
• S800IoModulebusHwLib 1.0-12
• S900IoCI851HwLib 1.0-1
• S900IoCI854HwLib 1.0-1
• S3964HwLib 1.0-6
• SerialHwLib 1.0-0

3BSE033044D5001 17
Hardware Section 1 Introduction

Legacy Library Versions


These libraries are compatible with Control Builder M version 3.2/7; they should
not be used for new applications.
Supplied manuals and online help do not describe these versions.

Library Version:
• CommunicationLib 1.0-0
• ProcessObjBasicLib 1.0-5
• ProcessObjExtLib 1.0-10
• SerialLib 1.0-0

Hardware
This release supports:
• AC 800M (PM851, PM856, PM860, PM861(A) and PM864(A))

Product Support
Contact ABB technical support for assistance in problem reporting.

18 3BSE033044D5001
Section 2 Functionality Changes New Functions

Section 2 Functionality Changes

The following changes characterize version 5.0.0/0 compared to version 4.1.0/0.


Version 5.0.0/1 does not add any new functionality.

New Functions
General

Coexistence of Controller Versions


Starting from version 5 and installing newer versions of Control Builder and/or OPC
Server does not require a controller upgrade. Controllers with different firmware
versions can coexist in the same network, and newer versions of Control Builder and
OPC Server can connect to controllers of older versions (not older than version 5).

Uninstall not Needed Before Upgrade


From version 5, it is not necessary to uninstall the current version of the product
before a newer version of the product is installed. Settings in the current version will
be kept during the upgrade. As a consequence of this, there is no version number on
the working folders anymore.

Migration Between Compact Control Builder AC 800M and 800xA


It is possible to move solutions between Compact Control Builder AC 800M and
800xA.
All migration between Compact Control Builder AC 800M and 800xA is done by
using Control Builder Professional. Migration cannot be done by using Compact
Control Builder AC 800M.

3BSE033044D5001 19
General Section 2 Functionality Changes

• Compatibility
It is only possible to migrate between 800xA and Compact Control Builder
AC 800M within the same version, that is it is not possible to migrate from
Compact Control Builder 4.1 to 800xA 5.0 and vice versa.
If a user want to migrate from Compact Control Builder 4.1 to 800xA 5.0, the
user must first upgrade the Compact Control Builder 4.1 project to Compact
Control Builder AC 800M 5.0, and then migrate to 800xA. The same applies if
a user want to migrate from, for example 800xA 4.0 to Compact Control
Builder AC 800M 5.0. In that case the whole system must be upgraded to
800xA 5.0, before a migration to Compact Control Builder AC 800M 5.0 can
be performed.
It is not possible to open an older Compact Control Builder project in the
current version of Compact Control Builder. The project must be upgraded
before it is possible to open the project. The Control Builder checks the build
version in the source code before opening any project.
• General constraints
It is possible to move a control project to 800xA only once.
It is not possible to migrate from 800xA to Compact Control Builder AC 800M
if the project contains AC 800M HI controllers, because it is not possible to use
HI controllers in the Compact Control Builder.
It is not possible to migrate projects, containing more than one version of a user
library, from 800xA to Compact Control Builder, because only one version of a
user library is supported in Compact Control Builder.
• Migration from 800xA to Compact Control Builder AC 800M
When migrating from 800xA to Compact Control Builder, it is only possible to
migrate complete projects. Migration of single libraries, applications,
controllers or types is not supported. If the user wants to migrate smaller
objects than complete projects, the user has to package them within a small or
empty project.
The migrated project are placed in the selected folder, together with all
applications and controllers within the project. All libraries (both POU and
hardware) that are user-defined are also placed in this directory.

20 3BSE033044D5001
Section 2 Functionality Changes Engineering Environment

• Migration from Compact Control Builder AC 800M to 800xA


When migrating from Compact Control Builder AC 800M to 800xA, it is only
possible to migrate complete projects. Migration of single libraries,
applications, controllers or types is not supported. If the user wants to migrate
smaller objects than complete projects, the user has to package them within a
small or empty project.
Before migrating, the user should ensure that all libraries that are used in the
project are available. Leave the libraries in the project folder, if they are placed
there. If libraries that are used in the project are placed in the “Libraries” folder
structure, this “Libraries” folder must be placed at the same level (in project
explorer) as the folder that contains the project to migrate. This is necessary to
be able to find all libraries used in the project.

Engineering Environment

Support for Chinese


The Control Builder user interface, that is the menus and dialogs are translated into
Chinese.

Library Handling
• Hardware libraries
Hardware libraries replace the built-in hardware types that were loaded into the
previous Control Builder version at startup. A hardware library contains
definitions, protocol handlers and firmware for one or several hardware units.
From a user point of view, the hardware libraries are similar to POU libraries
(create, version handling, state, password protection, source code handling
etc.). User-defined hardware definitions (output from Device Import Wizard)
are also stored in hardware libraries. The hardware libraries are structured after
a group of hardware, for example S800CI840CI854HwLib, that contains S800
units that can be used together with a CI840 and a CI854. A complete list of
Hardware libraries delivered with the Control Builder can be found in Libraries
on page 15. An upgrade of a project from a previous version, containing third
party hardware definition files, automatically creates a new hardware library,
and all the hardware definition files are placed as objects in this library. The

3BSE033044D5001 21
Engineering Environment Section 2 Functionality Changes

user can then reorganize the hardware objects by creating own libraries and
move the objects to the new libraries.
The benefit with hardware libraries is that it is possible to have more than one
version of a hardware definition in a project.

Device Import Wizard – Improved GSD Tool


The Device Import Wizard replaces the old GSD Import Tool and is integrated in
Control Builder. The Wizard is launched from the Control Builder, by right-click a
hardware library that is open and select “Insert/Replace Hardware Type(s)…”. After
the conversion of the hardware definition files, the corresponding hardware objects
will be stored in the hardware library where the Device Import Wizard was
launched. The system has support for GSD version 5.0.
Device Import Wizard supports a change of the configuration at any time without
loss of existing configuration. This means that the user can, for example, add some
I/O modules or add/change diagnostics later on. With the GSD Import Tool always a
full import was necessary.

Single Application Download


It is now possible to select if you want to download all applications that are
connected to a controller or select the application(s) that is to be downloaded to the
controller. It is also possible to download a single application to a controller,
although compilation errors may exist in other applications connected to the
controller.
All applications must have been downloaded to, and executing in the controller,
before it is possible to use the single application download functionality.

Init Restart Option for Application at Download


An “Init” restart mode is added to the warm and cold restart options at an
application download to a controller. This start mode forces all cold retained
variables to apply their initial values, even if saved cold retain values exist.

22 3BSE033044D5001
Section 2 Functionality Changes Control and I/O

Presentation of Date and Time for Cold Retain Values to be Downloaded


In the Application analysis information window it is now stated when the cold retain
values, that is to be used during the download was saved.

New Icons/Information in Control Builder


• Project object in Project Explorer
A project object is now placed in the “root” of the Project Explorer. The
Libraries, Applications and Controllers of the project are located below the
new project object.
• “S” on simulated hardware.
A “S” is shown on simulated hardware units in the Project Explorer.

New Menus in Project Explorer


• Possible to open session log from Control Builder
It is now possible to open the current session log for Control Builder from
Project Explorer, with the menu option: Tools > Session Log File.

Control and I/O

Task Handling
In this release, there are a number of improvements in the user interfaces, regarding
presentation of information from the tasks running in the Controller. Some new
functionality in the tasks has also been added, like default values of offset on the
tasks Normal and Slow when creating a new project. A system alarm is also
implemented, to give a warning when the task is close to get latency.
• Compiler warnings for non-optimal task settings
If task settings result in that two tasks are scheduled to start at the same time, a
warning is displayed during compilation.
Warning 9155 : Controller_1:HW Task Normal and Fast may
have colliding start times.

3BSE033044D5001 23
Control and I/O Section 2 Functionality Changes

• Task Properties dialog

Figure 1. An Example of the Task Properties dialog in 4.1 and 5.0 respectively.
The layout in the Task Properties dialog has been modified and the following
information has been added since version 4.1.
Task values:
– Offset
Used
Actual
Max
– Latency alarm limit
– First scan execution time (ms)
System values:
– Total load (in the controller)
– Application stop time

24 3BSE033044D5001
Section 2 Functionality Changes Control and I/O

• Task Overview window

Figure 2. An example of Task Overview window in version 4.1.

Figure 3. An example of Task Overview window in version 5.0.

3BSE033044D5001 25
Control and I/O Section 2 Functionality Changes

The following information has been added in the Task Overview window since
version 4.1.
The accepted latency is presented in milliseconds. In version 4.1 it was in percent
(%).
– Max Interval Time
– Max Execution Time
– Offset
– Actual Offset
– Max Offset
– Accepted Latency
– Max Latency
– Latency Alarm Limit
– First Execution Time
• Default offset setting on tasks when creating new project
When you create a new Control Builder project in version 5.0, you will
automatically get a suggested offset on the Normal and Slow tasks. This new
functionality decreases the risk of getting latency in the tasks and will provide a
smoother execution in the controller.
• System alarm when close to latency in task
A system alarm will be generated when a task is approaching its maximum
latency limit (70% of accepted latency).
• Optimizing load balancing
If a controller was heavily loaded and load balancing was activated it could
take up to 30 seconds before a task with lower priority was scheduled to
execute. This is now changed to a few seconds.

Controller Settings dialog


When errors are reported, they are categorized according to their causes, and given a
severity. Based on the severity, the settings in the Controller Settings dialog can, for
instance, create an entry in the error log or stop the controller. This error reaction is
configurable in the dialog.
The Controller Settings dialog also has a setting that turns off task load balancing.

26 3BSE033044D5001
Section 2 Functionality Changes Control and I/O

Warning if an Obsolete Hardware Revision is being Used


A warning is issued in case a controller is using a processor module with an obsolete
hardware revision.
An unit with an incompatible or not preferred version is indicated as follows:
– Warning indication in Project Explorer
– A status text in the hardware editor
– A system alarm

Dynamic Download of CEX Unit Support


Prior to version 5, the controller firmware included support for all CEX unit types
(communication protocols).
Starting from version 5, the base firmware does not support any CEX units from
start. Instead, the Control Builder downloads additional firmware components for
the actually used CEX units. These “protocol handlers” are fetched from within the
hardware libraries. This saves controller memory. Available memory, for user
application, depends of how many different types of CEX units that are used.

Handling of HWD Files during Download


With hardware libraries the download has been changed. It is not necessary to reset
the controller before downloading new/changed HWD files.

Online Replacement CI853


CI853 now supports online replacements. However PPP running on CI853 does not
support online replacement, but it is possible to remove a CI853 unit with PPP
online, if it becomes faulty. A replacement of CI853 with PPP requires a controller
restart.

3BSE033044D5001 27
Control and I/O Section 2 Functionality Changes

COMLI Enhancements
The COMLI protocol is extended with support for:
• Addressing extra registers (message type < and =)
– “<“ Request high registers, Registers 0 to 65535 (decimal)
– “=” Transfer high registers, Registers 0 to 65535 (decimal)
• Clock synchronization of slaves (message type J)
– “J” Transfer date and time, time synchronization of COMLI slave.

ABB Panel 800 and ABB Process Panel


CI851 and CI854A (PROFIBUS) have support for ABB Panel 800 and ABB
Process Panel.

CI865 – Satt I/O


The CI865 (Satt I/O) unit is the AC 800M communication interface for
Satt ControlNet. CI865 has support for:
– 19” Rack I/O
– S200 I/0
– S200L I/O
– I/O 200C

S800 I/O Enhancements


• “Over/under” range support for all analog outputs
Analog outputs can now be set to below 0% and above 100% in an application.
The ranges are defined by the capability of each I/O module type.
It is also possible to set the OSP value, according to the limits implemented for
under/over range on the AO modules
• Support of under and overflow when using square root on AI845 on modulebus
The channels on AI845 have a new setting, 4..20mA sqrt, which should be used
when supervising underflow on square root values.

28 3BSE033044D5001
Section 2 Functionality Changes Control and I/O

• Support for additional RTD sensors via AI830A (replacing AI830)


– U.S Laboratory
– U.S Industrial
– IEC751/ITS-90
– JIS C 1981
– JIS C 1997
• Changed default settings on DI830, DI831 and DI885
The default settings of “filter time” parameter is changed to 0 (before it was
100) for the I/O modules DI830, DI831 and DI885.
• Possible to measure voltage on AI845 connected to CI801
It is now possible to measure voltage on an AI845 running together with a
CI801, if the new parameter option "External Shunt" is selected as shunt mode
on the AI845 module.
• ABB Standard Drives
Channels Ref 1 and Ref 2 has been changed to signed integer and counts in both
directions.

Possible to Configure which MCU Alarm Bits to Treat as Alarms


It is now possibility to configure which INSUM MCU alarm bits to treat as alarms.
A new hardware unit, MCU A+, makes it possible to select alarm bits.

Status of Ethernet Ports on Backup CPU is Shown in Control Builder


Hardware Tree
An AC 800M configured with redundant CPUs now shows its Ethernet port status
for the Backup CPU in the hardware tree. A yellow icon is present in Control
Builder Project Explorer.

3BSE033044D5001 29
Alarm and Event Section 2 Functionality Changes

Compile Warning if Redundant Controller is Configured to Save Cold Retain


Values on Compact Flash Card
Saving cold retain values to the Compact Flash card is not permitted in a redundant
controller. A compile warning is given when the interval time for saving cold retain
values is anything but 0.
Warning 7002 : Controller_1:HW Settings : Save interval for
“ColdRetain”-values at CF Card will not affect redundant
controllers. : Row 1, Column 1

Code Sorting Loops in Control Modules Gives Compile Error


The default setting for “Loops in Control Modules” in the Compiler Switches dialog
is changed to Error (Warning in previous release).

Improved Log Handling


• Increased number of saved Log files (Bak Files) on hard drive
The number of *.log_bak files that are saved on the hard drive has been
increased from 2 to 9. This means that you, for example can have 10 different
session log files before the oldest is overwritten.
• Two controller logs from redundant controllers
There is now one log for each CPU in a redundant controller, thus making it
possible to view hardware revisions etc. from both CPUs without having to
make a switch-over.

Alarm and Event

SystemAlarmCond – New Function Block Type in AlarmEventLib


With the new function block type SystemAlarmCond it is possible to define system
alarms from application code.

30 3BSE033044D5001
Section 2 Functionality Changes Alarm and Event

New Parameters in the Function Block Types PrintAlarms and PrintEvents


Instead of sending alarms/events to a local printer, it is now possible to redirect the
alarm/events to the application.
The PrintEvents and PrintAlarms function blocks contain two parameters used for
this purpose.
New parameters in the PrintEvents function block are EventItem and
EventItemText.
New parameters in the PrintAlarms function block are AlarmItem and
AlarmItemText.

Remote Time stamp in AlarmCond(M)


The AlarmCond function block type and the AlarmCondM control module type in
AlarmEventLib have a new parameter named TransitionTime. With this parameter it
is possible to use a remote time instead of the system time for alarms. This
functionality has been available in the function block type SimpleEventDetector in
previous releases.

Harmonized System Alarm & Event Generation


System Alarms and Events from AC 800M controllers are now harmonized with
respect to chosen severity, if an event or alarms is generated. The I/O related
protocols that are harmonized are S800 I/O, CI854, CI855, CI856 and CI860.

Hardware Alarm has an Comprehensible description


The description of system alarms was earlier in hex code format. Now the alarm
presentation is in text format. The description is the same as in Control Builder.
The extended and device-specific status bits are not translated in the event text.

3BSE033044D5001 31
Standard Libraries Section 2 Functionality Changes

Standard Libraries

Added Behavior in Library Objects


– Bumpless start up of loops when using OSP values
– The objects have a new EnableParError parameter, that by default disables
the ParError calculation in non-SIL applications. Enabling of ParError
calculation increases the execution time of the object.

New Libraries
• ControlObjectLib
The library contains templates for CC modules that makes it easier for the user
to create user-defined objects and using the CC (ControlConnection) concept.
The control module types in the library are:
– Mimo22CC
MIMO (Multiple Input Multiple Output) control module can deal with
two inputs and two outputs, in both directions; forward and backward. The
outputs are linear combinations of the inputs.
– Mimo41CC
MIMO (Multiple Input Multiple Output) control module can deal with
four inputs and one output; in both directions; forward and backward. The
output is a linear combination of the inputs.
– Mimo44CC
MIMO (Multiple Input Multiple Output) control model can deal with four
inputs and four outputs, in both directions; forward and backward. The
outputs are linear combinations of the inputs.
• ControlSolutionsLib
The library contains PID loop solutions to be used as templates. The templates
contain alarm handling and trending. The control module types in the library
are:
– CascadeLoop
This control module provides a complete cascade loop control solution for
connection to I/O. The control module provides master and slave PID

32 3BSE033044D5001
Section 2 Functionality Changes Standard Libraries

control with signal supervision, velocity limiter, alarm handling, trending,


and operator graphics.
– FeedForwardLoop
This control module provides a complete feedforward loop control
solution for connection to I/O. The control module provides PID feedback
control and dynamic feedforward control. The loop comes with signal
supervision, velocity limiter, alarm handling, trending, and operator
graphics.
– MidrangeLoop
This control module provides a complete midrange loop control solution
for connection to I/O. The control module provides single PID control of
two outputs in parallel. The loop comes with signal supervision, velocity
limiter, alarm handling, trending, and operator graphics.
– OverrideLoop
This control module provides a complete override loop control solution
for connection to I/O. The control module provides a minimum selector
with four controllers; one master PID controller and three override
controllers. The loop comes with signal supervision, velocity limiter,
alarm handling, trending, and operator graphics.
– SingleLoop
This control module provides a complete single loop control solution for
connection to I/O. The control module provides PID control with signal
supervision, velocity limiter, alarm handling, trending, and operator
graphics.

New Functions in System


Four new firmware functions, that are used for converting to/from words bit mapped
according to IEEE floating point, are available.
These functions may be useful when communication floating point values, via serial
communication, such as Modbus RTU.
– Dword_to_Real
– Real_to_Dword
– Real_to_Words
– Words_to_Real

3BSE033044D5001 33
Standard Libraries Section 2 Functionality Changes

New Library Objects


– BiasCC (ControlExtendedLib)
This module adds two signals of type “ControlConnection”.
– RatioCC (ControlExtendedLib)
This module multiplies two signals of type “ControlConnection”.
– DecoupleFilterCC (ControlAdvancedLib)
Decoupling filter. A filter introduced to decouple the process dynamics so
that the total system behaves as two independent systems.
– ApplicationInfo (BasicLib)
ApplicationInfo gives information about where in the application it
executes, for example name and state.
– EvalRestartInhibit (BasicLib)
– PulseGeneratorAcc (BasicLib)
Generates the correct number of pulses over time. For a given time period,
T, the number of pulses are T divided by the PeriodTime parameter. The
generator is connected to the real time clock.
– CCInputGate (BasicLib)
This control module is used for applying ControlConnection to control
module code.
– CCInputGateExtended (BasicLib)
This control module is a CCInputGate control module type with extended
functionality (internal mode, enable ramp and flag). The
CCInputGateExtended should be used inside another control module as an
input gate, to ensure that signals (passing through) satisfy the
“ControlConnection” specification.
– CCOutputGate (BasicLib)
This control module is used for applying ControlConnection to your
control module code.

34 3BSE033044D5001
Section 2 Functionality Changes Standard Libraries

– CCOutputGateExtended (BasicLib)
This control module is a CCOutputGate control module type with
extended functionality (setting manual range, output defined
manually/automatically, enable ramp and enable integration). The
CCOutputGateExtended should be used inside another control module as
an output gate to ensure that signals (passing through) satisfy the
“ControlConnection” specification.

Improvements in Existing Library Objects


• SystemDiagnostics
In the interaction window for the Ethernet communication information, in the
SystemDiagnostics function block, the time is now displayed when the last
reset of the counters occurred.
The default initial value of the parameters “Memory quota” and “Memory
quota at download”, in the SystemDiagnostics function block, have been
changed from 50% to 90%.
• Local mode possibilities in AnalogOutCC, SignalOutRealM and
SignalSimpleOutRealM
To be able to locally control, for example a control valve the control loop needs
to be updated with the locally changed value, to obtain bumpless transfer. A CC
input for this purpose is needed to backtrack the control loop, during the local
mode phase. The real output objects AnalogOutCC, SignalSimpleOutRealM
and SignalOutRealM now have been extended with the CC input
“Feedbackpos” to be able to backtrack actuator values to a control loop.
• Voting Logic Enhanced
The voting logic has been improved. The number of sending and receiving
objects has been increased. Examples of objects that have been extended with
voting logic are PidCC, ManualAutoCC, SelectorCC and Selector4CC.

3BSE033044D5001 35
OPC Server for AC 800M Section 2 Functionality Changes

OPC Server for AC 800M

Alarms in the OPC Server Kept at Communication Error


Non-idle alarms in the OPC server remains, even if there is a communication error
to a controller.

Discontinued and Replaced Functions and Units


OPC Transfer of Domain Files via MMS no Longer Supported
In order to connect to a specific AC 800M, the OPC Server needs access to some
files (called domain files) describing the content of the AC 800M. These files are
created by the Control Builder and are automatically fetched by the OPC Server
when needed. The preferred solution is to set up a shared Project folder. If previous
versions of the OPC Server could not find the needed files on the shared folder, it
tried to fetch the files via MMS from the Control Builder that made the last
download. This functionality is no longer supported.

Downloading via PPP Makes it Impossible to read Compact Flash


It is no longer possible to generate a Compact Flash image, in cases the project is
downloaded to the controller via PPP.

OPC Server and MMS Server cannot be Launched from System Tray
For security reason, the Services cannot interact with the Windows system tray
(Notification area).
OPC Server and MMS Server can still be started from the Start menu. After a
Service has been started from the Start menu and then been minimized, it is possible
to launch it from the system tray.

36 3BSE033044D5001
Section 2 Functionality Changes Auto Log On from the Setup Wizard is not Possible

Auto Log On from the Setup Wizard is not Possible


It is not longer possible to configure AutoLogonOn from the Configuration wizard
of the products (Control Builder, SoftController and OPC Server).
This feature has not been needed since version 3.2/x, but third party software may
have used it.

Language Settings from Setup Wizard in Control Builder


In the Setup wizard for the Control Builder it is now possible to select “Use
computer settings” as language, instead of selecting a specific language.
This is not the default setting.

Changed Menus in Project Explorer

Project Constants Menu


Right-click the Project object and select Project Constants to access the project
constants for the project. (The Project Constants menu entry was located in the
Tools menu, in previous release).

Difference Report Menu


Right-click the Project object and select Settings >Difference Report to access the
Difference Report. (The Difference Report menu entry was located in the Tools
menu, in previous release.)

Compiler Switches Menu


Right-click the Project object and select Settings > Compiler Switches to access
the Compiler Switches settings. (The Compiler Switches menu entry was located in
the Tools menu, in previous release.)

3BSE033044D5001 37
Changed Menus in Project Explorer Section 2 Functionality Changes

Compilation Warning Menu


Right-click the Project object and select Settings > Compilation Warning to
access the Compilation Warning settings. (The Compilation Warning menu entry
was located in the Tools menu, in previous release.)

Properties on Controller Object


The following menu options are now sub menus under Properties (Right click a
controller and select Properties):
– System Identity
– Simulate Hardware
– Product Type (former Change Product Type)
(These menus were located in the menu when you right-clicked a controller, in
previous release.)

Insert Unit
In earlier versions, the menu option New Unit was used when you wanted to add a
hardware object to the Controller. This menu option is changed to Insert Unit and an
improved window is displayed, from which more than one unit can be added, before
the window is closed.

Removed Menus in Project Explorer


• Insert Hardware Definitions menu
The Insert Hardware Definitions menu, that was located in the File menu, is
now removed. Insert of hardware definition files are now handled in the
Hardware libraries using the Device Import Wizard.

38 3BSE033044D5001
Section 2 Functionality Changes Not Released Functions

Not Released Functions


The following functions are not included in this release. These functions are
available, either partially or fully, or referred to in the documentation. Any use is
consequently the full responsibility of the user.
• The firmware functions
– InsertArray
– SearchArray
– SearchStructComponent

3BSE033044D5001 39
Not Released Functions Section 2 Functionality Changes

40 3BSE033044D5001
Section 3 Compatibility Compatible Hardware Modules

Section 3 Compatibility

This release of Compact Control Builder AC 800M (Version 5.0.0/1) is


compatible with the previous versions 5.0.0/0, 4.1.0/x, 4.0.0/0 and 3.2/7 (or later)
Some Hardware Modules may have to be exchanged to new hardware revisions.
See Compatible Hardware Modules on page 41, for further information.
Listed Hardware Modules must be of stated version/revision or higher.
Control Builder and OPC Server must be upgraded to the new version in order to
work together.

When upgrading, consideration should be given to memory usage in the


controller. The firmware size has grown, resulting in less free memory for user
applications. The reduction primarily concerns processor modules with small
amounts of free memory (PM851, PM856, and PM860) and to controllers
including several types of CEX-modules. Please see section 3 in Compact
Control Builder AC 800M, Product Guide (3BSE041586R101) for information on
memory requirements.
Controller peer to peer communication is possible with other controllers running
version 2.x/x, 3.x/x or 4.x.x/x by means of Access Variables.
See Appendix C Upgrade in the manual Compact Control Builder AC 800M,
Getting Started, Introduction and Installation (3BSE041584R101) for further
information.

Compatible Hardware Modules


Listed Hardware Modules in the table below must be of stated version/revision or
higher.
Listed I/O Modules are included due to compatibility issues only.
For some other I/O Modules there is a recommendation about firmware and
hardware versions for other reasons. See other relevant documentation regarding
such reasons.

3BSE033044D5001 41
Compatible Hardware Modules Section 3 Compatibility

Firmware in all Hardware Modules must be upgraded to the delivered version.


See Compatible Firmware on page 44 and Libraries on page 15.
Table 2. Compatible Hardware Modules

Module Required Version Recommended Version


PM851 PR:A
PM856 PR:A PR:F
PM860 PR:B PR:H
PM861 PR:B PR:L
(Singular)
PM861 PR:B(1) PR:L
(Redundant)
PM861A PR:B PR:C
(Singular)
PM861A PR:B with FPGA 1.2/1 PR:C(2)
(Redundant) -or-
PR:C
PM864 PR:B with FPGA 1.2/5 PR:H
-or-
PR:C
PM864A PR:B PR:C
(Singular)
PM864A PR:B with FPGA 1.2/1 PR:C(2)
(Redundant) -or-
PR:C
CI851 PR:A PR:H
CI852 PR:A PR:B
CI853 PR:C(3)

42 3BSE033044D5001
Section 3 Compatibility Compatible Hardware Modules

Module Required Version Recommended Version


CI854 PR:B PR:G
Index 01.00 Index 01.03(4)
CI854A PR:D
Index 02.05
CI855 PR:B PR:C(5)
CI856 PR:A PR:B(6)(7)
CI857 PR:B PR:C
CI858 PR:A
CI865 PR:A
TB840 PR:B1, D or E PR:M(8)
DI830 PR: H, J or F PR: K or later
DI831 PR: H, J or F PR: K or later
DI885 PR:C
AI845 PR:F
AO845 PR:E PR:K
BC810 PR:C PR:E
200-APB12 1.6
200-IE8 B
200-OE4 B
(1) No empty base plates are allowed on the CEX-bus when using less than PR:D.
(2) PR:D or later supports online replacement of a defect RCU-cable in configurations with BC810.
(3) Firmware version [Link] or later (2002-01-17) must be used.
Hardware revision PR:A and PR:B can not be upgraded. Revision PR:C or newer must be used.
(4) When using less than Index 01.01:
AC 800M may in some configurations not resume execution after a power fail.
(5) Less than PR:C does not support firmware upgrade.
(6) PR:B is required when using DSBC173A or TK575V112 I/O Connection Cable.
PR:A sometimes fails to start up.
(7) CI856 must be upgraded to PR:D or later in order to support online upgrade.

3BSE033044D5001 43
Compatible Firmware Section 3 Compatibility

(8) When using less than PR:J:


The optical Modulebus on PM861(A) or PM864(A) must be disconnected from the backup CPU
before it is powered up, in case the primary CPU already is running.
When using less than PR:K:
SA supervision will report error on SB, and vice versa.
PR:F, G or H should not be used.

Compatible Firmware
Firmware in Hardware Modules listed in the table below must be of stated label or
version.
Table 3. Compatible Firmware

Module Label or Version


(1)
CI858 FWCI858 [Link]
CI801 1.0/2(2) (or later)
CI830 1.3/2(3)(4) (or later)
CI840 3.0/2(5) (or later)
CI920 1.4.1 (or later)
(1) Not possible to upgrade from Control Builder.
(2) CI801 version 1.2/3 or later is required when using the added set of RTD sensors in AI830A.
(3) CI830 versions less than 1.3/2 fails to set I/O to OSP in some situations.
(4) CI830 version 1.4/0 or later is required when using AI893 or DP840.
(5) CI840 version 3.3/8 or later is required when using the added set of RTD sensors in AI830A.

44 3BSE033044D5001
Section 4 Fixed Problems Version 5.0.0/1

Section 4 Fixed Problems

Version 5.0.0/1
Issues and problems are divided into functional categories:
• Administration
• Configuration
• Operational

Administration
Table 4 lists the major system or product administration issues that have been
corrected since the previous version or service pack. A brief description of the
correction has also been given.

Table 4. Corrected Administration Issues

Issue Correction or Fix


Single Control Module Missing in This problem has been corrected in Control
Backup File Builder.
Single Control Modules in the Control Product Bulletin: 3BSE047421D0006
Builder was not included in the project
backup files generated when backing up the
complete project. Such a backup was thus
incomplete and could not later be restored.

800xACON-AD-5000-007

3BSE033044D5001 45
Configuration Section 4 Fixed Problems

Configuration
Table 5 lists the major system or product configuration issues that have been
corrected since the previous version or service pack. A brief description of the
correction has also been given.

Table 5. Corrected Configuration Issues

Issue Correction or Fix


COMLI Startup Problems This problem has been corrected in
It could happen that the COMLI COMLIHwLib 1.0-8.
communication did not start in the following
cases, the function blocks returned
status -7004.
• After download to empty controller
• After power-up with warm start.
• After hot swapping the CI853.

800xACON-CN-5000-038
MODBUS RTU Startup Problems This problem has been corrected in
It could happen that the ModbusHwLib 1.0-7.
MODBUS RTUcommunication did not start
in the following cases, the function blocks
returned
status -7004.
• After download to empty controller
• After power-up with warm start.
• After hot swapping the CI853.

800xACON-CN-5000-039

46 3BSE033044D5001
Section 4 Fixed Problems Configuration

Table 5. Corrected Configuration Issues (Continued)

Control Builder Crash When Having This problem has been corrected in Control
Large SFCs Builder.
It happened that Control Builder crashed
during compilation. It occurred if a there
were a large number of parameters and
variables in a control module type together
with a large number of code blocks in that
type, the latter is the case in large SFCs.

800xACON-CN-5000-028
Using the Same Variable/Parameter as This problem has been corrected in Control
Graphical Node More Than Once Builder.
It was not possible to use the same variable Please note that the correction only prevents the
or parameter as a graphical CMD node problem from being introduced. Already affected
more than once, only one node was used CMDs will not be changed.
and all graphical connections were
redirected to this node. This has been
possible in earlier releases.
Please note that the program logic of the
user application was still the same even if
the drawing in the CMD editor looked
strange.

800xACON-CN-5000-034

3BSE033044D5001 47
Configuration Section 4 Fixed Problems

Table 5. Corrected Configuration Issues (Continued)

Diagnostic Problems with PROFIBUS This problem has been corrected in the
DP-V1 Slaves CI854/CI854A firmware version 5.52 included in
Some PROFIBUS DP-V1 slaves could CI854PROFIBUSHwLib 1.0-20.
cause diagnostic problems at
CI854/CI854A. Selecting SlaveDiagnosis
in the web interface could stop the cyclic
communication:
Running the service diagnosis for
CI854/CI854A by use of the web interface
and selecting the button SlaveDiagnosis
for the DP-V1 slave, could cause the
CI854/CI854A to stop the cyclic
communication. No error indication was
seen in Control Builder in this case. In the
web interface the message "No response
from CI854" was shown.
This kind of error was seen for the following
PROFIBUS slaves:
• Pepperl+Fuchs:
Power Hub System HD2-GTR-4PA
• Phoenix Contact:
L PB BK DI8 DO4-PAC
FLM BK PB M12 DI 8 M12

800xACON-CN-5000-036
PDQ22 Might Activate OSP when This problem has been corrected in the
Parameters were Changed CI854/CI854A firmware version 5.52 included in
If the settings for one module of the CI854PROFIBUSHwLib 1.0-20.
PROFIBUS PDQ22 device was changed New slave parameters are sent from CI854 to the
and downloaded, another module slave via the SetPrm telegram without doing an
connected to the same PDQ22 might get unlock and ChkCfg. Some slaves like PDQ22
disturbed and activated OSP. This was seen activated OSP because of the unlock command.
for UMC22 connected to PDQ22.

800xACON-CN-5000-040

48 3BSE033044D5001
Section 4 Fixed Problems Configuration

Table 5. Corrected Configuration Issues (Continued)

Chinese Grammatical Errors This problem has been corrected in Control


There were grammatical errors in the Builder.
Control Builder user interface (menus and
dialogs) when using the Chinese
translation.

800xACON-CN-5000-029
Error While Editing Hardware Units This problem has been corrected in Control
An annoying error message was frequently Builder.
shown in Control Builder while editing
certain hardware units (such as when
making I/O connections to it). The message
shown was:
Fel vid
CreateInstance"(AcStorageAIP) hr
= -2147221164
The error message was harmless and
should not have been shown.

800xACON-CN-5000-030

3BSE033044D5001 49
Operational Section 4 Fixed Problems

Operational
Table 6 lists the major system or product operational issues that have been corrected
since the previous version or service pack. A brief description of the correction has
also been given.

Table 6. Corrected Operational Issues

Issue Correction or Fix


Hardware Flow Control on RS-232 This problem has been corrected in the AC 800M
Channels firmware.
Setting the Flow control setting to Hardware Product Bulletin: 3BSE047421D0004
on a serial RS-232 channel did not give the
expected result. RTS (request to send) on
the channel would in this case be set high
all the time.
The correct behavior is that RTS is set only
when the channel sends data.
This problem made it impossible to use a
two wire multidrop configuration.

800xACON-OL-5000-014
AC 800M Crash due to Incomplete This problem has been corrected in
COMLI Messages COMLIHwLib 1.0-8.
There was a small chance that the Product Bulletin: 3BSE047421D0002
AC 800M would crash (halt) in case it was
exposed to incomplete COMLI messages.
This problem has only been seen while
using a partly broken third party hardware
unit that cut out parts of the messages.

800xACON-OL-5000-015

50 3BSE033044D5001
Section 4 Fixed Problems Operational

Table 6. Corrected Operational Issues (Continued)

Issue Correction or Fix


Erroneous COMLI Stamp Handling This problem has been corrected in
The COMLI stamp handling did not work in COMLIHwLib 1.0-8.
compliance to the COMLI specification. Product Bulletin: 3BSE047421D0002
The AC 800M did always send stamp 0,
which is not correct. It should start at 0 but
thereafter alter between 1 and 2. The slave
is using the stamp to recognize new
telegrams; in order to avoid processing
already received telegrams in case of re-
transmitted telegrams.
This problem was not visible in case both
the master and slave were AC 800Ms at
version 5.0.0/0, but in any other
combination the communication would be
frequently interrupted.
Another (not visible) result was that a slave
working in compliance with the specification
would not be able to determine if a write
request was a retransmission or not - the
slave would always process the write
request even if it was a retransmission.

800xACON-OL-5000-016

3BSE033044D5001 51
Operational Section 4 Fixed Problems

Table 6. Corrected Operational Issues (Continued)

Issue Correction or Fix


COMLI Message Type 3 not in This problem has been corrected in
Compliance to the COMLI Specification COMLIHwLib 1.0-8.
COMLI message type 3 (Transfer the status Product Bulletin: 3BSE047421D0002
of individual I/O-bits) did not work in
compliance to the COMLI specification.
The AC 800M assumed type 3 messages to
be binary encoded. But the specification
states that it should be encoded as ASCII.
This problem was not visible in case both
the master and slave were AC 800Ms at
version 5.0.0/0 (as both assumed the data
to be encoded in the same format), but in
any other combination would sometimes
wrong data be sent to the slave. An
AC 800M slave would for example in this
case see all types 3 messages as a request
to write True into an variable (despite if the
message contained False or True).

800xACON-OL-5000-017
AC 800M Crash due to Incomplete This problem has been corrected in
MODBUS RTU Messages ModbusHwLib 1.0-7.
There was a small chance that the
AC 800M would crash (halt) in case it was
exposed to incomplete MODBUS RTU
messages.

800xACON-OL-5000-023

52 3BSE033044D5001
Section 4 Fixed Problems Operational

Table 6. Corrected Operational Issues (Continued)

Issue Correction or Fix


Controller Stop due to Compact Flash This problem has been corrected in the AC 800M
Card firmware.
Usage of a Backup media in the AC 800M Product Bulletin: 3BSE047421D0005
could cause the controller to stop execute
after some time. This happened due to a
memory leak in the Compact Flash card
status handling.
The memory leak occured when a Compact
Flash (CF) card was inserted in the card
slot located at the front of the AC 800M
controller AND a CF Card was configured
below the CF Reader in the controller
configuration. The memory leak would
inevitably cause the controller to stop
execute.
The memory leak was constant and about
1 MB / 24 hours.

800xACON-OL-5000-018
Not Able to View Diagnostics for PDQ22 This problem has been corrected in Control
Device Builder.
Diagnostics for the PROFIBUS PDQ22
devices like UMC22 and MFI21 was not
seen in Control Builder.

800xACON-OL-5000-019

3BSE033044D5001 53
Operational Section 4 Fixed Problems

Table 6. Corrected Operational Issues (Continued)

Issue Correction or Fix


Diagnostic Problems with PROFIBUS This problem has been corrected in the
DP-V1 Slaves CI854/CI854A firmware version 5.52 included in
Some PROFIBUS DP-V1 slaves could CI854PROFIBUSHwLib 1.0-20.
cause diagnostic problems at
CI854/CI854A. Wrong diagnostics were
shown in Control Builder and PPA:
In case of an error on the slave device itself
it could be that no error at all was indicated.
It also could be that module errors were
indicated on wrong module positions or line
breaks were indicated when everything was
ok.
This kind of error was seen for the following
PROFIBUS slaves:
• Pepperl+Fuchs:
Power Hub System HD2-GTR-4PA
• Phoenix Contact:
L PB BK DI8 DO4-PAC
FLM BK PB M12 DI 8 M12

800xACON-OL-5000-021

54 3BSE033044D5001
Section 4 Fixed Problems Operational

Table 6. Corrected Operational Issues (Continued)

Issue Correction or Fix


CI854(A) Crash Due to Implausible This problem has been corrected in the
Diagnostic Data CI854/CI854A firmware version 5.52 included in
It could happen that the CI854(A) crashed CI854PROFIBUSHwLib 1.0-20.
when some implausible diagnostic data was
sent from the slave device. The Fault LED
on the CI854(A) was turned on and the
communication on PROFIBUS stopped. To
resolve the problem the controller needed to
be reset. This error was only seen with
PDP22.
A workaround was to set the CI854(A)
redundant. In case of an error a switchover
would then be performed and the
communication on PROFIBUS would
continue.

800xACON-OL-5000-020

3BSE033044D5001 55
Version 5.0.0/0 Section 4 Fixed Problems

Version 5.0.0/0
In addition to the listed fixed problems in version 5.0.0/0 below, are fixed problems
in 4.1.0/1 and 4.1.0/2 also corrected in version 5.0.0/0. See the referred Release
Notes below.
There has been general improvements to make CI854 and controllers more stable.
The functionalities that have been improved are:
• Downloading and configuration: CI854 (PROFIBUS) and controllers
• Hot Insert: CI854 (PROFIBUS)
• Hot Swap: CI857 (INSUM), CI855 (MB300) and CI856 (S100)
• Normal operation: controllers
See Compact Control Builder, Version 4.1.0/2, Release Notes (3BSE033044D4102)
for further information.
Issues and problems are divided into functional categories:
• Administration
• Configuration
• Operational

56 3BSE033044D5001
Section 4 Fixed Problems Administration

Administration
Table 7 lists the major system or product administration issues that have been
corrected since the previous version or service pack. A brief description of the
correction has also been given.

Table 7. Corrected Administration Issues

Issue Correction or Fix


False Gateway Connection Error These problems have been corrected.
Message from INSUM Devices
There was at least two cases when “GW
connection error” was set on for (and other
INSUM devices) even though the
connection was OK:
• If you broke the communication to the
INSUM Gateway and later reconnected
you got a problem with MCUs that were
configured in the hardware tree but
were disconnected from the LON bus,
or completely missing when the
connection was re-established.
The error indication “GW connection
error” was not cleared.
• Hot Swap of CI857. After the Hot Insert
all MCUs got “GW connection error”.
Removing an MCU Used in Application This problem has been corrected.
Resulted in Error on InsumConnect
When MCU:s that already had an ongoing
subscription in an application were removed
from the hardware configuration, the
parameter Valid was set to false in the
InsumConnect and the status code 8991
(CI857 message status) was returned. As a
result, all MCUs went to Failsafe since the
connection was cancelled.

3BSE033044D5001 57
Administration Section 4 Fixed Problems

Table 7. Corrected Administration Issues (Continued)

Issue Correction or Fix


Wrong Status Indication for I/O Modules This problem has been corrected.
after HotSwap of CI854
After a HotSwap of a CI854 the status
indication for the slaves was correct, but
some I/O modules got the status 'Device not
found' (not correct). This happened in
configurations with a large amount of
configured slaves.
PROFIBUS CI854 Dual LED Went Off/On This problem has been corrected.
Periodically
With high PROFIBUS cycle time (>250ms)
the CI854 DUAL LED went off/on
periodically, because the communication
monitoring between Primary and Backup
via PROFIBUS was running out of time.
Controller Shutdown when This problem has been corrected.
Reconfiguring Redundancy of CI854
When a reconfiguration from redundant to
single CI854 was done and the CI854
backup physically was missing, the
Controller was shutdown.
CI854 Redundancy Problem when no This problem has been corrected.
Slaves Were Configured
The redundancy didn’t work, if a redundant
pair of CI854 was configured without any
slaves, and the primary CI854 was
unplugged and inserted again. The LED
indication of the CI854 was as follows:
Primary: PRIM on, DUAL off
Backup: PRIM off, DUAL on.

58 3BSE033044D5001
Section 4 Fixed Problems Configuration

Configuration
Table 8 lists the major system or product configuration issues that have been
corrected since the previous version or service pack. A brief description of the
correction has also been given.

Table 8. Corrected Configuration Issues

Issue Correction or Fix


Search & Navigation Tool Limitation in This problem has been corrected.
Control Module Diagram
The Search & Navigation Tool could not find
references to identifiers connected to the
'Color' or 'Attributes' of Control Module
Diagram objects.
Renaming a FBD/LD Code Block This problem has been corrected.
Renaming a FBD/LD code block could
make another code block corrupted. The
problem occurred after renaming of a FBD
or LD code block that was given a name that
was identical to the beginning of the name
of another FBD/LD code block, for example
'Test' and 'Test_2'.
Hot Insert of CI854(A) This problem has been corrected.
Hot insert of CI854(A) was not working
during warm start configuration on CEX
bus.
Controller Shutdown when Changing This problem has been corrected
Controller Setting
The controller sometimes did a shutdown or
a switch over if the value of AE Max.
number of event subscription was changed
and downloaded to the controller.

3BSE033044D5001 59
Configuration Section 4 Fixed Problems

Table 8. Corrected Configuration Issues (Continued)

Long First Scan due to Alarms with not This problem has been corrected
Defined SrcName
If an Alarm/Event function block/control
module was called without the parameter
SrcName specified, that is SrcName was
not connected or was configured with an
empty string, this could result in a very long
first scan execution time. In some situations
this could cause task abortions.
Controller Shutdown when Added This problem has been corrected.
Application was Downloaded with Warm
Restart
If an new application was added to a
controller and connected to a task, that
already existed in the controller, the
controller was shut down during the
download of the new application.
Code Tab Named “P1” Caused Control This problem has been corrected.
Builder Shutdown
The Control Builder was shutdown when a
POU that contained a code tab named “P1”
was opened.
Graphical Connections Looses their This problem has been corrected.
Nodes and are Collected in one Place
After engineering in the CMD editor (moving
and changing control modules the graphical
connections lost their nodes and ended up
in one place. This was very rare!
Graphical Connections Connect to This problem has been corrected.
Wrong Node if to Close Between Nodes
In some rare situations graphical
connections were reconnected to the wrong
graphical node if the nodes were placed to
close to each other.

60 3BSE033044D5001
Section 4 Fixed Problems Configuration

Table 8. Corrected Configuration Issues (Continued)

Changes in CMD Editor Disappeared if This problem has been corrected.


Connections Dialog was Opened
If the Control Module Diagram editor
contained a number of control module
instances and some changes were done,
the changes sometimes were undone when
the parameter connection editor was
opened for a control module instance.
Control Builder Shutdown when Using This problem has been corrected.
Search & Navigation Tool
The Control Builder was shut down when
you tried to modify an simulated marked I/O
module, whose I/O editor was opened from
the Search & Navigation tool.
Control Builder was Shutdown when a It is not possible to make a check from an online
“Check” was Made Online Control Builder anymore.
The Control Builder sometimes was
shutdown if a “check” was made when the
Control Builder was online.
Large Arrays Caused Restart of CI854 This problem has been corrected.
Working with large arrays (creating,
searching, etc.) sometimes resulted in a
restart of CI854.
Not Possible to have Negative Speed on This problem has been corrected.
Drives Units Also see “ABB Standard Drives” on page 29.
It was possible to configure negative speed
on a drives unit, but it didn't work.
CI857 Tried to Connect to Wrong INSUM This problem has been corrected.
Gateway
When changing the IP address of the
gateway, the CI857 in some situations tried
to connect to the wrong gateway.

3BSE033044D5001 61
Configuration Section 4 Fixed Problems

Table 8. Corrected Configuration Issues (Continued)

Parameter Error in Library object This problem has been corrected.


ValveUniM
If the input parameter FBConfig of the
control module type ValveUniM was set to 5
or 6 (valid values) the parameter ParError
was set to true.
BCDToDint did not Work Correct This problem has been corrected.
If the last input parameter of a BcToDint was
set to true, wrong result was received from
the function block.
Example:
input1 = true
input2 = false -> out =1
Input1 = true
input2 = true -> out = 255.
Memory Quota in System Diagnostics This problem has been corrected.
Showed WrongValue in Byte Format
If the memory quota in the System
Diagnostics function block type was set to a
value greater or equal to 89% the value of
bytes was shown in a negative value and
the alarm from the function block was
activated.
ParError in ACOFAct did not Work This problem has been corrected.
Correct
The following settings of input parameters to
the function block type ACOFAct should
have set the parameter ParError to true, but
ParError was still false.
EnableParError = true
SelectSupDel = 0
SupDel > 0ms

62 3BSE033044D5001
Section 4 Fixed Problems Configuration

Table 8. Corrected Configuration Issues (Continued)

ACOFActDect3P Could not Handle This problem has been corrected.


Change of Parameter CascadeMode
If the parameter CascadeMode in the
function block type ACOFActDect3P was
changed online it could in some rare
situations occur that the function block went
to a unrecoverable state.
Erroneous PID Deadband Handling when Now the Pv changes are used when calculating the
Moving into Deadband process value derivative and its difference when
When a PID was configured with a entering the deadzone.
deadband, the calculation of control error
difference was incorrect, when moving into
the deadband. The objects that had this
error were PidLoop, PidLoop3P,
PidCascadeLoop, PidCascadeLoop3P,
PidCC, PidAdvancedCC, FuzzySpPvIn,
FuzzyController1CC, FuzzyController2CC
and FuzzyController3CC.
Not Possible to set Parameter This problem has been corrected.
ContinueStartSeq to False in
GroupStartObjectTemplate
It was not possible to set the parameter
ContinueStartSeq to false in the control
module type GroupStartObjectTemplate.
Error in Interaction Window of The button now shows the alarm window.
SignalSimpleInRealM
The button, for showing the alarm window in
the interaction window of the control module
type SignalSimpleInRealM type didn't open
the alarm window.

3BSE033044D5001 63
Configuration Section 4 Fixed Problems

Table 8. Corrected Configuration Issues (Continued)

ReqNoOfStarted did not Work Correct in This problem has been corrected.
GroupStartStandby12
The parameter ReqNoOfStarted was not
working for the control module type
GroupStartStandby12. If a variable was
connected to the parameter
ReqNoOfStarted, the value of the variable
always was -1.
Configuration Errors from Vote Control This problem has been corrected.
Modules when AEConfig was Set
to 2 or 3
The Control Module types Vote1oo1Q,
VoteXoo3Q, VoteXoo2D and VoteXoo8
generated alarm configuration errors when
parameter AEConfig initially was set to 2, 3
or 4. The error didn't appear if AEConfig
was set to 1.
Handling of CPU Settings in Simulated From now on, all settings for the CPU and the two
Controllers Ethernet channels will be used when downloading
When downloading a configuration to a to an AC 800M. When downloading to a Soft
simulated controller all CPU settings had Controller only the alarm & event parameter
their default values in previous versions. settings will be used.

Default Value for “CS Time Set Enabled" The default value has been changed to False.
The CPU parameter “CS Time Set Enabled
had the wrong default value when adding a
new controller to an existing project.

64 3BSE033044D5001
Section 4 Fixed Problems Configuration

Table 8. Corrected Configuration Issues (Continued)

Hanging Application Download This issue is solved and a master communication


It could in rare cases happen that download timeout of 90 seconds is introduced.
of application changes hanged. The reason
was that the application swap in the
controller never occurred, because the
controller was waiting for answers on
outstanding communication requests. The
controller had to be restarted in order to
escape this situation.
Update of Strings in OPC Clients too These problems have been corrected.
Slow
The requested update of strings from the
attached controllers is set in the OPC
Server panel. The actual update rate to the
OPC client should be between zero and the
requested time. This was however never the
case; it always took more than the
requested time to get an updated value of a
string from the OPC Server.
OPC Server not Coping well with This problem has been corrected.
Hanging Application Download Note! A hanging download should never occur,
If an application download from Control see Hanging Application Download on page 65.
Builder hanged, the OPC server also
hanged and needed to be restarted
manually.

3BSE033044D5001 65
Configuration Section 4 Fixed Problems

Table 8. Corrected Configuration Issues (Continued)

Control Builder did not Release Files This problem has been corrected.
The Control Builder did not release the files
on the hard drive for a project when it was
closed. It was thus not possible to use
Windows explorer to access the files from a
closed project, without first exiting Control
Builder.
The same problem concerned the project
backup function; the generated project
backup files were not released until Control
Builder was closed.
Check in Access Variable Editor did not This problem has been corrected.
Work
No check was made in the Access variable
editor if the Check button/menu option was
used.
Task Changes Affected Wrong Task This problem has been corrected.
This issue occurred during the following
circumstances:
• The priority or interval time of a task
was changed in online mode, in such a
way that the task should got a new
position in the task tree, as if the
change would have been done in
offline mode.
• If the user then went offline with the
Control Builder and online again
(without download).
If, for instance, the interval time now was
changed for one task another task was
affected.

66 3BSE033044D5001
Section 4 Fixed Problems Configuration

Table 8. Corrected Configuration Issues (Continued)

Connection Timeout for INSUM are With the new firmware for CI857 the timeout is
Configurable determined by the Failsafe Timeout parameter on
If the Ethernet connection between CI857 the INSUMGateway hardware unit:
and the INSUM system is broken this is The INSUM Ethernet connection timeout is the
indicated on the hardware unit same as FailSafe Timeout if FailSafe Timeout is
INSUMGateway in the controller. 10 seconds or more. If FailSafe Timeout is less
The time it took for CI857 to decide that the than 10 seconds the INSUM Ethernet connection
connection was broken was about one timeout is 10s.
minute and it was not configurable.
Source Code Error if More than 127 This problem has been corrected.
Subunits on User-defined Hardware
Object
A source code error was displayed when a
project containing hardware object(s)
(PROFIBUS) with more than 127 possible
subunits was reopened. The object(s)
containing the subunits was also deleted
when the project was reopened.

3BSE033044D5001 67
Configuration Section 4 Fixed Problems

Table 8. Corrected Configuration Issues (Continued)

Reopen Project Change Value on Dword This problem has been corrected.
Parameters
If the value 16#2 was given to a parameter
of the data type dword in the connection
editor of a control module instance it was
accepted and possible to make a download,
go offline and then make new downloads
(the value was kept all the time).
But if the project was closed and then
opened again a compilation error was
shown when a new download was started.
The value 16#2 was changed to 2, when the
project was reopened.
Change of Inverted Setting on Digital I/O This problem has been corrected.
Channel was not Saved
If a variable was connected to a digital I/O
channel in the I/O editor and the inverted
property of the channel was set to true,
before a save of the editor was done, the
inverted setting was not saved.

68 3BSE033044D5001
Section 4 Fixed Problems Operational

Operational
Table 9 lists the major system or product operational issues that have been corrected
since the previous version or service pack. A brief description of the correction has
also been given.

Table 9. Corrected Operational Issues

Issue Correction or Fix


Status for DSDI110A not Properly This problem has been corrected.
Displayed in Control Builder
Setting the parameter “Scan interval” to a
value in range 1-99 when using the S100
I/O board DSDI110A resulted in that the
FAIL-led on the I/O board was lit and the
communication with the I/O board ceased to
work. The status for the I/O board in Control
Builder showed no error.
No System Identity in Control Builder This problem has been corrected.
The Control Builder sometimes lost its
SystemID after it was restarted. It was not
possible to communicate with any controller
and the ip address in the “About Control
Builder” box disappeared.
Node Down/up Events from RNRP at This problem has been improved.
Long 1131 Execution Time
If the controller was running with high load
or long 1131 execution time, RNRP
generated “false” events for node down/up.
The nodes were not lost.
Not Possible to Run some Standard This problem has been corrected.
Function Blocks in Time Critical Tasks
It was not possible to run the following
function blocks in time critical tasks:
TimerOnHold, TimerOffHold,
TimerOnOffHold, TimerPulseHold,
TimerPulseHoldDel and PulseGenerator.

3BSE033044D5001 69
Operational Section 4 Fixed Problems

Table 9. Corrected Operational Issues (Continued)

Issue Correction or Fix


Controller Shutdown due to Error in This problem has been corrected.
Hardware Definitions for AO930
There was an error in the hardware
definition file for AO930, that potentionally
could result in a controller shutdown.
Save Cold Retain from OPC Server This problem has been corrected.
Failed
Occasionally, the save of cold retain files
from OPC server failed.
Control Builder was not Responding This problem has been corrected.
After a While in Online Mode
Sometimes an online Control Builder with
interaction windows opened for a while
entered a state where it didn’t respond to
input anymore.
Engineering Stations Out of This problem has been corrected.
Synchronization after Application
Change
Engineering of an application or a library
resulted in that time stamps of objects, in
the application/library, were changed even if
the object types weren't changed. This only
happened in some rare situations and the
result was that it wasn't possible to “go
online without download” from another
Control Builder. A new download was
required. This only occurred in multi-user
environments.

70 3BSE033044D5001
Section 4 Fixed Problems Operational

Table 9. Corrected Operational Issues (Continued)

Issue Correction or Fix


ParError was Never Set in TimerOffHold, This problem has been corrected.
TimerOnHold, TimerOnOffHold,
TimerPulseHold
The out parameter ParError was never set
by the function block types TimerOffHold,
TimerOnHold, TimerOnOffHold and
TimerPulseHold.
Code Loops in Standard Libraries These problems have been corrected.
In some situations the following control
module types generated code sorting loops:
PidAdvancedCC, StictionCompensator,
FuzzyPvIn, AccelerationLimiterCC,
Level2CC, Level4CC, Level6CC, LimiterCC,
LimiterHighCC, LimiterLowCC, PidCC,
SignalSupervisionCC, VelocityLimiterCC,
EquipProcedureTemplate,
GroupStartStandby4, GroupStartStandby8
and GroupStartStandby12.
Windup Indication Latched to Wrong This problem has been corrected.
Border
The windup indication indicated wrong limit
when the controller moved from one limit to
the other in one scan. If more than one scan
was passed during the travel between the
limits, the indication worked.

3BSE033044D5001 71
Operational Section 4 Fixed Problems

Table 9. Corrected Operational Issues (Continued)

Issue Correction or Fix


Overflow in MultCC This problem has been corrected.
Overflow occurred in the control module
type MultCC when the parameter
[Link]:= 0.0 and when the
parameter [Link] was set to
a value higher than 0.0. When these
conditions were fulfilled a division by zero
occurred with an overflow as result. This
happened only when the module was
backtracking.
Attribute on Variable Fraction not Cold The attribute of the Fraction variable is now
Retain in SignalInReal ColdRetain.
The Fraction variable in the function block
type SignalInReal didn't have the attribute
Cold Retain.
Impossible to stop MotorUni with This problem has been corrected.
GroupStartInterlock set to True
If the GroupStartILock was true in the
function block type MotorUni and the motor
was running and Group Start mode was
pressed, then all modes were lost! During
this time it was impossible to stop the motor.
Data Types in GroupStartLib are not This problem has been corrected.
Visible
The data types GroupStartStandby4Par,
GroupStartStandby8Par and
GroupStartStandby12Par in the
GroupStartLib were not visible in Control
Builder.

72 3BSE033044D5001
Section 4 Fixed Problems Operational

Table 9. Corrected Operational Issues (Continued)

Issue Correction or Fix


Low Level Handling at Cold Restart not Now the alarm and event supervision are inhibited
Correct Handled in SignalInReal until the startup phase is ended after cold reset.
The Low levels in SignalInReal (if This results in that no spurious indications take
configured to be used) was activated in the place but the observed behavior of the output
first cycle after a cold restart. This means parameter remains and is intended due to the
that the output parameters LTL, LTLL, demand of bumpless behavior. This addition is
LTLLL was activated. Alarm/Events was made in the objects: SignalInReal, SignalReal,
activated (if configured). The 'Out' output SignalInRealM, SignalOutRealM and
parameter of real type also had a very low SiganlRealCalcInM of SignalLib.
value in the first cycle, even if the input
value ([Link] and [Link]) was high
(above LevelL).
Disturbance in Frequency Value from This problem has been corrected
DSDP 170 Board (S100)
The disturbance might appeared with a few
seconds interval. The disturbance was
caused by inconsistency problem when
reading the multi-byte speed measuring
counter from DSDP 170.
Error in the Scaling Function for Analog This problem has been corrected.
Inputs
It was possible to get 100.0001% of the
value from an analog input signal,
depending on the resolution of the actual
hardware. This error gave problems in some
applications where comparisons with 100%
was done.
RNRP Could Show Wrong Distance to This problem has been corrected.
Tunnel Area
RNRP sometimes displayed the wrong
distance, in number of hop counts, when
using dual RNRP tunnel areas.

3BSE033044D5001 73
Operational Section 4 Fixed Problems

74 3BSE033044D5001
Section 5 Known Problems Administration

Section 5 Known Problems

Issues and problems are divided into functional categories:


• Administration
• Operational
• Configuration
• Instruction Manual Changes

Administration
Table 10 lists the issues that may exist and affect system or product administration
at time of release including user, node and service structure related issues and

3BSE033044D5001 75
Controller Section 5 Known Problems

[Link], clarifications, or helpful hints have been provided for each


issue wherever possible.

Table 10. Administration Issues

Issue Workarounds, Clarifications, and Helpful Hints

Controller
Backup CPU will Experience Difficulties Note: Any removal of BC810, at any time, will by
to Synchronize if BC810 is Hot-swapped design stop the backup CPU. The problem
During Synchronization recognized and described here is the state where
If BC810 is hot removed during the time restart by the INIT button will fail.
when the backup CPU is synchronizing Workarounds (any of these will help):
(DUAL LED in primary flashing) and hot 1. Do not perform hot swap of BC810 during
inserted before the end of the synchronization. Synchronizing is an
synchronization (the DUAL LED stops extremely temporary state.
flashing) the backup CPU will stop and
2. If BC810 already has been removed during
enter a state where restart attempts, by use
synchronization, then wait to insert it until the
of the INIT push button, will fail.
synchronization has ended and the backup
CPU has stopped. Finally push the INIT button
on the backup CPU.
3. If hot swap already has been performed during
the synchronization then either redo the hot
swap after end of synchronization and push the
button or have the backup CPU powered off
800xACON-AD-5000-001 and then on again.

76 3BSE033044D5001
Section 5 Known Problems Communication

Table 10. Administration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

Communication
Delayed Restart of SattBus on TCP/IP at
Cold Restart Download
If using SattBus over TCP/IP and
downloading the applications with the cold
restart option, it may take several minutes
before the SattBus communication is up
and running.
There is no problem when making a normal
(warm restart) download.

800xACON-AD-4100-003

3BSE033044D5001 77
I/O Handling Section 5 Known Problems

Table 10. Administration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

I/O Handling
S100: Scanning of DSDI 110 may not • Use scanning instead of interrupt based
Start after Adding a CI856 to a Running updating.
Controller • Interrupt based updating may be used with
When adding a CI856 unit to an empty base caution. If it is used and it does not work the
plate (no unit has been configured updating can be started by hot remove of
previously) on a running controller, the CI856 and hot insert of it on the base plate.
scanning of the input channels of DSDI 110
may not start and no indication will be
shown. This only happens if the channels of
DSDI110 are configured to update on
interrupt.

800xACON-AD-5000-002

78 3BSE033044D5001
Section 5 Known Problems I/O Handling

Table 10. Administration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


S100: Initialization of CI856 Sometimes If this happens the module needs another
Fails initialization. This can be done by removing it from
At start-up CI856 may not start as it should. its base plate or by power-off and power-on of the
controller.
The problem is corrected in revision; PR:D.

800xACON-AD-5000-004
S100: Error for I/O Conflict on Physical Hot remove/insert of CI856 corrects the problem,
Hardware not Cleared but stops all I/O communication from CI856 for a
If two S100 I/O boards are strapped to the while.
same address the CI856 will detect it and Another way, that does not disturb the I/O
set Unit status to “I/O module ID conflict”, on
communication for the working boards, is to
the module which is configured to have thatchange the address of the board to an unused
address. address in the hardware configuration and
Removing the boards with the conflicting download it. Then either change the address on
addresses and inserting the board with the the physical board to match the new one or change
correct address does not clear the error. the address in the hardware configuration to the
original address and download the configuration
800xACON-AD-5000-003 again.

3BSE033044D5001 79
Operational Section 5 Known Problems

Operational
Table 11 lists the issues that may exist and affect operation of the system or product
at time of release. Workarounds, clarifications, or helpful hints have been provided
for each issue wherever possible.

Table 11. Operational Issues

Issue Workarounds, Clarifications, and Helpful Hints

Control Builder
Backup CPU Network Interfaces
Incorrectly Error Marked
If a network interface on the Primary CPU
does not have any connection to the
network it is error marked. The
corresponding interface on the Backup CPU
is also error marked, even if it might work
correct.

800xACON-OL-5000-003
Not Possible to Change Boolean Values Declare the data type bool with the syntax: bool.
Online in FBD or LD Panes f the definition
of the data type bool for a variable,
parameter or component contains capital
letters it is not possible to change the value
of the variable, parameter or component in
online mode in the FBD or LD panes.
Instead of getting the menu option "On" and
"Off" in the context menu you get the menu
option "Set value" when you try to change
the value.

800xACON-OL-5000-011

OPC Server

80 3BSE033044D5001
Section 5 Known Problems Controller

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Query Condition Names does not Work
Properly
The OPC AE Server for AC 800M gives
wrong answer to the query condition names
call. AC 800M have two event categories
that define condition names, “Process
Condition Event” and “System Condition
Event”. If asked for the condition names for
one of the categories through the method
IOPCEventServer::QueryConditionNames,
condition names from both categories will
be returned. This entail that the same set of
condition names are returned for both
categories.

800xACON-OL-5000-007

Controller
CPU Battery Low Indication 1. Regular and frequent preventive renewal of the
When the battery is in, or near, a batteries according to our recommendations.
discharged condition, any power failure will 2. If a controller reset already has occurred, due
lead to a controller reset (application is lost). to battery low, then urge on renewal in all
The battery might, however recover controllers possibly concerned.
significantly after some time in unloaded 3. Also consider the new external rechargeable
condition, which means that the B-LED at battery alternative SB822. Also see SB822
the CPU front might return to lit condition. Documentation Missing on page 101.
This could cause the necessary renewal to
be overlooked.

800xACON-OL-4100-007

3BSE033044D5001 81
Controller Section 5 Known Problems

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Using GetIntervalTime in Start_Code A Start_Code code block does not have any
Might Hang the Soft Controller interval time since it only executes once, before the
The function GetIntervalTime has tasks are started (the function will in this case
unpredictable behavior when used in return 0).
Start_Code in a Soft Controller. This might
If the function shall be used upon application start,
hang the Soft Controller. There are no put it in an ordinary code block inside an IF-
problems using this function in a real statement trigged with
controller. FirstScanAfterApplicationStart. The function will
return the requested interval time of the task in
800xACON-OL-4100-008 which the program/module is executing.
Controller Can Hang if Tool Port Cable is
not Connected in the Other End
A cable connected to the tool port on the
CPU (COM4), may cause the controller to
hang during startup, if the cable is
unconnected in the other end, or if the PC
it's connected to is unpowered.

800xACON-OL-4100-009
Error Printout in Controller Log from The errors are harmless, but to avoid the printout,
CI853 turn off logging of Severity low errors in the Control
When using CI853, logging severity low Builder in the "Controller Settings menu".
errors (done by changing Error handler
settings under "Controller settings menu")
might result in error logs:
E 2004-10-12
[Link].336
ErrorHandler PM: CON
4119 Spur CEX IRQ 9
(1,1) spur IRQ since
start

800xACON-OL-4100-010

82 3BSE033044D5001
Section 5 Known Problems Controller

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Corrupt Flash Card is not Indicated No solution/workaround exists.
Properly
You will receive an error message the first
time a corrupt flash card is detected by the
controller. However, if you remove the
corrupt flash card and then reinsert it again
you will not get any indication that the card
was reinserted. It will take 28 hours until it is
indicated that the card still is corrupted.

800xACON-OL-5000-002
Save Cold Retain on Compact Flash Check that the Compact Flash card is properly
Card Fails mounted and restart the Controller.
If save cold retain values on the Compact
Flash fails you will get the error code -42.

800xACON-OL-5000-006

3BSE033044D5001 83
Communication Section 5 Known Problems

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

Communication
Settings for RNRP and for PPP Lost in a To get the correct settings into the controller,
Redundant CPU connect a PC with the Control Builder to the same
Settings for RNRP and for PPP may be lost network area as the controller and download a
after a power fail, if the battery is removed project with the correct RNRP and/or PPP settings.
or low during the power fail.
In such a case the application is as normally
lost, but additionally it may not be possible
to communicate with the Controller from the
Control Builder.
The problem happens if one CPU is primary
when the configuration is downloaded and
the other CPU is primary after the startup.
This should normally only be a problem in
these cases:
• If the Control Builder uses PPP to
communicate with the Controller
• If explicit RNRP configuration is used
and the Controller and the Control
Builder are connected to different
network areas.
See also RNRP Settings Lost after
Firmware Upgrade on page 94.

800xACON-OL-4100-011
Shutdown of Active PPP Node can Make sure the active controller doesn't stop. Use
Cause other Node to Crash UPS (Uninterruptedly Power Supply) if necessary.
The controller acting as a passive PPP Or try to use other communication protocols, if
node may crash if the controller acting as possible.
the active PPP node is shut down.

800xACON-OL-4100-012

84 3BSE033044D5001
Section 5 Known Problems I/O Handling

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

I/O Handling
Modulebus I/O Started too Late Use the [Link] value to interlock start-up
Warning! actions.
Start of Applications and Modulebus I/O are
not synchronized at startup. The controller
applications may start before all Modulebus
I/O has been started.

800xACON-OL-4100-013
I/O Running on CI865 Started too Late Use the [Link] value to interlock start-up
Warning! actions.
Start of Applications and I/O running on
CI865 are not synchronized at startup. The
controller applications may start before all
CI865 I/O has been started.

800xACON-OL-5000-010

3BSE033044D5001 85
I/O Handling Section 5 Known Problems

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


OSP Values are Reset During Startup Prior to the download; make sure the process is set
Warning! into a state were it can accept the temporarily de-
The following issue occurs after the energized outputs.
application(s) in the controller for some
reason are erased (for example after a
power fail with no attached battery or after
making a long press on INIT). The I/O
channels will in this state have entered their
pre-configured OSP values. In order to
restart the controller, the application(s) must
be re-downloaded from Control Builder.
When the download of the application(s) is
performed, just before the applications are
restarted, I/O channels with pre-
configured OSP values will be de-
energized for a couple of seconds. After
that, the I/O will be set by the now running
application(s).

800xACON-OL-4100-014
S800 I/O Linearization For AI845 single range 4-20 mA sqrt can be used.
An S800 I/O analog input signal set to 4-20
mA will, if it is set to Linearization and
connected via direct Modulebus, warn for
underflow at 3.74 mA instead of normally 2
mA.

800xACON-OL-4100-015

86 3BSE033044D5001
Section 5 Known Problems I/O Handling

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


S100 I/O Status Indication
A disconnected or broken S100 cable
between the CI856 module and an I/O rack
gives no error indication in the hardware
tree on the S100 rack level or for the bus
extender module. The same indication
problem also arises at a power down of
aS100 rack.
Note that all I/O modules in the rack are
correctly error marked if this happens.
The problem concerns only the hardware
units representing the rack itself and the bus
extender module.

800xACON-OL-4100-016
S100: No Indication at Dropped SOE Use several CI856 communication interfaces if
Events there is risk of alarm bursts from several S100 I/O
There is no overflow indication from CI856 racks.
when a SOE has been dropped.

800xACON-OL-4100-017
S900: I/O OSP Cleared
Warning! OSP on S900 I/O will be cleared
in the following two occasions:
• During a short period of time after
resuming after a controller power fail.
• Controller task abort, due to that a task
has executed too long.

800xAIO9-OL-4100-001

3BSE033044D5001 87
I/O Handling Section 5 Known Problems

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Unable to Acknowledge Warning for
CI920
If a redundant pair of CI920 is configured,
the hardware status displayed in the Control
Builder is "redundant switch over"; this
warning is not possible to acknowledge.
The functionality of the S900 I/O does not
affect this case.

800xACON-OL-4100-018
No Channel Error from S900 I/O if Wire
Break or Short Circuit
Digital inputs, digital outputs and analog
outputs on S900 I/O does not report data
quality 'bad' in the [Link]
component in case of wire break or short
circuit. This is because S900 I/O sends this
information via PROFIBUS diagnostics.
A line fault on such channels results in:
• No system alarm with plain text
• A PID controller may go into windup
• The OPC status will not show bad

800xACON-OL-5000-004
Problem to Use Short I/O Scan Cycle Set Modulebus scan cycle time to max 90ms.
Time in Redundant AC 800M Using
DP820
Scan cycle time less than 90ms results in
that DP820 will go to OSP state for some
seconds.

800xACON-OL-5000-008

88 3BSE033044D5001
Section 5 Known Problems PROFIBUS-DP

Table 11. Operational Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

PROFIBUS-DP
PROFIBUS Slave CI840 does not Report
which I/O Module Acting as
Primary/Backup
Information about redundant I/O-modules is
missing in the status component of the
IEC61131-3 data types BoolIO or RealIO, if
the redundant I/O-module is connected via
the PROFIBUS slave CI840.
This means that the function block
RedundantIn will not ramp as expected for
I/O connected on PROFIBUS at switch-
over.

800xACON-OL-4100-019

3BSE033044D5001 89
Configuration Section 5 Known Problems

Configuration
Table 12 lists the issues that may exist and affect configuration of the system or
product at time of release. Workarounds, clarifications, or helpful hints have been
provided for each issue wherever possible.

Table 12. Configuration Issues

Issue Workarounds, Clarifications, and Helpful Hints

Control Builder
Not Allowed Using Recursive Relations If the Control Builder is not responding it has to be
between Objects or between Libraries killed using Task Manager and then restarted.
It is not allowed to use recursive relations
between objects or between libraries. If
used the Control Builder may hang.
For example, if there exists two function
block types A and B, you can declare a sub
object of type A in type B, but if later on
trying to declare a sub object of type B in
type A the Control Builder might hang when
the editor content is saved.

800xACON-CN-4100-002
Settings in Time Synch. Dialog in Avoid pressing Enter. Close the menu with Save
Control Builder Fails and Close or Save to affect the new setting.
When the input fields in the Set Time dialog
in Control Builder are edited (time settings
are changed) and then Enter is pressed,
the time is not changed.

800xACON-CN-4100-006

90 3BSE033044D5001
Section 5 Known Problems Control Builder

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Changing CPU Type from PM851 The hardware configuration related to the currently
All I/O-modules on module bus will be used PM851 CPU type e.g. hardware topology,
removed if the CPU type PM851 is changed parameter settings and I/O-connections has to be
to any other CPU-type e.g. PM860. All manually stored before the CPU type is changed.
parameter settings and I/O-connections This could be done by manually copying relevant
related to these I/O-modules will be information unit by unit to an excel sheet. After the
removed. CPU type has been changed, the stored
information has to be manually copied back.
800xACON-CN-4100-008
Power-fail During Download Might Fail
If power fails during download the controller
may end up in a state where further
reconfigurations are not possible. This will
be indicated on the next attempt. To
reconfigure the controller a Controller reset
is necessary.

800xACON-CN-4100-010

3BSE033044D5001 91
Control Builder Section 5 Known Problems

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Running Control Builder and Do not simultaneously run more than one Control
SoftController, on Remote Builder or SoftController on a PC.
Desktop/Terminal Server
The use of Remote Desktop/Terminal
Server is only to be used for operations.
Running Control Builder, on Remote
Desktop/Windows Terminal Server is not
supported.
Problems that have been found are:
- Mysterious Source Code errors (loss of
data)
- Communication problems (MMS Server,
for example communication with AC 800M
controllers)
- Clipboard problems (Copy/paste)
- Problems with log files

800xACON-CN-5000-002
Firmware Upgrade After Remove of Start a new firmware upgrade and verify that the
Applications in Controller Fails firmware has been updated in the controller by
If application(s) are removed from a running using the "Firmware Information" button in the
controller from the "Application Information" "Remote system dialog" or check the controller log.
dialog and then a firmware upgrade is
started from the "Firmware Information"
dialog the controller will restart and the
"Firmware Information" dialog is closed
when the controller is up and running again,
but the firmware isn't upgraded.

800xACON-CN-5000-003

92 3BSE033044D5001
Section 5 Known Problems Control Builder

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Control Builder May Crash when Remove the simulation mark on the Controller
Reconnect Hardware Libraries on before reconnect of the hardware libraries and
Simulated Controller restore it.
The Control Builder may crash if hardware
libraries are replaced in a simulate marked
controller.

800xACON-CN-5000-004
Hardware Unit Delete/Move Attached to Do hardware tree changes and parameter changes
CI865 and Parameter Changes Cannot be at separate downloads:
Done at the Same Time 1. Perform hardware tree changes.
If a hardware unit attached to CI865 is 2. Download the project.
deleted or moved and any of the
3. Go offline and perform the parameter changes.
parameters of CI865 are changed, the
parameter changes for CI865 will not be 4. Download the project.
handled at the next project download. The order of 1 and 3 can be chosen arbitrarily.

800xACON-CN-5000-012
Download of Controller Configuration
when “Going Online Without Download”
If a change is made in an application, but
not downloaded, some data still may be
downloaded to the controller when “Going
online without download”. The data is
harmless and does not affect the
functionality.

800xACON-CN-5000-015

3BSE033044D5001 93
Communication Section 5 Known Problems

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Project Documentation from Control Instead of one big documentation of for example a
Builder large library, divide it into several smaller pieces
When using the menu entries like data types, function blocks and control
“Documentation…” and “Documentation modules.
Online…” in the Control Builder it is
important to not generate to many pages.
The time needed to generate the
documentation in word increases
dramatically when the number of pages
increases. Sometimes it will take long time
before the “Cancel” command is accepted
by the system; if the document that is to be
generated is very large.

800xACON-CN-5000-006

Communication
RNRP Settings Lost after Firmware To get the correct settings into the controller,
Upgrade connect a PC with the Control Builder to the same
The controller may lose the RNRP settings network area as the controller and download a
in the controller when upgrade of firmware. project with the correct RNRP and/or PPP settings.
If the controller is located in another
network area it is not possible to
communicate with the controller from the
Control Builder anymore.
See Also Settings for RNRP and for PPP
Lost in a Redundant CPU on page 84.

800xACON-CN-5000-017

94 3BSE033044D5001
Section 5 Known Problems Communication

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


The IP address can be changed if no
Insum Connect Hangs after Changing
INSUMConnect that refers to this hardware unit
Gateway Address
has (ever) been enabled (En_C=true).
If the IP address of an INSUMGateway (the
Some methods to change the IP address of an
hardware unit in the hardware tree) is
INSUMGateway:
changed there is a risk that the Control
Builder hangs and the controller needs to 1. Delete the INSUMGateway from the hardware
be restarted at a subsequent project tree
download. 2. Download and Go Online
3. Go offine
4. Add the INSUMGateway and the INSUM
Devices (for example MCUs) connected to it.
Make sure that the INSUMGateway uses the
correct IP address.
5. Download and Go Online
6. Toggle the En_C on the INSUMConnect block
An alternative that can be used if there is only one
INSUMGateway connected to the CI857 in the
hardware tree, or if it does not matter if the
connection to this gateway is lost for some time:
1. Move the CI857 to a different (free) position in
the hardware tree
2. Download and Go Online
3. Go Off Line
4. Move CI857 back to the original position. Make
sure that the correct IP address is used
5. Download and Go Online
6. Toggle the En_C on the INSUMConnect block
This method does not work well if another
INSUMGateway is connected to the
INSUMGateway, and it is supposed to work
800xACON-CN-5000-024
uninterupted.

3BSE033044D5001 95
Communication Section 5 Known Problems

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints


Operation of MCUs (and other INSUM The problems disappear as soon as the status of
Devices) does Initially not Work after the device is changed in some way. This can be:
Online Reconfiguration • Disconnect the device physically and reinsert
The operation of an MCU (or other Insum it again if it was connected
device) does initially not work if the • Connect the device if it was disconnected
corresponding hardware unit is added in an • Restart the corresponding Insum Gateway
online reconfiguration: • Disconnect and reconnect the Ethernet cable
• The unit status is empty=0 to the Insum Gateway
independent of if the MCU is • Hot Swap the corresponding CI857
connected or not. • Restart the controller
• If an INSUMReceive is used towards • Start the device if it was stopped
this device it gets status -7203 • Stop the device if it was started
cPHReadWrongProgIdReceived, Start/Stop Commands can for example be sent
Wrong program ID received. from the INSUM OS or the INSUM MMI
• If an INSUMWrite is used towards this The problem does not appear for the devices that
device it gets status -7157 are included in the hardware tree in the initial
cPHGwMsgStatusError and download of the project. The problem does also not
GWMsgStatus is 503 appear for devices that are added in an online
E_ILLEGAL_DEV_TYPE, Wrong change if they are added together with a new
device type (mostly ProgId). INSUMGateway hardware unit.
Once the status is indicated correctly the operation
and status indications will work properly as long as
the device is not removed from the Controllers
hardware tree.
Suggested workflow to avoid the problem if devices
need to be added in the hardware tree online:
1. Download the new controller configuration
2. Connect the physical devices
Before the devices are connected the Hardware
tree will incorrectly indicate that the devices are
OK, but the status will be=0.
When the devices are connected they will be
possible to use and the hardware tree will show
800xACON-CN-5000-025 correct status.

96 3BSE033044D5001
Section 5 Known Problems I/O Handling

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

I/O Handling
DP840 Scaling Frequency Input
The frequency input range for DP840
connected to CI801 or CI840 is fixed at
0...20 000 Hz, even though Min and Max
scaling properties has been altered.

800xACON-CN-4100-015
DP840 Variable Connections for Pulse Ensure that the variable connection matches the
Count and Frequency channel configuration of the DP840. Connect an
DP840 can be configured for either pulse application variable to the pulse count channel of
count or frequency measurement where the DP840 to get the values in the hardware editor.
frequency is the default. If the application
variable is not connected to the input
channel that corresponds to the
configuration, the values are interpreted
wrongly, which may lead for example to
faulty alarms. Furthermore, pulse count
values are not visible in the Hardware editor
when no variable is connected to this
channel.

800xACON-CN-4100-016
The Relation Between EPR and NUT in is Use only allowed relation between the parameters
not Correctly enforced in the Control NUT and EPR, even if the Control Builder also
Builder for CI865 accepts other relations.
The Control Builder allows any multiple, that
is EPR/NUT=1,2,3,4,5,6,7,8, but EPR
actually needs to be an even multiple of 2 of
NUT, that is EPR/NUT=1,2,4,8

800xACON-CN-5000-013

3BSE033044D5001 97
I/O Handling Section 5 Known Problems

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

Problems Changing EPR for a 200-ACN To get the node connected again:
or 200-RACN • Go offline
It's not possible to change EPR for a node • Change EPR back to the old value
to a higher value than the value it first got • Go Online with Download
from the Controller.
To change the EPR for the node to a higher value:
• Go offline.
• Change the EPR
• Do a Controller Reset, for example by a long
Init (or by a power down/up without a battery),
or alternatively do as follows:
1. Move the CI865 to an empty position in the
Hardware tree
2. Download and Go Online
3. Go Offline
4. Move CI865 back to its correct position in
the hardware tree.
• Go Online with Download
Note that there is no problem to change the EPR
for a node to a lower value than the original.
Another way to work around this problem is the
following:
• Set the default EPR in the CI865 settings to
the highest possible value depending on the
used NUT (EPR/NUT = 1, 2, 4 or 8)
• Set EPR for every node to “Use Default value”
• Go online (all nodes should be successfully
connected)
• Go offline
• Change the EPR to lower values for the nodes
that require it
800xACON-CN-5000-014 • Go Online with Download

98 3BSE033044D5001
Section 5 Known Problems PROFIBUS-DP

Table 12. Configuration Issues (Continued)

Issue Workarounds, Clarifications, and Helpful Hints

PROFIBUS-DP
Deactivating of S900 I/O Channels, in Remove and reinsert the S900 I/O-module.
Control Builder, is not Working Properly
Deactivating S900 I/O-channels via the
hardware configuration in Control Builder is
not working correctly. The I/O-channel
status supervision could be indicated
wrong.

800xACON-CN-4100-017
CI854 Baudrate Change with Many If RLM01 is used on the PROFIBUS with CI854(A)
Disturbed Slaves does not Work and many slaves are configured, the PROFIBUS
Baudrate change with use of RLM01 and might stop if the baudrate is changed from higher
many slaves might stop the PROFIBUS. to lower values. The CI854(A) might go into STOP-
mode. The change from lower to higher values
works normal. Before downloading the changed
baudrate with Control Builder, adjust the RLM01 to
800xACON-CN-5000-010 the new baudrate.
Default value inside UserPrmData in UserPrmData which is affected by user parameters
GSD not handled shall be set to 0 in GSD before import.
If a GSD defines default values inside the
UserPrmData string, parameters connected
to this data will not have any effect when the
file has been imported to Control Builder.

800xACON-CN-5000-016

3BSE033044D5001 99
Instruction Manual Changes Section 5 Known Problems

Instruction Manual Changes


Table 13 list the problems or issues in the instruction manuals that exist at product
release. The corrections to the instruction have been indicated.

Table 13. Instruction Manual Changes

Instruction Error (Page) Change or Correction


Control Builder online help n/a Redundant CI854A Support
Control Builder does not prevent
configuring a redundant CI854A
pair with CPUs other than
PM861A, PM864A, and PM865.
However, a redundant CI854A pair
will only work with those CPUs.
Use redundant CI854A only on
800xACON-MC-5000-005 PM861A, PM864A, or PM865
CPUs.
Control Builder online help Insum Status Codes Missing in
Online Help:
-7207
cPHReadOnDisconnectedGW
INSUMReceive tried to access an
MCU via a Gateway which is
disconnected
-7307
PHWriteOnDisconnectedGW
INSUMWrite tried to access an
MCU via a Gateway which is
disconnected
-7308 PHWriteTimeout
INSUMWrite failed to send to the
MCU

Controller

100 3BSE033044D5001
Section 5 Known Problems Controller

Table 13. Instruction Manual Changes

Instruction Error (Page) Change or Correction


AC 800M Controller SB822 Documentation Missing
Hardware, Hardware and Documentation regarding the new
Operation rechargeable battery unit, SB822,
is missing in the manual. See data
sheet 3BSE047037 for data on the
product.

3BSE033044D5001 101
Controller Section 5 Known Problems

102 3BSE033044D5001
3BSE033044D5001. Printed in Sweden March 2007
Copyright © 2003-2007 by ABB. All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.

[Link]

Automation Technology Products Automation Technology Products Automation Technology Products


Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
[Link]/controlsystems [Link]/controlsystems [Link]/controlsystems

Common questions

Powered by AI

The issue where a controller shutdown occurred during the download of a new application to a pre-existing task has been resolved. This was significant because it could interrupt operations and data handling, posing reliability risks in environments dependent on continuous control processes .

The issue causing the Control Builder to shut down when attempting to modify a simulated I/O module accessed via the 'Search & Navigation' tool has been corrected. This fix enhances software stability and reliability during interface navigation and editing tasks .

To prevent the loss of RNRP settings after a firmware upgrade, it is necessary to ensure that a PC with the Control Builder is connected to the same network area as the controller. Afterward, a project with the correct RNRP (and possibly PPP) settings must be downloaded to the controller . This procedure is crucial because the controller may lose these settings during a firmware upgrade, which can result in loss of communication from the Control Builder if the controller is in another network area . Furthermore, if RNRP configurations are specific and the Control Builder and the controller are in different network areas, settings can also be lost after a power failure if the battery is removed or low . Ensuring settings are correctly redeployed prevents communication disruptions and maintains network configuration stability .

Graphical connections in the Control Module Diagram lost their nodes during certain editing processes, resulting in misplacements. This was resolved by reinforcing the link integrity and spatial consistency to ensure reliable representation and use of graphical elements .

Incorrect hardware definitions for the AO930 module led to controller shutdowns because of issues with the Device Import Wizard while handling third party hardware definition files. When a project upgrade occurred, the creation of new hardware libraries added incorrect hardware objects that were not compatible with the controller, leading to system errors or shutdowns if these libraries were used without proper configuration validation . To resolve this, a new workflow was introduced where users can reorganize hardware objects by creating libraries and ensure configuration changes do not cause system failures by performing hardware tree changes and parameter changes at separate download instances . Additionally, firmware adjustments were made to avoid reliance on built-in hardware types, allowing downloads of necessary protocol handlers instead .

The 'No System Identity' issue in Control Builder was addressed by correcting the problem where the system would sometimes lose its SystemID after a restart. This led to an inability to communicate with any controller, as the IP address would disappear from the "About Control Builder" box. Resolving this issue was important because it ensured reliable communication and functionality across the system in Control Builder, preventing operational disruptions . Additionally, maintaining SystemID is crucial for identifying and managing components within the control system accurately, which is key for stability and diagnostics .

The problem identified with the representation of I/O Module status in redundant setups was that after a HotSwap of CI854, the status indication for some I/O modules incorrectly showed 'Device not found' despite being in correct working order. This issue was particularly evident in configurations with a large amount of configured slaves. The problem has been corrected by ensuring the status indication reflects accurate device status post-HotSwap . Additionally, a related problem in redundant settings was that the PROFIBUS Slave CI840 did not report which I/O Module was acting as Primary or Backup, affecting the expected ramp-up behavior during a switch-over. This issue was noted as unresolved, indicating ongoing representation issues in certain scenarios .

Changing the 'Scan interval' parameter in the S100 I/O board led to an inconsistency problem in the multi-byte speed measuring counter, which caused disturbances appearing with a few seconds interval. The issue was corrected with the update, removing the disturbance from the S100 board . Alternatively, for scanning issues related to DSDI 110, using scanning instead of interrupt-based updating was suggested, with the possibility of restarting by hot removing and reinserting CI856 .

Renaming an FBD/LD code block could corrupt another code block if the new name began identically to another block’s name (e.g., renaming 'Test_2' to 'Test'). This problem has been addressed and corrected to prevent such corruption from occurring .

The long first scan execution time was caused by Alarm/Event function blocks or control modules being called without specifying the 'SrcName' parameter. If 'SrcName' was left unconnected or configured with an empty string, it resulted in extended execution times for the first scan and in some cases, could lead to task abortions . This issue was mitigated by correcting the problem, ensuring that the 'SrcName' parameter is properly defined or connected, thus preventing delays and potential task abortions during the initial scan process .

You might also like