Building Automation Knowledge Base

Issue I/A Series G3 Modbus TCP communications to Siemens Moore 353 controller stops updating after a period of time after ENC/JACE reboot or station start.  The controllers do not drop offline and the associated Modbus proxy points no longer appear to update. Environment I/A Series G3, Modbus TCP 3.6.47 and lower Cause Modbus TCP transaction Identifiers are used to associate the future response with the request.  The transaction ID is a two byte value that can range between 0 and 65535. The Siemens Moore 353 controller appears unable to process Modbus transaction IDs at or higher than 1024. Resolution The I/A Series G3 Modbus TCP driver has been modified to allow the configuring of the maximum transaction ID for each device. Download the following modules from The Exchange Download Center: modbusCore-3.6.47.1.zip modbusTcp-3.6.47.1.zip Install to the appropriate I/A Series G3 Workbench modules folder and upgrade the modules in the ENC/JACE. Modify the transaction ID to a value lower than 1024 and reboot the ENC/JACE station.

Issue Danish Ø alphabet character in I/NET 2.42 build 2316 while upgrade from StruxureWare Building Operation 1.3.0.724 Beta 1 to 1.3.0.802 Beta 2 Environment Windows operating system, I/NET 2.42 build 2316 loaded, StruxureWare Building Operation 1.3.0.724 Beta 1 wanting to upgrade to I/NET 2.42 build 2325 with 1.3.0.802 Beta 2 Cause Danish Ø character is not considered intelligent text. Upgrade from I/NET 2.42 build 2316 StruxureWare Building Operation 1.3.0.724 Beta 1 to 1.3.0.802 Beta 2 renders a empty database. StruxureWare Building Operation views the Danish character as unintelligent text and a filler such as a block, triangle or other symbol.   Resolution Workaround is to edit the names or characters used and replace characters not in the English alphabet. In the example below I have replaced any ambiguous characters with an X. The upgrade performs without issue. A second alternative is to upgrade I/NET to 2.42 build 2325 and StruxureWare Building Operation software to 1.3.0.802 Beta 2, which understands characters not in the English alphabet. Here I have placed Danish and Deutsch characters which upgrade without issue.

Issue New hardware was supplied by the end customer for an existing InVue-installed computer.  InVue was installed from the original installation CDs.  The site backup was restored successfully.  Launchpad opens, Project Manager and Application Manager start properly.  When Communications is started, a pop-up error appears as shown below: Environment Wonderware for Intelligent Building Systems (WIBS) version 1.1 Cause This error is caused by one step of the installation process that does not complete. Resolution To correct the error, 1. Stop / close all WIBs programs. 2. Install CD#1 from the WIBS CD set. 3. Override pre-requisites and click on “Upgrade Operating System”.  Allow this step to finish.  When it is done, it will ask if the computer can be rebooted.  Select Yes.  If the computer reboots successfully, then move onto step 4.  If, after selecting Yes, the computer “hangs” and it needs to be manually forced into a reboot, then this step did not complete successfully.  Re-do “Upgrade Operating System” until the computer reboots successfully on its own.  Then move on to step 4. 4. Re-install WIBS1.1 service pack 3. 5. Open Launchpad.  Select the Job (in Job Manager).  Select the Application (in Application Manager).  Start Communications.

Issue Extended logs are not retrieving new values after an automation server (AS) has been restored underneath the enterprise server (ES). The problem occurs when there is an enterprise server extended log referencing an automation server extended log that is referencing a Xenta log.  Environment Workstation Extended Logs StruxureWare Building Operation Cause If an AS extended log with historical data is restored (for example after the Xenta controller that contains the Xenta log comes back online) the AS extended log can become locked up and will not record new data. When the Xenta controller goes offline and then comes back online the following sequence of events occur (Note: some values in this scenario are entered for example purposes only like the Xenta LogSize): After a restart of any kind the Xenta log will set its LastSeqNo to LastSeqNo+LogSize. This is to tell the AS extended log to do a read since it doesn't know if there are any new records; it should assume everything is new. (A key problem here is that the Xenta log will not increase its LastSeqNo until something reads from it. Normally when there is just an AS extended log and a Xenta log, the AS extended log reads and gets 3 records back. This makes everything go back to normal). The ES extended log notices that the AS extended log has been restored. The ES extended log sends a command to the AS extended log to clear the entire log and set the Last WrittenSeqNo to 101. This changes the scenario in event one from allowing the AS extended log to begin working properly. The AS extended log is only interested in new records now so it requests the LastSeqNo from the Xenta log. This value is used as the Last TransferredSeqNo in the AS extended log. When the AS extended log requests new records from the Xenta log, it answers 150 which is actually the LastSeqNo+LogSize. The Xenta log will not perform a real read to the external log to find out the actual LastSeqNo until something reads it and will not move beyond 150 because of the restart state it is in. Summary: The AS extended log won't read until the Xenta log tells the AS extended log that it has a new record and the Xenta log won't check for a new record until something reads it. Resolution Use a Trend Chart with Live Update The Xenta log can be opened in a trend chart with live update on. The chart will read every few seconds from the Xenta log causing the Xenta log to set its LastSeqNo to the value it should be. Given enough time the Xenta log will have reached the LastSeqNo where the AS extended log will start logging again. To speed this process up, the interval on the Xenta log can be set to the fastest possible scan time (10 seconds). Once the AS extended log begins collecting values again, the Xenta log can be changed back to the original settings. Note: The Xenta log will be cleared when changing the interval.   Create a New Extended Log A new AS extended log that monitors the Xenta log can also be created to correct the problem (disconnecting the old extended log). The new extended log will start reading from the beginning and start working immediately.

Issue Multiple function blocks using the same SNVT names in each function block, cause the Lon plugin to crash. Environment IC-Lon Plugin Multiple function blocks Cause In LonMaker, controllers which has multiple function blocks, and use the same SNVT names in each function block, cause the Lon plugin to crash. Resolution Work around - This issue can be overcome by manually changing the SNVT names in the function blocks to be unique, before using the IC-Lon Plugin. Below is the standard function block.   Here is a SNVT name having been modified. The next screen shot shows the view in the Sigma IC-Lon Plugin with the modified SNVT names.  

Issue Straight S-Cable and angle (L-shaped) S-Cable difference Product Line EcoStruxure Building Operation Environment Automation Server Automation Server Power Supply Automation Server I/O Modules Cause The description in the datasheets / installation instructions may not be sufficient to understand the difference(s) between the two types of S-Cables. Resolution January 2013 Update - The straight connector S-Cable has been discontinued. Refer to Product Announcement PA-00238 for details. The straight S-Cable (part number SXWSCABLE10001) and the angle or L-shaped S-Cable (part number SXWSCABLE10002) works the same in terms of functionality. Both are 1.5 meters in length. The difference is whether the connectors is a straight out type or an angled type. This will probably affect the installation. See the images below Straight type Angle or L-shaped * Note: The straight S-Cable is currently not available and all existing and coming orders for straight S-cable (SXWSCABLE10001) will be replaced with the L-shaped S-cable (SXWSCABLE10002) until further notice. Refer to TPA-SBO-12-0004 01 for details.

Issue Digital outputs do not operate correctly after upgrading. Environment Digital Outputs Hysteresis CMD Cause This issue can occur in two ways; A Sigma V53 CPU card has been replaced with an ARM7 processor card, and the digital outputs no longer operate as expected. A firmware upgrade has taken place, and the digital outputs no longer operate as expected. Resolution This issue has been caused by an early version of SigmaX, which switched the "Hysteresis" function in a DO to on. In earlier versions of Sigma this did not cause an issue, as the Hysteresis function did not work. But, in later Sigma firmware versions the Hysteresis function has been corrected, and therefore this problem will be experienced. To correct this issue carry out the following; Start the Sigma client and server. Select the "Display"menu, and then choose "Object Types", then select the CMD option. Starting at the top of the index, work though all folders and locate the CMD objects. For each objects found, edit the object and select the "General" tab, then deselect Hysteresis Control.   Repeat as many times as required to modify all objects. Having completed the editing, download the object to the controller.

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 ModBMS RUD (Request for Unsolicited Data) Updates Debug Environment Satchwell ModBMS Cause ModBMS appears to periodically not update certain points from the controllers. Resolution We can turn on the debug in ModBMS to see if we can capture any information that can assist with the troubleshooting. In the ModBMS directory, find the ModBMS.cfg file and open it using Notepad. Find the entry ‘Debug’ in the General section. If Debug is not there, add it. See the example below. The default value is 0. Setting to 2 will record only changes of data in RUD updates. Setting to 4 will record ALL RUD updates. We want to set this to 4. After editing, save the file and restart ModBMS. The example above has the value set to 4 ( 4 ). Turning on the debug will add additional information to the ModBMS.txt file. When an update issue happens, send this file to Product Support for analysis. You should turn the debug off / on depending on the recommendations from Product Support.

Issue Looping script programs continuously loop around the code, but a fallthrough needs a trigger to start it running and will stop at the end. How is this configured. Environment Script programs set as Fallthrough in an AS or ES Up to Release 1.3 Cause Plain English used Triggers in points to start a program, these do not exist in an AS or ES Binary value, so what is used to start the program running? Resolution Once a script program has been written, checked and  saved as a Flow Type "Fallthru", you can then edit the bindings. In the bindings use the variable called "Restart" a binary value to bind to the triggering point/ value which should also be Binary. This object can then be triggered on the required event to start the program, which will then execute the code and stop at the end awaiting the next restart. When you Bind a Digital Value to a Scrip program, you may get an error message like the one here: By Default, a Digital Value has no Configuration Settings defined. Enter 0 and 1 for the binary states and then performing your binding to the Program alleviates the error message.  Note: This functionality operates for versions up to Release 1.3. From Release 1.4 the Restart attribute is read only showing the restart status from the program and does not allow a point / value to be bound to this flag. In Release 1.4 a looping program will need to be used checking the state of the trigger point and action accordingly.   Note: in newer releases e.g. 1.7, 1.8 and above, triggers are now supported and you can bind directly to the Trigger attribute of the program, each change of the bound point will trigger the script to run.

Issue When you open LonMaker 3.13 the LonMaker Menu list is not shown in Visio. Environment Lonmaker Cause The Visio macro security settings sometimes become corrupted Resolution  To restore the link to the LonMaker software, follow these steps: Open the Windows Start menu, point to Program Folders, and then click Microsoft Visio. Visio starts Open the Tools menu, point to Options, and then click Security. If any of the check boxes under Macro Security are not selected, select them, click OK, and then exit and restart the LonMaker tool. If you restart the LonMaker tool and you see the LonMaker menu, skip the rest of this procedure. In LonMaker  open the Tools menu, point to Options and then click File Paths tab. Write down the LonMaker path shown in the Add-ons box, and then delete it. By default, the LonMaker path is C:\LonWorks\LonMaker\Visio. *This should be C:\LonWorks\LonMaker. The path may be followed by a semicolon if there are any additional paths in the list. Exit and restart Visio. Open the Tools menu, point to Options, point to Advanced, and then click File Paths. Enter the LonMaker path you wrote down in step 5 in the Add-ons box. Include the semicolon if there are additional paths after the LonMaker path. Exit Visio and then start the LonMaker tool.

Issue Attempting to upgrade an I/A Series R2 Enterprise Server station and the database conversion fails: java.lang.OutOfMemoryError Environment I/A Enterprise Server R2 (all versions) Cause The issue is related to the limitation of the Java Virtual Machine (JVM). The conversion process is attempting to perform the upgrade on the station database and is exceeding the 1GB Java heap during the process. This typically occurs on an Enterprise Server station where the station database (db) contains a large number of log objects and associated logged data records.  Even though the records are archived in the SQL, the running station (log objects) still maintains records within each object. Resolution Verify that the Java heap is configured to allocate the maximum memory. Use the Windows Explorer and locate the nre.properties file (\niagara\lib directory). Edit with a text editor and verify the setting is Java.options=-Xmx1024MB. If not, change and save then restart the Niagara service and try to upgrade again. If the upgrade or conversion still fails (out of memory error), logs will need to be cleared in the running station to decrease the number of logged records. Restart the station in the current version (prior to the upgrade). Open the station and save the current records to the associated SQL database.  Select the Log Service (double click) and perform an archiveAll command (WorkPlace Pro menu items - Command).  The archiveAll command causes the data currently held in every log object to be immediately archived (sent to the LogService archive destination). Note this applies even to logs that are not configured to archive (daily and/or near full). There are two methods of clearing the logs.  The first method involves selecting each log object (double click) and perform a clear command (WorkPlace Pro menu items - Command).  The clear command clears all log data currently held in the object’s log buffer. The second method utilizes the AdminTool object to globally modify the log buffer sizes to temporarily decrease the buffers that will subsequently remove records that currently exist in the log object.  The AdminTool object is a special “utility” apps object, available in the Local Library (tridium/apps/AdminTool). This object provides an admin-level command to “Search and Replace” property values for objects in the station database. Config properties define the property name to search, new value to write, plus other parameters for filtering and recursion. This operation automates what would otherwise be a manual process of opening and modifying multiple objects’ property sheets. Note: The adminTool will globally apply the changes to objects defined within the utility.  Multiple iterations of this process may be required if log objects are configured with different buffer sizes. Open the local library and copy the AdminTool object to the station's root directory. Open the AdminTool properties and select the Config tab. rootNode -- Configure the swid of the starting point (upper hierarchy) of the station database in which the AdminTool function operates. This can range from the station’s root (/db/stationName) to any container or primitive object in the station’s database. If the recurseChildren property is True, the AdminTool function applies to any and all objects under the rootNode swid.  In Tree View, a right-click “copy” on any object under the station captures its swid. Use CTRL-V to paste the swid into the rootNode field of the property sheet. propertyName -- The target property name, exactly as shown on the object(s) property sheet(s). The property should be a read-write type.  In this example, configure the propertyName to bufferSize. elementName -- Not required for most properties that specify a single value of type float, integer, boolean, or string.  In this example, leave unchanged "-". newValue -- The new value assigned to all matching properties in (and under) the specified rootNode.  In this example, configure the newValue to 1 (bufferSize temporarily changed to size of 1). recurseChildren -- Defines if the search-and-replace function is extended to all children (and subchildren, etc.) of the specified rootNode.  In this example, configure the recurseChildren to True. objectTypeFilter -- Defines a match filter, meaning only objects of this matching type are affected. The asterisk (*) is used as a “wildcard.”  Partial strings of object types are supported, for example, AnalogO* will apply to object types AnalogOutput and AnalogOverride.  In this example, configure the objectTypeFilter to *Log (modify all logs e.g. AnalogLog, BinaryLog, IntegerLog, MultistateLog, and StringLog).  Note: The entire log type could be specified to only apply the changes to a specific type. nodeNameFilter -- Defines a match filter, meaning only objects with matching name are affected.  The asterisk (*) is used as a “wildcard.”  In this example, leave unchanged "wildcard." propertyValueFilter -- Defines a match filter, meaning only objects with this exact value are affected.  In this example, leave unchanged "wildcard." Execute the search and replace command (WorkPlace Pro menu items - Command). Return the newValue to the required buffer size and execute the search and replace command.  The smaller database can now be saved and upgraded or converted as required.

Issue All the correct $LAN objects are setup in the Vista Master and Slave but neither will communicate with each other. If you check the nodes, the connection status shows connected but the Servers will not be online. Environment Vista 5 Cause The server has had the DMZ zone settings Unchecked. This will prevent Server to Server communications. Resolution Recheck the Server DMZ setting back to the standard install defaults.

Issue In Niagara R2, when using the chart/log servlet in a browser, can the legend size be extended or widened? Environment Niagara R2 Cause The name of log objects selected for a chart are truncated in the legend. Resolution The legend size cannot be adjusted manually.  However, the descriptor used for the logged object can be customized somewhat. When using the /chart/log servlet, use "Logs Only (Description)" or "Logs Only (Swid)", the Log Object's description displays in the Legend. There are about 26 digits available excluding units which can be used for customizing.   The descriptor field can also be cleared of any text and the /chart/log servlet will use the object's name in the Legend.

Issue How to put in multiple email addresses for emailing from Email Notification Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Site with at least one ES or AS Cause A good example of when multiple email addresses are required for alarm notifications is a facilities staff. You may need critical alarms to go to several people at once to make sure they are handled in a timely fashion. Note: Consider configuring Building Operation to email a distribution list as opposed to several email addresses. That way the IT department can handle making changes without having to access the building control system. Resolution in the email address field of the Email Notification, addresses should be separated with only a semicolon. No space is permitted between the addresses. Note: This will not work from Webstation, only from Workstation. Example: user1@gmail.com;user2@gmail.com;user3@gmail.com

Issue Unable to view a graphic in Xenta Server web interface. The graphic is not displayed and a Java error message is shown. The message is as follows: Environment TAC Xenta Server TGML graphics 5.1.X Cause The exact cause is unknown but this is somehow related to localisation - in other words a conflict between the language setting on the PC and the Xenta Server web interface. Resolution Set the PC's (on which the browser is located) language to English to eliminate the problem.

Issue The elaspedActiveTime property of the DiscreteTotalizerExtension is displaying the time in hours, minutes, seconds and milliseconds. How do we not display the milliseconds? In the example below, the composited elaspedActiveTime shown is 7 minutes and 33.687 seconds. Environment I/A Series G3 Workbench Cause This is the default display of the elaspedActiveTime property Resolution Follow these steps to configure how the elaspedActiveTime property should be displayed. The elaspedActiveTime property of the DiscreteTotalizerExtension should already be composited. Go to the Slot Sheet of the DiscreteTotalizerExtension parent object. The example below is shown with a BooleanWritable object. Right-click on the elaspedActiveTime property and select 'Config Facets'. The Config Facets window will pop up. Add in the Key 'showMilliseconds' and Type 'Boolean'. The value should be set to 'false' since we do not want to show the milliseconds. Click OK. The elaspedActiveTime property will now be displayed only in hours, minutes and seconds.    

Issue The Lonworks Network has been moved under the LNS Port and no longer resides directly under the Vista Server in the tree structure as it was in previous versions.  This will add a level in the binding path and the old paths are no longer valid. This will impact any binding paths to objects on the root level of the System Tree.  Product Line TAC Vista Environment Upgrade Vista from versions older than 4.5 to newer versions OGC Graphic bindings Trend Log bindings Cause Versions of Vista < 4.5 had the Lonworks Network connected directly to the Vista Server in the workstation tree structure. A revision to this tree structure was made in all versions of vista > or = 4.5. After an upgrade from an earlier version to 4.5 the Lonworks Network is under the LNS port and is no longer connected directly under the Vista Server. This will add a step to the path in your graphic bindings that must be corrected in the OGC Graphic Editor. Example: OLD Binding Path: VistaServer_LonWorksGroup_ControllerName_Point NEW Binding Path: VistaServer_LNSPort_LonWorksGroup_ControllerName_Point Resolution You will need to edit the binding path of graphics at the root level of the System Tree. Follow the steps below to repair the bindings: Right click on the folder that contains the graphics that need to be altered in Vista Workstation (This same procedure can be performed on individual graphics as well instead of an entire folder). Select "Change References". Click Search in the Change references window. This will display all references that are contained in this folder. Select all references (Alt A) in the window and click Replace. Type the OLD path into the "Find what" field (example:VistaServer_LonWorksGroup). Type the NEW path into the "Replace with" (example:VistaServer_LNSPort_LonWorksGroup). Click OK. Verify that the reference path in the New column is correct and then click Save. This will repair all of the bindings in this folder.  You will need to repeat these steps for all folders containing items that reference points below the LNSPort . Note: Correcting this path will fix the graphics bindings in all future releases of Vista.

Issue Sigma Reports "No Seats Available" SigmaX gives an "Authentication Failed" message Environment Sigma SigmaX Cause There are various scenarios that can affect the operation of Sigma and SigmaX. Usually caused by changing hardware or a different network connection since registering SigmaX. Resolution *******  TAKE EXTREME CARE WHEN USING THE SYSTEM REGISTRY AS ERRORS CAN AFFECT OPERATION OF THE PC  ****** Open the PC's registry by going to Start Menu>Run and type in regedit. Hit the enter key. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\IBS\SigmaX There should be an entry in the right hand window named Registered. The data type should be REG_SZ. The data column should have your unlock code entered.  

Issue Where should door connection be made on a SCU1284 Termination, Terminal number, PIN, SCU1284 Environment I/Net SCU1284 Cause What output to use for door contact Resolution This information is taken from TCON 312.  

Issue What authentication does Sigma ODBC use? Environment ODBC Authentication Cause There is a requirement for two Sigma servers to pass data to a dedicated MS SQL Server 2008 R2 machine. But there are issues with the authentication. Resolution Sigma ODBC does  not support authentication. When configuration the SQL database, NT AUTHORITY/ANONYMOUS must be used, Mixed Mode must not be selected.   The screen shot below shows part of the SQL Server installation process, with Windows Authentication Mode selected.