Building Automation Knowledge Base

Issue Update OS, changing a controller, BACnet to Infinet or Infinet to BACnet Can b3 controllers be converted to i2 controllers? Can i2 controllers be converted to b3 controllers? Converting between bCX4040 and bCX9640   Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 Controllers - See Compatibility Matrix bCX Controllers - Continuum 1.7 onwards Cause Only a limited number of controllers can be converted, BACnet to/from Infinet, using Update OS. Resolution The following controllers can be converted between Infinet and BACnet, using the appropriate firmware files: bCX (bCX4040 to/from bCX9640) (options like Xdrivers, node count, IO modules and expansion IO modules are not effected) i28xx-V - b38xx-V (i2865-V to/from b3865-V, i2866-V to/from b3866-V, i2885-V to/from b3885-V) Please see link for swapping the firmware of non -V model i2/b3 Attempting to flash (Update OS) any other controllers BACnet to/from Infinity is not recommended. In nearly every instance, the result will be a non-functioning controller.   UPDATE: A procedure is now available to convert the non -V i2s to b3s in the field https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/416712    (Note: In the bCX controllers, the ACCNetID will revert back to the default of "1", you may need to change this in the Controllers configuration webpage back to what it should be.  See Will IP settings persist when flashing a bCX4040 (BACnet) to a bCX9640 (Infinet)? for details.)   Please refer to Exchange for specific firmware: BACnet Firmware Infinet Firmware The following can be used as a general rule to determine which OS is currently running in the controller. bCX only. (b3 & i2 CPU is green) CPU LED is Green = BACnet OS CPU LED is Yellow = Infinet OS

Issue When configuring a BBMD what is the Broadcast Distribution Mask and what are the valid settings for the field. Continuum EcoStruxure Building Operation Product Line EcoStruxure Building Operation, Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution When configuring a BBMD the BACnet protocol defines two methods of propagating the broadcasts messages to other networks. The two methods are referred to as One-Hop also known as a Directed Broadcast and Two-Hop.   Note: In this article the subnet mask is shown using Classless Inter-Domain Routing(CIDR) notation. An IPV4 address is 32 bits long, CIDR notation defines the number of bits used for the subnet mask. The most commonly used are: /8 or 255.0.0.0 /16 or 255.255.0.0 /24 or 255.255.255.0 /32 or 255.255.255.255 One-Hop With the One-Hop method the local BBMD transfers the message directly to the remote devices via the remote router. In this case the IP routers have to support the transfer of IP broadcast messages to remote IP subnets Figure 1 Figure 1 above illustrates the one-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a message directly to the broadcast address of the 192.168.1.0/24 subnet, it is then up to Router2 to send the directed broadcast to all devices on the subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks. (i.e a bCX hosting an MSTP network on COMM2)   Two-Hop With the Two-Hop procedure a BBMD device transfers broadcast messages to a further BBMD in the remote IP subnet, which then distributes the messages in its local network as IP broadcast messages for its IP subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks.(i.e a bCX hosting an MSTP network on COMM2) Figure 2 Figure 2  above illustrates the two-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a unicast message to each BBMD device on its table, it is then up to each BBMD device on each subnet to send a broadcast that will be heard by all devices on the subnet. Which distribution mask should be used? As mentioned earlier, in order for the one-hop method to work, the router on the remote subnet MUST be configured to process incoming messages sent to the broadcast IP address, the two-hop method on the other hand is guaranteed to work, so when in doubt use the two-hop method. Most sites use two-hop distribution for the reason stated above,, the only obvious disadvantage of the two-hop method is that it is a little more verbose than the one-hop method since the message appears twice on the subnet, once as a unicast sent to the BBMD device and then again as a broadcast sent by the BBMD device. In Building Operation and Continuum the distribution mask defaults to the two-hop method (/32 or 255.255.255.255) How to configure the distribution mask For one-hop enter the subnet mask of the remote network in the distribution mask, the system will apply the mask to the IP address to obtain the broadcast address for the remote network. For two-hop enter 255.255.255.255, this tells the system not to do a direct broadcast and instead do a unicast to the remote BBMD device. Sample distribution mask In the BBMD table of a bCX shown in the screen shot above, BDT #1 and #3 use the two-hop method while BDT entry #2 uses the one-hop method.

Issue How do you set up the VisiSat server for MicroNet or IAC controllers? Environment VisiSat server settings Cause Assistance for correct configuration. Resolution LIB-4-485 is a RS-232 to RS-485 converter to be used with VisiSat for communicating to MicroNet NCP Controllers or Satchnet controllers without the need for a MNMI or MIU respectively. The LIB-4-485 is powered from the communications port of your PC and no external power is required, providing the PC port adheres to the RS-232 specification (we have used successfully with Dell PC’s). The connection to the LAN are:-  TD (A) – To negative (-) communications terminal of controller. TD (B) – To positive (+) communications terminal of controller. GND – Screen connected at LIB card only and not at controller.   VisiSat requires the following settings to be configured in the VisiSat Server. The Server is found minimized next to the clock in the system tray. At the bottom right corner of your desktop, double click the server icon to show the VisiSat Server client. Select settings from the Network Menu Option. The Configure Network Settings window will be displayed as below. Select ‘Serial Port’ as the Transport type, and click the Configure button. 1. The configuration for use with MicroNet controllers needs to be as detailed below. 2. The configuration for use with IAC controllers needs to be as detailed below. Once the correct selection has been made click OK. VisiSat is then ready to use with selected controllers.   The VisiSat Engineering guide contains additional information regarding the VisiSat server Click here to download or view the VisiSat Engineering manual.  

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 PCT does not run properly following installation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Certain environmental settings may need to be adjusted in order to successfully install PCT. These settings are not described in the Project Configuration Reference Guide. Resolution If you have issues successfully running PCT after installation, check the following items: Enable Virtual Hardware Acceleration in BIOS Use this tool to check if virtual hardware acceleration is already enabled on your PC: Intel: https://www-ssl.intel.com/content/www/us/en/support/processors/processor-utilities-and-programs/intel-processor-identification-utility.html AMD: https://support.amd.com/en-us/search/utilities?k=virtualization Disable all Ethernet Adapters except the one in use (Only applies to Server Mode): It may be necessary to check Windows Device Manager for hidden network adapters Disable the Windows firewall Disable Anti-Virus Software A true local account may be needed to install and/or run PCT due to Group Policy or other factors. Use Run as Administrator for both installing and running PCT Note: You can right-click the PCT icon, open properties, select the “Compatibility” tab, and check the box “Run this program as an administrator” Test PCT by opening up the software application, creating a project, creating a server, and opening it up in WorkStation If PCT opens and works then enable Windows firewall and Anti-Virus program. - User may need to allow PCT in Windows firewall and PCT utilize port 9091 as default. - User may need to add exceptions within Anti-Virus software settings. We recommend installing Microsoft Fix 50410 to prefer IPv4 over IPv6. This software can be found here: - https://support.microsoft.com/en-us/kb/929852 - Choose the following download: Prefer IPv4 over IPv6 in prefix policies.

Issue How to add Web Service and create Simple XML Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add XML files and how to add to a project or site How to create values from the XML Files added How to make a graphic that uses the values from XML Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: Are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Weather for a particular location data using Simple XML: Select New > Interface > Web Service > Simple XML Specify the URL for this data (to find the weather for your area, Google XML data Make changes to polling, alarm, retry interval Choose Create Now you can Create a value from that Simple XML Web Service by highlighting and select New > Value > and type of value. Select Analog for temperature, String Value for wind direction and so forth. One can add as many of the values as desired. The Simple XML List View would look like the below screen capture. Lastly for Simple XML Web Service a graphic is created and the values which come from the XML Web Service are place on the page. Also check out the SmartStruxure - Web Services - Simple XML Interface Quick-Help video on the Exchange.

Issue How and when are Modbus points polled? Product Line EcoStruxure Building Operation Environment Building Operations Enterprise Server Building Operation Automation Server Cause Need to understand the Modbus poll mechanism Resolution Consult the 'Modbus Deep Technical Reference' chapter of EcoStruxure Technical Reference Guide Or use WebHelp to find information on the Modbus Poll Manager, which manages all polling of the points/data and devices, and the Poll List which contains all the current subscriptions (eg. data being referenced within Programs, Listviews, Graphics, Logging, etc) These mechanisms isolate the Modbus Polling from programs and graphics. Note: For each network, the poll manager operates with a poll list and a poll task. If a Modbus Object value is only required for logging purposes, then the  "Requested poll interval" is set to a high number (typically 2,147,483,647 ms) This means the object values are not currently being polled. When the time arrives for the log value to be collected, the "Requested poll interval" is set to 1000ms, until the value is collected, at which point it reverts to this higher number.

Issue What is the compatible SpaceLogic BACnet/IP device firmware version for my EBO or Tridium Niagara N4 installation? Product Line EcoStruxure Building Operation, TAC IA Series Environment SpaceLogic BACnet/IP devices Tridium Niagara N4.10 and later versions Jace 8000 Tridium Niagara N4.10 and later versions Enterprise Server  Cause The SpaceLogic (formerly known as SmartX) IP Controllers shipped from the factory may not have the latest firmware installed. It is essential to verify that the controller has the latest firmware build loaded for the EcoStruxure Building Operation version or Tridium Niagara N4 build being used before programming the controller. Resolution The below table contains the supported SpaceLogic BACnet/IP devices firmware for each EBO release.  * CPs are available on: EBO Hotfix List Note: Versions not mentioned in the table above are out of full support. Refer to earlier versions' release notes for the older versions' compatibility matrix, refer to EBO- Release Notes and Software Support Policy for EcoStruxure™ Building Operation   Note: RP-C is only supported on EBO 3.0 and later SpaceLogic/EasyLogic versions compatibility SpaceLogic BACnet/IP devices can be upgraded using WorkStation, as explained in Updating Firmware in BACnet/IP Controllers.  SpaceLogic BACnet/IP devices firmware can also be upgraded using the eCommission SmartX Controller mobile application, you can download firmware to either a single BACnet/IP controller or multiple controllers, even if not hosted. This is only supported over an IP connection, as explained in Using the eCommission SmartX Controller Mobile Application to Download Firmware to BACnet/IP Controllers   Tridium Niagara N4 Compatibility Note: Previous to Version 1.0, SpaceLogic BACnet/IP devices firmware is only approved at v3.02.03 for Jace 8000 and Niagara Enterprise Server using N4.10 and newer platforms. Starting in Version 2.0 (Build 77) firmware v4.00.04.02002 CP1 is approved for use.  Make sure and reference the controller type in the table above as well. Release Notes  Starting with Version 3.1 (Build 85), firmware 6.00.03.03007 CP2 and 7.x RC can be employed. The EasyLogic controllers are supported by the Niagara modules with these releases.  N4.10, 4.13 and 4.14 are the only versions with these modules. Product Annoucement      

Issue For further information, refer to the FLEXnet Licensing End User Guide, available on the Flexera website. Product Line TAC Vista Environment Vista 5 Workstation FLEXnet Licensing Cause If you get this error and attempt to find the End User Guide, you will discover that the company that produces the FLEXnet software has gone through several name changes: Macrovision to Acresso to Flexera. Resolution If you would like a copy of this document, you can find the FLEXnet License Administration Guide (previously called the End User Guide) here.

Issue What are the PinOuts for the RS-232 Connection of the older 1st Generation CX controllers to connect through Hyper terminal. Product Line Andover Continuum Environment Hyper Terminal Continuum CX Gen 1 CX9900 Continuum CX Gen 1 CX9940 Continuum CX Gen 1 CX9400 Continuum CX Gen 1 CX9410 Continuum CX Gen 1 CX9200 Cause Need to direct connect to a first-generation controller to configure its IP address and ACC Net ID. Resolution The Hyper Terminal cable needs to have the below pinouts. RJ Connector - - - - - - - - - - - - - 9 Pin RS-232 PC Controller Comm3 Pin 1 - DTR - - - - - - - - - - - - - Pin 6 - DSR Pin 2 - CTS - - - - - - - - - - - - - Pin 7 - RTS Pin 3 - CXD - - - - - - - - - - - - - Pin 1 - CXD Pin 4 - RTS - - - - - - - - - - - - - Pin 8 - CTS Pin 5 - GND - - - - - - - - - - - - - Pin 5 - GND Pin 6 - RD - - - - - - - - - - - - - Pin 3 - TD Pin 7 - DSR - - - - - - - - - - - - - - Pin 4 - DSR Pin 8 - TD - - - - - - - - - - - - - - Pin 2 - RD On the RJ connector for the controller's comm3, Pin 1 is the furthest to the left with the insert clip facing away from you and the gold teeth facing you (download drawing). For the CX9200 and CMX controllers download the pinouts here. Download Command Terminal Reference Guide here

Issue Send an SMS text message when an alarm occurs. Product Line EcoStruxure Building Operation Environment Alarming SMS Text Cause Sending an SMS Text message in response to an alarm condition will allow the responsible personnel to react immediately, even if they are not currently at the workstation. Resolution EcoStruxure Building Operation does not support direct SMS texting. One workaround is to use an Email to SMS Test service provider that handles conversion of emails to SMS, as emails are easily created in EcoStruxure Building Operation.   If direct SMS functionality is required there are work arounds with 3rd party programs such as SysManSMS via file output options (see Using Sysman alert server with StruxureWare Building Operation). Note that this third party products such as this are not supported or tested by Schneider Electric.

Issue Looking for more information on the Schneider Electric Advanced Display offering from the Smart X family of controllers. Product Line EcoStruxure Building Operation Environment SmartStruxure SmartX Controller Advanced Display Technician Tool Mobile App Cause Unsure where to locate more detail about the Advanced Display and do not know the part numbers to order the products. Resolution The Advanced Display is a convenient option for users to access, monitor, and service their SmartStruxure system. For additional information please reference the SmartX Controller - Advanced Display documents found on the The Exchange. Applications The Advanced Display comes with the SmartXKiosk application already installed on it. This app, when launched, limits which other applications may be accessed on the tablet. The only way to exit the Kiosk mode is to enter a six character PIN. Any of the available Schneider Electric apps found on the Google Play Store can be added to the SmartXKisok. Technician Tool mobile app AdaptiApps custom user apps WebStation The Technician Tool provides a simplified user interface for operation and maintenance of the SmartStruxure solution.   Communications and Wiring Options Communication Options Available Availability Wi-Fi to the BMS network (requires straight USB cable) All SmartStruxure versions USB direct communication to the Automation Server (requires Y-shaped USB cable) Versions 1.7 and newer Wi-Fi or USB direct communication to the Automation Server Premium (requires straight USB cable) Versions 1.7 and newer   The Advanced Display communicates with the SmartStruxure servers through an access point or starting in version 1.7 directly to the Automation Server via the USB port with the application named SmartX-Ad Link. If using an Automation server, the Y-shaped cable must be used to connect to a locally sourced power supply as well as to the Automation Server. The power required is 5 VDC with a minimum of 500 mA up to 1.3 A. The USB port on the Automation Server Premium (AS-P) has the ability to power the tablet directly thus only requiring a straight USB cable.    Ordering Part number Description SXWADTAB410001 Advanced Display 7 - inch - - No longer available! SXWADBUND10002 Advanced Display 10 - inch Bundle Includes Advanced Display tablet unit, mounting frame, bezel, and Micro USB 2.0 data cable 1 m (3 ft) SXWADUSBA10001 USB cable, Straight 1.5 m (5 ft) for connection to AS-P or AS-B SXWADUSBA10002 USB cable, Straight 3.0 m (10 ft) for connection to AS-P or AS-B SXWADUSBB10001 USB cable, Y-shaped 1.5 m (5 ft) for connection to Automation Server SXWADUSBB10002 USB cable, Y-shaped 3.0 m (10 ft) for connection to Automation Server   Note: The Advanced Display 10 - inch Bundle does not include a power adapter.  For configurations where the external power adapter is required the appropriate power adapter must be ordered separately for the country in which it will be installed.

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue A warning banner is displayed at the top of the Workstation window that states "A license violation has been detected." even though a valid evaluation license has been activated on the machine or site. The user will also find another warning message on the LicenseManager screen, under the System folder, that provides greater detail. This message will state specifically what is missing, for example "An additional X automation server license(s) are required. Please purchase the required licenses." Product Line EcoStruxure Building Operation Environment EBO Enterprise Server 2.X and newer EBO Workstation 2.x and newer Cause The new scalable licensing structure established in version 2.0 requires licenses for each automation server device (and field devices if the system is a new database). The evaluation (demo) license will account for the required licenses as long as it is valid but sometimes can be stuck in a state where it has not been validated.  Resolution In the majority of situations, simply rebooting or performing a warm start of the Enterprise Server will clear this warning as long as there is a valid evaluation (temporary) license hosted in the license administrator the ES is referencing. Troubleshooting Steps: Restart the Enterprise Server. Restart the License Server (if on a different machine as the ES). If required, restart the ES again. Check for any errors in the License Server and verify that the Vendor Daemon is up and running. See Unable to log into WorkStation due to license error codes -12, -15, -18 or -97 for more details around this troubleshooting step. If these steps have not resolved the issue, then open a support case with your local country support organization.  For more information about the enforcement of licenses see the EcoStruxure Building Management WebHelp article, Licensing Enforcement. 

Issue How to change the firmware version in a controller. Product Line Andover Continuum Environment All flash-upgradeable controllers: CX9900, CX9940, ACX5720, ACX5740, all i2, b3, and bCX controllers.  Cause Controller firmware needs to be changed. Resolution Locate the firmware version that you need for each controller you want to change. The Continuum firmware files can be downloaded from the Schneider Electric Ecobuilding Exchange. The downloaded files are often a zip file which includes the release notes in PDF format and the flash file (UPD file). Note: You may need to upgrade or downgrade firmware (see also Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum?) Make sure you check the document Andover Continuum Software and Firmware Compatibility Matrix for the appropriate firmware version for your system.   Copy the file to a disk drive accessible to your CyberStation workstation. Edit the controller object in ContinuumExplorer and click on the "Update OS" button. Browse to the file location in step 2 and click "Open". A progress box "Updating Controller OS..." will appear. During this time the controller is reset and not functional.  Once complete, and if successful, you will get  a dialog box indicating that the upload was successful and the controller will return On-Line momentarily. Click OK. Click the refresh button in the controller editor. Once the controller is on-line the version field should indicate the new version. At this point some controllers may need a reload, others will be reloaded from flash memory. This depends on the controller type. For example, the CX9900 has no flash memory and therefore will need to be reloaded. This procedure also applies to upgrading controller options such as adding Xdriver support. In this case a UPD file will be provided by the Repair Dept. In the case of added Xdriver support, after doing the Update OS procedure the version will not change. Look at the controller Options tab after it comes back online following the upgrade. The information here, such as a non-zero entry in the numbers next to the appropriate Xdriver Commport will be changed. The above procedure was based on an IP level controller such as the CX, bCX and ACX II. Infinet and MSTP controllers are done in a similar manner. IOU models are also upgraded similarly via the "Update IOU" button in the IOUModule editor. However, the files are .IOU files instead of .UPD files and the versions are in the fourth pair of characters in the Program ID field.  

Issue Documentation supplied with new UNC, ENC, or Jace 8000 was discarded.  Is there a way to determine the default, the factory-defined IP address, for the Ethernet port on the controller? Product Line TAC IA Series Environment I/A Series (Niagara) R2 UNC I/A Series (Niagara) G3 ENC Niagara N4 or G3 Jace 8000 Cause Lost or discarded document, shipped with the controller, that contained the configured IP address. Resolution The default Ethernet IP address for an I/A Series (Niagara) UNC or ENC is based on the serial number and type of device. For a UNC or ENC, the default address is 192.168.1.14X where X is the last digit of the device serial number.  The default serial number is found on a sticker on the controller circuit board.  This sticker has the full model number, date code, and the serial number of the controller.  The serial number is preceded with S/N:.The subnet mask is 255.255.255.0 in all UNCs, ENCs, and Jace 8000 The default address base address (192.168.1.140) is the same for all UNC-410, UNC-510, UNC-520, ENC-410, and ENC-520 controllers. The default IP address of a Jace 8000 for PRI (LAN1) is 192.168.1.140.  SEC (LAN2) is by default disabled.

Issue Activation of the Security Expert SSN with a new installation of the client software, software extensions (e.g. SX-VIM, SX-DOR-50) and integration licenses (e.g. SX-NVR, SX-CAM-10) need to be completed manually because there is no Interne access. Product Line EcoStruxure Security Expert Environment Licensing Cause The computer which the Security Expert client is installed on, does not have Internet access to use the 'Automatic License Update' method to activate the license. The manual method must be used to register and obtain the new license. Resolution In the Security Expert client go to About | License | information make a note of your system's SSN In the Security Expert client go to About | License | License Update and select Generate a License Request File for this System Copy the 'ICT_LicenceRequest.req' license request file produced onto a machine that has Internet access. Navigate to https://se.ict.co/license/ and enter your details on this web page. Enter the SSN for your system Upload the 'ICT_LicenceRequest.req' license request file generated previously and Submit. You should then be able to download a 'Security Expert YJWB...............O4PJ5W License.lic' file. Return to your offline Security Expert Client and go to About | License | License Update , Select Browse for your Downloaded License file Select the 'Security Expert YJWB...............O4PJ5W License.lic' file downloaded previously. Once the license update is complete shut down the client and restart the services   Support for manual activation: v4.2.194 - Manual activation is supported. v4.2.216 - Manual license activation's are no longer supported and an Internet connection is required on the Security Expert installation to be able to perform a new activation or update a license. v4.2.243 - Manual activation is supported. v4.3.x - Manual activation is supported.

Issue Connecting a serial cable to a Xenta 5/7/9xx controller Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Xenta Servers have a service portal for use with HyperTerminal with a serial connection to the RS-232B port. Resolution Connect a serial cable, Programming Serial Kit, part no. 0-073-0920-0, between the PC and the RS232 port B on the TAC Xenta.  For more information about the cable see Cable Guide OFL-3972. Go to Start/All Programs/Accessories/Communications/HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. NOTE: Product support has also witnessed strange behavior with serial connections when certain laptops were not plugged into a power source or the Xenta Server was not grounded. If connection problems persist after the connection setting above are verified, make sure the Hyperterminal PC is plugged into a 120 vac power source.

Issue Integration to the Powerlogic CM4000 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic CM4000 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV property  0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue  EBO can have license violation bar without a known reason. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause License enforcement is the process of checking whether a software application has a valid license available to it at runtime. If you do not have enough licenses, a license violation occurs. This is accomplished by a license violation bar in WorkStation and WebStation.   Firstly, the license violation will be yellow, and it can be hidden for 8 hours. You can use Hide to hide the License Violation bar for 7 days. After 7 days, the Hide function is disabled. After 30 days, the bar turns red. Resolution Below information can be collected to help in troubleshooting: Refer to the document Part Number Summary and Hardware Software Matrix for software and features that need licenses and note that some feature licenses can be inherited from parent server to child servers. Get a screenshot of the License information page in the control panel, make sure to have all content in license information page are shown in the screenshots, ex child servers' status. It can tell which feature needs a license or which child server needs a license, refer to License Information Get the License Diagnostics, and entitlement certificates to make sure that required licenses are activated. Install the latest CP/hotfix to make sure that the system is not affected by one of the known license related defects, Make sure that all EBO servers have correct date and time, incorrect date and time can cause license violation, as explained in: Incorrect Automation Server date and time leads to license violation - Schneider Electric Community Check Known issues community. Get screenshots for the following: In ES, "System/LicenseManager/LicenseStatus/ConnectedASLicenseStatus" will show all connected Automation Servers. Show the license violation tab to know which Automation Server has violation as Automation Server may have violation although license information doesn't show that, ex. if the "Change Control" feature is enabled in an Automation server and ES doesn't have a license for it. For parent server and any server that has violation, search in folder "/System/LicenseManager/LicenseStatus". In the object name, write "*" and add columns License Violation, Checked Out License, Available Licenses, Required Licenses, and Installed Licenses. Export the results to XLSX. Check license Metadata for the parent server and any servers have license violation, search in folder "/System/LicenseManager/LicensingMetadata". In object name, write "*" and add columns FeatureVersion, FatureName, ProductVersion, EntitlmentID and Activation ID. Export the results to XLSX.   Get screenshot from FlexNet Publisher web interface, localhost:8888, concurrent tab. Make sure all features are shown in the screenshot, and the entire webpage can be saved instead of taking screenshots. If the server has just started, wait for some minutes till all data is collected.   Collect the logs and configuration files listed below: Log files located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\logs Configuration file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\conf Using EBO WorkStation, go to module, '/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.licensemanager", set trace level to debug, reproduce the issue, if possible. Collect the server logs, then set the module trace level back to "information", refer to Collect logs from an Automation Server - Communities and Collect logs from the Enterprise Server and Enterprise Central - Communities.