Building Automation Knowledge Base

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 Confirming compatible Modbus data types available for a Sigma IC3 Modbus Product Line Satchwell Sigma Environment Sigma Release 4_05-SEB (Build 3_43_18) Sigma Release 4_05-SP2 (Build 3_42_48) Sigma Release 4_06 (Build 3_44_14) Sigma Release 4_06 SP1 (Build 3_44_16) Sigma Release 4_07 (Build 3_45_48) Sigma Release 4_07-SP1 (Build 3_45_51) Sigma Release 4_07-SP2 (Build 3_45_58) Sigma Release 4_08 (Build 3_46_57) IC3 Modbus Cause The use of 64-bit is not mentioned in documentation Resolution 16-bit registers are supported with all versions of Sigma. From Sigma release 4 05 SEB (Build 3_43_18) 32-bit registers are supported. 62-bit registers are not supported with Sigma IC3.   The ba077 Modbus 32-bit application note provides information on the engineering of 32-bit registers. https://ecoxpert.se.com/search?documentUUID=74eaf0dd-fbd9-4429-9c82-eb205aa9be07&title=BA077%20Modbus%2032%20Bit%20Values%20-%20Satchwell%20-%20Application%20Note Sigma 4.06 IC3 Modbus Firmware and Release Note https://ecoxpert.se.com/search?documentUUID=cb99b073-d9ab-400e-8e67-2f8343447768&title=Sigma%204.06%20IC3-Modbus%20Firmware%20-%20Release%20Notes Sigma IC3 Modbus 1.n.2 firmware is the latest available version https://ecoxpert.se.com/search?documentUUID=02d88785-9d13-4184-b74a-d1a0b5ce7edd&title=Sigma%20IC3%20Modbus%201.n.2%20-%20Firmware    

Issue When backup to flash is automatically disabled by the system due to exceeding the flash circuit breaker write limit, no system alarm is sent to make the system's operator aware  Product Line EcoStruxure Building Operation Environment Continuum i2920 Controller Cause Implementation of Continuum Infinet integration in EcoStruxure Building Operation did not include this feature. Resolution As a workaround, a user-created alarm can be used instead of the system alarm. Here is a sample implementation of this workaround:   Under the Infinet Interface create an Alarm, in this example, we are using an 'Expression' alarm Here is the algorithm used as an expression for the alarm Value = BackupDisabld In the i2 device, edit the 'StatusBackup' system variable and attach the alarm above in the Alarm Configuration tab. Make sure to tick the 'Enabled' box to engage the alarm.   The alarm will be sent when the flash circuit breaker trips which in the i2 device takes place after 10,000 backups To resume backups the feature must be manually re-enabled from Workstation by right-clicking the device and selecting DEVICE->ENABLE BACKUP TO FLASH

Issue The WorkPlace Tech application drawing contains a hardware tag that is outlined in red and displays this error message when viewing the right-click Display Errors option for the tag Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio Cause The issue may be caused by incorrect copying and pasting of objects inside or between drawings.  An absolute cause has not been determined  Resolution Open the application in WorkPlace Tech or Editor.  Don't open the .vsd or .vsdx file in Visio alone. Enable the Developer in the Visio ribbon. File/Options/Customize Ribbon/check "Developer"  The Developer must be enabled to have the Show ShapeSheet option available  Right-click the Input object and select Show ShapeSheet In the ShapeSheet:  Step 1. Select the corrupted string for the Connection Points Step 2. Delete the string Step 3. Click the green check mark to save Unlink and Relink the connector between the previously corrupt object, UI01 in this case, and the Analog Input object.  Note, that this could be a Binary Input object as well.  This will add the correct string to the Connection Points.  

Issue IP Controller is getting incorrect overrides at Priority 16. The room control unit is writing to Priority 16 which is then writing to multiple setpoints with a zero (0) value in the function block program, causing programming to fail. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Even though priority 16 and the Value can sometimes be synonymous, they are still separate Objects The room control unit is writing to Priority 16 AND the Value has been set to Zero.   The value is set to 0  Writing directly to priority 16 from the room control unit Resolution The best practice would be to:  Bind to the Value Object from the room control unit and also set the retain level under Value rather than biding to and setting Retain level on Priority 16

Issue As of EBO 4.0.1.86 it is not possible to bind to the "Restart" property of a b3/Infinet Script program Product Line EcoStruxure Building Operation Environment Building Operation - Continuum Interface Cause Unable to bind directly to the "Restart" property of b3 or Infinet Script program. Resolution While the issue may be resolved in a future version of EBO there is a simple workaround. The workaround consists of binding via an intermediate value object.   EXAMPLE: A b3/i2 program (MasterProg) needs to run a second b3/i2 program (SlaveProg).   Create a digital value in the device (ProgReStart), Instead of binding in MasterProg directly to the Restart property of SlaveProg, bind to the value of digital value ProgReStart, then bind the value of ProgReStart to the Restart property of SlaveProg.   Here are the resulting bindings for the intermediate value object (ProgReStart)     The sequence will then be as follows: 1. When MasterProg needs to run SlaveProg, it sets its output binding (bound to the value of ProgReStart) to 1. 2. Upon a change in its value from 0 to 1, ProgReStart will then set the Restart property of SlaveProg to 1 causing it to run.   NOTES 1. Do not use Active/Inactive, it won't work, must use 1/0 instead. 2. MasterProg will need to reset ProgReStart to 0 before running SlaveProg a second time

Issue After Sigma transition into EBO, upon alarm and alarm clear there is no requirement to acknowledge the alarm. In the Sigma Interface, the object alarm 'Type of Acknowledgement is set to 'No' and cannot be changed. Product Line Ecostruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Priorities are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm acknowledgement type is set to a specific type. If no alarm priorities are set for acknowledgement in Sigma, then this is repeated in EBO.    To change to 'Single' so that alarms and alarm clears are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Acknowledgement Groups   Redistribute the alarm priorities into the the different acknowledgement groups as per the site requirement. The image below shows the default view on a new install of Sigma.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'Extended', then the KB article Type of Acknowledgement set to 'Extended' on Sigma Interface object alarm will explain how to change this.

Issue An XLSX report is created using a triggered Notification in EBO. When the report should be opened in Excel an error appear "Excel cannot open the file ..." and the report can not be opened. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Excel for Microsoft 365, Excel 2021, Excel 2019, Excel 2016, Excel 2013 Office for business Cause Formatting cells on your worksheet can make the right information easy to see at a glance, but formatting cells that aren't been used (especially entire rows and columns) can cause your workbook's file size to grow quickly. This can slow down not just Excel, but the overall performance of your computer when you have an excessively formatted worksheet open. Excessive formatting can also cause printing problems in Excel. Resolution Use the Clean Excess Cell Formatting command, available on Excel's Inquire tab in Microsoft Office 365 and Office Professional Plus 2013. Important: You may want to make a backup copy of your file before cleaning the excess cell formatting because there are certain cases where this process may make your file increase in size, and there is no way to undo the change. If you don't see the Inquire tab in Excel, do the following to enable the Inquire add-in: Click File > Options > Add-Ins. Make sure COM Add-ins is selected in the Manage box, and click Go.   In the COM Add-Ins box, check Inquire, and then click OK. The Inquire tab should now be visible in the ribbon.   To remove the excess formatting in the current worksheet, do the following: On the Inquire tab, click Clean Excess Cell Formatting. Choose whether to clean only the active worksheet or all worksheets. After excess formatting has been cleared, click Yes to save changes to the sheets or No to cancel. See Microsoft support topic:  Clean excess cell formatting on a worksheet 

  Issue PIBCV valves, stem up or stem down for valve open. Product Line Field Devices Environment PIBCV Valves VP220, VP221, VP222, VP228 Cause Further information required as to whether stem up or stem down for valve open position. Resolution When the stem is up (retracted into the actuator) the valve is open.   Example:

Issue Require the Automation license option to be able to configure C-BUS integration but the option is not enabled. Product Line EcoStruxure Security Expert Environment SP-C-WEB Cause Older SP-C-WEB controllers were shipped without the Automation license enabled. Resolution SP-C-WEB controllers purchased after 4-Oct-2021 are shipped with the Automation option included with the license.   For controllers ordered before this date the option can be enabled by contacting Product Support and providing the controllers serial number.

Issue What is the purpose of the battery/coin clip on some of the I/NET Hardware Product Line TAC INET Environment TAC INET Hardware  7718, 7716, 7798C  Cause The initial development path plan was to include an additional feature to allow communication with Dallas Semiconductor ID tag/coin, similar to that used with the I/NET Access Control I/DISC.  This development was never implemented Resolution This battery/coin tag serves no active purpose or functionality

Issue Subnet/Node address shown in Local Node Properties dialog is not what is used on the LonWorks Network. Product Line EcoStruxure Building Operation. Environment Building Operation Workstation. Building Operation Automation Server Premium. LonWorks . Cause When using External Managed Network, an external binding tool is used to address LonWorks devices, and the external tool sets the address in the Neuron chip, that is used for communication. This information is not tranfered to the database. Resolution When using External Managed Network, the correct address information could be read in the Domain table of the device.

Issue Replacements for Schneider-Electric SmartX MS41 Damper Actuator Product Line Field Devices Environment SmartX MS41 Cause Replacement of SmartX MS41 Damper Actuators within the Schneider-Electric range Resolution Outgoing Actuator Model          Replacement Model (Part Number)       MS41-6083-G00                        MD10A-24 (875 1019 000)       MS41-6153-G00                        MD20A-24 (875 1029 000)       MS41-6153-G10                        MD20A-24 (875 1029 000)       MS41-6153-G12                        MD20A-24 (875 1029 000) + Aux Switch (914 1061 000)

Issue Permissions are set with multiple tags as the following:      When the user logs into Access Expert and looks at the hardware tree, they are able then to see all the hardware on the instance rather than just those with the matching tags. Product Line EcoStruxure Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause The tags are meant to be on separate permissions and shouldn't be used on the same individual permission Resolution Tags and permissions should be set up as illustrated:

Issue After upgrading a site that contains MicroNet or IAC controllers from SBO to EBO the time Schedules no longer display time periods entered. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause From EBO 2.0.1 release includes support for MicroNet time and holiday schedules in WebStation, to achieve this the existing SBO schedules have been replaced by a TGML graphic for both WebStation and WorkStation. Resolution To enable the new schedules, run the Data Importer on each MicroNet interface, this will add new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Before upgrading. After upgrading. Carry out a Data import. After the Data import, then the associated TGML graphics can be seen. Further information is available in the EBO 2.0.1 release note. The graphic creation is confirmed in the trace information presented when Data importing: The trace will be sent to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt and the following is seen: Source: C:\Satchwell\Projects Full URL: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created

Issue Unable to access the SE7xxx Room Controller configuration parameters menu - displays an error code. Product Line EcoStruxure Building Expert, Field Devices  Environment SE7xxx Room controller SE7000 Series Ex. Viconics branding VT7000 Series Cause The display shows an error code when used, this is indicating a password is required, an example of the error code may be 977 or 996. Resolution Contact your region's Customer Care Center for a temporary password. The error code which is unique to that controller will be required by the Customer Care Center to calculate the temporary password. Note for PSS; Check Internal article. 

Issue Upon presenting valid credentials at the door and physically entering thru it, the event reported for the transaction is "Valid Access No Entry" instead of the normal Valid Access event. The door is properly configured with a door switch but the controller does not see the door switch open. Product Line Andover Continuum Environment Continuum CX Gen 1 Continuum Net Controller II Cause For unknown reasons the door's entry and exit IOU are set to the same value, typically the GUI will not allow such invalid configuration. Resolution Edit the door and set the Exit IOU to zero (for a single-sided door) or to the appropriate IOU number associated with the AC1/AC1Plus on the exit side of the door. 

Issue Importing Infinet devices into AS-P fails with the following error "Invalid Data Error: Invalid_Data (0x10000) in module Coml(11). "Invalid cast from null": CreateObjectRequest".  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause Infinet devices have a space character within their names Resolution Remove the space character and use an underscore in its place.

Issue Auxiliary I/O or inputs and outputs, allow a system to be expanded to include additional devices outside of standard door hardware such as sirens, panics buttons, or warning lights. Product Line Access Expert Environment Access Expert v3 Cause Lack of documentation on Auxiliary I/O Resolution Input Devices Inputs are also added to  Downstream (interfaces). Inputs are typically added automatically when used to support door contacts and REX but can be implemented to connect motion detectors, glass break detectors, and even panic buttons. Inputs in this section would be separate from those associated with the reader-controlled doors. Inputs can have cameras associated with them to associate alarm points.   Though you can assign multiple cameras to a single point the Assign Camera section will only present one camera at a time. The Assign View allows multiple cameras to be brought together in a single view. To add an Input: Open a downstream interface configuration Select the “Add Input” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. **Note: Take special care when setting the address as the value does not match the number labeled on the physical hardware. The first address is always 0 (not 1). Input Attributes: Display Name: This is the name of the input that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Behavior: The Normally Open or Normally Closed setting of the input. This is also where any custom EOL Tables are applied. Debounce: The amount of time required before registering the signal. Bouncing is the tendency of any two metal contacts in an electronic device to generate multiple signals as the contacts close or open. “Debouncing” is any kind of hardware or software that ensures that only a single signal will be acted upon for a single opening or closing of a contact. Latching Mode: This sets the type of latching used by the input. Normal Mode (No Entry or Exit Delay): This will cause the input to report an alarm immediately upon activation and deactivation. Non-latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires the alarm will be reported. If the input is not active when the Entry Delay expires, no alarm will be reported. Latched Entry: If set, the alarm will not be reported from an input activation until the entry delay expires. If the input is still activated when the entry delay expires AND the input has not been masked, the alarm will be reported. Entry Delay: The time before the input alarm will report. Exit Delay: This function is useful to secure a door when an individual is leaving.  When the ‘exit delay’ mode is set, the following shall occur.  The alarm will not be reported from an input activation until the exit delay expires.  If the input is still active upon exit delay expiry, the alarm will be reported.  If the input is not active upon exit delay expiry, the alarm will not be reported. Hold Time: This can be thought of as a Motion Detector Delay. This is the number of seconds that the change of state must be held before the input will be changed to a deactivated state. Attached: Sets the Attached status of the input. Input Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Input Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Outputs Outputs are also added downstream. Outputs are not only used to support strikes but can be implemented to connect sirens, strobes, and other signaling type devices. Outputs in this section would be separate from those associated with the reader-controlled doors. Outputs can also have cameras associated with them to associate alarm points.   To Add an Output: Open a downstream interface configuration Select the “Add Output” Enter a Display Name. Define the Address for the input. Set the Behaviour. Click “Save” or “Save & Close”. Output Attributes: Display Name: This is the name of the output that is used throughout the system. Address: The address that the hardware is connected to on the downstream. Activation Time: This is the amount of time the output will be active when pulsed. Mode: This sets the output to be in a normal operating mode (normally un-energized) or inverted operating mode. Schedule: This sets the time during which an output will activate. Assign Camera/View: The associated cameras or views for the output. These will display in the Live Monitor/Event History for events associated with the output. Output Addressing The address programmed in Keep will not match the address shown on the physical board. The programming address is 1 less than the space used on the physical board. Output Address on Board Programmed Address in Keep by Feenics 1 0 2 1 3 2 4 3 Scheduling Outputs Outputs can be scheduled by clicking the schedule drop-down menu and selecting the desired schedule. The output will then Activate when the schedule activates, and deactivate when the schedule deactivates.

Issue How does the controller-resident schedule work in a Revision 11.x MicroSmart controller? Environment MicroSmart controllers revision 11.x and 10.x Cause Main DMS panel and/or NC panel were removed. Resolution With the loss of schedule control from the DMS or NC, each controller has two built-in schedules numbered 1 and 2. The Start/Stop point requiring a schedule can be assigned either one of these schedules followed by a letter A or letter B. Letter A stands for 'always' and letter B for 'backup'. With no DMS or NC present, enter the schedule as 1/A or 2/A.  Assign 'off' and 'on' times as required. Remove any reference to a DMS or NC schedule number (i.e. set it to a value of 00). 

Issue When there are multiple displays, and the script editor is in the right window, the autocomplete popup window goes off-screen. *note* this only happens in full screen Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The issue depends on which way you assign the two monitors in the Windows settings or how you have the monitor cables hooked in the docking station/laptop. Resolution Swap the physical monitor plugs on the PC or docking station, allowing Windows to recognize your monitors synchronously from left to right Go into your Windows monitor settings and drag each screen to its proper position and hit apply.