Building Automation Knowledge Base

Issue Manually selecting warm start on the restart variable or using a program to try to set it will not work Environment B3 SmartStruxure Continuum Cause Attempting to set the restart or accrestart system variable to work start will not work and may generate errors Resolution The b3885-V does not have an onboard battery, so the warm start option isn't available. Cool start or Cold start are the only options.  Programs that attempt to set warm start will need to be modified to do a cool start and use backup to flash.

Issue The documentation for the SED-THSU5045 thermostat states that the super capacitor voltage can be measured across terminal strip TB1 terminals 1 and 2.  However, there is no mention of what an acceptable voltage reading would be.  Environment Super capacitor voltage specification is not published on the thermostat documentation. Cause A minimum voltage of 5.5 VDC should be present across TB1 terminals 1 & 2. Resolution If a 5.5 Volts DC charge cannot be maintained on the super capacitor, the device may require either an auxiliary light collector or external 24 VAC.  The Thermistat battery is not designed to run the thermostat for extended periods.

Issue An analog Modbus value has specific values when the system is in error. For example: 0 = No Error 1 = Over Current Acc 2 = Over Current DeAcc 3 = Over Current Constant Speed How could an alarm be defined to trigger when the object has Value = 2? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.5 Cause When using a Modbus analog value, it is not possible to create an alarm on a specific value. Resolution Instead of a Modbus Analog Value, create a Modbus Multistate Input. With a Modbus Multistate Input, it is possible to connect a multistate alarm which gives the option to create an alarm on a specific value.

Issue According to the documentation the max cable lengths for the sensors connected to a Multical device are : Temperature sensors : 10m Flow Sensor : 2,5m Is it possible under any circumstances to extend the cable length up to 15m?   Environment Multical Cause The sensors come in pairs and are calibrated. They must never be extended. The longest length available is 10 metres. Resolution It is not possible to extend the cables to the sensors, as the devices are calibrated with the sensors delivered from the factory.

Issue Are the BCX4040, BCX4000 and b3 line of controllers compliant with the most recent BACnet specification, ASHREA 135 2012? Environment Continuum Controllers Cause The consultant is requiring that all BACnet controllers be compliant with ASHREA 135 2012. Resolution As of August 27, 2014 the BCX1 and b3 family of controllers do not comply with ASHREA 135-2012. This is noted in the PICS statements as the Protocol Revision. The 2004 version of the spec correspond to Protocol Revisions 4, 5 & 6. The 2012 version is Protocol Revision 14 & 15. As of August 27, 2014 the BCX1 and b3 family of controllers comply with ASHREA 135-2004 spec revision.  

Issue Using I/NET Audible Alarms with Remote Clients No audible alarms with Remote Client configuration Product Line TAC INET Environment I/NET Seven Software 2.42 and newer I/NET Remote Client or Remote Client with I/O Server Cause The functionality was changed with the following TrackRecord 5940 fix in I/NET 2.42: Alarms in a Remote Client do not get an audible alarm Only clients configured as "Remote Client w/IO" are capable of routing alarms/events to the server. The masking on clients configured as "Remote Client" will not cause alarms/events to be routed to the server. On these clients, you can use the masking to get audible alarms with no danger of getting duplicate alarms.   Resolution To receive and activate audible alarms on a Remote Client, set the Distribution Group and Masking of the alarm point within AMT.   Note: This setting is only the case for I/NET 2.42 and above.  If this is setting is made in earlier versions of I/NET, it will cause alarms / events / trends to be routed to the server and possibly can cause duplicate events / trends to be sent to the server.  The following information is noted in TCON300: "Limitations to TAC I/NET Seven on Remote Clients   Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features:   Network functions                 Automatic DPU restore                 Archiving                 Dial after edit   Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed." "Limitations to TAC I/NET Seven on Remote Clients" Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features: Network function Automatic DPU restore Archiving Dial after edit Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed."  

Issue Integrating to Zigbee devices not available in Building Expert Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi Purpose Manager SmartStruxure Lite Building Expert Cause The Zigbee device is not available in Building Expert Resolution Zigbee devices are fairly complex to integrate when compared with EnOcean devices and requires development work from the engineers in R&D. Therefore, depending on the business case in your region, it has to be discussed with offer management on whether it could be part of the roadmap or not. You are reach out to the regional product managers to discuss about the opportunity. APAC - EMEA Dusan Janjic (dusan.janjic@schneider-electric.com) Ilda Metani (ilda.metani@schneider-electric.com)  North America Michael Sabinash (michael.sabinash@schneider-electric.com) South America Marcelo Varde (marcelo.varde@schneider-electric.com)   To be able to build a driver for a 3rd party Zigbee device, the following information are required. IEEE Address Endpoint(s) Cluster(s) Attributes Instead of waiting for R&D to build a driver though, you can always write your own script using the information above. However, no active support will be provided by our support teams.

Issue SHR100-T is obsolete and needs to be replaced Environment SHR100-T Room humidity sensor Cause Replacement of obsolete sensor Resolution The SHR100-T is replaced by SHR110-T with part# 006903115

Issue Cannot learn EnOcean thermostats into the MPM. Environment MPM, EnOcean Cause Purchased the wrong EnOcean frequency MPM. Can the antennas just be changed?  Resolution No, just replacing the antennas will not resolve the problem. The MPM controller and antenna must be replaced to match the frequency of the Enocean thermostats. Note: the 315 MHz EnOcean MPM uses an antenna with green stripes; the 902 MHz EnOcean MPM uses an antenna with yellow stripes. 

Issue How many SC2300 could be connected to one SE7300 or 8300? Environment SC3000 SE7300 SE8300 Cause Inputs from the relay packs could not be connected in parallel. Resolution It is not possible to connect inputs in parallel, therefore you could only connect one relay pack to one device.

Issue There is a display issue with PE programs running in a b3 device, depending on program code the current line shown maybe incorrect showing a line that is NOT the line the program is currently at, this issue exists in all versions of SBO. Note that program execution is not effected, the execution of the program iscorrect, it is only the CL shown that maybe incorrect. Issue will be fixed in SBO 1.6 Environment Workstation AS b3 Cause Firmware defect Resolution The defect has been corrected and the fix will be released in SBO 1.6 Currently there is not hot fix available for this issue.

Issue Structured SNVTs disappear from database following a LearnNv. Product Line TAC IA Series Environment G3 versions 3.6.406, 3.7.106, 3.8.37 Cause Modifications made to the LonWorks jar. Resolution Download and install the new LonWorks jar for the revision in question. See Lonworks 3.8 to obtain the latest LonWorks modules.

Issue How to bring an MPM-VA online over ZigBee to communicate with the ZigBee Coordinator (which is also the MPM you have your IP interface with). Environment MPM, MPM-VA, ZigBee Cause Cannot figure out how to get the MPM-VA to communicate over ZigBee to the Coordinator. Resolution Use web interface on the bench to set up ZigBee Pro Extended Configuration on the "remote MPM-VA" to match the Coordinator's Channel, PAN ID, Extended Network ID, Stack Profile, Security Profile and Trust Center Link. Save settings and save database to flash. You can now disconnect the IP connection to the remote MPM-VA. Re-discover controllers from the Coordinator MPM. It will appear as a "peer" below the coordinator, i.e., it will not be "under it" like a Room Controller (stat) or TE2.  

Issue The Schneider Universal Plug-In 2.5.1 s registered in StruxureWare and the XIF file for the MTN880601 is imported into the StruxureWare database.. After adding the device and choosing Configure, the Plug-In is not launched. Instead comes an error message saying, that no plug in matches the program ID. Environment StruxureWare OpenLNS Cause XIF files that, during the installation, is not placed in the Import folder, may not be registered correctly in OpenLNS. Resolution In the StruxureWare Control Panel, under "LNS Plug-in Registration", you may have a selection "Import device templates in LNS." Select this to import the XIF file (device template) into OpenLNS database.

Issue How to display a binary on/off value for fan the following hardware outputs for a Xenta 102-AX graphic page: Fan command Heat 1 command Heat 2 command Damper open Damper close Environment Xenta 102-AX StruxureWare Building Operation TGML Graphics Cause Universal Outputs 1, 2, and 3 on a Xenta 102-AX are controlled via percent based values. Through hystereses, they will turn on and off. Without knowing the previous status of the output, values between 1% and 99% will be unclear as to the present value of the output. Note: due to this SNVT being of a user-defined type, TAC Vista Workstation is unable to display these values. This solution can only be applied to a SmartStruxure Solution. Resolution Navigate to the Xenta 102-AX object in Building Operation Drill down to Node Object [0] > nvoRawHwValues > Universal Outputs Current Value Use the following signals for a true/false status of each command: Damper Drive Down State Damper Drive Up State Universal Output1 state (fan) Universal Output2 state (heat 1) Universal Output3 state (heat 2)

Issue JACE 645 Ethernet ports usage Environment JACE 645 Network Controller Cause JACE 645 has 2 Ethernet ports.  Resolution LAN1 is the primary network port for the JACE645. As per the JACE Install and Startup Guide, LAN2 (secondary port) can be used in the following scenarios.  Intended usage (of LAN2) is for: - Isolating a "driver's" Ethernet traffic from the primary (LAN1) interface. OR - In some cases, LAN2 may be set up with a standard, fixed, IP address that is used only by a company's service technician, when on site. This allows access to the JACE without disconnecting it from the customer's network, or without connecting the technician's service PC to the customer's network (which might go against local IT security policies). Note that only one LAN port can be set as DHCP. If enabling LAN2, you typically specify another (network) static IP address and the appropriate subnet mask. Also note the following: If enabling both LAN ports, note that the LAN1 IP address and LAN2 IP address must be on different subnets, otherwise the ports will not function correctly. For example, with a typical "Class C" subnet mask of 255.255.255.0, setting Interface 1=192.168.1.99 and Interface 2=192.168.1.188 is an invalid configuration, as both addresses are on the same subnet. A JACE does not provide IP routing or bridging operation between different Interfaces (LAN ports, GPRS, dialup). All of this also applies to the "third interface" provided by the "WiFi option" if installed in a JACE (at the time of this document, available for a JACE-700 only). However, it is likely the WiFi interface will be used as the primary interface in most cases (no LAN cabling available to the JACE).

Issue Which SQL collation setting should be used with StruxureWare WebReports? Environment StruxureWare WebReports installation and settings. Cause IT departments may wish to know which settings are/should be used if they are managing the Reports server SQL database. Resolution During the installation of Report Server,  the collation settings are configured automatically for 'StruxureWareReportsDB' at the database level and not at the SQL Server level. Irrespective of any collation settings at the SQL Server level.

Issue When trying to login to Linux console via Device Administrator the console display says the Admin account is locked out.   Environment StruxureWare Building Operation 1.5 Linux WinSCP Cause Linux cannot be accessed via Device Manager Console or utilities like WinSCP. Resolution Access to Linux in the AS no longer available in StruxureWare Building Operation 1.5

Issue Distributed Link Architecture DLA with StruxureWare Building Operation Environment Large TAC I/NET Seven site with StruxureWare Building Operation installed Cause Does Distributed Link Architecture (DLA) supported with StruxureWare Building Operation as the front end? Resolution TAC I/NET allows you to define a system-wide total of up to 100 links in order to connect controller LANs to the TAC I/NET system. In the traditional TAC I/NET system, if you use Xenta 527 Routers (NPRs) to connect remote controller LANs (i.e., sites) to TAC I/NET, each site consumes one unique link address. This limits the traditional TAC I/NET system to a maximum of 100 sites. The purpose for adding Distributed Link Architecture (DLA) capabilities to NPRs, and to the TAC I/NET IOServer, is to allow multiple NPRs to share the same link number. In a system that is configured to use DLA-enabled NPRs, up to 64 sites can share a single link address. The shared link is referred to as a distributed link. The use of distributed links allows the TAC I/NET system to support up to 6400 sites. Note: TAC I/NET’s system-wide limits of 6,400 controllers and 100 link addresses must be observed, regardless of whether or not DLA functions are enabled. For example, if your TAC I/NET system already contains 6400 controllers, implementing DLA will not allow you to expand the system with additional sites of controllers. TAC I/NET Seven DLA is supported with Building Operation

Issue Are mirrored values or mirror programs required in the AS when interfacing to MNB controller objects? Environment Automation Servers or Enterprise Servers Cause Confusion around this subject. Resolution No, since the MNB controllers support COV subscriptions it is not necessary to create mirrored values or programs in the AS.