Building Automation Knowledge Base

Issue To order the correct version of this controller. Environment IAC600 Controller, IAC 600 Controller, MER207 Chip Eaton Williams BT Controller. Cause Ordering the incorrect version of controller will not allow the Eaton Williams scheme to operate correctly. Resolution To order the MER207 version of the IAC600 controller use the IAC600-S specification. To download the Visisat 2.1 MER207 stencils, please click here. Copy the downloaded file to your computer and unzip the file. The files will be unzipped to a folder "Satchwell" with the mer files in the correct folder structure underneath.The files will unzipped to a folder "Satchwell" with the mer files in the correct folder structure underneath. 1        Copy the folder Satchwell including its sub folders. 2        To your computers C: drive. 3        This will put the required MER files in the correct places ready for use. Now you can choose the stencil in VisiSat, when you need it, by selecting "open Stencil" and navigating to "C:\Satchwell\Binary\VisiSat\EN\Visio\Specials Products.vss.  

Issue In a new installation, the ProView display (never configured previously) is powered and wired to the LON trunk back to a UNC-520.  In the station's LonWorks Service, a Find completes but the ProView display does not appear. Environment Niagara R2 version 529 or newer ProView Cause "New" ProView displays are somewhat unpredictable when added to a Niagara R2 station for the first time. Once it has been commissioned and programmed, its behavior improves. Resolution Add the appropriate shadow object from the 'distech' jar file (Ecdis210) to a container under the lonTrunk. The programID for the ProView display is:  90:0:83:32:b:84:4:15 In the LonWorks Service - Lon Device Manager, highlight the just-added Ecdis210 object and Commission. Use the SrvPin method to learn the neuronID (ProView display's service pin is located on the bottom to the left). Once the commission process complete, ProView is now available for programming.

Issue How to configure a Niagara R2 UNC as a LON Node  Environment Niagara R2 Cause How to configure a Niagara R2 UNC as a LON Node  Resolution Steps to configure UNC as LON Node

Issue What are the steps to reload a controller Environment CX controllers BCX controllers ACX controllers NCII NC2 CX9680 I2 controllers B3 controllers Cause Point or program not available, receiving 5121 error Resolution To reload a controller follow the steps below: In continuum explorer select Options/Send to controller options and either the middle choice or bottom choice depending how which and how many controllers to be reloaded The most common and the default is to set to the middle setting to reload only the controller selected. Now select the controller to reload and right click and select send to controller The distribution located in the icon tray can be launched from a double-click to watch the progress of the reload.

Issue Niagara G3 (NiagaraAx) Open NiCS (Niagara Compatibility Statement) Environment Niagara G3 (NiagaraAx) Cause NiCS attributes: Niagara G3 (NiagaraAx) licenses has brandId="TAC". A station's ability to accept NiagaraAx data from another NiagaraAx station depends on the accept.station.in="*" field in its license. A station's ability to share NiagaraAx data with another NiagaraAx station depend on the accept.station.out="*" field in its license. A station's ability to allow a copy of WorkBench to connect to it and engineer the station depends on the accept.wb.in="*" field in its license. A copy of WorkBench's ability to connect to a NiagaraAx station to engineer it depends on the accept.wb.out="*" field in its license. (Where "*" is the brandId) 'Open' licenses may be required when there is a need to: Allow sharing of a station's NiagaraAx data to another station which has a different brandId in its license. Accept NiagaraAx data from another station which has a different brandId in its license. Allow a WorkBench connection from a copy of WorkBench that has a different brandId in its license. Allow a copy of WorkBench to connect to a station which has a different brandId in its license. Resolution Niagara G3 open NiCS licenses have the following: “accept.station.in="*”; “accept.station.out="*”and “accept.wb.in="*”and “accept.wb.out="*”. The "*" is a wildcard designation to allow all brandIds. You can specify new licenses to have open NiCS by selecting the 'Request open NiCS (Niagara Compatibility Statement)' checkbox in the I/A Series G3 license request forms. You will need to purchase the part IA-LIC-CHG for each existing Niagara G3 that needs to have an open NiCS. 

Issue How many controllers can be connected to an ASD bus before a repeater is required? Environment Global controller with an ASD bus connected (GCM, UNC, ENC, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, SIM-YORK) ASD controller (LIM-1,MicroFlo II, MicroZone II, MN-ASDI integrator, PEM-1) Cause Requirements for ASD bus installation. Resolution A maximum of 32 nodes are allowed for each ASD bus segment.  Each controller and repeater count as one node, so a bus segment with a master (GCM, UNC, etc.) and a repeater can have 30 other nodes on it ( MZII, MN-ASDI, etc.) For details, See the Network 8000 Hardware Installation Practices manual, F-23061-1, "Network & Communication Wiring", "Repeaters - RS-485".

Issue How to filter in a listview AlarmEvent based on the EventNotification Environment Continuum Cause Continuum pre 1.91 did not allow filter in a listview AlarmEvent, based on the EventNotification Resolution See Continuum CyberStation Release Notes Version 1.91(Downloadable here) Fixed Problems 4.007 Cannot filter an AlarmEvent table based on the EventNotification using the query wizard (21101) Find another way to filter or upgrade your version of Continuum.

Issue Sigma IC-GEN 4.05 SEB and supported operating systems Environment Sigma IC-GEN release 4.05 SEB Cause New installation of IC-GEN and customer wants to know the latest version and its supported operating system(s). Resolution The latest version of Sigma IC-GEN is Sigma IC-GEN 4.05 SEB. Release 4.05 SEB IC-GEN provides rebranding to Schneider Electric. There are no other changes except for new build and release numbers. This release is shown as Sigma IC-GEN Build 3.43.07 in the installer, uninstaller and ‘About’ box. This release supersedes the previous Release 3.17 for IC-GEN (shown as Build 3.34.12 in the About box and Build 3.34.24 when uninstalling). This version is supported to run on Microsoft Windows XP Professional (32-bit) and Microsoft Windows 2000. (Microsoft Windows Vista and Windows 7 are not supported) Refer to 'Sigma Release 4.05 SEB IC-GEN' release notes for details. The IC-GEN 4.05 SEB software can be downloaded from the Exchange Extranet. Once logged on, go to 'Products' > 'Satchwell' > 'Sigma' > 'Downloads' > 'Upgrades and Software'. The release note can be downloaded from 'Products' > 'Satchwell' > 'Sigma' > 'Release Notes' > 'Options'.

Issue How to set an LNC-100 back to factory-default settings. This will erase all block programming and device configuration. Environment Network 8000 LNC-100 and related controllers based on the GCM-861X0 series platform, including the GCM-86110, GCM-86120, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK Cause Sometimes it is necessary to manually clear the controller EEPROM in order to reload a database. Resolution Follow the steps below: Backup the controller database. Clear the controller's EEPROM. This is accomplished by pushing the reset button and the EE CLR button and holding both for at least 20 seconds before releasing. The reset process is complete when the top two red LEDs on the right edge of the controller begin blinking in their normal sequence (second LED blinks twice as fast as top LED). This process will clear the user programmable memory (including all block programming), returning the controller to its original factory condition. This step is important as it insures there will be no conflict between the new revisions firmware and the older version. The procedure above is excerpted from Technical Bulletin 99-27 , steps 1 and 2.

Issue What issues, if any, are there to replacing Workplace Tech 5.7.7 with 5.7.6 on a Windows XP computer? Environment Workplace Tech 5.7.7 and 5.7.6 Cause none Resolution Workplace Tech version 5.7.7 comes with new firmware for the MNB-1000.  It is better to use version 5.7.7 with any MNB-1000 controllers installed with the new firmware.  This is especially true on job sites adhering to GSA guidelines. If the computer is only used with MNB-1000 controllers running previous firmware releases, then re-installing version 5.7.6 won't create any issues. Review the release notes below for more details. Release Notes - WorkPlace Tech 5.7.7

Issue A replacement for VisiView is required. Environment Satchnet VisiView Cause The VisiView software is now obsolete. Resolution VisiView can be replaced using a SmartStruxure Automation Server or TAC Xenta 555 Web server. Both the SmartStruxure Automation Server and the Xenta 555 provide web interfaces so that the customer can view their HVAC equipment graphically using an appropriate Web browser. Both the SmartStruxure Automation Server and TAC Xenta 555 Web server communicates with either IAC or Micronet controllers. Further information on the Micronet Transition to SmartStruxure can be found in PA-00228 The Xenta 555 is programmed using TAC Xbuilder, which allows data to be presented in a graphical format. Further information on the Xenta 555 can be found here.

Issue Are examples available to show how to write Plain English programs and create points for a Modbus RTU X Driver linked to Schneider Electric Power meters? Environment Modbus RTU X Driver Schneider Electric PM700, PM750 Power meters. Cause Requirement for some examples to see how Modbus RTU programs can be written to poll for the data in a 3rd party Modbus device. Resolution The attached example was written by an application engineer in the UK to extract data from the Schneider Electric PM700 and PM750 meters. This example provides the mapping of data for these 2 specific meters, but the polling principle utilized in the Plain English programming can be applied to any Modbus RTU interface Download file here. 

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 When trying to run Workplace Tech 4.0 for the first time, it may not start successfully, and an error message will be displayed: "Microsoft Visual C++ Runtime Library, Runtime Error!" Environment Workplace Tech version 4.0 Visio 2002, SR1 Windows XP Professional, Service Packs 1-3 Windows 2000 Professional, Service Pack 4 Cause The error is typically caused by not initializing Visio 2002 before running WPT 4.0 for the first time. Resolution See Technical Bulletin TB04-02, which details the issue and resolution.

Issue When using a USB to RS-232 adapter and an MN-CIM, cannot connect to MicroNet 2000 controllers. Receive an ERROR = -510. The problem has also been seen on laptops with an integral serial port. Environment Laptop computer running the MN-CI or MN-FLO-BAL software tools,  any version MN-CIM Controller interface Module Cause One cause of ERROR = -510 is that the serial port or USB to RS-232 adapter does not supply enough power to the "port-powered" MN-CIM. When the CI software is running, but not communicating on the U-LINK, it requires only 12 mA at 5 VDC. To communicate on the U-LINK, the MN-CIM requires 14 mA at 5 VDC from the DTR control line of the port.  Some computers have a mechanism to sense the increased current draw and shut down the DTR line. This loss of power causes the MN-CIM to reset, and after 3 attempts to communicate the MN-CI software issues the ERROR= -510 message. Resolution See Technical Bulletin 01-104 for information  on the Patton Electronics power supply adapter, model 3PMF9-BC.

Issue I/A Series R2 Enterprise Server and I/A Series G3 Enterprise Network Server redundancy solution Environment I/A Series R2 and I/A Series G3 Cause Continuous uptime is required for I/A Series system and data. Resolution The recommended software for I/A Series redundancy is from Stratus Technologies (http://www.stratus.com/). Contact your local Stratus Technologies office or distributor / partner for details. Also refer TVDA document 'everRun Mx with SE Building Management Systems'.   Frequently asked questions: What does Stratus Technologies solutions do? It delivers simple, affordable, continuous uptime for any Windows application running on unmodified, industry-standard server hardware. This high availability solution protects applications, data, and operating systems from faults, failures, and dropped network connections. How does it work? Stratus software synchronizes two standard Windows servers and creates a virtual application environment that runs on both of them simultaneously. If one server fails, the Windows application continues to operate uninterrupted using the other server with no failover, transaction rollback, or other complex procedure. Are there any special I/A Series licensing requirements? The Stratus solution requires a single I/A Series license only. Only one copy of the Enterprise Server / Enterprise Network Server is required. There are no special properties or license requirements. Which Marathon product should be used? All Stratus products can be used. The particular Stratus product will be determined by the end-user hardware and performance requirements. Are there any special properties that need to be set up in the Enterprise Server / Enterprise Network Server when using the Stratus product? The installation of I/A Series (R2 or G3) is no different than installing the product on a standard Microsoft Windows platform. Keep in mind; if the Microsoft Windows platform is running IIS, then either IIS or the Enterprise Server / Enterprise Network Server will have to run on something other than port 80. Both applications cannot utilize the same port.

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 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 Some issues which this article covers are: What rules or recommendations should be used with Indirect and Global Points? Why might a global point not change? Attempting to alter a global AO/DO points' value/state, by "Point Control" without "Manual Mode" being used, and the change does not take place. (Referred to as Global Output Retentive Feedback.) What scan rates should be used for global / indirect points? Product Line TAC INET Environment I/NET Software Cause Often within a system, a point's status or value within one controller has to be shared or used in other controllers connected to the system. An example could be an outside air temperature sensor connected to a controller. The value of the outside air temperature in that controller can be transmitted across the I/NET network to be used in algorithms in the other controllers. The I/NET software and firmware provides the mechanism to transmit and receive point data system wide. The outside air temperature point in this example would be called a "global point." The receiving points within the other controllers that reference and thereby mimic the global point's temperature value are called "indirect points." Resolution Each controller is capable of a total of 128 global and indirect points. Global points are used to share information from one controller to another. If a point is not a global point, the state or value of that point is available only to other points in the same controller. If a point is specified as global, you may use it to control an indirect point in another controller. Any internal or external point may be designated as a global point. When a point is defined as global, a corresponding indirect point must be set up in the additional controller(s) to receive the global point's data. The global point must be designated with the appropriate globalisation level. There are four (4) different levels of globalisation, as shown below: Local: This point provides information only to this controller. A global setting of "Local" indicates that this point is not a global point. LAN: This point may provide information to an indirect point in any device connected to this controller LAN. Link: This point may provide information to an indirect point in any device connected to this controller's Host LAN. This setting WILL NOT send global data across links headed by NetPlus Routers. System: This point may provide information to an indirect point in any device connected to the I/NET system including ETHERNET. This setting WILL send global data across links headed by NetPlus Routers. Global points "broadcast" or send their state/value to corresponding indirect points. The frequency of the broadcast depends on the point type. All global point types broadcast under the following conditions: The controller has been restarted, either by a power restore, the controller's red reset button has been pushed or the database, DCU0000.sav file, has been "Restored." A global point has been changed from "Automatic" to "Manual" or from "Manual" to "Automatic." This does not apply to the Test Mode. A global point changing to or recovering from the "old data" state due to either a communications failure, or an analogue input point falling outside or re-entering its sensor limits (defined within the 'Resident Points' editor). Global analogue points (AI, AO, GI, GO) broadcast whenever their value changes through a range greater than the specified "Broadcast change counts" parameter (defined within the 'Resident Points' editor). Global discrete points (DI, DA, DO, DM, DC) broadcast whenever their state changes. Global pulsed input points (PI) broadcast whenever their "Scans between broadcasts" parameter is exceeded (defined within the 'Resident Points' editor). When requested to by the associated indirect point. Indirect points "receive" their state/value from their corresponding global points. Indirect points must reside in a different controller from the global point, and they act as receptors for the value or status information broadcast from the global point. When entering an indirect point, you must specify the name or address of the associated global point. The frequency of the update from the global points depends on the following. Their associated global point broadcasting its status or value. In addition, an indirect point can request an update, at the indirect points scan rate, from their associated global point. This happens when: The indirect point is first entered. When the indirect point's controller is restored or reset (power restore, station restore or the red reset button is pressed). Whenever the local control LAN reconfigures. Whenever an AO or DO indirect point is put into "Manual Mode" or back into "Automatic Mode." When the indirect point has not seen a status/value change from its associated global point within 2 times the indirect point's scan interval it request an update from its associated global point. It then reports the update on its third scan interval. If the indirect point is unable to be updated from its global point (i.e. no communications) then the indirect point will report its last valid updated value/state and will flag the value/state as "Old Data." Direction of Point Data's Flow INPUT POINTS (AI, GI, DI and DA): The data flow is from the global input point broadcasting to the associated indirect point only. The flow is "one way" only, that is to say, if the associated indirect point should alter the state or value is not broadcast to their corresponding global point. GLOBAL INPUT --------------> LAN -------------> INDIRECT INPUT OUTPUT POINTS (AO, GO and DO): All output points (both global and indirect) broadcast their state or value changes to the other associated point(s). The flow is "two way," that is to say, a change to either the global or the associated indirect point will change their opposing point's value accordingly. GLOBAL OUTPUT <--------------> LAN <----------------> INDIRECT OUTPUT Click Here to view some recommendations / rules for Global and Indirect Points as well to view this complete article as one document.

Issue Trying to locate the BACnet PICS for a UNC and ENC.  Where are they located? Environment Niagara R2 revision 522 and higher Niagara G3 revision 3.2 and higher Cause Trying to locate a web-based resource for this information Resolution For Niagara R2, click here for the BACnet PICS.  For Niagara G3, click here for the BACnet PICS.