Building Automation Knowledge Base

Issue Wants to be able to access a remotely located group of BACnet MS/TP controllers via BACnet IP or BACnet-Ethernet.  Do you sell any routers or converters of this type? Environment MNB series BACnet controllers using MS/TP communications. Cause Customer wants to use BACnetIP to connect to a group of BACnet MS/TP controllers. Resolution The UNC-520-2 or ENC-520-2, with the BACnet driver installed, can operate as a BACnet IP to BACnet MS/TP router.  These devices allow routing between BACnet-IP or BACnet Ethernet to BACnet MS/TP.  This approach allows for up to four separate MS/TP networks to be routed to the BACnet-IP or BACnet-Ethernet network. The MNB-1000 provides a single MS/TP bus along with the BACnet IP or BACnet Ethernet capability. We have not tested and cannot support any third party BACnetIP to BACnet MS/TP converters.

Issue How to set up a Mantrap Product Line TAC INET Environment I/NET Access Control Site Interlocked Doors Person Trap Anti-Passback (APB) Cause What is a mantrap? A mantrap is a security device that monitors and controls two or more interlocking doors to a small room that separates a non-secured area from a secured area. These interlocking doors allow only one door to be open at any time. What are interlocking doors? “Interlocking doors” is a security term used to describe how two or more doors are interfaced with each other and locked. Doors that are interlocked cannot be opened at the same time. Either door can be unlocked and opened as long as the other door is locked and closed and no other alarm condition exists. What types of locations require a mantrap? Mantraps are used at high-value or critical security areas where only authorized persons are allowed to enter. Typical areas include sensitive data processing areas, cash handling areas, critical research labs, security control rooms, and automated airline passenger entry portals. Why would my company consider a mantrap? Typically, security personnel are posted in high-security locations to control access into the area. An automatic mantrap used in this same location would control the access to the area, allowing security personnel resources to be available for other tasks. What is the difference between a mantrap and an interlocking door control system? Regarding controlling two doors within a vestibule, “mantrap” and “interlocking door controller” can be used interchangeably. Once the number of doors controlled by a single controller exceeds two, then the term interlocking door controller should be used. Resolution I/NET has three ways to do a mantrap: Event sequences and calculations -- limit to 5-7 SCUs per 7798C due to system loading Use a "standalone" third-party device that is wired to the door and is not attached to I/NET at all Use the interlock wiring diagram that uses relay logic to function. This is also part of the I/NET System. I/NET Seven allows configuring a door to have both an entry and an exit reader and uses the selection of Anti-pass back/Anti-tailgate to set up Zones or areas with stricter control over access. However, even with the Anti-pass back option set to Hard, which denies access to successive reads at the same reader, it does not prevent multiple persons from entering and exiting together, and it does not provide real-time accounting for the number of people in a Zone. Besides having a guard at the door, the usual method of implementing Zones does not prevent violations.   The example below presents some thoughts about improving the Zone's security in an I/NET Seven system. There needs to be a way to restrict the number of people gaining access to the door. There needs to be a way to keep up with how many people are in the Zone. One method to accomplish the first goal is to use a two-door egress system, as is often used in jails and similar security setups. For a medium security setup where the intent is not to prevent people from leaving, only one door needs a card reader. Such a design is illustrated below: Notes: Electric strike normally energized. Low walls or fences. The area should be small enough to limit how many people or things are in it at one time. Gate with normally de-energized bolt. The gate could swing both ways, so one would only have to push it to open it. It should have a spring to close it. The door “a” would have both an Entry and Exit reader, so an Anti-pass back/Anti-tailgate can be implemented. The strike on the door “a” would normally be energized and opened by a valid reader transaction.   The bolt on the gate would be normally de-energized, allowing the gate to open freely. When the strike on the door “a” is de-energized, the bolt on the gate would be energized, preventing the gate from opening. This is designed to allow only one person to simultaneously move into or out of the Zone.   An added level of security would be accomplished by mounting IR emitter/receiver pairs along the low wall or fence at regular intervals. A person would interrupt the light at a limited number of receivers, so if more than expected are interrupted, it would violate one person at a time, and necessary action could be taken.   If material needed to be moved through the door, the gated area could be made large enough to allow for a dolly or whatever might be needed. A different access level would be provided to those who are moving material, thus preventing the alarm for too many people going through the door.   This approach would restrict movement into and out of the Zone, and the example given in the AIC note could be implemented to allow real-time monitoring of occupancy levels in the Zone.   Design thoughts:   To calculate whether more than one person is in the gated area, sum the number of receivers that are detecting and compare it to a minimum, e.g., four of six must be detecting if only one person is in the area. If material is in the gated area, generate an alarm if an authorized card is not read. Use the alarm delay for the point to give an individual time to make a card read before sounding the alarm. The AIC scheme described in the AIC note would have to be duplicated for the material mover individuals to change the calculation of a person in the gated area. For material movers, the detection would be (sum of detectors < minimum), whereas for regular individuals, the detection would be (sum of detectors > minimum). Remember, the SLI connected to this door can have only 64 AIC’s and this door now has used 2 of them. Use an inter-card delay long enough to let the person exit the gated area before another card can be read. For personnel safety, there must be a way to de-energize the strike. One method would be to mount an emergency exit button located far enough away from the door so a single person could not reach it and a second emergency exit button on the outside of the Zone so someone could keep the strike de-energized until everyone is evacuated. Most codes probably require that all strikes be de-energized in case of smoke or similar emergency to provide another fail-safe.   Here is a pdf document which explains the setup using an SCU Click here to download third-party ManTrap information.

Issue Controlli S300 Actuator Environment Controlli S300 Actuator Cause Controlli S300 Actuator terminal details. Resolution L=Neutral L'=230Vac B=Close signal from thermostat or control device R=230V to thermostat or control device V=Open signal from thermostat or control device To test: Place a wire link between R and B, the valve actuator will close, place a wire link between R and V, the valve actuator will open. If a auxiliary switch kit D22 is fitted, this can be used to signal the boiler/pump to start if the installation was a domestic. For the actuator datasheet click here.

Issue Reload fails during the programs portion with an error message similar to: Unable to reload attributes. OMS database is currently unavailable, backing up. Environment i2 bCX NC2 Cause A flash backup PE program is set to autostart. As soon as that program loads, it will start to perform a flash backup and any PE programs that have not loaded will not load and the reload will terminate. Resolution Make sure any programs set to automatically backup a controller cannot do so until after a reload is complete.

Issue Can a workstation communicate to a controller using Ethernet Network Address Translation (NAT) Product Line Andover Continuum Environment Cyberstation All Ethernet level CX and bCX controllers. Cause Some IT Departments may want to use Network Address Translation to connect between different sections of their network. Resolution Continuum does not support Network Address Translation (NAT) the IP address entered in the Cyberstation database must match the address entered locally in the controller.

Issue Using Modbus TCP and Modbus Serial (EIA/TIA-485) on an AS together? Product Line EcoStruxure Building Operation. Environment AS-P Modbus TPC Modbus Serial Cause Communicating with two third party devices simultaneously. Both are using the Modbus communication protocol. One is Modbus TCP, the other Modbus Serial (EIA/TIA-485). Resolution Modbus TCP and Modbus Serial (EIA/TIA-485) can be used together on an AS-P. This configuration is supported and has been used many times.

Issue Maximum number of expansion modules and doors per controller Environment SP-C Security Expert Security Expert Controller SP-RDM2 Security Expert Security Expert Door Expansion Module Cause Documentation states that one SP-C supports up to 128 doors but this is dependent on the communications.  Resolution The current recommendation from Product Management is a maximum of 24 to 34 doors per SP-C. This equates to about 10 to 17 reader expansion modules.  

Issue After the successful installation of Continuum 1.9x, users are receiving a DCOM Permission error when logging on to Continuum webClient. The error is intermittent. Product Line Andover Continuum Environment Microsoft Server 2008 Standard Microsoft Windows 7 Continuum 1.9x and 2.0 Continuum webClient Server Remote Desktop Cause When a remote desktop connection is made on Windows 7 or Windows 2008 Server the console occasionally gets locked. It stays locked until the local session is restored with a logon. Resolution Create a .bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console **************************************************************************************** Place this file on the desktop of the Continuum webClient Server system. When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be run "As an Administrator." This will disconnect the session and restore the console.

Issue When defining configuration on SE7300 part no, your choice is between "0" (override) and "5" (possibility to change between °C and °F in interface). Environment SE7300 Cause its not possible to have both override and °C/°F feature Resolution When defining the part number, you will have to choose. The override feature is usually the preferred choice in industrial applications, while the °C/°F feature is used for Hotels and similar, where users are given the possibility to change unit of desired temperature.

Issue When a Sigma data import is carried out, the following messages are displayed on the SBO ES computer. On the Sigma server computer, the Sigma server service has stopped. Product Line EcoStruxure Building Operation Environment Sigma 4.08 Building Operation Workstation Building Operation Enterprise Server Cause The Sigma database’s longtext file contains unsupported characters. Resolution Option 1: If Sigma longtext is no longer required: On the Sigma computer. 1)      Stop the Sigma server service. 2)      Delete the longtext.rec file from the Sigma Data folder (C:\Sigma\Data\longtext.rec). 3)      Start the Sigma server service. On the SBO computer Carry out the data import again. Option 2: If Sigma longtext is required: On the Sigma server computer. 1)      Start the Sigma server service. Open a Sigma client, either on the Sigma server computer or the SBO ES computer or other. 1)      Log into Sigma’s operator panel 2)      Go to the System Alarm manager 3)      Under the menu “Configure” select Longtext 4)      Open each longtext entry and remove the unsupported characters 5)      Add the longtext message your require. (You may find copies of the original longtext messages you can copy the text from, under “C:\Sigma\Data\Longtext” used by Sigma before the system was upgraded. On the SBO computer 6)      Carry out the data import again.   The data import should now complete.

Issue What needs to be changed in the Sigma configuration? Environment Sigma IP Address Moving Different network. Cause Are any changes required to the Sigma configuration, when a Sigma server is moved or the IP address is changed? Resolution Changes required when moving the Sigma server PC to another location or re-installing the Sigma server software onto another PC in a different location. Locate the PC in the new area and give it an appropriate IP address. Start the Sigma server and local client. Enter Sigma "System setup" and select "Networks and Devices" Select the zone that the server is in. In the "Networks" option, does the network already exist, if not then create it. In the "Servers" option select the Sigma server and select the correct network and IP Address. In the "Clients" option check that all clients are attached to the correct servers. In "Controller Items / Routesets" confirm that the routesets are correctly matched to the clients. Download the "Node Configuration" to all devices Download the Att.set and the Routeset.rec files to all controllers.

Issue Continuum displays Reason Code 12 error During Send to Database on BACnet/IP device. Environment 3rd party BACnet Continuum BCX4040 BACnet over IP Cause Third party device is not accessible to Continuum following configuration change by vendor. Resolution Restore communication to 3rd party device.

Issue Need to know the smallest change that an Input can measure or that an Output can provide. Environment All Continuum controllers. Cause Need to know for specification compliance or to determine the smallest measurable change in an Input. Resolution Some of our controllers support inputs with a 10 bit resolution and some support 12 bit resolution. As a rule, all 5.115v inputs are 10 bit and all 10v inputs are 12 bit. You can see which resolution each controller supports by viewing the Datasheet for each controller and noting the value of the "Input Resolution" and voltage range of the inputs (normally 0-10VDC). As an example, the b3920 shows an input resolution of 2.5mV on its 0-10VDC inputs. This equates to a 12 bit resolution as shown below.      2 x = 10VDC / 0.0025 VDC      2 x = 4000      x * log(2) = log(4000)      x = log(4000) / log(2)      x = 11.96578 or 12 bit   Further, a b3800 has an input resolution of 10 bits on its 0-5.115VDC inputs.      5VDC / 2 10 = 0.00499V or 5 mV You can find the individual controller Datasheets on Ecobuildings. Navigate to the Download Center and search the controller model number. Then narrow results by Asset Type = 'Specification Sheet'.  Most of the new Datasheets now note both the Input and Output resolutions.

Issue Can we integrate 3rd party LON devices Environment StruxureWare Building Operation AS or Enterprise Server Cause Integrating third part LON devices allows the system to take full advantage of the open protocol. Resolution We currently support 3rd party Lon devices in Version 1.0 and 1.1, but some large devices are too big to be configured in quantities according to specifications. No major change regarding this is scheduled until earliest 1.4. In 1.3 we will change the numbers that we support to configure but this will mainly be runtime improvements. Some devices can only be configured with Lonmaker which is an extra step during the engineering process.

Issue Please define the difference between the V211 and V211T Environment V211 V211T Cause There are 2 different valves with similar characteristics, what differences are there, and why should I choose one or the other? Resolution V211 is equipped with flanged connections, while the V211T has internal threaded connections.

Issue In the event of a hardware failure on a Xenta controller you may need to perform a proper replacement procedure in the TAC Plug-In to install the new device. Product Line TAC Vista Environment Vista Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Hardware failure in an LNS network Resolution In the event you have a piece of hardware fail on your LNS network you will want to follow the steps below to properly replace the device. Remove the bad controller and Install the new controller in its place Open your LNS network in LonMaker or NL220 Select to open the TAC System Plug-In in your network management tool In the Plug-In, locate the bad controller in the tree under the LNS Network pane and right click Select Replace... (the Replace TAC Xenta Device Wizard will open) Click Next Select the service pin button and press the service pin on the new controller Then click Next In the next window, click Next to update your Vista Database (NOTE: If you receive a warning during this process, see Warning about application file replacing a programmable controller in Vista System Plug-In) Once this process of updating your Vista Database is complete you will see the screen below confirming that the update was completed successfully Close the TAC Vista Load window Return to the Replace TAC Device Wizard and click Finish. This will complete the replacement process for your new device In some rare cases not all I/O modules will come online after this procedure. If this occurs a power cycle of the Xenta 400/300 will solve this issue.

Issue The data sheet states 2 different power consumptions: Power consumption: average 6 VA Transformer sizing: 30 VA Which one should be used for calculating power supply? Environment Forta Cause There are different figures specified in the documentation for the Forta series actuator. Resolution Average consumption is 6VA, but the peak consumption is 30VA, and this is just before the valve reaches the fully closed position.

Issue During step 9 of How to replace a Xenta controller in a LNS network it is possible to receive a warning with the following information: Warning: The device has no application file (MTA file) thus disabling the possibility of a download of application and parameters to the device. Please download via serial port any application file (MTA file) of your choice by using Menta before attempting to download to this device again. Product Line TAC Vista Environment Programmable Controllers 281, 282, 283, 301, 302, 401 & 401:B Cause Attempting to install a Xenta programmable device that does not have a Menta Application loaded into controller. NOTE: A new controller out of the box should have a simple MTA Application already loaded.  However, if you receive the warning above your controller may not have any Menta file and loading any simple Menta file (i.e. one PVR block) will suffice. Resolution You will need to direct connect to the new controller with a RS-232 cable to upload any simple Menta application (i.e. one PVR block) before the Vista System Plug-In will properly communicate and download the new controller.  The System Plug-In will not communicate with an applicationless device.

Issue When the EWS is installed on the same machine using the service then all packets will be going to the localhost and will not hit the NIC so will not be captured in a Wireshark packet capture. Product Line EcoStruxure Building Operation, EcoStruxure Security Expert Environment Security Expert Building Operation Enterprise Server Building Operation Automation Servers (AS-P, AS-B) Cause Packets sent between services on the same machine (like SOAP and EWS) do not hit the NIC and therefore cannot be captured with the default configuration of Wireshark using the WinPcap packet sniffing library.  Resolution Replace WinPcap with Npcap to emulate a loopback NIC for packet capture. Go to https://nmap.org/npcap/ for details on the library. Download the library installer from https://nmap.org/npcap/#download Uninstall WinPcap. Install Npcap. Npcap will then create an adapter named Npcap Loopback Adapter. In Wireshark choose this adapter to capture, loopback traffic will be the seen the same way as other non-loopback adapters. This can be tested by typing in commands like "ping 127.0.0.1" (IPv4)  or "ping ::1" (IPv6).

Issue As a part of the drive to improve information regarding our products, this document has been created to assist and clarify methods of connecting Touchscreens to newer and older series MicroNet controllers, and the controllers on the sub LAN under the Touchscreen unit. Product Line Satchwell MicroNet Touchscreen Environment Touchscreen wiring Cause Connecting MicroNet Touchscreen to microNet controllers. Resolution 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 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Remote Mounted Touchscreen (NCP) Connected to MN550/MN650 Controllers. Fig.1  Fig.2 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 3)  Fig. 3                                                                             Fig. 4 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 4) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. If the option of an isolated LAN for the 50 series controllers on the sub LAN is to be utilised, then a separate 24 Volt power supply should be used to supply the Touchscreen. Touchscreen (NCP) Directly Mounted on MN550/MN650 Controllers.   Fig.5  Fig.6 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 7)  Fig. 7                                                                           Fig. 8 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 😎 A visual check should be carried out to insure the jumpers, are fitted to the two auxiliary pins and they have a good physical connection. The MN50-TS-NCP specification of the Touchscreen differs from other variants and only has these 2 pairs of pins. This is to allow the Touchscreen to mount directly onto the controller; the other auxiliary pins are not fitted when manufactured. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. These are fitted at the factory, and should be removed. Connection to other controllers on the sub LAN should be done via LAN B of the base controller to LAN A of the other controllers on the sub LAN.  If the option of an isolated sub LAN, using 50 series controllers, needs to be fully utilised, the Touchscreen would need to be mounted remotely with a separate 24 Volt power supply. If the Touchscreen must be mounted directly onto a controller, that controller and the Touchscreen would not be fully isolated, but provided the Touchscreen /controller has a separate supply to the rest of the sub LAN, other controls on that sub LAN could be isolated. Remote Mounted Touchscreen (NCP) Connected to MN500/MN620 Controllers. Fig.9 Fig.10 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 11) Fig. 11                                                                                 Fig. 12 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 12) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. The controller on the sub LAN needs to have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. Touchscreen (NCP) Directly Mounted on MN500/MN620 Controllers.    Fig.13 Fig.14 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 15)  Fig. 15                                                                           Fig. 16  The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 16) A visual check should be carried out to insure the jumpers, on the Touchscreen, are fitted to the auxiliary pins and they have a good physical connection. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN should be done via LAN B of the base controller to LAN B of the other controllers. Caution to be taken when replacing an MN500 or MN620 controller if a Touchscreen is directly mounted on the unit. When replacing an MN500 or an MN 620 controller that has a Touchscreen directly mounted with a 50 series MN550 or an MN650 controller. The Touchscreen auxiliary pins 6 and 7 foul components on the controllers back plate, and will need to be cut. Pins 6 and 7 are identified in figure 17 below, will need to be cut close to the isolation strip A Once this modification has been carried out to the Touchscreen, the unit will no longer be suitable to run ARCnet communications. Fig. 17 An option would be to replace the Touchscreen at the same time as replacing the controller, with specification number MN50-TS-NCP. The MN50-TS-NCP specification of the Touchscreen has been modified, in production, starting Q2 2007, to allow direct mounting onto the MN500, MN 620, MN 550 and MN 650 controllers. Note: The 50 series controllers can be on the same LAN as the old 100 series of controllers. The LAN connections previously described, for the particular controller should be observed. Further information regarding these controller can be found in the product data sheets. See MicroNet 100 series controller MLi's and Data sheets See MicroNet 50 series controller MLi's and Data sheets