Building Automation Knowledge Base

Issue How to use multiple monitors when working in Building Operation WorkStation. Product Line EcoStruxure Building Operation Environment Multiple Monitors Building Operation WorkStation Cause Need to understand how to utilize multiple monitors with Building Operation WorkStation available as an option from version 1.4.1 and above. Resolution Building Operation Workstation provides the ability to place any pane in WorkStation on a separate monitor including the alarm, watch, and event windows. This can be a very productive feature for a building front-end computer or even in the engineering stages of the system. Versions 1.4.1 and above The multi-monitor display support in WorkStation includes the ability to save and reset workspace layouts. Individual users at a given WorkStation can modify the workspace layout and save it such that whenever that user logs in using that PC the workspace will revert to their modified layout. Included in the modified layout is the ability to move panes to a second monitor and have those panes positioned in the same way whenever that user logs in with that PC. The user can revert to the default layout at any time. How to move WorkStation panes to a second monitor Click, hold and drag the title bar (1) of any pane in WorkStation that is to be moved to another monitor. The pane will appear as a purple shadow (2).  Drag the pane to another monitor, release and re-size as necessary (3).    How to save the workspace layout for the current user At the top of the WorkStation window, click on the View menu (1) and select "Save workspace layout" (2).  When the same user logs out and then logs back in again, the layout will remain the same. To return the layout to the default, go to the View menu and select "Reset workspace layout". Note: When working with a two-monitor layout using a laptop on a docking station, if the laptop is undocked it will no longer be possible to see the panes that were moved to the second monitor.  To correct this go to the View menu and select "Reset workspace layout".     Versions 1.4.0 and prior It is possible to use WorkStation and WebStation on multiple monitors in prior releases: Launch multiple instances of the clients and run them on different monitors. In WorkStation, “Tear off” view windows and position on different monitors. Manual positioning of windows is needed.  To get more automatic behavior at start-up or logon, it is better to run with multiple computers with separate displays or see if a 3rd party window positioning utility can help.

Issue Running Bomgar Remote Support Client from Linux for support from Product Support Services Product Line EcoStruxure Building Operation Environment Building Operation Edge Server - Standard Cause Bomgar session downloads Bomgar-scc-[long string of characters].desktop file and need to run to connect with a Product Support Services agent. Resolution The file needs to be granted permission to execute and then run. Open browser on Linux OS for website: https://seconnect.se.com  Enter the 7-digit Session Key and press SUBMIT button. After saving the client to the Downloads folder, right-click on the bomgar-scc-[long string of characters].desktop file, then click Properties.  Click on the Permissions tab, then check the checkbox next to Execute to Allow executing file as program.  Open Terminal, then type "sh " (without quotes and not forgetting a space), then drag the file to the Terminal window, then press Enter. The full command will look similar to this image.  Once the executable runs, this image will appear on the screen as the full session begins.  Click Allow to let the agent view and control your computer. 

Issue Servers not visible after upgrade due to permission change Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The Domain Local Group " Reports Administrators" is removed when an ES is upgraded to v4.0 or greater. This Group is automatically deleted during the upgrade because Report Server is not supported in v4.0 or greater. It is possible for local users to be selected as User Group members of " Reports Administrators", so the permissions for these users may change after the upgrade. This is not good practice, only the Reports Server login user should be part of the " Reports Administrators" Group " After the upgrade the Group "Reports Administrators" is removed and the Servers are not accessible Resolution Any users that were part of Group "Reports Administrators" should be reassessed and their permissions corrected 

Issue When trying to activate an embedded license on a SmartX Server using Device Administrator, the activation fails with the following error message: Failure (error) received when reclaiming an embedded license on an Automation Server   "Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created." Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) All of the above v. 3.0 or higher Cause The cause of this problem is that the trusted storage, i.e., the embedded license database on the SmartX server, is corrupt. The embedded licensing framework undertakes internal checking and if it determines there is a consistency problem, it will consider the trusted storage to be corrupt. This means that no operations to the trusted storage, such as activating licenses, will succeed. At the time of writing, it is unclear why the consistency problems happen. In the server log, you may also observe the following error message: 10:08:06: Executing licensing command 10:08:06: Executing embedded operation: Activate ActivationID: ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX 10:08:11: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Capability request could not be created 10:08:11: Licensing command completed 10:08:11: Activating licenses failed (Real Activation ID replaced with ACT-XXXXXXXXXX-XXXXXX-XXXXXXXX)   Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the steps shown in the resolution. Please attempt all steps before contacting support.   Resolution   Building Operation 2022 v4.0.4  and above Upgrading to the above versions will now resolve the trusted storage corruption and inhibit license activation. Building Operation 3.2.X and up to EBO 2022 v4.0.3   Note: Although this process is specific to the "Capability request could not be created" error, similar errors can be corrected by following the below steps. Please attempt all steps before contacting support.    Clear trusted storage within the server Using Device Administrator select the affected server and Open a PuTTY Console An alternative way of connecting to the server is to use WinSCP. Use File protocol SCP and the admin user. When connected, follow the instructions as per the Word Document also attached below Warm or Cold Start the AS-P If failures still occur, attempt the Offline Activation of Licenses Workflow; The key step is that the license is activated offline and then transferred to the server in two different steps, allowing the license activation process to complete successfully.   Warm or Cold Start the AS-P If there are still failures with either of these options, send a support request through your local support center including the errors seen with each activation attempt.     Building Operation version lower than 3.2.X   If the embedded license is a Client license, there is no need to activate the license. Install the EBO Hotfix 3.0.3.2001 (CP1) or later. This will remove the enforcement of SmartX server Clients in the licensing system. See also article Embedded WebStaion client license when logging directly into a SmartX server no longer needed. Other licenses like SmartDrivers, SNMP, and Personal Dashboards may still need to be activated. Contact your local support center to fix this problem.

Issue Enterprise Server ES crash Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The ES/EC runs on a Windows platform and there are circumstances that can lead to a single crash or multiple crashes leaving the ES/EC not running Background - The ES service is usually running. The service can be seen below under the Windows services and via "Building Operation Software Administrator"  The ES v4.0 has crashed and will not restart. The "Building Operation x.x Connect Agent" collects any core dumps and packages them, so they can be quickly analyzed. It also checks if an ES is registered and online, then uploads the core dump files for automatic analysis. If the site is not registered or is offline, then these files are stored locally at %ProgramData%\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise [Server|Central]\db\Crash information (default for v4.0 "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\db\Crash information") The "Building Operation x.x Connect Agent" is a Windows Service and installed with the ES, the service should be left to run continually. If it is not running during an ES crash, the core dump may still get created, but does not get packaged up in a way that can be easily analyzed. Each packed crash dump file may look like "ES_ES_MYCOMPUTER_20221104T121314Z.zip" and likely be between 40MB and 200MB in size. The individual core dump will look like "server_20230314_132853__r4.0.3.176.dmp", but is very time consuming to analyze, without the other associated files Resolution Following a crash,the EC/ES will usually restart and operate correctly, however in some cases the EBO database or install file structure may be damaged and the EC/ES may fail to restart correctly EC/ES has crashed and is now running correctly Send the following information to Support - All core dumps from the "\db\Crash information" folder - All data from the "\db\logs" folder - Ideally a full backup of the ES (with history), always zip before sending to Support If the "Crash information" folder is empty, then check the "Building Operation x.x Connect Agent" is running. It is possible the core dumps have already been uploaded and analyzed automatically EC/ES has crashed, tried to restart but just stops again. (as seen in the first screen shot, "The server has made too many unsuccessful attempts to start..." is seen It is important to gather all the data as stated above, but also collected the EC/ES and AS backups from "\db_backup" It can be useful to get full copy of the files in "/db" Ideally the EC/ES is not critical to the operation of a site, but it can still cause a big problem. Checking the Trace and System logs may give a clue to the problem, e.g. a lack of disk space, but often there are only a few options   Collect the files above, then wait for a reply from support. Please state if the EC/ES is stopped and a resolution is being sort. Reinstall the EC/ES at the same version and choose repair current version, or upgrade to a newer CP Fix version or maintenance version. Uninstall the EC/ES, then re-install the same version with an empty database, then restore the last good backup to the ES. If option 2 or 3 is used, it is still important to log a case with support, so the crash can be investigated. The backup can be checked for errors using the XBK Analyzer.

Issue While editing a graphic, the editors components categories and menu options are too small to be used. This happens when Windows display scaling is not set to 100%. Product Line EcoStruxure Building Operation Environment Graphics Editor High Resolution monitor (4K) Scaling Cause An issue has been identified with how the default scaling used by Windows affects the Graphics Editor in EcoStruxure Building Operation 2.0 and later. Resolution Follow the steps below to work around the problem Update Windows with the latest available updates Update .NET Framework to latest version Change the compatibility settings of the Graphics Editor as outlined below   Open the Graphics Editor application file location   Open the properties for the Graphics Editor application   Override the DPI scaling 

Issue Is there a quick reference I can search to find out what features are included in a particular license When manually adding my Product during offline embedded license workflow, how do I know which Features is included and in what quantity?  Product Line EcoStruxure Building Operation Environment Building Operation EBO 2022 v4.03 and lower  Embedded Offline Licensing Offline Activation of Licenses Workflow Cause Currently, no information lists features for each Product name listed in the Part Number Summary for EBO 2022.  A documentation defect (QC 49762) has been raised, which should resolve this.  This article has been created to assist somewhat during this process while waiting for this to be corrected.  The recommendation, if possible, is to perform license activation online to avoid having to enter this detail.   Resolution Important Note: This information is no longer valid for EBO 2022 (Maintenance Release 4.0.4) and EBO 2023 and greater.  The details below are still provided for reference only and are not needed for these later versions.   Attached are two documents that provide version 3.0 and 4.0 License details.  The documents contain all searchable details, including: Product Name Features Part Numbers     Additional details required for Device Administrator "Feature Name" offline entry:   SpaceLogic Server license details Feature Name (seen in Device Admin) License name (seen in Features document) Description / Comments Automation Server server.as.base   SmartDrivers smartdriver.license   SNMP Notifications server.alarms.snmp   Personal Dashboard client.dashboard   TimescaleDB server.timescale   MQTT Publish/Subscribe server.mqtt.rw Enables EBO, as MQTT Client, to publish data on an MQTT Broker and to subscribe to the same data. Serial Modbus server.modbus.rtu Allows SmartX server serial communication - Modbus RTU Serial MS/TP server.bacnet.mstp Allows SmartX server serial communication - MSTP ES Connection server.connect.to.es Allows SmartX server to be hosted by an Enterprise Server Server I/O server.io Allows SmartX server to use IO Field Devices server.device.as Allows SmartX server to host one field device SAML Authentication server.as.auth.saml   Zoning client.zoning Enables use of zoning tools BACnet IP server.bacnet.ip Allows SmartX Server to communicate using BACnet IP Software Assurance software.assurance         Feature Name (Automatically included with bundle licenses)   client.webstation Allows Webstation to log on to an AS   server.cloud.customer Cloud connectivity - Checked by Cloud SMS (Production)   server.as.scalable Included in the license that allows SpaceLogic servers upgrades. i.e. Standalone to Standard etc.   Example: Product Name: ASP-NL Bundle upgrade - Full to ASP Full    Search the document for the product name in the attached document. In this case, the version 4 document.  Below is the result seen in the document: From this, the associated Features and Quantity are shown. In Device Administrator, then add the respective features and quantities when adding the product manually to the Entitlement. Use the above table to correlate between Feature Name and License Name. The example shown below:  

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 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 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.  

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.

Issue When looking in the EcoStruxure Building Operation Architectural Guidelines for the maximum number of Xenta and LonWorks devices per server, is a TAC Xenta I/O module placed under a TAC Xenta 300/400 counted as a LonWorks device? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The SmartX Server or Enterprise Server doesn't know that the TAC Xenta I/O module exists if it is placed under a TAC Xenta 300/400. The SmartX Server or Enterprise Server only communicates with the TAC Xenta 300/400 and not the TAC Xenta I/O modules under it. Resolution The TAC Xenta I/O module does not count as a LonWorks device in the EcoStruxure Building Operation Architectural Guidelines if placed under a TAC Xenta 300/400. This also means a TAC Xenta I/O placed under a TAC Xenta 300/400 does not count as a  Hosted Node or Connected Product.

Issue Need to configure SMTP settings to use a Google SMTP server Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no SMTP settings configured by default Resolution Note: As of May 30, 2022 please also consult Less secure apps & your Google Account 

Issue How to decrease the amount of LonWorks network traffic by using throttling. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause EBO servers could generate a lot of communication on the LonWorks Network. Throttling could be activated to decrease the amount of traffic. Resolution To decrease the amount of LonWorks Network traffic, it is possible to activate Basic Bandwidth Throttling. The setting is found under the Advanced tab for the properties for the Lonworks Local FT-10 Interface.   Picture showing default settings.   This video will show how to activate Basic Bandwidth Throttling and what impact this could have on the amount of LonWorks Network traffic.   At the end of this session you will be able to: Set up Basic Bandwith Throttling for the LonWorks network  

Issue Checking if a port is open Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution It is possible to check if a port is open in a network by issuing the Telnet command. Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet. If a port is open, a blank screen will be seen after issuing the command: telnet [domainname or ip] [port] where [domainname or ip] is the domain name or IP address of the server being checked [port] is the port number the server application is listening on For example: telnet 192.168.0.20 9001 (to a closed port would display a connect failed message)   telnet 192.168.0.20 9003 (to an open port would display a blank screen)   To exit the Telnet session, type Ctrl + ] and then type "quit".   For how to enable Telnet in Windows 7 please see Enable Telnet Client on a Windows 7 PC