Building Automation Knowledge Base

Issue How does TAC Vista SmartStruxure Interface affect the field bus traffic under TAC Vista? Environment TAC Vista SmartStruxure interface SmartStruxure TAC Vista Cause Does the TAC Vista SmartStruxure Interface ask for all values that are hosted and how often? Resolution TAC Vista SmartStruxure Interface creates subscriptions to the TAC Vista server and only asks for values that are being used. When you set up the EcoStruxure web service interface, you also set up how often the values get polled in the "value poll interval."

Issue How to specify the number of digits to display after the decimal point in a Pinpoint Graphic. Environment CyberStation Cause Have Graphic that is displaying a temperature value as 78.567, customer wants the temperature displayed with only ONE decimal place (78.56) Resolution PinPoint graphics display the value of points based on the point's print format. Edit the point and change the format from ###.### to ###.## If the point is in a BACnet device edit the point under the BACnet Devices folder and set its format appropriately.

Issue Enabling Extended Log with third party trend logs crashes the Continuum Workstation. When extended log is enabled, an accdataservices error may be received after a period of time. Product Line Andover Continuum Environment Continuum 1.94 SP1 Windows XP, Server 2003, Server 2008 Windows 7 BACnet Cause Some Third Party Equipment has built in trend logs. Even though these logs may not be needed, they are configured by default and may not be able to be deleted. When the trend log buffer is full, they try to send the buffered data down to the Cyber and SQL server. An AccdataService error can generate because the Event enrollments and event notification was not configured. Resolution Disable or disconnect the 3rd party device Edit the Trend logs and set LogInterval, RecordCount RecordsSinceNotifcation and RecordsDownloaded to 0. This will stop the trend log from downloading to the database.

Issue Uninstalling KB2858725 removed MS Dot Net 4.0 from the system and Web Client no longer accepts connections. Product Line Andover Continuum Environment Continuum 1.9x Windows 7 Windows 2008 Server Windows 2008R2 Server Cause Removal of KB2858725 not only removes the update it also removes Microsoft Dot Net 4, Dot Net 4.0 Client and Dot Net 4.5 extended. Resolution   Microsoft Dot Net 4.0 Extended. http://microsoft-framework-4-extended.en.lo4d.com/ Reinstall Microsoft Dot Net 4.0 Client profile. http://www.microsoft.com/en-us/download/details.aspx?id=24872 Note: Link to TPA-CONT-13-0005.00 for .Net Control errors with schedules once update for 4.5.1 is installed.

Issue Trend Chart shows dotted line across the screen instead of expected chart data. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Chart is waiting for a new record possibly caused by incorrect time in the Enterprise/Automation Server Resolution When waiting for a new record, the trend chart draws a dotted line (1) from the last recorded value and forward.  When a new value is recorded, the dotted line between the last and the new record is replaced by a solid series of lines.  Please see Trend Charts. Check the start time (2) and end time (3) period being observed in the chart includes data readings.  Additionally, ensure the Network Time is set appropriately .    

Issue Adding an object to an already opened Trend chart does not work correctly. Product Line EcoStruxure Building Operation Environment Webstation Open chart Adding objects Cause An AS or ES is logged into using a Webstation, and an existing Trend chart is opened. An object is then selected in the System Tree, and then using the right-hand menu, the "Open Chart" and "Add to already open chart" is selected. Values are not added to the already opened chart. This issue is caused by a Java 7 update 51 a specific fix is not available. Resolution Possible workarounds; Use an earlier version of Java. Change Java security level to Medium. Add site to the exception list For further details on "adding to the exception list", refer to Webstation graphics not working after Java updated to Java 7 update 51.

Issue No Messages Received in AMT from specific Link or Site Product Line TAC INET Environment I/NET Seven Xenta 527-NPR Xenta 527 Web Server NPR2000 Cause There are many causes outlined in AMT not receiving Data which show reason why AMT may not be receiving data. In some cases the issues is not due to programmatic issues but network Errors. I/NET uses UDP port 50069 to broadcast data from NPRs and Xenta 527s to any listening host device. While this does give the flexibility to have multiple hosts receive the same packet, it prevents the proof of delivery that a TCP packet provides. You can read more about UDP at this link. http://en.wikipedia.org/wiki/User_Datagram_Protocol Resolution  To prove a network error, use the following methods: Verify everything listed in AMT not receiving Data If feasible, repeat those steps above direct connected to the Xenta 527 via crossover cable. Ensure Window Firewall is disabled on the local PC when performing this task. Once you have a PC that will receive Messages while direct connected, re-connect the 527 to the network and use the same PC to connect to try to 527 over the network. If AMT works or fails based on being on or off of the network, then this is a networking issue. The PC, Domain Server, or Internet Service provider are all capable of blocking I/NET communication. This can be done by either blocking traffic going out of the PC(s) to the NPR/527(s), or it can block traffic from the NPR/527(s) to the PC. On a PC Windows Firewall these are referred to as outbound rule and inbound rule respectively. Please note the following conditions when certain parts of the network traffic are blocked. Traffic Blocked on traffic from NPR to PC Traffic Blocked on Traffic from PC to NPR Both Blocked You can connect to controllers in I/NET, values will update and you can control points You cannot connect to controllers in I/NET, values will not update and you cannot control points You cannot connect to controllers in I/NET, values will not update and you cannot control points AMT does not receive data from the blocked Link or Site AMT does not receive data AMT does not receive data   To Correct a PC Windows Firewall Issue: You will be able to prove a windows firewall issue by turning off the PC firewall for a few minutes and testing AMT. If traffic resumes, this is the cause. Open Windows Control Panel If needed, change "View By" from Category to Small Icons Click on Windows Firewall Select Advanced Settings Click on Inbound Rules Click on New Rule in the Actions Pane Select Program and click Next Browse to the InetIoSrv.exe application on your PC. Click Next Select the Action to Allow the connection and click Next   Set the Rule to apply to all locations. Click Next Name the Program and Click Finish. AMT Should begin to receive data. If not, repeat step 1 to verify this is a PC firewall issue and contact Product Support for additional assistance. If the data is being blocked by the network and not the PC Firewall: Contact your network administrator and explain that the Xenta 527 or NPR 2000 must be able to broadcast UDP data on UDP port 50069. This path must be open on every hop between the device and the PC. Verify that both the PC and device are on the same Windows Domain. Typically, UDP traffic will not travel outside of the Domain. If you are unable to get network blocked removed, you may be forced to put all I/NET devices and PC's on a single subnet.

Issue After a power cycle the Xenta Server need to be re commissioned to get it SNVTs functioning and the controller back online in NL220 or LonMaker Environment Lonmaker, NL220 Xbuilder 5.1.6. Cause As the Xenta Server is used in LonMaker and Vista the subnet is set in the Xenta project. When you then commission in NL220 or LonMaker the address is then set to the LonMaker or NL220 database specification. On a power failure the Xenta server reverts to its Xbuilders Subnet node address and goes offline in LonMaker or NL220 Resolution Save the X-Builder project out of the Vista database. this will allow the Subnet node to be set under the LON heading in the X-Builder project. Match the subnet and node address to the LonMaker or NL220 database subnet and node address of the Xenta Server. Save the X-Builder project back into Vista and then download to the Xenta Server. Now on a power cycle the subnet and node will Match the LonMaker or NL220 database and remain online.

Issue Can a schedule or calendar be printed? Environment StruxureWare Building Operation site Cause Desire to print a schedule or calendar either from AS or ES Resolution Neither Schedules nor Calendars can be printed from Workstation or Webstation using Building Operation

Issue Empty Legacy Code and Error converting PE code seen in Continuum Conversion Tool Many objects shown as "Partially converted" Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Infinet i2 BACnet B3 PE programs and functions Cause The Continuum dump file converts, but numerous errors are seen as below PE programs and functions are empty in line with the error Empty Legacy Code and Error converting PE code Resolution Create a new Continuum text dump by highlighting the b3 or Infinet controllers only (rather than the Network Controller (bCX, NC2 etc)) and create a text dump. This is achieved by right clicking on the highlighted devices, choosing "Send To" then "Text File...". Use this new text file in the Continuum Conversion Tool. If this converts correctly then there is an issue in the Net Controller configuration. Alternatively check the Net Controller configuration, specifically the "CommPort", in this example; the first 'CommPort' line should not exist and is the problem, once removed, the conversion then proceeds correctly. 'TYPE         : DEVICE                              : NAME    : TEMPLATE : DEFAULTMODE : BAUD           : ALIAS CommPort : SiteName\ControllerName : 6780       : False          : Printer                : Baud9600    : CommPort : SiteName\ControllerName : comm1   : False          : Infinet                 : Baud19200  : comm1 CommPort : SiteName\ControllerName : comm16 : False          : LON                    : Baud19200  : comm16 CommPort : SiteName\ControllerName : comm2   : False          : NotConfigured    : Baud9600   : comm2 CommPort : SiteName\ControllerName : comm3   : False          : AutoSet               : Baud9600   : comm3 CommPort : SiteName\ControllerName : comm4   : False          : NotConfigured    : Baud9600   : comm4

Issue How can the IP address of an MPX controller that is configured for DHCP be determined when there is no attached display Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause It is necessary to know the IP address of an MPX that does not have a display for troubleshooting and commissioning multiple MPXs,  Resolution

Issue The "Change set error" occurs after trying to save a LonWorks network variable binding in SmartStruxure. Product Line> EcoStruxure Building Operation Environment Workstation LonWorks Network Cause The LonWorks bindings have become corrupt and need to be rebuilt. Resolution Rebuild LonWorks Bindings Right click on the LonWorks Network. Go to Advanced > Rebuild LonWorks Bindings. Select Yes.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. 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 Are there restrictions on the location of the SP-C on the RS-485 bus? Product Line Security Expert Environment Security Expert Controller (SP-C, SP-AC1, SP-ACX, SP-C-WEB) Security Expert Expander Modules Cause The SP-C Installation Manual shows the SP-C as the first device in a standard network communication connection.  Locating the Security Expert controller in the middle of the RS-485 bus will reduce the amount of cable required. Resolution You can put the controller in any position on the RS-485 chain. Ensure you use the correct cable type, the overall length does not exceed 900 meters (3000 feet) and the two ends are correctly terminated with EOL resistors. Refer to the Encrypted Module Network section in the SP-C Installation Manual - System Controller for more details.

Issue In order to make page links between different I/NET graphic folders work fine, the same folder structure needs to be created manually in EcoStruxure / SmartStruxure. Refer to Converting I/NET graphics to TGML using the "Create Source Tree" option to realize this. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure / SmartStruxure 1.4 or higher I/NET Cause The I/NET graphic folder structure will not be created automatically before SmartStruxure 1.4.0. Resolution Starting in version 1.4.0, there was a new feature called Data import for I/NET graphic. Using this feature, all the converted I/NET graphic folders structure can be imported at one time without any need for manual work. Here are the steps to make it work: Convert the I/NET graphics according to Converting I/NET graphics to TGML using the "Create Source Tree" option, but do not create the folder structure manually in EcoStruxure / SmartStruxure. Create the default Inet Graphics folder by right clicking on I/NET Interface-->New. Right click on Data Import and choose the root folder of all of the I/NET graphics. Click OK. Data importer will check all the file names and bindings. If any error happens, check and fix it before importing again. (Currently apostrophe is not supported in SmartStruxure. Change the name and relative link and do it again. It may be fixed in later version) Check whether all the bindings and links work fine. Important: Currently this feature doesn't support export/import in SmartStruxure. It will fail to import if any sub folders are contained under INET interface. This may be fixed in later version. The workaround is to still create the whole structure according to Converting I/NET graphics to TGML using the "Create Source Tree" option.

Issue When browsing back and forth between Floor Plans the background image is not showing. This appears to be random with some background images showing up correctly with others not displaying the image. Product Line EcoStruxure Security Expert Environment Security Expert Client Security Expert Floor Plans Cause The Floor Plan background image sizes are too large. These must be close to the Width and Height size of the background canvas so that fewer resources are needed during image resizing. For example, where background images are approximately 9921x7016 pixels and been displayed on a canvas sized 1587x1122 will most likely display this issue. Resolution Use image editing software, such as Microsoft Paint, to resize and save the background images to a size closer to the Floor Plans canvas Width and Height. Floor Plan Canvas Size In the above example, the images were resized to 1920x1358 (maintaining the aspect ratio) which was much closer to the canvas size resulting in fewer resources being required to resize the images when viewing Floor Plans.

Issue AccDataServices crash on launch of Continuum CyberStation Environment CyberStation Cause Bad installation. Looking in Control Panel Add/Remove Programs we see 2 different instances of Continuum Resolution Remove Continuum  in Control Panel Add/Remove Programs Delete the Continuum folder in C:\Program File (or x86) Re-install Continuum

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 A huge number of BACnet Alarms stating Duplicate network identifier are being generated Environment BACnet Cause This has been seen when two Continuum bCX1-4040 units were inadvertantly connected together on to a single MSTP network Resolution Correct the wiring, restart the Enterprise Server and the alarms stop

Issue First Day of Week is incorrect Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation  WebStation Cause Calender/Schedule has the week starting on Sunday/Monday and the first day of the week in my region is Monday/Sunday. Resolution WorkStation Exit the Building Operation WorkStation. In the Operating System for Windows, select Start - Control Panel - Clock Language and Region. In Region and Language on the Formats tab, find First day of week and adjust to your regions choice: Open up Building Operation WorkStation and see your calendar changes the first day of the week to match your choice: WebStation Navigate to web_root/localization folder under the ES and find the Local-en.US.js.gz file to edit Using WordPad++ below I find the "First_Day_Of_Week" as shown below and change from "1" to a "2" then save, and using my zip software, I save to format gzip. Notice in the above screenshot the renamed OLDlocal-en-US.js.gz and the new one is in place. Now you can see in WebStation the first day of the week is Monday rather than Sunday

Issue Accuracy of values/input values displayed using a MPM Product Line EcoStruxure Building Expert Environment SmartStruxure Lite using MPM Cause Number of decimal places is 12.345 when the site would prefer 12.3 or 12.34. Resolution You may want to use this example in a running program (PGx) and replace ME.AVx by appropriate variable. Example Program: ME.AVx = math.floor(ME.AVx * 100 + 0.5) / 100 Below is a screenshot of AV3 2.234 value displayed correctly in AV4 as 2.23