Building Automation Knowledge Base

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Product Line TAC Vista Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and 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 to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Satchwell CZU Mk2 Zonemaster Controller requires replacement. Product Line Field Devices Environment Stand alone Fan Coil Unit Temperature Controller. Satchwell CZU Mk 2 Zonemaster Controller. CZU 2201 CZU 2202 CZU 2203 Cause Obsolescence of Satchwell CZU Mk 2 Zonemaster Controller. Resolution Replacement of Satchwell CZU Mk 2 Zonemaster Controller with S-E Satchwell CZU Mk 4 Zonemaster Controller. The CZU 4201 may be used to replace the following CZU Mk 2 Controllers :- CZU 2201, CZU 2202, CZU 2203 N. B. CZU 2201 Controllers provided an additional -9 to +9 V d.c. output enabling connection to peripherals such as the Satchwell NSU 1401 Night Set-back Override Unit, TSU 1402 Two Step Auxiliary Unit and SSU 1403 Signal Selector Unit. CZU 2202 and CZU 2203 Controllers provided an additional -0.5 to +9 or -9 to +0.5 V d.c. output enabling connection to the Satchwell NSU 1401 Night Set-back Override Unit.  Additional outputs are not provided on the CZU 4201 Controller and in those applications where these are required then it will be necessary to consider an alternative Controller to the CZU 4201. Details of the CZU 4201 may be viewed here. A remote Satchwell Adjustable Room Temperature Sensor such as the DRT 3451, or a remote Satchwell Duct Temperature Sensor from the DDU range of Sensors may have been installed and connected to the Controller. Any existing remote Satchwell Temperature Sensors may be retained for connection to the CZU 4201. Should the remote Satchwell Adjustable Room Temperature Sensor require replacement then this may be replaced by an S E STR 612 Adjustable Room Temperature Sensor. Details of the STR 612 may be viewed here. Should the remote Satchwell Duct Temperature Sensor require replacement then this may be replaced by an S E STD 670 Duct Temperature Sensor. Details of the STD 670 may be viewed here

Issue Satchwell CD2401 Proportional Controller-Actuator requires replacement. Product Line Field Devices Environment Stand alone discreet Satchwell CD2401 Proportional Controller-Actuator Cause Obsolescence of Satchwell CD2401 Proportional Controller-Actuator Resolution Replace Satchwell CD2401 Proportional Controller-Actuator with Schneider Electric Satchwell CZT5305 Proportional Controller, compatible Temperature Sensor and MD Series Actuator and Linkage Kit. Replace Satchwell CD2401 Proportional Controller-Actuator with Schneider Electric Satchwell CZT5305 Proportional Controller. Details of the Schneider Electric Satchwell CZT 5305 Proportional Controller may be viewed here. Replacement of Temperature Sensor It should be noted that although the existing Satchwell Temperature Sensor associated with the CD2401 Proportional Controller–Actuator is obsolete, it is compatible with the CZT Proportional Controller and may be retained. Should it be decide to install a replacement Temperature Sensor however, then the following may be considered. Room Temperature Sensor STR600 series details of which appear here. Duct Temperature Sensor STD660 details of which appear here. Immersion Temperature Sensor STP660 details of which appear here. NB In order to utilize the existing Pocket a Pocket Adaptor DWA0001 will also be required. Pocket Adaptor DWA0001 details of which appear here. OR Surface mounting Temperature Sensor STC600 details of which appearhere. Replacement of Actuator. Whilst the existing Satchwell MB Valve Body may also be retained, a new Schneider Electric Actuator and Linkage Kit will need to be installed on the MB Valve Body in order to permit control from the CZT Proportional Controller. Details of the Schneider Electric MD10A-24 Actuator may be viewed here. Details of the Schneider Electric LMD/AR-MB Linkage Kit may be viewed here.

Issue The modbus RS485 connectors on the MPM-UN are marked MOD A & B, the documentation does not state the polarity. Product Line EcoStruxure Building Expert Environment MPM-UN Modbus Cause Documentation does not state the polarity of the Modbus connectors. Resolution Connect the Modbus device to the A-B connectors on the MPM. Connect the positive lead to connector A and the negative lead to connector B.

Issue When trying to open web pinpoint on a remote client session the users receive the error below: Product Line Andover Continuum Environment MS Server 2008 and newer Windows 7 and newer Continuum 1.9x and 2.x webClient Remote Desktop Cause This issue is caused when a remote desktop connection is made on a Windows 7, Windows 2008 server or newer Operating Systems.  The console becomes locked.  It will stay locked until the local session is restored with a logon. Resolution  Resolution: 1)      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 ***********************************************************************************************   2)      Place this file on the desktop of the Web Server system. 3)      When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be ran “As an Administrator” This will disconnect the session and restore the console.

Issue When trying to connect to a Sigma system from SmartStruxure an "Unable to load SigXmlExport.dll" error message is displayed. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment SmartStruxure Enterprise Server version 1.5 Sigma 4.08 Cause The Sigma to StruxureWare Support files have not been installed to the Sigma installation. Resolution Download the Sigma To StruxureWare Building Operation Support Program from the Exchange Download Center. This additional software allows a Sigma Release 4.08 installation to respond to data import requests from SBO 1.5 and takes Release 4.08 to Build 3.46.66 On the existing Sigma 4.08 Sigma server PC, run SigmaSBOSupportSetup.exe and install the software to completion. There is no need to stop Sigma clients or the server.

Issue Lua Program for measuring EnOcean Signal Strength Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Cause Requirement to measure and alarm from the EnOcean Signal strength. Resolution Download either the txt file or c2g import file. The file is set to monitor 3 EnOcean devices, either copy the relevant sections to add more devices, or remove to reduce the number of devices. An AV is required for each EnOcean Device. In the Lua program, edit the EnOcean Device ID, this can be found in the "EnOcean Device Configuration" properties. In the Lua program, edit the AVs to those that are to be used. Edit the AV and add the ID in the description and any other description required. How the Lua program works: The Lua script is set to assign each AV an abnormal value (10000) after a time period in (3600) seconds. The EnOcean device will overwrite via the program the value in the AV when a value is received from the device. For an alarm, create an Event, set the high limit (9999) and a time period set to a value beyond that a signal is received from the EnOcean device. Set the low limit to -200. Notes: EnOcean devices send packets at varying times, some at change of state. The timer needs to reflect how often a packet is sent. Several Lua programs may need to be used and the EnOcean devices grouped with similar packet broadcast times. e.g. an infrequently used switch would be different to a temperature sensor.

Issue A browser connection to an I/A Series G3 graphic indicates "There is a problem with this website's security certificate.  The security certificate presented by this website was not issued by a trusted certificate authority." Product Line TAC IA Series Environment I/A Series G3 (builds 3.6 and earlier) Cause The message is related to the I/A Series G3 Crypto Service that provides Secure Socket Layer (SSL) technology between a browser and an ENC or ENS with web services.  SSL encrypts the http for communications security.  Security certificates are used as part of the https protocol to validate the targeted website and encrypt the data transferred between the browser and the site. Resolution The certificate included with the I/A Series G3 Crypto Service is a Tridium certificate, which is valid through 2054. The certificate is self-signed and the browser cannot validate it's authenticity with a trusted root certificate. Depending upon the browser and administration of rights, some browsers will let you add the certificate so that the message is not seen again. Other browsers will not, causing the message to be seen upon each connection to the website. One option available to network administrators is to generate a site specific certificate that identifies the server as trusted.  The following document details a step by step process utilizing the SSL resources of the standard Java Runtime Engine (JRE).  The TridiumProvider.jar is also provided. Note: Do not use the JRE installed and used by Niagara G3.  The JRE for the computer is typically located in the \Program Files\Java directory. The process involves adding a security provider to the local java.security file followed by the generation of a key pair with the user's information.  A certificate is then generated to provide the Certificate Authority.  Once signed and returned, the signed certificate is used to generate and package a custom site specific ssl.tks file for G3. SSL Installing a Signed Cert (3.6 and earlier) updated 9-5-2012 TridiumProvider.zip

Issue Is it possible thru PE or any other means to have more than 4 site codes assigned to a door in Continuum? A developer of a multi-tenant building has more than 4 clients all using HID proximity cards but each with different site codes. The main entrance is common to all tenants. How can the developer put a card reader on it with Continuum? Product Line Andover Continuum Environment CyberStation AC-1 family ACX family Cause Is it possible thru PE or any other means to have more than 4 site codes assigned to a door in Continuum? Resolution A single door object in Continuum is limited to the 4 site codes. If you do not need alarms, i.e, you just need an electronic key then there is a hardware workaround. Add a reader distribution amp like the RDA1 from ETS of Albuquerque, NM. The input of the RDA1 is wired to the card reader at the door. The outputs of the RDA1 are wired to multiple Continuum reader ports (AC-1s or ACX). Create another door object with the same arealink. Now you have 4 more site codes. You'll need to do some input and output re-wiring and every card read will give you at least one invalid attempt (invalid site code on one of the two door objects). If you can live with that, you're all set.  

Issue Satchwell “MM” combined Actuator & 3-port Valve Body assembly requires replacement. Product Line Field Devices Environment Stand alone Satchwell “MM” combined Actuator & 3-port Valve Body assembly. MM Actuator 3-port Valve Body Cause Obsolescence of Satchwell “MM” combined Actuator & 3-port Valve Body assembly. Resolution Replace Satchwell “MM” combined Actuator & 3-port Valve Body assembly with Schneider Electric MD10B Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “MM” combined Actuator & 3-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. It is possible that the "MM" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.

Issue When adding a new reader to a controller, the readers status shows "Unknown" in the hardware tree. Product Line EcoStruxure Access Expert Environment Access Xpert Version 2 Hosted & Premise Install Cause The newly added reader has not been brought into "Online Mode" Resolution From the hardware tree right-click on the reader and select "Online Mode". The reader should now show up as online, and the user should be able to control the door operation.     **Note - If unable to put the readers into online mode, it is necessary to first make the controller active, as shown below. After selecting this, a reboot of the controller is necessary for the changes to take effect. 

Issue On an existing InVue installation, some additions to graphic screens are being done with ActiveX Controls.  The only one being used for these additions is 'SECValueDisplay Control'.  Each graphic already has several of these ActiveX controls.  After a copy and paste of an existing one, a right-click to go to Properties returns no pop-up box.  There is no way to modify the copied (or existing) ActiveX controls. When clicking on the wizards hat in the toolbar, the ActiveX Controls are missing from the list (see below). Product Line TAC IA Series Environment Wonderware for Intelligent Buildings (WIBS) version 1.1 Cause Support for the ActiveX Controls specific to the 10 starting with "SEC..." is disabled. Resolution To restore the proper settings for ActiveX Control support, follow the steps below. Find to the Wizard/ActiveX Installation setting (see image below). Select all ActiveX controls that start with "SEC...".  There are ten in total (see image below).  Use the CTRL key to make multiple selections. Click the Install button and all ten ActiveX controls appear above in the "Installed ActiveX controls" area. Close the window and now a Properties screen appears allowing for modifications.

Issue Access Expert is able to communicate down to the SSC (a reboot works) but the SSC won't come online and its status shows as unknown. Product Line EcoStruxure Access Expert Environment SSC Cause In IIS the binding has been configured incorrectly. (On Premise ONLY) Mercury port (3001) blocked.  Resolution This is what a properly configured binding looks like. (On Premise ONLY) Reference How to verify ports needed for AX-SSC communication with the Access Expert server are open from within the AX-SSC itself to check status of the Mercury port, if block work with IT department at the site to have it unblocked.

Issue How to create a successful LDAP Query on Version 3. Product Line EcoStruxure Access Expert Environment Win 10 and above Version 3 Premise Hosted Cause There are no instructions on how to create an LDAP Query to bring in users from Active Directory.  Schneider Electric does not normally write the queries as these are duties more geared to a LDAP person or IT person who is familiar with the structure of the AD. Resolution The following steps are needed to create a successful LDAP Query: Make sure the LDAP appliance or Service is running and that the default port 389 is opened From Access Expert, select the General Configuration Tab and then the LDAP Agents Once opened, create a new LDAP Query by entering all the necessary fields and information to connect to the AD (Active Directory) Enter the mapping fields in the Set Person Mapping fields When Finished click on the Save button that will run the query Select the Access Control Tab and click on the List Icon If the query was successful, then all the users that the LDAP Query was based on will be displayed If it was unsuccessful, then it would be blank.  To troubleshoot any issues, connect to the appliance if possible and browse to the SEQ Folder Open up the Browse SEQ Look at what is displayed on the window to determine what the issue could be Click on the Error on the Right Side of the Window to bring up the Error Messages View the error and correct accordingly (for the most part it is probably the query having extra spaces) Once corrected, re-run the query and verify that it updated correctly by following step 6 again

Issue Communicating with a controller via its LAN connection, is not possible when connected to another controller's service port. Product Line Satchwell Sigma Environment Sigma all releases Sigma all firmware versions. Cause The Sigma system is not complete, messages generated by the controllers cannot be sent to the Sigma server and therefore build up in the Alarm Buffers, this can prevent communications with other controllers.. Resolution If a system is to be left without access to the backup/default Sigma server, then the following actions should be taken: Do not programme any object alarms. Do not configure any system logging. Unless the network configuration allows access to all the appropriate controllers, do not configure globals. Create an "Archive" of the controller. If the time period without the Sigma server is to be less than 5 days, then it is possible to "Set Controller Mode". To set the controller mode, go to System Diagnostics, then Options for the appropriate controller number, and then chose "Set Controller Mode". The following options are displayed. Select the items you wish to inhibit, and set the time in minutes, (a maximum of 7200 can be set).

Issue With the "Apply initial value" property activated in a script program, there may be confusion on how this impacts the operation of the program after a cold start of the controller, which includes system upgrades. Product Line EcoStruxure Building Operation Environment Script Programs Cause In SmartStruxure versions up to and including 1.9.X, when the “Apply initial value” property of a script program is set to Yes, then the following scenario will occur upon a cold start of the server; The inputs, outputs, and public numerics will revert to the initial values set in the script program. Note: It is important to keep this in mind before upgrading a site that has script programs in the database. If the “Apply initial value” setting is Yes, then the Input, Output, and Public Numerics will be re-initialized with their Initial Value attribute. Depending on whether these attributes were configured and/or the application, upgrade or cold start may result in data loss or unexpected behavior. Resolution Versions up to and including 1.9.X If the values of public numerics need to be retained after a cold start in a script program: The "Apply initial value" property must be set to No. Outcome after a Cold Start: Inputs and Outputs will go to null Public Numerics will retain their last known value   If the values of the public numerics need to go to their configured initial value: The "Apply initial value" property must be set to Yes. Outcome after a Cold Start: Inputs and Outputs will go to their configured initial value Public Numerics will go to their configured initial value   Warning: If "Apply initial value" is set to No, it has been observed in upgrades to version 1.9 that some public numerics do not retain their last known value. The fix for this issue has been assigned to EBO 2.0.

Issue Upgraded Site to Continuum 2.01, now get %N and %D in Alarm Message as seen in the message field in the snapshot below: Product Line Andover Continuum Environment Cyberstation Keywords %D %N Cause This is caused by the Enhanced Alarm Logging and Enhanced Alarm Delivery being unchecked Resolution This can be resolved by using the following steps: Close all the cyberstations Initialise the database making sure you have Enhanced Alarm Logging and Enhanced Alarm Delivery ticked as shown below:  

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the  statistics  from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2)

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 The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121 and 122, which does not have a D1 input. Product Line TAC Vista Environment Xenta 122 STR-150 Cause The correct terminal for the mode input from the STR-122 is labeled differently on the Xenta 122 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 122 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 9 If you are looking for the wiring diagram for an STR-150 into a Xenta 121 the click here. The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 122. When the Xenta 122 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained is it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.