Building Automation Knowledge Base

Issue When opening a dashboard graphic, the system operates very slowly.  Navigation to other links with the Dashboard displayed, and clicking on a linked graphic does not display immediately.  Product Line EcoStruxure Building Operation Environment Building Operation 3.2.3 and higher Building Operation Automation Server Bundles (AS-B) Building Operation WebStation  Cause Typically when a large number of stored values (100,000 per trend log) is needed to be displayed within the Dashboard widget (e.g., Period Chart) with a significant number of trend logs to be displayed (five or more) in the Dashboard, this will put excessive load on the AS-B and hence stops any or all navigation thereafter.   Dashboard widgets typically continue to read data required to be displayed after closing (or navigating away). This is to keep those logs cached for a few minutes after the dashboard is closed, so if the same logs are loaded again, then the data is available. Any calculations are always done on the client, regardless of whether a chart, dashboard, or trend list is shown. The same is also true for WorkStation. Resolution Below are some considerations to look at improving the overall performance when dealing with this issue: Reducing the number of storage records from 100,000 to something more reasonable for the dashboard to display (5,000 - 8,000) Having these logs stored on the Enterprise Server and Dashboard operated from the Enterprise Server.    If large storage is necessary, then create or use different logs for display within the Dashboards widgets.  If the intention is always to show calculated values, use log processor trend logs. Log Processing Trend Log. These can be pre-calculated and thus contain only a fraction of the full source log's data amount. Upgrade to the later version (EBO 2023) as many optimizations have been made for Dashboards since 3.2.        

Issue A site configured a schedule to have 2 different holiday durations during a spring break holiday week. The schedule is not working as expected. The Holiday week is set up as a range for Monday - Friday and assigned to a single Holiday group.   Two new schedule durations have been added with the respective days selected that they would like the durations to activate on. On the 2 new durations, they added the Holiday group in the "Always Active On" area.   Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Access Expert V3 Premise Cause Holiday and special date durations will activate on the holiday dates regardless of the day(s) of the week selected in the scheduled duration. The day(s) of week checkboxes in each duration is only used for setting a recurring weekly activation on those days and are not required for Holidays. For durations that will only be used during holidays, do not select any day(s) of the week. Resolution In this case, since you need two different durations during your holiday week, you will need two new durations but with different holiday groups for each duration. Set the M, W, and F duration as holiday group A and T, R for holiday group B. Now apply the Holiday Groups to the right dates via the Holidays Menu.      

Issue While RS485 requires a daisy chain topology, can b-Links be daisy chained along with b3 controller in the BCX segment. Product Line Andover Continuum Environment MSTP b3 B-Link RS485 Cause While RS485 requires a daisy chain topology, the addition of b-Links to a RS485 bus makes the limitations of bus wiring less clear. Resolution RS485 is an electrical standard.  The key to understanding RS485 topology conformance is to understanding that each segment of the RS485 bus must have a daisy chain topology with the required termination resistors installed at each end of the segment. The bus segment that runs from the BCX controller to inputs of several b-links and or b3 controllers would constitute one segment.  As long as this segment has a daisy chain topology with the proper termination resistors installed it conforms to the requirements of RS485 bus wiring. Each outgoing leg off of any given b-Link constitutes one distinct and separate segment. As long as this segment has a daisy chain topology with the proper termination resistors installed it conforms to the requirements of RS485 bus wiring.

Issue After TAC Vista Server is started, logging into TAC Vista Workstation, an error "Ensure that Vista Server is started" occurs. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation TAC Vista Webstation Cause This issue is due to the DCOM permissions that Vista Server relies on and they must be manually changed. Resolution Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET contains a DCOM Utility that can automatically set the proper permissions to clear the issue. To manually alter DCOM parameters: Locate the DCOM config in Component Service > Computers > My Computer Right-click TACOS and selected Properties Select Security tab Click the Edit in Launch and Activation Permissions. Add the appropriate groups or user names of computer and Allow them permissions. After finishing the above procedures, the issue should be solved. Error: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. also discusses this issue.

Issue When trying to create or update a Security Expert database the error 'Invalid Database Server is displayed Product Line EcoStruxure Security Expert  Environment EcoStruxure Security Expert  Microsoft SQL Server Cause The path to the SQL Server from the Client is incorrect or inaccessible and will not resolve Resolution There are a number of resolutions to this issue depending on the cause. This article mainly focuses on a configuration where the Security Expert and Microsoft SQL Server are on separate PCs. The error can happen locally also but is less likely. One or more of these resolutions may be required to fix the issue. 1. The Server / Instance name is incorrect when typing it into the Database Server dialogue box during installation. (Local SQL Server) Default Database Server Dialog Box    There can be some confusion on what to enter into the dialogue box because, by default, the instance name and the main database name are the same. Ex. Server Name\Instance Name    Database       localhost\SecurityExpert            Security Expert   (Remote SQL Server) Ex. Server Name\Instance Name    Database       SVR19SQL19\SecurityExpert     Security Expert Note: If just the ServerName SVR19SQL19 or SVR19SQL19\SecurityExpert\Security Expert The Invalid Database Server error would occur   Copy and Paste the Server and Instance Names using SQL Management Studio (SMSS) This method can help to avoid typing errors Install SMSS on the same PC that has Security Expert Installed or use SMSS on the SQL server with Remote Desktop From the Connect to Server dialog> Server name, select <browse for more...> Select Network Server and then select the remote SQL server and click OK Right Click> Copy on the blue highlighted server name and instance Paste into the Security Expert Database Server Dialog box   For a detailed description of Instanced and Database, click on the following link Microsoft Database and Instance Article  Note: Try using the IP address instead of the SQL server name. 2. Make sure SQL Server Service is running on the remote SQL server 3. If using a named instance, make sure the SQL Server Browser Service is running on the remote SQL Server 4. Ensure Firewalls have an open port for SQL server (default 1433) 5. Make sure the SQL Server is configured to allow remote connections 6. The Windows account being used to do the Security Expert Installation must have access to create the database on the remote SQL Server.  7. Check the Windows Application and System logs on the Security Expert and SQL Server for errors related to the Security Expert Install, DNS or Connection errors 8. Examine the SQL Server Log for error messages   Ex. If Active Directory is being used, the error “The SQL Server Network Interface library could not register the       Service Principal Name (SPN)” This issue can be fixed by giving the domain account the appropriate permissions in Active Directory. Permissions required are:  ServicePrincipalName: Read  ServicePrincipalName: Write   Log in to the server running your Active Directory service and execute the following steps: Run Adsiedit.msc In the ADSI Edit snap-in, expand Domain [YourDomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= [YourAccountName, and then click Properties. In the CN= AccountName Properties dialog box, click the Security tab. On the Security tab, click Advanced. In the Advanced Security Settings dialog box, select one (any) of "SELF"'s row Click Edit, Open Permission Entry dialog box. Make sure the Principal is "SELF", Type is "Allow" and "Applied to" is "This Object Only", in the Properties section, select the properties below: Read servicePrincipalName Write servicePrincipalName Click OK to apply all changes and exit the ADSI Edit snap-in Finally, you need to restart the SQL Service(s) that use the account in question.   9. If you are still unable to get passed the "Invalid Database Server' error, please open a case with Technical Support.

Issue Can a BS5308 part 1 type 1, 2 pair individually screened cable be used for M-Bus communications? Environment M-Bus Communication Cables Cause A BS5308 part 1 type 1 cable was installed for Modbus communications, but it was then found that the communications were M-Bus Resolution The correct cable to use for M-Bus is J-Y(ST)Y.  These indoor telephone cables transmit analogue or digital signals; Aluminium-laminated plastic foil static screen with tin-plated drain wire minimises the interference of high frequency, electromagnetic field;TP structure minimises crosstalk. For the datasheet please click HERE. The BS5308 part 1 type 1 cable can be used, and the chart below shows the calculations used to establish this. For the cable datasheet, please click HERE. For the Excel spreadsheet please click HERE.

Issue A new feature in EBO 3.2.X where the value is grayed out when the binding on the priority of a BACnet object matches the BACnet Default priority level Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Missing Release note documentation about the new feature added to EBO 3.2.X. Resolution In EBO versions prior to 3.2.X, when a bind in Priority matches the Default BACnet Write Priority, the values can be changed without forcing. From EBO 3.2.X, users need to force the value, let it change, and then un-force it. The following screenshots show this feature in more detail. The following image shows the Default BACnet write priority has been set to 16. Now, for example, if a program output is bound to Priority 16 of an analog value: The value property would be greyed out and has to be forced if changes are needed.   This is a new feature in EBO 3.2.X which is not mentioned in the Release Notes documentation.   Hint: A defect # 45570 has been documented in Release Notes 3.2.X about “Webstation - BACnet analog value's value property is not greyed out when there is a bind to the default priority.”. This issue has been fixed in EBO 4.0.X.   

Issue The BACnet object goes into fault when writing a NaN to an MNB controller. Product Line TAC IA Series Environment I/A Series MNB VAV I/A Series MNB 70 I/A Series MNB 300 Cause Firmware 1.424 and higher responds to receiving a NaN with an Error: "value out of range".  In firmware 1.420 it would accept the NaN and respond with a normal acknowledge message.  This is a result of a change required for BTL compliance. Resolution A slight setup change can accomplish the same result without causing the object to go into fault.  In the ENC edit the properties of the AVSPP object and set the fallback to "null".  Go to the slot sheet of the object being overridden to hide the "Set" option.  This will prevent the operator from attempting to send a NaN that causes the fault.  When a right-click override is performed only the emergency (priority1) and Override (priority8) choices are displayed.  When the override expires or the object is manually put back into “auto” the “fallback” value is output which is “null” and that is accepted at the controller and serves the same function as sending a NaN.

Issue What alternatives are available for accessing Continuum WebClient from browsers other than Internet Explorer? Product Line Andover Continuum Environment Continuum WebClient Server Cause While Internet Explorer is the only officially supported browser for Continuum WebClient, Microsoft has announced that support for Internet Explorer will end in June 2022.   When accessing WebClient sites using Microsoft Edge in Internet Explorer mode. WebClient server returns an error, indicating that Internet Explorer is needed to access WebClient. Resolution It is possible to access WebClient using Microsoft Edge in Internet Explorer Mode. 1. In Edge click on the ellipses (...) top right then select Settings and set like the snapshot below. a. Allow sites to be reloaded in Internet Explorer Mode(Allow) b. Add the webclient machine's login page (http://webclientservername/webclient/logon.aspx) 2. Setting Internet Explorer compatibility mode and Internet Explorer mode for future use. Navigate to the webclient URL with Edge and select Reload in Internet Explorer mode By default, these settings will be Disabled, Set both of the buttons to Enable as shown below. Note: you may have to go through the process twice to enable both buttons   A snapshot of a successful login to webclient with Edge and also the selection in yellow to Exit Internet Explorer Mode if necessary to run other web applications.   The method of specifying Internet Explorer Mode for a site’s webClient URL will depend on how the customer treats the configuration of Edge – either settings at the individual Edge level or via group policy settings.

Issue V321 had a design revision in 2007 that made the original part numbers obsolete. And again in 2020, valve sizes DN65, 80 and 100 were also revised. Product Line Field Devices Environment V321, DN65:  7312153000 (2007), 7312153010 (2020) V321, DN80:  7312157000 (2007), 7312157010 (2020) V321, DN100:  7312161000 (2007), 7312161010 (2020) V321, DN125:  7312165000 (2007) V321, DN150:  7312169000 (2007) Cause Revision in part numbers. Resolution In 2007, stems were changed from brass to stainless steel. In 2020, on sizes DN65, 80 and 100 the bonnet profile was changed, see PA-00790 New Valve Part nos V222, V292, V321.    Please use the latest available revision in part number when ordering, See your local price list, or product data sheet, or contact your Orders Dept for details.   At 2021 part no's are: V321, DN65:    7312153020 V321, DN80:    7312157020 V321, DN100:  7312161020 V321, DN125:  7312165010 V321, DN150:  7312169010  

Issue Using STR-350 Bypass button as On/Off button in Classic Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause Sometimes on/off function is needed when using STR 350/351 to start or stop a device. Resolution Following the steps below to realize this function in Classic Network: Create a Menta file and Click "Add STR Module" in the Device Specification. In the Bits field of HVAC settings, change the value of the last 3 rd bits of the first line from "0" to "1". This bit is to switch the using Bypass button as on/off function on. Create an STRIN and STROUT module. Bind the STRIN to OccManCmd variable, while bind the STROUT to EffectOccup. Connect the STRIN to an real DO point to control the start/stop of device. But an calculation is needed because when the button is off, the value is 2 while the button is on, the value is 3 instead of simple 0/1. Also connect the STRIN to STROUT to make the output synchronize with the input, like the program below. You can also download the sample from here. For the application used in the LNS network, refer to the Using STR-350 Bypass button as On/Off button in LNS Network.

Issue  Error  'Communications failure due to device not online' during personnel distribution Environment CyberStation CX9900 CX9702 CX9680 ACX5720 ACX5740 ACX701 ACX781 Cause By default CyberStation will try to speed up the personnel distribution as much as possible in order to expediently distribute all the card records to the controller. There may be situations where the controller may be overwhelmed,  100MB NIC in the controller  versus a 1Gig NIC in the Cyberstatom and by the amount of traffic caused by multiple CyberStations distributing multiple records simultaneously. Resolution Continuum contains some facilities available in the General Preferences window where adjustments can be made to throttle the personnel distribution. Lines 12 and 13 are the settings used to throttle personnel distribution going to field devices such as ACX701 or ACX781 Lines 14 and 15 are used to throttle personnel distribution going to LAN controllers such as the CX9680 (NC2), ACX5740 (ACX2), CX9900 etc The interval between personnel distribution is in milli seconds, a reasonable value to start at when issues are encountered is 50 milli seconds. Ex. Line 15 change from 0 to 50 Increase by 25 milliseconds after that to get better results. Ex. 50, 75, 100

Issue For troubleshooting and information gathering database queries are useful Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Cause At times engineers and onsite techs need some queries to gather information for troubleshooting or to correct issues. Resolution Click here to download some sample read only queries

Issue When a modbus AO is created and set to 32-bit real swapped, the correct value is not seen at the modbus device. 1000 is written and 1000 is shown correctly at the Modbus device. 1001, 1002, 1003 are written but 1000 is seen at the Modbus device. 1004 is written and 1004 shows correctly at the Modbus device. And so forth. The larger the number, the larger the error increase. Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause When 32 bit real swapped is selected Further down the configuration page, the write function code defaults to "06". 06 is to set a single 16-bit register write and this needs to be changed. Resolution Use the drop down tab and set the function code to "16". 16 is to preset multiple registers i.e. 2 off consecutive 16-bit registers or a 32-bit register.

Issue Define what Network 8000 devices that can be integrated with EcoStruxure Building Operation. Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation Automation Server version 1.2 until and including 3.2 Network 8000 Cause Need to know the supported devices for a Network 8000 to EcoStruxure Building Operation upgrade.  Resolution EcoStruxure Building Operation supports the following Network 8000 LCM devices: LCM EcoStruxure Building Operation supports the following Network 8000 ASD devices: Microzone II MicroFlo II LIM PEM  The following Micronet 2000 products are supported: MN-FLO MN-FLO3T MN-HPFC MN-ASDI  The following Network 8000 products are not supported in EcoStruxure Building Operation: CCL GCM LNC SIM GCM PLC Note: EcoStruxure Building Operation version 4.0 (EBO 2022) and higher are not supported

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Introducing a previously commissioned Continuum IOU module such as an AC-1 to an Access Expert or Security Expert site can cause communication issues in the LON bus due to duplicated node id. Product Line Andover Continuum, EcoStruxure Security Expert, EcoStruxure Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller Cause When IOU modules are commissioned in a Continuum system, the Net Controller assigns each module a Node ID, this is in addition to the LON Module ID that is unique to each module hardware, the purpose of the Node ID, is to decouple the identifier used by Continuum for communication from the specific piece of hardware, this in order to facilitate the replacement of a failed module without the need to change its Continuum identifier. The module stores the Node ID in nonvolatile memory so that it persists across power loss. If a Continuum IOU module is introduced to a LON network (Security Expert SP-AC1 or Access Expert AX-SSC) without clearing its Node ID, there is a risk of creating a duplicate Node ID condition that will prevent the LON network from operating properly. IMPORTANT This should not be an issue during the normal transition of Continuum site to Security Expert or Access Expert, as all the modules on the running LON bus should have unique Node IDs, this is only a problem when adding a module, or replacing a module with one that has been used before. Resolution In order to signal its presence on the LON network, each module will transmit on resetting its status network variable. If upon receiving this message, the Net Controller determines that the module is NOT in its local database, the controller will decommission the module by setting its Node ID to zero. Before introducing a Continuum IOU module that has been previously commissioned to the LON network of an SP-AC1 or SX-SSC controller, decommission the IOU module using the steps below: Attach the module to an empty Net Controller that is powered down with its battery removed. For a Net Controller II, in order to be absolutely sure that the Net Controller has an empty database, you may need to clear its backup in flash from a browser or by the use of the reset IP switch. See LL on how to use the controller's reset IP switch to clear its flash backup https://community.se.com/t5/Building-Automation-Knowledge/How-to-clear-the-controller-flash-backup-from-the-hardware-using/ta-p/5877 Power up the Net Controller Once the CPU led on the Net Controller starts blinking, press the 'Reset' button on the IOU module. Wait 30 seconds to make sure the decommissioning process has completed. Power down the Net Controller Remove the IOU module

Issue How to create a Binary Input or Digital Input on a MPM controller Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) Cause When a Binary Input is created, the object does not work. There is no documentation on how to create a Binary Input Resolution In order to use a Binary Input, both the BI object and the corresponding Analog Input AI object must be added from the object list. For example, if you need to use BI3 with a dry contact, you will also need to add AI3 and toggle its "input type" to Ohms, then save the object. You also need to keep the object in the object list. With regards to “Input type” for the Binary Inputs: (the "input type" property is in the AI object) -When set in Volts, anything >= 2VDC will be considered a 1 status.                                    anything < 2VDC will be conspired a 0 status. -When set in Ohms, anything < 10kOhm will be considered a 1 status.                                      anything >= 10KOhm will be considered a 0 status. Note: When "Input type" is set to ohms, a dry contact must be used for the BI to work properly. BO1 and BO2 of the MPM can be used for example, but not the relays of the TE2 as they are not dry contacts by design.

Issue Trying to run a Script program from a Graphic but getting error Read Only Property. The control in the Graphic has been bound to a VALUE object, in the Script program an output variable (ManualChange in the code below) is bound to the same VALUE object. The program is supposed to toggle the value of 'theOutput' when triggered by setting 'ManualChange' from the Graphic, this works in versions prior to 1.4. Numeric Output theOutput, ManualChange LEAD_CHANGE:   ManualChange = Off Goto WaitForManualCHG WaitForManualCHG:   If ManualChange = On then   if theOutput = on then theOutput = off else theOutput = on   Goto LEAD_CHANGE endif Product Line EcoStruxure Building Operation Environment WorkStation Automation Server - AS Enterprise Server - ES Cause Starting in version 1.4, SmartStruxure does not allow more than one write reference to the same VALUE, once a write reference is defined for a value or other references to the same value are READ ONLY. (See Reference Guide and References beginning with 1.4.x) Resolution Change the ManualChange variable in the Script to a PUBLIC and then from the Graphic bind directly to it. Numeric Output theOutput Numeric public ManualChange LEAD_CHANGE: ManualChange = Off Goto WaitForManualCHG WaitForManualCHG: If ManualChange = On then if theOutput = on then theOutput = off else theOutput = on Goto LEAD_CHANGE endif   See screen shot below of the binding in the Graphic

Issue A space temperature sensor is not reading correctly on a MicroSmart controller (Model # MSC-P-1504).  The type of sensor is not known due to its remote location.  What are the possible values for the SCALE, OFSET, and CVTYP elements? Environment MicroSmart MSC-P-1500 line of controllers Cause Trying to determine the type of sensor installed so a spare sensor can be brought for the service call. Resolution The different combinations of SCALE, OFSET, and CVTYP can narrow down the type of sensor installed (i.e. RTD, voltage, or current).  The exact model cannot be identified remotely.  See page Table 6 on page 17 of the Installation Guide for this controller family.

Issue Connecting an ARA 659 Esbe actuator to a Satchwell  CZT 5305 controller. Environment Esbe ARA 659 ARA 600 Series Wiring Cause Confirmation of the actuator wiring connections to the controller. Resolution The actuator is connected as follows; CZT 5305 - Esbe ARA 659 actuator. Terminal 36/37 - 24 volts (Brown wire). Terminal 35 - 0 volts (Blue wire). Terminal 19 - 0-10 volt (Black wire).- Heating actuator. Terminal 20 - 0-10 volt (Black wire).- Cooling actuator. To review the CZT 5305 datasheet please click HERE. To review the ARA 600 series datasheet please click HERE.