Building Automation Knowledge Base

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 How to truncate event tables in Continuum databases. Product Line Andover Continuum Environment Continuum 1.xx SQL 7 SQL 2000 SQL 2005 Cause Stand Alone Continuum Databases use Microsoft MSDE and SQL Express databases which have size limitations. Once these databases reach full capacity they will need to have data truncated from tables to try and reduce the size of the database. Databases should never exceed their size limitations, but if they do, reducing the size of some of the tables will in most cases allow the database to be functional again. Microsoft SQL MSDE database size limit is 2 gig Microsoft SQL Express database size limit is 4 gig Resolution Once logged into the SQL MSDE or SQL Express database, the queries below will reduce the size of the database. As with any database, make sure you backup the database before running any queries. The Usernames and Passwords used below are defaults, your UN/PW may differ. To log into SQL MSDE use the following commandline. osql -Usa -P To log into SQL 2005 Express us the following commandline with your servername sqlcmd -Sput_server_name_here\sqlexpress -Usa -Padminadmin Once logged in you'll be prompted with a 1> at which time you'll change the context of the database you'll be truncating information on. For example if your database name is ContinuumDB you would use the following. 1>Use ContinuumDB 2> Go 1>Now put in one of the queries below 2> type in Go to execute /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 ** To gain back the space after deleting rows SQL Express Right click on Continuumdb>Tasks>Shrink>Database MSDE(osql) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter)   To truncate from the Full SQL server or SQL Express non command line interface, see Removing unwanted entries from an Alarm log, Access Event log, Error log, and Activity log automatically.

Issue Issues being experienced can vary, here are some examples: The digital clock gains a minute every few seconds. The code (0112) when entered to accept alarms, is not accepted. Environment DC1100 controller DC1400 controller Cause The unit has not been correctly cold-started after first being powered on. Resolution The DC1100 / DC1400 controllers must be correctly cold-started after first powering up, this ensures that the default configuration is correctly installed. Cold-start the controller using the following process: Turn off the power to the controller. Press and hold in the ENTER and EXIT keys. Power up the controller whilst continuing to press the ENTER and EXIT keys. Release the ENTER and EXIT keys. The controller will now go through a self test programme and load its defaults. To review the DC1100 / DC1400 controller overview, select here To review the DC1100 controller general data sheet, select here To review the DC1100 controller installation, wiring and Commissioning information select here To review the DC1400 controller general data sheet, select here To review the DC1400 controller installation, wiring and Commissioning information select here

Issue How to filter in a listview AlarmEvent based on the EventNotification Environment Continuum Cause Continuum pre 1.91 did not allow filter in a listview AlarmEvent, based on the EventNotification Resolution See Continuum CyberStation Release Notes Version 1.91(Downloadable here) Fixed Problems 4.007 Cannot filter an AlarmEvent table based on the EventNotification using the query wizard (21101) Find another way to filter or upgrade your version of Continuum.

Issue Functional block names are shorter in XIF file, LonMaker or NL220 than the names defined in SmartStruxure Environment Automation Server Externally Managed LonWorks Network Cause LonMark defines how a xif file must be structured and written. There are especially three rules that comes into play when creating the functional blocks from an Automation Server in the externally managed LonWorks network. In the LONMARK® Device Interface File Reference Guide it states that: "If the static interface contains functional blocks, the device selfdocumentation string must be formatted as described in The LONMARK Interoperability Guidelines." In the LONMARK® Application-Layer Interoperability Guidelines it states that: "Manufacturers are free to assign any functional profile number to new non-inheriting profiles, as long as they are in the range of 20000 to 25000, inclusive; and as long as the number is unique for the program ID template and scope of the resource file set containing the functional profile." In the same document it also states that: "The device self-documentation string is a string of up to 1024 bytes (subject to device memory limits)" and also "If the name is text, it must consist of ASCII printable characters, be of no more than 16 characters in length". Due to the above mentioned rules, any functional block defined in the Automation Server will always start with a functional profile number from 20001 and up and the name of the functional block (excluding the 5 digit profile number) will not be longer than 16 characters. If the name defined in SmartStruxure is longer than 16 characters, the characters from 17 and up will be deleted. If the complete length of the self documentation string is longer than 1024 bytes, the maximum character length will be lowered by one until the complete string fits within 1024 bytes. Resolution The only way to get around this is to either make fewer functional blocks on the Local Node in SmartStruxure, or to make their names shorter.

Issue Automation Servers go OFFLINE Alarms received about duplicate device name and/or duplicate network identifier. Product Line EcoStruxure Building Operation Environment Enterprise Server, ES Automation Server, AS, AS-P, AS-B BACnet Cause In the BACnet interface duplicate information has been entered for the BACnet IP network for 2 or more Automation Servers. Resolution Make sure the BACnet IP network and broadcast address in the BACnet interface of the ES and all the Automation Servers  are set to a unique value and they match the IP address of the Server (AS, ES) You may have to physically disconnect the units from the network and then connect one at a time in order for Workstation to be able to communicate with the AS and change the configuration of the BACnet IP network.  

Issue Controllers may leave their network and join another if a nearby network has an identical "Extended network ID", "Channel" or "PAN ID" Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Ex. Viconics branding VT8000 Series Cause Conflict in zigbee networks (Same "Channel", same "PAN ID" or Same "Extended Network ID") Resolution Before deployment, and in order to ensure having a reliable ZigBee network, one has to be aware of the best practices and the limitations of RF signals. Here are some key points to be considered Network Conflicts: Always change your Extended Network ID from the factory default. The best thing is to use a naming convention that makes sense. One suggestion would be to use "SSLLITxx," where "xx" is replaced by the floor the network is on. For example, floor 5 would be "SSLLIT05." If you have multiple networks on the same floor, adding a letter code helps denote them. For example, if there were 2 networks on floor 5, "SSLLI05A" and "SSLLI05B" can be used. Note: In Firmware 2.20.1, the ZigBee Extended Network ID parameter is set by default to a unique string based on the serial number of the MPM. This will eliminate the possibility of having duplicate Extended ID's in a new deployment. For existing installations, the Extended Network ID will remain unchanged if upgrading from a previous version.   Alternating Channels: Alternating channels between network will minimize interference ensure stability. For example, for a 5-story building, alternate between channels 20, 25, 20, 25, 20. Tx Power Upgrade: The default value for "Tx Power" is 5dBm which was designed in order to meet various regulations in certain countries (Europe). However, the "Tx Power" can be increased to 18dBm in other regions of the world (North America) to boost the transmission power of the MPM.   Interference: There are different types of interference when a wireless signal travels through a given space: Physical objects: The number of walls the wireless signal can pass through is determined by the density of the materials used in a building's construction. Concrete and steel walls are difficult for a signal to pass through. These structures will weaken or at times completely prevent wireless signals. Also, the presence of individuals or water will diminish the signal due to the water's ability to absorb the signal. 2.4Ghz Frequency Interference: Cordless Phone - operates on the same frequency as the ZigBee and can cause a significant decrease in performance. Microwave Oven - operates by emitting a very high power signal in the 2.4GHz band. Often emits a very "dirty" signal across the entire 2.4GHz band. Wireless Routers - Wireless Wi-Fi Networks that share the same channel will have a negative effect on ZigBee network performance. Distance: To ensure reliable communications, a suitable distance between two devices has to be calculated before installation. The distance depends on three factors; transmitter power, sensitivity of the receiver and the propagation path loss. The latter is dependent on the number of walls/physical objects obstructing the signal. Locations: The physical location where a router or coordinator is placed also has an impact on the signal. Place the devices in higher ground to reduce the impact of physical objects. Route Redundancy: It is critical that the signal has multiple routes to hop from one device to the other, from one edge of the network to the opposite edge. (See example in images below)

Issue What is throttling range? Product Line TAC I/A Series Environment I/A Series controllers Cause Setting a proper throttling range will allow for more accurate control of external actuators and devices. Resolution Throttling range is the amount of change in the process variable that is necessary to cause the controller output to change from 0 to 100%. The controller output may be 4-20mA, a voltage range, or pressure range.

Issue How to get an MSTP capture file so it can be analyzed for comm activity on an MSTP bus How to determine if a site is using bad COV management How to determine if a controller has poor bus design or installation How to determine if a site has multiple BBMD's on the same subnet Product Line Andover Continuum, EcoStruxure Building Operation Environment bCX4000, bCX4040, ASP, ASB b3 controllers Third party BACnet MSTP devices Wireshark Cause Analyze MSTP traffic via capture. Resolution To capture MSTP communication activity to a capture file that can be analyzed using a network sniffer application such as WireShark you will need the following.   Hardware One is required to have an RS-485 Adapter to connect to the MS/TP trunk USB to RS-485 Adapter USB-RS485-WE-1800-BT FTDI, Future Technology Devices International Ltd | 768-1041-ND | DigiKey  RoamIA or RoamIO Any other RS-485 adapter compatible with BACnet MS/TP and baud rates used Software Download and install the following applications: BACnet MSTP Capture Application WireShark Configuration If using the USB to RS-485 Adapter Connect the USB adapter cable to the USB port on a laptop PC Connect the RS232/RS485 adapter to the 9-pin end of the USB adapter cable. Attach a length of MSTP bus cable to the wire terminal on the RS485 adapter. If using the FTDI Connect the TDI RS-485 adapter to the USB port on a laptop PC Connect the cables to the MSTP trunk where Orange = Data+ (A) and Yellow = Data- (B) Ensure the RS-485 adapter driver is installed in Windows by opening Device Manager and ensuring that it is listed as expected under Ports (COM and LPT). Record the COMx being reserved by the adapter.  If using Wireshark with MSTPcap.exe to capture Ensure MSTPcap.exe is installed in the Wireshark Extcap folder per MSTP Capture Application link above NOTE: Wireshark may need to be rebooted if MSTPcap.exe was added while it was open Launch Wireshark Select gear next to BACnet MS/TP on COMx Set known baud rate Click to start a capture.  If using MSTPcap.exe via Command Prompt to capture Copy the MSTP Capture application to C:\ Open a command window. Launch the application by entering C:\> Mstpcap com# ###### where com# is the PC's serial port (Com1, Com2, etc.) and ##### is the current baud rate the bCX/AS MSTP bus is configured for (19200, 38400, etc.). The command window will indicate the name of the file the activity is being captured to. Once done, close the command line window The capture data can be viewed by running Wireshark. Select File > Open and navigate to the folder the capture file was saved to and select the capture file. With the higher-end MSTP capture tools such as tools developed by PolarSoft and Cimetrix, MSTP captures at 76.8K baud are possible. Lower-end capture applications like MSTPCap typically are only able to capture MSTP packets from networks running at bus speeds at or below 38.4K baud. Also, check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange. This video uses the older pipe method that was used before Extcap was available in Wireshark.

Issue To assist locating data sheets if you do not have access to The Exchange or other Schneider Electric storage areas Product Line Satchwell MicroNet Environment MicroNet 50 series Controllers Micronet Touchscreens Micronet LCD SLink sensor Cause To assist customers that do not have access to our internet or partner websites. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MN 50 Series MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN350 Controllers MLi and data sheets for Satchwell MicroNet MN450 Controllers MLi and data sheets for Satchwell MicroNet MN550 Controllers MLi and data sheets for Satchwell MicroNet MN650 Controllers Download all of the above (file size 12.0 MB) Data sheets for MicroNet 100 series controllers ETC can be downloaded from MicroNet 100 series controller MLi's and Data sheets.

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 After starting upgrade from Device Administrator AS hangs during initialization. Automation Server has a solid red status light. Unable to connect through Workstation. Product Line EcoStruxure Building Operation Environment Device Administrator Automation Server Cause Solid red LED indicates a critical error detected in the AS. It may be software or hardware related. Resolution Start Device Administrator and establish USB connection between PC and AS. Try to reinstall the firmware through the Device Administrator. If that does not work, put the unit into DFU mode: Quickly press the reset button on the AS three times in a row to place it in DFU mode. The AS will disappear from the Device Administrator and re-appear in DFU mode. Be patient to wait for this happens. Download new firmware, choose new Database. Once it goes online, restore a backup. If the LED returns back to a solid red state, this indicates a hardware failure. Contact Product Support for further assistance.

Issue RAM, Remote Alarm Manager Environment Sigma, Micronet, BAS, Vista, RAM 1.2 Cause Configuration Controller Monitoring Scripts Output Interfaces Resolution There are 3 guides to assist in configuring RAM: Operators Manual Engineers Manual (more comprehensive than the Operators Manual) Script Editors Guide Note: There are scripts that are used in RAM. These can adapted to suit specific requirements. Copy the relevant script and rename. Use the renamed version. The scripts can be found in C:\Satchwell\Binary\Remote Alarm Manager and have the .scr extension. 

Issue Belden Cables for LonWorks Networks Approved LonWorks cables Product Line EcoStruxure Building Operation,Satchwell, MicroNet,TAC IA Series,TAC Vista Environment LonWorks networks TP/FT-10, TP /XF-78 and TP/FT-1250 Cause The Echelon document 'Junction Box and Wiring Guideline for Twisted Pair LonWorks Networks' indicates Belden 8471 and Belden 85102 as the recommended cables from Belden for LonWorks networks. These may not be available from the local Belden office or the Belden distributor. Resolution Refer to Belden Technical Bulletin TB 102E 'Belden Cables for LonWorks Networks' for a list of Belden cables suitable for LonWorks communications. Take note of the difference in cable drop length and total cable bus length for the various cable models listed.

Issue Using the RD and TD LEDs to help commission and Fault finding a Modbus RTU Continuum Xdriver Using the RX and TX LEDs to help commission and Fault finding a Modbus RTU AS, AS-P, AS-B Product Line Building Operation Automation Server Premium Continuum bCX4040 (BACnet) Environment Continuum Automation server Cause How to use the TD RD(TX RX) LEDs to help commission or check an installation Resolution Continuum The Comm Port LEDs on a net controller can be helpful when first setting up or fault finding an Xdriver (ModbusRTU) Every time the net controller transmits the TD LED will flash and every time another device on the bus transmits (such that the net controller can receive it) the RD LED will flash. Thus if Xdriver seems not to be working correctly this is often the first thing to check A simple check with Modbus RTU would be to stop any automatic polling on the network, then manually refresh a modbus point and watch for a single Transmit (TD) followed by a Receive (RD). SmartStruxure The Comm Port LEDs on an AS controller can be helpful when first setting up or fault finding ModbusRTU Every time the AS transmits the TX LED will flash and every time another device on the bus transmits (such that the AS can receive it) the RX LED will flash. A simple check with Modbus RTU is to create only a  single device (or inhibit polling to all but one device) and watch for a single Transmit (TX) followed by a Receive (RX). Modbus Simulation Another useful technique when commissioning or troubleshooting with Modbus is to simulation software on a PC (with RS232/485 convertor for RTU if required). A Slave device or the Master node can be simulated eg ModSim, ModScan, ModbusSlave, ModbusPoll, Mod_RSsim

Issue What is the replacement for the Drayton Autotherm? Environment Drayton Autotherm Cause The Drayton TA/L1 actuator is obsolete, and no like for like actuators are available, this makes the Autotherm controller unusable. Resolution The TA/L1 actuator provides positional feedback to the Autotherm controller, and actuators providing feedback are very few, and providing the correct feedback is not possible. The Autotherm controller provides considerable functionality, and in our current  ranges of controllers, these cannot be matched. To upload the Autotherm data sheet, please click HERE.     The most appropriate replacement controller is CSC5352. This device will provide a compensated heating system with a timed start, the output relay can be used to enable the hot water system. Please click HERE to upload the data sheet. If separate time periods are required for the heating system and how water system, then the DC1100/1400 should be considered. Please click HERE to upload the data sheet. Please note that in both of the above options, new sensors will be required and possibly actuators too.

Issue What is the procedure for upgrading the I/A Series G3 software in an I/A Series ENC? Product Line TAC IA Series Environment I/A Series G3 Workbench software on computer (both the old version and new version need to be installed on the computer) I/A Series G3 ENC-520 or ENC-410 Cause Need to upgrade the software that is installed in the ENC. Resolution With the old version of Workbench running on the computer, backup the station running in the ENC.  All required graphic files, etc., stored in the ENC should also be backed up.  Note the station folder name for use in step 5, below. Verify that the license in the ENC is compatible with the new release to be installed. If not, use the License Manager (under the Platform) to install an updated license. If the correct version of the license is not currently available, it must be obtained and installed prior to beginning step 6, below. If the new release of the I/A Series G3 software has not already been installed on the computer, install it now. Verify that the Workbench computer has a license that is version compatible with the new release of the I/A Series software to be installed.  If the license is not version compatible, acquire a new license for the Workbench computer before continuing. Copy the entire named station folder (used in step 1) from the old release Stations folder to the new release Stations folder.  See NOTE below regarding the installation of a version downgrade. Run the "Install Platform Daemon" command from the Windows Start Menu folder for the new version of the software. Open the Workbench in the new version of the I/A Series G3 software and connect to the platform of the ENC to be upgraded. From the Platform menu, open the License Manager and verify that the ENC license has been updated to allow use with the new version of the I/A Series G3 software. Right-Click on the ENC platform in the Workbench tree and select Commissioning Wizard. Complete the commissioning process as documented in the Niagara AX Install and Startup Guide . On the first screen, select the operations to be performed.  The required minimum operations will normally be checked and shown in grey.  The "Install a station..." option needs to be checked if not already checked. Click [Next] to begin the commissioning process.  Continue through the various steps, as required.   When prompted, select the station copied in step 5. When prompted, verify that all required modules are available and are selected for installation. Allow the commissioning process to complete, following the prompts as required. The upgrade is now complete.  Start the station as required. NOTE: Do not use the process to directly downgrade the version of software installed in an ENC.  You must use the Platform "Distribution File Installer" to install the appropriate clean distribution (from the cleanDist folder under the software version to be installed.  Typically, only one clean distribution file will be available to be installed.  Select that file then click the [-> Install] button to downgrade the ENC software.  This process needs to be done as noted in step 5, above, after backing up the station but before beginning the commissioning of the device with the older I/A Series G3 software version.

Issue How to connect a SpaceLogic IP Controller via MSTP Product Line EcoStruxure Building Operation Environment Workstation Automation Server (ASP/ASB) Space Logic IP Controller RS-485 Adapter Cause Only certain SpaceLogic IP Controller models and versions support the new BACnet MSTP Adaptor and details are required on how to configure these controllers for BACnet MSTP. Resolution The following video will illustrate how to: Configure ASP/ASB for BACnet MSTP Communication. Configure a SpaceLogic IP Controller as a BACnet MSTP device. Discover the SpaceLogic IP Controller on the BACnet MSTP network. Things you need: Software EcoStruxure Building Operation Workstation 2022 Building Commission Application (available from Google Play, Apple Store, or Microsoft Store) Hardware ASP/ASB version 4.0 or higher RP controller (hardware version 10 ) RS-485 Adaptor (Isolating or Non-Isolating) RJ45 UTP Straight Through Cable (12"/300mm or less) Note: - if the RP controller does not show MSTP settings check the Space Logic IP controller firmware release notes and install firmware corresponding to the EBO version.  For example firmware versions 3 and below do not have settings for MSTP configuration. Before attempting to install a SpaceLogic controller on MSTP consult the following: Isolated RS-485 Adapter and Non-isolated RS-485 Adapter for SpaceLogic IP controller types supporting the RS-485 MSTP adapter RP-C BACnet MS/TP Support for RP models supporting BACnet MS/TP Installing an RS-485 Adapter for information on installing the BACnet MSTP adapter Connecting an Isolated RS-485 Adapter and Connecting a Non-isolated RS-485 Adapter for port usage and CAT 5 UTP connection cable Allocating Flexible Ports for additional considerations on port usage Enabling the BACnet/IP Controller to Communicate on an MS/TP Network Please see the video below:

Issue What are the basic steps when doing a conversion from TAC Vista to EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Vista Server Cause When doing a conversion from TAC Vista to EcoStruxure Building Operation (EBO), a tool called TAC Vista Conversion tool is used to build the EBO database using an export file from TAC Vista. Resolution This video shows a basic conversion of a TAC Vista database to EBO, and the steps that needs to be taken for a successful conversion.

Issue Common card vendors, types and formats commonly used by Continuum Product Line Andover Continuum Environment Continuum HID Indala Corporate 1000 Cause There is a wide range of card formats available. It's necessary to understand the most commonly used options for Continuum. Resolution Credential Card Format H50932 - Schneider Corporate 1000(35) Format A10202 - Andover 37-bit Wiegand Format 4041X (ASP-ANDINF) - Andover 37-bit Indala Format 40045 (ASP-CSI) - CSI Indala Format Indala Reader Format (FP3511A, FP3521A) 10723 (ASP-ANDINF-1L) - Andover 37-bit Indala Format 1009X (ASP-CSI-2L) - CSI Indala Format 10022 (ASP 26-bit Wiegand-1L) - 26-bit Indala Format HID MultiCLASS Reader (9xx Series) 4041X (ASP-ANDINF) - Andover 37-bit Indalat Format For additional  information on other HID formats, see the following article: Which HID card formats are supported by Continuum?

Issue A Schedule or PE program can not change the value of a point because it is set by another process at a higher Command Priority. Product Line Andover Continuum Environment CyberStation bCX4040 B3s Cause Command value must be Relinquished at the priority that no longer needs to control the point's value so that a command with a lower priority can take control of it. Resolution Edit the point from the BACnet view. Go to the Command Priority tab, this tab shows the 16 priorities and their current statuses   Select the priority to relinquish and then click on the Relinquish button. The command with the next highest priority should then immediately take over.

Issue  Script error when navigating menu in TGML graphic in 1.4. Graphic was working fine in 1.3. Product Line EcoStruxure Building Operation Environment Workstation Enterprise Server Automation Server Cause In releases prior to 1.4, graphic objects were not unloaded when navigated away from. This has been fixed in 1.4. As a result of this change, If a TGML has a navigate in a script (by using invoke) this could cause a script error if there are scripts on parent elements. Resolution Open the graphic Navigate to the script and edit, or view in source mode Add evt.stopPropagation(); before the invoke in the Click() function. For an updated version of the component without the error, go to the community: Navigation Menu (JF/Denmark) rev 2.