Building Automation Knowledge Base

Issue Alarms cannot be created in a BACnet b3 controller because the fields are grayed out. Product Line Andover Continuum Environment Continuum Cyberstation b3 BACnet MS/TP controllers Cause Alarms are created differently in a BACnet controller than with an Infinet controller.  These fields are grayed out since they are not used for alarm creation in a BACnet controller. Resolution There are instructions in the BACnet section in the Continuum help for creating an event notification and then mapping the point and the event notification within an alarm enrolment. For an example see AlarmCreatingAndConfiguring BACnet.doc

Issue Information on the MicroSmart Laptop Interface Module (MSC-LIM) Environment DMS MicroSmart Cause Information Resolution Installation / Connection sheet

Issue How to convert earlier versions of Microzone II PSI files to 3.3 revision or later Environment Network 8000 Microzone II, PSI/XPSI Revision(S) 3.13 and 4.1 Cause Error Not a valid application file!  File is not compatible with existing XPSI revision.  It must be upgraded with Zconvert.exe Resolution Procedure on how to convert Microzone II files to revision 3.3 or later and read me file.

Issue How to open an external document (e.g. Word, Excel, PDF) from a G3 graphics page Environment I/A Series G3 (Niagara AX), revisions 3.3 and later Cause N/A Resolution The attached document provides detailed instructions on how to launch an external documents from a G3 graphic.  Click Here to open the document.

Issue What OPC options does sigma support? Environment Sigma OPC DA AE ModBMS IC-GEN-OPC IC GEN OPC Cause Requested details Resolution There are two options available; 1. OPC Server:  ModBMS software available from Product Support London. This supports up to 5000 OPC DA tags and OPC AE events.  See release note for details 2. OPC Client:  IC GEN OPC software mimics a Sigma controller and is loaded onto the same PC as the OPC Server. This supports up to 1000 OPC DA tags only.  See datasheet for details.

Issue Satchwell "AM" series Rotary Actuator requires replacement Environment Satchwell “AM” series Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.   N.B. Where a Satchwell “AM” series Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. In addition to replacing the AMS Actuator it will also be necessary to replace the VV Butterfly Valve Body. The replacement Actuator is S-E type MF type. Please check the latest catalog for current equipment. The Satchwell VV Butterfly Valve Body should be replaced by a S-E Butterfly Valve Body selected from the VF208W series of Butterfly Valve Bodies. It should be noted however that significant pipe work modifications will also be necessary in order to accommodate any selected VF208W series Butterfly Valve Body due to the differing construction of the VF208W Butterfly Valve Body. Please check the latest catalog for current equipment. Cause Obsolescence of Satchwell AM series Rotary Actuator. Resolution Replace Satchwell AM series Rotary Actuator with MV15B-230 Linear Actuator and Linkage Kit :- AM = MV15B-230 + L7SV (880-0126-000) Linkage Kit. N.B. Should the Satchwell AM series Actuator include a wired Auxiliary Switch then the following Auxiliary Switch Pack S2 (880-0469-000) - two independent 250 volt 10 amp (inductive) 3 amp (resistive) rated SPDT Auxiliary End Point Switches - may be purchased separately permitting local installation.   Please check the latest catalog for current equipment.

Issue OPC Server with third party and alternatives Product Line Andover Continuum, TAC INET Environment System requiring third party connectivity Cause OPC Server to communicate between hardware and the iBMS (intelligent Building Management System). Resolution The OPC server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. OPC Client Servers are used to communicate between BACnet IP interfaces and iBMS (intelligent Building Management System) programs such as TAC I/NET or Andover Continuum. There is also no Continuum OPC Client software to use for a direct OPC link. The best way to integrate from 3rd party EIB or OPC protocols is using BACnet IP on Continuum; there are third party interfaces and gateways that will convert to BACnet/IP and others that go from OPC Client/ Server to BACnet/IP. I/NET OPC For I/NET a great solution is to install a Xenta 913 controller which gives the capability to go with Modbus or BACnet/IP to third party solutions. The I/NET to Xenta 913 allows communication with Continuum BCX, StruxureWare AS-B, and other 3rd Party solutions. Continuum OPC Standard 3rd party gateways are established to communicate between the protocols such as BACnet and Modbus. Andover Continuum has an OPC Server available here. The hardware requirements are Windows NT 4.0 or Win2K. If wanting to run on XP or newer operating systems, please be aware that no testing has not been done with these OS. For more info on the OPC and XDriver, please see OPC Server Integration. Only one instance of the OPC server on a computer. Each system would need a separate PC with license key to connect to the individual systems and host controllers. The Andover Controls OPC server must be running a separate 3rd Party OPC client computer and cannot be on the same computer as CyberStation. From there it is configured to retrieve point values from a the suggested dedicated Infinity (CX) Controller. It is suggested to install a OPC gateway Infinity Controller since this controller will constantly be busy with OPC traffic. Therefore it is the separate third party vendor computer which requires the ACC OPC Server security key, not Cyberstation security key. Both USB and parallel port keys are available. If no choice is available for OS, one alternative is to check on 3rd party OPC servers like Kepware and Matrikon. Note: For Continuum, determine which one of your controllers will become the “Primary Controller” The Server requires that you designate one external Andover Controls Infinity or Continuum controller located on the same network as its “Primary Controller.” This controller must have had the network taught to it prior to selection. (This is done through the “Teach” function in the workstation.) The Server gets its information about the network through this controller. This suggested single controller is designated as the interface through which all point access is obtained. Controller Type Select the type of network where the controller is located. For a NetController, b4920, CX9702 or upgraded Infinity controllers that can be connected to a Continuum network you would select “Continuum”. For older Infinity controllers, select Infinity. Works with any IP level controller. There is no limit on the quantity, but rather it depends on how you tune.

Issue Unable to ping the MNB-1000 (Plant Controller) using firmware Revision 1.50E until 1.532  Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, until 1.532. Cause Common IP (Internet Protocol) ports echo (7), daytime (13) and time (37) are open. Having any of these IP ports open may be a cause of concern for customers that are sensitive to network security issues; these customers include defense installations, financial institutions, and government buildings. Resolution The services using the echo, daytime, and time protocols have been disabled which prevents IP ports 7, 13, and 37 from being open. These services and protocols have no purpose during the normal operation of the MNB-1000. Disabling the echo protocol and closing of port (7) has the side effect that the MNB-1000 cannot be “pinged”. Using the command line program Ping will not detect an MNB-1000 that has firmware v1.50E installed. Use WPCT instead of Ping to verify communications with the MNB-1000. Click here to see the Release Notes for firmware Revision 1.50E. Update; In firmware 1.532, the ping function was re-initiated as the default.  Please see the TPA-IA-19-0004.00 Firmware 1.532 Release Notes.  It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue BAS2800+ does not  see the dongle when it is started. Environment Windows XP, BAS2800+ V2.9 Cause The PC is too fast for the dongle to be detected. When BAS2800+ is installed on a PC and BAS2800+ is run for the first time, a warning message is displayed - "No Dongle Driver Detected".  Resolution Download here the fast dongle driver, unzip and install in c:\bas\bin and run dk2wn32.exe Follow the on screen instructions and finally restart the PC. The dongle should now be detected and BAS2800+ is allowed to run.

Issue Attempting to commission and bind to a Trane lon controller (object name:  Lcir & programID 80:00:CF:07:00:0A:04:05, 80:00:2A:55:00:03:04:0C, and Lcir-DAC 80:00:2A:56:0A:03:04:04. Both processes fail.  An xif file was created directly from the controller using Nodeutil. Click here to view the xif file. Environment Niagara G3 version 3.5.25 Cause The commissioning process concludes with a change of state to the controller ('config/online' to 'offline' to 'online'). The issue is that this particular Trane controller responds to the first requests ('config/online' to 'offline') but fails to respond to the 'online' request (original message plus three retries as defined by the LonWorks protocol) or approximately 400 mSec. In addition, the binding process also utilizes an 'online' to 'offline' to 'online' change of state and has some similar delays within the controller response. Resolution Modifying the Retry Count within the Lon Comm Config settings (from 3 to 6) allows up to 6 retries in the event of a no response for this type of  message. The actual Trane node appears to take a long period of time (over 500 mSec) to respond to the change of state message. This change to the retry count will not affect the bus unless there are bus issues that generate multiple retries. Basically, the change will be not be noticeable on a solid operating bus.

Issue There are no existing objects in Niagara G3 that can split a 16-bit Modbus register into two 8-bit values with one representing the high byte (bits 8-15) and another the low byte (bits 0-7). Environment Niagara G3 all versions Cause Modbus integration of a 3rd-party product using 16-bit values which must be split into two 8-bit values. Resolution A program object is available below that will achieve this requirement.  The output of this object generates two 8-bit integer values and two string values for use with logic programming and display purposes.  Text file of program code

Issue The purpose of this verification checklist is to provide documentation to the Project Manager that the Site Engineer has confirmed the Continuum Security configuration. Basic Settings Access Events Reporting Alarm Event Notification and Alarm Enrollments Door Alarms Other Alarms Time Sync Video including Pelco Digital Sentry IP Camera System Administrative Tasks Other Tasks Basic Checklist Access Events Reporting Checklist Alarm Event Notification and Alarm Enrollments Checklist Door Alarm Checklist Other Alarm Checklist Time Sync Checklist Video Checklist Administrative Tasks Checklist Other Tasks Checklist Environment Continuum with Security enabled Pelco Digital Sentry IP Camera System Cause Beneficial checklist for Verification of security site settings. Resolution Please find the attached pdf document which will walk you through the Continuum Security Checklist. The first section provides step by step instructions for novice users. The second section is the actual checklist where each task should be initialed by the Site Engineer, and the whole document signed by the Site Engineer and the Project Manager. To print the Checklist section of this procedure, start printing on page 21 of the attached checklist. Please find the attached pdf document which will guide you through a Pelco Digital Sentry IP Camera System Quick-Setup

Issue WorkPlace Tech revision 5.7.7 installed on a Windows Server 2003, 64-bit machine, receives the following error: Environment WorkPlace Tech Tool version 5.7.7 Windows 2003 Server, 32 bit or 64-bit Windows 2008 Server, 32 bit or 64 bit (multiple processors) Cause WorkPlace Tech Tool (WPT) is not supported on computers with Windows Server operating systems, nor on computers with 64-bit operating systems. Resolution Install on an approved hardware platform, per the Installation Instructions.

Issue Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Controllers: ENC-410-1 ENC-410-1-N ENC-520-2 ENC-520-2-N Cause There maybe a need to access the ENC via its serial port if the IP address of the ENC is unknown or for troubleshooting purposes when the ENC's Ethernet port is not functioning. Resolution Hardware required for connection to ENC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors. RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430). A functioning COM port on your computer. A 2-pin jumper for connection to the ENC's 'Mode' connector. Refer to the Installations Instructions for ENC-410 (pages 10 & 11) or ENC-520 (pages 10 & 11) for details on the cable and adapter.  Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC also refers to these pin outs. Connection to ENC's serial system shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the ENC’s RS-232 port and the RS-232 COM port you are using on your computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to ENC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port you are using on your computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 57600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Click OK. On the ENC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 7 of the ENC-410 or ENC-520 Installation Instructions for position of the Mode connector. With your HyperTerminal session active and configured to log to a file, remove power from the ENC, let it cycle down, then reapply power.  The easiest way to power cycle the ENC is to unplug the 6-pin power plug from the circuit board, wait 15 seconds and plug it back in.  After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... Do not press any key, wait for the login prompt. If you did press a key to stop auto-boot, select option 1. At the login prompt, enter the platform user name, and at the password prompt, the platform password. The default user name is 'tac' and password is 'niagara'. The system shell menu should now appear. You should able to see the IP address of the ENC now. When finished using the serial system shell, do the following: Remove the 2-pin jumper from the Mode connector of the ENC. From the system shell menu, select the Reboot option. Type 'y' at the 'Are you sure you want to reboot [y/n]' prompt, and press Enter. Shutdown-related text appears in the HyperTerminal window, and then the connection is dropped. Press the Disconnect button on the HyperTerminal tool bar. Exit from the HyperTerminal application, selecting to Save if you wish to reuse this HyperTerminal setup for future connection to an ENC. If you are troubleshooting the ENC, send the HyperTerminal start up messages to Product Support for analysis.

Issue This utility, TAC Vista Check References, will check references (every binding and every link) on every graphic at once and provide a summary of any empty or invalid database paths. It will also allow you to correct these broken or missing links and bindings. Environment TGML Graphics Vista Workstation Links/Bindings Cause Viewing the bindings or links of a TGML graphic can traditionally only be done on individual graphics one at a time. In addition, to see if a network path is invalid, it must be clicked on and will turn red if there is a problem. Resolution This utility was created by Benjamin Roswall at Schneider Electric Denmark. It is not an official release, nor is it supported by Schneider Electric. While it has been tested and used successfully, it should be used at your own risk. Download the TAC Vista Check References Utility by clicking here. Unzip the file onto the harddrive, view extracted files Double click TAC Vista Check References.exe Make sure Vista Server is running, click Login and log in to the database Choose whether to check for empty paths, and whether to validate .[OBJECT] bindings Click Check A summary of the network can be viewed and saved by switching between tabs.

Issue IOU Modules power requirement Environment CX9900 CX9940 CX9980 ACC LON IOU Modules Cause Limit on AC power supply capacity. Resolution See "Maximum number of I/O modules' in the I-O System Reference Guide document.

Issue What transport type should be used when setting up an ACX57xx, CX9702, or bCX9640? (UDP TCP Netcontroller) Environment ACX5720 ACX5740 CX9702 bCX9640 Cause What transport type should be used when setting up an ACX57xx, CX9702, or bCX9640? Resolution The definition on the transport type settings from our Technical Reference Guide states that: UDP - This controller will communicate with other controllers and Workstations primarily using the UDP protocol. TCP - This controller will communicate with other controllers and Workstations primarily using the TCP protocol. TCP/UDP - This controller will communicate with other controllers and Workstations primarily using the TCP protocol, but can also speak to controllers and Workstations that communicate primarily using the UDP protocol.   You can set the controller to use either or both transport types for communication with other devices depending on your specific network requirements. UDP is the preferred option for Continuum devices. See the Andover Continuum Network Ports document for details on what specific ports are required. Three things you need to be aware of with this: Make sure that both the transport setting in the device object and the controllers IE configuration webpage are the same. No matter what transport type you choose make sure that any network firewalls are setup to allow packets through on those ports. View this document for some reasons to use Continuum's reliability layer over UDP rather than TCP.

Issue Using the IR Tool or RS 485 converter to communicate with the controller Environment NCP Palm IR Tool RS232 to RS485 converter. Cause Configuration and use of NCP Palm. Resolution Using the IR Tool to communicate with a Unifact Pro controller. Connect the IR Tool to your laptop and Unifact Pro controller. Start the NCP Palm programme. Select the correct serial communications port and uncheck the CTS / RTS selection boxes, then select OK. From the "File" menu select "Connect" Enter 0 for the Subnet address, 0 for the Node address, then select OK. This has now confirmed that you are connected to the IR Tool. To connect to the controller select the "File" menu and select "DisConnect" Select the "File" menu and then select "Connect". Enter 1 for the Subnet address, 1 for the Node address, then select OK. You are now connected to the controller. Using an RS 232/485 converter is similar to connecting to the controller, but the controller communications terminals are used instead of the IR Tool. For further details on NCP Palm, please click HERE.

Issue Is there is an application that will display the duress (panic) button alarm to the operator, when pushed, along with sound. Product Line TAC I/NET Environment I/NET Seven Automatic Page Display, Event Definitions & Sequences, User Defined Button  Cause Sample application / guide to program duress alarms in I/NET. Resolution I/NET provides various functions that allow it to provide a pop-up duress alarm, one feature is to use one (or many) graphic page(s) which automatically appear (pop-up) on activation of an alarm. Along with this, it is also possible to generate a sound either PC based or, the more preferred option, to an externally wired Buzzer / Siren at the same time.  The attached document shows a few steps as a guide to make a start on your own application using the following features: Automatic Page Display AMT Audible Alarm Event Definition / Sequences User-Defined Tools and Buttons If you are not familiar with these items you should refer to the TCON documents mentioned in the attachment.

Issue Need a M-bus device template for Multical 602 to use in Xbuilder Environment Vista 5.1.8 Xbuilder 5.1.8 Cause an Xbuilder device template for Multical 602 is required to integrate it with a Xenta Server (such as Xenta 913) Resolution Here is a M-bus device template for the Multical 602