Release Notes

Release Notes
StruxureWare™ Building Operation

v1.9.1
This document is written for and on behalf of Schneider Electric and is supplied on the express
terms that it is to be treated as confidential and that it may not be copied, used or disclosed to others
except as authorized in writing by this Company. This document is intended for internal use only.
[ Release Notes ] StruxureWare™ Building Operation v1.9.1
Table of contents
1. INTRODUCTION ........................................................................................................................... 6
1.1 Change History........................................................................................................................................ 7
2. STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE AVAILABILITY........................ 8
3. NEW FEATURES IN STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE ............... 9
3.1 Install/Upgrade ........................................................................................................................................ 9
3.2 Device and System Settings .................................................................................................................. 9

3.2.1 Set Date and Time on Automation Server from WebStation ................................................................................... 9
3.3 Cybersecurity .......................................................................................................................................... 9

3.3.1 TLS 1.2 support ..................................................................................................................................................... 9
3.3.2 EWS Interface support for additional HASH algorithms .......................................................................................... 9
3.3.3 Policy options for embedded web content .............................................................................................................. 9
3.3.4 Device Administrator - SSH Public Key Validation ................................................................................................ 10
3.4 WebReports ........................................................................................................................................... 10
3.5 Alarm Presentation ............................................................................................................................... 10

3.5.1 Condition-based Alarm Decoration Rules ............................................................................................................. 10
3.5.2 New alarm text substitution codes ........................................................................................................................ 10
3.5.3 Alarm sort order enhancement ............................................................................................................................. 10
3.5.4 Display millisecond in Alarm and Event Views ...................................................................................................... 10
3.5.5 Relative path in Alarm and Event view ................................................................................................................. 10
3.6 Search, Navigation and List Views ...................................................................................................... 11

3.6.1 Relative search path ............................................................................................................................................ 11
3.6.2 Content types - Default and Favorites List View settings ...................................................................................... 11
3.6.3 Panel Navigation Pane type – custom tree ........................................................................................................... 11
3.6.4 Search forced values improvements .................................................................................................................... 11
3.6.5 Find instances ...................................................................................................................................................... 11
3.6.6 Mass rename ....................................................................................................................................................... 11
3.6.7 Intellisense in the Binding View ............................................................................................................................ 11
3.7 Notification ............................................................................................................................................ 11

3.7.1 Notification Reports .............................................................................................................................................. 11
3.7.2 Default email server change ................................................................................................................................. 12
3.8 Users, permissions and logon ............................................................................................................. 12

3.8.1 Guest account ...................................................................................................................................................... 12
3.8.2 Auto login Guest .................................................................................................................................................. 12
3.8.3 New permission levels.......................................................................................................................................... 12
3.8.4 Password policy exclusion – Password never expires .......................................................................................... 12
3.8.5 Registration information at login ........................................................................................................................... 12
3.9 Trends .................................................................................................................................................... 12

3.9.1 Maximum number of trend records ....................................................................................................................... 12
3.9.2 Dynamic Trend Chart title..................................................................................................................................... 12
3.10 Schedules / Timers ............................................................................................................................... 13

3.10.1 Simple timed force objects ............................................................................................................................... 13
Schneider Electric
Boston ONE Campus, 800 Federal Street, Andover, MA 01810 Telephone +1 978-794-0800 www.schneider-electric.com
RN_SBO_v1.9.1 – April 2017 Page 2 of 60 Company Confidential
© 2017 Schneider Electric, all rights reserved

3.11 Script Editor........................................................................................................................................... 13
3.12 Troubleshooting / Diagnostics ............................................................................................................. 13

3.12.1 Serial Port Logs ............................................................................................................................................... 13
3.13 Export / Import ....................................................................................................................................... 13

3.13.1 Merge data during Import................................................................................................................................. 13
3.13.2 Support for previous Export files ...................................................................................................................... 13
3.14 BACnet® enhancements ....................................................................................................................... 13

3.14.1 BTL® Certification ............................................................................................................................................ 13
3.15 Modbus enhancements ........................................................................................................................ 14

3.15.1 Extended Modbus Device Address Range ....................................................................................................... 14
3.15.2 Modbus Multibit Objects................................................................................................................................... 14
3.16 LON enhancements............................................................................................................................... 14

3.16.1 Upload XIF from device ................................................................................................................................... 14
3.16.2 Support for LON configuration parameters using FTP ...................................................................................... 14
3.17 EWS enhancements .............................................................................................................................. 14

3.17.1 Web Services domain login ............................................................................................................................. 14
3.18 Andover Continuum Transition ........................................................................................................... 14

3.18.1 Andover Continuum Conversion Program ........................................................................................................ 14
3.18.2 Support for Infinet ............................................................................................................................................ 14
3.19 Satchwell Sigma Transition .................................................................................................................. 15

3.19.1 New Sigma TGML Schedules .......................................................................................................................... 15
3.19.2 Sigma Short Form Edit support for Alarms ....................................................................................................... 15
3.19.3 Sigma Commands for Controller Warm & Cold Start ........................................................................................ 15
3.19.4 Sigma Action Schedules .................................................................................................................................. 15
3.19.5 Sigma Mnemonic available in Alarm Viewer..................................................................................................... 15
3.19.6 Sigma Long Texts ............................................................................................................................................ 16
3.19.7 Sigma Log Set Description in System Tree ...................................................................................................... 16
3.19.8 Sigma Log Set Wizard ..................................................................................................................................... 16
3.19.9 Sigma Log Set Objects .................................................................................................................................... 16
3.19.10 Import of Sigma Historical Logs ....................................................................................................................... 16
3.19.11 Support of Sigma Log Objects from TGML ...................................................................................................... 16
3.19.12 Support of Notification Reports for Sigma Logs ................................................................................................ 16
3.19.13 Simplified Engineering of Sigma Globals ......................................................................................................... 16
3.19.14 Support for Sigma Link Addressing .................................................................................................................. 17
3.19.15 Sigma RUDs and Globals Monitoring ............................................................................................................... 17
3.19.16 Enhancement to Data Import of Sigma Log Sets.............................................................................................. 17
3.19.17 Sigma Database Alignment ............................................................................................................................. 17
3.19.18 Alternative Sigma Navigation View .................................................................................................................. 18
3.19.19 Automatic Configuration of Sigma Controller Communication Timers .............................................................. 18
3.20 TAC I/A Series – Native MNB Support and Transition ....................................................................... 18
3.20.1 Operating system and Visio support ................................................................................................................ 18
3.20.2 WorkPlace Tech Monitor for MNB devices ....................................................................................................... 18
3.20.3 Backup and restore MNB COV client object configurations .............................................................................. 18
3.20.4 Backup and restore MNB VAV flow balance configurations ............................................................................. 19
3.20.5 Monitor and write-to-RAM in WorkPlace Tech Editor ....................................................................................... 19
3.21 TAC I/NET Transition ............................................................................................................................ 19

3.21.1 Updated Icons ................................................................................................................................................. 19
3.21.2 Enhanced Performance of the USB-485-INET ................................................................................................. 19
3.21.3 Additional DCU Properties ............................................................................................................................... 19
3.21.4 Time Scheduling Point Extension..................................................................................................................... 19
Schneider Electric

3.22 TAC Vista – Native Xenta Support and Transition ............................................................................. 20

3.22.1 Support for Xenta 122 as a built-in device........................................................................................................ 20
3.22.2 Xenta Group editor .......................................................................................................................................... 20
3.22.3 Enhanced support for ‘TAC Vista to SBO transition tool’ .................................................................................. 20
3.22.4 Xenta 400 I/O modules .................................................................................................................................... 20
4. DEFECTS FIXED IN STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE ............. 21
5. KNOWN DEFECTS IN STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE .......... 33
6. IMPORTANT ENGINEERING INFORMATION ........................................................................... 46
6.1 General Engineering ............................................................................................................................. 46
6.2 WebStation ............................................................................................................................................ 47

6.2.1 Graphics Viewer ................................................................................................................................................... 47
6.2.2 Workspace and Panels ........................................................................................................................................ 47
6.2.3 General information.............................................................................................................................................. 47
6.2.4 Security ................................................................................................................................................................ 47
6.3 Graphics................................................................................................................................................. 47
6.4 LonWorks............................................................................................................................................... 48
6.5 b3 Devices ............................................................................................................................................. 48
6.6 Trends .................................................................................................................................................... 49
6.7 Archiving ................................................................................................................................................ 49
6.8 Web Services ......................................................................................................................................... 49
6.9 Reports................................................................................................................................................... 50
6.10 Authentication ....................................................................................................................................... 50
6.11 Schedules .............................................................................................................................................. 50
6.12 WorkStation Alarm/Client Notifications .............................................................................................. 50
6.13 WorkStation Alarm/Email Notifications ............................................................................................... 51
6.14 Import / Export ....................................................................................................................................... 51
6.15 Search .................................................................................................................................................... 51
6.16 Sigma ..................................................................................................................................................... 51
6.17 Xenta 400 Series I/O Modues ............................................................................................................... 52
7. APPENDIX A – STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE

DELIVERABLE ................................................................................................................................... 53
Schneider Electric

8. APPENDIX B – KNOWN ISSUES ............................................................................................... 54
9. APPENDIX C – PROCEDURES ................................................................................................. 55
9.1 Installing ................................................................................................................................................ 55
9.2 Upgrading .............................................................................................................................................. 55

9.2.1 General Upgrade Information ............................................................................................................................... 55
9.2.2 Memory Consumption Before Upgrade ................................................................................................................ 57
9.2.3 Upgrading a System with LON devices from version 1.5/1.6/1.7 .......................................................................... 57
9.2.4 Upgrading a System with LON devices from version 1.8 ...................................................................................... 58
9.2.5 Delete obsolete objects after upgrading a System with LON devices ................................................................... 59
9.2.6 Update objects and tools that use path based LON references ............................................................................ 60
9.2.7 Forced Change of Default Password .................................................................................................................... 60
9.3 Commissioning ..................................................................................................................................... 60
Schneider Electric

1. Introduction
The StruxureWare™ Building Operation Release v1.9.1 Release Notes document includes
information about the new release as well as some general information about the StruxureWare
Building Operation products. The general information can be found in the numerous APPENDIX
sections.
Release v1.9.1 allows a user to upgrade from any previous release that is v1.5.xxx or later. Prior
to accomplishing any upgrade, refer to the upgrade documentation. In addition, some of the
features that have been added between 1.5 and 1.9 have increased the amount of memory that
is used. It is critical that users with Automation Servers (AS) that use large amounts of memory
read the appropriate section in 9.2 of this document. (Although this issue is most apparent with
the Automation Server (AS) since it has a smaller amount of memory, it is also valid for AS-P
and all models of AS-B.
NOTE – Release v1.9.1 offers the possibility to upgrade a system in a non-sequential way. Any
SmartStruxure solution that is currently at v1.5 or higher can be upgraded directly to v1.9.1.
These release notes describe the changes that have been made since v1.8. If you are upgrading
from a version that is older than v1.8, it is important for you to read the earlier Release Notes
which can be found here:
StruxureWare Building Operation v 1.5.1 Release Notes
Release v1.9.1 of StruxureWare Building Operation provides many new features for the user in
the following areas:
 Install/Upgrade
 Device and Systems Settings
 Cybersecurity
 HTTPS support in WebReports
 Alarm Presentation
 Search, Navigation and List Views
 Notification
 Users, permissions and logon
 Trends
 Schedules/Timers
 Script editor
 Troubleshooting/Diagnostics
 Export/Import
 BACnet
 Modbus
 LON
 Web Services, EWS
 Andover Continuum™ Transition
 Satchwell Sigma™ Transition
 TAC I/A Series™ Transition
 TAC I/NET™ Transition
 TAC Vista™ Transition
The feature enhancements for each of these areas can be found with details in Section 3.
Note: It is imperative that any upgrades be accomplished only after reading and understanding
this document, especially those areas that are related to the transition process.
Schneider Electric

If you are a user of any model of SmartX Controller - AS-B, please reference TPA-SBO-16-
0010.00 AS-B – Important software update.
As announced in PA-00500, the Automation Server is to be ordered only for service parts.
Consequently, any new Automation Servers that are purchased will be shipped with version
1.8.1. There will be no new Automation Servers shipped with version 1.9.1.
1.1 Change History
Revision Date Revision/Author Description/Change

01 April 3, 2017 D. White Initial Version
02 May 8, 2017 D. White Fixed defect 32147
Schneider Electric

2. StruxureWare Building Operation v1.9.1 Release

Availability
The software and firmware included in the StruxureWare Building Operation v1.9.1 Release
deliverable is available for download on The Exchange.
For additional information about the deliverables see Appendix A – StruxureWare Building
Operation Release v1.9.1 Deliverable.
Schneider Electric

3. New Features in StruxureWare Building Operation

v1.9.1 Release
3.1 Install/Upgrade
Release v1.9.1 offers the possibility to upgrade a system in a non-sequential way. Any
SmartStruxure solution that is currently at v1.5 or higher can be upgraded directly to v1.9.
See APPENDIX C, Section 9.2 Upgrading for details on the upgrade procedure.
3.2 Device and System Settings

3.2.1 Set Date and Time on Automation Server from WebStation
It is now possible to set the Date and Time on the Automation Server directly from WebStation.
3.3 Cybersecurity
3.3.1 TLS 1.2 support
HTTPS communications now supports TLS 1.1 and TLS 1.2 in addition to existing support for TLS
1.0. The versions of TLS that may be used is specific to each HTTPS communication path:
 SmartStruxure servers (server-to-server) – TLS 1.2 only

 WorkStation - TLS 1.2 only
 WebStation - TLS 1.0, 1.1 or 1.2.
o The TLS version used by WebStation is dependent on the settings configured in the
Web Browser.
 AdaptiApps – TLS 1.2
3.3.2 EWS Interface support for additional HASH algorithms

The EWS Interface now supports SHA2-256 in compliance with RFC 7616. When MD-5 HASH
algorithm use is disabled in SBO, EWS connections can be validated with the SHA2-256 HASH
algorithm if supported by the connecting system.
3.3.3 Policy options for embedded web content

There are two new settings which can be used to protect SBO presented Web content so it is
resilient against clickjacking vulnerabilities:
Option 1) Enable external content to be embedded in WebStation – This option must be selected to
permit browser to render a <frame> or <iframe>. To protect against clickjacking for all use cases,
this option should be turned off.
Option 2) Enable WebStation to be embedded in another site – This option permits a browser to
render a <frame> or <iframe> from the local server. If this option is selected with option 1, then there
is no protection against clickjacking.
The most secure and recommended configuration is when both options are turned off. However,
when an application requires embedded web content, these options can be turned on.
Schneider Electric

3.3.4 Device Administrator - SSH Public Key Validation

Fingerprints of the public key of each SmartStruxure server device are stored automatically the first
time the Device Administrator connects to it. Matching fingerprints are required for connection. This
prevents an impersonating device from receiving the user name and password.
SmartStruxure server devices that are replaced or installed with DFU mode with have mismatched
fingerprints. The new fingerprint can be accepted in those valid use cases by the operator.
3.4 WebReports
 It is now possible to access the WebReports URL using https
 Configure SSL certificate
 Ensure WebReports Website is accessible using Web browser
 Change the Website and WebService URLs in the Report manger object of Enterprise
Server
Note: Create New Report functionality from WorkStation will not work for Self Signed
Certificates, if they are not trusted under Trusted Root Certification Authorities.
3.5 Alarm Presentation

3.5.1 Condition-based Alarm Decoration Rules
It is now possible to setup an Alarm Decoration Rule to override alarm properties when a filter
condition is met. The Alarm Decoration Rule can include overriding alarm presentation, user actions
and attachments (including Alarm test message, Font color, Cause note, Checklist and Required
User Actions), when an alarm meets the filter conditions.
These Alarm Decoration Rules can also be used to configure and separate System Alarms. Multiple
Alarm Decoration Rules can be configured; they are executed from top to bottom when the alarms
trigger.
3.5.2 New alarm text substitution codes

It is now possible to type any of the 65 alarm substitution codes in the alarm text fields. Intelli sense
will guide the user after @( is typed.
3.5.3 Alarm sort order enhancement

When changing alarm sort order in the alarm view, it will apply to all users and all views.
3.5.4 Display millisecond in Alarm and Event Views

Timestamps in alarm and event viewers can now be displayed in milliseconds. This is configured
from WorkStation using the “Enable milliseconds” option for the view properties.
3.5.5 Relative path in Alarm and Event view

Standard filters in Alarm Views and Event Views support relative paths for the Source property. For
example, in a relative path: '../../*' where '../' represents a folder or other container object and '*'
represents anything below the folder or container object.
Schneider Electric

3.6 Search, Navigation and List Views

3.6.1 Relative search path
It is possible to create search objects with a relative path so that it can be copied and re-used in
many locations. Note that it must be pasted “special” in order to keep the reference.
3.6.2 Content types - Default and Favorites List View settings

The layout of a List View can now be persisted using the feature “Content types”. When the column
content, width, sort order and content group of a List View is saved as a Content type, it becomes
the default configuration for that List View for all users.
Other views can be configured with the same “Content type” reducing the engineering time to define
List Views.
The custom List View layouts can also be saved as a “Favorites.” Favorites is stored for the current
Users and is available to that user from any WorkStation and WebStation client machine. Favorites
will also store filter conditions.
3.6.3 Panel Navigation Pane type – custom tree

Using the Menu object, it is now possible to create a navigation pane where you can customize a
tree view independently from the default tree view, e.g. representing a logical view of the building,
and including or excluding particular objects. A Navigation Pane can be presented in a workspace in
place of the System tree.
In v1.9.1, this feature is only available in WorkStation. It will be available in WebStation in a future
release.
3.6.4 Search forced values improvements

It is now possible to include or exclude forced values in device when doing a search. Default is
excluding device value and only search for db value.
3.6.5 Find instances

You can select an object, right click and choose “Advanced - Find instances of this type” to search
for instances of the same type. This can for example be used to find the instances of Shared
Graphics
3.6.6 Mass rename

It is possible to rename many objects in the same view.
3.6.7 Intellisense in the Binding View

Intellisense, or auto complete, has been enabled in the edit fields of the Binding View. The auto
complete will help the user to find a path quickly, but it will not validate if the binding is valid until it is
saved.
3.7 Notification
3.7.1 Notification Reports
Notification Reports template can now also handle Events, Search and Watch.
Schneider Electric

3.7.2 Default email server change

The default email setting for a server is now changed to “Primary” instead of Schneider Electric
Email Server. The change will be applied also to upgraded servers.
3.8 Users, permissions and logon

3.8.1 Guest account
The old Guest functionality has been replaced with a new concept and a new account type - “Guest
account.” The password for this account type is not configurable and will not expire. The typical use
case for this is for auto logon to WebStation or WorkStation without credentials. It can also be
combined with the feature “Auto logoff” to automatically log on to the account. The “Guest account”
must be a member of a configured group, typically a group with read-only permissions.
Note: The old guest accounts does not work anymore and must be replaced with this new concept.
3.8.2 Auto login Guest

Setting the User Group option “Logoff to guest account” in WorkStation will force a login of the guest
account when either manually or automatically logging out from a user account in WebStation.
3.8.3 New permission levels

The previous permissions “Full access”, “Read” and “No Access” are now replaced with “Read”,
“Write”, “Create”, “Delete”, “Edit” and “Force,” which allow the user to configure more granular
permissions.
Note: “System” folder is default setup with no access and therefore at least read permissions must
be set up manually when needed, e.g. for Backup and Restore and EWS.
There is also a specific permission for “Command,” which modifies the effect of the old Command
Permission choice “No Setting”. If “Command” is set, the command permission “No Setting” means
“allow” on that path. If not set, “No Setting” means “deny” on that path.
3.8.4 Password policy exclusion – Password never expires

When the aging policy is bypassed for an account, the password will not expire. This feature is
particularly useful for non-interactive logins such as with service and guest accounts. For guest
accounts, the aging policy is always bypassed and non-configurable.
3.8.5 Registration information at login

User registration information is now presented on the login screen.
3.9 Trends
3.9.1 Maximum number of trend records
Trend record limits of 2.5 billion (ES) and 10 million (SmartStruxure server device) were soft limits.
They are now hard limits. It is not possible to save more than these amounts.
3.9.2 Dynamic Trend Chart title

Trend charts support relative property references for the trend chart title. You can reuse the trend
chart and have the trend chart title dynamically changed depending on where you paste a copy,
make a duplicate, import, or move the trend chart.
Schneider Electric

3.10 Schedules / Timers

3.10.1 Simple timed force objects
Three new Timed Force Utility objects are available with a Value property that can be forced for a
specified duration or until a specified end date and time. For more information, search for “Timed
Force Objects” in WebHelp.
3.11 Script Editor

A new polling switch has been added to the Binding Values window of the Script editor. The switch
allows you to start and stop the updating of the variables displayed in the window. If the Script
program is located at the SmartStruxure server level, the update will default to being on. (It will poll.)
If the Script program is located at a field device (b3 or i2), the update will default to off. (It will not
poll.)
3.12 Troubleshooting / Diagnostics

3.12.1 Serial Port Logs
It is now possible to extract serial port logs. When enabled the serial port logs provide information on
the data transmitted and received through the serial port, useful for low level debugging. The serial
port logs can be opened for viewing from the PortPlugInSerial object under the Modules folder. To
view the serial port logs simply select the serial port log and the default viewer for .log files will open.
Use the file save function in the default viewer to save serial port logs to disk. Do not use the right-
click "Save as..." option to save serial port logs to disk.
3.13 Export / Import

3.13.1 Merge data during Import
A new import mode is introduced that allows the engineer to add data objects in existing folders and
to update properties of existing objects.
Note: The merging capability will not allow for the updating of the “body” in private types, i.e., the
actual program in a Script or Function Block program will not be changed. The actual function in a
Script function will not be changed, and the actual picture in a graphic will not be changed.
3.13.2 Support for previous Export files

In keeping with the general policy of maintaining support for a period of time after releases are
delivered to the market, the v1.9 release will not guarantee backward compatibility to files that were
exported prior to release v1.5. See PA-00300 for more information on the SmartStruxure Software
Support Policy.
3.14 BACnet® enhancements

3.14.1 BTL® Certification
The SmartX Controller AS-P and AS-B (with SBO v1.9 firmware) has been BTL certified as a
BACnet Building Controller (B-BC) at protocol revision 12.
Schneider Electric

3.15 Modbus enhancements

3.15.1 Extended Modbus Device Address Range
The Modbus protocol defines an extended device address range for TCP devices outside the usual
1-247 addresses. In this release it is possible to define addresses for Modbus TCP devices from 1-
247 and 249-255. Device addresses 0 and 248 are reserved.
3.15.2 Modbus Multibit Objects

Two new Modbus objects have been added to support bit mapping of individual bit values in a
Modbus 16-bit register to digital type objects in Building operation. Each object will provide 16 digital
values that can be bound directly to other digital values. The new objects are called “Modbus Multibit
Input Point” and “Modbus Mutlibit Output Point”. The advantage of these new objects is that you only
need only one object to provide 16 digital values from the Modbus device.
3.16 LON enhancements

3.16.1 Upload XIF from device
Engineers can now configure online 3rd party LON devices without having access to the XIF file.
It is now possible to retrieve and upload an XIF file from a discovered LON device. The uploaded
XIF file can then be LonWorks imported to SBO just like XIF files retrieved from the vendor.
3.16.2 Support for LON configuration parameters using FTP

SBO now supports LON device types that use file transfer (FTP) to upload and download
configuration parameters.
3.17 EWS enhancements

3.17.1 Web Services domain login
EWS now supports logging in to domains other than the default domain. If a certain domain is to be
used to logged in to, other than the default domain, it is prepended to the login name
<domain>/<username>. In a multiserver environment (example AS under an ES) where the default
domain of the AS is created on the ES and the login is performed on the AS, the domain name must
be prepended to the username. If the default domain is on the AS the domain name does not have
to be prepended.
3.18 Andover Continuum Transition

3.18.1 Andover Continuum Conversion Program
The Andover Continuum Conversion Program has been updated to allow for the input of files either
from b3 devices or Infinet devices. The input file can be all of one type or a mixture of b3 and Infinet.
As part of the target designation it is necessary to identify the appropriate field bus.
3.18.2 Support for Infinet

A SmartX Controller – AS-P running version 1.9.1 or higher will support the creation of an Infinet
Interface under which it will be possible to learn in a network of Andover Continuum Infinet devices
or create new devices.
Schneider Electric

3.19 Satchwell Sigma Transition

In order to obtain the new Sigma features it is necessary to install the latest Sigma Transition
Component on the Sigma Server. See section 6.15 for more information.
3.19.1 New Sigma TGML Schedules

Sigma graphical schedule editors have been replaced by TGML schedule editors. The new schedule
editors will work in both WorkStation and WebStation. The time schedule editor supports drag
functionality which was missing from the current time schedule editor.
During upgrade to v1.9 the current graphical schedule editors will be removed and a Data
Import must be performed to get the new TGML schedule editors.
3.19.2 Sigma Short Form Edit support for Alarms

Sigma Short Form Edit (SFE) is now provided for alarm objects which allows graphical editing of
Sigma alarm objects. The Sigma alarm objects that are supported are as follows
 Digital Alarm
 Low Limit Alarm
 High Limit Alarm
 Window Alarm
 Cross Reference Alarm
To make these short form edit alarm editors available, enable SFE alarms in the Sigma Interface
object and then carry out a Data Import. The SFE editor will be added to the Sigma alarm objects.
3.19.3 Sigma Commands for Controller Warm & Cold Start

It is now possible to execute a controller warm start and cold start from WorkStation. These
commands can be executed from the context menu on the controller object or by first selecting the
controller object and executing the command from the Actions menu.
3.19.4 Sigma Action Schedules

Sigma Action Schedules have been added in the v1.9 release for retiming controllers and retrieving
Log Sets from controllers. These new action schedules are created under a new folder called Action
Schedules.
3.19.4.1 Controller Retime

The controller retime action schedule objects will retime controllers to the time in the Enterprise
Server at the time and days specified in the Controller Retime object. It is possible to specify a range
of controllers to retime and the days and time of day to execute the controller retime.
3.19.4.2 Log Set Retrieval

The log set retrieval action schedule objects will retrieve log set logs from controllers at the time and
days specified in the Log Set Retrieval object. It is possible to specify a number of log sets to
retrieve from controllers and the days and time of day to execute the log set retrieval.
3.19.5 Sigma Mnemonic available in Alarm Viewer

The Sigma mnemonic is now available in the WorkStation alarm viewer. To include the Sigma
mnemonic in the WorkStation alarm viewer, select the “Message Text” property. Note that this
property is shared with TAC I/NET.
Schneider Electric

3.19.6 Sigma Long Texts

When enabled Sigma Long Texts are now automatically created as alarm attachments in the
Enterprise Server. To allow the Sigma Long Texts to be created in Enterprise Server, enable Long
Texts in the Sigma Interface object and carry out a Data Import.
3.19.7 Sigma Log Set Description in System Tree

The Sigma Log Set Description is now automatically included in the Log Set object name. This will
improve the user experience.
3.19.8 Sigma Log Set Wizard

There is a new wizard in this release to create Sigma Log Sets in WorkStation. The wizard can be
used to create empty Sigma log sets or create Sigma log sets with log objects using object
multiselect. This wizard will reduce the time it takes to create Sigma log sets in WorkStation.
3.19.9 Sigma Log Set Objects

Sigma log sets created in WorkStation now have a writable property for “Log set number.” This
property is writable so that the user can modify the log set number. Imported Sigma log sets still
have this property read-only as the log set number cannot be changed in the Enterprise Server.
During upgrade to v1.9 user defined log set objects will be identified and converted so that the log
set number is writable. To enable the upgrade to identify user defined log sets the description
property must be empty otherwise the log set objects will be identified as imported Sigma log sets.
3.19.10 Import of Sigma Historical Logs

It is now possible to import Sigma historical logs from the archive files on the Sigma Server. The
historical logs are imported to a new folder called Log Set Archives under the Log Sets folder. The
user can configure the number of archives files to import, the number of samples per log, and
optionally specify the Sigma Server to import the archive files from. To import the Sigma archive files
into the Enterprise Server, run the Data Importer from the Log Set Archives Folder. This will
reconstruct the Sigma archived data in the Enterprise Server as Sigma log sets with manual trend
log objects.
3.19.11 Support of Sigma Log Objects from TGML

Sigma log objects will be recognized by WorkStation and WebStation in this release so that from
TGML graphics that have Sigma values, the user can navigate to the associated Sigma log objects.
3.19.12 Support of Notification Reports for Sigma Logs

In this release, it is possible to trigger a Notification Report from a Log Set retrieval. This means that
the user can configure a schedule to retrieve Sigma log set controller logs which will then trigger a
notification report when the log retrieval is complete.
3.19.13 Simplified Engineering of Sigma Globals

In this release, the engineering of Sigma globals being brought from the Sigma network into the
Enterprise Server has been simplified to make it easier to understand and engineer. The user no
longer has to create Sigma Global Output objects for each global value that needs to be made
available to Building Operation objects in the Enterprise Server. Instead each Sigma object has a
new property group called “Sigma Globals” that has properties for the Primary and Secondary value.
To engineer a Sigma global value the user simply creates a binding from one of the new global value
Schneider Electric

properties to another Building Operation object value. This binding will register a global value on the
Sigma controller object for this value.
For users who have already created Sigma Global Output objects, the upgrade to v1.9 will move any
bindings from these objects to the new Sigma objects global values properties and delete the
redundant objects in the Enterprise Server.
3.19.14 Support for Sigma Link Addressing

Support for Sigma Link Addressing is provided so that Sigma global messages can be received and
transmitted on the Enterprise Server from Sigma controllers that are on different subnets. To use this
new feature simply enable Link Addressing in the Building Operation Sigma Interface object and
engineer the link addressing from Sigma engineering client.
3.19.15 Sigma RUDs and Globals Monitoring

In this release, the number of Sigma controller RUDs and Globals that exist in the Sigma system is
monitored. Only the Sigma controllers that have been transitioned to the Enterprise Server can be
monitored. Two new configuration properties are provided in the Sigma Interface object to define the
maximum number of Sigma RUDs and Globals that should be allowed before a system alarm is
triggered. The default number of RUDs and Globals is set to 5000. This is only a soft limit, however
exceeding these default limits is not supported nor recommended. The following system alarms are
generated when limits are exceeded.
 Sigma RUDs exceeded the network limit

 Sigma RUDs exceeded the controller limit
 Sigma globals exceeded the network limit
The system alarms can be disabled by setting the configuration properties to “inhibit.”
3.19.16 Enhancement to Data Import of Sigma Log Sets

The Data Import of Sigma Log Sets has been enhanced in this release.
 When using the Data Importer to import Sigma log sets, the user will be prompted to
authorize download of these log sets to the controllers. This means that the user will no
longer need to manually download imported Sigma log sets to the Sigma controllers.
 When the user uses the Data Importer to import Sigma log sets and duplicate log sets are
found that have been created in the Enterprise Server, the user will be prompted to
authorize moving these log sets to new log sets and downloading all log sets to the Sigma
controllers. The Data Importer preserves all data by first uploading the controller logs before
moving the data to new log sets and downloading to the Sigma controllers. If the user does
not authorize this, the Sigma logs will not be imported and the user will need to manually do
this operation.
3.19.17 Sigma Database Alignment

Currently changes made in WorkStation to Sigma SFE properties in controllers are not aligned in the
Sigma Server. This means that if a controller cold starts, these changes are lost when the controller
data is restored from the Sigma Server. There is a new controller firmware upgrade that is available
that will enable database alignment to the Sigma Server. Once the firmware is upgraded changes
made in WorkStation to Sigma SFE properties in controllers will be aligned to the Sigma Server.
See latest Sigma controller firmware release notes for more detailed information.
Schneider Electric

3.19.18 Alternative Sigma Navigation View

In this release, it is possible for Sigma users to use the new Panel Navigation Pane type to provide
an alternative navigation view. The alternative navigation view can allow users to show the Sigma
tree the same as the Sigma Client. To facilitate this the Data Importer will create an import file that
can be used to create the navigation object for Sigma. The Sigma Data Importer creates the Sigma
menu object import file on the Sigma Server at the following location
“\Sigma\Data\XMLExport\SegmentMenu.xml”. The user can either import this file directly or copy the
file to another computer and import it from there. The file should be imported from the Menu folder
under the Sigma Interface object.
For more information on the Panel Navigation Pane type see section 3.5.3.
3.19.19 Automatic Configuration of Sigma Controller Communication Timers
In this release the need to set the Sigma UNC Controller Communication timers individually to
control / stagger UNC controller subscription refresh is no longer necessary, instead the Enterprise
Server determines the optimum refresh period based on the number of objects and UNC’s
requested.
However please note that this change does not do away with the need to ‘tune’ the Sigma object
tolerance setting to keep the subscription updates to a minimum.
The system alarm generated by the Enterprise Server when exceeding the recommended number of
concurrent subscriptions on the Sigma network is set at 5000, however, it is acceptable to exceed
this limit providing a deterioration in system performance is not apparent, i.e. slow graphic updates,
delayed alarms etc.
The subscription statistics can be monitored on the Enterprise Server for individual Sigma controllers
and the Enterprise Server by selecting the Network Communication Statistics and the Subscriptions
tab under the Diagnostics folder.
From there the number of subscriptions, current update frequency and peak values can be
monitored to determine which controllers are updating to frequently. These can also be dropped into
the Watch Window for dynamic updates.
Remember the statistics can also be zeroed by selecting the Reset statistics menu item when the
Network Communication Statistics is selected in the system tree for individual controllers and the
Enterprise Server.
3.20 TAC I/A Series – Native MNB Support and Transition

3.20.1 Operating system and Visio support
WorkPlace Tech Editor and Workplace Tech Monitor now support Windows 10, Visio 2013 (32 bit)
and Visio 2016 (32 bit). For more information, search for “System Upgrade Software Requirements”
in WebHelp. Installations with Visio 2007 (32 bit) will continue to work but are no longer officially
supported.
3.20.2 WorkPlace Tech Monitor for MNB devices

Users can now view MNB applications and perform write-to-RAM operations in WorkPlace Tech
Monitor. For more information, search for “WorkPlace Tech Monitor” in WebHelp.
3.20.3 Backup and restore MNB COV client object configurations

After using Link Builder in the WorkPlace Tech Commissioning Tool to configure COV client object
links in MNB devices, you can back up the configurations into the Building Operation server
database. If you need to replace a controller, you can restore the MNB COV client object
configurations without having to use the commissioning tool. It is also possible to manually configure
Schneider Electric

MNB COV client objects in WorkStation. For more information, search for “MNB COV Client Data” in
WebHelp.
3.20.4 Backup and restore MNB VAV flow balance configurations

After using the MNB Flow Balance tool to balance MNB VAV controllers, you can back up the flow
balance configurations into the Building Operation server database. If you need to replace a
controller, you can restore the flow balance data without having to use the flow balance tool. For
more information, search for “MNB Flow Balance Calibration Data” in WebHelp.
3.20.5 Monitor and write-to-RAM in WorkPlace Tech Editor

Users can now connect to I/A Series MNL and MNB controllers to monitor real-time values and
perform write-to-RAM operations in WorkPlace Tech Editor. This saves time by reducing the need
to switch between WorkPlace Tech Editor and WorkPlace Tech Monitor when developing and
troubleshooting I/A Series applications. For more information, search for “WorkPlace Tech Editor” in
WebHelp.
3.21 TAC I/NET Transition

3.21.1 Updated Icons
The icons for TAC I/NET points have been updated to better represent each point’s type and to
follow the style of the StruxureWare Building Operation interface.
3.21.2 Enhanced Performance of the USB-485-INET

When you create an I/NET Interface on an automation server (AS/AS-P), a new property named
Token Extend Time is now available. Using this property, you can enter the amount of extended
time (if any) you will allow the USB-485-INET device to initiate communications on the controller
LAN before releasing the network token. Extending the token time can provide noticeably better
performance of DCU uploads and point polling through the USB-485-INET device.
Be aware that other taps on the same controller LAN may exhibit reduced performance as you
increase the token extend time on the USB-485-INET device. For this reason, you may wish to leave
the Token Extend Time at its default setting of 0 (i.e., no token extend time) on hybrid systems
where the legacy I/NET software product is communicating on the same controller LAN as the USB-
485-INET device.
The Token Extend Time function requires USB-485-INET firmware revision 1.01 (06/22/2016). With
firmware prior to revision 1.01, the setting of the Token Extend Time property is ignored.
3.21.3 Additional DCU Properties

This version of StruxureWare Building Operation includes support for the following additional DCU
properties:
 Sunrise/Sunset
 Special Days
 Daylight Saving
3.21.4 Time Scheduling Point Extension
StruxureWare Building Operation now provides support for the Time Schedule (TS) point extension
on DC and DO points. Independent, master, and slave time schedules can be added, deleted, and
modified directly within StruxureWare Building Operation.
Schneider Electric

3.22 TAC Vista – Native Xenta Support and Transition

3.22.1 Support for Xenta 122 as a built-in device
Two new device types, Xenta 122FC and Xenta 122HP, are added to the LonWorks Network built-in
device list.
(Xenta 122 availability will be announced separately.)
3.22.2 Xenta Group editor

A new Xenta Group editor offers the SBO engineer a more user-friendly way to administrate Xenta
Groups. Xenta Group assignment is independent of folder structure and device addressing.
The Xenta Group concept applies to Xenta 2xx/3xx/4xx device series.
3.22.3 Enhanced support for ‘TAC Vista to SBO transition tool’

The Vista to SBO Conversion Tool supports transfer of LON network configurations from Vista to
SmartStruxure, including LNS networks. LNS will stay in such installations and will continue to be the
tool for managing the network, such as assigning network addresses and create LON bindings.
The main objective is to be able to move the LNS network into SmartStruxure and to be able to
continue to maintain the network. Maintenance includes being able to modify Menta applications and
replace broken devices. Expanding the system shall be done by means of SmartStruxure with use of
LNS, even though it will be possible to add single controllers.
In order to be able to maintain such sites some features have been added to SBO v1.9.1:
 Possibility to make a download without commissioning. Used e.g. when a Menta application
in a Xenta controller is modified
 Manual setting of subnet/node on LON devices
 Manual setting of subnet/node in AS
 Protection of network managed by LNS, so that not allowed actions, such as creation of
LON bindings, cannot be done in SBO
Detailed information will follow with the release of Vista to SmartStruxure SBO Tool for SBO v1.9.
3.22.4 Xenta 400 I/O modules
In order to be able to transition Xenta 700 sites to SmartStruxure, the Vista to SBO Conversion Tool
converts the majority of Xenta 700 content to AS-P. One function currently missing in AS-P is the
ability to access the Xenta 400 I/O modules used by Xenta 700. The development is ongoing and
will be released soon after the v1.9.1 release. There will also be a new version of the Vista to SBO
Conversion Tool.
In v1.9.1 it is possible to add Xenta 400 I/O modules, but be aware they cannot be used. The
program code needed to communicate with them is under development. The reason it is possible to
create devices in v1.9.1 is only to allow for a smooth upgrade once the function is available.
Schneider Electric

4. Defects Fixed in StruxureWare Building Operation

v1.9.1 Release
Defect ID Functionality Description PSS Ticket ID
27264 Account Users with no access to the system folder may 15126649
Management still see and download backups from it
Logging on to WorkStation as another Windows
Account
27490 User using HTTP issue error: Wrong User name 16570694
Management
or password
Not possible to mass create alarms for inputs
30217 Alarms 24511170
with different units.
A Variable Status Alarm goes into alarm and
30522 Alarms 99
clears after a warm start
Value in alarm window shows variable status
30891 Alarms instead of variable value when substitution code 26364871
is used
Default WorkStation Alarm View does not display
user changes made to the 'Sort order' until a
31025 Alarms 99
change to the sort order setting is made after
shutting down the WorkStation
SNMP Trap messages coming out of the AS or
31699 Alarms ES are supposed to be V3 but are showing in the 27871577
info field as a V2
Notification filter for Previous alarm state not
31823 Alarms functioning when previous alarm state should 29620871
ignore disabled alarms
Can't set SNMP password for AS through Device
Administrator -
31875 Alarms 00
'system.service.snmp.user.authPassword' could
not be found
Multistate Alarm string not showing in email
31913 Alarms 30562447
notification it displays an integer
Blinking alarms in alarm pane when connecting
32102 Alarms 30813382
to an AS-B using HTTP
32557 Alarms Problem in Alarm view sorting. 32374183
Entries missing in notification editor substitution
32694 Alarms 32968069
code list
"View History" on an alarm show all events for a
32727 Alarms user without write access to System/Events
folder
Alarm email contains incorrect alarm message
33037 Alarms and value when the return to normal email is 32330220
sent.
Enterprise Server does not start up correctly
34645060,
33357 Alarms when certain alarm triggered notifications are
35299674
used
32129 AS-B AS-B Power fail hangs the unit 99
AS-B display never turns off - power consumption
32506 AS-B 00
- life time of the display
Schneider Electric


"Communication Certificates" dialogue in Security
32507 AS-B 32388436
settings is greyed out in a AS-BL.
AS-P Ethernet switch seems to cause offline of 28950253,
32147 AS-P
AS-P to the ES due to operation of EEE. 32993553
Unable to create a Floating Limit BACnet Alarm
30516 b3 in a b3 controller, the Setpoint Reference cannot 25538469
be entered and saved.
Can't reset b3 flash circuit breaker from within
31410 b3 31599379
Script Program.
29451 Backup / Restore Files left in db folder after restore 00
Not possible to apply Lead object to AS Default
30926 Backup / Restore 26353042
backup rule
When special characters are used in the
31624 Backup / restore Automation Server name the backup functionality 28956306
in the ES don't work as expected.
Unable to use "Get Backup set from device" on
31886 multiple AS's because all backup sets have the 30336739
Backup / Restore
same name db_backup.xbk. Note it works when
doing one at a time
Editing BACnet schedule incorrect event
26652 BACnet 243287
recorded
Importing a v1.6 calendar object into v1.7 results
29590 BACnet 22505770
in incorrect dates and names in date list
Schedule Exceptions are overriding schedules
30194 BACnet 24612389
when they are not supposed to
Monitoring a CIO point with an ETlog fills the
30866 BACnet 25754105
trace log with errors
Not possible to apply Lead object to AS Default
30926 BACnet 26353042
backup rule
Unable to upload VT7600-1000B rev2.3.03 and
31605 BACnet 28811011
VT76000B5X00B
31747 BACnet BACnet crash while updating BroadcastAddress 98
ES Crashed while inserting a polled BACnet
31748 BACnet 98
variable
Automation Server will not start after a power
31942 BACnet cycle or coldstart in revision 1.7.2 but it reboots 26176919
and starts okay in revision 1.6
Enterprise Server Upgrade - ES will not start
32269 BACnet 31778674
correctly after upgrade from v1.7.1 to v1.8.1
The AS trace log is spammed with BACnet error
32283 BACnet 123456
0x80030000 since upgrading to v1.7.2
32290 BACnet Memory leak in BACnet plug-in 123456
Who-Is message not observed after a
WriteProperty request goes unanswered, causes
32525 BACnet 32547106
3'rd-party device to remain offline in SBO
WorkStation
Building Operation Tech Tool, IOS - Editing a
30841 BOTT time schedule via the Tech Tool does not allow 00
you to select if a period is on/off
Schneider Electric


EWS objects are not displayed when using the
31331 BOTT 27442226
Technician Tool on an IOS or Android device
29645977,2951
31527 BOTT SBO Tech Tool will not show graphics
6459,29592787
32736 BOTT Some graphics are not displayed in BOTT app
29474751,
Online detection is done to all servers, even if
32044 Communication 30717333,
nothing needs to be communicated
31243738
33036 Crash Enterprise Server crash at version 1.8.1.7000 33888889
BDC-2016-013 - BOTT Unauthorized Disclosure
31666 Cyber Security 27740011
of Information
Device Device Administrator takes 70 minutes to
31486
Administrator upgrade on some computers
Gets recurring alarm "Email Service configuration
31778 Email 29367868
error" in SBO WorkStation on an AS
Automation Server - from v1.5 you can no longer 246036 and
27001 Engineering download the serial port logs from the
243737
Automation Server
Changing the folder name causes an error in the
30436 Engineering 25097027
"Source" address
Unclear error message when fetching trace or
system log through WorkStation fails
Cant rename the AS, "Validation failed for
31509 Engineering property 'PrimaryPassword'. Path: 27813647
'/AS051/PrimaryPassword'. Type 'Password'
31529 Engineering ES Crashing on regular basis creating DMP files 28507485
31587 Commission with upload does not give values in 00
Engineering
device
31597 User is able to save a Report object in the alarm 28217654
Engineering
styles folder
Server Communication has been hidden in the
system tree in v1.8.1
Locked binding path when folder name start with
system
Choosing to clone an AS from a backup set
31721 containing BACnet interface, restores device 99
Engineering
from chosen backup set instead of restore it to its
previous state
When an attempt is made to bind a point that is
31780 Engineering already bound, the option to keep the existing 29663347
binding does not work as expected
Binding template matches the correct path but
binds to the wrong path
The Enterpriser Server does not show the same
values as the Automation Server
32463 Engineering Problem in the binding view in SBO version 1.8.1 32169893
WS crashed after selecting Favorite Content
32703 Engineering
Type
Binding between two child servers unresolved
32982 Engineering
after upgrade
Schneider Electric

31586 AS or ES continually crash if an EWS interface is 28780425

EWS
to Power SCADA Expert 8.1.
ES Crashed/restarted due to "Max number of
33015 EWS 98
sessions reached"
33125 EWS EWS Alarms not honoring millisecond values 34537713
FBP: AS crashes when adding a binary
Function Block
26212 output/input with the same name as an existing 236112
Programs
public block
Function Block DELR/DELI do not function correctly when input
31512 28049650
Programs is connected to a DELR/DELI
31657 Function Block 28983582
Tam32 error during Function Block generate
Programs
Duplicate GUID's in X700 Menta results in failure
Function Block
32407 to import MTA file - Number of blocks don't match 32116207
Programs
in Function Block Program
Function Block AS-P gets stuck in a reboot loop caused by alarm
32695 32929776
Programs flooding (BACnet - Function Block - Alarms)
Function Block FB editor stops working when editing specific
33062 34151559
Programs programs after upgrading to 1.9
Not possible to view or create Trendlog from
29997 Graphics 23848812
floating TGML window
Graphics does not show in WebStation if server
31006 Graphics 26578321
name has a hash tag (#)
Graphics Editor crashes when resizing the work
31014 Graphics area in preview using the responsive graphics 26883759
feature
31042 Non-conformity in the implementation of 26919625
Graphics
setTimeout in graphics
31100 Graphics Issue on changing sweepangle of pie object 27100571
Links in a graphic are not highlighted when
31506 Graphics 28482293
moving the mouse between the links
Responsive graphics does not resize correctly in
31530 Graphics 28627261
WorkStation and WebStation
Force value box accessible after DisableLeftClick
31783 Graphics 29376550
script is added to DynamicText point in Graphic
CDATA file not copied when copy paste between
31930 Graphics 99
servers in v1.8.1 - Graphics will be empty
Graphic editor - Crash when editing a tgml object
32138 Graphics 30510646
in a graphic
Graphic menu objects take a long time to open in
32523 Graphics 32289914
WebStation
WPT Monitor: Constants connected to custom
27045 I/A Transition
object inputs do not work with Write-to-RAM
Grouping by some columns in Work Tech Place
Editor list crashes WorkStation
Internal server error after releasing a forced value
31904 I/A Transition 30496138
(BVSPP) in MNB controller
Hot Fix Installer does not work - Work Place Tech
Crashes
Schneider Electric


Requested operation is presently disabled error
when attempting to import an IA Series MNB-V2
application into the AS-P with WorkPlace Tech
Editor
MNB retained-configuration-values not working
on application download
SBO BACnet - graphics values are not being
shown correctly
Launch WorkPlace Tech Monitor option no longer
32527 I/A Transition available for MNL controllers if Write to ram 32126841
command permission is set to deny
WorkPlace Tech Editor fails to operate on Server 31384576,
2012 with latest updates 32610834
The "Global" Property of an Indirect I/NET point
30058 I/NET Transition 24073418
always shows as unresolved
Any SmartStruxure server hosting TAC I/NET
30880 I/NET Transition crashes when the server clocks changed
(advanced 1 hour) for Daylight Savings Time
31391 I/NET Transition ES Crashed in I/NET 98
30451177,
31909 I/NET Transition I/NET command error alarm cannot be cleared
32299845
Unable to acknowledge I/NET command error
32150 I/NET Transition 31450825
alarms in SBO
Frequently removing and restoring
30554 Infinet Transition communication for i2 devices causes the AS-P to
restart and require a DFU
Imported Infinet Alarms do not evaluate if its
31861 Infinet Transition foreign address is the same as an Infinet alarm
already present.
i2 script programs with input bindings to Infinity
32239 Infinet Transition Server Values in Infinet Interface Value become
disabled after download
You cannot bind i2 inputs to properties of the i2
32431 Infinet Transition
script program (example: current line and state)
i1 devices: Infinet objects are not given unique
32777 Infinet Transition infinity names if you copy/paste or import the
same object with a name > 16 characters
Infinet Device to Infinet Device Communication
does not work with Infinet date time values.
i2 script programs with input bindings to i2 values
32862 Infinet Transition in different i2 device become disabled after
download.
Infinet device to Infinet device communication
does not work after an AS-P restart
Infinet schedules are not included in the Not
32973 Infinet Transition Converted count in the Continuum Conversion
tool.
Schneider Electric


Infinet IE stops working if you delete the Infinet
32979 Infinet transition
network and recreate it.
In the Continuum to SBO conversion tool, if there
32992 Infinet Transition are any quotes in string properties of an object,
none of the properties of that object will get set
AS-P LON led is always active when no LON
31866 Installation 30054059
network exist
Incorrect handling of Russian characters in
31984 Localization 30864882
path/naming
32864 Localization Danish time format in WebStation is incorrect 33539082
Inconsistent presentation of a NVO SNVT value if
21668 LON comparing watch pane and properties in
Workstation
Issue with externally managed LonWorks
26828 LON Interface when a function block starts with a 245286
number.
Lon communication hangs after upgrade of AS to 24343593,
30128 LON
version 1.7.1 28799276
30961 LON After deleting network variables in Local node AS 26559961
crashed
ES crashed when subscribing to variables of a
31800 LON 31226545
ProgressObject
WorkStation - Dialog error when copying LON
31900 LON 30517901
device
Incorrect calculated value shown for SNVT after
32299 LON 31328784
upgrade to v1.8.1
Unable to load Stibil resource files after
32323 LON upgrading to v1.7.2/1.8.1 where negative values 654321
exist
32363 LON Xif import issue 31546487
Not possible to change value on a configuration
32427 LON parameter for a LON warema device added in 31900106
v1.8.1.
Migrate a Lon device with only one domain table
32878 LON from Vista will cause error in database(?) and 33467216
export files (XML)
Trane SCOPE4 DRF kit import failure (Commit:
32881 LON public.lon2.types.80002a5500000000.enumeratio 33249129
ns.cooling_source_t)
After upgrading from 1.7.1 to 1.8.1 some LON
33094 LON 33505636
devices are missing.
Applying HF 1.8.1.7607 causes new problems
33099 LON (automatic backups stop, navigation to Lon 33663075
devices locks workstation)
Removing a binding from LON value causes WS
33313 LON 34900740,98
to hang.
nciCfg1FcuZn UNVT from SE7XXX series not
33705 LON 37553310
represented correctly (UNVT_cfg_1_fcu_zn)
Schneider Electric

23134 Menta Editor generate failure not caught by 201791

Menta
SmartStruxure
MicroNet AS fails to start due to MicroNet plugin contract
31437 28043458
Transition violation
MicroNet MicroNet VisiSat import file replace all non-ASCII
31467 28043458
Transition chars with replacement char
MicroNet Certain period values in a Micronet schedule will
33081
Transition crash the Workstation
Writing Modbus points take long time when Serial
30111 Modbus
and TCP networks configured in the same AS-P
2 crashes that are related to Deleting Modbus
31540 Modbus 28667877
object in a changeset
AS-P Crash - to Modbus, crashing while trying to
31647 Modbus get a DeviceObjectHandle when adding a 28950253
pollpoint to a group
Modbus TCP communications issue - no data is
31722 Modbus 28864158
returned
"Illegal Data Value" returned by SBO Modbus
31844 Modbus 00
TCP Server interface
FC 2b is not disabled when you disable the poll
31915 Modbus 30203983
request
32430 Modbus DLR-IAD38 S206 DCIM01 Modbus crash 32106187
Modbus points are loaded in runtime database
32705 Modbus 19554581
(RtDb) with the value 0 and set as valid
Modbus TCP device does not come back online
33341 Modbus 34104932
to AS-P after device power is interrupted
33341 Modbus TCP device does not come back online 34104932
Modbus
to AS-P after device power is interrupted
Deleting Modbus write points that have
33379 Modbus
subscriptions crashes the server
ES Crash (service stopped) during engineering of 35799013
33536 Modbus
a MODBUS TCP interface on the ES
Issue with new Notification Object, duplicate
31557 Notification 28721821
entries into the text file
Alarm Triggered Notification - Deleting the entry
32151 Notification from the "To Users and Groups" field causes the 31466431
WorkStation to crash
Network 8000 Event Record references the
NW8000
30474 wrong system event ID when a PSI joins the ASD 25483913
Transition
network
NW8000 AS-P is unable to communicate with ASD
31023 26347649
Transition network
NW8000 NW8k RnetAv object status is OFF when it
31794 99
Transition should be ON
NW8000 Network 8000 OSS block fails to properly
33246 34829537
Transition calculate table values during optimum start
31845 PCS PCS will not deploy to a AS-P 29718023
Schneider Electric

31686 ES Performance Issue / Crashes after upgrade 28858732

Performance
from v1.7.1.89 to v1.8.1.89
ES performance slow / hanging at times. Had 45
31843 Performance 29232473
warms starts in last year
31890 Performance Constant ES crash at v1.8.1.2103 30452979
Report server is not saving trend log data for all
29429 Reports
ET logs
User name with German characters does not
31325 Reports 27786802
work for WebReports login
No longer possible to use a custom Microsoft 29690641,
31792 Reports Reporting Services port (different from 80) in
29847594
version 1.8.1
Trend Log data not transferring to reports server
32028 Reports (Arithmetic overflow error converting expression 30673558
to data type bigint.)
Web Reports - Upgrading the Report Server from
32218 Reports v1.6.1 to v1.7.1 - Custom reports no longer 30844734
accept the inputting of the a name in a text field
After upgrading to v1.8.1 it is no longer possible
32266 Reports to use a non-English Operating System and a 99
non-English SQL server for Reports
It is not possible to use a combination of a non-
32268 Reports English OS and an English SQL server for 99
Reports
WebReports data transfer stops due to SQL table
32798 Reports column size (UpdateEvent 33021487
System.InvalidOperationException)
Error when running the Calendar consumption
32829 Reports 32823952
report in Web reports.
Importing a v1.6 calendar object into v1.7 results
29590 Schedules 22505770
in incorrect dates and names in date list
Schedule Exceptions are overriding schedules
30194 Schedules 24612389
when they are not supposed to
Renaming an i2 or b3 script causes SBO
30683 Script
bindings to become empty
Saving script program gets its unit reset to
30827 Script Programs 26011416
NoUnit intermittently
Workstation crashes when trying to open a folder
31286 Script Programs 27665608
with Script programs
Import from Plain English is broken in v1.8 - it
31329 Script Programs shows all objects as not found when convert is
attempted
31591 Script editor locks up while editing 2 programs in 28670174
Script Programs
b3 device
SBO After v1.7.1 upgrade. Search for forced
29828 Search 23370472
BACnet points does not appear to complete
Schneider Electric


Creating Search for Disabled Script Programs
31556 Search does not work. Cannot select "State Is Equal To 28601081
Disabled"
Search's result is misleading since it doesn’t warn
31841 Search 29837508
user about offline servers
Workstation hang after doing a search for alarms
33376 Search 35499212
in an AS from the ES
When an SPA object is of type Fixed and viewed
31018 Sigma Transition in the property grid and value displayed is below 99
10 it shows in red
Source C:\Sigma\Data\Graphics\Drawings
31161 Sigma Transition 99
displayed when using data import
Sigma: System & Trace log is spammed with
"UNC532K/0077 - Optimiser/CheckListRequired"
Graphics containing digital output points are
31655 Sigma Transition incorrectly bound when transitioned to SBO 99
(Sigma)
ES crashes during shutdown - related to Sigma
and trend log plugin - inhibits database upgrade
ES performance slow / hanging at times. Had 45
warms starts in last year
Sigma Contingency logging when displayed in
31952 Sigma Transition SBO, is +1Hr in advance of the computer time or 30746824
the Sigma server
After upgrade from 1.7 to later version, it is not
32314 Sigma Transition
possible to delete Sigma objects via Data Import
It’s not possible to write to a Sigma object when
bound to another SBO object (SFE properties)
Graphic elements that do not have an alarm
configured in Sigma, flash in SBO
Timeschedules that pass through Sunday
midnight - Day 7 to Day 1
IAC timeschedule not updated when changed in 33577206,3335
WebStation 8939
IAC timeschedule when highlighted leads to
WorkStation fail
Sigma Transition - Retiming Sigma V53 hardware 35030175
33337 Sigma Transition controllers from SBO, causes the Weekday
setting to be a day behind
Retiming Sigma V53 hardware controllers from
33337 Sigma Transition SBO, causes the Weekday setting to be a day 35030175
behind.
33377 Sigma Transition ES crash in trend log code during shutdown 34804947
Restarting an ES while logset data is arriving can
cause the ES to crash
Sigma: the Controller Communications Timers 34804947
33491 Sigma Transition settings in SBO are fixed at the default value and
do not reflect what is set in native Sigma
31357 The unit is lost when copy/paste a Modbus point 27853163
Spreadsheet
in Spreadsheet view
Schneider Electric

31674 Unable to copy & Paste entire row of 29216163

Spreadsheet
spreadsheet in IO
The unit is not pasted from Excel when pasting
32072 Spreadsheet 31035456
Modbus points to SBO "Edit in Spreadsheet"
Printing of Trend or Extended Trend charts cuts
30783 Trends 25897096
off some of the point names
Monitoring a CIO point with an ETlog fills the
30866 Trends 25754105
trace log with errors
100ms Interval trend logs make CPU usage three
31274 Trends 99
times higher or more
A variable triggered trendlog doesn't log the value
31687 Trends 28939170
when the trigger variable is set to true
31857 Implicit logs do not display correct units in 29519567
Trends
WebStation or multi-trend log list
Trend chart trend log bindings are saved
32085 Trends incorrectly if the trend log name contains a 31049306
comma
Trend Log list not handling "Meter Consumption"
32825 Trends 00
calculation properly for extended trend logs
Wrong value plotted in trend log list when
32867 Trends 32306537
calculation is set to delta on a meter trend log
32985 Trends incorrectly if the trend log name contains a 31049306
comma
LON communication hangs after upgrade of AS 24343593,
31028 Upgrade
to version v1.7.1 28799276
28858732,
31590 Upgrade ES Upgrade failure v1.7.1.89 to v1.8.1.79
28804274
SMTP server port(s) are changed from 25 to 587
31607 Upgrade 28909253
following an upgrade
Invalid binding for the Administrators group after
31689 Upgrade 28919302
upgrading from v1.7.1 to v1.8.1
Device administrator requires PC Administrator
31819 Upgrade rights to run, even when run on a PC that does 123456
not have an ES installed.
31839 WorkStation crashes while browsing tree 29953848
Upgrade
structure after upgrade
Error after upgrading to v1.8.1-
31853 Upgrade 30095634
SaxParser.cpp(305)
Some graphics are empty after upgrade and
32353 Upgrade 123456
export/import from v1.5 to v1.9
ES database (v1.7.1.89) fails to upgrade to
32500 Upgrade 31931055
1v.7.2.24
Automation Server CIO Counter Input Value
32522 Upgrade increases (jumps) during an upgrade from v1.7 to 32348482
v1.8
AS Upgrade failure: ERROR: MAP file is
32576 Upgrade 32521176
required for upgrading [v1.7.2.8103 to v1.8.1]
Schneider Electric


Upgrade of AS between version 1.7.1 and 1.8.1
32614 Upgrade 32443464
fails.
Upgrade fails from 1.7.2 to 1.8.1 - LonWorks map
32804 Upgrade 33249129
file missing (pre-upgrade)
AS will not start up after upgrade from 1.7.2 to 34132674,
33057 Upgrade
v1.8.1 33008903
The Right-Click Menu in the System Tree Doesn't
24075 User Experience 207014; 213205
work when the System Tree is floating
Most options blocked when trying to use the right
25651 User Experience 237636
click menu in a floating work area window
SBO Workstation crashes clicking on Account
32740 User Management 33106084
Group
Double clicking column headers in Domain
32863 User Management Members makes server move from one list to
another
User added columns need to be re-configured to
27529 Views
change language
31181 SBO EWS Client Sends Invalid Alarm Polling 29711050
Web Services
Requests
Multiple Panels in WebStation representation not
30788 WebStation 24465818
the same as WorkStation
WebStation - TGML/HTML5 – Can’t view trend
from a point in a Xenta FBP
Horizontal bar in Graphics works fine in WS but
disappears in WebStation
WebStation - Unable to reach ES when using
certificate that i using DNS name instead of IP
Links in a graphic are not highlighted when
moving the mouse between the links
28977197,
29169776,
WebStation link not working - Uncaught 29305667,
31612 WebStation TypeError: Cannot read property 29306841,
'ERROR_LOGGED_OUT' of null 29309804,
29331790,
29409671
When using the “Redirect web clients to https”
Security Configuration option in a standard IT
configuration including a router and NAT, the
31697 WebStation 99
nsp_server redirect code uses the local IP
address of the AS/ES rather that the external
router address
31760 WebStation Links not working in WebStation 29524702
Enterprise Server crashes when ETL (Power
Manager Extraction tool) tries to load sources
31991 WebStation Link to PDF doesn't work in Panel 30924657
WebStation retains the last logged on location in
the Work Area Window for any user
Schneider Electric


WebStation retains the last logged on location in
the Work Area Window for any user
WEB Trend Charts, it is not possible to open the
32041 WebStation Series selections box for series assign to right 31002043
axis
WEB Trend Charts, it is not possible to open the
32041 WebStation Series selections box for series assign to right 31002043
axis
32085 WebStation incorrectly if the trend log name contains a 31049306
comma
Animations (scale and skew) locking up Internet
Explorer - other browsers are fine
Animations (scale and skew) locking up Internet
Explorer - other browsers are fine
WebStation Graphic not loading all details of floor
plan version 1.8.1
When a trend chart is displayed on a WebStation, 32306537,
32784 WebStation the values displayed are over 1000 times larger
33739692
than the true value.
A Xenta Time Schedule in WebStation will not let
you enter a time between 6:00 PM and 11:59 PM
Trend chart display chart values on occasion
differ from those displayed via the WorkStation
When adding group to user in WebStation, it is
32923 WebStation not possible to scroll down the group list when 33673621
ten or more groups exist.
Graphic drop down menu does not display at
correct location in WebStation
Xenta 913 conversion to SmartStruxure does not
31831 Xenta 29774534
have any points in an AS-P
Xenta Central Time chart link is corrupted during
32098 Xenta 31247506
a v1.7.1 to v1.8.1 upgrade
The "Edit Xenta groups" menu option are shown
33043 Xenta 34151933
in the "LonWorks Network" => "New" menu
When open the new function "Edit Xenta groups"
33044 Xenta and adding a group Workstation will crash when 34151933
save
Xenta exception times schedule in WebStation
with Spanish language pack installed displays 1st
33157 Xenta Jan 2017 on Sunday and Monday, rest of month 34469754
is 1 day out, days 8th. 9th and 10th January also
missing
Could only download to a TAC Xenta device
33414 Xenta 34786122
once
Schneider Electric

5. Known Defects in StruxureWare Building Operation

v1.9.1 Release
The known defects are included in this release. Those marked with an * after the ID are new with
this release.
Defect ID Functionality Description Workaround/Solution

Log in to the AS and re-
enable the default admin
Account Unable to add server if default
26570 account. Add the AS to the
Management admin account is disabled
ES. Disable the default
admin account again.
Domain Local security groups are
Account
26931 not in the SBO list of Windows
Management
group names
21686 Archive schedule settings are not
Archiving Manually reset the settings.
transferred when upgrading.
Archiving - System alarm "IO error
when generating archive"
30773 Archiving Acknowledge alarm.
generated every time an archive is
created
Disable and enable the
Sometimes Ethernet 2 setting stays
setting again and it will get
29406 AS-P disabled on AS-P when set to
reset properly.
enabled in Dev Admin
Disabled b3 scripts become
31878 b3
enabled after a download
Firmware upgrade: Upgrade of the
32180 firmware is aborted leaving the b3 Increase time for auto log
b3
in an offline state when the out.
WorkStation times out
Adding columns: Error loading
* b3 items is displayed after adding
32281
columns under b3's application
folder after a copy merge
bValue column on b3 application
32381 * b3 folder does not display the value Select current line instead
for a program. However, watch of value.
window displays it correctly
Shared graphic does not work
32897 b3 Use copy and paste.
when merge b3 devices
View the state in the
b3 Programs show enabled in a list
property grid of the script
32909 b3 view when they are actually
editor or in the watch
disabled
window.
The path simply cannot be
The 'Back up sets' path is not
25694 Backup / Restore edited, even if looks like it
editable and should be grayed out
can.
Schneider Electric


Ignore the status flags and
trust the object overlay. A
Wrong value on Xenta Status flags
Xenta field device should
26374 Backup / Restore after a device is duplicated using
always be updated and
Restore from a backup set
commissioned when it is
assigned to a new serve.
Navigating away from backup rules
while it is being loaded will not
30633 Backup / restore
show the user any objects in other
views
Unsupported BACnet properties in After upgrade, download or
23780 BACnet a third party device appear in the upload the third party
GUI after upgrade device.
The IP and broadcast
addresses must be
BACnet IP and broadcast address changed manually from the
25044 BACnet do not change when the IP of the Basic tab of the IP Network
server changes beneath the BACnet
Interface of the Automation
Server.
Copy and paste of multistate Create separate new
25916 BACnet values or points will fail and crash objects rather than via
the WorkStation copy/paste.
Unable to 'backspace' to delete
Type in the new text before
30477 BACnet when editing a reference in a
deleting the original.
BACnet trend log
BTL 1.9 7.2.X5 Should get
31739 * BACnet response of property.value-out-of-
range
Drag some objects’ values
to the watch window and
33045 * BACnet Value transfer from SBO to a bCX
view the bindings. These
stopped working
items are enough to start it
again.
BOTT - Issues when using the
Problem is related to the
zooming in/out function on
29036 BOTT browser zooming instead of
graphics, also loss of clarity of the
the graphics viewer.
graphic
"Remember Me" does not
30085 BOTT remember the user name when Type in user name.
connecting to the AS via AD-Link
Technician Tool - If the server
Change the password via
31923 BOTT password expires, then the BOTT
SBO.
just continues to try to logon
Confusing visual indication of
32328 Cascading Menu selected item when editing a
cascading menu
If multiple users are accomplishing
imports at the same time, it is
9886 Engineering
possible for the event log to contain
erroneous data
Schneider Electric


When upgrading from v1.5 to v1.6,
trying to open the bindings view
Open the view when logged
27429 Engineering directly from an AS that has not yet
into the ES.
been upgraded, the WorkStation
crashes
Detaching child AS by logging on
27567 Engineering to the AS itself makes the detach Detach via ES.
server command in ES unavailable
Duplicate server name in content
* Engineering Redo the content type
33253 type reference after upgrade from
reference.
1.9.0RC
1. Dock event view first.
New date and time filter for the 2. Open the filter settings
32686 * Event View Event view is not working when the and set time in the filter
Event view is using auto hide dialog (instead of date &
time picker).
Multiple Filters: After user rename
* Filters Log off and log in again
28445 no additional favorite filter savings
after changing User Name.
persist after logoff
Importing a Xenta application Replace character '/' with a
Function Block
25457 containing character '/' in signal valid character before
Programs
names fails importing the application.
When Workplace Tech Editor Acknowledging the error
.12682 attempts to import an application will allow the user to
I/A Transition
into Visio 2003, it will issue a “Can’t continue successfully
open location” error message through the import.
Subscriptions (i.e. watch window,
View I/A Series I/O point
graphics, etc.) to I/A Series LON
Default configuration
17640 I/A Transition I/O point Default Configuration
property values in the
properties display the NULL icon
properties pane.
instead of their current values
Set the regional settings of
Unable to connect objects in the client machine to use
WorkPlace Tech Editor period as the decimal
separator.
Do not use legacy
WorkPlace Tech Tool to
download an MNB device
No error message displayed when at the same time as
30169 I/A Transition two MNB application downloads someone downloading the
occur simultaneously device using WorkStation.
If this situation occurs, re-
download the controller
using WorkStation.
Schneider Electric


Disregard values from
monitor tags connected
directly to the outputs of the
Monitor tags don't work on outputs NVI. Use monitor tags on
of chiller status NVIs in MNL-800s the outputs of objects
downstream from the NVI
to verify the operation of
the NVI.
MNL-800 SNVTs are not all
* I/A Transition removed when device type is Manually remove the
32566
changed from MNL-800 to SNVTs.
standard controller
When updating a PCT from
a live server containing
WPT applications, delete
* I/A Transition When an AS is restored into PCT, the automation server in
33384
an MNL application will not open the PCT, and then import
the server instead of
restoring an existing server.
After saving modifications to an

existing I/NET time schedule, if you Navigate to the I/NET
reopen the schedule to view it, Interface and then navigate
back to the I/NET time
* I/NET Transition there is a chance that the list of
32258 schedule. All actions
actions for that schedule may defined for the time
display incorrectly (i.e., one or schedule should now
more actions may be missing). display correctly.
It is not possible to adjust the time Use WorkStation to make

33115 of an I/NET time schedule from adjustments to the I/NET
I/NET Transition
WebStation. time schedule.
After recovering from a loss of

Ethernet connectivity, I/NET point
values on the Enterprise Server
may not begin updating again for
what could be a long period of
time. This delay can occur if
programs in the server have been
attempting to control I/NET points
during the Ethernet outage. Once
33378 * I/NET Transition Ethernet connectivity has been
restored, all queued I/NET
commands must be delivered
before the updating of I/NET point
values can resume. The length of
the delay will depend on how many
commands have been queued and
how quickly they can be delivered.
Delays in excess of 60 minutes
have been reported.
Schneider Electric


User cannot learn two Infinet
Learn one network and wait
Networks at the same time and
30089 * Infinet Transition until it is complete, then
when it is attempted you get a
learn the other network.
BACnet server error
Change windows setting for
Infinet version system variable decimal quantity or view in
31321 * Infinet Transition does not display entire Infinet
the device properties
firmware version
window.
The Default Value of a MultiState
Input is displayed as 7F802801 in
31374 * Infinet Transition
its Array when log is set to
Instantaneous
Users do not get a commission
31493 * Infinet Transition
error for duplicate Infinet ID
You cannot set the manual array
31585 * Infinet Transition elements of Infinet analog, digital,
or multistate inputs
After 'disable state-change
logging’ is selected, the
user continues to see any
alarm or reset events for
the alarm. This applies only
Infinet alarm 'Disable state-change to alarms that are already
31620 * Infinet Transition logging' behavior differs from SBO in the SBO alarm viewer.
alarm behavior So, acknowledge the reset
alarm in the viewer. After
this, you will not see alarm
or reset events if the
'disable state-change
logging' is checked.
When hosting Infinet objects
* Infinet Transition through EWS then navigation in
31717
WebStation stops working and user
gets logged out
Infinet system variables do not
31965 * Infinet Transition utilize Continuum import/export
(COV)
Script editor crashes when an i2
Drag application folder to
* Infinet Transition device is dragged into the Binding
31976 the template instead of
Template, Default name matching
entire device.
field in an SBO Script
* Infinet transition Infinet I/E: The export flag property
32002
is exported in SBO export files
Copying an i2 point with its Export
flag set to True, then pasting the
32021 * Infinet transition point into a different device, the
pasted points Export flag is set to
true
i2 programs reading infinity Server
* Infinet Transition values become disabled when Save the programs
32182
saving programs at the same time individually.
on COM A and COM B
Schneider Electric


i2 programs fail to save with a
32213 * Infinet Transition numeric input or output named Call it Setpoint.
'SetPoint'
Importing an Infinet Analog Output
that has an invalid channel results
32251 * Infinet Transition in a misleading error message, and
misleading State property value
Script Editor: Exception indicating

external component has thrown an
* Infinet Transition Use Task Manager to kill
32259 exception is displayed when user
the script editor.
attempts to open multiple script
editors
Infinet Schedule fails to download if
32292 * Infinet Transition the Occupancy point is selected
prior to the Schedule then
downloaded
Download required icon appears
* Infinet Transition Download the i2 to clear
32435 after editing i2 Infinet device
the icon.
Description and Location fields
AS-P crashes when deleting Infinet
32759 * Infinet Transition Interface with two Infinet Networks
Delete individual networks.
with 127 i2 devices each and the
objects do not get deleted
This will present seemingly
odd time stamp and value
Infinet i1 intrinsic logs last log time
* Infinet Transition listings when the same log
32812 is the current time and is not a
is viewed in two lists that
stored property as in the i2.
were generated in the
same interval.
Log back into server device
WorkStation intermittently crashes
* Infinet Transition with workstation and
33167 when renaming an Infinet device
rename the bound Infinet
value bound to an Infinet script.
value.
If an exported Infinet datetime
value is deleted and then another
Make sure that it does not
33264 * Infinet Transition is created to give it the same object
get the same ID as the
ID as the previous, the new
deleted object.
datetime value cannot be
controlled
Download the affected
Infinet values with alarm links
objects or the entire device.
* Infinet Transition intermittently fail to download when
33278 There will be an indicator
the Infinet bus experiences heavy
on the device that a
traffic
download is needed.
This is a result of importing
an object with a duplicate
Object ID (Foreign
Under certain conditions you can't Address). When this is
33394 * Infinet Transition create Infinet alarms when the path done the ID will be set to
is already being referenced Null until the object is
loaded to a live controller.
Always reload the controller
after an import to be safe.
Schneider Electric


Bring the value back to
Infinet 1: Attaching an alarm to a within range and
33540 * Infinet Transition point whose value should put it in subsequent alarms will be
alarm does not deliver an alarm. delivered.
Check the backup flag on

18346 LON Values of PV blocks not retained
creation.
Uncheck unconfigured
Enabled but not configured NIC_IP
NIC_IP_00X in L-Config
22080 LON in L-Config stops all interfaces in
and in WS use Device
ES
Discovery again.
The upload actually works,
Buffer overflow when but other unsaved objects
24669 commissioning a third party LON that may have been
LON
device that has more than 1024 opened at the time of the
NCIs tree collapsing will have
been lost.
Sometimes valid LON Bindings are
Although the binding is
indicated as faulty (Background
25364 LON indicated as faulty, it still
Color is red in Binding field) when
can be saved.
created
33329 * LON Failure to commission a device
LonWorks device
User is logged out before receiving
* LON Create User Group that has
33602 result from import of 3d party LON
no auto logoff
device
If the number of Network Variables Contact Product Support
26649 LonWorks/Xenta plus Alias entries >255 in 'Hosted' Services to get help to
device types, commission fails modify the XIF-file.
Takes up to 40 seconds to transfer
an analog value from one ES/AS to See final bullet in Section
31428 LonWorks/Xenta
a Xenta device and back to the 6.4.
ES/AS via bindings
XIF file created by Menta is deleted
25146 Menta
when Menta is closed
Comments counts as blocks when
Remove comments to
system is checking for max number
28344 Menta make room for more
of blocks while saving a Menta
blocks. Max is 4000.
program
MicroNet Holiday Schedule does Change focus and view the
32971 * MicroNet not refresh its dates when set by Holiday Schedule again
VisiSat. and the dates are updated
Create and subscribe
another Modbus input
33303 * Modbus Modbus TCP Network slowness object pointing to the same
Modbus register that is
being written
Modbus TCP Server
(TCPInterface) and Modbus Slave
33399 * Modbus Network (SlaveNetwork) doesn't
send exception to function code 43
(0x2B)
Schneider Electric


The OSS object found in
the NETWORK 8000
Interface using the self-
learning feature will learn
pre-start and pre-stop times
that are incorrect. The
times affected are for
outdoor air temperatures
Network 8000 OSS block fails to
33246 * NW8000 properly calculate table values
nearest the heating and
Transition cooling change-over
during optimum start
setpoints. This means that
for warm winter days and
cool summer days the
optimized times may not be
correct. At the temperature
extremes the OSS will still
be accurate.
The information in the Network tab Restarting the server will

21983 Other
is not updated update it.
Using auto-hide on multiple
WorkStation: Cannot open auto- nesting levels of panels
26169 Panels hidden tabs in a panel if that panel concurrently may produce
is auto-hidden in another panel unexpected results in
WorkStation.
If the trend log or graphic is viewed
directly in the WebStation or
WorkStation, then the zoom
31519 Panels/Workspace controls are shown correctly, but if Avoid empty initial paths.
a workspace containing a panel is
used, then the zoom controls are
not shown
Don’t execute the
Command "Commission" for LON
31450 * PCT command since it has no
hangs forever in PCT
meaning in PCT.
31483 * BACnet IP Network is offline after Change the IP broadcast
PCT
deploying from PCT address manually.
Deploy the configuration
and download the i2
PCT/Offline Engineering: You
device. On download, these
cannot edit any Infinet device
* objects with unassigned
32277 PCT object configuration properties in
object IDs will get assigned
PCT if the object does not have an
object IDs. Then users can
object ID
edit the configurable
properties.
Add the permission
* CRUD commands require less than capability to “delete” if the
33293 Permissions
obvious permissions user must be able to move
or rename objects.
Schneider Electric


Full support for NaN,
+infinity and –infinity is not
yet implemented. Use Nan,
+infinity, or –infinity for
LonWorks network
variables. For more
It’s possible to set many numeric
information, see WebHelp
26815 Property grid properties to NaN, +infinity and
topic "Not Active (NA)
–infinity
SNVT Values For MNL
LonWorks Devices". Use
NaN for Value and Priority
array properties in I/A
Series MNB BACnet proxy
objects.
Running a large number of reports Schedule reports to be run
22000 Reports at the same time may cause some on intervals of one or two
to be missed minutes.
Object not found/Incorrect Reports
23508 Reports being displayed when Reports are
opened in multiple tabs/windows
Reporting agent activity table not
23516 Reports visible completely when exported Export to Word.
to Excel in collapsed state
Add the existing tags after
adding the new tags to the
Newly added tags to the site/meter site/meter. Execute the
25534 Reports are not listed in the tbTagMappings tbTagMappings table and
table observe that newly added
tags are displayed along
with the existing tags.
Report Server will not collect
Refer to Engineering
26975 Reports events due to mismatch in Server
section 6.9.
name
WebStation: Reports are not
displayed in object list view and
Select to show unsecure
27520 Reports can therefore not be generated
content in the browser.
when the user log on to
WebStation through https
b3 Multistate schedule: User can
set value greater than 32 (options
32293 * Schedules are only up to 32). In that case, Only use values up to 32.
schedule reflects the value
incorrectly
User created script data is
Save user created libraries
22562 removed during the uninstall
Script Programs to a non-default location
WorkStation portion of the upgrade
prior to upgrade.
process
Schneider Electric


If the WorkStation is
required to operate in
“FIPS” mode, then each
Edit script program not possible
26224 Script Programs time editing a Script
from a "FIPS" WorkStation
program is to take place,
the WorkStation must be
removed from FIPS mode.
A script program can get the status
of "Halted" with the error "Invalid Change the position of the
27112 Script Programs Function Binding" when many functions in the function
functions (discovered with 21) are declaration.
called within the same program
Non-English characters are not
28085 Script Programs resolved in Script Editor Binding
Variables and in SBO values
Prior to v1.8, the StrToNum
keyword permitted the
passed string to contain
non-numeric characters
and would still return the
numeric part of the string.
In v1.8, that is no longer the
Script Program - StrToNum case. In v1.8 StrToNum
31654 Script Programs function gives different results in requires that the string
v1.9.0 contain only valid numbers.
There is also a very useful
external function that has
been posted to the
community that can be
used in place of the
StrToNum keyword. That
file can be found here.
Schneider Electric


In SBO v1.6, the 'Xenta
Digital Schedule' has two
representations (object
types). The schedule object
type under 'Schedule Base'
represents the object in
SBO v1.5 and the other
schedule, on "the root"
object represents the object
in SBO v1.6. The reason
why the schedule object
exits in two versions in
When searching of Xenta Digital SBO v1.6 is to support the
26524 Search Schedule (in Include types) nothing user during upgrade from
is found SBO v1.5 to SBO v1.6,
when different servers
temporarily can be in both
SBO versions. The new
Xenta schedule editor can
handle both versions.
If you want to search for all

'Xenta Digital Schedules',
include both types in the
search criteria ('Include
types').
WorkStation crashes when copy
33277 * Search command is used from Search
result
When importing a search object or
upgrading a system that contains After upgrade or import of
search objects, the server will no search objects, confirm that
33874 * Search longer normalize non-existent the path of the search
paths to “~”. Instead it will enter the object is correct.
configured search path even if it
cannot resolve that path.
When saving an AS port log the Do not use the right-click
"Save as..." option to save
33400 * Serial port logs port log object changes to folder
serial port logs to disk.
and the log can't be saved again
The TGML graphic snippet
must be altered to use the
"setForce" method to
Sigma setpoint cannot be altered change the Sigma property
on a native TGML graphic value. This technique can
only be used with data
values and not
configuration properties.
Upgrading the Enterprise Server to
* Sigma Transition Restart the Enterprise
33213 1.9.0, causes the ES (Sigma)
Server.
global updates to stop.
Schneider Electric


Mouse icon "hangs" in scroll mode
31341 Spreadsheet View if left click and scroll mouse at the
same time Spreadsheet view
Instead of creating the
trend chart from the View
menu, create a new one in
the New Object Menu.
Users do not see data in trend Right click the b3 or i2
22534 * Trends charts for 'intrinsic' continuum logs application folder and
when selecting Point and View> select
trend chart New>Trend>TrendChart.
Select Trend Log Series to
Display.
When configuring Extended

Extended Trend Logs miss records
Trend Logs to retrieve trend
from b3 Continuum-Style logs data from a b3 controller,
when the log records are not set the number of records
26545 Trends
evenly divisible by the Extended configured in the b3
Trend Logs Maximum Transfer intrinsic logs to a multiple of
Interval the Extended Trend Logs
Maximum Transfer Interval.
The ES Service in the Skynet Use Windows task
system fails to stop fully when manager and kill the
31029 Upgrade
stopped from the Software process for the Enterprise
Administrator Server.
This may occur when many
AS are group selected
within Device Administrator
and the attempt to capture
the backup file occurs after
the initial logon to the AS
such that it has auto logged
off and, for some external
8 out of 162 AS (mixed types) reason, fails to log back in.
31497 Upgrade
failed to generate backup Three tries are made and
then the Linux system will
lockout the user for the lock
out “wait” period.
Subsequent upgrades are
likely to be successful. The
lock out wait can be
adjusted in the Security
settings of Control Panel.
it is possible to change
Some communication settings are protocols before upgrading
33326 * Upgrade not updated to AS in runtime the ES or simply upgrade
compatibility mode the AS which solves the
issue.
Schneider Electric


Enter C:\Program Files
(x86)\Schneider Electric
StruxureWare\Building
AS upgrade failed from Operation 1.8\Device
1.7.1.21001 to 1.8.1.17108. This Administrator\DBImporter\e
33623 * Upgrade occurs in rare situations when tc\config
customer has close to the Edit AS.Properties
maximum possible objects Change
NspServer.RuntimeDBMan
ager.ObjectPool.MaxNoOfI
ncrements from 6 till 7
When editing a User group from Edit using the properties
33408 * User Management Control panel, the Auto Logoff field instead of the Control
is not displayed Panel.
* Views Content type name is not updated
32786
on AS after rename
Events filter is removed when
32899 * Views WorkStation is refreshed, view
reverts to Standard
Duplicate server name in content
* Views Redo the content type
33253 type reference after upgrade from
reference.
1.9.0RC
For users with read-only
access it appears as they
Appears as if user can change
can edit values but this is a
25775 WebStation properties on values with only
pure visual effect.
Read access
Refreshing the page will
show the correct value.
IE11 sometimes stops working
28246 WebStation when clicking on a Cascading Restart Internet Explorer.
menu
In WebStation, BACnet objects that
30002 * WebStation are left at default NaN value, do not
show properties
Add users and/or groups in
Unable to add additional send to WorkStation and then edit
30476 WebStation email addresses in WebStation the users emails directly
v1.7.189 from WebStation.
System tree is not visible in edit

Add the Work Area before
26551 Workspace layout mode for Workspaces until
adding the System tree .
removed and added again
Graphic components not shown in Open graphic editor and
26908 WorkStation Graphic Editor after repair of WS add all components and
installation categories manually.
A monitored variable for a Function
17431 Xenta
Block Alarm can be edited
Schneider Electric

6. Important Engineering Information

Important engineering information with regard to the StruxureWare Building Operation v1.9.1. is
listed below. Before any engineering is accomplished, it is imperative that the upgrade
procedure described in section 9.2 be understood and followed.
6.1 General Engineering

 If operating from a WorkStation via a VPN to the StruxureWare Building Operation
servers, it is possible that communication to the license server could be disrupted. In this
case, licenses that are local to the WorkStations may be required.
 Change operations are queued for data integrity reasons; consequently, lengthy change
operations carried out by users may affect other logged on users so that their "queued"
changes seem to take longer. If there are extensive changes to be accomplished, it will
have less impact on day-to-day operational activities if the large changes are
accomplished at times of light utilization
 Setting time
o Until the time is set, b3 data will not update in the Watch Window.
o Until the time is set, BACnet COV will not be functional.
o Automation Server time does not synchronize directly with the Enterprise Server.
Instead, all servers can synchronize to the same accessible time server.
 If there are communication failure alarms with the Automation Server as the source
server and/or alarms indicating that the Automation Server Alarm Control Panel could not
“Verify Lead Object Status” with the Enterprise Server’s Alarm Control Panel, then there
is likely to be a communication problem between the Enterprise Server and the
Automation Server. The following items should be examined:
o Look at the “Communication” tab for the Enterprise Server and confirm that the IP
address for the Enterprise Server is correct.
o Examine the OS on the Enterprise Server and confirm that there is no firewall.
 Binding
o Changing the units to units that are incompatible after two objects have been bound
can result in a broken binding, unless the units were “No Units” prior to the change.
The Reference Manager will show this as an invalid binding.
 WebStation operation
o Some cybersecurity software products are currently available that make use of what
is known as “aggressive” caching. This action will prevent redirection and will prevent
a user from being able to log into an Enterprise Server or Automation Server that is
downstream of a device that uses this software. Such caching will need to be
disabled for WebStation to operate correctly.
 Long user initiated operations
o A user triggered operation, like hosting a big system via EWS or the manual start of a
huge backup, that takes more than 90 minutes to complete by the server will result in
an error message “Wrong user ID or password” and then WorkStation will be
restarted. The message is somewhat benign since the actual operation started by the
user will be successfully completed by the server.
 Resource limitations to consider during engineering
o When designing and engineering a system, make sure not to over-engineer a server.
Follow stated architectural guidelines and, for example, do not add too many trend
logs in an AS where resources are the most limited. Adding too much content and
logs can cause performance reduction and even a crashed server if disk ends up
being full. Reference the Architectural Guidelines from The Exchange for further
information.
o Uninstall one of many versions of SBO WorkStation
o If you have many versions of SBO WorkStation and uninstall one of the versions, you
need to do a “Repair” of the remaining installations in order for external editors
(Graphic, Function Block Program, Script) to work properly.
Schneider Electric

6.2 WebStation
6.2.1 Graphics Viewer
 Global variables that are already defined in IE, Firefox and Chrome will not work.
Example: top,x,y, width, height
 Functions that are called and that actually are properties show a script error.
Example: array.length() instead of array.length
 Scripts that do 'drag', need to call preventDefault() on mousedown. This disables
standard touch/drag panoration
 Use of Java classes is unsupported.
 Use 'var' when declaring variables inside TGMLscripts instead of assigning global
variables. This enables you to use global scripts (UseGlobalScripts flag in TGML root
element) that make it possible to share functions between Script nodes. Having
UseGlobalScripts set to True will also improve performance substantially in WebStation.
See section 6.3.
 There is a simple tool in the Statistics tab of the Graphics Editor that will tell you if your
image has some of these commons issues.
6.2.2 Workspace and Panels
The use of toolbars in WebStation is restricted. The Statusbar, Historybar and Addressbar have no
effect in WebStation. Hidden and Not available have the same results (Hidden).
6.2.3 General information

 Status overlays on the icons in the System tree are not available in WebStation.
 The feature Panel Navigation Pane type – Custom tree is currently not available in
WebStation
6.2.4 Security
Two new security features have been added in WebStation. They can be configured from
WorkStation -> Control Panel -> Security Settings
6.2.4.1 Enable external content to be enabled in WebStation

Checking this option (less secure) will allow linked content (hyperlinks) to be embedded in a panel. If
this option is not checked (more secure), external content will not be embedded but open in a
separate web browser tab. By default, external content is not allowed.
6.2.4.2 Enable WebStation to be embedded in another site

Checking this option (less secure) will allow WebStation to be hosted in an iframe within a third party
web application. If this option is not checked (more secure) third party web application will not be
able to host WebStation in an iframe. By default, WebStation is not allowed to be embedded.
6.3 Graphics
 The JavaScript engine in the Graphics Editor and WorkStation was updated in release
v1.8. This has a number of advantages: bugs fixed, better performance, stronger
compliance with the JavaScript standard and better compatibility with the JavaScript
engines that are used by web browsers. The stronger compliance with the standard may
result in compatibility issues with JavaScript code written in older versions of
StruxureWare Building Operation. The old version was sometimes more forgiving when
running JavaScripts that were not written correctly.
 By default, each Script element (script block) creates a JavaScript context. In this mode,
function calls between script blocks (contexts) are not supported, that is, no support for
global script functions. It is possible to enable scripts to run in one single context for the
Schneider Electric

whole graphic so that functions and variables can be shared between script blocks, by
setting the TGML element property UseGlobalScripts in the Graphics Editor to True. The
default is False for backward compatibility reasons. Setting UseGlobalScripts to True has
a very positive effect on graphics loading performance in some of the viewers, depending
on technology used.
 In order to improve performance in the WorkStation Graphics Viewer the behavior of links
has been changed. Before, when a graphic was shown, all links were validated to find out
if they were resolved or not. This took some time. Now the link is not validated until the
user clicks on it.
 When editing a TGML graphic in the editor, if you select “Save as” to save the TGML to a
file, the “Save” button will be disabled and it will not be possible to save the changes to
StruxureWare Building Operation. If the desire is to save a copy to file, then you should
choose export rather than “Save As”.
6.4 LonWorks
 When creating folders beneath a LonWorks Network, naming is more restrictive than other
StruxureWare Building Operation names. The name is restricted to 20 characters with no
minus sign.
 When a LON binding is created to a CPT, the delta is displayed as a property, but there
will be no effect if the user changes this delta. Consequently, the CPT will be written to
even on changes that are less than the entered delta. As a workaround, the user can
create a StruxureWare Building Operation binding to allow for adjustable polling
properties.
 When the Local Node is imported, it is necessary to perform a commission on the node
order to activate the bindings.
 To view network variables and configuration parameters in WorkStation select the
Variable Fields tab in Properties.
 To edit properties of a Network Variable (NV) in WebStation, simply left click on the NV in
the System Tree and the property grid is displayed. Alternatively, right click the NV in the
System Tree and select Properties and a Property Dialog is displayed. The Variable Fields
tab contain the values of the NV.
 After an upgrade to version 1.8, or later, you need to manually update some path
dependent internal functions if they reference LonWorks network variable fields. Check
and update your saved searches, saved watches and binding templates.
The structure in 1.7 and earlier:
.../SNVT/Member1/Value
The structure in 1.8 and later:
.../SNVT/Value.Member1
 After an upgrade to version 1.8, or later, you also need to manually update external
utilities that either generates structured LonWorks network variables to the system or
collect structured LonWorks network variables from the system. Examples of external
utilities are EWS, Expert Tool or other transition tools using the WorkStation transition
SDK.
 If a Xenta 401 device has an overall high load, with a large application program and many
trend logs, the following settings of the device Non-group receive timer are recommended:
o 768 ms, if the number of Network Variables <=50
o 1024 ms if 50 < the number of Network Variables <=100
o 1536 ms if the number of Network Variables > 100
6.5 b3 Devices
 When selecting and downloading from the application folder, it is necessary to select and
download in the appropriate order to satisfy all of the referencing accomplished in the
bindings. Downloading the entire device avoids this type of problem.
 When creating BACnet schedules, it is important to add those items to be controlled by the
schedule to the Object Property Reference List and NOT to use the binding tool to bind
those items to the schedule’s value.
Schneider Electric

 In order for extended log data to capture b3 log data successfully, they must be configured
in a very specific way: a) Smart Logs = False b) The intrinsic b3 logs must be evenly
divisible by the maximum transfer interval of the ETL Reference on The Exchange
Knowledgebase.
 Defect 30806 causes script programs that are triggered by system variables to continue to
be triggered even when the trigger is removed. To stop the trigger, it is necessary to
delete and recreate the program.
6.6 Trends
 When a COV trend log is created in an Automation Server to monitor an object from a field
bus device, attention should be given to the capability of the field device. If the field device
supports COV, as many BACnet devices do, then the BACnet device will supply the
Automation Server with data via COV, but it will do so at an interval that corresponds to
the devices interval not to the delta as established by the trend log. If the device does not
support COV, then the trend will function as a polling trend with an interval of 500ms. In
those cases, users should create an interval log to avoid unnecessary field bus
communication.
 In order for extended log data to capture b3 log data successfully, they must be configured
in a very specific way: a) Smart Logs = False b) The intrinsic b3 logs must be evenly
divisible by the maximum transfer interval of the ETL Reference on The Exchange
Knowledgebase.
 Each SmartStruxure server in an installation has two properties relating to trend logs:
Trend storage capacity and Trend storage usage. Whenever the usage exceeds the
capacity, a system alarm will be generated. There is also an indication whenever a trend
log of any type is created of how many records the new log will consume and what the
available storage is.
 Previous versions of the Architectural Guidelines contained erroneous information
concerning BACnet trend logs. All SmartStruxure server devices have a limit of BACnet
trend log size limit of 1,000 records. The v1.9.1 Architectural Guidelines have been
updated to include this limit.
 Several defects were resolved in v1.9.1 to eliminate the likelihood of a corrupt database.
In the course of resolving the defects, it was found that the likelihood of database
corruption increases dramatically as the quantity and frequency of trending increases. If
you are logging more than 300 trend logs per hour (and that could be any interval / CoV)
then you are in much greater risk of the database write error occurring. The problems are
mitigated by upgrading, but, until a site is upgraded it is wise to be reasonable in the
amount of trending that is done at the AS.
6.7 Archiving
When archiving using the CSV format, the maximum size limit for the archive will be 65,536, which is
the maximum allowed in an Excel spreadsheet.
6.8 Web Services

 Script Web Service
o When capturing date / time data through a script program in an Automation Server,
that time will be localized by the WorkStation to the time zone of the WorkStation
whenever the data is displayed. Consequently, the Automation Server’s script
program should include the logic to adjust the date/time value to UTC.
o Script programs do not recompile based upon bindings. Consequently, you may enter
a program, save it, establish bindings, and save the bindings. Yet, it will only appear to
be running without many of its outputs actually being set. It is necessary to force a
recompile of the programs to allow the web service information to be incorporated into
the actual byte code of the program.
 EcoStruxure™ Web Service (EWS)
Schneider Electric

o When configuring trend logs and extended trend logs, it is important to be aware of
their relative sizes and polling intervals. The trend log must have a size big enough to
store all values from a single poll - typically at least twice the size of values received in
one poll. Otherwise, the extended trend log will not be able to keep up with the trend
log. There must be sufficient time for the extended trend log to read the values from
the trend log before they are overwritten.
o EWS connections to servers and clients that support MD5 and not SHA2 (SHA-256)
HASH algorithms will require the MD5 is enabled in the SBO Server. The
documentation of each connecting EWS solution should be reviewed to determine
which HASH algorithms are supported when configuring SBO servers. MD5 is the
least resilient HASH algorithm and SHA2 (SHA-256) is the most resilient HASH
algorithm that SBO supports. The option can be found in WorkStation Control Panel ->
Security Settings -> Disable MD5 Hash.
o When configuring a multi-server system, it is best to establish the EWS interface after
all server renaming takes place. A client that uses cookies will suddenly trigger error
messages such as "access denied", and no more data will be communicated when the
server is renamed or moved into a multi-server configuration in a running system. The
cookies, and all other communication parameters, are valid so the client does not
detect any communication problems and continues to use that cookie. When this
occurs, it will be necessary to restart the reconfigured server.
6.9 Reports
 If the installation type is ‘Install’ then HTTPS in Enterprise Server URL is mandatory.
 The user account used for connection with the Enterprise Server should be a part of
‘Report Administrator’ group.
 If Enterprise Server is renamed, after collecting few events, and Reports Server is
installed at this time, then the first event details with the new server name (i.e. first
sequence number associated with the new server name) should be manually entered into
the tbEvents table to make the agent collect events data successfully.
 If Enterprise Server is generating around 2500000 ETLog records per day then the
maxHistoricalReadcount in reporting agent config file should be modified to 250000.
6.10 Authentication
 If the Enterprise Server is offline when logging on to an Automation Server there is only
one log on attempt. If that attempt is failed a timer is started which will not allow any log on
attempts until 2 minutes have passed.
 When setting up a site with a Windows Active Directory, make sure the Enterprise Server
is running with rights to read at least those AD-groups that are intended to be used for
authentication via SBO.
6.11 Schedules
 In order to accommodate as many resolution settings as possible for the graphic display of
the WorkStation Schedule editor, the smallest event duration for that editor would be 5
minutes. If an event duration of less than 5 minutes is desired, the user is directed to use
either the text editor that is located on the Advanced tab of the graphical schedule editor
or to use WebStation.
6.12 WorkStation Alarm/Client Notifications

 The Client Notification that was added in v1.7 to allow user control over the alarm “bubble”
that always appeared in early releases requires that a Client Notification object be present
for the notification (bubble) to appear. A system upgraded from before v1.7 will not have
this object and consequently the notification will no longer appear.
 If you wish to have a notification, create the object or objects and specify what the
conditions are to be for it to appear. You can create multiple object for different displays
based upon different schedules. Review the help system for more details.
Schneider Electric

6.13 WorkStation Alarm/Email Notifications

When setting up an SMTP server for email notification, there is an option to use a Schneider Electric
Email Server, smtpservice.buildings.schneider-electric.com. It is strongly recommended not to use
this service, but instead use one provided by the customer.
The Schneider Electric Email Server was introduced quite a few years ago and has not developed to
make it a good choice today. It suffers from low availability and does also not live up to the cyber
security requirements of today.
The service will be closed in a near future, so not only is it recommended not to use in new
installations, existing installations should also be re-configured to use another service.
6.14 Import / Export

 In keeping with the general policy of maintaining support for a period of time after releases
are delivered to the market, the 1.9 release will not guarantee backward compatibility to
files that were exported prior to release 1.5. See PA-00300 for more information on the
SmartStruxure Software Support Policy.
 Export files are, in general, NOT backwardly compatible. A Script or Function Block
Program that is exported from v1.9 is NOT guaranteed to import successfully into an
earlier release.
 Import of export files created before v1.8, with SBO bindings to Lon variable fields outside
the scope of the export file, will not convert those bindings when you import the file into
version 1.8, or later. They need to be corrected manually after the import. Please use
Binding Diagnostics in the Engineering section of the Control Panel to detect references
that are not properly converted.
 Import of an export file that contains a large number (>1000) trend log configurations has
a performance that is slightly worse than prior to v1.9.1.
6.15 Search
 If a saved Search-object from previous versions, has contained a type that no longer
exist in the server, e.g. an E-mail-notification that is converted to an Alarm Triggered
Notification, then the search operation will not find any object in v1.9 and need to be
manually re-configured in order to present the expected result.
 When importing a search object or upgrading a system that contains search objects, the
server will no longer normalize non-existent paths to “~”. Instead it will enter the
configured search path even if it cannot resolve that path. After upgrade or import of
search objects, confirm that the path of the search object is correct.
6.16 Sigma
 Before upgrading to v1.9 it is important to ensure that all Sigma Log Sets that have been
previously created using WorkStation are edited so that the ”Description” field is empty.
This is because during upgrade Sigma log sets with an empty ”Description” are identified
as Sigma log sets that have been created using Workstation and are converted to a
different object type. Once the upgrade has been completed the Description text can be
added again.
 After upgrading to v1.9 the Sigma Data Importer must be run so that the new TGML
schedules are added to the Sigma schedule objects. Failure to carry this out will result in
there being no graphical editor for Sigma schedule objects.
 Before running the Sigma Data Importer the Sigma Transition Component version
3.46.104 must be installed on the Sigma Server. The Sigma Transition Component is
available on the Software Download Centre.
 If Sigma globals are being used prior to upgrading to v1.9 it is important to restart the
Enterprise Server after the upgrade has completed in order to receive global broadcasts
from the Sigma network.
Schneider Electric

6.17 Xenta 400 Series I/O Modues

StrucureWare Building Operation 1.9.1 has been partially prepared for being able to connect Xenta
400 series of I/O modules to AS-P. Using Xenta 400 I/O mudules will open up for efficient transition
of Xenta 700, and potentially Xenta 401, to AS-P.
The full functionality is not available is not included in StruxureWare Building Operation1.9.1. Even
though it is possible to add such modules, the communication will not work. The full functionality will
be released as a Service Pack later this year. Separate announcement to follow.
Schneider Electric

7. APPENDIX A – StruxureWare Building Operation v1.9.1

Release Deliverable
The StruxureWare Building Operation Release.1.9.1 deliverable includes the following software
and firmware.
Hot fixes to prepare for upgrade to 1.9.1 (See Section 9.2)

Upgrading From Required Hot Fix
1.5.xxx WorkStation hotfix v1.5.0.171xx
1.8.1 WorkStation hotfix v1.8.1.23xxx
1.8.1 Enterprise Server hotfix v1.8.1.23xxx
1.8.1 Device Administrator (Automation Server) hotfix v1.8.1.23xxx
StruxureWare Building Operation 1.9.1 software and firmware

Product Version Build Included Service
Pack/Hot fixes
StruxureWare Building Operation Device Administrator 1.9.1 95
(Automation Server)
StruxureWare Building Operation License Administrator 1.9.1 95
StruxureWare Building Operation WorkStation 1.9.1 95
StruxureWare Building Operation Enterprise Server 1.9.1 95
StruxureWare Building Operation Report Server 1.9.1 95
Schneider Electric

8. APPENDIX B – Known Issues

Known issues in the StruxureWare Building Operation v1.9.1 are listed below.
1. Many problems arise when the Enterprise Server and Automation Servers are renamed.
Consequently, it is only possible to rename a server when no connection exists between the
Enterprise Server and any Automation Server or vice versa. The Enterprise Server must be
named first and the Automation Servers are named at the time of adding them as child
servers to the Enterprise Server. Do not attempt to restore a backup file that was generated
when the server had a different name. Once a server has been given a name, it should be
backed up for future protection.
2. Some elements of the system will occasionally fail to remove the temporary files that are
created on the WorkStation PC. Consequently, it is prudent to check the Temp directory and
accomplish deletions manually. This should be accomplished when WorkStation is not
running.
3. Occasionally, trend objects may look empty, but retain values in the List View. This can
happen if a Xenta device has been reused without emptying it first.
4. It is not possible to move a folder that contains a LON device from one Network to another.
5. When upgrading an Automation Server, the Device Administrator will indicate the upgrade
has completed successfully before it is actually possible to log on. The time difference can
be quite long for a large size database.
6. When two engineers are simultaneously editing the same program (Function Block or Script)
or using WorkPlace Tech Editor, they will have no idea that someone else may be editing
the same object. The final save of the object in question will be the final copy that is in the
server.
7. Alarm polling for an alarmed object on a LON device will continue to take place even if the
alarm shunt has been activated.
8. Alarms in the Reset state will be removed from the active alarm list if the Enterprise Server
abruptly loses power.
9. TAC I/A Series text reports do not function in the WebStation.
10. If a binding name is changed in the graphics or script editor, any binding that might exist for
that component is removed.
11. If a value is displayed in the spreadsheet view with localized units, then any copying of that
value to another location will also copy the localized units.
12. When a hot fix is applied, the true revision number can only be found from the properties of
the Automation Server as viewed from the WorkStation.
13. When working with Schedules on Xenta devices, it is possible to enter “over-night” events
and “Days of Week” exceptions directly through the Menta editor.
14. In some instances, when the Enterprise Server and License Server are on the same PC, the
Enterprise Server may attempt to start before the license server has successfully started. It
may be possible to delay the starting of the Enterprise Server using a batch file.
15. An event view can only show 100,000 entries. If there are entries that are older than
100,000 entries, a filter will need to be created that allow the entries of interest to be
included in the view.
16. Due to changes that were made in several areas of the Linux server operation, there are
more frequent spikes to the CPU utilization percentage. The average CPU utilization is not
substantially increased but there will be spikes that could generate false alarms if alarms are
attached to the CPU percentage. It is recommended that CPU percentage alarms include a
time delay of at least 60 seconds.
Schneider Electric

9. APPENDIX C – Procedures
9.1 Installing
For installation of StruxureWare Building Operation v1.9.1 WorkStation, Enterprise Server,
or Report Server, please reference the Web Help for that topic.
Note: The new SmartX Controller - AS-B product and SmartX Controller - AS-P will be
shipped from the factory with no SBO operating system. When the software (v1.9.1 or
later) is downloaded and Device Administrator is run, there will be an option to select
either New Database or Upgrade Database. New Database is the only option that will
work, since there is no database to upgrade.
As announced in PA-00500, the Automation Server is to be ordered only for service parts.
Consequently, any new Automation Servers that are purchased will be shipped with
version 1.8.1. There will be no new Automation Servers shipped with version 1.9.1.
9.2 Upgrading
9.2.1 General Upgrade Information
System upgrades need to be performed in a prescribed sequence to ensure there is no
loss of configuration or historical data. It is highly recommended that the Web Help
procedures starting with the System Upgrade Workflows topic are followed carefully. See
Functionality Upgrade section in Web Help.
Note: Release v1.9.1 offers the possibility to upgrade a system in a non-sequential way.
Any SmartStruxure solution that is currently at v1.5 or higher can be upgraded directly to
v1.9. These release notes describe the changes that have been made since v1.8. If you
are upgrading from a version that is older than v1.8, it is important for you to read the
earlier Release Notes which can be found here:
During upgrade from any of the previous releases, there is a limited level of runtime
compatibility during the upgrade process. The following compatibility is available:
1. Alarms and events on upgraded and non-upgraded SmartStruxure server devices
can be viewed from the upgraded Enterprise Server.
2. Trend logs on upgraded and non-upgraded SmartStruxure server devices can be
viewed from and collected (ET log) from Enterprise Server.
3. A graphic object on any server in the system with bindings to values on upgraded
and non-upgraded SmartStruxure server devices can be used to view and edit
those values.
4. View and edit properties (including e.g. forcing values) on non-upgraded
SmartStruxure server devices from Enterprise Server.
5. Search objects and properties on upgraded and non-upgraded SmartStruxure
server devices from Enterprise Server.
6. Consuming values to and from upgraded and non-upgraded SmartStruxure server
devices and Enterprise Server.
7. Backing up a non-upgraded SmartStruxure server devices from the upgraded
Enterprise Server and restoring the backup.
8. Lead / shadow relationships are maintained with the exception of the security
settings. Global security settings are NOT cascaded downward from the
Enterprise Server.
9. Communication setting changes that are accomplished at the Enterprise Server
will be propagated only to upgraded SmartStruxure server devices. However,
Schneider Electric

changing communication settings for a SmartStruxure server device is propagated

to all other SmartStruxure server devices.
Logging on to SmartStruxure server devices that have not yet been upgraded: Once
you upgrade the Enterprise Server to v1.9, you can no longer log on to the child
Automation servers with users that are members of a domain that is owned by the
Enterprise Server. You must log onto the v1.8 child Automation servers with a user with
appropriate permissions from a domain that resides in a v1.8 Automation Server. This is
due to the improved permission system in 1.9. Once the Automation Servers are upgraded
to v1.9, all users in local or ES Domains will be able to have the same access that they
had in v1.8.
IMPORTANT: Depending upon the size of the system and the quantity of trends, it is
possible that the database on the Enterprise Server could be quite large. When upgrading,
always make certain that you have at least twice as much disk space available as the size
of your database. It should also be expected that the Enterprise Server may appear to
“hang” for as much 20 to 30 minutes upon the first initial startup after the upgrade, but only
on the first start.
If ES-upgrade hangs and show error “-4”, then a restart of the PC will solve the problem.
The upgrade of Automation Servers from v1.7.1 to v1.9.1 will take longer than previous
upgrades because of a change in the way that trend and event data is stored. The added
time requirement is unique to this particular upgrade due to the changes being made to
data storage techniques. The more trend log and event data that you have, the longer it
will take to upgrade. For a typical installation the restart time will be approximately 20
minutes, however for extremely large db’s (300MB) the time taken for the upgrade could
be as much as 1 hour.
Note: Although an AS CPU-load may be high for some minutes after upgrade depending
on how large historical db there is, in extremely rare cases it can remain very high for
several hours. It is possible for multiple internal processes to be queued up in such a way
that the ability for the processes to complete is delayed by the need for the CPU to
accomplish higher priority items. Until that queue is emptied, the CPU usage can show to
be 100%. The AS will continue to operate correctly and will eventually calm down to its
normal usage levels. If an upgrade is performed at the same time as a backup is initiated,
it increases the likelihood of getting into a high CPU usage event. Consequently, it is
recommended that you insure that backups are not going to be triggered in the midst of an
upgrade.
Note: When upgrading Automation Servers, it is much faster to upgrade via the network
(IP) rather than via USB. Automation Server will upgrade in a two-stage process where the
first step copies the backup file from the Automation Server to the PC running Device
Administrator and completes all of the necessary activities to upgrade the database.
During this time, the Automation Server will remain operational. Once the database
upgrade has been completed, the user must choose to deploy the new database. During
the deployment period the Automation Server will not be operational from a controls
perspective.
Default Password Policies – An upgrade to v1.9.1 will apply default password policies. If
the user has not needed to change the admin user password as part of the upgrade, then
the user may not be aware of what the new policies are. It is strongly recommended
that the password policies be reviewed after upgrade.
Note: In a semi upgraded system where the Enterprise Server is upgraded to v1.9.1 and
the Automation Server is not, changes in Password Policies in the Enterprise Server will
not propagate to the Automation Server until the Automation Server is upgraded.
Schneider Electric

Downgrade – Downgrading a system has never been supported; however, there are
occasionally circumstances that may cause a person to abort an upgrade and revert their
system to the previous version by downgrading servers and restoring back up files.
Downgrading must be done locally via USB and following a DFU reset of the
Automation Server. The DFU reset may also result in the Automation Server falling back
to the default IP address which will then need to be changed.
9.2.2 Memory Consumption Before Upgrade

The RAM system memory usage on a SmartStruxure server device should never exceed
80%.The system will, after upgrade from 1.5 or 1.6 to 1.9.1, require slightly more
memory, so the current level of memory usage should be assessed prior to upgrade to
1.9.1.
The system memory usage must be less than what is stated in the “Pre-Upgrade System
Memory usage” column below to ensure it remains under the recommended maximum
memory loading of 80% after the upgrade.
If your pre-upgrade system memory usage exceeds that amount, you may need to make
engineering adjustments to reduce your memory usage or consider upgrading older AS
devices to AS-P or AS-B which have larger memory capacities.
Upgrade Increase Pre-Upgrade

from System Memory
usage
1.5 10% 70%
1.6 5% 75%
9.2.3 Upgrading a System with LON devices from version 1.5/1.6/1.7

In systems that have SBO servers that already are hosting LON devices based on
LonWorks imported device templates (.XIF) or resource kits (.DRF), the servers need to
be prepared before the upgrade from versions 1.5/1.6/1.7 to version 1.9.1 is done. Even
servers where device templates (.XIF) or resource kits (.DRF) are just imported, and no
devices or network variables are created yet, the servers have to be prepared before the
upgrade. If you are unsure if it is needed, go through the pre-upgrade process anyway.
The pre-upgrade process will not do any harm to servers not requiring pre-upgrade.
In multi-server installations, the Pre-upgrade LonWorks configuration command should be

issued in WorkStation logged on to the Enterprise Server. The Enterprise Server and all
Automation Servers online will then be prepared for the upgrade to version 1.9.1.
It is also possible to prepare each server individually by running the command logged on
to each server separately. The command can be launched multiple times, in any order, at
any time, as long as the server is running version 1.5/1.6/1.7. Not all servers have to be
prepared at the same time. If you decide to upgrade your installation step by step, you can
prepare the servers one at a time.
Steps to upgrade a 1.5.0 multi-server system:

1. Download the WorkStation hotfix v1.5.0.171xx from Exchange and apply the hotfix.
2. In WorkStation 1.5.0, logon to the Enterprise Server and prepare the LonWorks
configurations in all online SmartStruxure servers for version 1.9.1 upgrade. On the
File menu, point to LonWorks and click Pre-upgrade LonWorks configuration.
3. Proceed with the normal upgrade process, now or at a later time.
Schneider Electric


3. Proceed with the normal upgrade process, now or at a later time

3. Proceed with the normal upgrade process, now or at a later time.
9.2.4 Upgrading a System with LON devices from version 1.8

In systems that have SBO servers that already are hosting LON devices, and is running a
version or a hotfix with a build number that is less than 1.8.1.23xxx, the servers need to
be repaired before the upgrade from versions 1.8.1 to version 1.9.1 can be done. The
upgrade process is applicable both if the 1.8.1 configuration has been upgraded from
version 1.7 or if it is a new 1.8.1 installation.
In multi-server installations, the Repair LonWorks configuration command can be issued

in WorkStation logged on to the Enterprise Server. The Enterprise Server and all
Automation Servers online will then be prepared for the upgrade to version 1.9.1.
Steps to upgrade a 1.8.1 multi-server system where the original build or a hotfix is
installed with a build number that is less than 1.8.1.23xxx:
1. Download WorkStation hotfix v1.8.1.23xxx from Exchange and apply the hotfix.
2. Download Enterprise Server hotfix v1.8.1.23xxx from Exchange and apply the hotfix.
3. Download Automation Server hotfix v1.8.1.23xxx from Exchange and apply the hotfix
to all sub-servers (AS) already hosting LON devices based on LonWorks imported
device templates (.XIF) or resource kits (.DRF). If you are uncertain, apply the hotfix
to all sub-servers (AS) hosting LON devices.
4. Log on the Enterprise Server (ES) and run the Actions – Advanced - Repair
LonWorks configuration command. If the command is launched from the Enterprise
Server (ES), all servers in the multi-server system will be handled. You can also run
the command on each sub-server (AS) selected in the system tree, still logged on to
the ES. It is also possible to repair each server individually by running the command
logged on to each server separately. Make sure you have applied the hot fix to both
workstation and server(s) before you launch the command. The command can be
launched multiple times, in any order, as long as the server is running version
1.8.1.23xxx. The time to execute the repair command is highly dependent on the
number of LON devices in the configuration and the complexity (“size”) of each device
type. Save the information in the repair user feedback window (“Copy to clipboard”).
5. Restart repaired servers, Actions – Warm start. The list of repaired servers can be
found in the repair user feedback window.
6. Now it’s a good time to run the Actions – LonWorks - Delete obsolete Lon objects
command from the ES, if not already done. Make sure that all your servers in the
configuration have been updated to 1.8.1.23xxx before you launch the command. For
more details please see section 9.2.5 below.
Schneider Electric

7. A good practice is also to check bindings status before the upgrade to 1.9.1 takes
place. Open the Control Panel – Engineering - Bindings Diagnostics view to
check current binding status. Fix and re-bind broken bindings if necessary.
8. Proceed with the normal upgrade process.
Note 1: The system will not allow the upgrade to 1.9.1 unless the 1.8.1 configuration has
been repaired. If a server needs to be repaired, the system will prompt you to do so before
you can continue the upgrade process.
Note 2: The repair process may trigger some warnings in the Trace log that are OK. The
key words to search for is RecoverableException and Value.raw_data.
Example:
2017-03-23 07:02:11.000 [1826493440] nsp.csc.rtdbm.VariableManager LoadPropertyRTI swallowed
exception:RecoverableException: /home/ci/ci-build/rb-hf-181-cp-11-17100-
system/source/server/nsp_servers/csc/runtimedbmanager/source/RtDb.cpp(1358) Invalid Data Error:
Object_Property_Does_Not_Exist (0x10006) in module Runtime_Db_Manager(41). "~/port/net/3 part
devices/Warema_12M_2140210a (90:00:57:05:01:86:04:01)/BlindsController(0)
[22003]/nciInput_19/Value.raw_data"
Note 3: If you get an error message – Repair failed, contact the support – the following
information is needed to analyze what went wrong:
 A backup of the database before the Repair command was launced
 The workstation log – C:\Users\[CURRENT USER]\AppData\Roaming\Schneider
Electric StruxureWare\Building Operation\WorkStation\Logs\CoreLog.txt
 The Repair log – Copy to clipboard from the user feedback window
9.2.5 Delete obsolete objects after upgrading a System with LON devices
During the upgrade process from versions 1.5/1.6/1.7 to 1.9.1 all servers, hosting LON
networks using LonWorks imported Lon device templates (.XIF) or LON resource kits
(.DRF), need to keep objects representing references between servers in both the "old"
LON format and in the updated format. This is done to support runtime compatibility
during upgrade, when servers in a multi-server system are temporarily running different
versions. When the upgrade is completed and an internal "reference synchronization" is
done, the now obsolete objects can be deleted. The "reference synchronization" can take
all from a couple of minutes, up to a couple of hours, depending on how many servers and
how many bindings there are in the system.
The Delete obsolete LON objects command is found in the Actions menu when the server
object is selected. Make sure all servers have been updated to v1.9.1 before you launch
the command, or you may break references (bindings) between servers. If the command
is launched from the Enterprise Server (ES), all servers in the multi-server system will be
handled. It is also possible to launch the command logged on to each sub-server
separately.
Steps to optimize the configuration database

1. Make sure all servers in the system are successfully upgraded to version 1.9.1.
2. Let the system run for an hour, or two, to make sure the system "reference
synchronization" is completed.
3. In WorkStation, logon to the Enterprise Server to delete obsolete LON objects in all
online SmartStruxure servers. Select the Enterprise Server object. On the Actions
menu, point to LonWorks and click Delete obsolete LON objects.
4. Wait for the command to complete in all servers.
5. Done!
Schneider Electric

9.2.6 Update objects and tools that use path based LON references
As a result of the changes to the LON model, other changes are required to update path
dependent internal functions if they reference LonWorks network variable fields. Check
and update your saved searches, saved watches and binding templates.
The structure in v1.7 and earlier:
.../SNVT/Member1/Value
The structure in v1.8 and later:
.../SNVT/Value.Member1
After the upgrade to version 1.9.1 you also need to update external utilities that either
generate structured LonWorks network variables to the system or collect structured
LonWorks network variables from the system. Examples of external utilities are EWS,
Expert Tool or other transition tools using the WorkStation transition SDK.
9.2.7 Forced Change of Default Password

If default logon credentials for administrator account are used, you can expect a request
being shown to change password after upgrade which is mandatory. This is to increase
security aspects of the system.
9.3 Commissioning
1. In order to maximize the productivity of multiple engineers, it is best for each engineer to
work on one individual StruxureWare Building Operation Server. Allocate one engineer to
work on each Automation Server and then after the Automation Server devices are
approaching completion, they can be added as children to the Enterprise Server and the
necessary binding can be accomplished. It is possible that, when the Automation Server is
first added to the system and multiple Extended Logs are created at the Enterprise Server
which point to logs in the Automation Server, there will be a slowdown in the Enterprise
Server until the log updates are completed. Once an Automation Server has been added
beneath an Enterprise Server, it is still recommended that multiple engineers be
accommodated by logging directly into separate Automation Servers rather than the
Enterprise Server.
2. As in all software activity, frequent backups should be made. Perform backups when the
system is either unused or very lightly used.
3. As part of the regular system monitoring and maintenance plan, it is recommended that
Automation Server CPU usage and memory usage be monitored with alarms that trigger if
either item is at an excessively high level for a period of time. You can determine the
appropriate trigger values after configuring the system and validating normal operation. If
the alarms become active, evaluate your system storage and usage and if it cannot be
explained, then contact PSS to determine what might be at the root cause and how the
situation can be resolved
4. Be vigilant about closing unused panes, panels, tabs, etc.
Schneider Electric

Release Notes - V1.9.1 - StruxureWare Building Operation

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Release Notes - V1.9.1 - StruxureWare Building Operation

Загружено:

Авторское право:

Доступные форматы

StruxureWare™ Building Operation

1.1 Change History........................................................................................................................................ 7

2. STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE AVAILABILITY........................ 8

3. NEW FEATURES IN STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE ............... 9

3.1 Install/Upgrade ........................................................................................................................................ 9

3.2 Device and System Settings .................................................................................................................. 9

3.3 Cybersecurity .......................................................................................................................................... 9

3.4 WebReports ........................................................................................................................................... 10

3.5 Alarm Presentation ............................................................................................................................... 10

3.6 Search, Navigation and List Views ...................................................................................................... 11

3.7 Notification ............................................................................................................................................ 11

3.8 Users, permissions and logon ............................................................................................................. 12

3.9 Trends .................................................................................................................................................... 12

3.10 Schedules / Timers ............................................................................................................................... 13

© 2017 Schneider Electric, all rights reserved

3.11 Script Editor........................................................................................................................................... 13

3.12 Troubleshooting / Diagnostics ............................................................................................................. 13

3.13 Export / Import ....................................................................................................................................... 13

3.14 BACnet® enhancements ....................................................................................................................... 13

3.15 Modbus enhancements ........................................................................................................................ 14

3.16 LON enhancements............................................................................................................................... 14

3.17 EWS enhancements .............................................................................................................................. 14

3.18 Andover Continuum Transition ........................................................................................................... 14

3.19 Satchwell Sigma Transition .................................................................................................................. 15

3.21 TAC I/NET Transition ............................................................................................................................ 19

© 2017 Schneider Electric, all rights reserved

3.22 TAC Vista – Native Xenta Support and Transition ............................................................................. 20

4. DEFECTS FIXED IN STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE ............. 21

5. KNOWN DEFECTS IN STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE .......... 33

6. IMPORTANT ENGINEERING INFORMATION ........................................................................... 46

6.1 General Engineering ............................................................................................................................. 46

6.2 WebStation ............................................................................................................................................ 47

6.5 b3 Devices ............................................................................................................................................. 48

6.6 Trends .................................................................................................................................................... 49

6.7 Archiving ................................................................................................................................................ 49

6.8 Web Services ......................................................................................................................................... 49

6.10 Authentication ....................................................................................................................................... 50

6.11 Schedules .............................................................................................................................................. 50

6.12 WorkStation Alarm/Client Notifications .............................................................................................. 50

6.13 WorkStation Alarm/Email Notifications ............................................................................................... 51

6.14 Import / Export ....................................................................................................................................... 51

6.15 Search .................................................................................................................................................... 51

6.16 Sigma ..................................................................................................................................................... 51

6.17 Xenta 400 Series I/O Modues ............................................................................................................... 52

7. APPENDIX A – STRUXUREWARE BUILDING OPERATION V1.9.1 RELEASE

© 2017 Schneider Electric, all rights reserved

8. APPENDIX B – KNOWN ISSUES ............................................................................................... 54

9. APPENDIX C – PROCEDURES ................................................................................................. 55

9.1 Installing ................................................................................................................................................ 55

9.2 Upgrading .............................................................................................................................................. 55

9.3 Commissioning ..................................................................................................................................... 60

© 2017 Schneider Electric, all rights reserved

© 2017 Schneider Electric, all rights reserved

1.1 Change History

Revision Date Revision/Author Description/Change

© 2017 Schneider Electric, all rights reserved

2. StruxureWare Building Operation v1.9.1 Release

© 2017 Schneider Electric, all rights reserved

3. New Features in StruxureWare Building Operation

3.2 Device and System Settings

 SmartStruxure servers (server-to-server) – TLS 1.2 only

3.3.2 EWS Interface support for additional HASH algorithms

3.3.3 Policy options for embedded web content