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 Services for assistance. Issue User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue After successfully setting up KIOSK mode to automatically login in to WebStation another user wants to login through WebStation on the same PC. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Cause The GUEST account login URL used with KIOSK mode retains the last user logged in and the WebStation menu bars have been removed so that user cannot "logout". Any subsequent attempts to access the WebStation using the same browser result in being automatically logged in under the GUEST account. Resolution The "KIOSK" link that you create will login automatically with the GUEST account as long as the GUEST account has already been created in the ES/AS. This then must set the "last credentials" in IE for that website and any subsequent connections to that server, even to the direct login URL, result in automatically being logged in with those last credentials. One of the two options below should work to disable GUEST login depending on where your ES is located. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port while Building Operation Workstation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation Workstation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. To be prompted for a login: Disconnect the ES/AS with one of the options above. Then try to connect to the server page at "http:/localhost:444" (or your specific URL:Port). This results in a "this page can't be displayed" (or similar) message. Then start the service, or reconnect cable, and again attempt to connect to "http:/localhost:444". You should be presented with the login page. Do not try to open up the "KIOSK" URL or else this will again login with the GUEST account and you'll be back to square one. The next time you use the "KIOSK" URL it will automatically login with the GUEST account and this will again be used for subsequent logins until the above steps are repeated. Note1: This could result in loss of data while the Enterprise Server is stopped. Note2: Also see StruxureWare Building Operation Workstation Auto Login feature locked if encountering this issue with a Workstation.

Issue Unable to see EWS objects/points under an EcoStruxure Web Services interface Product Line EcoStruxure Building Operation Environment EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause An EWS License may be needed to allow your ES/AS to use EcoStruxure Web Services Resolution Purchase and install an EWS License if required.     Note: The EWS option is NOT required when using EWS to integrate between two Schneider Electric systems or services. Refer to PA-00349 for details.   This includes the new Smart Connector by Schneider Electric which does not require an EWS License but does require a Smart Connector License as usual

Issue How to transfer EBO 2022 or higher data to Azure IoT hub via MQTT protocol Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to configure EBO MQTT interface and Azure IoT Hub, so EBO can send MQTT messages to Azure MQTT IOT Hub. Resolution The following video will illustrate how to: Create Azure IoT hub and IoT device using Azure Portal Create IoT interface and Azure MQTT client in EBO Configure the MQTT connection Create and configure a data group Test the connection Things you need: EBO 2022 or later with valid MQTT license or demo license (Enterprise Server, AS-P or AS-B) valid Azure Subscription with possibility to use free account during testing. For each Azure subscription one IoT hub in the free tier can be created, refer to IoT Hub | Microsoft Azure Visual studio code to be used to test the connection between EBO and Azure IoT hub, can be download from: Visual Studio Code

Issue Automation / Enterprise Server configuration very slow Attempting to make any configuration changes in the AS such as creating a new point/value or modifying existing objects is extremely slow. Note: This applies to the ES as well although less of a problem since the ES has better resources than the AS. CPU usage as seen in the Status Information of the server is very high. (above 80%) Question marks are shown on many objects in the application folder of third party BACnet devices that have been uploaded to the AS Enterprise Server takes a long time to startup (15 minutes) before allowing users to log on with Workstation.  Deleting the BACnet Interface allows log on with 2 - 3 minutes on a restart. Product Line EcoStruxure Building Operation Environment Automation Server Enterprise Server BACnet Cause Uploaded BACnet devices contain unresolved references to notification class object(s) Resolution Ask for SE.SBO.ES-AS-1.5.0.1501-Hotfix. (SE.SBO.WS-1.4.1.16001-Hotfix for 1.4.1, there is no hot fix for versions before 1.4.1) After applying the hot fix the server should become responsive. The unresolved references can typically be cleaned up by creating a BACnet Notification object in the application folder of the third party BACnet device proxy that reside in SBO and manually setting the Instance ID to 0 (zero) NOTE: Cases have been seen where multiple notification class objects must be created using instance IDs 0,1,2,3,4 in order to clean up all the unresolved references. A few minutes after the notification class object with the proper instance ID is created the question marks should disappear from the icons and created notification class object will show up in the intrinsic alarm property as seen below.   If creating the notification class objects with the above instance IDs does not resolve all the references a backup of the server can be provided to PSS, a PSS/R&D engineer can look directly at the database to determine the proper instance IDs the unresolved references are looking for.

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 Locating and downloading latest images Product Line Satchwell Sigma Environment 3.46.57 3.46.66 3.46.80 3.46.89 3.46.100 3.46.104 3.46.105 3.46.106 3.46.107 3.46.108 3.46.110 3.46.111 3.46.131 Cause Identifying the correct image version for different hardware versions. Resolution Sigma UNC/ (V53) = Firmware 6b Sigma Firmware UNC596 6.b - Release note   Sigma UNC3 (ARM7) = firmware build 1.p.0 Sigma Firmware 1.p.0 UNC3 - Release note   UNC 532 V25 = Firmware 6b Sigma Firmware UNC532 6.b - Release Note   IC-Modbus = Firmware V5h IC-Modbus v5h Release Note   IC3 Modbus = Firmware1.n.2 IC3 Modbus - Release Note   IC SNP = Firmware 5d IC-SNP Integration Controller v5d for Sigma Rel 3 - Release Note   IC3 SNP = Firmware 1.g.1 Sigma 4.05 Firmware Supplement - Release Note (there is no release note specific to SNP Firmware 1g.1).   IC York = Firmware V3e - Not available to download. IC-York Integration Controller v3e for Sigma - Release Note   IC3 York = Firmware 1.d.0 IC3 York = Firmware 1.d.0 – Release Note   Sigma IC3 Unifact 1.d.0 – Firmware Sigma IC3 Unifact (RTC) - Release Note Sigma IC3 Unifact pro 5h – Firmware Sigma IC3 Unifact pro 5h - Release Note  

Issue After setting up a UNC as a BBMD the other UNC's on that subnet are getting "network mismatch" errors in their standard output windows. Product Line TAC IA Series Environment R2 UNC's with BACnet jar's earlier than 535a. Cause This type of error is indicative of a routing loop on the BACnet internetwork.  UNC's with a BACnet jar prior to 535a when set up as a BBMD will broadcast on their own subnet as well as to the other BBMD's and this can cause that also. Resolution Install BACnet jar 535a or later in the UNC that is the BBMD to see if this corrects this issue.  If the issue persists investigate the BACnet internetwork for a router loop. 

Issue How to configure a G3 station as a BACnet BBMD Product Line TAC IA Series Environment I/A Series G3 version 3.3.22 and later Cause Documentation Resolution In the G3 Station, expand the BacnetNetwork, expand Bacnet Comm, expand Network, and then double-click IP Port.  The IP Port Property Sheet opens (see below)   In the IP Device Type drop-down, select Bbmd.  Click Save The station is now configured as a BACnet BBMD

Issue On a large system with more than 32 subnets, is their a workaround for the 32 BBMD limit on a Continuum system? Product Line Andover Continuum Environment BBMD Foreign Device Registration. Subnets Cause It is not possible to configure more than 32 BBMDs within a BCX40xx. Resolution While foreign device registration can be used as a workaround when controllers must be installed on a subnet but no additional BBMDs can be configured, foreign devices present their own limitations. Let's say we have two subnets.  Subnet A has a BCX4040 that is configured as a BBMD.  On subnet B there are two BCX4040 controllers.  One controller on subnet B is registered as a Foreign device with the BBMD on subnet A Foreign Device Table registration supports up to 1024 devices on the workstation (v1.94 and later).

Issue How many BBMDs and Foreign Devices can be registered on a CyberStation and a bCX4040?   Product Line Andover Continuum Environment BACnet bCX4040 CyberStation BBMD Foreign Device  Cause Concerned about large BACnet sites and exceeding a limitation on the number of BBMDs and Foreign Devices that can be registered.  Resolution Maximum number of BBMDs The maximum number of BBMDs that can be registered on a bCX4040 or on a CyberStation is 32.   Maximum number of Foreign Devices (FDs) Continuum v1.93 or earlier The maximum number of Foreign Devices (FDs) that can be registered on a bCX4040 or on a CyberStation is 64. Continuum v1.94 or later The maximum number of Foreign Devices (FDs) that can be registered on a CyberStation is 1024 The maximum number of Foreign Devices (FDs) that can be registered on a bCX4040 is 64.

Issue Configuration of multiple BACnet BBMD's over several subnets Product Line Andover Continuum, EcoStruxure Building Operation Environment Bacnet BBMD Cause Bacnet Broadcast communication through IP router Resolution Configuration of multiple BBMD's over several subnets: INCORRECT METHOD For example if there are 4 subnets on the same B/IP (BACnet IP Network): Subnet 1: Workstation setup as a BBMD with an entry in the Broadcast Distribution Table for each BCX Subnet 2: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 3: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 4: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. The BCX's do not reference any points from each other. Since there is no data sharing between the BBMD's, one might think that in each BCX's Broadcast Distribution Table that there would only be a need to add one entry for the Workstations BBMD. Sounds like with this setup we'll reduce traffic by only adding the one entry in each BCX's BBMD Broadcast Distribution Table. The above scenario could in fact slow down a network and cause unnecessary traffic.   The supported method is that every BBMD on a B/IP network have the same routing tables(better known as the Broadcast Distribution Table) as in the below configuration. CORRECT METHOD For example there are 4 subnets on the same B/IP (BACnet IP Network). Subnet 1: WS BBMD with an entry in the Broadcast Distribution Table for itself and all BCX's setup as BBMD on the same B/IP. Subnet 2: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 3: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 4: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. The entry below can be found in the BACnet Standards 2004:   J.4.3 BBMD Concept Each IP subnet that is part of a B/IP network comprised of two or more subnets shall have one, and only one, BBMD. Each BBMD shall possess a table called a Broadcast Distribution Table (BDT) which shall be the same in every BBMD in a given B/IP network.

Issue Cannot open Calendars on several BACnet Networks. Product Line Andover Continuum Environment Continuum 1.9X BCX 4040 B38XX controllers Cause BBMD Sub Net Mask Configuration. Resolution There are two configuration methods allowed in a BBMD Subnet mask. One hop configuration and a Two hop configuration. See Understanding BACnet BBMD Distribution Mask for further details

Issue When configuring a BBMD what is the Broadcast Distribution Mask and what are the valid settings for the field. Continuum EcoStruxure Building Operation Product Line EcoStruxure Building Operation, Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution When configuring a BBMD the BACnet protocol defines two methods of propagating the broadcasts messages to other networks. The two methods are referred to as One-Hop also known as a Directed Broadcast and Two-Hop.   Note: In this article the subnet mask is shown using Classless Inter-Domain Routing(CIDR) notation. An IPV4 address is 32 bits long, CIDR notation defines the number of bits used for the subnet mask. The most commonly used are: /8 or 255.0.0.0 /16 or 255.255.0.0 /24 or 255.255.255.0 /32 or 255.255.255.255 One-Hop With the One-Hop method the local BBMD transfers the message directly to the remote devices via the remote router. In this case the IP routers have to support the transfer of IP broadcast messages to remote IP subnets Figure 1 Figure 1 above illustrates the one-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a message directly to the broadcast address of the 192.168.1.0/24 subnet, it is then up to Router2 to send the directed broadcast to all devices on the subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks. (i.e a bCX hosting an MSTP network on COMM2)   Two-Hop With the Two-Hop procedure a BBMD device transfers broadcast messages to a further BBMD in the remote IP subnet, which then distributes the messages in its local network as IP broadcast messages for its IP subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks.(i.e a bCX hosting an MSTP network on COMM2) Figure 2 Figure 2  above illustrates the two-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a unicast message to each BBMD device on its table, it is then up to each BBMD device on each subnet to send a broadcast that will be heard by all devices on the subnet. Which distribution mask should be used? As mentioned earlier, in order for the one-hop method to work, the router on the remote subnet MUST be configured to process incoming messages sent to the broadcast IP address, the two-hop method on the other hand is guaranteed to work, so when in doubt use the two-hop method. Most sites use two-hop distribution for the reason stated above,, the only obvious disadvantage of the two-hop method is that it is a little more verbose than the one-hop method since the message appears twice on the subnet, once as a unicast sent to the BBMD device and then again as a broadcast sent by the BBMD device. In Building Operation and Continuum the distribution mask defaults to the two-hop method (/32 or 255.255.255.255) How to configure the distribution mask For one-hop enter the subnet mask of the remote network in the distribution mask, the system will apply the mask to the IP address to obtain the broadcast address for the remote network. For two-hop enter 255.255.255.255, this tells the system not to do a direct broadcast and instead do a unicast to the remote BBMD device. Sample distribution mask In the BBMD table of a bCX shown in the screen shot above, BDT #1 and #3 use the two-hop method while BDT entry #2 uses the one-hop method.

Issue Communications failure due to transaction timeout when reloading b3 device. b3's version number as seen from the Infinity side reads 0.0000 Product Line Andover Continuum Environment CyberStation bCX4040 b3 Cause A b3 BACnet controller is found to exist in the BACnet folder under an MSTP Network which is different from the Network specified in the bCX's comm2 Port. Resolution Delete the MSTP network under the BACnet folder and perform a 'Find new BACnet devices'.  A new MSTP network should be created with the right network ID.

Issue What is the BACnet attribute COV Increment and how to use it Product Line Andover Continuum Environment BACnet Cause The COV Increment attribute on a BACnet point is equivalent to the Threshold attribute of standard Continuum Infinity inputs. When a Continuum BACnet point is subscribed to by other BACnet devices using COV (Change of Value), its value must change by at least that COV Increment value before a new Value Notification will be sent out. Using this attribute will decrease network traffic especially on the MSTP network when subscribing to frequently changing values.  Resolution This CovIncrement attribute can be set in the BACnet point's Editor on the Basic Alarms Tab.   If you have a CyberStation prior to Version 1.8, setting this value from the point editor will not stay persistent in the controller after the controller is reloaded, it will default to 0. In order to keep the value after a reload, you will need to write a PE program to set the desired value after a reload. The program should be Autostart and Fallthru. A sample of the program is below: Line SetCov Writeproperty("Full Bacnet Path to Point", CovIncrement, "Desired Value") Stop If you have several points that need the CovIncrement set, you would just add the additional lines into this program.   In 1.8 or greater, this program is not needed as these attributes get sent to controller on a reload. Suitable initial CovIncrements still need to be added to each BACnet point however as they default to 0.

Issue There is a need to know if Continuum and/or EcoStruxure BACnet support NAT. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum EcoStruxure BACnet BBMD NAT Cause Many sites use NAT for security purposes.  Resolution NAT traversal is not supported in BBMD implementations (Continuum or EcoStruxure). It is an optional feature that has not been implemented. Requests to add this feature should be directed to Product Marketing to include on the backlog for prioritization. Related Continuum article: Can Continuum operate over a NAT Ethernet connection? Ashrae information: here

Issue SmartStruxure comes preloaded with LonMark's resource files. It is not documented what version of the LonMark Resource Files are build into each version of SmartStruxure. Product Line EcoStruxure Building Operation Environment LonWorks LonMark Cause This is missing from the documentation Resolution SmartStruxure Version Resource Files Version 1.2 13.02 1.3 13.02 1.4 13.12 1.5 14.00 1.6 and later 14.00

Issue Site implements Entry/Egress anti passback access sequence and uses a program that runs overnight to 'forgive' all anti-pass back violations. Product Line Andover Continuum Environment Continuum CyberStation Cause Documentation Resolution The following PE code is provided as a sample of how to have a PE program set the current area in ALL personnel objects. NOTE: The code is given for illustration ONLY and is not intended to be taken as a complete solution, engineers using this sample code must be sufficiently proficient in Plain English so as to make the necessary changes and modifications to the code to adapt it to their particular application.                                         'This WorkStation program sets the current area of ALL personnel objects found in 'theFolder' to "theArea" 'Program's flow type is LOOPING. Number RESULT Object thePerson, theArea, theFolder Line INIT 'ENTER THE FULL PATH TO THE FOLDER THAT CONTAINS THE PERSONNEL OBJECTS   theFolder = Root\CredentialHolders 'ENTER THE FULL PATH TO THE AREA   theArea = Root\MyAreas\TestArea2   Count = 0 'OPEN THE LIST OF PERSONNEL OBJECTS IN THE FOLDER   RESULT = OpenList("Personnel", thePerson, theFolder)   If RESULT = Success then Goto COUNT_THEM Else Goto CLOSE_LIST 'COUNT THE OBJECTS SO WE KNOW WHEN WE HAVE GONE THRU THE LIST EVEN IF WE ENCOUNTER AN ERROR Line COUNT_THEM   While GetObject(thePerson) is Success     Count = Count + 1   Endwhile   CloseList(thePerson)   Goto RE_OPEN   Line RE_OPEN   RESULT = OpenList("Personnel", thePerson, theFolder)   If RESULT = Success then Goto SET_AREA Else Goto CLOSE_LIST Line SET_AREA 'GET THE NEXT PERSONNEL OBJECT IN THE LIST  While GetObject(thePerson) is Success 'SET THE CURRENT AREA   thePerson Value = theArea   'thePerson Value = UnKnown   'to set all to UnKnown comment the line above and un-comment this line   Count = Count - 1  Endwhile  Goto CLOSE_LIST   Line CLOSE_LIST   CloseList(thePerson)   Stop Line E   If Count > 0 then 'WE ARE NOT AT THEN END OF THE LIST, HERE PROBABLY DUE TO SOME ERROR SETTING THE AREA, SKIP THIS OBJECT AND GO TO THE NEXT     Goto SET_AREA   Else 'END OF LIST, WE ARE DONE     CloseList(thePerson)     Stop   Endif

Issue Changes to COV and ReadProperty in bCX from v4.500048 Product Line Andover Continuum Environment bCX b3 Controllers Cause New feature to allow user flexibility for using Forced Polling and not COV Resolution From bCX version v4.500048, all Controllers will have the option of forcing a poll of points from other Continuum and third party BACnet controllers. This new feature: allows programmers to decide which data exchange method to use by the syntax in which they write their data-sharing programs. provides a method for forcing point-to-point polling from a device that does not support COV and sends an invalid error message when the subscription is attempted. This previously caused Continuum to reject polling, resulting in a failure to share data. allows programmers to decide to poll a point only when needed, even if the device supports COV subscriptions. This ensures that data from a device is only sent when necessary instead of always being sent on a “change of value”. The following Plain English formats force polling: "Local point = Infinity Remote Point Value" "Local point = BACnet Remote point Value" "Local point = ReadProperty(BACnet Remote point Value)" The second argument, Value, ensures that polling is commanded – now for BACnet, as well as Continuum/Infinity. (The third example shows the use of Plain English’s ReadProperty system function.) If the Value argument, shown in these examples, is left out, Continuum BACnet will operate as it always has – always attempting a COV subscription and only falling back to the polling method if the target device sends the appropriate COV subscription failure message. Caution: If you have a device that does not support COV subscriptions or you have chosen to use the polling syntax, you must be careful how you write your Plain English programs. A program that runs every scan and polls a point from another controller will cause major problems. For instance, if your scan is running at 100 milliseconds and you try to poll any BACnet device at that rate, you will most likely knock the device offline. It will also cause the program to disable and seriously slow down the scan in your controller that is requesting the data (since the scanner waits for an answer to a poll before continuing). You should also use a line E in your programs, since any communication problem to the target device will cause the polling program to disable.

Issue An application will not open in WorkPlace Tech Editor with the following error:   WorkPlace Tech Editor returned errorOperation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))   Product Line EcoStruxure Building Operation Environment Building Operation Workstation (WorkPlace Tech Editor) Visio 2013, 2016, and 2019   Cause Visio crash causes the Add-In for WorkPlace Tech Editors fluent ribbon to become disabled Resolution To re-enable the WorkPlace Tech Editor fluent ribbon bar, perform the following steps: Open Visio.  NOTE: Open Visio, not WorkPlace Tech Editor Select Options from the File menu. From the menu in the Visio Options window, select Add-ins At the bottom of the window, you will see a field that says 'Manage:' with a selection box after it, select 'Disabled Items' and then click the [Go] button. In the 'Disabled Items' window, select 'SE.WorkStation.IA.VisioRibbon' then click the [Enable] button. Close the open Visio windows and sub-windows. After closing Visio, the WorkPlace Tech Editor fluent ribbon bar will be available in WorkPlace Tech Editor