Building Automation Knowledge Base

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

Issue Measuring dry bulb temperature and relative humidity and need to use them to calculate the following Enthalpy Wet Bulb temperature Dew Point temperature Product Line TAC Vista, Ecostruxure Buildings Operation Environment Function Block applications Cause Need to calculate Enthalpy, Wet Bulb Temperature, or Dew Point Temperature.  These values are typically used to compare the latent heat in the outside air versus inside air for economizer cycles, in chilled water applications where condensation must be avoided, or in humidity control applications. Resolution Enthalpy - the total energy of both the dry air and water vapor per pound of dry air. Wet Bulb temperature - the temperature a volume of air would have if cooled to saturation by evaporation. Dew Point temperature - the temperature to which a volume of air must be cooled for water vapor to condense into water. Download the appropriate HFB below: Psychrometric Calculations in US Imperial Measurements Psychrometric Calculations in SI Metric Measurements

Issue Where are the DUI expander objects for the MNB-300 and MNB-1000 controllers in Workplace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech version 5.1 through 5.9.4 I/A Series WorkPlace Tech version 5.10.0 till current Cause The standard stencils do not include an object for Momentary SS or a DUI multiplexer.  Resolution The I/A Series BACnet controllers do not currently support the DUI object directly within the MNB-300 or MNB-1000. An application performing the same basic function was created and factory tested. This application was created as a custom object named "DUI_App". For support of these objects in Workplace Tech 5.1 until 5.9.4, log into The Exchange Download Center and download the file Application Objects_rev1.zip. There is also a detailed DUI_Application_Documentation_rev1.pdf that describes the operation of the "DUI_App". For support of these objects in Workplace Tech 5.10.0 until further notice, log into The Exchange Download Center and download the file Application Objects_rev2.zip. There is also a detailed DUI_Application_Documentation_rev2.pdf that describes the operation of the "DUI_App". Note: VAV box controllers do not have DUI expander objects available. See TB06-02 for additional details.

Issue Satchwell ALE series Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell ALE series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Actuator type :- ALE series.  Cause Obsolescence of Satchwell ALE series Linear Actuator. Resolution Replace Satchwell ALE series Linear Actuator with Schneider Electric M800 Linear Actuator and Linkage Kit :-   Linkage kit to mount a M800 actuator to a Satchwell valve (MZ,MZF, VZ, VZF, VSF and MJF) = L2SV Replace ALE Actuator with M800 + L2SV combined part number 880-0650-000 Replace ALE with Auxilary Switch kit with M800-S2 + L2SV combined part number 880-0651-000 Just linkage kit = 880-0124-000 Just M800 = 880-0310-030 N.B.  Should the Satchwell ALE series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :-  S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an Schneider Electric Forta M800 Actuator to replace an existing Satchwell ALE series Actuator. The Schneider Electric Forta M800 Actuator may be used to replace an existing Satchwell ALE series Actuator but it should be noted that where an existing Satchwell ALE series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) will also be required. (e.g. Schneider Electric Transformer Type TR60)   Where an existing Satchwell ALE series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALE series Actuator (9.5VA) only.   In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) (e.g. Schneider Electric Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here

Issue What version of Microsoft.Net Framework and ASP.NET is used by Webstation 5.1.9? Product Line TAC Vista Environment Vista Webstation 5.1.9 Cause ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. TAC Vista Webstation is developed using ASP.NET, which is a part of the Microsoft.Net Framework. Resolution TAC Vista Webstation uses Microsoft.Net Framework 4 and ASP.NET 4. For details on additional Vista versions and the .NET framework and ASP.NET versions required please consult the compatibility matrix in the Supported version of .NET framework and ASP.NET for Vista software.

Issue Problems with alarms or configuring alarms in Vista Environment TAC Vista Workstation Cause Improper alarm configuration Resolution Here are steps to configure each part of the Alarm  in Vista. Change of State Object - This is the source of the alarm. Right click on a folder in Vista and select New > Object > Change of State Name the object Double click on the object to modify it Provide a description of the alarm and set a priority level if required. Click on the Object Tab and select the Object to Monitor and the Reference property Click on the Alarm Tab Select an Alarm processing control.  These should be located under the TAC Vista Root object. The default is $Alr_Cntrl Fill in the appropriate text field.  Note: "Text for" fields are text issued as the result of the alarm. "Triggering" text should only be used when monitoring a string value. Set Low and High Limit for the alarm to occur Set Minimum change: This is the smallest deviation required to trip an alarm when using numeric values. Alarm Receiver Objects - These objects route alarms that are intended to go outside of Vista. There are 3 types: Print, file, and Mail (email) Right click on a folder in Vista Workstation and select New>Object>Alarm Receiver - E-Mail (or applicable type Name The Object Double Click on the Object to modify it In the General Tab provide the description and appropriate information for your alarm type (email recipient) In the Alarm Fields Tab, select the fields you wish to appear in the printout or email If you are using Alarm Receiver - Video you will need to set the video settings in the General tab and select cameras to record in the Video Cameras Tab Click Okay Alarm Control Group - This allows us to control distribution of an alarm.  Multiple control Groups will allow multiple distribution lists.  From Vista Workstation, right click on the TAC Vista folder (Alarm Control Objects can only be created here) Select New > Object > Alarm Control Name the Object Double Click on the Object to modify it Enter a description Click "Add" and browse to the desired Alarm Receivers Click on the Acknowledge tab and configure appropriate parameters Click on the Time Control Here you can browse to a time variable that will determine when to use the Alternate Receivers list Add Alternate receivers Click OK

Issue A Pelco IWP221-1ES IP camera is being used and configured as a direct camera in Security Expert but the image from the camera is not being displayed in the Security Expert. Product Line Security Expert Environment Security Expert Pelco IWP221-1ES IP camera Cause The wrong URL to the image feed was used. When we use the IP address of camera to display the camera image in a web browser, it requires the Pelco Media plug in or Quicktime but these cannot be used in Security Expert. Resolution Use a direct URL to the camera stream. For the Pelco IWP221-1ES IP camera, use "http://camera.ip.address/jpeg/pull".

Issue When attempting to trust a self signed certificate, the option to permanently trust the certificate is not enabled. When viewing the certificate, you see the message "Bad server certificate" in the field "Issued by" Refer to WebHelp Article 10326 for further information about certificate types Product Line EcoStruxure Building Operation Environment Certificates Cause There can be various reasons why a certificate can not be trusted, and many or these are described in SSL Certificates - Security Certificate Risk warning logging in to WorkStation or WebStation using HTTPS. In this specific case where you see the message "Bad server certificate", the cause is that the certificate is not deemed trustworthy. First of all, you need to check what the reason behind the certificate being flagged as bad is. This is easiest done by examining the "CRL Distribution Points" property of the certificate, to determine which service is checking or affecting the certificate. In this example, we can see that it is ZScaler (a proxy server provider) is listed, so the reason why the certificate is deemed as bad, is most likely because the certificate is self signed, and that is not accepted by the company policy. If disabling the usage of a proxy server on the PC you are working on allows you to trust the certificate, you can confirm that it is an issue with the proxy server not allowing the self signed certificate. For more information about how e.g. ZScaler handles certificates, refer to the How does ZScaler protect SSL traffic article. Resolution Either reconfigure the proxy to allow the self signed certificate, or (the better option) get a proper CA signed certificate. For more information about preparing and importing a CA signed certificate, refer to Preparing and importing a signed CA certificate.

Issue The CPU light condition allows for limited troubleshooting of Expansion Modules Environment Continuum i2 controllers b3 controllers BCX B4920 ACX 57xx Cause Expansion modules require troubleshooting and the CPU light offers some information Resolution The expansion module closest to the controller will blink once at a 2Hz rate. A second module connected to the first expansion module will display 2 short blinks every 2 seconds Incompatible or malfunctioning expansion modules may display the CPU light as a steady ON or ON and then completely OFF When main power supply does not provide enough power for the controller and connected expansion modules, the CPU light of expansion module display a steady ON.

Issue  To convert a 0 - 20 mA signal into an acceptable form to be used into a variety of controller types. Environment Sigma BAS Micronet X96 controllers X32 controllers IAC controllers Micronet controllers Cause Some controllers will not accept a 0 - 20 mA signals and therefore the signal must be converted. Resolution To achieve this conversion, please follow the instructions below. Install a 500 ohm 0.1% resistor in series with the 0 - 20mA signal. From across the resistor, take the signal to the controller . The Universal Input or Analogue Input should be set as a standard voltage input.

Issue When replacing an EP1501 controller, do all doors and schedules have to be recreated? Product Line Access Expert Environment Microsoft Windows Server 2012 or later Microsoft SQL 2012 R2 or later Access Expert EP1501 Controller Access Expert v3 Premise Software Access Expert v3 Hosted Software Cause Recreating all the doors and schedules can cause a lot of downtime during the replacement process of an EP1501 Resolution Open up the instance that the device is configured on From the hardware tree, select the device that needs to be replaced and double-click on it to open a new window Once the replacement device is powered and configured, copy its MAC address and paste it where the old devices MAC address is showing Click save and close at the bottom right of the screen Right-click the controller in the system tree and select Push Controller Database Once the controller comes online again it will start communicating with the sub devices Open up a Live Monitoring Window and verify that events are being properly reported

Issue After launching WebClient logon screen appears but attempt to logon results in "Webclient is unavailable"  Product Line Andover Continuum Environment Windows Vista Windows 7 WebClient Cause Incorrect Internet Information Services (IIS) configuration. Resolution 1. Open Internet Information Services Manager 2. Expand the Computer Name in left pane and click on Application Pools in treeview 3.  Select DefaultAppPool and click Set Application Pool Defaults 4. In Application Pool Defaults dialogbox select Identity under Process Model. A selection control should appear in the second column. Click this button 5. Under Built-in account select Network Service in the dropdown listbox. Click OK 6. Click OK button in Application Pool Defaults dialogbox

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue Is there a limit to the number of read/writes available for a BACnet Setpoint object? Environment WorkPlace Tech versions 5.1 and later Cause Not applicable Resolution The BACnet Setpoint object (analog or binary) is used for writing setpoint values to a controller, where it is stored in EEPROM. Observe normal precautions to avoid frequent writes to EEPROM. Excessive writes (typically greater than 100,000) can greatly shorten the life of the EEPROM and adversely affect its reliability. The BACnet Setpoint Priority object (analog or binary) represents a Value BACnet object type, of which the data is read-write accessible. This object can be used to write data to the controller. The Setpoint Priority object provides access to temporarily stored application values, usually setpoints or setup values, that are stored in RAM.  These setpoint values can be monitored and changed via BACnet communications, using the BACnet priority array.  When written from WP Tech, the default value is written to the priority array “relinquish default” location. Only this default value is stored in EEPROM. For more information, refer to the WorkPlace Tech Tool Engineering Guide Supplement (F-27356)

Issue Unable to reload entire database using "Send to Controller" option. The error "Not enough memory" is seen in Distribution View when trying to reload some objects. Product Line Andover Continuum Environment Continuum b3 Series Controllers i2 Series Controllers Cause Data is corrupt in controller Database or individual points such as Infinity Programs have become corrupt and are unable to be reloaded to the controller. Resolution Clear the database in the controller and retry a "Send to Controller" as follows: Open the Device object of the i2 or b3 controller. Go to the "Runtime" tab. Press the "Reset" button to reset the controller and clear its memory. Retry "Send to Controller".

Issue How do you set up the VisiSat server for MicroNet or IAC controllers? Environment VisiSat server settings Cause Assistance for correct configuration. Resolution LIB-4-485 is a RS-232 to RS-485 converter to be used with VisiSat for communicating to MicroNet NCP Controllers or Satchnet controllers without the need for a MNMI or MIU respectively. The LIB-4-485 is powered from the communications port of your PC and no external power is required, providing the PC port adheres to the RS-232 specification (we have used successfully with Dell PC’s). The connection to the LAN are:-  TD (A) – To negative (-) communications terminal of controller. TD (B) – To positive (+) communications terminal of controller. GND – Screen connected at LIB card only and not at controller.   VisiSat requires the following settings to be configured in the VisiSat Server. The Server is found minimized next to the clock in the system tray. At the bottom right corner of your desktop, double click the server icon to show the VisiSat Server client. Select settings from the Network Menu Option. The Configure Network Settings window will be displayed as below. Select ‘Serial Port’ as the Transport type, and click the Configure button. 1. The configuration for use with MicroNet controllers needs to be as detailed below. 2. The configuration for use with IAC controllers needs to be as detailed below. Once the correct selection has been made click OK. VisiSat is then ready to use with selected controllers.   The VisiSat Engineering guide contains additional information regarding the VisiSat server Click here to download or view the VisiSat Engineering manual.  

Issue Issues being experienced can vary, here are some examples: The digital clock gains a minute every few seconds. The code (0112) when entered to accept alarms, is not accepted. Environment DC1100 controller DC1400 controller Cause The unit has not been correctly cold-started after first being powered on. Resolution The DC1100 / DC1400 controllers must be correctly cold-started after first powering up, this ensures that the default configuration is correctly installed. Cold-start the controller using the following process: Turn off the power to the controller. Press and hold in the ENTER and EXIT keys. Power up the controller whilst continuing to press the ENTER and EXIT keys. Release the ENTER and EXIT keys. The controller will now go through a self test programme and load its defaults. To review the DC1100 / DC1400 controller overview, select here To review the DC1100 controller general data sheet, select here To review the DC1100 controller installation, wiring and Commissioning information select here To review the DC1400 controller general data sheet, select here To review the DC1400 controller installation, wiring and Commissioning information select here

Issue In newer versions of XBuilder, when importing I/NET sav files into the project, an attribute called "flags" is included.  In an I2V integration, this signal can be used to decode the binary flags associated with an I/NET point. Product Line TAC INET, TAC Vista Environment XBuilder 5.1.5 and later Cause In earlier versions of XBuilder, each binary flag was separated out into an individual signal.  These signals include: test manual alarm old unack alarm_ack Binding each of these values (along with value, state, and/or control) for every point displayed on a graphic could quickly cause the number of bindings to expand to a number that caused performance issues with TGML graphics.  To combat this, all of the binary flags were combined into one signal called "flags." Resolution The masking for the flags signal comes from the communications format of I/NET: 7 6 5 4 3 2 1 0 Test Alarm Alm Inh Unack Old Manual Not Used To use these in a TGML graphic, read in the flags signal to a component attribute.  Then read the value and mask off the necessary bits: test = ((flags & 128) == 128); alarm = ((flags & 64) == 64); unack = ((flags &16) == 16); old = ((flags & 😎 == 8); manual = ((flags & 4) == 4); Test, Old, and Manual can be used to append the point value with a T, O, or M, respectively to emulate an I/NET environment.  Logic will need to be written to read in the alarm and unack signals: alarm unack inhibit result false false   No alarm condition true false false Alarm is still active, but has been acknowledged true false true Input active, but no alarm condition false true   Alarm has cleared, was never acknowledged true true   Unacknowledged alarm present

Issue There is a compatibility issue between Revision 2 MNL controllers and S-Link sensors. This incompatibility is noticed when a later production S-Link sensor is connected to an older Revision 2 controller. When the sensor is connected to the controller, 88.8 appears on the sensor’s display window along with all of the other LCD icons. The display never recovers from this mode, which makes the sensor non-functional. Product Line TAC IA Series Environment MN-Sx sensors MNL-10Rx1 and MNL-20Rx1, where x denotes profile type (F, H, R) MNL-V1RV1, MNL-V2RV1, MNL-V3RV1 Cause New MN-Sx production S-Link sensor firmware is not compatible with older Revision 2 MNL controllers. Resolution Newer model S-Link sensors have been released to address this issue. The new part numbers are MN-S1-2, MN-S2-2, MN-S3-2, MN-S4-2, and MN-S5-2. The MN-Sx-2 model line was designed and verified to work with older Revision 2 controllers.  Reference TPA-RKFD-09-0028-00 for more details. Please note that the new MN-Sx-2 S-Link sensors are only for use with older Revision 2 controllers.

Issue Provides additional setup information for the G3 ASD (tacAsd) driver implementation. Environment G3 ASD (tacAsd) driver (all revisions) Cause None Resolution G3 ASD (tacAsd) driver setup basics ...   Monitor properties Ping Enabled = true Ping Frequency = 5m change to 1m Alarm On Failure = true Startup Alarm Delay = 5m The baud rate sync properties is the mechanism that synchronizes the baud rates for the ASD bus. Upon reset, ASD devices initialize to 1200 baud and it is this mechanism that locates those devices and sets the baud rate to 19.2K or 9.6K (if PEMs are used on the bus). These values are part of the ASD specification and should not be changed. Last Time Sync is the last time a successful sync occurred Baud Rate Sync Time = 1m Baud Rate Set Timeout = 0.2s Baud Rate Set Repeat = 1 Baud Rate Change Millis = 800 Total Devices indicates the total number of devices active. Total Down indicates the total number of down devices. Scan Time indicates the total time to poll through the list if devices. The ASD communications protocol is designed to exchange most data between the host (ENC) and device with one transaction. This means that typical data (e.g. EMS, etc.) is written to the device as part of the request and response data (e.g. Window, Output, Diagnostics, etc.) in one transaction. In this case, the scan time is 6.9 seconds for 33 devices or approximately 4.5 devices per second. Tuning Policies (Default Policy) Min Write Time = 0 Max Write Time = 0 Write On Start = false Write On Up = false Write On Enabled = false Stale Time = 0 Note: The stale time actually involves the proxy point objects. The polling mechanism still continues and the internal point information is still updated. The driver does not implement the interaction between the point updates and proxy point stale. The values should be left at their default settings. Poll Scheduler Poll Enabled = true Fast Rate = 5s (defaults to 1s) Normal Rate = 10s (defaults to 5s) Slow Rate = 30s (defaults to 30s) Typically set the Normal Rate based upon the rules specified in the R2 documentation or (Normal Rate seconds = Number of devices / 3.5). For example, a network with 33 devices would be set to (33 / 3.5 = 10 seconds). As indicated earlier, the driver inherits the basic driver properties and mechanisms. G3 implements a complex poll scheduling mechanism that automatically determines and continually adjusts the poll list to achieve the most efficient polling. Retry Count The retry is only used in the event that a response from an ASD device is not received.  This value defaults to 1 and can be increased if needed to a maximum of 3 if devices are unable to respond to the initial message and one subsequent retry,  Devices that do not respond to the initial message may indicate a potential issue with the ASD bus. Response Timeout This is the amount of time the driver will wait for a response to a request before retrying the request.  This value defaults to 2 seconds and should not be changed. Inter Message Delay This value defaults to 0 seconds and should not be changed.