Building Automation Knowledge Base

Issue In some applications, auxiliary switches on the actuator are requested. Environment MD-S1 MD-S2 MD5 MD10 MD20 MD40 MF20 MF40 Cause Aux switches are not included and needs to be ordered separately if application requires them. Resolution MD-S1(1 switch) and MD-S2(2 switches) are suitable add-ons for all MD5/10/20/40 damper actuators.

Issue How long has an Automation Server been running since the last power cycle or reboot? Environment Automation Server SmartStruxure Device Administrator Cause The uptime of an Automation Server indicates how long the server has been operational since the last power cycle or system reboot. This is not currently visible in the StruxureWare Building Operation Workstation, but it is available through the Console interface in Building Operation Device Administrator. By monitoring the uptime of the device this can be a valuable diagnostic tool to determine if power loss occurred, crashes in Automation Server occurred, or other situations that might have resulted in a reboot and what time this occurred. Resolution In the Building Operation Device Administrator connect to an Automation Server (IP or USB) and select the "Open Console" option. Once logged into the Console issue the "uptime" command in the prompt. The uptime will be listed in Days, Hours, and Minutes as visible below: admin@AS-B-RKFDMW:~> uptime  14:18:20 up 1 day,  1:01, load average: 1.26, 1.16, 1.06   If you are using Report Server, this information is also available using SQL Server Management Studio from the Report Server PC. Enter the following query and the "Runtime" column will provide the current uptime for the specified ES or AS. SELECT Top (1) CAST(CURRENT_TIMESTAMP - DateTimeStamp AS Time) AS 'Runtime' ,DateDiff(Day, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Days Up' ,DateDiff(HOUR, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Hours Up' ,DateDiff(MINUTE, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Minutes Up' ,DateDiff(SECOND, DateTimeStamp, CURRENT_TIMESTAMP) AS 'Seconds Up' ,[DateTimeStamp] ,[TYPE] ,[OriginatedServer] ,[OriginatedDevice] ,[SystemEventId] FROM [StruxureWareReportsDB].[dbo].[tbEvents] WHERE SystemEventId = 'Server initialized' AND OriginatedServer = '/Server 1' ORDER BY DateTimeStamp Desc   NOTE: Change the WHERE statement "OriginatedServer = '/Server 1'" so that '/Server 1' become '/yourServerName'

Issue How can a TreeTech database be moved from one computer to another? Environment TreeTech - all versions Cause New pc purchase Resolution The project backups are stored in a "Jobs" folder.  The folder location in Windows 7 is:  C:\ProgramData\Schneider Electric\TreeTech\JOBS The folder location in Windows XP is:  C:\Documents and Settings\All Users\Schneider Electric\Jobs Use any compression utility to create a .zip or .rar of this folder.  Unzip the file in the destination computer in the same folder path.

Issue Why is not nvoSpaceCO2 propagated in TAC Xenta 121-FC? Environment TAC Vista TAC Xenta 121-FC Cause You must have a binding for the SNVT to be propagated. Also, not all SNVT are sent by heartbeat (please note that the tooltip text in ZBuilder was corrected in version 5.1.7). Resolution Make sure that you have a binding from the actual SNVT. Make sure that the value is changed more than the actual setting for propagation.

Issue Need a report of personnel that have not accessed the facilities in some specified time. Environment CyberStation Cause Documentation Resolution Create a List View of the Personnel class Add desired columns (Name, Card Number etc) In the Qualifiers tab add the following advanced qualifiers TimeEntered <= MyCyberStation\Date - xxx where MyCyberStation is the name of the workstation object and xxx is a number that represents the number of seconds going back in time. For example to generate a list view report of all personnel that have not accessed the facilities in a day enter the following qualifier TimeEntered <= MyCyberStation\Date - 86400  (86400 is the number of seconds in a day) For a qualifier for a month enter... TimeEntered <= MyCyberStation\Date - 86400 * 30

Issue Why does not my Host bindings show up in TAC Vista? Environment TAC Vista Echelon LonMaker Cause Host Bindings in TAC Vista could only be from other devices in to TAC Vista, to be able to show values in TAC Vista. It is not possible to have Host Bindings from TAC Vista to other devices, because these points do not have any information holder in TAC Vista, it is only virtual points. Resolution Host Bindings in TAC Vista could only be from other devices in to TAC Vista, to be able to show values in TAC Vista. It is not possible to have Host Bindings from TAC Vista to other devices, because these points do not have any information holder in TAC Vista, it is only virtual points. From the manual: You should not use group bindings when binding to the host. Important To make the host SNVTs available in the Vista database, the check box Export Host Bindings to TAC Vista Database must be selected. The check box is found in Vista System Plug-In in the Settings dialog on the TAC Network menu. Note Digital and multistate SNVTs should be sent as soon as a change of state occurs and analog SNVTs should be sent as soon as they reach a defined limit. All SNVTs should be sent with a heartbeat determined by the priority of the information. For more information about how to set these parameters, see the LonWorks device documentation.  

Issue Replacement stuffing box/stem seal Environment stuffing box 100108100 VG321 VG222 VG311F Cause When leaking by the gland, a stuffing box replacement may sometimes help. Resolution Replacement/spare stuffing box for VG321, VG311F and VG222 DN65-DN150 is part no 100108100.

Issue Need to Export a Trend log file without using Reports Server Product Line EcoStruxure Building Operation Environment SmartStruxure Workstation Cause Customer needs a log file, but does not have Report Server Resolution In Workstation, right click on a Trend and create a new Trend Log List View Once the List populates, click on the Icon showing a green arrow labeled .csv Save the file to an appropriate location. If this is a frequent action, save the Trend Log List View Please Note that this feature is not available in WebStation  At v2.0 WebStation introduced the option to export to Excel, creating an XLSX file, this can be opened in Excel and saved as a CSV if required (this option is not available if WebStation is directly logged on to the AS/P/B)

Issue When doing a binding using relative path the folder name is included in the binding. When clicking on the relative path button the binding looks like it should without the folder name but it is no possible to save it like that. Environment StruxureWare version 1.3 Cause In the folder name a space was used.   Resolution When taking away the space in the name the relative bindings looked like the should, no folder name in them.

Issue Does the Enterprise Server license have a 'node count' like the server license in Niagara R2? Environment SmartStruxure Niagara R2 Cause Comparing the order processes between I/A Niagara R2 and SmartStruxure Resolution The Enterprise Server has an open license.  There is no 'node count' built into it as is the case with Niagara R2. Keep in mind that version 1.3 of SmartStruxure supports a maximum of 32 AS controllers (for optimum system performance).

Issue The temperature reading randomly  fluctuates between 69.5 deg and 327 deg. Environment Controllers with SPWR / Smart  Sensor support. Cause This situation can be the result of running one 6 conductor cable for all of the wiring to the thermostat; including the 24 VAC for the LED light.  The 24 VAC is causing interference with the temperature  input . Resolution Use a different cable for the LED light 24 volt.  Use 0-5 VDC to feed the LED Light.

Issue A replacement motherboard is required. Environment Motherboard Cause Motherboard has failed. Resolution It is not possible to order a new motherboard only for an X96 controller. To obtain a new motherboard order either an S-696 or a S-796, this will consist of the case, power supply unit, and motherboard.

Issue Which valves sizes are available for the V241 valve? Environment V241 Cause Size specifications for V241 valves. Resolution The V241 valve is available in the following sizes: DN15, DN20, DN25, DN32, DN40, DN50. Some of these are available in different Kvs values. For more information and details, please see the V241 data sheet available on the Extranet.

Issue Obsolete heat controller Environment TAC200 TA200 2001000000 2001000009 Cause Obsolete product, no longer available for ordering Resolution The TAC200 controller was made obsolete in the end of 2011. No replacement product is available in the TAC range.  The Satchwell DC1100 and DC1400 offer similar functionality, but require Satchwell sensors.

Issue An R2 station is unable to communicate with any BACnet -MSTP controllers. Error in Standard Output Window: "ERROR: Cannot open BACnet MSTP Driver tridium.nre.DriverException: Cannot open Com5 [mstp]       at tridium.nre.vxworks.mstp.VxWorksMstpDriver.doOpen (bytecode 46)       at tridiumx.bacnet.services.link.mstp.MstpLinkService.start (bytecode 63)" Environment R2 station with BACnet/ MSTP trunk Cause The port specification is case-sensitive, and Com5  incorrectly includes lower-case characters. Resolution The MSTP port specification should be changed to COM5.

Issue Is it possible to configure a door so that a card holder can gain access using only his unique pin number. Environment Continuum Access control Personnel objects unique PIN Cause Cardholders often lose their cards and need access to an area. Resolution For PIN only validation to work the Unique PIN option under Allowed Credentials must be selected. * On door object Deselect all Access Validation. Under General Access Validation, select Validate PIN. *  If Unique PIN is not selected, cardholders using a valid pin will be able to gain access through the door, but Continuum will be able to provide reliable cardholder information for access events at this door. There are security issues that make it necessary for the badging personnel to issue a predetermined and available pin number to the cardholder. 

Issue SmartStruxure integration to StruxureWare Data Center Expert via EcoStruxure WebServices Environment StruxureWare Building Operation EcoStruxure Web Services StruxureWare Data Center Expert 7.2.0 Cause There is a need to have StruxureWare Building Operation pass data to StruxureWare Data Center Expert using EcoStruxure Web Services. StruxureWare Building Operation Web Services is capable of both 'Serve' and 'Consume' functionality. However, StruxureWare Data Center Expert (version 7.2.0) is only capable of Web Services 'Serve' function. Resolution Use Modbus TCP instead of EcoStruxure Web Services if StruxureWare Data Center Expert is required to read from StruxureWare Building Operation. 

Issue Longtext messages not correctly upgraded can cause the Sigma server to stop. Environment RAM Remote Alarm Manager Longtext Server shuts down Cause Upgrading of the Longtext messages was not carried out correctly. Resolution All new Longtext messages were added correctly, but messages that existed before the upgrade were copied in and not upgraded. The result of this was that the Sigma server would periodically stop. When upgrading Sigma from a release earlier than 4.05, ensure that the Longtext folder is present in the Data folder, then run the Sigma upgrade programme.

Issue Changing an I/NET DI to a DA does not show up in StruxureWare Building Operation Workstation Environment I/NET SmartStruxure Integration Cause After integrating I/NET to SmartStruxure the designed intent is to allow all point name changes and alarming to be done in SmartStruxure workstation.  If you delete a point and re-create it using the same point address, point name but a different point type, the change will not show up in SmartStruxure. Resolution To successfully change an I/NET point from DI to DA: Delete the Point using the I/NET Resident I/O Editor Re-create the Point using the I/NET Resident I/O Editor using the new point extension DA. YOU MUST change the point name in some way. Perform a Station Save Open Building Operation Workstation Right Click on the Controller and select Update.

Issue Sigma devices connected to an Ethernet Cat7 network? Environment Network Ethernet Cat5e Cat6 Cat7 Cause Connecting Sigma devices to a Cat7 network. Resolution Ethernet networks are categorised by numbers, 5e, 6 and 7 for instance. These numbers refer to the cable types used and the speed they are capable of communicating at. With this in mind, Sigma devices mostly communicate at 100M, so as long as the switches they are connected to will communicate at this speed, Cat5, 6 or 7 does not matter. Below is some general information on the Cat numbers. Cat5/5e. This is the older standard for Ethernet cabling, used by older equipment which was capable of either 10BaseT (10MBs) or 100BaseT (100MBs). These cables used 4-pair, twisted, unshielded cable. Cat6 Increases cable's frequency rate to 250MHz, instead of the Cat5 and Cat5e's 100MHz spec. It allows faster and more reliable transfer speeds, especially when combined with Cat6's improved insulating qualities. In fact, these two features combined make both Gigabit and even 10-Gigabit speeds possible, though the maximum cable length is halved to around 55m when using the latter. Cat7 Increases cable's frequency rate to 1000MHz, To achieve this, shielding has been added for individual wire pairs and the cable as a whole. Besides the foil shield, the twisting of the pairs and number of turns per unit length increases RF shielding and protects from crosstalk.