Building Automation Knowledge Base

Issue HID Corporate 1000 48-bit card not natively supported by Continuum System Product Line Andover Continuum Environment CX9900/9940 CX9702 CX9680 ACX5740/5720 Cause Continuum does not have built-in support for the HID Corp 1000 48-bit cards.  The system must be configured using a custom card format program. Beginning March, 2015, HID Global will introduce a new Corporate 1000 format referred to as “Corporate 1000 – 48”. All end-users who register for the Corporate 1000 program after February, 2015 will be issued a unique Company ID in the new Corporate 1000 – 48 format. The original 35-bit Corporate 1000 format will now be referred to as “Corporate 1000 – 35”. Those end-users who have been issued a unique Company ID in the Corporate 1000 – 35 format can continue to order credentials without interruption or change. Introduction of the new format will not impact or affect customers who registered for the program under the original structure. Resolution Here is the process to create a custom format for a HID Corp 1000 48-bit card in Continuum.  Only one custom card format can be used in NC1(CX99xx), NC2(CX968x) using AC1 modules, while up to four custom formats can be used with the ACX57xx and NC1/NC2 using AC1Plus modules. Create in each NC1, NC2, ACX57xx an InfinityNumeric point called AccessFormat (use this spelling exactly!). During the creation process, attach a manual array (log) with 22 entries to the point.  If creating more than  custom card format create InfinityNumeric points called Accessformat2, AccessFormat3 and AccessFormat4. Create the following InfinityProgram in each controller. The program should be type FallThru, and AutoStart.  The program can be copied to other access controllers where it is needed.   Note: The HID Corp 1000 48-bit card format allows site codes to be up to 22 bits, however, site codes in Continuum are restricted to a 16 bit value (0 to 65535), due to this Continuum limitation only the 16 least significant bits of the site code encoded on the cards can be read in Continuum, site code values above 65535 will show as different smaller number in Continuum. Program Name: SetCustCrdArray FlowType: FallThru AutoStart: True Code: Line SetFormat Set accessformat[0] to 1 'array has been initialized Set accessformat[1] to 48 'total number of bits in the format Set accessformat[2] to 0 'control mask Set accessformat[3] to 0 'mfg mask Set accessformat[4] to 0 'start bit of mfg Set accessformat[5] to 0 'end Set accessformat[6] to 8 'start of site code Set accessformat[7] to 23 'end Set accessformat[8] to 24 'start of card number Set accessformat[9] to 46 'end of card Set AccessFormat[10] to 14043 ' odd parity mask, first 16 bits Set AccessFormat[11] to 28086 ' odd parity, next 16 Set AccessFormat[12] to 56173 'odd parity, next 16 Set AccessFormat[13] to 0 ' odd parity, next 16 Set AccessFormat[14] to 23501 ' even parity, first 16 Set AccessFormat[15] to 45811 ' even parity, next 16 Set AccessFormat[16] to 28086 'even parity, next 16 Set AccessFormat[17] to 0 ' even parity, next 16 Set accessformat[18] to 0 'even number multiplier Set accessformat[19] to 0 'card number divider Set accessformat[18] to 0 'even number multiplier Set accessformat[19] to 0 'card number divider Set accessformat[20] to 0 'start bit of issue code Set accessformat[21] to 0 'end bit of issue code Set accessformat[22] to 0 'decimal shift of issue code stop

Issue Where can I get example programs and programming information on the Smart sensors? Product Line Andover Continuum Environment Smart Sensors: TTS-SD-LCD-1 TTS-SD-LED-1 Cause Smart sensors require specific Plain English programming that is different from other controllers, where is the documentation to support this? Resolution The Smart Sensor Installation and User's Guide and Example programs for the Smart Sensors are available for download from The Exchange Extranet.   PSS Example programs

Issue Enterprise Server will not start due to no valid license file error: "nsp.csc.licensemanager No valid Enterprise Server license found. Terminating server." or Cannot find license file. (Error code: -1) Product Line EcoStruxure Building Operation Environment Building Operation Software Administrator Building Operation License Administrator Building Operation Workstation Cause Enterprise Server is not started and states no valid license file is found. License Server is installed on the same computer and has valid license(s). Similarly, WorkStation may not start even with a License Server installed with a valid license. If you get error -1, it means that you didn't enter the required @ before the license server address. Resolution In general, any licensed Building Operation software (Enterprise Server, WorkStation, Editors) needs to know where the license server is located. That means that the license server path needs to be entered on any PC having licensed Building Operation software installed. The "License Administrator" part of the license installer can be installed on any PC, and the license server address set using the administrator. The license server itself does not need to be installed on all PC's, but only on the PC hosting e.g. the Enterprise Server. The IP or DNS name of the PC hosting the license server is entered with an initial @, e.g. if the IP of the license server PC is 1.2.3.4 you enter @1.2.3.4 Checkpoints Remember to enter the license server address starting with a @. For example, don't use "localhost" but "@localhost". Is your evaluation license current? If not, download from EcoXpert Extranet Check that antivirus software is configured to allow the operation of the license server. (refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96)) Reboot the machine where the License Server is running. It has been observed in some cases where the error 'No valid license or Cannot find license file error' appeared after an upgrade that rebooting the machine solves the problem. Check to see if there are multiple versions of the License Server installed on the machine. If multiple versions are installed, make sure to only run the highest installed version as a Windows Service. All other License Server and License Administrator software should be uninstalled from the machine.

Issue Support is required for the Automated Engineering Tool commonly known as AET Product Line EcoStruxure Building Operation, Automated Engineering Tool Environment AET Cause Further support is required for Automated Engineering Tool AET. Resolution For more information including videos, user guides, specification sheets, etc about the tool, please visit the Schneider Electric Exchange and EcoStruxure Building Management System WebHelp. For assistance or to report problems with the AET applications/programs, please post your questions on the Exchange Community.  In order to report functional problems with AET, please reference the support contact information found in Automated Engneering Tool - PA-00559 or email  aet.support@schneider-electric.com  

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue The specifications and setup details of the EH series humidity sensors. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, TAC IA Series, TAC INET, TAC Vista Environment Humidity Sensor Cause The EH Series Room, Duct and Outside humidity sensors are a universal Relative Humidity transmitter that can be powered with either a +15 to 36 Vdc or 24 Vac supply voltage. The EH series sensors are designed with a field selectable 4-20 mA, 0-5 Vdc, or 0-10 Vdc output signal that is equivalent to 0 to 100% RH. The EH Series is used in building automation system, humidity chambers, and OEM applications and is compatible with Vista, Continuum, I/Net, I/A, and SmartStruxure systems. Resolution EH Series Humidity Sensors Click the below links to look at the documentation for these sensors including the dip switch settings. EH Series Humidity Sensor Data Sheet EH Series Humidity Sensor Installation and Operation Instructions Old EH Series Humidity Model For information on the older style of dip switches (models with two separate sets of dip switches), see the document below. Old EH Series Humidity Sensor Installation and Operation Instructions

Issue COVNotification messages in BACnet captures. Product Line EcoStruxure Building Operation Environment BACnet IP network BACnet MSTP network BACnet networks with controllers that support COV (Change of Value) Cause COV increment is an attribute that is available in several BACnet points that is settable and when this attribute COV Increment is left at a setting of zero can cause COVNotification messages appearing as broadcast storms creating un-necessary network traffic. Resolution It is suggested to set the value of the COV increment attribute to something other than the default zero or to a value that is pertinent to the point in question. The COVNotification services are uni-cast messages and can have a many to one relationship depending on how may clients are subscribing to the point. Example: Jobsite has a BACnet OAT (outside air temp) input point with the COV increment of zero. The OAT point is added to the watch window or a binding to a graphic or program. The OAT is changing ridiculously fast due to wind and intermittent clouds. The value is changing by 1/1000 of a degree and each COV (change of value) message is delivered out to any object that is referencing the point. But does the value need to display or do we care if the point changes by 1/1000 of a degree. Let's say that the sites requirement only needs value changes of 2 degrees or more. The COV increment can be set to 2.0 and now the UnconfirmedCOVnotification message would only be sent if the OAT changed by 2 degrees or greater. This alone would reduce 100's if not 1000's of network packets. Imagine a jobsite with the above scenario and 100 different points all with the COV increment of zero. Setting the COV increment to something other than the default of zero is one of many ways to improve BACnet communications and reduce what may appear as broadcast storms on the network.

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 Backup and Restore assures that Building Operation server data can be restored after a hardware failure or data loss. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Enterprise Server Automation Server Workstation Cause Restore is the process of restoring data to an original or former state. Using restore, you can revert back to a previous snapshot of the server data despite any configuration changes made since the last backup. In Building Operation, restore is designed to be a manual rather than an automatic process to avoid the accidental overwriting of current server data. For convenience, Building Operation displays only the backup files that apply to the selected server.  For more information on making a backup, see Backup of StruxureWare/EcoStruxure Building Operation AS and ES. Resolution Restore an Enterprise Server Backup Set If restoring to a previous snapshot of the database that is currently running, start with step 6. If restoring a database that is different from the one currently running, start with step 1. Launch StruxureWare Software Administrator; Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare Software Administrator. Click the Stop Service button and then click OK. Go to the Enterprise server database folders; C:\ProgramData\Schneider Electric\StruxureWare X.X\Enterprise Server Change the name of the current database folder to something that identifies it with the project's name (Example outlined in red: db changed to Old_db). Make a duplicate of the "db - Copy" folder (Example outlined in orange). It is important to always maintain a clean database folder by making copies. After first installing StruxureWare, a copy should be made of the original "db" folder. Copies of this folder should be made before restoring databases or creating new ones from then on. Change the name of the "db - Copy" folder to "db" (Example outlined in blue: db - Copy changed to db). Launch StruxureWare Software Administrator again, click Start Service, and then OK. Launch StruxureWare WorkStation and log into the enterprise server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the enterprise server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Note: If a backup set is seen in red it means that the backup is not compatible with the current version of the server. The backup has to be the exact same version as the server including any hotfixes or service packs.   Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available. Note: The server name is part of the restore data. Therefore, if you rename a server after a backup, a restore process will revert back to the previous server name.       Replace an Automation Server with a Restore Note: The automation server restore should be done by logging directly into the automation server. Launch StruxureWare WorkStation and log into the enterprise server or the automation server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the automation server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available.

Issue How can Continuum be setup to read the 32 bit serial number from a Mifare smart card for use in access control? Product Line Andover Continuum Environment Using iClass serial number readers: R10, R15, R30, R40, RK40 Custom Wiegand, AccessFormat array Custom Format Cause Mifare smart cards that have been provided and programmed by others may not have the keys available to allow a reader to access the data on the card. Without sending the cards away for re-programming how can the card still be used for access control. Resolution The HID iClass readers (R10, R15, R30, R40, RK40) have the ability to read the 32 bit serial number from a Mifare Smart card. These readers will output a single 32 bit Wiegand string representing the card serial number. To use this on Continuum: Create a numeric point called "AccessFormat" and define it as a manual array with 19 entries. Create a Plain English program in the controller to fill up the array with values as per the Mifare Serial Number spreadsheet. In the door configuration select "Custom Format" and ensure one of the 4 site codes is set to 0. Swipe the card at the reader and open a list view of Events, this will show the card number as the serial number from the card. Create a new Person with card type Custom Wiegand, Site code 0 and set the Card number to the serial number as read in the list view. This may be a 9 or 10 digit number. Notes: If using card numbers in Plain English Programs or displaying in Pinpoint Graphics, you will be restricted to using a maximum of 6 digit numbers (maximum card number being 999,999). See Loss of resolution on metering points when the number is 7 digits or longer for details on this restriction. The old style Personnel editor will not allow the entry of site codes of 0. Use Personnel Manager or set attributes in List Views of Personnel.

Issue SPP920 Datasheet, Technical Information and Installation Instructions Product Line Field Device Environment SPP920 Differential Pressure Switch Cause No information available for the SPP920. The Sensor catalogue says it is supported by Huba. Resolution Either click link www.hubacontrol.com and search for 630. or the Technical information can be downloaded here. Installation Instructions can be downloaded here. Mechanical connections are: P1 = High Pressure (discharge/flow), P2 = Low Pressure (suction/vacuum) All of the various pressure range options come with the following options: - EPDM diaphram material - Brass Case - Spec Cover PG9 - IP65 Rating - Bracket Type A

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 for assistance. Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue Unable to add an Automation Server into the Device Administrator via IP. Error seen - Could not logon to server x.x.x.x This can be caused by providing the wrong password or the password has expired on the server.  If the password has expired, log on to the server using WorkStation and change the password. Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause Failed attempts of connecting to an AS-P, AS-B, or any IP controller with device admin will trigger the EBO security feature of SSH console lockout. This security feature defaults to 15 minutes and since the device admin uses SSH for communication, it will not allow the connection to an automation server while in this lockout state.  Resolution If a site is experiencing communication issues, then the SSH console lockout could be going into effect before a good connection is established. Reducing the SSH console lockout time period will allow for a connection to be made sooner without waiting out the default setting of 15 minutes. Use Workstation to log in to the server experiencing the issue. Go to Control Panel. Click on "Security settings" under the Security and Communication title. Locate the "SSH Console Lockout" configuration setting and adjust the lockout time to a shorter duration such as 1 second. Click Save. Open Device Administrator and add the Automation Server using IP.

Issue Is there a way to reset the password for web access to a BCX? Product Line Andover Continuum Environment Continuum site with passwords other than the default Cause The password was changed by mistake. Resolution Restore the controller's user names, passwords and configuration settings to the original factory values (Reset IP button using a two stage operation) The location of the Reset button and the Reset IP button on the controller board. Page 124 in appendix A of the Technical Reference Guide. If you cannot get into Continuum Explorer and edit the controller user under that controller and set the password. You will have to reset the controller and then re-commission and then reload.  Try acc/acc first and then after that the following: Using the Reset IP button The Reset IP button has two stages of operation: Stage 1 is initiated by depressing the button for 5 seconds. After 5 seconds, the IP address, and all network-related addresses entered on the Network Configuration page, are returned to the original factory default values. Stage 2 is initiated by depressing the button for 35 seconds. After 35 seconds, the database is cleared and all persistent configuration data is erased, with the exception of the error log. Note: Depressing the button for 35 seconds performs both operations, setting the IP address back to the factory default setting and clearing the database. When you initially depress the Reset IP button, the CPU Indicator LED will begin blinking. At 5 seconds, the LED will stop blinking and remain lighted in a continuous state. If you release the button before 5 seconds has passed, no changes are made. If you release the button after 5 seconds, but before 35 seconds, stage 1 is executed, but stage 2 is not. The IP address has returned to the original factory value, but the database has not changed. Please see Default IP address for BCX, ACX57xx, CX9702 and Netcontroller II for information on default IP addresses.

Issue Example graphics components required Product Line EcoStruxure Building Operation Environment TGML - Building Operation Graphics Editor Cause No standard graphics or components are supplied within the product. Resolution A Standard graphic component library can be downloaded from the Buildings Download Center. This consists of a number of Component Libraries that can be installed on a Workstation by double clicking on each one. In your TGML Editor, Right click in the Components window and select "Categories" you can then select the categories you require to see in your components section. There are also a lot of standard Snippets that have been developed by users around the world, these are available to download from the EcoStruxure Building Operation Forum - Graphics Exchange.

Issue There may be a situation where the External Interface File (XIF) needs to be extracted out of the controller in order to properly set up the controller in a building automation system.  Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment External Interface File (XIF) NodeUtil Loytec XIF Builder Cause These tools will help with the extraction of an XIF file. An XIF file is used to create a Niagara R2 shadow object, a Niagara G3 LMNL file, LonWorks device template, and a SmartStruxure device template.  Resolution The device manufacturer should provide an XIF, and in most cases, a DRF kit as well. The XIF provided by the manufacturer of the controller should be used first but if issues arise it may be required to extract the file from the controller. There are a number of tools available that will create an XIF, but the DRF kit cannot be created by any tool and must be supplied by the manufacturer. This MUST be provided along with the device. The list below covers some of the tools which are available. NodeUtil                          (header: bad,           NVs: ok,                      DMA/File-SCPTs are omitted) Vista's XIF-builder           (header: bad,           NVs: almost ok..,       DMA/File-SCPTs are omitted)  Loytec plugIn                  (does a perfect XIF from a device using Loytec's stack)   NodeUtil is available from the Echelon website (free registration is required) - The NodeUtilLauncher package attached makes it easy to use NodeUtil with Loytec interfaces. Loytec XIF Builder is available from the Loytec website (free registration is required) Using Lonmaker and the XIF Builder. Using NL220 and the XIF Builder. If the uploaded XIF still contains some detailed prompted error, refer to Error displayed when importing a device XIF into SmartStruxure.

Issue Starting in EcoStruxure Building Operation 2.0, a new licensing structure has been implemented to reflect the new scalable pricing model.  This new pricing model is different from previous versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Version 2.0 and up Cause Due to the change in our pricing model within EcoStruxure Building Operation 2.0 and later, we have new policies regarding scalable pricing which has been different in the past. Resolution In regards to questions around the new scalable pricing structure For EcoStruxure Building 2.0, please reference the sources below. EcoStruxure Building Operation Scalable Pricing Frequently Asked Questions EcoStruxure Building Operation v2.01 - Scalable Pricing Policy Scalable Pricing Overview Video - EcoStruxure Building EcoStruxure WebHelp Article about Licensing Model General Notes: An upgraded or newly purchased 2.0 license will work with sites running older versions of EcoStruxure Building Operation. Each Enterprise Central and each Enterprise Server license comes with one client license.  It will always be possible to operate the system and will always be possible to add to the system (besides attaching automation servers to the enterprise server) if you do not have enough licenses. After certain time periods, the warnings, banners, and prompts will get larger and more noticeable.  If ONLY hosting IP devices and no Automation Servers under the Enterprise Server, it is still necessary to purchase the minimum size Enterprise Server license (10 or fewer Automation Servers) as well as then the appropriate number of hosted node licenses.  The intent of this is to limit the development and support costs of having a highly resourced user interface at the Enterprise Server and to distribute this load across multiple servers.

Issue Default IP Address for AS,TCP/IP IPv6, and StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment Building Operation site Cause Attempted to ping AS and got "Request timed out." (AS does not have a default IP address) After going through StruxureWare Building Operation Device Administrator's Open Console which is also referred to as PuTTY(outlined below #1), the configuration has the proper: Hostname DHCP enabled/disabled IP address Subnet mask Default gateway DNS server Domain name Still the ping of the AS IP address receives "Request timed out"  Is this from a Virtual environment? See Resolution 6 below. Resolution Check the following settings: Use Device Administrator to set a static IP address for an Automation Server. Connect the Automation Server to the PC's USB port In Device Administrator, select the Automation Server you want to set the IP address for. On the View menu, click Console which opens console or PuTTY.  See NOTE below if Console icon not shown. If you are prompted to type a login name, default is "admin". Press Enter. If you are prompted to type a password, default is "admin". Press Enter. Type "setip". Press Enter. If you want to change the host name, delete the current host name and type a new host name. Press Enter. Type "no" to use a static IP address. Press Enter. Type the IP address for the Automation Server. Press Enter. Type the subnet mask. Press Enter. Type the default gateway address. Press Enter. Type the DNS server address. Press Enter. Type the domain name. Press Enter. Type "yes" to write the configuration. Press Enter. After the Network settings, "successfully updated" message is displayed, Type "exit" to log off. Press Enter. Rather than connect through a router or switch, plug the Ethernet cable directly into the AS. Ethernet port is AutoSensing (No Crossover Cable required). Adjust IP settings to close proximity IP and Subnet, such as the following example: Computer IP=192.168.1.2 Computer Subnet=255.255.255.0 Automation Server IP=192.168.1.5 Automation Server Subnet=255.255.255.0 Have only one NIC or network card enabled in Network Settings on this computer In Network Settings, uncheck the Internet Protocol Version 6 (TCP/IPv6), which will disable. TCP/IP Version 6 is the latest version of the internet protocol which provides communication across diverse interconnected networks which is not necessary for this configuration. If you are using a virtual environment, exit that virtual environment and attempt the configuration from the real-world environment.  If AS hangs or comes up with the Status light in red: Start Device Administrator and establish a USB connection between the computer and AS. 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. Perform Upgrade device operation. The AS can be configured using DHCP (Dynamic Host Configuration Protocol) using Device Manager. It is recommended to not use DHCP but rather Static IP addresses. If the IP of the AS/ES changes, then reconfiguration of other AS/ES, or BACnet/IP, Modbus/IP interface needs to be changed also. NOTE: Beginning with StruxureWare Building Operation release 1.4.0, the Device Administrator no longer displays the "Console" icon on its toolbar. You can still access the PuTTY console by holding down the shift key and right-clicking on the automation server. You will have the option to open 'Console'. NOTE: Some network configuration setting changes may be prevented by the connected network. If you have issues getting the AS to save changes, disconnect the AS from the ethernet and use the USB connection only.

Issue BACnet MS/TP Bus Communication Troubleshooting Checklist Product Line TAC IA Series Environment I/A Series BACnet controllers (MNB-70, MNB-V1, MNB-V2, MNB-300, MNB-1000) on an MS/TP bus. Cause BACnet MS/TP Bus Communication Troubleshooting Checklist Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. Power Each controller requires 24 VAC from a Class 2 transformer. See the Installation Instructions for each controller, and the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Read-Only Flag Use the WorkPlace Tech Commissioning Tool (WPTCT) to check “Device Properties” of the controller. If the status is “Operational, Read-Only”, the input voltage to the controller may be too low. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Due to the short duration of the low-voltage condition required to set the flag, it is unlikely that you will see it when measuring the input voltage with a digital meter, so check the “Device Properties”, and correct the problem as noted on page 28 of the guide, (reduce transformer loading, reduce wire length between transformer and controller, and /or use wire with higher current rating). Diagnostic LEDs The MNB controllers have onboard diagnostic LEDs that are useful in troubleshooting. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 3, “Communications Hardware Checkout”, Table: “LED Indications”, for a detailed description of the behavior of the LEDs and their diagnostic uses. Topology It is very helpful to draw the topology of the bus when you start troubleshooting. If there are no repeaters on the bus, the topology must be a daisy-chain, with no tees or stars. MS/TP network wiring to MN-Sx sensors must be run to the sensor, then to the next controller on the bus, in a daisy-chain; no tees or spurs are allowed. Maximum length of a wire segment is 4000 feet. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “MicroNet MS/TP Network Wiring”, for details on Communications wiring. Repeaters B-LINK-AC-S, Andover Controls MS/TP Repeater B-LINK-AC-F-S, Andover Controls MS/TP Repeater Fiber See the MicroNet BACnet Smoke Control Systems Manual, F-27419, for details on the use of these wire and fiber repeaters with MNB controllers. See F-27419, Chapter 5, “Approved MS/TP Repeaters”, including the wiring example. Maximum Number of Devices The maximum number of MNB controllers depends on the cable used, and the Baud Rate. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types”. The MNB controllers are quarter-load devices, so a maximum of 128 or less are allowed on an MS/TP trunk, depending on the cable used. Addressing Avoid duplicate addresses. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Required Configuration”, CAUTION: “Duplicate addresses on an MS/TP network trunk will result in erratic behavior, lost tokens, and disrupted communication. There is no software tool that will identify duplicate addresses on an MS/TP network trunk. Typically, if two controllers are set to the same address, one of the controllers will appear to be missing from the list, and the address shared by the two controllers will intermittently come and go from the list.” Biasing As a requirement of EIA-485 (formerly RS-485) bus topology, an MS/TP network must have a minimum of one set, and a maximum of two sets, of bias resistors in place. The MNB-300, MNB-1000, UNC-520, and ENC-520 have jumpers to enable or disable the bias resistors. See bulletin TB06-09, “RS-485 Bias Resistors and the UNC-520-2 / ENC-520-2”, page 3, for a photo of the bias jumpers on a UNC-520-2. Terminators A 120-Ohm End-of -Line (EOL) resistor is required across the “MS/TP +” and “MS/TP -” terminals at each controller at the end of a wire segment. The MNB-1000 and MNB-300 are equipped with a jumper-selectable end-of-line (EOL) termination resistor. The default position for the EOL jumper is “EOL termination not present.” See the MicroNet BACnet Smoke Control Systems Manual, F-27419, Chapter 5, “Approved MS/TP Repeaters”, Figure titled “UL 864 Listed MS/TP Repeater and Isolation”, Note 4, for an important exception, requiring external EOL for the MNB-300 and MNB-1000, when used on a bus with an approved repeater. If a UNC-520-2, ENC-520, MNB-V1 or MNB-V2 is installed at the end of the trunk, install a discrete 120 Ohm EOL resistor, part number EMSC-546, or equivalent. Cable Use of the proper cable is critical to the communications performance of the networked controllers. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types” for a list of recommended cable types. As shown in the table, cable selection affects both the maximum number of controllers allowed on the trunk, and the maximum baud rate. WorkPlace Tech Interface The MNB-ROAM-IA is the recommended communications converter for connecting WorkPlaceTech, including the WPT Commissioning and Flow Balance Tools, to an MS/TP trunk. It is supported in versions 5.7.1 and later. A converter that had been recommended earlier, the B & B Electronics model USOPTL4, was found not to operate reliably at speeds above 38.4 K baud. (See Direct MS-TP Connection with B & B Electronics Converters (Revised) - TB08-02-02 for details). The MNB-ROAM-IA supports Bluetooth wireless connection between WorkPlace Tech suite and the MS/TP network, for distances up to about 40 feet. One external Bluetooth adapter has been tested and approved - the Belkin USB adapter. (See Supported models of Bluetooth adapters with WorkPlace Tech for details). A problem we have seen with some MNB-ROAM-IAs is when trying to add Bluetooth device, the Bluetooth Wizard identifies it as "Serial Port Device, Unknown: Major(0), Minor(0)" instead of "tac-RoamIA:xxxxxxxx" where xxxxxxx is the serial number. There is no way for WPT to use the ROAM-IA if the computer can’t pair with it. Currently, there is no known solution, other than replacing the device. Divide and Conquer This is a strategy for dividing a bus into smaller sections in order to isolate a controller or section of bus that might be causing communication problems. The general idea is to divide the bus in half, and see if communications are possible from one end to the other end. If not, divide each half again, and continue until the problem(s) are found. Reference Documents F-27360 TAC I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide F-27358 TAC I/A Series MicroNet BACnet Workplace Commissioning Tool and Flow Balance Tool User’s Guide F-27456 TAC I/A Series MicroNet BACnet MNB-70 Zone Controller Installation Instructions F-27345 TAC I/A Series MicroNet BACnet MNB-300 Unitary Controller Installation Instructions F-27346 TAC I/A Series MicroNet BACnet MNB-V1, MNB-V2 VAV Controller Installation Instructions F-27347 TAC I/A Series MicroNet BACnet MNB-1000 Controller Installation Instructions F-27419 TAC I/A Series MicroNet BACnet Smoke Control Systems Manual

Issue Tridium N4.11 Upgrade Considerations  Product Line TAC IA Series Environment I/A Series N4.11 Enterprise Server I/A Series N4.11 Jace 8000 Cause Detailed information about N4.11 upgrade prerequisites and best practices  Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.11. Please review prior to upgrading to Niagara 4.11. Niagara 4.11 and Default NRE Memory Changes: A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000. Prior to upgrading your JACE-8000, please review NRE default configuration changes and RAM disk removal In 4.11. Niagara 4.11 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.11, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised, or derived from untrustworthy sources. Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules. Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.11, unsigned modules will not execute. For more information, please review the Niagara documentation on Third-Party Module Signing Niagara 4.11 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide. Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.11.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Ubuntu Linux 20.04 LTS – Desktop & Server Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10) As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward. Using Web Launcher with Niagara 4.11 Web Launcher 21.4.1 was recently revamped for Niagara 4.11 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 311 and certificate management has been updated to work with Niagara 4.11 along with any legacy or prospective release. Prior to using Web Launcher with Niagara 4.11, customers should update Web Launcher accordingly (see steps below). How to update Web Launcher? Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page. Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version. Niagara 4.11 Release Notes: The release notes for Niagara 4.11 are located here.

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server  Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Within the Automation Server logs are many records that are logged as a part of normal operations and unexpected events. Resolution Automation Server: Automation Server error logs can be retrieved using Workstation, Device Administrator, or WebStation. Device Administrator can be used in case of crash information is required, ex. dump files, or if the Automation Server is not accessible via WebStation or WorkStation. Workstation: Connect to EBO system with EBO WorkStation. Select the target Server  Expand the System folder Expand the Modules folder Expand the Trace folder and see Trace Settings For EBO 3.1 or higher, Double-click both Trace Log and System Log to open separately  For EBO 3.0 and lower, including SBO 1.x Right-click in Trace Settings Select Trace Settings in the menu Select Get System Log Repeat to select Get Trace Log  Device Administrator: Follow this WebHelp article: Getting Automation Server Debug Information If requested to retrieve a core dump, use this method to retrieve the Device Administrator Debug Information zip file. Then perform the following to make sure the zip file contains a core dump with a relevant timestamp for the event being investigated. Open Zip Open the folder containing the server name and IP address Open Server folder One should see file(s) with filename in this format core_dump_<Serial Number>_nsp_servers_<Timestamp>.tgz WebStation: NOTE: The steps below are no longer valid for EBO 2022 and above. See the Webhelp Topic on collecting these logs from Automation Servers: Viewing and Downloading Automation Server Log Files. This process is now similar to that described above for WorkStation.   Credentials used to log in must be a member of a group that allows the policy of Web Configuration: Allow members to access Automation Server Web Configuration. Launch a web browser that is compatible with the installed EBO version as mentioned Webstation Specification Sheet. Type the IP address of the automation server to open the Webstation. Log into the Automation Server.                   Once logged into the Automation server, go to the Settings menu in the top right corner and click on Device Configuration. Click on the Server Log tab to view the automation server's log files. To save a copy of the log to your PC, click on the Get all log files link. The log files are compressed into a zip file and exported to downloads folder. Enterprise Server and Enterprise Central: For more information, check this article: Error logs from the Enterprise Server and Enterprise Central - Communities