Building Automation Knowledge Base

Issue  Unable to find or learn devices under Niagara. Environment R2 or G3 Niagara Cause Unable to find or learn devices under Niagara.  The LON device or devices may be configured to a different domain length.  Resolution To find devices under a different domain length download procedure click here

Issue DC1100 / DC1400 Optimiser / Compensator Controller switched contact output compatibility with existing Boiler / Pump / Control Valve Actuator control circuits. Environment Stand alone Optimiser / Compensator Controller CMC1801 CMC1802 CMC1803 CMC1826 CMC3803 CSMC3804 CSMC3805 DC1100 DC1400 Contacts Output Cause DC1100 / DC1400 Optimiser / Compensator Controller is to be connected to existing Boiler / Pump / Control Valve Actuator control circuits previously connected to Satchwell CMC or CSMC Optimiser / Compensator Controller. Resolution IMPORTANT NOTE Satchwell CMC / CSMC Controller output contacts are VOLT FREE. S-E Satchwell DC1100 / DC1400 Controller output contacts are LIVE MAINS VOLTAGE. It may therefore be necessary to install Relays between the DC1100 / DC1400 outputs and any Plant Control Circuits / Control System Devices under control. For example, where a 24v Valve Actuator was originally controlled via volt free contact outputs of a CMC / CSMC Controller then the Actuator may now need to be controlled via live mains voltage contact outputs of a DC1400 Controller. A 230v coil Relay will therefore need to be connected to the Valve Open contact output of the DC1400 Controller while another 230v coil Relay is connected to the Valve Close contact output of the DC1400 Controller. The 24v power to drive the Valve Actuator Open and the 24v power to drive the Valve Actuator Close should then be connected to the Valve Actuator via the contacts of the appropriate Relays. Should the 24v power source originally have been provided by the CMC / CSMC Controller and no other 24v power source is available on the existing installation then this may be remedied by the installation of a S-E TR 230/24v Transformer. N. B. Normally a Satchwell CMC or CSMC Controller would be replaced by a S-E Satchwell DC1400 Controller in order that existing Satchwell Sensors may be retained for connection to the DC1400 Controller. In the event that a Satchwell CMC or CSMC Controller should be replaced by a S-E Satchwell DC1100 Controller then any existing Satchwell Sensors will also need to be replaced. DC1100 Overview details appear here. DC1100 Wiring and Commissioning details appear here. DC1400 Overview details appear here. DC1400 Wiring and Commissioning details appear here. TR Transformer details appear here

Issue Outside dimensions of the enclosure for the MNB-1000? Part Number MNB-1000-ENC. Environment Plant Controller, MNB-1000 Enclosure for the Plant Controller, MNB-1000-ENC Cause Need to determine mounting clearances. Resolution Outside dimensions are 12" wide x 11 1/4" high x 2 5/8" deep. See the figure below, from the MNB-1000 Installation Instructions, F-27347-3. (Figure 3, p.3.)   Click here for a link to F-27347.

Issue What are the Drayton controller passwords? Environment Drayton DC2100 DC 2100 DC 3000 DC3000 Cause Password is not known. Resolution The password for the DC 2100 is 4012, for controller documentation please click HERE. The password for the DC 3000 is 012, for controller documentation please click HERE.

Issue Locating the IC3-Modbus documentation Environment Sigma IC3 Modbus Documentation Cause Unable to locate documentation. Resolution To download the IC3-Modbus Gateway.txt file click HERE. To download the IC3 configuration guide click HERE. To download the IC3 data sheet click HERE.

Issue When integrating I/NET into Vista; by default I/NET alarms do not show the station name, link name, or device name (point name). Environment I/NET Seven Vista 4.5 and up Cause The settings on the $AlarmColumns object in Vista do not have the I/NET column fields checked by default. Resolution To customize the Vista alarm queue with the proper fields for I/NET alarms please follow these steps. Click on the root level TAC Vista object in the Vista tree. Right click on the $AlarmColumns object and choose properties. Check the desired boxes in the Columns fields. Note: The link name selection will display the I/NET link name that the alarm originated from. Example: Link 5 South Campus The station name field will display the I/Net station name that the alarm originated from. Example: AHU5 The device name field will display the physical point name programmed within the I/NET controller. Example: OA Damper The site field is only needed when using DLA (distributed link architecture) and will display the name of the DLA site Example: Site 1 North Campus

Issue NXT will not communicate using RS-485 port 3 Environment R2/AX Niagara Cause Incorrect documentation of communication port number and RS-485 wiring diagram Resolution New document is available with correct comport number 4 and RS-485 wiring diagram.  To download a copy click on link T-NXT-MtgWiring Guide

Issue Do Xenta controllers support PT100/PT1000 sensors for measuring the temperature? Environment Xenta Controller TAC Menta PT100/PT1000 Temperature sensors Cause Requirement to measure the temperature using PT100/PT1000 Temperature sensors. Resolution PT100/PT1000 sensors are not supported within any of the Xenta controllers.  The following is a method to achieve this using Menta: When using PT100/PT1000 to connect to a thermistor input, Menta Logic is required to add a polynom using the expression block. It is also strongly recommended to implement some calibration software in Menta to allow for fluctuations in resistance for every input that PT100/PT1000 is connected to. If a sensor is replaced / changed, re-calibration will be required. Sample experiment results and Menta Logic's are available here.

Issue What is the part number for a flying lead temp sensor for Continuum? Environment Measuring air temperature in fan coil applications or exhaust ducts Cause On site or inability to find the HVAC Sensor Catalogue Resolution STD550 The 550 is intended for measuring air temperature in fan coil applications or exhaust ducts. The sensor, which are made of stainless steel, is delivered with a 2m (6.5 ft.) cable, PVC sheathed overall. Mounting details such as screw and clamp are included with the product. Description Duct Temperature Sensor STD550 Order Code 5123058400 Part Number STD550 For Continuum Systems   HVAC Sensor Catalog in pdf format

Issue Personnel are not deleting properly using a stand alone database in 1.82 and above Environment Continuum 1.82 Continuum 1.9x SQL Express 2005 (Stand Alone) Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There is a different mechanism used to delete personnel in SQL Express than was used in previous versions of Stand Alone databases (MSDE). The SQL agent is no longer available in SQL Express so a combination of batch files, SQL queries and Microsoft scheduler are used to accomplish this task. Resolution Several things to check: Ensure all controllers are online (a controller offline can cause deletions to not happen) A personnel listview with the deletepending attribute indicates True A controller was not deleted No areas were deleted Expiration date is not greater than 2031 Check the access distribution view for any errors At times for permission issues not all the components for deletion are configured by the Cyberstation installation and it's necessary to troubleshoot those components. Click here for a Word document describing these components to help troubleshoot.

Issue Replacement of Obsolete ZVX 4302 , ZVX4302, ZVX-4302 Environment site with ZVX 4302 that needs to be replaced ZVX4301 ZVX4302 ZVX4303 Cause Obsolete ZVX 4302 valve , T-type, 3port, 230V with Actuator, screwed, 3/4 inch size. The ZVX 2-port Flow Control and 3-port Diverter Valves are for the regulation of low pressure heating and chilled water circuits where on/off control is required. Resolution The Satchwell ZVX 4202 was just one specification among many of similar ZVX series Zone valves. Details of the complete range of ZVX 2-port and 3-port Zone Valves from the Satchwell “Options” range appear in the pdf attached in the link at the bottom of this article (pdf). The ZVX range of Zone Valves were “badged” Satchwell and, to the best of my knowledge, were of ORKLI manufacture. Please note at the present (2011) there is no direct replacement for the Satchwell ZVX series of Zone Valves. This may require the pipe and fittings to be replaced or altered. At present the replacement for the Satchwell ZVX range of Zone Valves still appears to be the ERIE VT range of Valve Bodies and ERIE AG/AH range of Actuators. Replacement details are included in the following extract from an earlier cross-reference document produced by Gina Kimmins whilst in the Product Sales division of TAC / Satchwell WHEN ORDERING BODY & ACTUATOR TOGETHER, DROP THE "A" FROM THE ACTUATOR EG. VT2231G13A230 AND USE THIS PART NUMBER TO ORDER   Here is the documentation for the Satchwell ZVX 2 port and 3 port zone valves. VT Valve Body and AG / AH Actuator that currently replace the ZVX ERIE POP TOP Datasheet and ERIE POP TOP Install Guide

Issue Replace Invensys Actuator Model MA5-419-500-0-3 Environment Damper Control Actuator site Cause Replacement Specifications for Obsolete Invensys MA5-419-500 which is a Two Position Damper Actuator, SR, 240V, 50 Hz, 60 lb-in, w/SPDT Aux. Switch Resolution The closest replacement would be the MD5B-24(-S)/-230(-S) On/Off or 3-point 24 V AC/230 V AC Damper Actuator 5 Nm (45 in-lb). Note: This is a Rockford, Illinois offering, which we would not normally have offered this in Europe in the past. There is a range of Non-Spring Return Damper Actuators detailed in Pages 54 and 55 of the below Schneider Electric Catalogue. Similarly there is a range of Spring Return Damper Actuators detailed in Pages 56 through 58 of the below Schneider Electric Catalogue. Damper Actuator Accessories are shown on Page 59 of the below Schneider Electric Catalogue. Schneider Electric HVAC Valve and Actuator Catalogue  

Issue Dumping or reloading a NetController using HyperTerminal. Environment Windows HyperTerminal CX9900 CX9400 CX9200 Command Terminal Configuration Guide Infinity and Continuum Window Interface Cause Not known cause. Resolution Click here for instructions on using HyperTerminal to dump or reload controller.  For full details on using the Window interface as used on Infinity and 1st Generation Continuum controllers, you can download the Command Terminal Reference Guide.

Issue Satchwell CZU Mk 1 Zonemaster Controller requires replacement. Environment Stand alone Fan Coil Unit Temperature Controller. Satchwell CZU Mk 1 Zonemaster Controller. CZU 1201 CZU 1202 CZU 1203 Cause Obsolescence of Satchwell CZU Mk 1 Zonemaster Controller. Resolution OVERVIEW Replacement of Satchwell CZU Mk 1 Zonemaster Controller with S-E Satchwell CZU Mk 4 Zonemaster Controller. The CZU 4201 may be used to replace the following CZU Mk 1 Controllers :- CZU 1201, CZU 1202, CZU 1203 N. B. CZU 1201 Controllers provided an additional -9 to +9 V d.c. output enabling connection to peripherals such as the Satchwell NSU 1401 Night Set-back Override Unit, TSU 1402 Two Step Auxiliary Unit and SSU 1403 Signal Selector Unit. CZU 1202 and CZU 1203 Controllers provided an additional -0.5 to +9 or -9 to +0.5 V d.c. output enabling connection to the Satchwell NSU 1401 Night Set-back Override Unit. Additional outputs are not provided on the CZU 4201 Controller and in those applications where these are required then it will be necessary to consider an alternative Controller to the CZU 4201. Details of the CZU 4201 may be viewed here.   CZU Mk 1 CONTROLLER - INTEGRAL TEMPERATURE SENSOR APPLICATION CZU Mk 1 Controllers were manufactured with an integral Temperature Sensor. Adjustment of setpoint was undertaken by means of a dial mounted on the front of the Controller housing. This enabled the Controller to be installed in the controlled space. The CZU 4201 however is intended to be installed either in or on a Fan Coil Unit casing or in a ceiling void. No setpoint dial is mounted on the front of the CZU 4201 housing, thus precluding installation of the Controller in the controlled space. Where an existing CZU Mk 1 Controller is installed in the controlled space and is to be replaced, it will be necessary to install an Adjustable Room Temperature Sensor in the controlled space in order that a CZU 4201 may be utilised as a replacement. The S E STR 612 Adjustable Room Temperature Sensor may be utilised for this purpose. Details of the STR 612 may be viewed here. Any existing Actuator / Valve Body assemblies connected to the CZU Mk 1 Controller may be retained for connection to the CZU 4201.   CZU Mk 1 CONTROLLER - EXTERNAL TEMPERATURE SENSOR APPLICATION In some instances an existing CZU Mk 1 Controller may have been installed with its integral Temperature Sensor disabled. In such instances a remote Satchwell Adjustable Room Temperature Sensor such as the DRT 3451, or a remote Satchwell Duct Temperature Sensor from the DDU range of Sensors may have been installed and connected to the Controller.. Any existing remote Satchwell Temperature Sensors may be retained for connection to the CZU 4201. Should the remote Satchwell Adjustable Room Temperature Sensor require replacement then this may be replaced by an S E STR 612 Adjustable Room Temperature Sensor. Details of the STR 612 may be viewed here. Should the remote Satchwell Duct Temperature Sensor require replacement then this may be replaced by an S E STD 670 Duct Temperature Sensor. Details of the STD 670 may be viewed here.

Issue Self-Registration Error while installing Remote Workstation (some of the "dll" files are not installed). The following files did not self-register or unregister. Environment TAC Vista 5.0.X Remote Workstation Cause When uninstalling the TAC Vista Remote Workstation some of the "dll" files will not un-install from "TAC Shared" folder (Find the TAC Shared folder in "C:\Program Files\Common Files). Due to this, while reinstalling the Remote Workstation pop-up an error-"Self-Registration" and few "dll" cannot install, then the Installation terminates. Resolution Uninstall the Remote Workstation. Delete the TAC Shared folder from C:\Program Files\Common Files Reinstall Remote Workstation. Note: Install .NET Framework 2.0 before installing the Remote Workstation software.

Issue How can a communication heartbeat time be detected in Menta? Can you detect if a value has not changed for more then a specified time period? Environment Menta Cause There are multiple methods to detect a timeout scenario and which method to use will likely depend on the specific criteria of your application. The included examples are intended to indicate some of the options available that can be built upon to customize your application. Resolution These methods can be used to detect if another device has stopped communicating or if another portion of your process logic is stuck. Timeout Simple (Click image for AUT file) This macro block will output a value of one when the input value has not changed for the DelayOn time period and you do not require the previous value for processing. Timeout Complex (Click image for AUT file) This macro block will preserve the last value for use in your process logic if that is necessary.

Issue A GCM / LCM stops working and displays the error message "Insufficient System RAM".  It no longer responds to information requests via the front panel keyboard/display nor via XPSI software connected on either of the available serial ports. A power cycle restores functionality but only for a limited amount of time (ie: hours or days). Environment Network 8000 GCM-84000 series GCM-86000 series LCM-84000 series LCM-85000 series LCM-88000 series Cause Free system ram drops below minimum requirements: Any GCM with sys ram below 18k Any LCM with sys ram below 10k Resolution The amount of free system ram must be kept above minimum requirements. Use Tech Bulletin 95-33 for troubleshooting the GCM / LCM.  It is a comprehensive guide providing both hardware and software suggestions that will increase free system ram.

Issue DC1100 / DC1400 Optimiser / Compensator Controller Alarm LED is illuminated. Environment Stand alone discrete Controller in Alarm mode. DC1100 Optimiser / Compensator Controller. DC1400 Optimiser / Compensator Controller. Cause DC1100 / DC1400 Optimiser / Compensator Controller Alarm LED has been triggered by the occurrence of one of the following conditions: Sensor Input is short circuit or open circuit and / or out of range. Boiler Temperature at least 10 deg C above Boiler High Limit value. Boiler Temperature below Boiler Low value after one hour. Compensated Flow Temperature below Flow Low value after one hour. Resolution DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be viewed and / or cleared using the following procedures. VIEW ALARMS DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be viewed as follows :- Turn Front Panel Selector to SET Using Up and Down Arrow Keys move Screen Display Arrows to SYSTEMS MENU Using Up and Down Arrow Keys move Screen Display Arrows to TEMPS & ALARMS Using Up and Down Arrow Keys move Screen Display Arrows to VIEW ALARMS CLEAR ALARMS DC1100 / DC1400 Optimiser / Compensator Controller Alarms may be cleared as follows :- Turn Front Panel Selector to SET Using Up and Down Arrow Keys move Screen Display Arrows to SYSTEMS MENU Using Up and Down Arrow Keys move Screen Display Arrows to TEMPS & ALARMS Using Up and Down Arrow Keys move Screen Display Arrows to CLEAR ALARMS Using Up and Down Arrow Keys Select Pass Number (0112) and ENTER In the event that an Alarm is not cleared by the above procedure and the Alarm LED does not extinguish then the Sensors and / or installation in general should be checked further. DC1100 Optimiser / Compensator Controller overview may be viewed here DC1100 Optimiser / Compensator Controller details and menus may be viewed here DC1400 Optimiser / Compensator Controller overview may be viewed here DC1400 Optimiser / Compensator Controller details and menus may be viewed here

Issue Customers wanting to use a Barcode Reader for door access Environment Access Control site wanting to use Barcode Readers Cause Barcode Readers often are a higher  Resolution I/NET The SCU is the best you could have so that makes it easier with memory requirements and so forth. Since you have the SCU, set it up for 26-bit Wiegand (2 parity bits and 24 data bits). It would look like this: e eeeeeeee eeeeooooooooooooo o That is a 1-bit starting bit, even parity, 8-bit facility code, site number, card number, 16-bit segment, and the 1-bit ending parity (26 bits all together). That is how many data bits the reader normally takes. 26-bit Wiegand is typical and most common. The true bits are the facility code, site and card number. The beginning and end is the parity. For more information, see TCON300, beginning on page 9-59. This is the key card translations section, and may be valuable in figuring out the solution to the bar code reader. Lastly, one idea is to contact a company called RFIDeas.com. They make a bar code reader that may be a solution. If the bar code reader is outputting a card number larger than 16 digits, convert it to 26-bits of Wiegand data (it can handle up to 64-bitWiegand). If it goes over 64-bit, they have a special firmware which allows up to 254 bits of wiegand data. With the SCU, the 26-bit is the standard. Code 128 is used to barcode INET products. The Cypressworld CVX-1300 is an alternate solution for connection between the I/NET SCU and the Barcode Reader. Continuum Code 39 is used to barcode the serial number on Continuum and Pelco boards.  Most readers can auto switch between these and other code types.  

Issue When editing a personnel object an error is received "Input string was not in a correct format" using 1.82 or 1.90. Environment Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Microsoft released .Net 2.0 SP2 which caused an issue with our code in the personnel area. Resolution The version of Continuum you are using will determine the solution you need to use. 1.82 - Uninstall .net 2.0 SP2 1.90- Install the following hotfix  Click here to download The issue was corrected in 1.91.