Building Automation Knowledge Base

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Upgrading a JACE-8000 or Edge-10 from 4.10U7 to 4.11 or 4.12 will prevent Niagara Daemon from starting.  You will be unable to connect via Workbench or Browser. Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Tridium Edge 10 Cause The software in builds 4.10u7 and later LTS builds (4.10u8, 4.10u9, 4.10u10) was released after 4.11 and 4.12 reached EOL.   4.10u7 contains a newer signing key that is not recognized by 4.11 and 4.12. Resolution When upgrading JACE-8000 and/or Edge 10 running 4.10 LTS builds 4.10u7 and later, please skip over 4.11 and 4.12 and instead upgrade to 4.13u3 or newer. Alternatively, you may apply the dist that reverts JACE-8000 to clean 4.9u1 state, or for Edge-10, the dist that reverts it to clean 4.7 state. You can then install 4.11u2 or 4.12u2, if that's the version you have to use.  If you've already attempted the commissioning operation and bricked a device, and have backups, you can connect to the debug port and use the factory reset process per the documentation.  For Edge 10, consult the section titled Factory Default Recovery  in the Niagara Edge 10 Install and Startup Guide.  For JACE-8000, consult the section titled Restoring factory defaults  in the JACE-8000 Backup and Restore Guide. If you are lacking any backups for the host, then before performing the factory reset, you should enable SSH/SFTP via the debug port, and then copy out the Station files using Filezilla or WinSCP or equivalent.  Reach out to your support channel if you have difficulty finding the location of station files. Typically, the files will be in a subfolder of /home/niagara/stations. The config.bog file will be keyring encrypted, and you'll have to reset it using the Bog File Protection Tool. See Editing the .bog file passphrase offline in the Niagara Platform Guide  for details on using the Bog File Protection Tool.  For details on using the debug port on JACE-8000, see Debug port  in the JACE-8000 Install and Startup Guide.  For details on using the debug port on Edge-10, see Connecting to the debug system shell  in the Niagara Edge 10 Install and Startup Guide.

Issue EBO acts as a BACnet server and a BACnet client send SubscribeCOVProperty to get value updates of specific property of a BACnet object, ex. present value, but EBO respond with "NOT_COV_PROPERTY".   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Specified property does not support COV notifications. Resolution EBO only supports SubscribeCOVProperty (DS-COVP-B) for the following properties and object types: Status_Flags: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop, Trend Log Event_State, Reliability, Out_Of_Service: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop When a client attempts to use SubscribeCOVProperty for another property not listed above, the appropriate response is 'Not COV Property', as specified in BACnet standard. When getting this response from EBO, the client is expected to automatically use another method to acquire the property value (either via COV subscription or polling). If the client is attempting to read Present_Value, then using SubscribeCOV would be the preferred mechanism.

Issue Do the Xenta IO modules, when used under a programable Xenta device, need to have a Field Device license added? Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause No clear information is provided on if the Xenta IO model needs a Field Device license. Resolution No Field License is needed for IO modules if they are set up under a Xenta programable device like a Xenta 400 or 300 series device. Only the devices that communicate to a Building Operation server require a license (Enterprise or Automation Servers). The Xenta IO modules only communicate with the Xenta programable device using LACNET communication and not the Building Operation servers.

Issue Is there any limitation for the number of local program variables that can be declared in a script program located in ExoStruxure BMS servers or BACnet/IP controllers?   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) 24 V Cause A script program has a lot of variables declared. Resolution There are no hard limits imposed by the script compiler. for the number of local program variables. The limits are performance and device resources. The bigger a program is, the more memory and processor bandwidth it will consume and the longer it will take to execute. 

Issue When changing values like Check-in interval (s) under Poll Control for Zigbee device SED-MTH-G-5045, the value seams not to have been change when opening the dialog again. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RP-C) non-Greenpower sensors SED-MTH-G-5045 Cause Setting is sent to the sensor only once every tenth minute. Resolution Open the dialog box again after 10 minutes to verify your changes.

Issue Details on Access Expert Keep Alert Feature Message usage Product Line EcoStruxure Access Expert Environment Access Expert Hosted software V3 Cause Details on Access Expert Keep Alert Feature Message usage Resolution The Keep Alert feature in Access Expert comes with a default 500 SMS messages a month. This can be used to send a broadcast to the users on the system. For example, if the administrator wants to send a text out to 50 people based on an event, then that would leave a total of 450 remaining.   Another use case would be if there was an active shooter at a school campus where there are 500 students, then this would be done one time and the max texts would be sent.   Additional amounts can be purchased in 500 amounts based on what the need is for the customer. so that their monthly usage stays within the amount purchased.

Issue Frequency of Zigbee device SED-CO2-G-5045 sending its values. Product Line Field Devices. Environment Zigbee SED-CO2-G-5045 CO2 sensor with room temperature and humidity Cause Unsure how frequently the sensor updates it's values to the network. Resolution The sensor has a Transmission Period (writable) that sets how often the device will send a measurement. Default value = 150 seconds Minimum period = 30 seconds maximum period = 600 seconds   Note that there is also a “Night Mode” to help extend battery life. During “Night Mode”, the transmission period is multiplied by 4.   Night mode is entered when the CO2 level falls below the “Comfort Limit Value”, which is 600 ppm by default.  

Issue When importing and saving an application from TAC Vista into Building Operation Workstation, an Error message shows up. Product Line TAC Vista, EcoStruxure Building Operation Environment Building Operation Workstation TAC Xenta Control Device Cause In the application, there were two trend log entries with the same name. Resolution Rename one of the duplicate trend log names.

Issue When a very long path is included in a request to the SmartConnector RESTful EWS gateway, such as when attempting to acknowledge an alarm with a long path, the gateway returns the error "HTTP Error 400: The request URL is invalid."   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Bad Request</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD> <BODY><h2>Bad Request - Invalid URL</h2> <hr><p>HTTP Error 400. The request URL is invalid.</p> </BODY></HTML> Product Line EcoStruxure Building Operation Environment SmartConnector Cause In Windows, the default maximum number of characters in a URL path segment (the area between the slashes in the URL) is 260 characters. When the object path, after double URL encoding, exceeds 260 characters, it triggers error 400. Resolution To resolve this issue, follow these steps: Add a registry key "UrlSegmentMaxLength" to the following path in the SmartConnector PC registry: Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters Name: UrlSegmentMaxLength Type: DWORD Value: 0 - 32,766 (e.g., set the value to 1000) After adding the registry key, restart the HTTP services or restart the PC. Detailed instructions for this process can be found in the "Http.sys registry settings for Windows" guide on the Microsoft Learn website. Http.sys registry settings for Windows - Internet Information Services | Microsoft Learn

Issue How to calculate memory needed for PCT. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause Unclear memory usage in PCT. Resolution The specifications show that the PCT default memory is 8 GB in Hyper-V. Each running PCT server takes 2 GB and 170 MB per running server. A 4-core CPU can run up to approximately 100 servers and an 8-core CPU can run up to approximately 200 servers. Memory Usage calculation example: For 23 servers, i.e. 23*0.170 GB + 2 GB = 6 GB For 36 servers, i.e. 36*0.170 GB+ 2 GB = 8 GB (default) For 47 servers, i.e. 47*0.170 GB+ 2 GB = 10 GB To start 100 servers, 100*0.170 GB+ 2 GB = 19GB   Helpful Link: PCT 2.0 memory configuration in Hyper-V

Issue When using the SBO xbk Analyzer, a warning with the following details is observed:  *** possible configuration issue *** (QC#49504)  Issue: 'Communication failed' alarms between servers, even if no bindings are made Action: Make sure servers can communicate with each other so they can synchronize. Product Line EcoStruxure Building Operation Environment Building Operation Server backups version 3.x and above.  Cause The defect mentioned in the tool (QC#49504 / DBSQA-57599) was initially created because alarms were generated between two (or more) Automation Servers that had no bindings (or references) between them. This behavior is considered normal. This occurs because the servers attempt to synchronize references but fail due to communication issues, resulting in the alarms. These Automation Servers were previously part of the same system but were separated before reference synchronization was completed. A possible scenario for this issue is: Two servers can see each other. Bindings are established between the two servers. The connection between the two servers is then disrupted (i.e., offline). Subsequently, one or more of the bindings are deleted, leading to offline alarms between these servers, even if no binding exists now, due to pending synchronization. Resolution  The XBK analyzer tool detects this situation via a "SyncPending" flag, indicating that it needs to be investigated if a "Communication Alarm" exists between these servers. This warning can be ignored if no communication alarms are associated with the servers listed by the analyzer tool.   In most cases, if the server names listed by the tool are part of the system, the issue can be resolved by checking and verifying for unresolved bindings via Binding Diagnostics. while connected to a working EBO System.   If the tool lists any other server names that are not part of the system, these server names can be cleared by upgrading to EBO 2024 (v6.0.x) and above.  As stated, it is only a warning for earlier versions and can be ignored, as there can be instances where this is not cleared until upgraded to this release.        

Issue A system with multiple WebRequest calls appears to become erratic after upgrading the AS-P to EBO 2022 and above. After a reboot, multiple scripts execution are hanging.   In previous EBO versions, the script would be stopped and return an Unknown Exception error message.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause The Architectural Guidelines always recommended a maximum of 5 concurrent WebRequest calls. In EBO 2022, this limitation is enforced to limit the impact on the system resources and prevent scripts stopping due to Unknown Exception errors.   Architectural Guidelines    Web requests exceeding this number will be queued, and the scripts doing these calls will hang on that function as the queue is emptied. This will directly impact the execution of other scripts.   Resolution 1. Enforce a good scripting practice to prevent more than 5 concurrent Web Request calls. 2. Cascade the execution of scripts to make sure that after a reboot, the scripts are executed in a sequence to prevent simultaneous calls filling the queue and causing scripts to be stopped.  

  Issue Configuring Schlage PID300 Product Line EcoStruxure Access Expert Environment Access Expert Hosted software  Cause Configuration information needed Resolution When configuring the Schalge PID300 that is used to communicate to a Schalge AD300 Lock, the communication to this device is hardwired to the downstream device. It is wired up as a reader on the MR 50 or MR 52. 

Issue How do you determine which version of Access Expert being used Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Unsure which version of Access Expert is installed Resolution When opening Access Expert new users may not know what version they are currently running. The following differences can help to identify the version being used.   Version 2: Uses a url e.g. http://seba.accessxpert.com The Hardware tree is on the left pane when selected Only five tabs on the header Icons are larger on screen No Folder View  Version 3: Uses an app that needs to be installed The hardware tree is on the right Seven tabs on the header depending on the license Icons are much smaller Folder view when enabled  These are just a few of the differences that are visible to help determine which version is being used.

Issue When using Project Configuration Tool (PCT) in Server mode and connecting from a remote PCT client, it is not possible to transfer backups or exports. The transfer gets stuck, and a complete reboot is required to start using the project again. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause In the "Settings for Project Configuration Tool" the Notification and Listening port defaults to 0. Port 0 means that PCT will ask the OS for an available port. But if network policies prevent PCT from communicating using that port, PCT cannot detect that.  Resolution In "Settings for Project Configuration Tool" Change the port number for the Notification port and Listening port to a port that is available to use.

Issue Port information is needed for Access Expert Visitor Management Integrations   Product Line EcoStruxure Access Expert   Environment Access Expert V3 Hosted   Cause LAN port requirements for each VMS integration   Resolution   Overview The VMS connection is an important step to the setup of your VMS. Below is a chart of supported VMS and required ports. This article is valid as of 15 November 2019. It should also be noted that many of the VMS allow for the customization of ports and that is not be accounted for in this article.    Ports OpenEye Port Usage  80 TCP 2000 TCP Center/Command Incoming Port 2002 TCP Video/Image Incoming Port 2003 TCP Search Incoming Port 9876 TCP Clip Backup Incoming Port 3100 TCP 4007 TCP Live Incoming port 80 TCP 443 TCP 3478 TCP 1024-655335 In/Out Range Outgoing Ports 3001 TCP 4006 TCP DVR Incoming Port ExacqVision Port Usage 80 excaqVision Web Service (customizable) 8082 excaqVision Web Service - Web Socket (customizable) 22609 exacqVision Client computers communicating with exacqVision servers. Default port 22609.   Milestone Milestone maintains its own knowledge base with an article on ports. Management Server service and related processes Port number Protocol Process Connections from... Purpose 80 HTTP IIS All XProtect components Main communication, for example, authentication and configurations. 443 HTTPS IIS XProtect Smart Client and Management Client Authentication of basic users. 6473 TCP Management Server service Management Server tray controller, local connection only Showing status and managing the service. 7475 TCP Management Server service Windows SNMP service Communication with the SNMP extension agent. Do not use the port for other purposes even if your system does not apply SNMP. In XProtect Advanced VMS 2014 systems and older, the port number was 6475. 8080 TCP Management Server Local connection only Communication between internal processes on the server. 8080 TCP Management Server Local connection only Communication between internal processes on the server. 9000(*) HTTP Management Server Recording Server Services Web service for internal communication between servers. 9993 TCP Management Server service Recording Server services Authentication, configuration, token exchange. 12345 TCP Management Server service XProtect Smart Client Communication between the system and Matrix recipients. You can change the port number in the Management Client.    Recording Server service Port number Protocol Process Connections from... Purpose 25 SMTP Recording Server service Cameras, encoders, and I/O devices Listening for event messages from devices. The port is disabled by default. 5210 TCP Recording Server service Failover Recording Servers Merging of databases after a Failover Recording Server has been running. 5432 TCP Recording Server service Cameras, encoders, and I/O devices Listening for event messages from devices. 7474 TCP Recording Server service Windows SNMP service Communication with the SNMP extension agent. Do not use the port for other purposes even if your system does not apply SNMP. In XProtect Advanced VMS 2014 systems and older, the port number was 6474. 7563 TCP Recording Server service XProtect Smart Client, Management Client Retrieving video and audio streams, PTZ commands. 8966 TCP Recording Server service Recording Server tray controller, the local connection only Showing status and managing the service. 9001(**) HTTP Recording Server service Management Server Web service for internal communication between servers. Note: Every Recording Server service needs a port. Additional ports will be 9002, 9003, and so on. 11000 TCP Recording Server service Failover Recording Servers Polling the state of the Recording Servers. 65101 UDP Recording Server service Local connection only Listening for event notifications from the drivers.   Client components (outbound connections) XProtect Smart Client, XProtect Management Client, Milestone Mobile server, Log Server Port number Protocol Connections to... Purpose 80 HTTP Management Server service Authentication 443 HTTPS Management Server service Authentication of basic users. 7563 TCP Recording Server service Retrieving video and audio streams, PTZ commands. 22331 TCP Event Server service Alarms. 22337 TCP Log Server Server Logs (System, Audit, Rule-triggered)   Web Client, Milestone Mobile client Port number Protocol Connections to... Purpose 8081 HTTP Milestone Mobile Server Retrieving video and audio streams. 8082 HTTPS Milestone Mobile Server Retrieving video and audio streams.   DataCollector Port number Protocol Connections to... Purpose 7609 TCP Recording Server Collecting data   Avigilon Port number Protocol Connections to... 50080 HTTPS Server 55080 HTTP Default Camera Device Port 80 HTTP Streaming / Configuration 443 HTTPS Streaming / Configuration   Salient CompleteView Port number Connections to... 80   6970-7225 Completeview Server for cameras using General RTSP/UDP 4242 Data 4243 Command 4250 Config Server 4255 Admin Service 4502-4534 Webserver (optional)   Wavestore The default connect port is 8601. This is configurable.

Issue Could we have 128 characters passwords in Struxureware?  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Workstation Cause In earlier versions of SBO (version 1.7), the password was limited to 100 characters.   Resolution In EBO version 2.0 and 3.0, 128 character passwords are allowed. Passwords have been tested with 500 characters.    

Issue When using the Find function to search for specific records the default size of the Find window can mislead the user to think there are no records to select from. Find Button Product Line EcoStruxure Security Expert Environment Security Expert Client Cause The default size of the Find window is too small for some of the field values to be displayed which can lead the user to think there are no records to search for. Resolution Resize the Find window by pulling down on the bottom right corner which reveals a list of selectable records and the right-hand side scroll bar. Expanded Find Window

Issue Bitwise operations in script behave differently in the AS-P compare to ES regarding negative values. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Premium Cause Bitwise operations in the script only defined for positive Integers. Resolution Enterprise Server processes negative operands as twos complement whereas Automation Server Premium does not handle negative operands. Behavior with negative integers is undefined.

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 An explanation of Hosted backup options is needed to understand which objects are backed up and which are not. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause It's important to understand the backup options available for an instance. Resolution By default, each instance includes a one-year transactional history retention, giving one year of Event History backup. Additional event history retention time can be purchased if required, and such purchases will be visible under "Manage License." Example: Note: There are currently no configuration specific backups that are retained or that can be restored to reinstate deleted hardware or objects into an instance.    Recommendations: Exercise caution when deleting objects, especially controllers, from Access Expert. A prompt requests confirmation before deletion. Generate snapshots of controller configurations and other detailed objects. These snapshots serve as references in case of accidental object deletion, assisting the reconstruction of controllers or other objects with their original configurations. Summary reports can also be useful when trying to rebuild objects. For example: Inputs, Outputs, Readers, etc.