Issue WorkPlace Tech 5.8.x, 5.9.x, and 5.10x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, and 5.10x Microsoft Windows and Microsoft Office Visio requirements, see the "Resolution" section, below. Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause What Microsoft Windows operating systems and what versions of Microsoft Visio are compatible with the WorkPlace Tech Tool version 5.8.x, 5.9.x, and 5.10.x? Resolution Microsoft Windows WorkPlace Tech Tool releases 5.8 through 5.8.6 are certified to run on the following versions of Microsoft Windows: Microsoft Windows XP Professional with Service Pack 2 or Service Pack 3 Microsoft Windows Vista 32-bit Business, Ultimate or Enterprise Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional WorkPlace Tech Tool release 5.8.7 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.9.1 to 5.9.4 are certified to run on the following versions of Microsoft Windows: Microsoft Windows 7   32-bit Professional Microsoft Windows 7   64-bit Professional Microsoft Windows 8.1   32-bit Pro or Enterprise Microsoft Windows 8.1   64-bit Pro or Enterprise Microsoft Windows 10    32-bit Professional Microsoft Windows 10    64-bit Professional Microsoft Windows Server 2012   64-bit WorkPlace Tech Tool release 5.10.0 to 5.10.x is certified to run on the same as WorkPlace Tech 5.9.x and the following versions of Microsoft Windows: Microsoft Windows Server 2016 64-bit Microsoft Windows Server 2019 64-bit Microsoft Windows Server 2022 64-bit Microsoft Visio Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8 32-bit Pro or Enterprise Microsoft Windows 8 64-bit Pro or Enterprise Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.8 through 5.8.6 require one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WPT 5.8.0, WPT 5.8.1, no known issues with WPT 5.8.2 through 5.8.5) Microsoft Office Visio 2007 with Service Pack 1 or Service Pack 2 Microsoft Office Visio 2010 with or without Service Pack 1 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.8.7 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2007 with Service Pack 3 Microsoft Office Visio 2010 with Service Pack 2 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.9.1 through 5.9.4 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2010 with Service Pack 2 Microsoft Office Visio 2013 with Service Pack 1 Microsoft Office Visio 2016 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool releases 5.10.0 through 5.10.x requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2016 Microsoft Office Visio 2019 Microsoft Office Visio 2021 Microsoft Office Visio Office 365 Subscription Plans 2 Note: Workplace Tech Tool 5.10.0 and future releases will require .NET Framework 4.8 to support Open LDV 5.1 which is included in the installer.  .NET Framework 3.5 Sp1 is no longer required.   Follow the instructions in the article link for the security updates required. Workplace Tech 5.10.x and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office For the Visio requirements for earlier versions of the WorkPlace Tech Tool software, see What versions of Visio are required for WorkPlace Tech?.

Issue WPT and WPTE require certain Microsoft Security updates for Visio and for Office running on the host machines. Issues currently observed: Different and various functions in the fluent ribbon do not work or the ribbon does not appear. The following error "Application compile failure during save operation" is seen when saving/compiling an application in WorkPlace Tech Editor Product Line EcoStruxure Building Operation, TAC IA Series Environment Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause Interoperability of Visio and Office can cause problems with Workplace Tech and Workplace Tech Editor if these MS16-70 updates are not applied.  If the Office / Visio product is "Click to Run" the software has not been updated to the latest version. Resolution Install the updates from Microsoft Update Catalog To use the catalog, copy and paste the KB number into the "search".  Always select the 32-bit version of the update. Visio 2010 32 bit KB3114872                Office 2010  KB3115198 select 32 bit  Visio 2013 32 bit KB3115020                Office 2013  KB3115173 select 32 bit  Visio 2016/2019 32 bit KB3115041       Office 2016  KB3115144 select 32 bit Visio 2016/2019 32 bit KB4484333 NOTE:  If the Visio or Office is "Click to Run" (subscription such as Office 365, Plan 2) rather than from a Microsoft Office .msi, the product should be upgraded by using the Update Options feature If you try and install the KB/.msi install patches, you will get this message

Issue Creating an Extended Trend Log for b3 (Infinet i1/i2) Point and Value Logs Product Line EcoStruxure Building Operation Environment b3 BACnet Controller Infinet i1 & i2 Controller Building Operation Automation Server, AS, ASP, ASB Extended Trend Logs (ETLs) Cause Using an extended trend log to store log records for long periods of time. The extended trend log is often saved on a higher-level server with more storage capacity. This extra storage capacity enables the server to store more records before overwriting the old ones. For more information, see WebHelp. Configure extended trend logs for b3/i1/i2 devices the same way as configuring extended trend logs in other Building Operation devices. There is one difference, however. do not use smart logs when configuring extended trend logs in b3 BACnet devices. Instead of using smart logs, use the Maximum Transfer Interval property to specify the transfer interval. Resolution In Listview, select the b3/Infinet Object (point or value), click Properties/Advanced Multiply the "Log records" by the "Log interval" to calculate the maximum transfer interval. The "maximum transfer interval" is the frequency at which the extended trend log will transfer log records from the b3/Infinet Object before any entries in the b3/Infinet controller log are overwritten Right click the object, choose New then "Extended Trend Log" In the Create Object box, set Smart Log to False, Set the "Maximum transfer interval" to less than that calculated above (2) Click Create For Infinet systems always refer to Infinet under the hood otherwise the creation is as the Webhelp for creating BACnet B3 Logs In theory it would be possible to create the Extended Trend Log in an ES (where there is more storage capacity), but this could introduce other timing and bandwidth issues, so it is usually best to keep the first Extended Trend Log in the AS, then extend this to a second Extended Trend Log in the ES, as shown. (the second ETL in the ES scan use smart logging in the usual way) If significant logging is required then External Log Storage should be considered. (the B3 or i1/i2 logs still need to be collected via Extended Trend Logs)    

Issue Capturing packets from Zigbee Standard Security Network shows packets marked Bad FCS or Encrypted Payload Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Room Controller Cause Zigbee Standard Security Networks implement multiple keys to encrypt data for the Zigbee Network and each device Resolution This resolution assumes you have a Zigbee adapter that can capture packets in Wireshark.   Ensure zigbee_pc_keys are available in each profile you are going to use to analyze the Zigbee packets. The file location is generally: %AppData%\Roaming\Wireshark\profiles\<Profile Name>\zigbee_pc_keys   Open Wireshark and configure the Zigbee adapter NOTE: Please substitute your adapter name if not using the TI CC2531 adapter. Open Wireshark Click the gear next to the 'TI CC2531 802.15.4 packet sniffer' Select the known channel (11-26) and click Save Click on 'TI CC2531 802.15.4 packet sniffer' to start capturing Update formatting to resolve Bad FCS packets Go to Edit -> Preferences -> Protocols Select IEEE 802.15.4 Depending on your Wireshark version, check or "TI CC24XX FCS Format" or set FCS format = "TI CC24xx metadata" Add default link key for Zigbee Alliance Go to Edit -> Preferences -> Protocols Select ZigBee Set Security Level = AES-128 Encryption, 32-bit Integrity Protection Click Edit next to Pre-configured Keys Click + and Enter Wireshark Key from below, Byte Order = Normal, and Label Enter the Zigbee Alliance Default Link Key Key = 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39 Key Value = 5A6967426565416C6C69616E63653039 Remove colons (:) for entry into Wireshark ByteOrder = Normal Label = ZigbeeAlliance09 Find and add Standard Network Key Ensure you have configured the default transport key (above). Use this display filter to find the request Key exchange:   zbee.sec.decryption_key Find Standard Network Key Look in the Info column for the Transport Key and select it Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Standard Network Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED:   Use Descriptive label because you will have   Network Key per Zigbee Network, so includes Device, PAN ID, and NetworkKey, ie ASP087_12345_NetworkKey Find and add Trust Center Link Key PER device Ensure the following are configured: formatting, transport key, and Standard Network Key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Since this is per device, one can include the Network Address for the device. Example: If the network address of the device is 0x2074, the display filter would be: zbee.sec.decryption_key and zbee_nwk.addr == 0x2074 Find Trust Center Link Key per device Using the Info field, find the pair of Request Key and Transport Key. The Request Key will have Source = Device Network Address, and the Transport Key will have the Destination = Device Network Address. Click on the Transport Key packet Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Trust Center Link Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED:   Use a Descriptive label because you will have a Key per device, so includes Device, Network Address, and Trust Center Link Key, ie TH907-01_0x2074_TCLK

Issue What diagnostic information is available within Niagara that can be sent to Product Support or acted on locally? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series Jace Cause Jace or Enterprise Server operating slow or specific problems are causing the need for debugging a station or platform Resolution There are several diagnostic tools available: Check the station Resource Manager Right-click on the station and select "Views - Station Summary" This will open up a resource monitor page where you can check CPU and memory usage.  The CPU should not be consistently above 80%.  Spiking is common as the process is executing and completing tasks.  There are other things easily referenced here also. Heap memory will vary as well.  It can slowly increase until a garbage collection cycle releases unused heap back to the pool.  You should never use more than 75% of the total available heap memory. Heap Memory is primarily used by station modules and java program objects, so if the memory usage is high, these 2 might be the main reasons Engine Hogs   Right-click on the station, and select "Spy". From the main view, click on "sysManagers". Click "engineManager" and then scroll down to find "Engine Hogs". Clicking Engine Hogs will open a list of the main components of the station and a column on the right-hand side will display the average execution time of the component. Review the top 10 or so and see if any are taking an extraordinary amount of time.  This can help to locate improperly executing objects. Driver Poll Rates Drivers that are based on polling data, like BACnet when COV is not enabled, or Modbus constantly run commands to read data based on the fast, normal, and slow configured rates.  Open the Poll Service under the network the points are being polled on. Looking at the property sheet of the driver, it is important to verify that the cycle time (1) for each rate (fast/normal/slow) is always equal to, or below the actual time configured (2) for that rate. The defaults are 1 second for Fast Cycle Time, 5 seconds for the Normal Cycle Time and 30 seconds for the Slow Cycle Time. Seeing a longer cycle time is usually an indication that the network is saturated with commands and may cause the Jace/Niagara controller to be slow with heavy use of controller resources.  There are several ways to correct this: changing the polling rate spreading the number of objects being polled at each rate, etc. In this example, all points (3) are in the "normal" bucket. Application Director console The "Application Director" (under "Platform") shows a live console output.  Open it by clicking the option under the platform Copy the content of the Application Director, or "stream to file" to send the content to support. It will be essential to help the support engineer to understand the problems in the station.  Add more debug information to the Application Director console You can add more granularity to the messages in the Application Director for a deeper look into possible issues. This can be accomplished in 2 different ways: Right-click on the station, and select "Spy". Then, select "logSetup" on the main view From the list that appears, you can scroll and find appropriate topics to log and you can select at what level you want the information to appear.  This will add traffic to the application Director window so be careful how "fine" and how many logs you enable.  It might be good to consult with support before enabling these logs. example; bacnet.debug/finest if you select this box. Debug Service   Select the "DebugService" from the station "Services" In the Log Category, type a few letters of the topic and scroll to find what you are interested in logging From the pulldown menu, determine the granularity of the log Click the plus Click "Save" Setting this logging and streaming the output to a file will allow information to be sent to support for better diagnostics if required.  Remember to set this logging back to "Default" when done so the Application Director is not overwhelmed with information when you are only trying to view normal station activity.

Issue When configuring Basic Elevator Control there is no option in the Elevator car for the Credential Type for the Elevator car to use. Product Line EcoStruxure Security Expert Environment Security Expert SP-C, SP-RDM2, SP-I16, SP-O8, SP-IO84 Cause The AN 248 Security Expert - Configuring Basic Elevator Control - Integration Guide does not describe how to handle credential types as the Authentication mode when configuring Elevator cars. For card formats other than the default selection in the Door record, Credential Types are used with Door Types to define the credential to be used to authenticate at that door. When configuring Elevator control however, the Elevator car record does not have a Door Type field to set the relevant Credential Type to use. Resolution In the Elevator Car record set the Authentication mode field to "<not set>". This will process as normal if the user has a valid credential based on the Reader Expander Reader Port configuration. The Reader Expander Port is set to "Custom Credential" and "Elevator" for access. The Elevator car reader will go through the list of Credential Types programmed in the controller and match the Bit Stream of the card read to the first Credential Type that fits. If there were three Credential Types programmed as below; 32 Bit 37 Bit 26 Bit Badging a 26 bit card would use the first 26 bit format found in the list which would be Credential Type number three. Typically this would work fine in most cases however some additional allowances will need to be made if there are multiple credentials with the same number of bits. If there were  multiple 32 bit formats; ESMI 32 Bit Custom 32 Bit For Elevators The system will use the first matching format which would be the ESMI 32 bit, this would result in your elevator processing the wrong format and therefore potentially not granting access. To resolve this the Credential Types would need to be programmed so that the first credential is the one the elevator needs to use. Custom 32 Bit For Elevators ESMI 32 Bit

Issue How to add a third party LonWorks device? How to create a LonWorks device template? Why is a device template not available after import? Product Line EcoStruxure Building Operation Environment Building Operation version 1.8 and above Building Operation WorkStation Cause In order to add a third party device, need to create a device template (XIF file) for it. Device templates must be created in the server that the controller will created under. If a third party controller is going to be added to an AS-P that is associated to an ES, then the template must be created when logged into the AS-P directly. Resolution To import a device template   Log in to the SmartStruxure Server in which the device will be added underneath. In Workstation, Right mouse click on the Server and select LonWorks then import device Template. In the XIF file box, select the XIF file to import. Click Import. In the Template Name field, type a name for the template. Click OK. In the Import Device Template box, click Close. Now, this third party device template will be listed when adding a device into the LonWorks network. Note: If the device template refers to NVT or CPTs not on your system, you will be prompted to import necessary resource files. When the resource files have been imported, the device template import restarts. When finished, the device template is imported and available when creating a new device.

Issue Using Modbus TCP and Modbus Serial (EIA/TIA-485) on an AS together? Product Line EcoStruxure Building Operation. Environment AS-P Modbus TPC Modbus Serial Cause Communicating with two third party devices simultaneously. Both are using the Modbus communication protocol. One is Modbus TCP, the other Modbus Serial (EIA/TIA-485). Resolution Modbus TCP and Modbus Serial (EIA/TIA-485) can be used together on an AS-P. This configuration is supported and has been used many times.

Issue Can SLPSXC2 CO2 sensor calibration be used with both methods (ABC standard and Fresh Air process) at the same time? Product Line Field Devices. Environment Building Operation SmartX Living Space Sensor. Cause SLPSXC2 CO2 can be calibrated using two different methods. Automatic Baseline Calibration(ABC) The ABC algorithm constantly keeps track of the sensor’s lowest reading over a pre-configured time interval and slowly corrects for any long-term drift detected when compared to the expected fresh air value of 400 ppm. ABC calibration is enabled/disabled through coil 4 (invoke = enable ABC). Manual Calibration Coil 11 triggers the manual calibration (FRC 400ppm) => this will tell the sensor that the current level of CO2 should be interpreted as 400ppm. When setting this register to 1, it automatically goes back to 0 a couple of seconds later. Setting Coil 11 to value 1 is the same as pressing the calibration button. Resolution The both methods of calibration can be used simultaneously since one method is for correcting drift over time (1 week intervals), the other is a manually executed reset.   The only error would come if the unit was exposed to high CO2 concentrations at night, inducing abnormal averages. If ABC is disabled, manual calibration would need to be performed more frequently.

Issue What is the latest firmware version for the MNL-800? Product Line TAC IA Series Environment I/A MNL-800 Cause Upgrade the device to the latest firmware. Resolution The latest firmware version is 2.0 (p/n MNEA-810-200), which was released in January 2004. See Announcement 04-01 listing the features of this version. Announcement regarding the end of commercialization of this part 

Issue There is no built-in Credential Type for the HID 37-Bit badge with no site code (H10302). Product Line Security Expert Environment Security Expert Server Access Card Format Cause Security Expert does not have the HID 37-Bit badge (H10302) with no site code as a built-in available Credential Type. Resolution 1) In the Security Expert Client, select Sites -> Credential Types 2) Create a new Credential Type with a name of your choosing. 3) Under Configuration, select the Format as Wiegand. 4) In the field labeled Wiegand or TLV Format, enter the following exactly as written:                                                        A,FACILITY,0,MSB,BIN__B,CARD,35,MSB,BIN__PBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBP_EXXXXXXXXXXXXXXXXXX.................._..................XXXXXXXXXXXXXXXXXXO 5) Save   NOTE: This article assumes that the reader is familiar with creating and deploying Custom Credentials, If this is not the case, then please reference the Complex Transition Programming section of the Transitioning Continuum Sites to Security Expert - Transition Guide

Issue How to populate customized information on the SpaceLogic Sensor display Product Line EcoStruxure Building Operation Environment SpaceLogic Living Space Sensor Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation Workstation Cause Additional information required on how to customize information to be displayed on the SpaceLogic sensor Resolution Note: This feature may not work in controller FW V4.00.x, due to know issue Custom value text is not displayed and/or updated on the SmartX sensor device, in this case please upgrade controller firmware to V5.00.1 or higher. Before starting, make sure the Integrator Menu icon and the custom information page have been activated: The Integrator Menu icon can be configured under "SmartX Sensor Device/ Display/ Button and Scene configuration" as shown in the screenshot below: Turn on "Allow custom information page" under "SmartX Sensor Device/ Display /Advanced" tab. By doing this, the custom information page is created under the Integrator menu icon of SmartX Sensor Display:        To show how to add custom information to the custom information page of SmartX Sensor display, create a sample script program, where DI1 is a digital input and Status1 is a string output. numeric input DI1 String output Status1 If DI1 = on then Status1="running" Else Status1="not running"​   In this program, when DI1 is on, the Status1 gets the string value of “Running”, otherwise the Status1 gets the string value of “Not Running”. DI1 is bound to a Digital Value (Green Arrows) under the Application folder and Status1 is bound to the CustomValueText1 (Red Arrows) as shown below:   Open the Watch pane, under the View tab, and add Digital Value and CustomValueText1 (access it through the “SmartX Sensor Device/ Display/ Basic” tab) to it.  When the Digital Value is Active the Custom value text 1 shows “Running”. On the SmartX Sensor, navigate to the custom page through the Integrator menu icon, this will show the “Running” string . Likewise the “Not Running” string would be populated on the SmartX Sensor custom information page screen when the Digital Value is Inactive.  

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 A large number of alarms have accumulated and need to be acknowledged at one time. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause A large number of unacknowledged alarms have been allowed to build up until the number is too large to acknowledge them manually one at a time. Resolution To acknowledge the alarms all at once, please raise a Support Case with your local Customer Care Centre and Product Support can assist with a ' one time'   SQL Query direct to the Security Expert Database. See Browsing slow in Security Expert Client for some methods to minimize unacknowledged alarms accumulating so rapidly in the database.

Issue Browsing between different records in the Security Expert Client is slow. It takes a longer than normal amount of time to see records update. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause There are a large number of unacknowledged alarms being stored in the SecurityExpertEvents database. When the Security Expert Client starts up it will process all of these unacknowledged alarms which can impact browsing the database. Resolution To resolve the immediate problem: 1. Reduce the size of the SecurityExpertEvents database by reducing the overall number of events that will be stored. Setting up automatic event purging and backup helps keep this in check. Under Global | Global Settings | General change the Purge Events older than from the default setting of "Never" to another value from the drop down menu. To backup these events before being purged, ensure the Generate Differential Events Backup option is checked. This is the default setting. 2. If there are more alarms to be acknowledged than can be done manually then contact Product Support mentioning this Knowledge Base Article. Remote access to the site and SQL Server will be required.   To minimize this from happening again: 1. Reduce the amount of events that are setup as alarms. Remove any alarms that are setup for All Events and review any configured alarms to ensure those events are required to be generating alarms. Double check all Inputs and Trouble Inputs to see if they have the Log to Event Buffer option enabled. Not all inputs will require this for normal operation and in some cases having this enabled can result in a large number of unwanted events being logged. This, in addition to an alarm setup to monitor the All Events event filter, is a recipe for disaster resulting in a large number of alarms being generated in a short amount of time. 2. Ensure that a large number of unacknowledged alarms are not allowed to build up over time. Alarms are not able to automatically acknowledged and will stay in the active alarms list until an operator acknowledges them. Operators need to acknowledge alarms on a regular basis. Note that it is possible to batch acknowledge blocks of alarms at one time in the Security Expert Client by doing a multiple selection then right-click acknowledge alarm. Note: If your system has already built up a large number of unacknowledged alarms and you want to quickly acknowledge them all at once to get back to a manageable starting point, then please raise a Support Case with your local Customer Care Centre and Product Support can assist in doing this with a 'one time' SQL Query direct to the Security Expert Database.

Issue Model and Device Name from SLP sensor via Modbus RTU Product Line EcoStruxure Building Operation Environment Automation Server AS, ASP, ASB SpaceLogic Sensor SLP Cause The Model, Device Name and Serial number are 64bit values and need to be collected with a single query to get the correct data. Script and Function Block programs can not manipulate 64 bit values - Model Register 9, 64bit, read only, Read Function Code 4 - Serial number Register 42, 64bit, read only, Read Function Code 4 - Device Name Register 42, 64bit, read/write, Read Function Code 3 (currently the documentation shows these as 32bit) Resolution A simple way to collect the Model and Serial Number is shown below This involves creating a Modbus Poll Group for the 4x 16bit parts of the 64bit Modbus Register. This will effectively query the 4 registers in a single packet, ensuring the correct data is collected. The same method can be used to collect the Device Name, but this value cannot be written using the same Group, as block/group write is not supported in EBO Create a Modbus Poll group containing the four 16bit registers, then create a String variable Then create a script to convert to ASCII characters

Issue How to setup and configure External Log Storage in EcoStruxure Building Operation (EBO) when using Microsoft SQL Server as external log storage. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Enterprise Server Building Operation Enterprise Central Cause You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature. The External Log Storage feature uses an external database administered by either a combination of TimescaleDB and PostgreSQL software, or Microsoft SQL server. Resolution Please see video which will show how to: Create a database and user account in Microsoft SQL (MSSQL) Server using Microsoft Server Management Studio. Configure the External Log storage connection between EBO and MSSQL server in EBO. The script used when creating the database in the MSSQL server can be found here: External Log Storage - MSSQL Installation Script v5.0 - EcoStruxure Building  The script used when adding the user to the database and give the user the correct rights level is attached to this Knowledge Base article.  

  Issue After transitioning TAC INET Access to Security Expert, SP-C health status shows the message "Ring-loop failure at reader expander".   Product Line EcoStruxure Security Expert, TAC INET Environment  Security Expert SP-C   TAC INET Access Control Cause This message indicates that the ring-loop connection is not made.  For the ring-loop connection, the opposite end of the INET subLAN must be connected to Reader 2 on the SP-C. Resolution If an INET subLAN loop is not used, then  this message can be ignored. If an INET subLAN loop is used then this message indicates a break in the ring-loop.    1. Reference Guide I/NET Access Control Transition to EcoStruxure™ Security Expert (Hardware            Guidelines for Transitioning from I/NET Page 23)

Issue With the same time interval as the trend log, the traffic on the LonWorks network increases for a short period. This can be seen by a spike in the LPA log when viewing the bandwidth. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Lonworks Cause The LonWorks traffic increases with the same time interval as the trend log. Resolution To ensure we could log values in the trend log from a LonWorks device, a subscription is set up about 30 seconds before the value should be logged. After the value is logged, the subscription is removed until the next log interval. A good solution to flatten a spike caused by this issue is to stagger the times of the LonWorks trend logs. This will ensure the subscription for all the logs do not happen at the same time.

Issue When comparing values of Modbus registers within WorkStation and Modscan the values do not match. Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server. Building Operation Automation Server. Cause The third-party Modbus device does not support single register requests. Modscan was set to poll 10 registers as a group poll and giving the correct responses. The Modbus request in the Enterprise Server or Automation Server was polling individual register one at a time. This resulted in incorrect responses from the third party device Resolution Add a Modbus register group to the Server then add the Modbus points to this group. This will cause the Server to poll multiple registers in 1 request and get the correct response from the third party Modbus device.   For more information on Modbus grouping refer to the EBO Webhelp Modbus Register Groups topic

Issue How to read individual bits from a Modbus Holding Register that holds a 16-Bit Word and represent each Bit as a separate Digital point Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B) Modbus TCP/IP Modbus RTU (RS485) Cause There is a requirement for a Modbus Holding Register that is a 16-bit unsigned value, each bit represents a digital state in the Modbus device and to replicate this as 16 separate digital states in EBO. The 16-bit unsigned value is an integer with a range of 0 to 65,535 and needs to be converted into 16 digital values. Resolution Use a Modbus Digital Input point for each bit required. Each object will be configured to read the same Modbus register address, but with a different bitmask value applied prior to evaluating the value. For example: Read Modbus Holding Register 40123 with a value of 32769 (16-bit unsigned) and decode bits 0, 8, and 15 as three separate Digital points Since the actual Value of 32769 being read at address 40123 is shown in Binary as 1000000000000001 it can be seen that Bit 0 and Bit 15 should return TRUE while Bit 8 should return FALSE Configure each point as follows: Modbus Digital Input Point 40123 bit 0 Register number 123 Register type 16 bit unsigned Read function code 03 Bit mask - enable only Bit 0   Modbus Digital Input Point 40123 bit 8 Register number 123 Register type 16 bit unsigned Read function code 03 Bit mask - enable only Bit 8   Modbus Digital Input Point 40123 bit 15 Register number 123 Register type 16 bit unsigned Read function code 03 Bit mask - enable only Bit 15   Additional information can be found in the EcoStruxure Building Operation - Technical Reference Guide - Search for Bitmask.   If you need to break this bit information out for programming this can be done with a FB application and just binding the full 16 bits to the FB as shown here.