Building Automation Knowledge Base

Issue Using the RD and TD LEDs to help commission and Fault finding a Modbus RTU Continuum Xdriver Using the RX and TX LEDs to help commission and Fault finding a Modbus RTU AS, AS-P, AS-B Product Line Building Operation Automation Server Premium Continuum bCX4040 (BACnet) Environment Continuum Automation server Cause How to use the TD RD(TX RX) LEDs to help commission or check an installation Resolution Continuum The Comm Port LEDs on a net controller can be helpful when first setting up or fault finding an Xdriver (ModbusRTU) Every time the net controller transmits the TD LED will flash and every time another device on the bus transmits (such that the net controller can receive it) the RD LED will flash. Thus if Xdriver seems not to be working correctly this is often the first thing to check A simple check with Modbus RTU would be to stop any automatic polling on the network, then manually refresh a modbus point and watch for a single Transmit (TD) followed by a Receive (RD). SmartStruxure The Comm Port LEDs on an AS controller can be helpful when first setting up or fault finding ModbusRTU Every time the AS transmits the TX LED will flash and every time another device on the bus transmits (such that the AS can receive it) the RX LED will flash. A simple check with Modbus RTU is to create only a  single device (or inhibit polling to all but one device) and watch for a single Transmit (TX) followed by a Receive (RX). Modbus Simulation Another useful technique when commissioning or troubleshooting with Modbus is to simulation software on a PC (with RS232/485 convertor for RTU if required). A Slave device or the Master node can be simulated eg ModSim, ModScan, ModbusSlave, ModbusPoll, Mod_RSsim

Issue Configured a new UNC / ENC with the proper IP address using a direct  Ethernet connection.  After installing the UNC / ENC on the customer's network, the UNC / ENC cannot be accessed.  It's IP address does respond when pinged. Environment I/A Series (Niagara) R2 -- UNC and  WorkPlace Pro I/A Series (Niagara) G3 -- ENC and Workbench Cause Customer's network (router, smart switch, etc.) is blocking one of the Ethernet ports required for communication with the UNC / ENC. Resolution If the UNC / ENC has been configured with the default ports, verify that those ports are open through the router and/or switch.  The selected ports need to be open for bidirectional TCP and UDP communications. The default ports for a UNC are 80 and 3011.  Additional information is available in the "IT Manager's Frequently Asked Questions" document and in the Niagara Networking & Connectivity Guide".   These documents also lists other ports that might be required depending on the optional features included in the UNC station.  These documents are included with the documentation set optionally installed with the I/A Series R2 software. The default ports for an ENC are 80, 1911 and 3011.  Additional information is available in the "Niagara AX Networking and IT Guide".  This document also lists other ports that might be required depending on the optional features include in the ENC station.  This document is included with documentation set optionally installed with the I/A Series G3 software.

Issue Need to save the application, configuration and COV link data for an MNB-controller so that in the event the controller fails, all the information can be easily reloaded into a new controller. Environment MNB family controllers WorkPlace Commissioning Tool, version 5.7.2 or newer Cause Need to save the application, configuration and COV link data for an MNB-controller so that in the event the controller fails, all the information can be easily reloaded into a new controller. Resolution The Backup and Restore facility of WorkPlace Commissioning Tool allows the user to backup the complete controller application, configuration, flow balance and COV link data for a single or multiple controllers or restore of a single controller on a given network in a simple operation.  The procedures for using the Backup and Restore functions of the WPCT are included in the WorkPlace Tech Tool version 5.7.2 release notes.  The Backup and Restore documentation is available via this WorkPlace Tech Tool release 5.7.3 Release Notes from The Exchange Download Center.

Issue Need to be able to read and write to a point. Environment StruxureWare Building Operation Workstation ES AS Cause Need to be able to read and write to a point. Resolution Declare the point as Output and bind it. Outputs can be read and written.

Issue How many characters can an object in Vista have? Environment Vista 5.1.6 and newer Cause When naming an object, all letters and digits are allowed. Additionally, the following characters may be used: (space) [ ] _ : / Up to 40 characters in length can be used. Resolution When naming an object, all letters and digits are allowed. Additionally, the following characters may be used: (space) [ ] _ : / Up to 40 characters in length can be used.  Examples of prohibited characters are: ! " # $ % & ' ( ) * + , - ; < = > ? @ \ ^ ` { } | ¦ .(period/fullstop)

Issue What log files exist in Vista Server and can be used to help diagnose problems experienced by Vista Server. Environment Vista 4.x.x/5.x.x b0warlog.txt b0dbglog.txt b0errlog.txt b0cfglog.txt Cause Vista Server creates log files in the $log sub directory of the Vista database folder. These logs are created as needed when a warning, error, or other message that needs to be communicated. The nature of messages in these log files are related to the Vista Server installation, configuration, and errors experienced when processing data from the network defined in Vista Server. Alarms and errors caused by the actual network are not displayed in these log files but are visible in the alarm pane or event log inside the Vista database. If experiencing a problem in Vista Server review of these log files and matching the time stamps can help identify the cause of the problem. Resolution There are multiple log files created when a warning or error occurs. Each message is time stamped with details of the process and message. b0warlog.txt - Warning Log File Warnings are recorded here. Some Vista Server alarms might point here for more details such as failure to transfer logs from a programmable controller.  Can also find configuration errors such as SMTP setup problems, failure to write property values,  or Vista report problems when trying to launch Microsoft Excel. b0dbglog.txt - Debug Log File Information related to debugging messages b0errlog.txt - Error Log File Error messages that are more severe then warnings relating to Vista Server. b0cfglog.txt - Configuration Log File Configuration messages such as importing a network from the Vista System Plug-in or communication port problems in LonWorks networks.

Issue Customer wants UNC to calculate times to turn outdoor lights on and off. Environment I/A Series (Niagara) R2 (any version) Cause Customer request for Scheduling functions based on SunRise and / or SunSet. Resolution There is a program called "SunClock" that be used for that purpose. Here is a brief overview of using program modules, if you are not familiar with their use. Create a folder, such as MyProgLib, for holding your program modules under the Niagara release folder: Extract the SunClock.sns file from the attached zip file and place it in the folder you created. Open WorkPlace Pro and open the UNC station into which the program module is to be placed. Open the Local Library and navigate to the folder you created in step 1 above. Copy the SunClock.sns module. Paste the module into the desired container within the UNC station. The SunClock program module has the following outputs: sLights        BooleanStatusType     Status Output On between LtsOn and LtsOff times     pLtsOn         BooleanPriorityType   Priority Output to turn lights on pLtsOff        BooleanPriorityType   Priority Output to turn lights off SunRiseTime    DateTimeType          Calculated Sunrise Time SunSetTime     DateTimeType          Calculated Sunset Time LtsOn          DateTimeType          Calculated Lights On Time LtsOff         DateTimeType          Calculated Lights Off Time The program uses the following properties to control its operation: LtsOnPriority          Priority level for turning lights on LtsOffPriority         Priority level for turning lights off Latitude               Geographic Latitude of location Longitude              Geographic Longitude of location SunRiseOffset          Minutes before sunrise to turn lights off SunSetOffset           Minutes after sunset to turn lights on DSTEnable              Enable Daylight Savings Time calculation DSTBeginWeekOfMonth    Week of month that DST starts, 1=first DSTBeginDayOfWeek      Day of week that DST starts DSTBeginMonth          Month of year that DST starts       DSTEndWeekOfMonth      Week of month that DST ends, 5=last DSTEndDayOfWeek        Day of week that DST ends DSTEndMonth            Month of year that DST ends Notes:  Enter Latitude as a positive number for locations in northern hemisphere Enter Longitude as positive number for locations west of prime meridian  Enter negative offsets to set control times after sunrise / before sunset      

Issue RAM is unable to read the Sigma alarm record file. Environment Remote Alarm Manager 2.0 RAM 2.0 Sigma Alarms Cause Corruption has occurred in the files stored in the "Runtime Folder" Resolution Stop the Remote Alarm Manager services either via the "Services" window, or by selecting to change the RAM Computer Configuration, and when asked if you want to stop the services, answer yes. Locate the Remote Alarm Manager "Runtime Folder" and delete all of the files in this folder, make sure that the empty folder is left. The location of the "Runtime Folder" could vary from PC to PC and will be dependent on the operating system and installation, so it is best to use the "Search" function to locate it. Restart the Remote Alarm Manager services and test its operation.

Issue Continuum Database Initializer hits an error when an attempt is made to update the database. Environment Continuum Database Server Continuum Database Initialization Cause Technician is using the wrong Andover97 password. Resolution Use the current Andover97 password during the update database process.

Issue Information required for replacement Environment X 96 BAT Battery pack Cause X96-BAT battery pack replacement Resolution The X-96-BAT contains a fuse holder with a 5 amp quick blow fuse type.

Issue Are the current Veeder Root Xdrivers compatible with the TLS450 and TLS2P console? Environment Xdriver Cause The current Xdrivers are compatible with the Veeder-Root TLS350 Console. Are the current Veeder-Root Xdrivers compatible with the TLS450 and TLS2P console? Resolution No. The current 1st and 2nd Generation Continuum compatible xDriver for Veeder-Root TSL300/350/350R is not compatible with the TLS450 or TLS2P. For the current Xdriver see Leak Detection Systems Drivers on The Exchange  Download Center.  

Issue Getting runtime error 312 when in the embedded webpage on both NC2 and BCX. Environment Embedded Webpage NC2 BCX ACX B4 Cause Malware present on PC. Resolution Run virus scan. If virus scan software is not successful at eradicating the virus, format and reinstall operating system.

Issue In a Niagara G3 station, attempts to send email fail with message:  invalid address error. Environment Niagara G3 Cause If spam filter is enabled the SMTP server will not route email, as long as the Reply to parameter is empty.  It will treat the message as spam. Resolution The Outgoing account under the email service should have an email address listed under the Reply to parameter. If an account is required in the Outgoing Account parameter, for example:  joe.jones@acme.com, the same email address can be entered in Reply to parameter. If no Account is required for the SMTP server to route email but the spam filter is enabled, enter a fictitious account.

Issue A seven day schedule has been setup in the MNB-1000 using WorkPlace Tech but I don't see any way to set the controller time? Environment WorkPlace Tech 5.X, Commissioning tool Cause The time and date in the MNB-1000 cannot be defined using WorkPlace Tech. Resolution Open the WorkPlace Tech Commissioning tool, locate the desired controller in the Device list and open the Device Properties for that device.  On the Device Properties - General tab there is a "Device Clock>>" button used to synchronize the MNB-1000 to the PC's time and date.  This is also where the Time Zone is defined for the MNB-1000.

Issue Can not connect to a Remote SQL server 2008 R2 from Vista. Locally where the SQL server is installed it is working fine. Environment Vista 5.1.6 SQL server 2008 R2 Cause To connect remotely to a SQL server some additional settings must be set, see resolution below.  Resolution Open the SQL server management studio, open the properties for the SQL server, go to connections, make sure "Allow remote connections to this server" is marked. Open "Security" in the properties, make sure the correct server authentication mode is marked. In the firewall open port 1433 and 1434 which is the default ports used by the SQL server.

Issue Editing Multi-Stage control objects. Environment Sigma Control Multi-Stage Multi Stage Cause Multi-Stage control objects cause the controller to lock up when edited. Resolution The exact cause of this issue has not been located, but here are two suggestions. Download the complete object file periodically when editing these objects. If contingency logging is enabled on the multi-stage control object, it should be disabled before working on that object.

Issue The Forta range actuator does not fit onto the V321 Valve. Environment V321 M800 M1500 MV15B M3000 Cause The actuator has a 10mm fitting, the valve (DN65 to DN100 only) spindle has a 8mm stem. Resolution On V321 valves size DN65 to DN100 an adaptor piece is supplied with the valve part no. 880-0133-000 to adapt the valve spindle to the actuator drive. The part no. 880-0133-000 can be ordered separately.

Issue Can communicate (ping and open controller webpage) when plugged into the controller but cannot communicate from CyberStation over the site network. Environment CX, bCX, NC2, NetController, ACX2, ACX57xx  Cause Can communicate (ping and open controller webpage) when plugged into the controller but cannot communicate from CyberStation over the site network. Resolution In this case the problem was an issue with the end user's IT department. They missed one of the MAC entries in their router table causing the communication to stop at the router

Issue Need to write a setpoint value from one controller to the setpoint of a different controller but the receiving controller does not show up in the Link Builder Client list. Environment I/A Series Workplace Tech Commissioning Tool - Link Builder Cause Only controllers that contain AVCOV or BVCOV objects will show up on the Link Builder "Client" side.  Resolution Link Builder "Server" objects can only link to AVCOV or BVCOV objects in a "Client" controller.  Once an AVCOV or BVCOV object is created in a controller that controller will show up in the "Client" list.  A setpoint value from a "Server" controller can then be linked to a AVCOV object of a client controller and used as desired in the client controller.

Issue Workplace Commissioning Tool is showing a yellow triangle with red exclamation point on an MNB-1000 controller icon. Environment WorkPlace Commissioning Tool version 5.x.x MNB-1000 controller Cause The yellow triangle icon indicates that there is a firmware or Remote I/O Status issue on the RIO bus of that MNB-1000 controller. Resolution There are three ICON overlay symbols that can be displayed over the device icon in the WorkPlace Commissioning Tool.  These symbols are defined in the Device Icons table of Chapter 1 of the I/A Series MicroNet Commissioning Tool manual, F-27358.  Further information regarding the reason for the display of the Remote I/O Warning (yellow triangle with exclamation point) is found in Table 6.1 of that manual.  This document is installed along with the WorkPlace Tech Tool software package and can be accessed from the Help menu of the Commissioning Tool. Any R-I/O module status except Communicating OnLine is reported with the warning symbol being displayed overlaying the MNB-1000 device icon.