Building Automation Knowledge Base

Issue After replacing Automation Server hardware the SNMP "msgAuthoritativeEngineID" changes, is this a possible security breach? Environment Automation Server SNMP Management console Cause This is intended behaviour and part of the snmpV3 implementation as described in RFC3414 2.2.1. msgAuthoritativeEngineID The msgAuthoritativeEngineID value contained in an authenticated message is used to defeat attacks in which messages from one SNMP engine to another SNMP engine are replayed to a different SNMP engine. It represents the snmpEngineID at the authoritative SNMP engine involved in the exchange of the message. When an authoritative SNMP engine is first installed, it sets its local value of snmpEngineID according to an enterprise-specific algorithm (see the definition of the Textual Convention for SnmpEngineID in the SNMP Architecture document [RFC3411]). Resolution The handling of this is not a StruxureWare Building Operation server activity. This is standard functionality as defined by the Automation Server's Linux platform and net-snmp protocol stack.

Issue Selection and installation of a pulsed output module. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, TAC Vista Environment Heat Meter Multical 602 Pulsed output module No pulses Cause Installed card does not give output pulses. Resolution Selection of the output card. The Schneider Electric part number is MAPULSETOPC and this is the equivalent to Kamstrup part number 602-0C This card will provide 2 pulse outputs for energy and volume, CE and CV respectively. Normally, energy (CE) is connected to 16-17 and volume (CV) to 18-19, but other combinations can be selected via the PC program METERTOOL, also used to select pulse duration 32 or 100 ms. The MAPULSETOPC is actually a top module, which means that it is fitted into the top piece of the MC602 calculator, basically the inside LCD cover. This is released by pressing downwards in the middle of the plastic piece on the left, and at the same time pushing the top module towards the left.

Issue A Schedule in a b3 under an Automation Server does not seem to have the same option to clear events that the Automation Server has or that was present when the same b3 is under a bCX in Continuum. Environment Automation Server b3 controllers Cause There is no option to delete multiple exception events from b3 Schedules similar to what can be done in the Automation Server. Resolution  They will need to be removed individually or wait until the exception event expires which should them remove them from the Schedule.

Issue When accessing http://help.sbo.schneider-electric.com you get an message saying "This topic contains privileged information" even though you should have access. Product Line EcoStruxure Building Operation Environment Building Operation WebHelp Cause The access right associated with the credential you log in with, does not allow you to view the topic you are attempting to view. Resolution The access right for the StruxureWare Building Operation help pages are handled by the Buildings Exchange team. Send an email to the team regarding issues with the WebHelp platform, and include as much information as possible. It is mandatory to include which email address you log in with, and what page and/or information you are trying to access: ExchangeSupport@schneider-electric.com

Issue In the TAC Xenta 151-D, the nvoAlarmStatus handles the test of the dampers, but the translation of the status is not documented Environment TAC Xenta 151-D Cause nvoAlarmStatusis used to report the actual status of the fire damper tests. Resolution nvoAlarmStatus is a SNVT_state with the use of the following bits: nvoAlarmStatus.bit0 = 1   OBJECT1_CLOSE_TIME_TOO_LONG    nvoAlarmStatus.bit1 = 1   OBJECT1_CLOSE_TIME_TOO_SHORT   nvoAlarmStatus.bit2 = 1   OBJECT1_OPEN_TIME_TOO_LONG     nvoAlarmStatus.bit3 = 1   OBJECT1_OPEN_TIME_TOO_SHORT    nvoAlarmStatus.bit4 = 1   OBJECT2_CLOSE_TIME_TOO_LONG    nvoAlarmStatus.bit5 = 1   OBJECT2_CLOSE_TIME_TOO_SHORT   nvoAlarmStatus.bit6 = 1   OBJECT2_OPEN_TIME_TOO_LONG     nvoAlarmStatus.bit7 = 1   OBJECT2_OPEN_TIME_TOO_SHORT    nvoAlarmStatus.bit8 = 1   OBJECT1_SET_CLOSE_TIME_FAILED nvoAlarmStatus.bit9 = 1   OBJECT1_SET_SELFTEST_OK        nvoAlarmStatus.bit10 = 1  OBJECT1_SET_SELFTEST_FAILED    nvoAlarmStatus.bit11 = 1  OBJECT2_SET_CLOSE_TIME_FAILED nvoAlarmStatus.bit12 = 1  OBJECT2_SET_SELFTEST_OK        nvoAlarmStatus.bit13 = 1  OBJECT2_SET_SELFTEST_FAILED     

Issue It is desired to configure a minimum off time, so when the compressor stops in e.g. heating mode, it will not start again before a minimum time has elapsed in the same mode. This setting is not available in the device. Environment TAC Xenta 121-HP Cause There is no setting for minimum stop time when in the same mode, there is only a minimum stop time between modes. Resolution As a workaround, set the "Activate at" value to something other than zero (say 10%), so that you can use the "Hysteresis" at 10%, and this way get a delay. This way you will get a delay in the most cases, a little time before the controller reacts.

Issue Is a certain version of Technician Tool Mobile Application compatible with all versions of StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool Automation Server Enterprise Server Cause The Technician Tool will always be backwards compatible, meaning that the latest version of the tool will work with any version of SBO. Older versions of the Technician Tool may not work with a newer version of SBO. Resolution Please note: Mobile experience to be replaced with EcoStruxure™ Building Operation v2.0 WebStation. For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool Always use the latest version of Technician Tool Mobile Application when possible, as that will work with all SBO versions.

Issue When attempting to rename an Automation Server, the following error is shown: Validation Error Validation failed for property 'PrimaryPassword'. Path: '[server path]'. Type 'Password' Cannot set property value to null because the property is not nullable. Environment Automation Server Cause The Automation Server has been cloned using a backup of another Automation Server, and in that process the SMTP server passwords have been set to null. Resolution Configure a password for the primary and secondary SMTP server. It does not matter what the password is set to.

Issue Error importing a StruxureWare Building Operation export file. Below is an example of the error.  ERROR: Import failed to commit changeset transaction with an exception. RecoverableException: /home/ci/ci-build/rb-rb-1.8.1-system/source/server/nsp_servers/csc/changesetmanager/source/ChangeSetTransaction.cpp(1442) Invalid Data Error: File_Extension_Not_Permitted (0x10048) in module Security_Manager(74). "Not permitted to store the file "htgseqintro.wmv" with the current Document Policy." - Stack Environment StruxureWare Building Operation 1.8 Cause The export file contains a document file extension that is not permitted in the Document Policy Permitted File Extensions Resolution The file extension has to be added to the Permitted File Extensions list. See Adding a File Extension to the Permitted File Extensions List on Web Help. For the error example shown in the issue of this article, the extension wmv has to be added to the Document Policy Permitted File Extensions. list. 

Issue The communication with TAC Xenta controllers is slow or inconsistent Product Line EcoStruxure Building Operation Environment TAC Xenta LonWorks communication Cause The Non group receiver timer is not properly set. Every device has a timer called Non group receive timer. The Non group receive timer is used to make sure that a re-sent Lon package will not be treated as a new message and to determine when a receiver buffer can be released. It is used in Acknowledged, Repeated and Request/Response transactions, but not in Unacknowledged ones. If this timer is set too low, a re-sent package, like Unacknowledged repeated message, may be treated as new messages, that will be sent on to the application. The communication buffers will not be released until the timer has expired. If the timer is set too long, that may result in the device running out of buffers, and new messages will not be received during this time. If a device has many SNVTs or TACNV’s being transferred there may be a need to increase the value of the Non group receiver timer. The default value for a programmable Xenta device is 768 ms. Resolution Change the Non group receive timer of the Xenta devices. The default value for a programmable TAC Xenta device is 768 ms. The recommended timer values are:   Number of network variables Non group receive timer value < 50 768 ms (default) 50 – 100 1024 ms > 100 1536 ms     The default value for the AS and AS-P  is 8,092 ms. There is no need to change that value.

Issue If a Variable status alarm is setup on a BACnet point it never triggers. Environment Workstation V1.8.1  and earlier Cause The reason is that the 3 available triggers (Forced, Overridden and Offline) do not apply to the BACnet protocol. If you open up the bindings page for a BACnet point you will see that none of the BACnet point attributes are the same as these 3 trigger statuses. Resolution Although from the SBO side you can force a point, what actually happens is that the value becomes commanded at "Command priority 8" (by default). The BACnet protocol does not have a Forced attribute. There is also no attribute listed for Overridden and Offline point in the BACnet standard. Because of this the Variable Status Alarm does not apply to a BACnet point.  

Issue Why isn't the OpenLNS a full, un-limited license? Environment OpenLNS OpenLNS CT Cause Renewing OpenLNS CT Annual Maintenance You can renew your annual maintenance for OpenLNS Server and OpenLNS CT before they expire. Renewing your OpenLNS and OpenLNS CT annual maintenance enables you to continue installing software updates and upgrades. If you do not renew the products’ maintenance, you can still use the products; however, you will not be able to upgrade it with updates or upgrades released after your annual maintenance expired. You cannot renew your annual maintenance after it has expired. Once it has expired, you must purchase a new activation key to be able to install any updates or upgrades released after your maintenance expired. To renew your annual maintenance, purchase an OpenLNS Commissioning Tool Professional One-Year Maintenance Renewal (Echelon model number 93800) or an OpenLNS Commissioning Tool Standard One-Year Maintenance Renewal (Echelon model number 93810). Echelon will process your order, and your maintenance coverage will be extended so that you can continue updating and upgrading OpenLNS and OpenLNS CT for an additional year. Resolution If paying the annual maintenance fee, you have access to updates and upgrades. Not paying still means that the program could be used, however it could not be updated with the latest patches.

Issue How to automatically have b3 controller backup to flash. Product Line EcoStruxure Building Operation Environment b3 Script Program Cause Script program syntax is a bit different to how it was done in Continuum, specific details needed on how to set this up.  Resolution This is a sample script program to enable automatic backup to flash when the controller database is different to what is currently stored in Flash. Create the below Script Program in the b3 controller. Make sure to bind both the input and output variables to statusbackup/value. 'bind statusbackupin and statusbackupout to the systemvariable statusbackup/value. numeric input statusbackupin numeric output statusbackupout init: if ts >= 5 then goto checking checking: if statusbackupin = backupneeded Then   statusbackupout = backupnow Endif goto wait1day wait1day: if td >= 1 then goto init

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.4x Integration with Enterprise Server EcoStruxure Building Operation 1.8 and above Cause Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown). Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database. Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation This EventId is seen in a registry entry called NspAmtEventId under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations Resolution Current workaround is to manually edit this registry key NspAmtEventId value to: A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required. OR Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue. If not then you should check the [InetDb].[dbo].[Events].[EventId].value After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation. It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.

Issue After re-installing Open Minds HAS causes, the license no longer appears in License Administrator. Environment License Open Minds HAS 8.6   Cause Re-installing LifeKeeper may have affected License Administrator installation due to the Open Minds volume monitor. Resolution Re-install License Administrator. Licese will show and operate after re-installation.

Issue Locating partners Environment Partner SmartStruxure Building Operation EcoStruxure Building Operation Cause Require engineer to visit for maintenance, servicing, installation or advice. Resolution Click Here to be linked to the available UK and Ireland SmartStruxure / EcoStruxure partner list. Note: For Ireland, enter Belfast, and partners in Ireland will also be shown.

Issue Alarm Control Panel - Number of entries for Cause Note, Action Note and Checklist  Environment SnartStruxure Building Operation Workstation 1.9 Cause The maximum number of entries that can be added for Cause Note, Action Note and Checklist are not indicated in available documentation.  Resolution There are no hard coded limits to the number of entries that can be added for the Cause Note, Action Note and Checklist

Issue Customers want to know how to localise their Reports Server  Environment SBO 1.9.3. Cause User may wish to change language on produced Reports etc.. Resolution Localisation of the Reports Server is currently not supported although there are plans to add this feature in a later revision.

Issue After starting up the SmartX Advanced Display for the the first time, the operator finds himself stuck in SmartXKiosk mode before having any chance to select a password/PIN code. Product Line EcoStruxure Building Operation Environment Advanced Display v1 Advanced Display v2 Cause SmartXKiosk has been selected as launcher. The first time the SmartX Advanced Display is booted up the operator is presented of a choice to use  SmartXKiosk or TouchWiz as launcher. If SmartXKiosk then is selected instead of TouchWiz the operator will enter SmartXKiosk without having set a password first. Resolution Request an unlock code (PIN) from your local support center, which will enable the operator to exit Kiosk Mode. Press the Home (Hardware) Button at the SmartX Advanced Display. This will enable you to choose launcher again. Make sure that "TouchWiz" is selected. Note: In the next release this will note be an issue, since you are forced to select "TouchWiz" at first use to proceed (if SmartXKiosk is selected, you will be prompted to choose again)

Issue Converting the entries from an MPX controller error log can be useful when there has been a software revision change. Product Line EcoStruxure Building Operation Environment EBO MPX Cause There may be an entry in an MPX error log that shows as follows: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change Resolution The ability to extract the firmware revision numbers from the controller error log is useful especially if you do not have the device report. Take a look at the last 2 numbers of the following line: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change 0x10000134  == 1.00.01.00134  (please disregard the missing 01) 0x18061101 == 2018 06 11 (ignore the trailing 01 in the hex number)