Building Automation Knowledge Base

Issue The XML Automation Server application on the WebClient Server does not open when a remote WebClient browser tries to access WebClient. WebClient does work from the browser on the WebClient server itself but can't be accessed from another PC. The XM Automation Server keeps closing by itself. Environment WebClient Windows Server 2003, Windows Server 2008, Windows 7 Cause DCOM Permissions have not been set properly to allow access to these WebClient components. Resolution Confirm that DCOM permissions have been set properly. Follow the steps detailed in the section "Configuring DCOM Default Security Settings" starting on page 100 in the WebClient Installation Guide, paying particular attention to the NETWORK SERVICE account. Please see the link below for the relevant section from the WebClient v1.94 Installation Guide. DCOM Permissions excerpt from 30-3001-835 webClient Planning and Installation Guide

Issue What is the pinout diagram for the interface cable connecting a computer to a Network 8000 LCM? Environment Network 8000 Cause cable not available for purchase Resolution Diagram available here.

Issue M-AF230 is no longer available for ordering. Environment M-AF230 8750000010 MD20SR MD20SR-24/230T Cause Obsolete actuator needs replacement Resolution The M-AF230 is replaced by MD20SR-24/230T. Please see PA_00153 and other related documentation for more details. 

Issue Cannot order the VZ*8 valves, its no longer available.  Environment VZ*8 VZ*08C Cause A new line of VZ valves is now available. Resolution The old VZ series actuators have been replaced with a new. The old (VZ*8) is replaced by the VZ*18. for more information and details, please see PA_00156 and the related data sheets. Click here.  

Issue Which accessories and linkage kits are available? Environment MD5 MD10 MD20 MD40 AF LF Damper actuator Cause Accessories availability for damper actuators Resolution All available accessories are available in this document.

Issue Unable to link an I/A Series R2 UNC to a McQuay Microtech III DAC or SCC to clear alarms via nviClearAlarms. Product Line TAC IA Series Environment I/A Series R2 UNC-410 UNC-520 Cause The nviClearAlarms is used to clear faults, problems, warnings, etc. from a McQuay Microtech III controller.  The variable used by McQuay is a UNVT (user network variable type) and requires a combination of objects to connect and control. Resolution This article specifically details the interface to the newest Microtech III shadow objects as shown below.  The same general solution can be applied to other McQuay devices as needed. McQuay Microtech III Applied Air Unit Controller DAC - MtIIIAhuDac01B (80:00:25:56:0A:03:04:B2) McQuay Microtech III Applied Air Unit Controller SCC - MtIIIAhuScc01B (80:00:25:55:00:03:04:B2) Note: Update the lonMicrotechIII jar file to version 535b or higher.  An issue with UNVT definitions prevented the DynamicMux object from properly interfacing to the nviClearAlarms on the MtIIIAhuScc01B shadow object.  The lonMicrotechIII-2.302.535b.zip file can be downloaded from The Exchange Download Center Add a DynamicMux object from the tridiumx lonworks jar (conversion folder) to the workspace.  Connect the DynamicMux object to the nviClearAlarms input. Add a Program object to the workspace.  Edit the Program object and add the program text from the appropriate text file.  Compile the Program object and link to the DynamicMux. Download text file ... MtTIIIAhuDac01B_Alarm Download text file ... MtTIIIAhuScc01B_Alarm Add a Multistate Output object and configure the Visual stateText to the desired values shown below.  Link the Multistate Output object to the Program object. 0 = None 1 = ClearAllFaults 2 = ClearAllProblems 3 = ClearAllWarnings 4 = ClearAllAlarms default = Error

Issue How does the import/export (IE) system work in the Continuum controllers? Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller. The principle is that the value of a controller point that is referenced by other controllers on the network only needs to be sent out when it changes, much like the BACnet COV which stands for Change Of Value. The two parties involved in the IE transaction are the controller that owns the point (the owner) and the controller(s) referencing the point's value (the subscribers), a second CX controller may also be involved and acting as a router when a value is imported/exported from/to a remote field device under a remote CX. Resolution Read more in the attached document, Understanding Continuum IE System.  See how to correct Import Export tables KBA

Issue How to configure an analog input on a DMS MicroSmart controller as a voltage input. Environment MSC-MPC (revision 10) and MSC-MPC-001 (revision 11) MicroSmart controllers Cause Adding new voltage sensors Resolution Click here for an explanation on how to configure an analog input as a voltage input

Issue Can a BS5308 part 1 type 1, 2 pair individually screened cable be used for M-Bus communications? Environment M-Bus Communication Cables Cause A BS5308 part 1 type 1 cable was installed for Modbus communications, but it was then found that the communications were M-Bus Resolution The correct cable to use for M-Bus is J-Y(ST)Y.  These indoor telephone cables transmit analogue or digital signals; Aluminium-laminated plastic foil static screen with tin-plated drain wire minimises the interference of high frequency, electromagnetic field;TP structure minimises crosstalk. For the datasheet please click HERE. The BS5308 part 1 type 1 cable can be used, and the chart below shows the calculations used to establish this. For the cable datasheet, please click HERE. For the Excel spreadsheet please click HERE.

Issue The power supply filter in a 196/296 496/596 controller's power supply unit needs replacement. Product Line Other, Satchwell Sigma Environment BAS Sigma Cause The power supply filter has gone bad. Resolution The power Supply Filter used is a Tyco-Corcom type 2VK1. RS Components order code 2509234656. Note: This must only be replaced with that exact part number. No "near equivalent" is allowed for safety and performance reasons. Click here to view the Data Sheet for the Tyco-Corcom type 2VK1.pdf.

Issue Loading or upgrading new firmware into a 102-AX VAV controller that resides under a Jace controller Environment Jace Vista Xenta 102-AX Firmware Cause Updating firmware in a 102-AX VAV controller that has previously been commissioned into an existing network Resolution Please click here to see a step by step procedure document on the recommended procedure for this task.

Issue There are many files located in the c:\ Micronet\binary\vcommon folder with names like: 20101024.AEH to 20121119.AEH, they vary in size between 1 kb to 750Mb. What are these files and why are they filling the hard drive? Environment MicroNet View InTouch Cause The file type *.AEH stands for Alarm Event Handler and is the Wonderware Logger (WWLogger) file. The WWLogger file contains information about an application, including InTouch error and warning messages. Resolution PIB – 00.07.10-3 lists the historical files that can be safely deleted from MicroNet View to conserve space or before backing up the site.

Issue High and Low Setpoint Limits on MN-HPFC Controller do not appear to be operating properly.  The local high setpoint limit appears to limit only the high heating setpoint and the local low setpoint limit appears to limit only the low cooling setpoint.  What do I have configured wrong? Environment MN-HPFC with local setpoint control Cause As designed. Resolution As noted in the MicroNet Heat Pump / Fan Coil Controller reference manual, F-26174. the "Local Hi Lmt Spt" defines the Maximum value for the local heating setpoint and the "Local Lo Lmt Spt" defines the Minimum value for the local cooling setpoint for use when the heating/cooling setpoint is set through the MN-SDK deluxe sensor.  This operation is also documented in Technical Bulletin 01-01.

Issue Unifact Pro - Master and Slave controller ratio Unifact Pro - Number of controllers on a LAN Environment Unifact Pro Cause What is the Master to Slave controller ratio of Unifact Pro controllers on a LAN? What is the maximum number of Unifact Pro controllers on a LAN? Download here the Unifact Pro Datasheet Resolution There is 1 master to a maximum of 3 slaves. A single Unifact Pro LAN can support up to 80 controllers. Note: A S-Link sensor wired to the master can be shared by up to 3 slave controllers. If fan speed control is used then S-Link sensors cannot be used on the slaves.

Issue It is not possible to write to any parameter in the IAC400, IAC600, MMC3601 or MMC4601; reading is not a problem. This is because VisiView is attempting to write an EEPROM value that is not supported by these devices. IAC420's are not affected. VisiSat is able to write parameters to all these devices. Environment VisiView Cause Global time update is currently being transmitted to Group 1. This has been corrected to transmit as Group 0. Resolution Install service pack 3 Click here to download service pack 3 Click here to view the release note for service pack 3 Click here to download the release note for service pack 3

Issue List of Tables and Offsets for MicroNet 50 series, 100 series, and IACs Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment VisiSat VisiView MicroNet View Cause Need to define the Tables and Offsets for MicroNet 50 series, 100 series, and IACs. Resolution Click here to download the list of tables and offsets for the MicroNet range of controllers. Click here to download the list of tables and offsets for the IAC range of controllers. Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 and PA-00528 

Issue What's a functional equivalent to the SHM-001 or SHM-002 Short Haul Modems used primarily with DMS control systems? Environment DMS Cause Failure of the SHM-001/002 short haul modems Resolution Use the Model 1000SM from Patton Electronics:  http://www.patton.com/products/product_detail.asp?id=98 Original data sheet for the SHM-001 and SHM-002

Issue The TA210U controller is obsolete since many years, but the manual is sometimes still requested Product Line Field Devices, TAC Vista Environment TAC210U TA210U 2107030QRW 2107030QRT 0844427005 0844428005 Cause Old controller Resolution The (Swedish-only) manual can be found here: TA210U Controller User Manual (L3238001.pdf).

Issue TA 240 U Tour Andersson Controller Environment Site with a TA 240 U Tour Andersson Controller Cause Controller needs change in programming Resolution Attached Manual for the Tour Andersson 240 can be found HERE. 

Issue Do extended logs have accurate entries for the spring and fall time change periods?   Environment CyberStation, all Continuum controllers, extended logs, controller logs. Cause What happens to extended log data during time changes? Resolution When the clocks are turned back, log data in the controllers will not be updated for the time interval of the change and therefore that data will not be collected by the extended logs. When the clocks are turned forward, log data in the controllers is logged twice for the time interval of the change and therefore that data is collected twice by the extended logs.   This occurs due to the fact that each log entry in the controller does not consist of a value and a timestamp. The timestamp we see in a report is calculated by the time of the last log entry (LastLogTime) in conjunction with the configured logging interval (LogIntervalSecs). This mathematical calculation saves memory in the controllers. Extended logging is the mechanism most sites use to store, and report on data that is in excess of the amount of data stored in a controller. The extended log engine automatically collects the controller log data before it is overwritten. An added benefit of using extended logging is that the data can be easily backed up via several strategies such as database backups and/or running extended log archiving applications. In the controllers, not only is the memory limited, but the data is stored in volatile RAM, so extended logging is a more robust and long term strategy of collecting and storing the data. Extended logs can be set up on any of the automatic log types (LogInstantaneous, LogAverage, LogMinimum, LogMaximum).  During a period when the clock is moved forward, (for example, 2:00am Sunday March 11, 2012 on the east coast of the US), reports may display timestamps that essentially never existed (in this example 2:00am to 2:59:59am). It is recommended that these entries are simply ignored or crossed out. The period when the clock is moved backward is more difficult, if it is critical that data be captured for the duplicated time. An example is Sunday November 4, 2012. At 2:00am on the east coast of the US the clock is set back one hour. This means that the times from 1:00am to 2:00am occur twice. However, extended log reports will only show one set of data for the reason described above. The reports will show the first 1:00am to 2:00am data; the second 1:00am to 2:00am data needs to be captured separately.  If point log data must be captured for the duplicated timeframe, additional point configuration and Plain English (PE) programming must be used to capture and timestamp the realtime data values for the duplicated timeframe. This involves creating a numeric with a manual log  for each critical point which mirrors the live data value of the affected InfinityInputs, InfinityOutputs and InfinityNumerics. In addition, an InfinityDatetime point with a manual log must be created, one in each controller for each different loginterval of the points being mirrored in that controller. The PE program(s) capturing the point values will write the controller's date system variable to this InfinityDatetime at the same time it writes the live point value, thereby creating a timestamp that will be used for reporting. The last step will be writing the mirrored points and their corresponding timestamps to a file on disk and then printing and/or backing up that file for redundancy.  Click here to download a zip file containing sample dump files and a readme. This is an example of one way to accomplish the above data capture.