Building Automation Knowledge Base

Issue Cannot order the VZ*8 valves, its no longer available.  Environment VZ*8 VZ*08C Cause A new line of VZ valves is now available. Resolution The old VZ series actuators have been replaced with a new. The old (VZ*8) is replaced by the VZ*18. for more information and details, please see PA_00156 and the related data sheets. Click here.  

Issue One of many methods that can automatically backup SQL Express 2005 databases Product Line Andover Continuum Environment SQL Express Continuum Cyberstation Standalone Cause Some customers are looking for a way to automatically have a database backed up on a schedule. Since the free limited version of SQL express that comes built into Continuum for smaller site setups does not come with a front end, backups of the database must be performed via windows command line utility. There are commands available to run at the windows command line but this article will help with performing this operation automatically and on a schedule of your choice whether is be daily, weekly, monthly. This is accomplished by creating a  batch file and using the windows task scheduler. Help on using the task scheduler and also creation of batch files can be found on a simple Google search. In the resolution section below we give one example of how to set this up. Resolution Open up notepad and paste in the sample query below. Please note that you may need to change the query a bit to adjust to your sites needs. Here is the query. Please note the bold and underlined text. You will need to put your machine name and also your SA password in the bold and underlined sections. Also notice where the words backup database continuumdb is in the query. Your database might be named something else, but you can find that out by viewing the database tab of the Continuum database initializations workstation editor. Lastly notice that the location of the backup and the name. In this example there is a directory named DBbackup that you'll need to create for this example or create your own directory and change the path in the query. The name of the backup file is called MyBackup.bak. You will need to change this name to something that is meaningful to your site. The switches below are -S for the servername and in the case of type of command line query -S is your machine since it is the server locally. The switch -U is username and we are using the System Admin account for SQL that was created when the instance was created. The switch -P is password and in this example we are using the sa account so please put in the sa password that you created when first installing SQL express 2005. The switch -Q means command line query and notice that everything in double quotes will be the query. Also notice the single quotes for the path that the database backup will be created at.   sqlcmd -Sputyourmachinename\sqlexpress -Usa -PputyourSApassword  -Q "backup database continuumdb to disk='C:\DBbackup\MyBackup.bak' with init"   Once the query and been corrected and pasted into notepad, save the file as something meaningful like DBbackup.bat notice that the notepad file is not saved as text but as a *.bat file which is a batch file that can be double clicked on to execute. It is advised to test this batch file now to make sure it works. Go to your backup directory and check to make sure you have a backup file. Now the only thing left to do is create a windows scheduled task.  In order to accomplish this you will need to Select Start/All Programs/Accessories/system tools Click on Task Scheduler (this path may vary depending on which windows OS you are running). Under the Actions menu item select Create basic task. Follow the prompts giving your newly created task a name, date to run, time to run Select program and browse to the location you have saved your DBbackup.bat file to. Once created it will run on the time and dates you have selected. You can also select your task in the Task scheduler and right click to run now for a test. IMPORTANT NOTE: Please keep in mind that automatically backing up the database using this method will continue to replace the old backup and create a new backup. it is highly suggested to always verify the backups and maintain enough disk space to complete these tasks.

Issue The bandwidth utilization in the Lon network is high, it is possible to see what Lon device and what objects in the Lon device that is causing the high load on the Lon network. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause When the load on the Lon network is too high (above 50%) you need to analyze the Lon communication to understand what Lon devices and objects in the Lon device that is causing the high load on the network. Resolution Use a Lon Protocol Analyzer to measure the Lon bandwidth utilization on the Lon network if the load on the network is too high (above 50%) analyze the communication. When doing that it is possible to use the trace log in the ES or AS-P, please see attached video of how that is done.    Configure Trace Log to capture Lon Communications Open Workstation and navigate to [AS/ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon Right-click "nsp.pin.lon.comm" and choose Properties Under Level, change from "Information" to "Trace", then click ok Let it run for a few minutes. If there is some user input needed to recreate the lon issue, then perform these steps now Retrieve the log by right-clicking [AS/ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log Save the log file

Issue A Dashboard is created with a couple of widgets in it, the widgets are placed where they should be and the Dashboard looks good. But if the Dashboard is opened in a monitor with a smaller screen, the available work area for the dashboard is smaller and the widgets move around. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause There is no option to lock the widget positions on both horizontal and vertical axis as the screen area available to the dashboard changes when creating the Dashboard. Resolution Set the Maximum column count in the Dashboard Layout setting to the total number of columns of the desired widget layout. For example if widget one has Column span 2 and widget two has Column span 3 then the Maximum column count should be set to 5 for the Dashboard. Then set the Minimum column size to 0. Now the text still scales but the widgets lock in position.

Issue Parts of the Calectro product range can be ordered through Schneider Electric as Class 3 products. Environment Part number Description 6553066000 VR-2.8M 6553065000 VR-1.5M 6553049000 UG-mounting bracket 6553048000 STB-4-SE base f.smokedet.f.cei 6553047000 NSAOS/i smoke detector 6553046000 NSAIS/i smoke detector 6553039000 Smoke Sensor UG-Cover 6553036000 Smoke detector UG-3-A5O 6553038000 Smoke detector UG-3-O-F 6553037000 Smoke detector UG-3-J-F 6553035000 Smoke detector UG-3-A51 6553017000 Smoke detector UG-2-NS-AOS 6553016000 Smoke detector UG-2-NS-AIS 6553015000 Smoke detector ST-I-LON 6553014000 Smoke detector ST-P-DA 6553013000 Smoke detector ST-I-DA 6553007000 Control unit ABAV-S3 230v 6553006000 Control unit ABAV-S3 24v 6553033000 Smoke detector UG-3-A4I 6553034000 Smoke detector UG-3-A4O 6553028000 Smoke detector UG-3-O 6553027000 Smoke detector UG-3-J Cause Cross referencing Calectro and Schneider Electric part numbers Resolution Part number Description   6553066000 VR-2.8M 6553065000 VR-1.5M 6553049000 UG-mounting bracket 6553048000 STB-4-SE base f.smokedet.f.cei 6553047000 NSAOS/i smoke detector 6553046000 NSAIS/i smoke detector 6553039000 Smoke Sensor UG-Cover 6553036000 Smoke detector UG-3-A5O 6553038000 Smoke detector UG-3-O-F 6553037000 Smoke detector UG-3-J-F 6553035000 Smoke detector UG-3-A51 6553017000 Smoke detector UG-2-NS-AOS 6553016000 Smoke detector UG-2-NS-AIS 6553015000 Smoke detector ST-I-LON 6553014000 Smoke detector ST-P-DA 6553013000 Smoke detector ST-I-DA 6553007000 Control unit ABAV-S3 230v 6553006000 Control unit ABAV-S3 24v 6553033000 Smoke detector UG-3-A4I 6553034000 Smoke detector UG-3-A4O 6553028000 Smoke detector UG-3-O 6553027000 Smoke detector UG-3-J

Issue The extended trend log contains approximately 50% of the configured storage capacity. For example, only 250 entries are in the Trend log view even though the ETL is configured for 500 entries.   After the ETL runs long enough to fill up the 500 entry capacity, ONLY 250 entries are shown in a Trend log list view. (see below)   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause An extended trend log (ETL) includes an equal number of internal entries hidden from view; these entries are overhead incurred in the operation of the ETL. For example, each time a transfer takes place, an internal entry is added. Depending on the specifics of the configuration (i.e., Maximum Transfer Interval), the percentage of internal entries for a given ETL relative to its full size varies. From EBO 3.2.3, the internal entries of an ETL are hidden, and no information is provided to give any visibility into how much storage is being used by internal entries. Resolution The solution is to increase the size of the ETL to ensure there is enough storage capacity for data and overhead. Typically, the size must be doubled (in this case, 1000) in the particular ETL to make sure 500 entries of data can be stored.  Although these transfer events are hidden, it is possible to identify these events by adding the Sequence number column in the trend log list.  It is also possible to decrease the overhead amount stored in the ETL by increasing the "Maximum transfer interval" in the ETL properties, as shown in the screenshots.  Here it can be seen that by increasing the Maximum transfer interval to 1 hour for an interval log of 5 minutes that ONLY 1 'overhead' record (sequence # 565) is added per 10 entries.   Using this or a similar setting will allow to reduce the storage requirement of the ETL.

Issue When using WPT 4.0 to upload controller databases, the system may display the following error message at the end of the upload process: Environment WorkPlace Tech version 4.0 Cause This error will occur whenever an Upload is performed under the following circumstances: 1. Any time the WPT project path is changed from the factory default such that it references a  drive path other than "C:", and the project is opened from that location. 2. Any time a project is opened through the use of the "Browse" function, and that project is located on a drive other than "C:"   Resolution See the attached Technical Alert TA04-05 for complete details.

Issue Created new Alarm Enrollment, attach to point and put point in alarm but no alarm is received and the points alarm value does not show the point is going in alarm. No problem when using an existing Alarm Enrollment created in the past when the total number of Alarm Enrollment objects was much less. Environment CyberStation CX9900 CX9640 CX9702 CX9680 ACX5720 ACX5740 Cause Controller's handle id limit on Alarm Enrollment objects has been exceeded. Resolution Click here to download this article as a PDF: Continuum Alarm Enrollment Handle ID Limits Continuum Alarm Enrollment Handle Ids Limit. (Note the information presented here applies only to non BACnet alarms) In Continuum there is a limit on the number of Alarm Enrollment objects that can be sent to the controller, the limit is 4000. Unlike the BACnet alarms, the Continuum alarm enrollments are meant to be re-usable, the system was designed for the Alarm Enrollment to be reused hence the limit, when the system is used as designed is very unlikely if not impossible to exceed the 4000 Alarm Enrollment objects limit. There have been cases where this limit has been exceeded due to site requirements that do not conform to the Continuum design, further more as of version 1.94 Continuum does not provided any feedback when the limit is exceeded, the alarm simply won’t work since the controller does not accept the alarm enrollment objects sent by the CyberStation. Guidelines to avoid exceeding the alarm enrollment handle id limit. Re-use, re-use, re-use. The Continuum system was designed for the Alarm Enrollments to be reused. If for some reason the number of alarm enrollment object is approaching the limit, do not delete Alarm Enrollment objects, if you have an alarm enrollment that is no longer needed rename it and re-purpose it instead of deleting it and creating a new one, the reason for this is that the handle ids once assigned are never re-assigned, so if you delete an alarm enrollment its handle id is lost forever. How to clean up if the limit is ever exceeded. If there are any Alarm Enrollment objects with handle ids out of range in the database they should be deleted to avoid confusion but before they are deleted all links to the enrollments have to be identified and the links removed. To find any links to alarm enrollment objects with id out of range run the following query against the ContinuumDB Select * from EventEnroll where AlarmRefLo > 562041735 If you get any results look at the uiName column, the uiName will consist of the point’s number and the AlarmEnrollment’s name separated by a period. Example: Num1.TempTooHigh Now From the Continuum explorer, find the point named ‘Num1’ that has a link to ‘TempTooHigh’ and remove the link. After all the links have been removed run the following query to find all the Alarm Enrollment objects with handle ids out of range. Select * from AlarmEnroll where ObjectIdLo > 562041735 Note the name in the uiName column, from the Continuum explorer delete the AlarmEnrollment objects.

Issue Where can I find documentation which explains what a Trend Log Comparison Report does? Environment StruxureWare Building Operation 1.3 Cause The Trend Log Comparison report provides a way for you to compare the output of the trend logs associated with a data point, such as the kilowatts for a power meter. The report provides similar reporting as the Trend Chart, however, you can export the report, schedule the report, and run the report using a Web browser and without access to WorkStation.   Resolution It is possible to read about Trend Log Comparison report in the manual Web report reference guide which you find on the Extranet under Products > StruxureWare Building Operation > Product information > StruxureWare > Building Operation 1.3 > Report server.  

Issue Replacement of obsolete actuator Environment Valve actuator replacement Cause Obsolete Valve actuator Resolution The current replacement for the AVUX 2-201 actuator is the AVUX 5-202 Click here to view the data sheet for the AVUX 2-202. Click here to view the data sheet for the AVUX 5-202. .

Issue What type of objects can be viewed using "Edit in Spreadsheet" mode Product Line EcoStruxure Building Operation Environment Edit in Spreadsheet mode Building Operation WorkStation Cause The objects that can be edited in Spreadsheet mode vary depending on the device or object you are viewing Resolution When you are viewing the AS IO Bus or an AS IO module, then clearly the only objects that cab be configured are Points. Below you can see the "IO" tab, but the "New" tab is greyed out. When viewing a "Folder" in an AS then possible tabs are "Alarm", "Value", "Folder" or "Trend". Below this can be seen (v1.3) LON device, Modbus Devices etc. will allow different access via the spreadsheet mode. This will vary for different versions If you need to find out what spreadsheet access is possible with your chosen device/folder, then it is best to navigate to the relevant Object, folder or device, enter Spreadsheet mode, then check what tabs are available when "New..." is select NOTES: If there is only a single possible spreadsheet object type, then even if there are zero of these object types created, then a blank spreadsheet is shown. If there is more than a single possible spreadsheet object type, and none of these object types are created, then no blank spreadsheet is shown. "New..." needs to be selected. When a row is selected, then an entry modified, all the text data in that row that is visible will be modified. Most EBO objects can be edited using Spreadsheet View with the exception of BACnet Objects. It follows that all objects that exist within MP/RP series controllers cannot be edited in Spreadsheet View as these are all BACnet Objects (This would include Modbus objects within the RP controllers that are actually BACnet objects) For further information refer to the Spreadsheet Overview EBO Webhelp topic  

Issue Attempting to map a 3rd party bacnet alarm and there is no way to navigate down to the object Click here to see the following snapshots illustrating the issue Environment SmartStruxure Windows XP SP3 Windows 7 Cause We currently do not support external alarming (that is a BACnet alarm in the AS or ES monitoring a property in some other device.) This is being considered for a future revision. Resolution If the 3rd party device does not support alarming they would have to create an SmartStruxure alarm to monitor it.    An alternative work around if the 3rd party device supports alarms (Ex. Veeder Root in this case) is to create a BACnet Value in the AS (or ES) and then binding it from the Veeder Root object to the local value, and configure alarming from there.

Issue Will the TE200AD24 sensor from Greystone Energy work with a MNB controller? See the datasheet. Product Line TAC IA Series Environment MNB controllers Cause Retrofitting an existing 3rd party control system with a MNB controller Resolution Any 10k thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the MNL/MNB controllers. An 11k shunt resistor wired in parallel with the sensor (1/8 watt, +/- 0.1% tolerance) is also required. See What 10k Thermistor sensors are compatible with the I/A Series MNL and MNB families of controllers? The inputs only take a 10k resistive load. So, for the setpoint slider, use a 10k linear pot. The datasheet says the AP model comes with a 20-30k pot and that you’ll have to call for other values. The 5 Vdc source required is not available on the MNB-300. It is available on the MNB-1000

Issue Reverting to an older than installed version of the firmware is required. Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series MNB 1000 Cause Prior to the 1.515 version of the firmware, it is not possible to revert to an older release of the firmware. Resolution Firmware after 1.515 has the ability to be reverted. 1.515 is the oldest version the controller can be installed with.  If this procedure is required, please contact your countries Product Support for more information.

Issue Continuum BACnet devices not seen in Continuum Explorer Environment CyberStation Cause "Continuum Explorer\View\Show Continuum BACnet Devices As" is set to "Infinet Controllers only" Resolution "Continuum Explorer\View\Show Continuum BACnet Devices As" is set to "Infinet Controllers only" Set to "Infinet Controller and BACnet Device The slightly confusing thing is that all Non Continuum (third party) devices still appear in the Bacnet view. This is correct, as designed. See below for both examples  

Issue Graphics appear fine when viewed from WorkStation, but when a web browser (WebStation) is used to view the AS, dark lines appear across portions of the graphic. Some objects with transparent backgrounds (fill set to "None") may appear with a grey background when viewed through a web browser. Product Line EcoStruxure Building Operation Environment AS TGML Graphics WebStation Cause WebStation is less forgiving of some improper configuration settings than WorkStation. Objects attributes must follow proper syntax for Fill, Stroke, or Visibility. Resolution Open the graphic page in the TGML viewer Change lines, borders, and fills to some other value (black, for example) Change the attribute back to the desired setting (Visibility = Hidden or Fill = None) Save the graphic The improperly formatted attributes should be overwritten with the correct syntax and the graphic appears as desired in both environments.

Issue Network scanning software causes a loss of Jace network communication. Product Line TAC IA Series Environment I/A Series Jace 8000 N4.9 and later Cause As network security awareness continues to expand, software-based scanners, such as industry-standard Qualys and Nessus, intended to detect and report on vulnerabilities within internal networks will likely continue to gain popularity.  Today, Tridium is seeing these scanners being deployed and run against Niagara-based platforms like the JACE-8000 and Edge 10.  In some cases, these scans are causing Niagara platforms to become unresponsive or reboot via an Engine Watchdog Timeout, all of which are not acceptable for the critical applications that Niagara facilitates. Resolution While Tridium has no control over how these scanners behave, or how and when they are executed within an organization, Niagara 4.9 introduces a number of changes intended to allow a Niagara-based hardware platform to appropriately respond to the scanning utilities, and also maintain operation.  Below is a brief explanation of how Niagara will function under the different known circumstances currently employed by these scanners, and how to interpret the results.   Recognition of non-Niagara Traffic on the platform In the event a scanner is interrogating a Niagara 4.9+ platform connection, the Niagara Daemon has been modified to recognize non-Niagara traffic over a period of time, shut down the connection if necessary, and wait for a pre-determined amount of time before re-enabling connectivity.  Under these conditions, a scanning utility may report that the Niagara instance has encountered denial of service, when in fact, Niagara has simply disabled the communication mechanism by which the scanner was attempting its interrogation. During this time, normal platform communication will also be affected; however, the Niagara platform and station will continue to run.   Prioritization of Internal vs. External Communication on the Niagara station In the event, a scanner is interrogating a Niagara 4.9+ station (external communication) and Niagara detects that this interrogation may cause an Engine Watchdog Timeout, the station’s web server will be stopped and restarted. Under these conditions, a scanning utility may report that the Niagara instance abruptly stopped communicating, and may have encountered denial of service.  During this time period, normal/expected client web connections to the station will also be affected; however, the Niagara platform and station will continue to run. As mentioned, these scanners are outside the control of Tridium, and likely always evolving to meet the needs of the various threats they are intended to protect against. As a best practice, Tridium recommends not scanning in production if possible, as any findings would be just as legitimate during scheduled downtime. Additionally, it may be prudent to work with the scanning tools to configure the appropriate priority of a scan, as the intensity of which you scan a production multicore, failover redundant web server host, is likely not the best choice for scanning a single-core JACE. Should you encounter an issue with a network scanning utility and Niagara 4.9 and above, please contact your support organization.

Issue Error 503 when testing for SOAP service availability using URL:   http://localhost:8030/SecurityExpertSOAPService/service.svc  Product Line Security Expert Environment Security Expert Server Cause Application pool in IIS not running.   Resolution In IIS Application Pools, start the pool associated with the Security Expert site.

Issue The customer is requesting a documentation on how the Alarm notification from Continuum works with MS Outlook to send out alarm email alerts to their facility engineers.   Environment MAPI MS Outlook CyberStation Email Cause The client is asking for information on how Cyberstation works with MS Outlook. Resolution Continuum uses the Enhanced MAPI messaging architecture to interface with MAPI compliant messaging applications/systems.  To understand this process in better, research Enhanced MAPI.

Issue What is SiteStat and where can I find documentation on this product? Is the SiteStat hardware supported by the Schneider Electric repair department? Environment SiteStat Cause SS-SCI controller has failed and a repair or replacement is needed. Resolution While the SiteStat product line is no longer sold or supported by Schneider Electric, a compatible replacement for the SS-SCI controller is the SS-NT-SSA16/CLK which is available on iPortal. https://ecobuilding.schneider-electric.com/search#keyword/SiteStat/tab/documents