Building Automation Knowledge Base

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue When attempting to create a SOAP Web Service in StruxureWare,  WorkStation crashes after pressing the "Get operations" button for a WSDL file. Environment StruxureWare Workstation version 1.2.0.767 (released 1.2 build) Cause StruxureWare only accepts simple data types in the WSDL file.  Some WSDL files (e.g. Microsoft Exchange Server) uses complex data types (types.xsd) for input parameters and StruxureWare cannot process these data types.   Workstation crashes because of an unhandled exception. Resolution The unhandled exception error crash will be addressed in a future release so that Workstation does not crash upon receiving the error.  At this time, StruxureWare cannot process complex data types in WSDL files, and there are no plans to add this feature.

Issue When connecting MP-C controllers in a daisy chain, do they act as a repeater and boost the signal thus allowing total network distances of greater than 90 meters. Product Line EcoStruxure Building Operation. Environment Building Operation Multi-purpose Controller. Cause Each MP-C acts as a switch and decodes and generates a new fresh packet. Resolution Maximum 100 meters between each device when using daisy chain when connecting MP-C.

Issue With the M42 series actuators being obsolete, they need to be replaced. Environment M42 Actuator M42/230 8401000000 Actuator M42/230 8401300000 Actuator M42P/24 8402100010 Actuator M42PBB/24 8402400010 TAC Forta series M9/EM9 Cause Replacement of obsolete actuators. Resolution Spare part for actuator for valves with linear moving stem the complete actuator TAC Forta should be used. When a 230 Volt actuator is requested the TAC forta needs a supplementary 230/24 Volt transformer. Depending on the electrical installation certain modifications may be necessary. For valves with rotating stem, actuators M9/EM9 can be used.

Issue How to create custom reports in Building Operation WebReports Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Custom reports are typically created by modifying another report and then saving these changes. Typically used are the factory-supplied reports as the base for a new report then enter the filtering criteria that are required to be used in the new report. Assign a unique name to the custom report and save the new report as a dashboard or prompted report.  There may be a need to create a report not based on any of the standard reports provided in these Report Packs, this article covers this process. Resolution To create a non-factory-supplied report within WebReports it is necessary to use an editor.  Since WebReports use Microsoft Reporting Services it is recommended to download the Microsoft SQL Server 2008 R2 Report Builder 3.0 or MS MSQL Server 2012 Report Builder.  This is a free tool provided by Microsoft that provides an intuitive report authoring environment for business and power users. This download provides a stand-alone installer for Report Builder 3.0.  Please note that Product Support does NOT provide support for Report Builder.  After downloading and installing the Report Builder application, the steps are as follows:  Each of these steps is also located on the Building Management System WebHelp site, a link for each of these steps is provided for additional reference and guidance. Start Report Builder and create a new blank report, see Creating a Basic Report for the steps.  After Creating the report create a data source that connects this report to StruxureWareReportsDB, see Creating a Data Source for these steps Then create the Data set, so add to the report which tables, views, stored procedures, and fields from the StruxureWareReportsDB are required to use in your report, see Creating a Dataset for these steps. This data can then be added to the custom report as required.  See Setting Up a Report for an example of setting up a report. See Adding an Image to a Report  on how to add images to the report  The new report now must be deployed to the Reports Server where it can be accessible to WebReports. To complete this procedure use SQL Server Reporting Services Report Manager. See Deploying a New Report to the Reports Server to view these steps in detail.  Finally, the report must be synchronized in WebReports to be deployed and therefore appear in the WebReports Reports Tree. Use WebReports with a Web browser to complete this procedure.  See Synchronizing WebReports with a New Report for the steps to complete this. Once all these steps have been completed successfully the new Report should be visible in the tree - the placement of these reports will depend on where they have been uploaded in step 5 above.  See the image below:

Issue Can the Execution Precedence determine the priority of a program binding to a value? Environment SBO Function Block and Script programs Cause Clarification on the function of Execution Precedence is required. Resolution In both Function Block and Script programs there is an attribute called Execution Precedence, this can be set in the program "Properties", Basic tab. For a Function Block program:    For a Script Program: Execution Precedence determines the order that the programs will be run, the lowest numbers will be run first. In the 2 screenshots above the Function block program (Value 1) will be run before the Script program (Value 20). This can be used for applications where a calculation is done to generate a value, that is then used in a second program e.g. Calculation of a compensated setpoint, that is then used in a PID control program as the reference value. The PID program must have a higher Execution Precedence than the setpoint calculation. Execution Precedence does not affect priority. If the outputs of 2 programs are bound to a single value, both programs will be trying to control the value and give an indeterminate result.   To combine the outputs of 2 programs the programmer must use the appropriate logic to determine how the 2 signals should be combined for the application. So for Binary values use one of the logical operators: AND, OR, XOR etc, For Analog values combine the 2 results with Max, Min, Average etc as required.

Issue When a DELR or DELI block is used with a comparison operator to detect a change of value in the output of a function block, the output of the comparison operator should go ON for one scan when the source output value changes. If the source function block is a PVR or PVI this does not occur. For example: This code does not work This code works Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.3.0 or earlier Function Block Editor Cause There is a defect in StruxureWare Building Operation version 1.3.0 or earlier that causes this behaviour when writing to a public PVR or PVI block in a Function Block Program in the ES or AS directly from the Workstation. Resolution This defect has been logged with Quality Center and will be fixed in SmartStruxure version 1.4.0 Meanwhile, the workaround is to insert any compatible block immediately after the PVR or PVI.  For example: The inserted block could be an operator, an expression block or even another DELR. Although the workaround works, the preferred practice for new applications would be to replace the PVR with a RI and bind the RI to an Analog Value in the ES or AS. This defect does not occur in Menta programs in Xenta controllers, including those written in the SmartStruxure Menta Editor.

Issue One or more inputs on the SP-ACX will randomly report as open for a brief moment (a second or less), This can result in unauthorized door access if for example the input is associated with a door Exit Request. Product Line EcoStruxure Security Expert Environment SP-ACX Cause Electrical noise in wiring Resolution Increase the Alarm input speed, issue has been seen with Alarm input speed set to 0, increasing the input speed to 1 second typically resolves the problem.

Issue Error reads....BACnet Device for this Infinity controller is not created, please perform a ‘Find new BACnet devices’. Site does not have any BACnet devices Environment CyberStation CX Infinity controllers Cause Some how Event Notification objects are configured under the infinity controllers in the database Resolution Delete non applicable BACnet only objects that some how got configured under the infinity controllers

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 for assistance. Issue If TLS 1.0 is disabled on Microsoft Server 2016 you cannot connect to SQL Server 2016 database using Continuum database initialization. Product Line EcoStruxure Building Operation, Continuum Environment Continuum Cyberstation Microsoft SQL Server 2016 Microsoft Server 2016. Cause Microsoft no longer supports TLS 1.0 protocol and IT departments are disabling it. The current version of the ODBC driver (SQL Server) used with Continuum will not function correctly when TLS 1.0 is disabled on Windows Server 2016 in order to use TLS 1.2. A defect/hotifx QC#2290 has been issued for this issue. Resolution There is a hot fix for QC#2290 that needs to be applied to the cyberstation after the installation of the ODBC driver version 13. Use the following link to download the appropriate version of the ODBC driver for your version of the OS. Link to download ODBC driver version 13 https://www.microsoft.com/en-us/download/details.aspx?id=50420 This hotfix fixes the following defect 2290 = When TLS 1.0 is disabled on server 2016 ODBC does not connect to SQL database. Hotfix is attached below. Contact PSS for the hotfix for Cyberstation 2.03 Please note: The ODBC Driver 13 for SQL Server needs to be installed before the hotfix is applied Deprecation date   Steps to apply this hotfix: Create a ContinuumDB backup Shutdown Continuum if it is running Make a backup of OmsInst.exe in the Continuum folder Extract the OmsInst.exe from the hotfix zip file and copy the new file to the Continuum folder Do an update/initialized database Start Continuum

Issue How can I find out whether the EBO 2022 multi-version support applies to AS Classic module?  Does it apply to all the AS, AS-P, and AS-B modules? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The EBO 2022 Release Note describes that the EBO 2022 Device Administrator software is not supported on the original AS classic (part number SXWAUTSVR10001) but there is no description of the software backward compatibility of the EBO on AS classic. Resolution An AS classic can continue to exist in a multi-version system; the maximum version an AS classic can operate at is 3.1.2. It is nowhere implied that it is not supported under a multi-version setup. The statement “EBO 2022 does not support AS classic” in the EBO 2022 Release Note is misunderstood. It simply means that one cannot install EBO 2022 on an AS Classic, the same as the previous EBO 3.2 version. Note that the AS Classic will not inherit any features introduced in later EBO releases when operating in a multi-version system.

Issue When configuring the in-built Visitor Management System (VMS) there is no report mechanism under the Visitor tab to show visitor access. Product Line EcoStruxure Security Expert Environment Security Expert Client Visitor Management System Cause Reports for visitors are part of the list of the Report types under the more general User reports Resolution Visitor reports for visitors using the in-built VMS can be generated with a User Report by selecting one of the following Report Type options: All current visitors All overdue visitors All visitors by date Visitor user report setup This can then be further configured to your requirements by editing the report filter. Launch the event report view in a new window by pressing the Edit in report view button. The report can be run and filters can then be configured as required and saved as the default report filter.

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue Building Operation WorkStation freezes and crashes. The stack trace shows: System.ComponentModel.Win32Exception: Not enough quota is available to process this command Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause This is an error from Windows system: Not enough quota is available to process this command There are two potential causes for this error: Windows does not have enough virtual memory for all of the processes that are currently running on the machine or Windows is running out of other resources such as: disk space, handles, GDI resources, process message queue or something else. This error turns up on a lot of programs in Windows intermittently, such as Windows File Explorer. WorkStation freezes (usually because its waiting on the server) and the user tries to do a 'soft' shutdown (not a kill process) of WorkStation in the Task Manager. The Windows OS then sends instructions via the message queue (to simulate a user press on the "red cross" button on upper right in caption bar) which in turn leads to this quota error. Resolution If this error is seen, Microsoft recommends closing some applications and trying again. If you still get this message, increase the size of your paging file.   In the Taskbar Search, type “Advanced System“. You will see View Advanced System Settings. Click on it. Or you can navigate to it via Control Panel In System Properties, click the Advanced tab In the Performance section click the Settings button Performance Options will open. Click the Advanced tab Here, under Virtual memory, select Change Uncheck Automatically manage paging file size for all drives Highlight your Windows system drive Select Custom size Change the Initial size value and the Maximum size value to a higher value Click Set Finally, Click Apply/OK all the way  

Issue Why do controllers go into bootloader mode? Product Line Andover Continuum Environment Bootloader NC2 BCX CX99xx CX96xx i2 b3 Cause Continuum controller are placed into bootloader mode if they repeatedly hit a firmware level exception. An exception is when the controller tries to do something that cannot be done.  Some examples of an exception are... A controller tries to read from memory that it cannot read from. A controller attempts write to memory that cannot be written to. On startup, flash generation controllers load the application from flash RAM.When they hit an exception, older, non-flashable controllers would simply clear the application software from ram, power up and wait for the software to be loaded from the front end.  If there is a bad application there needs to be a means by which a user can intervene before the application is loaded so that the controller firmware can be reloaded or upgraded.  When a flashable controller hits more than three exceptions within a ten minute time period the controller is placed into bootloader mode intentionally. Resolution When a controller repeatedly goes into bootloader mode it is time to take a close look at environment which might be driving the controller to hit exceptions A controller usually goes into bootloader mode due to environmental issues such as Heavy ARP traffic Controller grounding Controller power issues Problems with the communication bus. A controller that repeatedly hits exceptions is placed in bootloader mode by design.  Flashing a controllers firmware is the only way to get a controller out of bootloader mode. 

Issue How to connect a SpaceLogic IP Controller via MSTP Product Line EcoStruxure Building Operation Environment Workstation Automation Server (ASP/ASB) Space Logic IP Controller RS-485 Adapter Cause Only certain SpaceLogic IP Controller models and versions support the new BACnet MSTP Adaptor and details are required on how to configure these controllers for BACnet MSTP. Resolution The following video will illustrate how to: Configure ASP/ASB for BACnet MSTP Communication. Configure a SpaceLogic IP Controller as a BACnet MSTP device. Discover the SpaceLogic IP Controller on the BACnet MSTP network. Things you need: Software EcoStruxure Building Operation Workstation 2022 Building Commission Application (available from Google Play, Apple Store, or Microsoft Store) Hardware ASP/ASB version 4.0 or higher RP controller (hardware version 10 ) RS-485 Adaptor (Isolating or Non-Isolating) RJ45 UTP Straight Through Cable (12"/300mm or less) Note: - if the RP controller does not show MSTP settings check the Space Logic IP controller firmware release notes and install firmware corresponding to the EBO version.  For example firmware versions 3 and below do not have settings for MSTP configuration. Before attempting to install a SpaceLogic controller on MSTP consult the following: Isolated RS-485 Adapter and Non-isolated RS-485 Adapter for SpaceLogic IP controller types supporting the RS-485 MSTP adapter RP-C BACnet MS/TP Support for RP models supporting BACnet MS/TP Installing an RS-485 Adapter for information on installing the BACnet MSTP adapter Connecting an Isolated RS-485 Adapter and Connecting a Non-isolated RS-485 Adapter for port usage and CAT 5 UTP connection cable Allocating Flexible Ports for additional considerations on port usage Enabling the BACnet/IP Controller to Communicate on an MS/TP Network Please see the video below:

Issue Unable to perform a backup or copy files from an I/A Series G3 station - indicates: Error parsing list of remote modules.      javax.baja.sys.LocalizableRuntimeException: Error parsing list of remote modules Environment I/A Series G3 (all versions) Cause The backup and copy processes include a scan of the remote station's module directory.  The software is encountering a file that is not a module and does not have the .jar extension.  A user may have transferred a non-module into the directory by mistake. Resolution Locate and remove the file causing the issue. Using Workbench, connect to the platform of the ENC, JACE, or remote station and run the File Transfer Client. Navigate to the /niagara/modules directory that will list out the modules (jar files) installed in the station. Review the list to locate the file that is not a module (jar extension). Highlight and delete the file.

Issue BACnet MSTP Wireshark capture Product Line EcoStruxure Building Operation Environment Schneider Electric StruxureWare Building Operation AS using MSTP for BACnet Cause Example of Wireshark capture and WriteProperty in MSTP    Resolution Using Wireshark, a bacapp.confirmed_service == 15 filter is applied which shows only BACnet WriteProperty packets Below is a screenshot of the Wireshark screen after applying the filter. I have Requests (REQ) and Acknowledgements (ACK) shown: Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be 0.00 Below is a Request, and clarification on what is Requested. A third party Metz (address 91) device is requested from the AS (address 0) for Analog Value 1 to be a value of 100.00 Filters which may be useful: Capture Filters   udp port 47808 BACnet/IP packets on UDP port 47808 udp port 47808 or udp port 47809 BACnet/IP packets on UDP port 47808 or 47809 Display Filters   bvlc || bacnet || bacapp all BACnet packets bacnet BACnet NPDU packets bacnet.mesgtyp BACnet Network Layer (router) packets bvlc BACnet/IP packets bvlc.function == 0x0b BACnet/IP Broadcast packets bacapp APDU packets bacapp.confirmed_service == 12 readProperty packets bacapp.confirmed_service==14 readPropertyMultiple bacapp.confirmed_service == 15 writeProperty packets bacapp.confirmed_service==16 writePropertyMultiple bacapp.confirmed_service==1 confirmedCOVNotification bacapp.confirmed_service==5 subscibeCOV bacapp.unconfirmed_service == 0 I-Am packets bacapp.unconfirmed_service == 8 WhoIs packets bacapp.unconfirmed_service == 2 unconfirmedCOVNotification packets bacapp.unconfirmed_service==3 unconfirmedEventNotification bacapp.unconfirmed_service==6 timeSynchronization     mstp.frame_type>2 exclude all token passing mstp.frame_type>127 view all proprietary traffic mstp.frame_type==0 only token passing mstp.frame_type==1 only poll for master mstp.frame_type==2 only poll for master responses bacapp.instance_number==[BACnet ID] all traffic from/to a specific ID mstp.dst==[MAC address] all traffic to a specific MSTP address mstp.src==[MAC address] all traffic from a specific MSTP address ip.dst==[IP address] all traffic to a specific IP address ip.src==[IP address] all traffic from a specific IP address      || (between filters) combines above filters (or)  && (between filters) combines above filters (and)   Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.

Issue While RS485 requires a daisy chain topology, can b-Links be daisy chained along with b3 controller in the BCX segment. Product Line Andover Continuum Environment MSTP b3 B-Link RS485 Cause While RS485 requires a daisy chain topology, the addition of b-Links to a RS485 bus makes the limitations of bus wiring less clear. Resolution RS485 is an electrical standard.  The key to understanding RS485 topology conformance is to understanding that each segment of the RS485 bus must have a daisy chain topology with the required termination resistors installed at each end of the segment. The bus segment that runs from the BCX controller to inputs of several b-links and or b3 controllers would constitute one segment.  As long as this segment has a daisy chain topology with the proper termination resistors installed it conforms to the requirements of RS485 bus wiring. Each outgoing leg off of any given b-Link constitutes one distinct and separate segment. As long as this segment has a daisy chain topology with the proper termination resistors installed it conforms to the requirements of RS485 bus wiring.

Issue Need information on programming holidays and special dates Product Line EcoStruxure Access Expert Environment Access Expert Hosted software V3 Resolution Programming Holidays and Special Dates   Overview   Holidays are exceptions to a normally scheduled interval. Feenics has made several fundamental changes to the holidays within the Keep by Feenics System. This article will walk through how the new holiday sets work and how to implement them. The holidays apply globally to all schedules.   Updating    The launch of the new holiday system requires a system upgrade within your instance. This upgrade only needs to occur once and is irreversible. To upgrade, click the "Update Holidays" button.   Note: Before you begin converting holidays, there can be no more than 8 holiday sets in the older system for the update to work.   Once that button is clicked, a warning will pop up letting you know that the process is irreversible. Click OK and your instance will be updated.     ***Note: Customers within an Enterprise instance will need to apply this update to ALL shared instances and the Enterprise instance separately.   Adding Holidays   Holidays are added to the system through the "Add Holiday Duration" button. This will add a holiday interval to the system. Holiday Durations   Holiday Durations are days in the system on which, the schedules should not activate. To add a Holiday, click "Add Holiday Duration", then name the day. This day will prevent all schedules from activating unless added to the "Always Active On" column in a schedule. Holiday durations are limited to 255 per instance.  Display Name: The name of the holiday interval, i.e. Valentine's Day, Halloween, Veterans Day. Start Date: The date the holiday interval begins on. End Date: The date the holiday interval ends on. (If the start and end date match, the holiday will be for that day only). Special Date: This flag inverts the behaviour. If this holiday interval is assigned to a schedule interval (via Holiday Groups), the schedule interval will activate for that day. Holiday Group: This selection allows the user to group holiday intervals into sets.  Tags: As in the rest of keep, tags allow for organization and permissions to be set by these groupings.   Holiday Groups   Holidays can be grouped together by using holiday groups. These groups are edited by selecting the "Edit Holiday Groups" button and modifying the Group Name. Holiday intervals are then added to the group by assigning them in the Holiday Group column of the holiday interval. ***Note: The shared holidays between groups should be in their own group. This will allow the non-shared holidays to be applied to schedules correctly.   Applying Holidays   Holidays apply globally to all schedules. A holiday Group can be added to a schedule interval to tell that interval to ignore that holiday.   ***Note: If a holiday exception is added to a schedule interval, the schedule will activate on the day of the holiday, regardless of the day selection on the schedule interval. Special Dates   Special Dates can be used to activate a schedule interval for a day or group of days regardless of the other intervals within the schedule. To add a special date, open the Holidays page and add the day(s) as a holiday interval, then check the "Special Date" box. Add the special date(s) to a group on its own.