Building Automation Knowledge Base

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.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue How to uninstall PCT 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause The uninstalling instruction isn't documented. Resolution Launch Hyper-V. Turn off PCT VM. After the VM is turned off, select Delete from the bottom right window. Select Delete if the confirmation window prompts. It may take some time depending on the VM size.   Go to the VM location selected during the PCT installation The default installation path is  "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool 2.0"     Right-click on the pct folder then select Delete    

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.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device, but once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

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.

Issue Error message "Access denied" when starting TAC Vista Server Environment Vista Server Cause To start TAC Vista server you have to be an administrator on the computer. Resolution To start TAC Vista server you have to be an administrator on the computer. If you want to log in to TAC Vista with a user that isn't an administrator, you have to run TAC Vista Server as a service. The service has to be started with an account that is an administrator on the computer.