Building Automation Knowledge Base

Issue Is MNL-V2RV3-APP the actual controller hardware or is it an application for the actual physical controller? Environment I/A MicroNet LonMark series controllers. MNL-5RF3-APP, MNL-5RH3-APP, MNL-5RR3-APP, MNL-5RS3-APP, MNL-5RS4-APP MNL-10RF3-APP, MNL-10RH3-APP, MNL-10RR3-APP, MNL-10RS3-APP, MNL-10RS4-APP MNL-11-RF3-APP MNL-13-RF3-APP MNL-20RF3-APP, MNL-20RH3-APP, MNL-20RR3-APP, MNL-20RS3-APP, MNL-20RS4-APP MNL-V1RV3-APP, MNL-V2RV3-APP, MNL-V3RV3-APP Cause Part Number description Resolution The MNL-V2RV3 is the actual controller; the extension -APP is an option for factory to install customer's in-house engineered application. Contact Customer Service for details.

Issue What entries are needed in the INPUT_XLATE table for the Sigma digital input to work? Environment Sigma gateway.txt IC GEN DDE IC GEN OPC Cause The Sigma digital inputs operate a reverse logic of 100.0 = off and 0.0 = on.  This needs to be reflected in the IC GEN Gateway.txt file XLATE table Resolution 1.  For the IC GEN gateway.txt input XLATE table when mapping to digital input objects; [INPUT_XLATE] count=2 Item0=1 / 0.0      ;DDE input of 1 = DI on Item1=0/ 100.0  ;DDE input of 0 = DI off 2. For the IC GEN gateway.txt output XLATE table when mapping from digital output objects; [OUTPUT_XLATE] count=2 Item0=0.0/ 0        ;D0 off = DDE output of 0 Item1=100.0/ 1   ;D0 on = DDE output of 1

Issue SVT Optimiser Controller does not enable the controlled space to recover to the required day temperature after an unoccupied period during which the inside air temperature has fallen to 12°C. Environment SVT4201 Optimiser Controller fitted with Analogue Time Switch. SVT4251 Optimiser Controller fitted with Digital Time Switch. Cause SVT Optimiser Controller Time Switch settings do not allow for selected Design Preheat Hours (DPH) Resolution SVT Optimiser Controller Time Switch settings should allow for selected Design Preheat Hours (DPH) SVT Optimiser Controller Time Switch settings should be carried out as follows :- Set Td to "Day" temperature required during occupancy. Set Tn to minimum "Night" temperature required during unoccupied periods. Set DPH to design preheat time. DPH is the maximum time required in order to enable the controlled space to recover to the required day temperature after an unoccupied period during which the inside air temperature has fallen to 12 deg. C. Select the approximate time in whole hours on the rotary switch (1 to 5 hours) Fine trim +/- 1/2 hour on the associated setting potentiometer. Note.  ALL "ON" times must be set earlier than the start of occupancy by the selected pre-heat time (DPH) set at (3) above. Example : DPH = 2 hours Occupancy time = 8.00 a.m. Set Time Switch "ON" time to 6.00 a.m. Setting the Time Switch "ON" time to 6.00 a.m. will enable the SVT Optimiser Controller to switch the plant ON at any time between 6.00 a.m. and 8.00 a.m. depending on the heating loss experienced in the controlled space during the preceding plant OFF period. N.B. The setting method detailed in the example above applies equally to both SVT4201 Analogue Time Switch and SVT4251 Digital Time Switch versions of the SVT Optimiser Controller.

Issue DMS MicroSmart, Global point passing (broadcast) not working. Environment MSC-L1000 MSC- MPC-001 MSC-P-751, MSC-P-752, MSC-P-753, MSC-P-754 MSC-P-1501, MSC-P-1502, MSC-P-1503, MSC-P-1504 MSC-V-510, MSC-V-511, MSC-V-521, MSC-V-522 MSC-V-751, MSC-V-752, MSC-V-753, MSC-V-754 Cause The number of TXD and RXD broadcast channels are limited per controller type. Resolution The Level 11. controllers' MicroSmart Global Data Broadcasting capabilities are as follows: MSC-L1000: TXD and RXD on 1-122 channels MSC- MPC: TXD and RXD on 1-122 channels MSC-P-75x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-P-150x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-V-51x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-V-52x: TXD on 1-122 channels. RXD on 1-24 channels. MSC-V-75x: TXD on 1-122 channels. RXD on 1-24 channels.  

Issue The IC3 Modbus IP interface is a client. How can this be linked to another Modbus IP client such as the Carrier i-VU gateway? Environment IC3 Modbus IP Client server Sigma Carrier I-VU Cause The IC3 Modbus only supports the IP client and cannot be directly connected to another IP client.   Other systems such as Carrier are similarly only IP client. Resolution Using the BCX1 as a Modbus IP server to hold a mapping table will allow both clients to read/write data to it.

Issue In WorkPlace Tech can a SNVT exist in a Custom Object? Environment I/A Series WorkPlace Tech 4.0 and higher. Cause Custom Object Rules Resolution Nearly all types of WP Tech shapes may be included on the Definition page of a Custom object, There are several exception and  "SNVT objects"  is one of them. This object must be on the top page of any control logic drawing instead. For  additional  exceptions see WorkPlace Tech Tool 4.0 Engineering Guide (F-27254-3), Chapter 3 "Custom Object Rules"

Issue When using DCT version 11.6, modifying the MSC-NCM schedule start-stop times do not save. The time reverts to the setting before the change was attempted. Environment MSC-NCM Cause Version 11.6 of DCT has an error in the compiled code. Resolution Instead of starting DCT from the desktop shortcut, launch it from the DCT folder (double-click DCTGL.EXE).

Issue Modify occupied cooling and heating (nciSetPts) variables on Viconics VT7652 LON stat, but changes are not transmitting to  thermostat. Have a DynamicCmd object linked up and can write the values in the DynamicCmd but they don’t ever change in the thermostat and they don’t show up in the nvoEffectSetPt variable. Environment VT7200 LonWork series VT7300 LonWork series VT7600 LonWork series Cause Setup of limits Resolution Check the HeatMaxSetpoint and CoolMinSetpoint limits found in the nciCfgRtuHP ( Vt76Pir properties). When a change that is outside of the limits, it will take the request but will not transmit change down to the thermostat.

Issue In WorkPlace Tech Tool, the Definition tab of a Custom Object, right click on any object to request Properties info. The response is an error "Exception happened finding Visio shape". What does this mean? Environment WorkPlace Tech Tool 5.7.x Cause There was an error in Visio. The custom object may have been copied from a newer version of Visio to an older version. There may have been an error when creating the custom object. Shapes may have been added to the custom object when opened directly in Visio instead of being opened in WPTech. Some other corruption to the drawing took place. Resolution Do a “Rebuild Application”, and then try opening the shape properties again.  If this does not work, try creating a new custom object, and then try copying the contents of the old custom object definition page into the new custom object definition page (while in WPTech).  Then delete the old custom object, and then try the shape properties in the newly created custom object.

Issue Unable to connect with DCT to log in MicroSmart MSC-NC Environment MSC-NC MSC-NCM MSC-DCT Cause Flash Memory got corrupted. Resolution Reloading Flash Memory on an MSC-NC (M) Power down; jump J1 (near processor); power up. Can DCT connect? If so, remove J1 jumper Do Alt-L to start Load Flash ROM installation If unable to connect with DCT, will need to consider replacing/repairing unit.

Issue Need to replace Analogue Timeswitch for Satchwell SVT4201, CSC 1776, CSC 1777, CSC2776 or CSC2777 Controller. Environment SVT4201 CSC1776 CSC1777 CSC2776 CSC2777 Analogue Timeswitch. Cause Faulty Timeswitch requires replacement. Resolution Replacement Analogue Timeswitch for Satchwell SVT4201, CSC1776, CSC 1777, CSC2776 or CSC2777 Controller is part number 561-9-260.

Issue The word TEST is displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation preventing it from being commissioned. Environment Satchwell Climatronic CSC5252 CSC5352 CXR5805 CXT5605 CZT5305  Controller Display TEST LCD Screen Cause The cause of the word TEST being displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation and preventing it from being commissioned is normally due to a micro processor programming error occurring during the course of production. Resolution There is no field remedy that can be applied to a Climatronic Controller displaying the word TEST on the Liquid Crystal Display screen that will enable it to be commissioned successfully. The Controller should therefore be returned to the vendor for replacement under the terms and conditions of the warranty applicable at the time of purchase.

Issue Error during installation of Vista:  "Unable to Locate Microsoft Excel" or may say "Could not find Microsoft Excel which is needed to use Vista Reports." Environment Windows 7, XP Microsoft Excel Vista Cause Vista may not be compatible with the version of Excel that you have installed on your computer or Excel may not be installed. Resolution Download document TAC Vista Compatibility Matrix Use the matrix to compare the version of Vista you are trying to install and the software installed on the machine Correct any discrepancies by either purchasing a different version of Excel for the computer or using a different version of Vista.

Issue Is it possible to set a delay on a EE_mess alarm in Vista? Environment TAC Vista server Vista workstation Cause A delay on the EE_mess would prevent triggering of unnecessary alarms   Resolution It is not possible to delay a EE_mess alarm in Vista, the delay attribute does not exist on a EE_mess object.

Issue Locating partners Environment Partner Continuum Cause Require engineer to visit for maintenance, servicing, installation or advice. Resolution Click here to be linked to the available UK and Ireland Continuum partner list.

Issue I have a large site and need to add a new Xenta controller. Can I add the group bindings manually as the option to create group bindings in the System Plug-in takes time and controllers are taken offline for the period of the process. Environment NL220 Cause This is possible to do and works very well and effectively if you understand the process. Resolution Follow these steps to add TAG 0 system binding and TAG 1 Xenta binding to your new Xenta controller. In NL220 go to the project setting option. Then check the "Message Tags Connections Tree" option under the Trees tab This will cause a new option to be selected in the tree view labeled Message connections In this tree there will be one TAG0 that covers the entire Xenta controllers. Right click on this TAG 0 connection and select Edit. With the connection window open then select the subsystem       view and drag the TAG 0 from the new Xenta controller into the connections window. This will add your new Xenta controller into the TAG 0 existing binding. Use the update button to update the database. The next step is similar to the TAG 0 but for the TAG 1. You will need to locate the TAG1 Xenta group that you are adding the new Xenta controller into. Look for the name of the Xenta controller in the Xenta group that you need to use. Once you have located this TAG 1 connection right click on this connection and select Edit, with the connection window open then select the subsystem view and drag the TAG 1 from the new xenta controller into the connections window. This will add your new Xenta controller into the Xenta TAG 1 existing binding. Use the update button to update the database.

Issue Integration of the Carlo Gavazzi EM21 Power Meter with the Xenta 5xx\Xenta7xx Xenta 913 and Modbus RTU Environment Xenta 511, 527, 55, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Carlo Gavazzi EM21 Power Meter Cause Disclaimer:  This device template is intended to provide a starting point for an integrator and is not meant to be a mandatory points list for your integration project. Product Support Services has written this device template in an effort to give our customers a solid example of how to develop a device template for the above product.  The integrator will be responsible for any additions or modifications to this device template.   Please report any problems with this template to Product Support, via the Contact link at the top of this page. Resolution Please use the following dev file as a starting point and a guide to the integration.  This .dev file contains a subset of the registers in the device that PSS considers will be of most use to the integration process.  If any other data is required please see the latest Carlo Gavazzi documentation to make the necessary changes.   To use these files in XBuilder please follow these steps: 1.  Extract the .dev file from the .zip file in the link above and place it in a convenient location on your harddrive. 2.  In XBuilder, right-click on the Modbus Master device and choose 'Add Device'. 3.  Browse to the extracted dev file and choose 'Open'. 4.  Rename the newly added device to a unique name within the Modbus Master network.

Issue How to change the IP address of the Automation Server and ensure proper communication. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Building Operation Device Administrator Building Operation Workstation Cause At times the IP address information for an Automation Server must be changed after being added to an Enterprise Server to accommodate changes in IP network design, correction of incorrect data, or any other reason. Changing the IP address needs to be done in the proper method to avoid artifacts and confusion after the change. Resolution To avoid complications, follow this process to modify the IP address of an Automation Server that is already communicating with an Enterprise Server. In the Building Operation Device Administrator connect the AS controller via USB or IP.  WebHelp Topic Connect to SmartX Servers Right-click on the AS and select Network Settings Modify the IP address settings to the new values Additionally, this can be changed through PuTTY with the "setip" command. Power Cycle the Automation Server (If a power cycle is not completed the AS will still have invalid data for network settings despite the physical network interface running with the new settings) Start Building Operation Workstation and log in to the Enterprise Server Select the Enterprise Server and open the Communication Tab Highlight the Automation Server that needs to be changed and modify the address field for the IP address of the device. (The Communications settings tab is enabled by selecting the Show/Hide tick icon). Click the Save button The Enterprise Server should now automatically establish communication with the AS, but if you want to speed this process you can right-click the Enterprise Server and select the "Advanced\Repair Server Communication" option. IMPORTANT: As of 1.41 if the IP address is changed on a server that is configured with a BACnet interface, the IP address and possibly the broadcast address of the IP Network under the BACnet interface must be updated manually. (see below)

Issue Micronet BACnet (MNB) AV and BV objects in G3 are purple indicating they are overridden. The AV and BV objects are read only, how can they be overridden? Product Line TAC IA Series Environment Niagara G3 Micronet BACnet MNB-300 MNB-VAV MNB-1000 Cause Purple BACnet values (I/A Series R2 and G3 graphic override color) are internal BACnet points that can not be modified (display only). This behavior is normal and began to appear in MNB controller firmware versions 1.2 and higher. Per the BACnet specification, read-only type points must be set to indicate an override condition. The root cause is a design change required by the BACnet specification to bring the controllers into compliance for BTL certification. The ASHRAE BACnet Specification 135-2004 specifies that the "read-only" type objects (e.g. Analog Value, Binary Value, etc.) OVERRIDDEN flag is: Logical TRUE (1) if the point has been overridden by some mechanism local to the BACnet device. In this context "overridden" is taken to mean that the Present Value property is not changeable through BACnet services.In this case, the override is meant to indicate to Niagara that the point is locally overridden (by the controller) and cannot be changed by the Niagara BACnet service (or user).When the ENC learns the device it reads what "Protocol Services" it supports. If it supports COV then the "use COV" flag is set to true in the device object and when the proxy points are brought in they are defined as COV and once subscribed they will send their present value and status flag values to the ENC. In this case the AVM & BVM (being read only) objects will show overridden along with their value and be purple by default. Resolution All MNB devices support COV so the use COV property is set to true when they are discovered in the ENC.If the use COV property of the Device object is changed to false the ENC will use readPropertyMultiple (if supported in the device) to poll for data. If readPropertyMultiple is not supported in the device the ENC will read one property at a time. Now when the points are learned they will be defined as polled and when polled only the present value (PV) is requested (by default). Hence the AVM & BVM objects will show their value but not show overridden because their status flags are not known at the ENC. If the use COV device property is set to true after the AVM and BVM proxy points are defined in the ENC they will show overridden and purple after they are successfully subscribed. Turning the use COV property in the device to false at this point will cause these objects to be polled but their status is already known so they will continue to show overridden along with their present value. The only way to change that is to delete and re-learn them while the device use COV property is sent to false.

Issue How is a subnet defined? Environment Refer to "TCP/IP Network Administration" by Craig Hunt, O’Reilly & Associates, Inc. Cause Sectioning network communication by subnets. Resolution A subnet is defined by applying a bit mask (subnet mask) to the IP address. If a bit is on in the mask, that equivalent bit in the address is interpreted as a network bit. If a bit in the mask is off, the bit belongs to the host part of the address. The subnet is only known locally.