Building Automation Knowledge Base

Issue CE Declaration of Conformity Certificate for manufactured cables for interconnecting EBO modules. Product Line EcoStruxure Building Operation Environment Cabling Cause No CE Declaration of Conformity available for the SXWSCABLE10001 and SXWSCABLE10002 that connects EcoStruxure Building Operation AS-P and IO modules when fitted for example: when modules need to be mounted on separate DIN rails. Resolution CE Declaration of Conformity certificate is not required for an item e.g. premanufactured interconnecting wiring that has no functionality or is inert to the operation of the system.  Europe – CE Marking In general, CE Marking Directives are aimed at products, not at components, although there are some exceptions. Wire and cable products are one of those exceptions that stand out. On its own, wire or cable has no defined use or application, in that it must be built into something to be useful.

Issue Security Expert Smartcard Readers support for DESfire EV2 Cards Product Line Security Expert Environment Security Expert Smartcard Readers DESfire EV2 Cards Cause There is a requirement to use DESfire EV2 cards in a Security Expert system. Currently, the Security Expert Smartcard Readers' specifications sheets indicate support for DESfire EV1. Resolution New Smartcard Readers with firmware v1.04 build 229 and above support DESfire EV2. Older readers' firmware can be upgraded with the new firmware. Contact your Local Country Support for details on upgrading the firmware.

Issue Many users are unsure of the implication of the field "Interval time zone" in the Trend Log configuration window. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Cause The setting "Interval time zone" under the Trend log configuration has caused some users to believe that this setting stores trend data in either "UTC" or "Server local time" Resolution The trend log data is always stored in UTC time, regardless of the option selected under this setting. This setting is intended for preventing problems with Daylight Savings Time (DST) when the logging interval is more frequent than 1 hour. See Interval Trend Log Properties – Basic Tab in EcoStruxure WebHelp. NOTE: When the interval is longer than 1 hour and you want to continue to log that interval after a DST change, use Server Local Time. For example, the log interval is every 24th hour at midnight and you want to continue to log at midnight even after a DST change, so you use Server Local Time. During the DST change in the Spring, the log sample will register after 23 hours. After the DST change in the Autumn, the log sample will register after 25 hours. Interval Time zone 

Issue When creating a BACnet trend log in an offline IP controller (e.g. an MP-C), the following properties are visible and can be adjusted: Delta Align intervals Interval offset Before download to the MP-C: After downloading to the MP-C these properties are not visible anymore. After download to the MP-C: Product Line EcoStruxure Building Operation Environment SmartX IP Controller Building Operation Workstation Cause Before downloading a “generic” object to a BACnet device, Workstation doesn’t know what BACnet properties the device supports and which it does not support. Therefore it will display the full super-set of BACnet properties for the given object type to the user. When the object has been downloaded, any property not supported by the device will be removed from the editor. Resolution This is by design.

Issue Trying to create a Lon binding from two or more nvo's in one Lon device (hub) to two or more nvi's in many Lon devices (targets), a so-called fan-out binding. The binding between the first Lon devices works fine, but when trying to create the binding from the Hub Lon device to the second Lon device (target) it does not work. The binding window for the second Lon device (target) is opened; the Lon device (hub) is chosen in the browser window on the right side; and the nvo in the hub is dragged to the nvi in the second target device. But the binding tool will not accept this binding. It is not possible to release the nvo from the Hub Lon device on the nvi in the second target Lon device. Product Line EcoStruxure Building Operation Environment Building Operation Workstation LON Devices Cause Normally when creating a binding using the EBO binding tool you open the binding window for the target (receiver of the value). But in this particular case you need to do it the other way around and open the binding window for the hub (sender of the value) instead, and then drag the target to the hub. Read more about Fan-out Bindings in the Webhelp. Resolution Go to the Lon device with multiple ins or outs (hub) and open the bindings window In the browser window on the right side find the target Lon device Drag the nvi from the target device to the nvo in the hub Lon device

Issue An SP-C-WEB needs to be upgraded.  Can this be done without removing the controller? Product Line Security Expert Environment Security Expert Controller (SP-C) Security Expert WEB Controller (SP-C-WEB) Cause Due to site expansion, it is necessary to upgrade an SP-C-WEB to an SP-C.  Resolution It is not possible to upgrade an SP-C-WEB to an SP-C in the field. The SP-C-WEB will need to be replaced and re-programmed via Security Expert Server.

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 deploying ES/AS, it will go through for a while until the end. Then it will show failed, and the cause is communication error. Environment SmartStruxure PCS Cause 1. First check whether there is any real network issue, like router setting, fireware or anti-virus software. If it is confirmed that the network is good, check whether the date/time setting match the current ones. 2. If both are checked for the first point, the cause is there is a defect for PCS when the project contains BACNet interface and objects. Resolution 1. Change the date/time to current ones. 2. If it doesn't work, contact PSS to ask for hotfix: R1.5.0.7201.

Issue BACnet points are not updating in the UNC after the replacement of a BACnet device. Environment Niagara R2, UNC 520 Cause Tech replaced a drive from one manufacturer with a drive from a different manufacturer. The BACnet device object in the UNC was reused. Since the replacement drive was not the same model or manufacturer as the one being replaced, the BACnet points between the two devices are different. The points in the replacement device do not match the points in the reused BACnet device object in the UNC. Resolution The solution would be to delete the BACnet device object in the UNC, discover the replacement device and learn it into the UNC.

Issue Which version of USB serial leads work with Sigma and BAS Environment Sigma BAS Cause Newer laptops do not have an onboard RS232 serial port. Can a USB-Serial converter be used. Resolution Not all types of USB to serial converters work with Sigma and BAS2800+. USB to serial converters work in conjuction with the laptop. Local testing may have to be done to find the best product. Generally, USB to serial leads have 2 version of chipsets, Prolific and FTDI. Note, there are also fake versions of these chipsets, the original versions are available from RS and other well known distributors. Sigma seems to work only with Prolific converters and can work on a low COM port no. e.g. 1, ensure that the comm port is not in use by any other applications e.g. Bluetooth. For Sigma, remember to change the setting in the sigma.ini file when using serial communications. BAS seems to work only on FTDI converters and can work on high COM port no. e.g. 7.

Issue Data not passing from Enterprise Server to Reports Server after upgrading to 1.6 Reports folder does not appear on new 1.6 Reports installations Logon failed at attempt no. XX User account has been temporarily disabled. Contact your administrator. Product Line EcoStruxure Building Operation Environment Building Operation WebReports 1.6 and above Cause New features require additional configuration to allow Reports to function. Specifically, the Reports installation requires that the SystemReportsService user account be enabled before installation.  If this is not done, the steps below must be taken.   For Issue #3: If the user account used to access WebReports is changed through WorkStation, WebReports is still using the previous account password to access the Enterprise Server, this will lock the user account out and if used to log in to WorkStation will indicate that the account is disabled To verify that this is what is causing the lockout, open the Report Agent log StruxureWareReportingAgentLog and check for Logon Failed at attempt xx Reason: User account temporarily disabled.... error is shown. The default path for this log file is: C:\Program Files (x86)\Schneider Electric (StruxureWare)EcoStruxure\Building Operation Resolution During the installation of WebReports, you will see the popup message below. In order for the installation to work correctly, the SystemReportsService account must be changed to enabled before clicking OK. Ensure that SystemReportsService user account is enabled in the Enterprise Server before you proceed with the installation process further. To correct this error after installation: If running stop the Repot Agent Service and wait 1 minute before proceeding Log into Workstation using the admin account Modify the user "SystemReportsService" (or user account used) that is part of the Local domain Check/Change the property "Disabled" is set to "False Change/verify the password Close WorkStation On the Report Server open the program "Building Operation WebReports Administrator" Enter the newly created password for the SystemReportsService (or account used) Click Apply - a successful update should be reported. Click Save Close Building Operation WebReports Administrator Restart the Reporting Agent Service. Verify logins now work. For additional Authentication issues please see the online help topic: Authentication Failed (se.com)

Issue Continuum Security Key does not work and Product Support has requested for it to be sent back to Repairs. Product Line Andover Continuum Environment Continuum Security Key Cause Security Key was not working and needs to be replaced.  Resolution Download the Andover_Continuum_Software_Upgrade_Forms_-_Americas_&_APAC.7z file from the link in this Product Announcement and then fill out the "CyberStation-web Client Option Upgrade.doc" form with the below information. The P/N will be USB REPLACEMENT. A PO# is required for the amount of the part number. Fill out CyberStation-web Client Option Upgrade.doc with appropriate information and send in to  your local logistics team. An Advance Replacement order will be generated to ship a new USB key to the shipping address. You will need to send back the defective key within 30 days of receipt of the replacement key.

Issue From time to time TAC Vista Server stops communicating with LonWorks devices and needs to be restarted. Product Line TAC Vista Environment TAC Vista Server LonWorks Cause There can be various reasons for this. One of the reasons can be, that one or more devices is flooding TAC Vista Server with communication, and the communication finally stops. Among other things, this can be due to one or more TAC Xenta's suffering from the rare memory fault issue described in TAC Xenta 401 - Rare Memory Fault Issue - TPA-MALI-09-0011.01, or that the system program in the TAC Xenta device has become corrupt. To identify the issue, make a communications log as described in Start TAC Vista Communications Log, and open the log with the "TAC Vista Comm. Log Decoder". Filter on "C1" messages, and check if there's extensive communication from one or more devices. If that's the case, you have identified that file transfer loop is the issue. Resolution The first thing to try, is to update the system program in the Xenta. Follow article Download an .MOT file into a Xenta Programmable controller for instructions on how to do that. If that doesn't work, replace the Xenta device(s) causing the massive file transfer.

Issue Can the old Robertshaw T99 temperature sensors be integrated to SBO? Product Line EcoStruxure Building Operation, TAC IA Series Environment SBO all versions Cause Retrofit job installation Resolution According to the RTD-DI-16 specification sheet, the T99 sensor can be integrated to SBO as follows with some limitations. Configuration Use an RTD-DI-16 module with a 2 or 3 wire RTD resistive input. Select 1000 ohm for the Sensor class property of the RTD input object. Configure the Conversion Settings properties of the RTD input object near the endpoints of the temperature range to be measured using values from the T99 temperature/resistance table. Configure the remaining properties of the RTD input as needed. Limitations Input Range. An RTD-DI-16 input configured for 1000 ohm operation is limited to an input resistance range of 500 to 2200 ohms. This will limit the temperature range that can be measured with a T99 sensor to ~115 deg. F maximum. Linearity Error. Depending on the range of temperatures to be measured and the needs of the application, linearity error may be significant. This can be corrected by using a script or function block program to linearize the signal based on the T99 temperature/resistance table values.

Issue Windows installer fails to install an application Environment Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows XP Windows 7 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 8 Windows 8.1 Windows Server 2012 editions Windows Server 2012 R2 Cause Errors with the Windows Operating system are preventing the installation from completing. Resolution Run the file at the link below on the affected PC:   https://support.microsoft.com/en-us/mats/program_install_and_uninstall

Issue After installing Continuum 2.0 SP1 problems are found with two of the System Default Listviewis. Errors This Month returns no results. Personnel_Expired Cards shows all cards not just expired cards. Environment Continuum 2.0 SP1 Cyberstation ListViews Filters Cause Misconfigured Listview qualifier or filter.  Resolution Errors This Month The filter in the listview configuration is set to Root\OneMonthToNow.  It should be set to Root\MonthToNow. Personnel_Expired Cards The listview qualifier needs to be configured as shown below.

Issue AutoCAD wiring symbols for I/A Series MicroNet LON controllers (MNL) Product Line TAC IA Series Environment I/A Series Micronet LON controllers (MNL) Cause The files are not available on the Download Centre Resolution The files can be downloaded from here.

Issue Can I configure (translate) the I/NET Software into another language besides English? Is I/NET supported in different languages? I/NET Seven ver 2.41 supporting the user interface for either Chinese Language (Traditional) and Chinese Language (Simplify).   Product Line TAC INET Environment I/NET 2000 I/NET Seven Cause I/NET is provided in U.S. English language. Translation into other languages is possible with some limitations. Resolution There has been some success observed in translations using a product called Passolo. Although Passolo is not supported by Schneider Electric, you may employ it as a translation tool at your own discretion. More information is available at SDL/Passolo. Note: Passolo does not modify Windows® dialog boxes - this is managed by the language used during installation of the Operating System. This Customer Advisory CA-2001-09 - Update INET2000 and Languages.pdf discusses various items on this issue. Customer Advisory 2001-09 dated 10/1/2001. Within the I/NET Seven CD there is a folder called Inet7-Translation which contains the relevant file used with any translation software.  Update from 2011: for I/NET Seven Ver 2.41 and its support of the user interface for either Chinese Language (Traditional) and Chinese Language (Simplify). Answer: If you are talking about translating language then, yes, it should be translatable through the 3rd party translation program. Although we do not test translation in the lab. Update 2013: There are freelancers who could be of assistance to help your site. https://www.upwork.com site with potential low cost translators.  

Issue Daylight savings do not take effect when it starts on 4th October Environment Multi Purpose Manager 2.15 and 2.16.    Cause Australia starts DST in October and ends in April of the following year. In North America and Europe, DST starts In March and ends in October or November in the same year. The built in DST feature in the MPM assumes that the "DST_Start_month" must be before the "DST_End_Month".  This issue will also applies to countries where the start of DST is towards the end of the year and DST ends the following year.  Resolution This issue has been reported to R&D. The following workaround can be used before this issue is fixed in a future MPM firmware.  1. Configure DST in the MPM to start in April and set DST to end in October. 2. Set the DST offset to -1 hour using the following Lua script in the MPM (add a Lua object and enter the following code)         if not init then            ME.CFG1_Time_Dst_Offset.value = -3600            init = 1         end     if not init then ME.CFG1_Time_Dst_Offset.value = -3600 init = 1 end

Issue How to configure a Niagara G3 ENC serial port for dialup modem. Product Line TAC IA Series Environment ENC-520-2 ENC-410-1 Cause Dialup modem setup. Resolution In the Station, under Platform Services, go to the SerialPortService In the Port Config field, change the setting to Com1_232_com2_modem. Save this setting. Now, go to the Platform of the ENC, and go to Dialup Configuration The Init String should look something like this: ATE0S0=0Q0V1X4&D2&K3\N3%C2&C1&Q5W2 Change the 0 just after the "=" sign to a 2.  This will tell the modem to answer on the second ring. Make sure that the Port field says COM2 Check the Enabled box next to Listen for Calls In the Local IP Address field, type in the IP address of the ENC In the Remote IP Address field, type in an unused IP address on the same subnet as the ENC. Type in a User Name (eg. invensys) Type in a password (eg. niagara) Save your changes, then click the Start button at the bottom of the page.  This will start up the dialup daemon. Re-boot the station in Station Director.