Building Automation Knowledge Base

Issue A site backup is not available. Product Line Satchwell BAS2800+ Environment Backup No Index Uploading Cause The site is stand alone and the backup is not available. Resolution To recover the site data carry out the following; Use the Pocket Terminal application to review the outstation node configuration. Setup the BAS2800+ terminal to match the configuration observed from the node. Using the BAS2800+ System Diagnostics; Select the outstation number and then from the options menu, select "Transfer Files" Select to transfer PNTFLE.REC from the outstation, to C:\BAS\Data\osn??\PNTFLE.REC Shutdown BAS2800+ Locate and run the "No Index" utility. Run the utility to create the index Restart BAS2800+ and confirm that the points are available and can be displayed. Please note the "No Index" utility cannot name the index segments, this will need to be done by hand. Link to download the No Index utility

Issue It is recommended to save often when working with Menta. Product Line TAC Vista Environment Menta Cause We have experienced lockups of Menta when we conduct very long programming sessions. Resolution Save often. When you take a break, shut down Menta and then restart it when you return. This will help you to avoid losing time should Menta freeze up which is known to happen. It is good practice to let Vista DB folder structure be the file cabinet. When a change is required, export the application from Vista, make the changes, then re-import to Vista and download the controller. This will keep your field environment in synchronization with the operator interface.

Issue Transactions stopped working after an Upgrade. No Transactions or Controller Events in AMT after a Station restore. These are received though, when directly connected to the serial port of the controller. When using direct connect and communication is lost between the controller and I/Net PC, the access control system still functions correctly, but once the communication is restored back to normal none of the buffered messages are seen the I/Net AMT (database). Product Line TAC INET Environment I/NET Seven rev 2.13 and above Cause There is a feature called Reliable Tap that was introduced with I/NET Seven release 2.13 that sometimes needs to be reset on the controller in order for these events to be passed through from the controller to the Host PC.  It is also required to be set correctly when using a Direct Connect profile, in this instance the reliable Tap setting is used to ensure buffered messages are stored by the correct TAP (i.e. the onboard TAP which the Host PC is connected too).   Resolution Start I/Net and Connect to the controller that has the issue Select Edit, Controller, Configuration In the Distribution Parameters section (top right), change the selection for Reliable Tap from either “none” to the address of the tap, controller or NPR. Reset the controller by pressing the Red Reset Button or cycling the power. Check the Transactions Window and all the stored events should appear now. If the Reliable Tap feature is NOT required then change this back to 'None" and reset the controller again. Repeat this for any other controller having the same issue.

Issue Receive error 1001 when installing Cyberstation or Webclient Environment Continuum Cyberstation Webclient 1.9x Windows XP SP3 Windows Server 2003 Windows Server 2008 Windows Vista Cause Windows application viewer is full Resolution Clear the Windows application event view log. See the following link or the lettered steps below. Open Event Viewer (Start>Run>Eventvwr or Go to Administrative Tools>Open Event Viewer) In the console tree, click the log you want to clear. On the Action menu, click Clear all Events. Click Yes to save the log before clearing it. Click No to permanently discard the current event records and start recording new events. Install Continuum

Issue MNB-1000 BACnet MS/TP communications do not auto-baud (synchronize). Product Line TAC IA Series Environment I/A Series MNB-1000 Firmware 1.2 and above Cause I/A Series MNB controllers with firmware 1.2 and above support baud rate synchronization (auto-baud) for BACnet MS/TP communications. This auto-baud feature is available if the device is configured for BACnet MS/TP communications only.  If the MNB-1000 BACnet Ethernet (or BACnet IP) communications are enabled, even though this is not being used in normal operation, it will cause the auto-baud to be disabled. Resolution 1. Disable the BACnet Ethernet (or BACnet IP) communications on the MNB-1000. Use a compatible RS-232 to RS-485 converter or the Roam IA to access the MNB-1000 via BACnet MS/TP communications. 2. Set the baud rate of the MNB-1000 MS/TP port to a fixed speed that matches the configured baud rate of the RS-485 port of the Jace. - Connect to the MNB-1000 using the WorkPlace Commissioning Tool. - Go to the MNB-1000 device properties, MS/TP tab, and set the baud rate of the MNB-1000 MS/TP port. See the example below.

Issue Controller stops sending Valid and Invalid Access events but other types of events such as Exit Requests events are delivered fine. Environment CyberStation NetController I (CX9900) Cause Due to a defect in the firmware the controller can randomly get in a mode where Valid/Invalid Access Events are stuck in the controller and not delivered to CyberStation, the defect has been fixed in the second generation access controllers (CX9680 version 2.100035 and ACX57xx version 1.100037) but not in the older first generation controllers such as the CX99xx. Resolution A PE program running in the CyberStation can detect and alert of the condition and also perform an automatic reload to make the controller resume sending the valid/invalid access events. The following program is provided for illustration purposes ONLY and can be used as a guideline for creating a program in CyberStation to detect that a controller has stopped sending valid access events.

Issue CNT block in the Function Block Editor is replaced by the PI block. How to set up a pulse counter input in a function block program Environment StruxureWare Building Operation Workstation Function block editor Cause Differences between the regular Menta and the Builder Function Block editor programming Resolution The CNT block is replaced by the PI (Pulse input) block in the function block editor. In Workstation, connect the PI to a input where the sensor type is set to counter.

Issue Configuring a SetPoint in EcoStruxure Building Operation so that the set value of the SetPoint is retained after a Warm or a Cold Start rather than defaulting to zero. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The value retention configuration is not held in the initial properties page of the Analogue Value when used as a SetPoint. Resolution Navigate to the actual value within the properties page of the Analogue Value. On the right hand side of the GUI there is a Configure button. Pressing on this button then takes the user to a sub menu where the Retain level option can be enabled. Once enabled it is then possible to decide whether the SetPoint needs to retain its value under a Warm Start or a Cold Start condition.

Issue An obsolete part from the Network 8000 and DMS product lines has failed. Is there an option to repair and/or replace it with a refurbished unit? Product Line TAC IA Series Environment NETWORK 8000 Cause Replacement parts for obsolete parts on the Network 8000 and DMS product lines. Resolution A company has been retained that can repair and/or replace several parts from both product lines. Contact information: Name: ISA Phone: 1-800-430-6013 Web: www.isa-net.com On the home page of their website, select "Energy" at the top of the screen and then click on "Parts". On the new screen, click on "Barber-Colman (Invensys)". On the subsequent screen, click on "Invensys". A list of available parts for both Network 8000 and DMS will result. Availability varies so it is best to contact them by phone.  For additional information, see Product Announcement PA-00164 Network 8000 Availability – REPAIR UPDATE.

Issue When trying to view values in a Classic Network, "[No license for LonWorks communication]" message shows up in the Value tab and the alarm window. Product Line TAC Vista Environment Vista Classic Network Cause Though you are using Classic network, it's still using LON standards. You still need the license for TAC Vista Server. If the Server license is missing or invalid, you will get this kind of message. Resolution Check your license file and make sure you have the server license included. The server license should look something like listed below:  INCREMENT Vista.Server taclic 5.1 permanent 1 ISSUER=TAC \ If you do not have the line above, it means you do not have the proper license for TAC Vista server. Thus, you get the error message saying "No license for LonWorks communication."  The solution is to purchase the TAC Vista Server license, or use the demo license or an engineering dongle. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue The FlexAnalog object in the I/A Series R2 programLib jar does not pass the NaN (not a number) to the link when the value at the FlexAnalog input is changed from a valid value to NaN. Product Line TAC IA Series Environment I/A Series R2 Cause The object was based off the standard Analog Input object where the object holds the last valid value when NaN is applied to the input. Resolution There is a jar available that has an updated FlexAnalog object that will pass the NaN to the link when the value at the FlexAnalog input is changed from a valid value to NaN (not a number).  Contact Product Support Services to obtain this jar.

Issue 527/913 Hostname in I/NET Environment I/NET site using Xenta Cause getting generic serial number station name using 527/913 Hostname in I/NET Resolution The Xenta 527/913 will show up in the Station Summary report in I/NET, but if you have not configured it correctly it will show up with a generic serial number station name. To define this name you need to specify the hostname of the Xenta controller. This can be done with the setip command with HyperTerminal or via the Web Page in the Configuration\Network\TCP/IP page. Once you have changed this setting you will need to reboot your Xenta controller for the change to take effect.  

Issue When using TAC Vista 5 Demo License and Site License at the same time, Vista returns “Your application was not able to obtain a license because the FLEXnet license server manager could not determine where to find the licensing data it needs. Please choose one of the following: Specify the License Server System Specify the License File Product Line TAC Vista Environment Vista 5.X.X with Site License and Demo License Cause Using Vista 5 Demo License concurrently with Site Licenses, or having an expired Demo License in the License File folder with Site License may cause Vista ignore the Site License or not fully read the Site License. Resolution Remove Demo License from the License File folder. Restart the computer. If the issue still exists, follow Switching from the Demo license to the site License in Vista 5.1.7 or older.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Unable to enable or disable Enhanced Alarm Logging or Enhanced Alarm Delivery flags in Database Initialization. The Enhanced Alarm Logging flag goes back to what it was set to before making the change and the Enhanced Alarm Delivery flag is greyed out and uneditable. Product Line Andover Continuum Environment Continuum Database Initialization Cause The owner of the ContinuumDB is set to something other than the default andover97. In this specific case it was set to SA. The SA user was unable to write these changes to the database hence why the settings kept reverting back. To compound the issue it was found that an andover97 user had been created under the Security folder in the ContinuumDB, this then blocked attempts to change the owner to the correct andover97 user. Resolution Backup the ContinuumDB before making any changes. See Move / Backup / Restore a database on a Single User SQL2005 Express system. Attempt to change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO If this produces an error "The proposed new database owner is already a user or aliased in the database" then see Unable to change the ContinuumDB database owner using the stored procedure sp_changedbowner for instructions on how to drop the incorrect user so we can use the correct one. After successfully dropping the user from the ContinuumDB, re-run the query in step 2 above to change the database owner to andover97.   After successfully setting andover97 to the database owner you should now be able to toggle the Enhanced Alarm Logging and Enhanced Alarm Delivery options in Database Initialization. If you want these enabled; toggle them both off, update the database, toggle them both on, update the database again. This will ensure they have been enabled properly. Note: The definitive check to see if the Enhanced Alarm logging and Enhanced alarm delivery are both enabled is by checking the dbo.ACCDBVersion table in the SQL database using SQL Server Management Studio (or Express). New Alarm Logging and New Alarm Delivery should both be set to 1.

Issue Following an attempt to update firmware, some MNB MS/TP controllers appear to be in a locked-up condition (ie: the status LED is red and blinking). Product Line TAC IA Series Environment I/A Series MNB controllers Cause The device was interrupted before completing the update, which cause the controller to be in bootloader mode. Resolution To perform a successful firmware update it is imperative that once the update has been initiated it must not be interrupted until complete. A successful firmware upgrade must be completed to get the controller out of bootloader mode. However, in most cases when this issue occurs the unit is no longer displayed in the WorkPlace Commissioning Tool device list.  Therefore it cannot be selected for an upgrade. To get the unit to show up in the list, it must be added as an MS/TP slave. This is done under the WorkPlace Commissioning Tool menu selection: File – add MS/TP Slave. The network number and the controller's MS/TP physical address must be known. Once defined as a slave it will appear in the list and can be selected for a firmware upgrade. Note: If a controller shows up in MS/TP slave mode and indicates it contains the latest firmware it will be necessary to downgrade it to the previous firmware version to recover the unit and then upgrade to the latest firmware.  To downgrade the firmware in an MSTP device open its Device Properties, go to the Firmware tab and click on "Update firmware".  On the Update Firmware window check the box next to "Check here to preview or modify the updates to be applied and click "next".  On the Update Details window click on the change button and a window with available firmware versions for that controller will be displayed.  Select the "bin" file for the previous firmware revision and click on the Open button.  Now click on the Start Update button to perform the firmware downgrade.  If successful the controller will show up in the WPCT device list and can be upgraded to the latest firmware. If suspect communications are what caused the update failure, it must be remedied prior to attempting another update. Once a successful firmware update has been completed the unit will boot normally.  The status LED will be green and it will appear in the Device list.

Issue What I/A Series BACnet hardware (MNB) is officially UL 864 listed? Environment MNB UL 864 Cause Many consulting engineers would like documented proof that the hardware within a smoke control system is UL 864 tested and approved. Resolution The Schneider Electric MicroNet BACnet UL 864 case file, outlining exactly what I/A Series BACnet hardware is approved for UL 864 systems can be obtained at: www.UL.com Navigate to the bottom of the home page under Useful links and click on Online Certifications Directory Find the UL File Number field and type s5381 The Schneider Electric MNB file will show up and click the link UUKL.S5381 under the link to file column. This will show you all of the I/A Series hardware that is UL 864 certified, and can be installed in an official smoke control system. Also refer to the I/A Series MicroNet BACnet Smoke Control Systems Manual (F-27419) for further information related UL 864 Smoke Control applications.

Issue In an R2 (Niagara) station with BACnet, getting errors in Standard Output Window, "Transport lockup detected!" and multiple "TException E_QUEUE_FULL {BClient}". Environment I/A Series R2 (Niagara) UNC station with BACnet service. Cause Queue sizes in BACnet Service are too small. See the BACnet Integration Reference, Chapter 6, "Configuring BACnetService Properties", "Engineering", Figure 6.4, and section titled "Message Queue Properties" for further details. Resolution Increase all three of the queue sizes(transportQueue, serverQueueSize, clientQueueSize) , from the default values of 16, up to 90.   Monitor the Standard Output Window for errors, and increase the queue sizes in increments of 50, up to 500. It may be necessary to reboot the station in order for the changes to take effect, because the changes are being made to a service.

Issue Require manuals, datasheets, install guides or sales information for Field Devices. Product Line Field Devices Environment European Field Devices, U.S. Field Devices IPortal, USiportal, Extranet Datasheets, Specification, manual, sources of information Cause Where to obtain field device data? Resolution Field Device information for your part of the world can be accessed from the Exchange Extranet: Field Devices. When you logon to the site it will allow access to products available for your location. U.S. Products can also be easily found using the search in iPortal. Catalog information can be obtained via the following Valve, Actuator, Sensor, Field Device, Peripheral, HVAC Control Devices Datasheets and Catalogues, Selection Tool. Note: The Extranet links above are for Schneider Electric personnel or approved partners, if you do not have a logon account please contact your local Schneider Electric office for information. For pricing information please contact you local Order Entry or sales contact.

Issue TAC Xenta alarms are configured with a priority of 1 in Menta, but these same alarms appear with a priority of 100 in EcoStruxure Building Operation. Product Line EcoStruxure Building Operation Environment Building Operation Workstation TAC Xenta 301, TAC Xenta 302, TAC Xenta 401, TAC Xenta 281, TAC Xenta 282 Cause This is per design, Building Operation supports priorities from 0-1000, aligning alarm priorities from TAC Xenta within the range of 100-900 is a deliberate choice. By default, all alarm priorities from TAC Xenta are multiplied by 100 to fit this scheme. Resolution To revert the priority back to the original, open the properties for the alarm and manually adjust the priority.

Issue Rehosting is defined as the process of moving a license from one machine to another. Is there a limit to the number of rehosts allowed per year? Product Line EcoStruxure Building Operation,TAC Vista Environment Building Operation Licensing Cause Re-hosting means that the license bindings to the physical hardware or its substitutes on a Virtual Machine are moved i.e. the host ID is changed. This can be required if the license is moved to a new computer or Virtual Machine.  A maximum of 4 license re-hosts are allowed in 12 months. Resolution If the re-hosting limit is exceeded and further re-hosting is justified and necessary, the policy can be overridden by Product Support. When contacting support please provide the entitlement details so that the license policy can be overridden.