Building Automation Knowledge Base

Issue Replacing a DC3000 controller. Environment Drayton DC3000 Cause The DC3000 is now obsolete. Resolution The DC3000 controller is obsolete, and there is no direct replacement available. Our current range of discrete controllers cannot provide the same functionality as the DC3000, assuming that functionality has been used. To provide the same controller functionality a programmable controller such as the Micronet or Xenta ranges will be required To upload an overview of the Micronet range, please click HERE. The Xenta controller range is listed as part of the TAC Vista Product Catalogue which can be downloaded from Schneider Electric but a table of the controllers and their I/O are shown below.

Issue Where can you obtain the Database Schema for the EBO WebReports / Report Server Database Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause From EBO version 3.2.x WebReports/RS is no longer being developed as we move to External Log Storage with Postgres and Timescale DB.    To allow our customers to continue to work with existing WebReports/RS databases if they so wish, it may be helpful to provide the DB Schema. Resolution An inbuilt Report already exists within WebReports call 'Database Schema' which allows you to select which Tables you would like to see in the WebReports / RS Database Running this will produce a .pdf Report detailing the RS Database Schema tables, to aid with 3rd Party integrations and other DB manipulation. A full database schema report is attached for reference (Version 3.2.3) 

Issue When browsing the IP network using the WorkPlace Commissioning Tool, third party devices are displayed in addition to the I/A Series BACnet devices but no information is known about those devices. Product Line TAC I/A Series Environment WorkPlaceTech Commissioning Tool 3rd party BACnet IP & MS/TP devices Cause 3rd party BACnet devices are sometimes connected to the IP network without the knowledge of the engineer  programming the I/A Series system. Resolution When performing a global browse of the IP network, unknown devices are sometimes displayed in the WorkPlaceTech Commissioning Tool device list display.  Since all data columns are not necessarily displayed, some of the device information may not be able to be directly determined. Right-click in the column headers and a menu of available data columns will be displayed. The following columns may be displayed at a minimum to allow identification of the devices on the network as well as the BACnet routing path to those devices:     Instance     Vendor     Model     Router     Network     Address   If the device is a BACnet IP device, the "Address" will be displayed as an IP Address and Port.  For example the address of a BACnet IP device communicating via port 47821 at IP 10.159.34.238 Address   =  10.159.34.238 : 47821   If the device is a BACnet MS/TP device under a BACnet IP device, the address is the MAC address of the device on the MSTP bus and the Router is the address of the BACnet IP router to that device in Hexadecimal numbers.  For example, for MSTP device #4 under BACnet IP Router address, 10.159.34.238 : 47821 10 = 0A, 159 = 9F, 34 = 22, 236 = EC and 47821 = BA CD  Address   =   4 Router      =   0A-9F-22-EC-BA-CD   If the device provides vendor and model information, that information will be displayed in the appropriate columns.

Issue What image formats are supported in a TGML graphic? Product Line EcoStruxure Building Operation Environment EcoStruxure ES, AS Vista Graphic Editor Cause Clarification of supported graphic formats required. Resolution When inserting a picture in a TGML graphic you can select the image file from the following file types: Bitmap, GIF, ICO, JPEG, Metafiles, PNG, TIFF  

Issue When swiping a card in front of the reader, there should be a beep indicating that the reader has read the card. There is no beep. Product Line EcoStruxure Security Expert, Andover Continuum, TAC I/NET Environment Access Control HID Reader Cause There are 3 possible reasons for this issue: The beeper is disabled through a default configuration when the card is shipped The beeper has failed The Reader and Card represent incompatible technologies such as an 125Khz Prox Reader trying to read a 13.56MHz IClass Card Resolution Ensure Reader and Card both support a common technology (125Khz/13.56Mhz etc..) Short the Beeper wire (yellow) and the GND wire (Black) with the reader powered On If there is a beep, that indicates that the beeper can work but is disabled. Ask the manufacturer to send a configuration card to enable the beeper (use 3 seconds after reader power is on) If shorting the beeper produces no sound, the beeper has failed. Send the reader to repair and replace it with a new one.

Issue In a Niagara G3 station with a BACnet MSTP integration, the following error appears in the application director output: Transaction Timed out! invokeId 223 TransactionException in poll() for BacnetDevice {Kens_RM106}:pl=PollList [Kens_RM106 device:7219 3000:13] 196608025 {160} 10 PLEs) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) .... Hundreds & hundreds more Environment Niagara G3 Cause MSTP trunk / traffic issues Resolution See the discussion about an identical issue at Niagara-Central.com.  Here is a link:  https://community.niagara-central.com/ord?portal:/discussion/DiscussionThread/11258

Issue A BACnet devices can contain 1000's of objects, performing an upload on these devices can take upwards of 30 minutes to complete when only a few objects are required for integration. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause Uploading all objects in a controller can take a lot of time and is often not required. Resolution From version 2.0 Open the device discovery view / BACnet - then Discover All. Once the Device is hosted, click on the device (in the Device Discovery window) and open the right-hand Object pane. Drag/drop the required Object into the hosted BACnet device Application folder. Alternatively, the Hardware folder can be used, this was the best method for some earlier versions Perform the BACnet discovery, then view the Hardware folder at /ServerName/System/Hardware/BACnet devices. Navigate to the required Device/Object, then Drag and drop the Device and Object as above.

Issue WorkPlace Tech will not recognize the Echelon U10 USB Lon Network Interface adapter. The “Loading Device Driver” is displayed but nothing happens after that. Environment WorkPlace Tech 5.8.x Cause LON1 port may have been previously assigned to another LON interface. Resolution 1. Make sure the Echelon Open LVD 4.0 is installed on PC. 2. Close WorkPlace Tech if open 3. Disconnect the Echelon Lon USB adapter from the PC. 4. Open Control Panel and open LonWorks Interfaces 5. Select View from the Menu and check “Show Detached Interfaces” 6. Highlight LON1 in the tree and click the “Remove” from the menu        - Click Yes in the “Confirm Removal” window to remove the detach device 7. While in same widow, reconnect the Echelon USB Lon Adapter to the PC        - The messages: “Installing device driver” will display in the system tray followed by “Echelon USB Network Interface Installed.        - The LON1 interface should now be displayed You can test the communication if you like Now open WorkPlace Tech and you should be able to discover the LON devices.  

Issue Does the Niagara R2 Modbus driver support a 6-digit address format? Product Line TAC IA Series Environment Niagara R2 Modbus driver Cause Modbus 6 digit addressing is not supported when using modbus format in the driver. Resolution The six-digit address format and the five-digit format are just two different notations for the same thing - there is no difference in the protocol. For example, the first one thousand holding registers are normally represented as: (modbus) 40001 to 49999 -or- (decimal) 0 to 9998 -or- (hex) 0 to 270E When using modbus format in the driver, the left most digit, '4' in this example, is part of a convention that indicates the 'type' of point and, when using that convention, the point type does not have to be specified.  For example, for modbus point 40001 the '4' indicates that it is a holding register. But there are actually 64000 holding registers available and, using the common 5-digit modbus notation, it is not possible to specify more than 9999 of them. The six digit convention just moves this 'type' digit one space to the left. In this six-digit notation, the first one thousand holding registers would be 400001 to 409999. This 6-digit convention for 'modbus' formatted addressing is not supported but it is still possible to use decimal or hex notation to specify these addresses with Niagara R2. When 'modbus' formatted addresses are used, the driver subtracts 1 from the entered address, since modbus uses base 1 formatting and decimal uses base 0.  When using decimal or hex, the leading digit is dropped and subtract one from the register value and optionally convert to hex and use that as the point address. For example, to read data from register address = 422202 Drop the leading character = 22202 Subtract 1 = Decimal address 22201 or hex address 56B9

Issue Is it possible to use both Modbus/IP and BACnet/IP on the same AS-P Ethernet Port 2? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Cause There is a need to have both Modbus TCP as well as BACnet/IP devices on the same AS-P secondary Ethernet port. Resolution This is not a common configuration so it has not been tested extensively. With regards to the architectural guidelines, consider the Modbus/IP as BACnet/IP devices. For example, where the maximum number of SpaceLogic BACnet/IP devices per private IP field-bus is 200, adjust this limit to 190 if you have 10 Modbus/IP devices on the secondary Ethernet port.

Issue Need to use Mobile Apps to access EBO. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation Commission mobile application Building Operation Engage mobile application Cause What are the mobile apps available to use with EcoStruxure Building Operation sites? Resolution WebStation: WebStation is a web-based user interface for day-to-day operation in an EcoStruxure BMS. WebStation, V2.0 or higer, improves user experience by automatically adapting the user interface to the resolution of the device being used: desktop, laptop, tablet or smartphone, using Windows, Linux, Android or iOS, out-of-the-box using standard web browsers, without the need to install additional applications.  WebStation replaces the obselete Technician Tool app. Refer to: WebStation Overview Building Commision: EcoStruxure Building Commission mobile application (requires EBO V2 or higher, formerly eCommission) is designed to help airflow balancers, electricians, and technicians carefully and quickly pre-commission and commission SpaceLogic BACnet/IP devices and RP controller expansion modules. The Commission mobile application does not require a license for activation and is available at no cost to the user. It is designed for use with Android, iOS (Apple), and Microsoft Windows 10 and Windows 11 devices, and is available for download from Google Play, Apple App Store, and Microsoft Store. Refer to: Commission Mobile Application Engage: The Engage mobile application (requires EBO V3.1.2 or higer) enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. The Engage mobile application connects easily via BLE (Bluetooth Low Energy) to the RP-C controller. The application is compatible with RP-C (HVAC) and RP controller expansion modules (lights and blinds). The Engage mobile application is free and available for download from Google Play and Apple App Store.  

Issue Need information on securing a building automation system. Environment Best practices Cause End user has requested assistance for their IT department to secure the building automation system. Resolution Click here to get a copy of Best_Practices_for_Securing_an+IBMS_WP.pdf,  a white paper written by Schneider' Electric's Buildings BU IT Security Group. This also located on the Download Center here

Issue How to recover the AD v3 password if lost / forgotten? How is a factory reset done on an Advanced Display version 3 (AD v3)? Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V3 Cause If losing the kiosk password for AD v3, it is not possible to get a recovery password. If the kiosk password is lost for the AD v3 a factory reset must be done on the tablet to be able to get out from the kiosk mode. Resolution The following video will show the steps to perform a factory reset on an AD v3:

Issue Steps for replacing a BACnet B3 controller and things to consider. Product Line Andover Continuum Environment Continuum b3xxx Controller Cause Steps for replacing a BACnet B3 controller and things to consider. Resolution Steps for replacing a B3 controller and things to consider. Use these steps when replacing a B3 controller from brand new stock, it is relatively straight forward. Physically disconnect power and MS/TP data cables from existing B3 Controller. Remove existing B3 Controller. Install replacement B3 Controller. Pull the battery tab on replacement B3. Connect MS/TP data cable to the replacement B3 controller. Connect power to the replacement B3 controller. Edit the B3 controller object in Continuum on the infinity side. On the Runtime tab enter the Serial Number of the new replacement B3 controller and click Apply. Click refresh until B3 controller returns Online. Reload the B3 Controller. Verify existing points and programs are running correctly. Perform a “Backup to Flash” operation on the B3 controller. Perform “Send to Database” operation on B3 controller from BACnet view. One scenario, for example, is the Replacement B3 controller came from a different job that has previously been programmed and has a valid flash backed up onto it. If installed on the new network, when powered up will start trying to communicate with controllers it has routing tables for. Could potentially cause issues on the new network. It is suggested that if you are replacing with a previously used controller from an old site with a valid flash backed up is to flush the controller out before applying to the new network. From a test machine with a test DB bring the controller online, this will require a BCX to do as well. Once the B3 is learned in and online, perform a reload to the controller and then a backup to flash. The only thing that will be reloaded will be the system variables. Another thing to think about is let's say you've already replaced the B3 and sent it off to repair. You've got it back and now want to put it back to its original location. That one is very simple and following the replacement steps above will suffice. Just remember that step 8 above you would make sure the Bacnet Device ID and the serial number match for the original unit integration. But if you wanted to add a new B3 controller to the same site and use the repaired B3 as a newly installed controller, just remember that the previously replaced B3 will have the Bacnet Device ID of the repaired B3 and you'll have to make sure that when manually creating a new B3 with the repaired B3 you'll have to make a new Bacnet Device ID that is unique. Rules to remember: Flush out used B3 controllers before adding to an existing MS/TP network or replacing a defective B3 Bacnet Device ID's must be unique for each given BACnet network  

Issue Error "Ensure that Vista Server is started" when the server is already running. Product Line TAC Vista Environment Vista Server Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). test Resolution These are some utilities created by Benjamin Roswall at Schneider Electric Denmark. They are not official releases nor are they supported by Schneider Electric. While they have been tested and used successfully, they should be used at your own risk.   DCOM Config 1.0.3.0.exe: Configure DCOM for TAC Vista Network If you want to run TAC Vista Web Applications on Windows Server 2003 Standard Edition, both Internet Information Services (IIS) and ASP.NET 2.0 must be installed. ASP.NET 2.0 must be installed and activated before you start installing TAC Webstation. Refer to Chapter 4 of the TAC Software Installation Manual for more information. If you've made it this far, then it's time to refer to Chapter 3.5 of the TAC Software Installation Manual for the network security and permissions settings required to run Webstation (DCOM). Or just run this utility. Click the picture to download the utility.   Webstation installations will use Option 3. If Webstation doesn't come right up and start working after this, also download the next utility.   WEB.exe: Corrects common problems with Vista Webstation This utility will install and register the versions of ASP.NET required for running Webstation on the server PC. There are other articles on the command prompt commands to accomplish this, but this utility will take care of it for you. Click the picture to download the utility.   After this utility finishes running, restart the PC as instructed.

Issue Often data is required to be exported out from the Continuum system for record keeping or for further analysis, what keywords can be used to help with this? Environment Cyberstation Plain English programs - all versions. Microsoft Excel Product Line Andover Continuum Cause Specific help is available in the product for specific keywords but how can these be put together to export data to .CSV format. Resolution As we do not advocate 3rd party system trying to directly extract data from the Continuum database, you should create a Plain English program in a Workstation that can export logged data directly from the controllers out to a .CSV or .TXT file.   Keywords to use for this purpose are: OpenFile WriteFile CloseFile   Details of the above Keywords are available in the Cyberstation internal help pages.   The attached example dump file could be run on a daily basis to extract temperature logs from a controller and save them to files with a date stamped naming convention.   Click to download the example WriteFile dump file. 

Issue Registering/Unregistering TAC Vista Server as a Windows service will allow the server to start automatically and run in the background of the PC (it won't show up on the Windows taskbar). This is not the same as having it run on Startup (for information on that, please see Configuring Vista Server to run on Startup). Product Line TAC Vista Environment Vista Server Microsoft Windows -- All versions Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Reference Chapter 16.3 of the TAC Vista Technical Manual "Running TAC Vista Server as a Service in Microsoft Windows XP" for more information. When you log out of Microsoft Windows or restart the computer, all running processes, for example, Vista Server, are shut down. These processes are not resumed at log on or at restart. You have to start Vista Server manually again. To get Vista Server to remain running at log off and automatically start up when the computer restarts, you can run Vista Server as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Before you start Vista Server as a service, you must first install and configure your Vista Servers and your network and have everything running satisfactorily. It is not advisable to start Vista Server as a service until you have completed all the settings (including security and authority) and the TAC Vista system is running well. Resolution Register Vista Server to run as a Windows service Go to Start > Run Register the service by typing: Tacos.exe /service When you register TAC Vista Server as a Windows service, it will default to run under the "Local system" account.  This is not supported by TAC Vista Server. Right-click on My Computer and select Manage. Browse to Computer Management (local) > Services and Applications > Services Find TACOS, right-click and select Properties On the Log On tab, specify "This account:" with admin authority.  It is ideal to use a domain account with local administration authority if your system is a member of a domain. At this point, if you would like to start the service, highlight TACOS in the Services window and select Start the service. If you choose to run Vista Server as a service in a multi-computer network, we recommended that you run every Vista Server as a service. Change from running as a service to running as interactive Go to Start > Run Unregister the service by typing: Tacos.exe /unregserver You must then register the server back to interactive by typing: Tacos.exe /regserver Helpful Utility This utility will read in the current run mode of the Vista Server and allow you to switch between running as a service and an application. It also lets you set the user to run the service under. Click the image to the right to go to a Community post containing the utility .exe file. Accessing Vista Server Menus and Dialog Boxes Once the service has started, it is not possible to use the Vista Server menus and dialog boxes. To be able to use these, you have to unregister the service and start Vista Server in the normal way. LonTalk Adapter from Loytec When TAC Vista is running as a service and you are using a LonTalk adapter from Loytec, you must ensure that the program LConfig is also running as a service. You do this when you configure the network interface card. TAC Vista Tools and Microsoft Windows Vista Some of the tools installed in the installation folder of TAC Vista cannot run if TAC Vista is running as a service in Windows Vista. These are TAMIAN, CIPCL, SYSDOC, TADRAW, and DBGEN. Related Articles: Unable to save periodic report to network drive when Vista is running as a service Regional settings might differ when TAC Vista server runs as a service Dependencies for Vista Server running as a service Upgrading Vista while running Server as a service

Issue Two related issues are covered in this article While attempting to activate a customer or demo license, the activation process stops at around 80%. When clicking the "Diagnostics" tab in the License Administrator it crashes with a "System.DllNotFoundException" error. System.DllNotFoundException: Unable to load DLL (Tac.Nsp.Archive.Licensing.Client.dll) Product Line EcoStruxure Building Operation Environment First detected in Windows 10 First detected with Microsoft Visual C++ Redistributable 2012 (VC++ 2012) License Administrator Cause There can be two reasons why this happens If the activation process stops at around 80%, but the License Administrator does not crash when the "Diagnostics" tab is selected, the license system needs to be completely reset. If the activation process stops at around 80%, and the License Administrator crashes when the "Diagnostics" tab is selected, Microsoft Visual C++ components need to be repaired. Refer to solutions below depending on the issue detected. Resolution Solution 1: Resetting the license system The process to reset the license server system is covered in Resetting the License Server. In some cases, a deeper reset can be required. For that, a tool called "SBO License Server Reset" can be downloaded from the Community. Solution 2: Repairing Microsoft Visual C++ components Method 1 In Control Panel, click Uninstall a program in the Programs group. In the programs list, locate Microsoft Visual C++ 2012 Redistributable (X64) - 11.0.61030 or Microsoft Visual C++ 2012 Redistributable (X86) - 11.0.61030, depending on your system architecture. Right-click the entry name, and then click Change. In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this. Method 2 Run the Modify Setup repair functionality for Microsoft Visual C++ Redistributable by starting the installer. VC++ installers In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this.

Issue Can the red crosses (that indicate that a signal is offline) in Vista or SmartStruxure Workstation/Webstation be disabled? Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure TGML Graphics (Workstation, Webstation) Vista TGML Graphics (Workstation 5.X, Webstation 5.X) Cause When a signal which is bound to an object in a TGML graphic is offline, this is indicated by a red cross when viewing the graphic in Vista or SmartStruxure Workstation or Webstation. Resolution This can easily be disabled in TGML by adding a script to the OnSignalChange event: function signal(evt){   evt.preventDefault(); }  Note, this script will only disable the red X when a point is offline. This does not address any issue that might cause points to be offline. A short video is available on this process, to review, please see SmartStruxure - Graphics - Removing Red Crosses.mp4.

Issue Satchwell ALi series Linear Actuator requires replacement. Environment Satchwell ALi series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Actuator type :- ALi series. Cause Obsolescence of Satchwell ALi series Linear Actuator. Resolution Replace Satchwell ALi series Linear Actuator with S-E M800 Linear Actuator and Linkage Kit :- ALi = M800 + L2SV (880-0124-000) Linkage Kit. N.B. Should the Satchwell ALi series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :- S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an S-E Forta M800 Actuator to replace an existing Satchwell ALi series Actuator. The S-E Forta M800 Actuator may be used to replace an existing Satchwell ALi series Actuator but it should be noted that where an existing Satchwell ALi series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) will also be required. (e.g. S-E Transformer Type TR60) Where an existing Satchwell ALi series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALi series Actuator (16VA) only. In such circumstances the existing independent Transformer will also require replacement by another independent Transformer, rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) (e.g. S-E Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here Details of the Schneider Electric L2SV Linkage Kit may be viewed here