Building Automation Knowledge Base

Issue Is it possible to change the subnet/node and domain for the Lon network in an AS? Environment StruxureWare Building Operation 1.5 and previous Cause The subnet/node for an AS is hardcoded Resolution No Subnet/node is not possible to change for an AS. But the Domain is possible to change.

Issue Knowing the type of cryptographic protocols that Vista uses for communication security. Product Line TAC Vista Environment TAC Vista Server TAC Xenta Server SSL Cause Some systems will require to know the security protocols that TAC Vista uses in order to ensure communication across their network.  Resolution At this time TAC Vista only supports Secure Socket Layer version 3 (SSLv3) to ensure data integrity and security for network communications. More specifically the SSLv3 cryptography algorithm is: SSL_RSA_WITH_RC4_128_SHA This security protocol is hardcoded into the server and is not adjustable. Note: Be aware of other SSL-related issues, mentioned in the following articles: TAC Xenta servers are going offline in TAC Vista Error connecting to Xenta Server in browser using HTTPS

Issue BACnet points are not updating in the UNC after the replacement of a BACnet device. Environment Niagara R2, UNC 520 Cause Tech replaced a drive from one manufacturer with a drive from a different manufacturer. The BACnet device object in the UNC was reused. Since the replacement drive was not the same model or manufacturer as the one being replaced, the BACnet points between the two devices are different. The points in the replacement device do not match the points in the reused BACnet device object in the UNC. Resolution The solution would be to delete the BACnet device object in the UNC, discover the replacement device and learn it into the UNC.

Issue Unable to connect Continuum I/O's to Access Expert Product Line Access Expert Environment Win 8.1 and above on Version 3 Cause The Continuum Integration has only been configured to bring in the AC-1 and AC-1 Plus door controllers as sub-devices. Resolution There is no resolution, but the Continuum I/O's are simply not compatible with Access Expert. Use Mercury 16 In/Out boards for applications that require these types of devices.

Issue When importing a XIF file generated by XBuilder a warning (that might look like it's an error) is shown regarding missing file name and generated date Environment SmartStruxure Xenta Server XBuilder Cause The XIF file generated by XBuilder doesn't completely follow the LONMARK Device Interface File Reference Guide Resolution The warning can be disregarded, but the XIF file can easily be altered to avoid getting the warning if desired Open the XIF in notepad or similar editor, and change the following. Note the colon before the filename. Original XIF header File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00 Changed XIF header File: X913.xif generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on Mon Nov 03 08:00:00 2014 File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00File generated by TAC XBuilder version 5.1.9, XIF Version 4 Copyright (c) 2000 by TAC AB All Rights Reserved. Run on 0000-00-00 00:00

Issue When attempting to open WorkPlace Tech Editor or Monitor an error is displayed stating: A supported version of Visio must be installed for WorkPlace Tech Editor or Monitor to function properly. Product Line EcoStruxure Building Operation Environment Building Operation Workstation WorkPlace Tech Editor and Monitor Cause This message is displayed if WPTE requests Visio be started and Windows is unable to comply. Resolution Confirm the version of Visio loaded is a supported version. If it is then set Visio.exe and SE.WorkStation.IA.wptEd.exe to "run as administrator" and retry. To set a program to always run as Administrator, locate the executable file then right click it and select properties. From the Compatibility tab check "Run this program as an administrator" and then click OK Find the SE.WorkStation.IA.WptEd.exe for the EBO version being used and perform the same process as in step 2+3. See the path below

Issue Host conflict window always pops up, and cleaning routing table doesn't help. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause Host conflict is a normal issue happening in I/NET. It is usually caused by the duplicated host ID setting on different servers, or an engineer laptop is inserted into the network with the same host ID setting with some server. And the routing table will be messed up since all the IP related information will be recorded in the routing table and it will be distributed to all the network devices, including all the servers and NPRs. The usual solution is to clear all the routing tables on all the network devices, . Refer to How to Remove the Routing Tables in a Device or PC about how to clear the routing tables. But if the routing table is cross referred, like Server 1 adding NPR 1 and NPR 2 as reference hosts, while NPR1 adding Server 1 and NPR 2 as reference host, the routing table will never be cleaned out since when you clean the routing table for Server 1, NPR1 and NPR 2 will still try to send their wrong routing table to Server 1. Unless all the network devices are disconnected and the routing tables are cleaned one by one, or disable the 50069 port for the whole network, which is used by the communication between network devices, there is no other way to clean them out. And these two method are not applicable sometimes. Resolution If the routing table can be managed well, such kind of issue will never happen. The best practice on adding reference host and creating routing table is: On the servers: Choose one server as the master reference host. All the other servers add this server as reference host. Don't add NPR as reference host. All the NPRs can be added into the master server by clicking on the NPR button in I/NET configuration and added one by one manually. By this way, the master server can build its own routing table without impacted by other devices. And this one is the only routing table in the whole network. On NPRs. If NPR doesn't need to talk to other NPRs, like transferring indirect points, there is no need to add reference host for NPR. If indirect points are needed, just add the master server as the reference host. Then this NPR will be able to see all the other NPRs based on the routing table on the master server. If the master server is not equipped with UPS, or not always promises to be online, another master NPR can be chosen as a secondary reference host. Add this NPR as a reference host to all the servers and other NPRs. Under this scenario. if the routing table needs to be cleaned, only the master server and the secondary reference host need to be cleaned. It will be more easier to clean all the routing table and get rid of the host conflict error.

Issue Need to know Electromagnetic Compatibility for Power Supply PS-24V Environment AS PS-24v Cause Electromagnetic Compatibility Resolution Please have a look at the attached document for Electromagnetic Compatibility test report  --Report--

Issue Cannot get the SE8300 Series stat to function in the auto mode in a 2 pipe heating application. Environment SE8300 Series Room Controllers Cause The wrong terminals were being used on the SE8300 stat. A 2 pipe heating configuration was being used. When configured for a 2 pipe application, terminals 9 and 11 are used regardless of if it’s a heating only or cooling only application. In this instance terminals 10 and 12 were used. These are the correct terminals for heating in a 4 pipe system, but terminals 10 and 12 are not in a 2 pipe system. Resolution Correct the wiring issue. Remove control wiring from terminals 10 and 12 and wire to terminal 9 and 11.

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 Require a method on how to apply individual setpoints in EBO when Users are granted access at a Security Expert  Door. Product Line EcoStruxure Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause An example of this would be to have room temperature setpoints, or other specific settings, be changed when specific Users are granted access to a room or area. One method on how to do this would be to create a separate Access Level and Access Level Output for each user. When the User with that Access Level is granted access the associated output will be enabled. Using the EWS integration, the states of these virtual outputs can then be monitored within EBO and action were taken when they change state. Resolution Perform the following steps to configure this: Create an Access Level for each User object. Create a virtual output for each User object. A virtual output is an output object that is not assigned to an output expanders physical outputs. You could create outputs on existing expanders above the maximum output channel that you will be using but it is recommended putting these virtual outputs on a completely different module address outside the range that will be used for any physical modules. Module address = 32 would be a recommended starting value. Steps would be: Under Programming | Outputs create three new outputs. Set Module Type to "Output (PX)" Set module address to "32" or greater. Set Module Output to "1", "2", "3", etc... Save the changes. For each of the Access Levels add the corresponding virtual output to the Access Levels Output tab. Access Level Outputs Ensure the Access Level has access to the Door(s) in question. Set the Time to Activate (seconds) in the Access Level | General tab to something appropriate such as 5s. The output will disable after this time period. Set the Reader Access Activates Output on the Access Level. Set Activate Access Level Output on the Reader Expander | Misc Options.    

Issue Site looking for a sample program to monitor the thermostat and alarm if it stops updating the temperature. Environment AS PE Script MPM EnOcean Cause Documentation Resolution Write a PE script to monitor the temperature and alarm as necessary. Click HERE for sample PE Script program.

Issue How to order Continuum v2.0 to take advantage of a Software license instead of a Hardware license. Product Line Andover Continuum Environment Continuum v2.0 and above Continuum Software Licensing Cause A new site requires software licenses, not hardware security keys. Resolution For details on how to order the licensing for Continuum software key see Ordering and Activation of Software License for Continuum v2.0 Note: Purchase a new Continuum Security Key before upgrading to a keyless license. The following is taken from the above document. A new installation – Software license ordering and activation is available only as an upgrade to a hardware key. For new installations please order the USB key from the factory, upon receipt follow the steps outlined hereon for upgrading your USB license to software license. The following products can be ordered with a Software Key: WebClient Server All factory Add-On options [–E (Endura), -D (Data Exchange/Active Directory), -B (Badging), etc...] CoE Add-On options. (see Continuum 2.0 Keyless Add-on Applications FAQ V1.0.pdf for details.) The following can not support a Software Key and will require a Hardware Key (USB or Parallel port): Continuum Interface Server

Issue When logging in to Web Reports, the "Reports Tree" to the left is not shown, and an error message is shown stating that login has failed for the user "NT AUTHORITY\IUSR". Product Line EcoStruxure Building Operation Environment Building Operation WebReports Cause This is a result of not following the Web Reports installation guide.  The SQL Server must be installed with an instance name, and the SQL Server must be started by the user "SYSTEM". Resolution There are two solutions to this issue: Reinstall the SQL Server and Web Reports following the installation guide Use the SBO Reports Agent Config tool on the Community to give access to the 'NT AUTHORITY\IUSR' Alternatively for a more in-depth answer consult How to Fix Login Failed For User NT AUTHORITY IUSRS to add the user "NT AUTHORITY\IUSR" to the SQL Server

Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions.  (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.

Issue In Webstation, when clicking on a hyperlink located on a TGML that references another TGML, nothing happens. Product Line EcoStruxure Building Operation Environment Webstation Cause Sometimes when a graphic is saved, it gets compiled incorrectly. When this happens, the graphic will generally work inside Workstation because Workstation is a closed environment and much more forgiving then Webstation. Resolution Edit the graphic that you cannot open Save it again It will get recompiled correctly

Issue Alarm colors in Workstation Product Line EcoStruxure Building Operation Environment  Building Operation Workstation Cause The default color for active alarms is white font with a red background. Some customers may want this to be in a different color.  Resolution In Building Operation Workstation System tree, go to Alarm Control Panel > Alarm Styles.  From here, the font type, font color and background color of acknowledged, active, disabled, fault or reset alarm states can be changed.  Refer to: Styling the Alarm States in the Alarms Pane and Alarm Views   Also available from EcoStruxure Building Operation 1.9 and above is Alarm Decoration. This allows overriding an alarm configuration for a specific alarm or group of alarms and applying an alarm decoration rule.  An alarm decoration rule is similar to a filter and allows changing other properties in addition to the font type, font color and background color.

Issue A PCS deploy fails and an error message comes up with the text "Xif nnn could not be found" Environment Project Configuration Server (PCS) StruxureWare Building Operation 1.5 and newer Cause An import originating from a live system that has LON network containing network variables on the local node becomes a potential risk in PCS, but will import correctly as long as no local node variables are deleted. There is not currently support for dynamic update of changes on the local node in PCS. Resolution Leave an import containing Local Node variables unchanged, if importing to PCS

Issue Unable to set SE7000 series room controllers local displays in a language other than English Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment SE7000 VT7000 Cause Request from a European country Resolution The SE7000 / VT7000 series displays are only available in English. The SE8000 series have non-English local interfaces.

Issue When TAC Xenta 421-A is used as stand alone LonWorks node, a value read from an 0-10 VDC or 4-20 mA is sent only as 0-100%. Is it possible to send as engineering values? Product Line EcoStruxure Building Operation,TAC Vista Environment TAC Xenta 421-A Cause Then the TAC Xenta 421-A is used as a stand alone LonWorks nodes, the values from an analog input is always sent as nvoAnalog1-4, in 0-100%. Only exception is then using thermistor inputs, when the measured temperature is sent out as nvoTemp1-4. Resolution TAC Xenta 421-A used as stand alone LonWorks node, the values from an analog input is always sent as nvoAnalog1-4, in 0-100%, unless the input is configured from 1.8 kOhm or 10 kOhm thermistors..

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 When viewing a meter consumption report, the values shown in the report does not match the values in the extended trendlog in SmartStruxure Environment SmartStruxure 1.5 and below Web Reports Cause Generally this will happen if the meter is reset and that time the last value of that meter will set a BaseValue. To calculate the total consumption of the meter we are adding the BaseValue to the offset. This means that the value shown will be the logged value + the offset. In some cases however you would want to completely reset the log and just show the same values that are represented in the extended trendlog. It has been identified, that a defect causing a trend logging a 0 after each restart triggers this reset. Request the latest hotfix for 1.5 from Product Support in order to avoid this happening in the future.   Note: This issue (Defect #26360) has been fixed in 1.6.1 release. Resolution 1. Open "SQL Management Studio" and connect to the database "StruxureWareReportsDB" 2. Locate the log you want to reset using this query: SELECT * FROM tbLoggedEntities 3. Note the ID of the log you want to reset 4. Reset the log using the following query, replacing xxxx with the ID of the log DECLARE @id INT SET @id = xxxx UPDATE tbLoggedEntities SET BaseValue = 0 WHERE ID = @id UPDATE tbLogTimeValues SET FloatValue = OdometerValue WHERE ParentID = @id ##WARNING## The above script will reset BaseValue to 0 this may impact on any previous Meter Readings.  Please contact Product Support to discuss this if you have concerns before applying this script.