Building Automation Knowledge Base

Issue Cannot communicate to third party devices using the MODBus TCP XDriver or MODBus RTU XDriver. Environment CyberStation ACX5740 XDriver MODBus TCP Cause The MODBus TCP configuration point was not created Resolution Create the MODbus TCP configuration point following the guidelines in section 5.1.3 of the MODBus TCP guide

Issue What entries are needed in the INPUT_XLATE table for the Sigma digital input to work? Environment Sigma gateway.txt IC GEN DDE IC GEN OPC Cause The Sigma digital inputs operate a reverse logic of 100.0 = off and 0.0 = on.  This needs to be reflected in the IC GEN Gateway.txt file XLATE table Resolution 1.  For the IC GEN gateway.txt input XLATE table when mapping to digital input objects; [INPUT_XLATE] count=2 Item0=1 / 0.0      ;DDE input of 1 = DI on Item1=0/ 100.0  ;DDE input of 0 = DI off 2. For the IC GEN gateway.txt output XLATE table when mapping from digital output objects; [OUTPUT_XLATE] count=2 Item0=0.0/ 0        ;D0 off = DDE output of 0 Item1=100.0/ 1   ;D0 on = DDE output of 1

Issue The default font size in the TGML Graphics Editor is 15. Can this value be changed? Environment TAC Vista - TGML Graphics Editor Cause Default Font Size in TGML Editor is 15 and it is hard coded in the software.  Resolution It is not possible to modify the default font size. When we change the font size, the TGML editor automatically remembers the last value used.

Issue When connecting to several OPC servers, is it necessary to have several OPC Client licenses? Product Line TAC Vista Environment Vista OPC Server Cause In some cases, several counts of the same license module is required if several simultaneous sessions are in use. (Example: Workstation) Resolution You can connect to several OPC servers simultaneously while you just have (1) one OPC Client license.  

Issue Correct Boot Up sequence for I/NET Enterprise Server Level Integration to StruxureWare. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET to StruxureWare Enterprise Server Level Integration Cause Sites which are recovering from a power failure are are using Remote Client with I/O may have certain failures within the system. A site where I/NET works on the local PC but devices seem offline from the Enterprise server may have had the Enterprise Server Start before the I/Net I/O Server A site where I/NET points can be controlled from the ES, but messages are not received by either the ES or I/NET AMT may have had the SQL server start after the ES or I/NET IO Server started. Resolution Restart the SQL Server or Server PC Restart the I/NET I/O Server and ensure it is running as a service Restart the Enterprise Server In order to add the I/NET I/O Server as a dependency for the Enterprise Server use the command prompt line below. Be sure to change the 1.X to reflect the current version of SBO installed. Open the Command prompt Enter the command: sc config "Building Operation 1.X Enterprise Server" depend= inet7iosrv

Issue A Controller with X Driver support has been loaded up with the M-Bus (or M Bus) X Driver and connected to a M-Bus to RS-232 converter (i.e. Westermo AD-01) but is not getting data from the M-Bus meter. Note: This is M-Bus (Meter Bus) and not Modbus which is a different protocol Environment bCX1 and Netcontroller II 2nd Generation controllers with X Driver port enabled MBus, M Bus, XDriver, X-Driver Cause Incorrect comm port settings for the M-Bus interface will stop correct communications to the M-Bus meters. Resolution DefaultMode = Xdriver Baud = Baud300 Parity = Even Stopbits   = StopBit1 Datalength = Databits8 Connect up and configure the system as detailed in the M-Bus manual as supplied (downloaded) with the M-Bus X Driver software. Unless specified otherwise in the manual for the specific 3rd party meter being used, set up the Comm port on the Controller with the above parameters: These settings should be entered and verified through the Command line, then printed back to verify they have been accepted.

Issue Unable to connect with DCT to log in MicroSmart MSC-NC Environment MSC-NC MSC-NCM MSC-DCT Cause Flash Memory got corrupted. Resolution Reloading Flash Memory on an MSC-NC (M) Power down; jump J1 (near processor); power up. Can DCT connect? If so, remove J1 jumper Do Alt-L to start Load Flash ROM installation If unable to connect with DCT, will need to consider replacing/repairing unit.

Issue What can cause RAW alarms seen in alarm log? Environment Continuum error alarm log List View Cause The two most common reasons for seeing Raw Alarm Errors are... Alarms have been updated or deleted offline Continuum DB server is being overloaded. When this occurs, the alarm event coming off the wire gets dropped in the Raw alarm table to get its name and all other information rendered out into a readable format.  If the server is too backlogged the alarm could fall off the raw alarm table before the rendering is complete which in turn would generate the Raw Alarm error. Resolution If the alarm has been updated or deleted offline, reloading the controllers should remove these RAW alarm errors.  This will ensure the database is fully synchronized with the controllers. If there are indications that SQL is overburdened steps should be taken to address this issue.

Issue I/A Series MNL version 3 controller profiles are not shown in the list when adding a new LON device to a SmartStruxure Automation Server.  How do I add the template for one of those controllers to the Automation Server? Environment SmartStruxure 1.3 or newer Automation Server I/A Series MNL version 3 or earlier controllers. Cause Templates are not provided in SmartStruxure 1.3 for the older families of I/A Series MNL controllers Resolution Import a device template per StruxureWare Building Operation release 1.3 Technical Reference Guide section 40.14. This procedure is used any time the device template was not pre-defined or has not been imported into the AS. The templates for the older MNL family of controllers can be downloaded from the Download Center. You should also download the associated readme file so that you understand the arrangement of the files in the folders of the zip file. We suggest that you download and unzip the entire file to your computer using the folder structure contained in the zip file. The readme file lists the xif files contained in each of the xif folders. The xif files contained in the xif_40 folder are already contained in the SmartStruxure 1.3 system. When importing these templates into StruxureWare 1.3, you may get some warnings about SelfDoc strings and possibly errors about missing DRF types. Both issues can be ignored. If errors are reported regarding missing DRF types, click the [No] button to continue the import process.   After importing the template, you can then create the device under the LonWorks network as defined in the StruxureWare Building Operation Technical Reference Guide section 40.2. The template that you imported will be listed based on the name and profile of the device. You can assign a name of your choice (or use the default) for the created device. After device NeuronID or using the service pin process to send it from the controller, you then commission the added device. You should select the option "Keep current configuration in the device". Do not check the "Device application file" because the I/A Series MNL controllers do not use loadable executable files.

Issue Not all features are seen when a BMS platform is viewed using remote control software e.g. RealVNC Environment Remote Control Software. Cause Not all features are seen when a BMS platform is viewed using remote control software. One example is: When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. Resolution When the SmartStruxure License Software application is used, the drop down menu for adding the license detail is not available when viewed remotely using RealVNC. The above example is one scenario. There are a number of other remote control software applications where similar instances may occur. If such an issue occurs, check that the BMS software is functioning correctly by both being viewed and ran in the same environment. Because of the number of different remote control software options that are available, anomalies will prevail.

Issue Site may be migrating from I/NET to another access control system and would like to import the data. Product Line TAC I/NET Environment I/NET Seven SQL Management Studio Cause The site is migrating from I/Net to Continuum or another access control system. Resolution Open SQL Management Studio and create a New Query by clicking on the "New Query" button Run the script below: SELECT * FROM InetDb.dbo.IdWorksView Note:  This view only shows the Primary Group associated with each individual.     Select File>Save Results As... Save the file as a .csv to a location of your choosing

Issue Replacing a Satchwell MBF 2730 2 1/2" 3-Port valve with a current version. Environment MBF 2730 MBF 4732. Cause The Satchwell MBF 2730 was an imperial valve and the replacement MBF 4732 is metric, so there will be differences in size. Resolution The Satchwell MBF 2730 was an imperial 2 1/2" valve, this valve is replaced by a MBF 4732 65mm version, therefore there are some differences in size, the following table shows details of this valve.    Below are details of the current range of MBF valves.

Issue In Niagara R2, how can alarms be viewed and acknowledged using a web browser? Product Line TAC IA Series Environment Niagara R2 Cause Incorrect URL (Alarm Summary) in the address bar of the browser will not display the alarm summary page. The alarm summary page provides a view of exist unacknowledged alarms. Resolution Click below to watch a video document (v-doc) explaining the process of how to View and Acknowledge alarms using Niagara Servlets.  

Issue Continuum Analyzer Failure  (sample) [-] Alarm Integrity Looks for ghost alarm enable flags in the AlarmInfo table Failed Point AlarmEnrollment ObjectIDHi ObjectIDLo FireSmk19Closed DigitalOnALM 1015028650 1086324775 Product Line Andover Continuum Environment Continuum 1.92 Windows XP Cause File Configuration Resolution download file from here then unzip and rename to .xml* The patch is only for versions 1.92 and V1.93 Shut down CyberStation Go to C:\Program Files\ContinuumUtilities\Continuum Analyzer\Queries\System Reports\Alarms folder Rename the file 'Alarm Integrity.xml' to 'Alarm Integrity Old.xml' Copy the new file to the folder Run Continuum Analyzer and verify you no longer get the error. *To download you can RIGHT click on the link and select Save As

Issue Procedure to Change Imperial to SI units in VAV Controller in Classic Network System. Environment Xenta 102-AX VAV Controller TAC Vista (Classic) Cause In classic Network System, when trying to change the Xenta 102-AX VAV units from Imperial to SI, it is not changing. Resolution It is possible to change the Xenta 102-AX VAV units from Imperial to SI, in LNS System using the plug-in, But in Classic Network system, it requires some system settings to take the effect. Follow the below steps to change the Xenta 102-AX VAV units from Imperial to SI: Make sure that these setting are checked in the Administrator account. I some cases there may be two or more administrator accounts that require these setting checked Go to Control Panel -> Open "Regional and Language Options" -> in Standards and formats, change from English (United States) to English (United Kingdom). Note: - If the units are required in Fahrenheit set the English language to United States. - If the units are required in Degree Celsius set the English language to United Kingdom.   Change the Location to your local region.   Go to Advanced TAB -> change from English (United States) to English (United Kingdom). Note: - If the units are required in Fahrenheit set the English language to United States. - If the units are required in Degree Celsius set the English language to United Kingdom.   Click on "Apply all Settings to the current user account and to the default user profile".   Click on "Apply" and then click on "OK".   Re-Start the Computer.   After the computer has restarted, open the TAC Vista Server and Work Station. Then Right Click on "VAV Controller", go to its properties, and reload the XIF file, then press "OK".   Commission and Download.   It should now be possible to change the units of the device.

Issue How is a Pulse Digital Output (BACnet Binary Output) created via a Continuum Conversion Product Line EcoStruxure Building Operation Environment b3 Controller Infinet Controller Continuum Conversion Cause A Continuum Infinet Output created as Elec Type Digital has Format $###, as below When this is converted to EBO, a Type "BACnet Digital Output (Continuum) binary-output" is created. Resolution The Format needs to be modified to ###.### or #.###, as below The BACnet binary output created in the conversion will now be  a "Digital Pulsed Output" Summary below  

Issue TGML Graphic does not display. Shows only a red X Xenta Server TGML Graphics not updating following XBuilder download Miscellaneous Java error messages Product Line TAC Vista Environment Xenta 511, 527, 711, 731 TGML graphics XBuilder Cause Dynamic TGML graphics are rendered in the web browser using a Java applet. Java on the PC will store applets and graphics in its cache for faster load times. This can sometimes be problematic as changes are being made -- either to the graphic source files or the firmware version of the Xenta Server. Resolution Clear the Java cache before loading the page again: Open the Java Control Panel If viewing a Java page, the icon for the control panel will be in the task bar of the PC. Double click it. Otherwise, go to Start > Control Panel > Java. On the first tab, General, see the third box item, Temporary Internet Files. Click Settings...   Click Delete Files...   Select both "Applications and Applets" and "Trace and Log Files". Click OK, and exit the Java Control Panel   Reload the graphic.

Issue TGML Objects are not highlighted when dragging and dropping snippets to the graphics editing pane. If a number of objects are close together, it can be difficult to see which object the snippet is being dropped on to. Product Line TAC Vista Environment TAC Vista 5.1.7 TGML editor 5.1.7 Cause Updates to the TGML Editor in 5.1.7 removed this feature. Resolution The item which the mouse-pointer is hovering over is highlighted in the TGML menu tree in later versions. An upgrade will restore this functionality. As a workaround in version 5.1.7, snippets can be dragged directly to the desired object in the Objects Pane as opposed to the editor workspace to ensure the proper object is selected.

Issue Improper wiring can damage controllers. Product Line Andover Continuum Environment All i2 and b3 24VAC-powered controllers. Cause Improper wiring, such as reversing the conductors, may result in damage to one or more controllers. Resolution Each i2/b3 low voltage powered controller must have its own 24 VAC step down or isolation transformer. X2 of the transformer must be connected to earth ground AND to the terminal marked with the ground symbol on the controller. X1 of the transformer must be connected to the terminal marked "L" or "24VAC". Here's an example of the proper wiring - the i2_b3+887+Installation+Instructions.pdf. Please reference Field bus (Infinet or MSTP) will shut down as soon as device is connected for more information on why the RS485/MSTP will go down if power is wired incorrectly.

Issue The System License Information screen has a lot of useful data on the status of licenses in the EBO system. Is there a way to export or screenshot the entire System License Information page? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Cause Unable to save or export the System License Information screen Resolution There is no option to print or export the Control Panel System license Information screen. It is possible to get a reasonably close facsimile by viewing the LicenseStatus item in System>LicenseManager and adding columns for Required Licenses, Checked Out Licenses, Installed Licenses, Available Licenses, and License Violation.   This can then be Exported in XLSX format for future reference or if required by Product Support